Run the Problem, Not the Update
The builder PM’s approach to keeping executives engaged across complex, evolving work
What would it take to scale this?
This question comes as you update the leadership team on your first few customer wins.
Each one was hard won.
You were pulled into sales, delivery, and finance at every step.
The product works, but only with a lot of coordination.
As you worked across internal and external teams to onboard each customer, you thought about scaling. But it was always too early.
Stepping into builder PM work is what enabled these wins. Now your leadership team wants to repeat this at scale.
Your excitement drains out as you think about your response.
Because you realize this isn’t a single pretty set of slides.
And more importantly, you realize you’re not the only one trying to figure it out.
The leaders asking about scaling your complex solution aren’t waiting for a fully polished answer.
They’re trying to stay engaged while the answer is forming.
They want to be involved in:
the tradeoffs
the constraints
the direction it takes across the organization
What they need isn’t more answers.
They need a way to participate without getting pulled into the weeds and without slowing the work down.
The Challenge: Leadership Participation While Building
This is the shift that comes with builder PM work.
You’re no longer expected to figure it out first and present it cleanly.
You’re expected to drive it forward with leadership involved.
You’re running a problem that:
spans functions
evolves over time
and requires leadership to stay engaged to reach a real conclusion
Handled well, this is how you:
build trust with executives
drive meaningful outcomes
and move on to the next problem with momentum
Handled poorly, you either:
become the bottleneck, carrying everything yourself
or lose alignment before the work lands
Most advice focuses on better updates.
But this isn’t an update problem.
It’s a system problem.
You need a way to:
let the work evolve
keep leadership engaged at the right level
and drive the whole thing toward a conclusion over time
A System for Building with Leadership Engagement
The builder PMs who do this well run a different operating model. They treat executive engagement as part of the system, not an interruption to it.
It starts with recognizing that you’re not just updating leadership on progress.
You’re running a problem that needs to converge over time with leadership involved.
That requires a different kind of structure.
1. Hold a persistent leadership question
Most executive conversations drift because the question keeps changing.
One week it’s about scaling.
The next it’s about margin.
Then it’s about delivery risk.
Builder PMs anchor the work to a single, persistent question that doesn’t reset each time:
What would it take to make this consistent across customers?
What has to be true for this to scale?
Everything else, such as updates, insights, analysis, connects back to that.
It gives leadership something to stay oriented around.
And it gives the work a sense of accumulation instead of motion without direction.
2. Show movement through decisions, not updates
A common trap is to show how much has been learned.
But executives aren’t tracking learning. They’re tracking whether the problem is getting closer to resolution.
So instead of:
what you explored
who you talked to
what you discovered
Translate progress into:
what is now clear
what has been decided (even implicitly)
what remains unresolved
Over time, this creates a visible sense of convergence.
The work starts to feel like it’s narrowing toward something real.
3. Separate exploration from what you surface
The work itself will be messy.
You’ll:
follow threads that don’t pan out
uncover edge cases
revisit assumptions
That’s necessary.
But not all of it belongs in the leadership conversation.
Builder PMs run two tracks in parallel:
a wide exploration space where the work evolves
a narrow leadership narrative where only decision-relevant pieces show up
This is about making sure what becomes visible helps the problem move forward, instead of expanding it.
4. Set guardrails with your manager early
If you don’t define how you’ll operate, your manager will default to reviewing everything.
Managers don’t know where the edges are and they want to contribute.
Early on, align on:
what needs to be fully baked before going up
what can be shared while still evolving
where you’ll pull them in vs. move independently
This creates space to move faster, while keeping trust intact.
And it prevents the “heavy time drag” that shows up when everything routes through one person.
5. Control visibility to create contribution
More visibility isn’t always better.
If you show too much too early:
you create churn
you invite premature decisions
you expand the problem again
If you show too little:
leadership disengages
or re-enters unpredictably
The goal is to make specific parts of the problem visible at the moment they benefit from executive input.
Not to inform.
But to invite contribution at the right level:
tradeoffs
constraints
directional calls
That’s what keeps leaders engaged without pulling them into the weeds.
6. Close loops aggressively
One of the fastest ways to lose momentum is to leave things half-resolved.
Even small ones.
If something has been addressed, close it clearly:
what was explored
what was decided
why it’s no longer in play
Otherwise, it comes back.
And each time it comes back, the conversation expands instead of converging.
7. Design toward a conclusion
This is the part that often gets missed.
A lot of cross-functional work continues indefinitely because it’s never structured to finish.
Builder PMs are always working toward:
a clear set of decisions
a stable system or approach
and a point where the problem no longer needs executive attention
Because “done” often means it’s now operationalized.
That’s what allows you to:
build credibility
free up leadership attention
and move on to the next meaningful problem
Bringing it together
When this system is working, a few things change:
Leadership conversations start where the last one left off
Executives engage on decisions instead of reopening context
The problem feels like it’s getting smaller, not bigger
And you’re no longer carrying everything yourself
You’re still doing the work.
But you’re not doing it alone, and you’re not waiting until the end to make it real.
You’re running it in a way that lets it actually land.
I’ve put together a companion guide with:
real scenarios (new PM → senior PM)
templates for exec readouts and decision framing
scripts for aligning with your manager without slowing down
It’s designed to help you run your next problem like this, not just understand the concept.
Conclusion - Building while keeping leadership involved
The goal is to run the problem in a way that lets executives contribute at the moments it matters most.
Because at this level:
you don’t get full clarity upfront
you don’t get uninterrupted time to figure it out
and you don’t get alignment for free
You build it.
Over time.
Across functions.
With leadership engaged along the way.
When this works, something important shifts:
You’re no longer the person carrying the problem.
You’re the one structuring it so it can be solved.
And that’s what allows you to:
drive real outcomes
build trust with senior leaders
and take on the next problem with momentum
Q&A on building with active leadership
Would this be easier if I let everyone know this is for a named leader?
No. This is your initiative to lead and you don’t need to say this is “requested by a specific leader”. You can keep people updated on the perspective you intend to provide to leaders. Teams can use this information to get feedback from their functional leaders.
How do I know the leadership team wants to be involved like this?
Flat organizations that move fast are waking up to this new approach. However, you won’t hear your leaders ask to participate; they don’t have time for that.
You will sense these perspectives:
“Bring me into the decisions that matter”
“Don’t wait until it’s fully formed. I’m part of shaping it”
“Show me how this is progressing toward something scalable”
“Help me engage without pulling me into the weeds”
Builder PMs are new and leadership teams are learning builder approaches too.
What if leadership keeps changing direction?
That’s usually a signal the problem isn’t anchored tightly enough.
Go back to the persistent question.
If the question is shifting, the work will too.
Re-anchor the conversation before trying to stabilize the answers.
How do I know if I’m showing too much vs too little?
If the conversation keeps expanding, you’re likely showing too much.
If leadership disengages or re-enters unpredictably, you’re likely showing too little.
The right level creates decisions and not new threads.
What do executives want from builder PMs in these situations?
Not updates. Not detail.
They’re looking for three things, consistently:
1. Signal of convergence
“Is this getting clearer—or just more complex?”
They want to feel the problem is narrowing toward decisions, not expanding with new insights.
2. Decision framing (not raw information)
“What am I being asked to weigh or decide?”
They don’t want the full landscape.
They want the shape of the tradeoffs.
3. Confidence the system is being handled
“Do I need to get involved deeper or is this under control?”
This is the big one.
If they don’t feel this, they will:
dive into details
reopen settled topics
or disengage entirely
Keeping the exploration separate from the executive perspective lets the executives contribute at their level.
Looking for more practical tips to develop your product management skills?
Product Manager Resources from Product Management IRL
Product Management FAQ Answers to frequently asked product management questions
Premium Product Manager Resources (paid only) 4 learning paths, 6 product management templates and 7 quick starts. New items monthly!
Connect with Amy on LinkedIn, Threads, Instagram, and Bluesky for product management insights daily.
Thank you for this!