We scan new podcasts and send you the top 5 insights daily.
When an executive gives a highly specific suggestion, don't just blindly implement it or ignore it. Build their version exactly as requested, but also prepare two other versions you feel good about. This acknowledges their input while creating a productive forum to debate the merits of different approaches.
Product leaders often feel they must present a perfect, unassailable plan to executives. However, the goal should be to start a discussion. Presenting an idea as an educated guess allows for a collaborative debate where you can gather more information and adjust the strategy based on leadership's feedback.
As seniority grows, a leader's casual thought can be misinterpreted as a direct order, derailing a team. To counter this "executive megaphone" effect, leaders must be explicit about their intent by labeling all feedback as either an "idea," a "suggestion," or a required "action item."
Feedback, especially from leaders, can be ambiguous. The 'Do, Try, Consider' framework clarifies intent: 'Do' is a required change, 'Try' is a suggested exploration, and 'Consider' is a low-priority idea. This helps designers prioritize and act on feedback without misinterpreting suggestions as commands.
To empower your team, enforce the '1-3-1 rule' for problem-solving. Before anyone can escalate an issue to you, they must define the one problem, research three potential solutions, and present their single best recommendation. This forces critical thinking and shifts the team from problem-spotters to problem-solvers.
Leaders can reduce team anxiety and prevent misinterpretation by explicitly categorizing input. 'Do' is a direct order (used rarely), 'Try' is an experiment, and 'Consider' is a low-stakes suggestion (used 80-85% of the time). This ensures a leader's random thoughts aren't treated as gospel.
When leaders demand high-fidelity prototypes too early, don't react defensively. Instead, frame your pushback around resource allocation and preventing waste. Use phrases like "I want to make sure I'm investing my energy appropriately" to align with leadership goals and steer the conversation back to core concepts.
Early-stage ideas are easily killed by practical objections. To prevent this, implement a rule where feedback must begin with "Yes, and...". This forces critics to be additive and constructive, building upon the initial concept rather than immediately shutting it down. It creates space for a bold idea to develop before facing harsh reality checks.
When presenting a strategy to leaders who like to 'leave their mark,' proactively design a space for their contribution. Instead of a sealed plan, explicitly ask for their opinion on a specific area. This satisfies their need to add value and makes them a co-owner of the strategy, increasing adoption.
When a senior stakeholder proposes a potentially disruptive idea, direct resistance ('pushing') is counterproductive and strengthens their resolve. Instead, 'pull' them into a collaborative exploration. Acknowledge the idea, discuss the underlying problem it solves, and then gently steer the conversation back to how it aligns with the agreed-upon North Star, defusing tension.
When giving feedback, structure it in three parts. "What" is the specific observation. "So what" explains its impact on you or the situation. "Now what" provides a clear, forward-looking suggestion for change. This framework ensures feedback is understood and actionable.