Managing Expectations Like a Pro

Welcome to the 2nd newsletter, week to week. Am I finally finding the rhythm to publish regularly? Hope so!

Also, it’s the last week to sign up for my and Aakash Gupta’s premium 10-week cohort:

https://www.landpmjob.com/

We build it so that you are ready to land your next PM job, even in the current challenging times.

Hurry up, it’s the final days of open sign-ups.

Now, to today’s story:

Every manager wants every project done now, with great quality, all at once.
And as every Product Manager knows, that’s simply impossible.

We’ve all been there: a leader storms into your meeting, animated by urgency, demanding a critical feature yesterday. They may not know (or care) about your dependencies, tech debt, discovery work, or design bottlenecks. What matters to them is outcomes, fast.

By the time they’re demanding impossible timelines, it’s already too late to fix the dynamic easily. The relationship has already been framed: they demand, you defend.

But there’s a better way.

If you consistently manage expectations before the tension builds, you’ll earn something far more valuable than short-term wins: long-term trust.

Here are eight principles I’ve learned, often the hard way, to prevent unrealistic demands and build relationships that scale with you.

1) Don’t treat a roadmap as a Gantt chart

A roadmap is not a delivery plan. It’s a statement of direction, not deadlines.
It’s meant to show what you’re exploring, why it matters, and where you’re heading, not a promise of fixed delivery dates months in advance.

The moment your roadmap turns into a static Gantt chart, you lose flexibility. And when priorities inevitably shift, you appear unreliable.
Set the expectation early that your roadmap is a living document, constantly refined as new data and insights emerge.

2) Communicate any problems along the way

Silence kills trust faster than bad news.
When delays, blockers, or resource issues arise, share them early. But don’t just dump the problem, explain the context, the trade-offs, and what’s being done.

Stakeholders handle bad news surprisingly well when they see ownership and reasoning. Transparency turns uncertainty into confidence, even when progress slows.

3) Prioritize based on universal rules

Prioritization shouldn’t feel like a tug of war.
Establish a clear decision framework, for example, connecting each initiative to measurable outcomes like revenue, retention, or strategic advantage.

That way, when someone asks, “Why not this feature?”, you can point to the shared framework instead of subjective preference.
It transforms prioritization from emotion-driven negotiation into rational alignment.

4) Request additional resources when it makes sense (and stress when adding those won’t help)

“Just add more people” is one of the most common misconceptions in product delivery.
Sometimes it works. Often, it doesn’t.

Adding new people increases communication overhead and slows down coordination. Be clear about when resources will actually accelerate outcomes, and when they’ll just complicate them.
This shows you’re thinking systemically, not just pleading for help, but optimizing for real impact.

5) Define "done" together

You’d be surprised how many projects go off the rails because teams and stakeholders never agreed on what “done” actually means.

Is it when the feature ships? Will it be used by 50% of your target users? When will it move a key metric?
Aligning on the definition of success early prevents disappointment later. You’ll be judged by shared standards, not hidden assumptions.

6) Use trade-offs as teaching moments

Every “yes” implies a “no.”
When new requests appear, don’t just reject them; show their consequences.

If we prioritize X, Y will move to the next quarter.
If we shift scope, quality, or testing time will shrink.

Over time, these conversations teach your stakeholders how product decisions are made, and they start framing their asks with trade-offs in mind. That’s when you know you’ve built real alignment.

7) Share progress visually, not verbally

A weekly written update or dashboard beats ten status meetings. Visualizing progress, even in a simple Notion board, Miro map, or lightweight roadmap view, gives everyone the same source of truth.

It reduces repetitive “how’s it going?” questions, keeps focus on outcomes, and lets stakeholders self-serve answers instead of interrupting your flow.
Visibility kills anxiety, and anxiety drives most unreasonable demands.

8) Anchor conversations in outcomes, not effort

When you talk about timelines, avoid focusing on how much work something is. Focus on what it achieves. Instead of saying, “This will take 6 weeks,” say, “In 6 weeks, we can have users applying twice as fast.” This framing helps leadership see progress as value creation, not just calendar time, which makes your negotiation room bigger.

Final Thoughts

Building the right expectations is not about saying “no” more effectively. It’s about building a shared understanding of why certain things take time.

You’re not there to protect your team from leadership, but to connect leadership’s ambition with the team’s capacity to deliver.
That’s what makes a Product Manager a bridge, not a bottleneck.

Thank you for making it till the end and see you in the next edition :)