Phillip Starke
How we used quarterly planning to align and protect teams

Quarterly planning should not be necessary, but it often is. Here is the four step process we used and three things that make it work.
Phillip Starke

Quarterly planning should not be necessary, but it often is. Here is the four step process we used and three things that make it work.

Trying to hide one's insecurity is one of the main causes of waste in product development that no one is aware of. The solution: transparency.

A lack of trust is the main source for meddling and micromanagement in product development. Communication is the way to build trust. Here is how to go about it.

Any team profits from writing down team purpose and team values. What are these artifacts? And what is the easy way to define them?

Many have to deal with low performers in teams. The good news: underachieving is not a character trait. You can do something about it.

If you are trying a new approach within an established organization you will face headwinds early on. How to get going? Build something!

Many claim to be data driven in their decision making. But no one ever explains what that actually means in practice. While making data driven product decisions sounds great in theory, actually doing so is not always easy. The way to get there may seem straightforward but many struggle with the details.

In product development it seems to me that there is too much focus on labels and specific frameworks or methods. Regardless of how we get there, many seem to forget that the goal is always to create successful products. The goal is successful product development. What does this mean?

In product development, changing priorities are frustrating. Luckily, there are best practices in dealing with frequent strategic shifts.

Turnover is tech is high. The main reason for this is poor leadership. Fortunately, there are things you even if you have no formal power.