Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Senior leaders often suggest specific solutions not because they're attached to the idea, but because they see an urgent business problem going unsolved. This is a cry for help. Focus on their desired business outcome, and you can nudge their idea towards a better solution that achieves it.

Related Insights

Instead of solving problems brought by their team, effective leaders empower them by shifting ownership. After listening to an issue, the immediate next step is to ask the team to propose a viable solution. This builds their problem-solving and decision-making capabilities.

Product managers frequently receive solutions, not problems, from stakeholders. Instead of saying no, the effective approach is to reframe the solution as a set of assumptions and build a discovery backlog to systematically test them. This builds alignment and leads to better outcomes.

Instead of pitching a new idea in a vacuum, connect it directly to a leader's existing priorities, such as market disruption or a specific annual goal. This reframes your idea as a way to achieve their vision, increasing the likelihood of approval.

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.

When customers talk, trust their articulation of what they're trying to accomplish (demand) and why their current tools fail (supply problems). However, completely disregard their suggestions for what product or feature you should build (supply they want). That is your job to design, not theirs.

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.

When handed a specific solution to build, don't just execute. Reverse-engineer the intended customer behavior and outcome. This creates an opportunity to define better success metrics, pressure-test the underlying problem, and potentially propose more effective solutions in the future.

Don't be afraid to surface problems to executives, as their job is almost entirely focused on what's not working. Withholding a problem is unhelpful; clarifying and framing it is incredibly valuable. Your champion isn't offending their boss by raising an issue, they're demonstrating strategic awareness.

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.

Customers often suggest solutions (e.g., "add this feature") based on their limited understanding of what's possible. A founder's job is to look past the specific request and identify the core problem or desired outcome. Building exactly what the customer asks for verbatim is a mistake; solving their underlying goal is the key.

A Leader's “Go Build This” Is a Signal that a Business Problem Is Unsolved | RiffOn