Back to resources

How to Grow a Planning Mindset

Managing Expectations
Team Processes
Prioritization

23 January, 2021

Chitrak Ojha
Chitrak Ojha

Director of Engineering at Twilio

Chitrak Ojha, Engineering Manager at Twilio, tells how spreading planning throughout a quarter and involving as many people in the process will give planning the importance it deserves.

Problem

Planning is often only discussed towards the end of a planning cycle -- usually a quarter -- when most of the people responsible for the execution will be excluded from the planning. Even when there is an effort to make the process more participatory, people are brought in when key decisions are already made and when they can’t significantly influence the process.

Instead of including some people at some time, the planning should become a centerpiece activity that would require people to make an intentional effort to plan throughout a planning cycle.

Actions taken

As a manager, my first goal was to get teams into a habit of planning consistently. To do so, I had to create an environment where rather than intensifying the planning towards the end of a quarterly cycle I could encourage them to develop and nurture the habit of consistently looking ahead and not only being focused on what is going on at the moment.

That required a significant mindset change since teams would typically spend more time planning toward the end of a quarter, squeezing in all the planning activities in the last two weeks of the quarter.

The most important thing I had to do was to include the whole team and promote the planning mindset among all team members. People on the business or product size of things are more inclined to look ahead, but I wanted to include people on the team who would execute on things. Moreover, involving them earlier in the process could result in feedback beneficial to the planning itself.

I introduced weekly planning sessions lasting from 30 minutes to an hour and the focus of these sessions was on the next cycle. As soon as a quarter would begin, we would start having discussions about the next quarter. We would start discussing a set of items and their validity and as time would pass, the discussions between Engineering and Product would become more concrete and centered around prioritizing the next forward-looking items. After the first half of a quarter, we would be able to prioritize much better and remove the overwhelm that would happen when planning is all stuck in the last two weeks of the quarter.

Also, spreading the planning throughout a quarter helped us better prepare. For example, during the first month of a quarter, we would be discussing a project that would require a lot of discovery and we had to re-align ourselves to include the discovery in our regular activities. In addition, consistent planning could empower the team to create its own team processes that would improve their overall performance.

Lessons learned

  • The consistent planning allowed the team to step back and look at the broader picture that spread beyond the most immediate focus on the current items they are working on. It also allowed them to alleviate the overwhelm of the hectic planning happening at the end of a quarter.
  • Planning improves the alignment between long-term business objectives and priorities that are communicated to Product and Engineering and that are translated into concrete engineering projects.
  • Consistent prioritization also helps with focus. We are constantly prioritizing and are able to differentiate things that should be top priorities and deserve our undivided focus. Therefore, planning is also a path to continual improvement.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Scaling a Team in Two Parts: The Product and Manager

2 August

Viswa Mani Kiran Peddinti, Sr Engineering Manager at Instacart, walks through his experience scaling a team, product and his skills as a leader.

Managing Expectations
Product
Scaling Team
Leadership
Meetings
Viswa Mani Kiran Peddinti

Viswa Mani Kiran Peddinti

Sr Engineering Manager at Instacart

How to Organize, Manage, and Grow Your Team

12 July

Vineet Puranik, Senior Engineering Manager at DocuSign, discusses the impact of roadmaps, organization, and proper management for your teams to procure growth.

Managing Expectations
Delegate
Collaboration
Roadmap
Strategy
Vineet Puranik

Vineet Puranik

Senior Engineering Manager at DocuSign

Building Up Your Technical Skills in a Fast-Paced Industry

8 July

Otavio Santana, Distinguished Software Engineer at Zup Innovation, shares his best practices for upskilling without stretching yourself too thin.

Different Skillsets
Personal Growth
Prioritization
Otavio Santana

Otavio Santana

Java champion, software engineer, architect, and open-source Contributor at Independent Technical Advisor

How to Navigate Your Manager Role at a New Company

1 July

Saikrishna Desaraju, Engineering Manager at Marks & Spencer, draws from his personal experience to advise new managers on thriving in their roles.

Managing Up
Managing Expectations
Leadership
Collaboration
New Manager Of Manager
Changing Company
Saikrishna Desaraju

Saikrishna Desaraju

Engineering Manager at Marks and Spencer

Team Development Framework for new managers

26 June

Individual Contributors are familiar with a technical development framework that helps them with building products. Managers, especially new managers can leverage a parallel framework to help them build their teams while drawing analogies from an already familiar framework.

Building A Team
Team Processes
New Manager
Viswa Mani Kiran Peddinti

Viswa Mani Kiran Peddinti

Sr Engineering Manager at Instacart