Discussion about this post

User's avatar
Bruna Rasmussen's avatar

This is gold! Been working on an outcome-based roadmap and have been facing some challenges with the engineering team. The engineering manager fears having this more "subjective" prediction instead of objective projects, which would allow him to foresee how many people he needs to hire and how to organize the team. Any tips on dealing with it?

Expand full comment
Andrea Saez's avatar

One is about outcomes, the other is about output. I don't think there's a 'choose' but more like, why not use both? Focus on outcomes to plan your strategy, then look at your output and outline how and when things are meant to come through with the appropriate context. The issue generally is when people only choose project-based (timelines) that don't fully communicate the full picture and incorrect expectations are given. However, no harm in having both, if anything, it's probably better!

Expand full comment
11 more comments...

No posts