Product managers who feel "too busy" to provide context are making a false economy. A simple five-minute explanation or Loom video clarifying the "why" behind a task can prevent an engineer from spending a week or more building the wrong thing, offering a massive return on investment.
Related Insights
In an age of rapid AI prototyping, it's easy to jump to solutions without deeply understanding the problem. The act of writing a spec forces product managers to clarify their thinking and structure context. Writing is how PMs "refactor their thoughts" and avoid overfitting to a partially-baked solution.
To ensure clarity and impact, mandate that any explanation of the platform team's work to non-technical stakeholders must be understandable in under three minutes. This forces the team to distill their message to its core value, cutting through technical jargon.
Bupa's Head of Product Teresa Wang requires her team to explain their work and its value to non-technical people within three minutes. This forces clarity, brevity, and a focus on the 'why' and 'so what' rather than the technical 'how,' ensuring stakeholders immediately grasp the concept and its importance.
To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.
Status update meetings are a major productivity drain. Replace them with asynchronous videos (e.g., Loom). This method is more efficient, allowing people to consume updates on their own time. It also conveys more signal—tone, emphasis, and personality—than a written update, fostering better connection on distributed teams.
Contrary to the popular belief that it's always detrimental, for product managers, context switching is a core strength. Fluidly moving between customer, engineering, and marketing conversations is essential for integrating diverse perspectives to bring a product to life.
When pursuing a long-term strategic solution, dedicate product management time to high-level discovery and partner alignment first. This doesn't consume engineering resources, allowing the dev team to remain focused on mitigating the immediate, more visceral aspects of the problem.
A simple but powerful framework for any product initiative requires answering four questions: 1) What is it? 2) Why does it matter (financially)? 3) How much will it cost (including hiring and ops)? 4) When do I get it? This forces teams to think through the full business impact, not just the user value.
Instead of using meetings for context-setting, Loom’s team sends a required 'pre-watch' video walkthrough of the strategy. This forces stakeholders to arrive with full context, allowing the live meeting to be shorter and entirely focused on critique, asking clarifying questions, and making decisions.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.
