Stop rambling in leadership 1:1s


Hi Reader,

What’s one thing you slightly dread…
and when it finally happens, it never quite goes to plan?

There are many contenders.
But for a lot of internal PMs, 1:1s with product or business leadership are right up there.

Talking about your product.
Your roadmap.
Your priorities.
Your asks.

So today, let’s prep together.

And if you don’t have a 1:1 scheduled yet, my hope is this gives you the confidence to set one up.

Today in 10 minutes you will:

  • Understand why 1:1s with leadership actually matter
  • Learn what leaders usually care about (before they say it)
  • Get a reusable 1:1 impact template
  • See a real example that follows it (for real)

Why this matters more than it feels like

You already know this on some level.

Visibility with leadership has a disproportionate impact.

On your product.
On your team.
And yes, on your own career.

As a PM, you’re responsible for more than delivery:

→ getting the right attention
→ securing resources
→ making trade-offs visible
→ explaining why your product matters

Unfortunately (or fortunately), your work rarely speaks for itself at leadership level.

If it does, it often sounds like:
“Good team. Hard workers.”

That’s not enough.

In my previous role as a PM for manufacturing integration products, arguably one of the least “cool” product areas, regular short 1:1s with leadership made the biggest difference.

Integrations aren’t flashy.
They’re not what business leaders naturally gravitate towards.

But because we had ongoing check-ins:

→ leadership knew what was coming
→ they understood the impact
→ they knew me
→ and over time, they felt ownership

That’s when mentorship started to happen.

Most people don’t proactively set these meetings up.
It’s uncomfortable.
It feels like overstepping.

But being proactive here is exactly what puts you ahead of the curve.


Start with how leadership sees the world

Before any 1:1, it helps to step out of the PM bubble and ask:

“What does this person actually care about day-to-day?”

For most product or business leaders, it looks like this:

→ Is the business on track this quarter?
→ Where is value being delivered and where not?
→ What risks could hurt results later?
→ What investments have the best ROI?
→ Where do decisions or escalation help the most?

Whether they ask these questions explicitly or not, they’re always there.

So let’s answer them before they’re asked.


A reusable 1:1 impact template (save this)

You don’t need slides.
You don’t need a long status update.

You need clear framing.

Use this structure for almost every leadership 1:1:

1. Context (1–2 sentences)

→ What changed since last time?
→ Anything new they should know?

2. Impact delivered

→ What outcome moved?
→ What is better now than before?
→ Who benefits from this?

3. What’s next

→ What are you focusing on next?
→ Why does it matter for the business?

4. Trade-offs & risks

→ What can’t be done in parallel?
→ What risk increases if nothing changes?

5. The ask

→ What decision, alignment, or support do you need?

If you can answer these five clearly, you’re doing leadership-level communication.


My very real example from last week

Here’s how this looked in practice.

5 minutes – Personal check-in

I shared context about being new in the team and adjusting to a different pace and mindset.
Commercial operations move very differently than manufacturing operations, and that learning curve affects how quickly we can execute.

I also asked about his week. Simple, but it sets the tone.


10 minutes – Impact delivered

Operational stability & risk reduction

What changed (outcome first):
→ Order placement reliability improved, removing daily workarounds for sales reps during customer interactions.

How we achieved it:
→ We stabilized a business-critical Sales CRM that previously had performance and resource allocation issues.
→ We kicked off remediation work with the vendor to keep the system compliant and supported long-term.
→ A new compliance requirement surfaced that, if unaddressed, would put future operational support at risk and require a significant server migration next year.

Why this matters:
→ We protected day-to-day operations and reduced future operational risk.


Innovation with direct business impact

What changed (outcome first):
→ Quarterly manual payroll corrections are being eliminated, reducing risk and increasing trust in performance data.

How we achieved it:
→ We’re automating sales performance calculations that previously required manual corrections every quarter.
→ We now have a working version and started user sessions.
→ Sales reps and managers are excited about having live metrics, roll-ups, and KPIs instead of static reports.
→ Early feedback is shaping which views are most useful for decision-making.
→ We started designing how to bring this data internally, enabling cross-region comparisons and real store-level insights.

Why this matters:
→ Less manual effort, fewer errors, and better decisions for both managers and reps.


10 minutes – What’s next + blockers (and the decision)

The trade-off:
→ Mandatory compliance work may need to take priority over parts of the data hub innovation, depending on the outcome of the server migration investigation.

The risk if we don’t act:
→ Delaying compliance could put future operational support at risk.

The consequence:
→ One planned innovation around media performance would move further down the timeline if vendor data consistency issues are not resolved by the end of February.

The ask:
→ Alignment on prioritizing operational compliance over one innovation stream if the risk materializes.


A quick note for visual learners

I didn’t use slides in this 1:1.

The conversation itself was verbal and structured using the template above.

This visual is a summary learning artifact for those who process information better visually.
It captures:
→ what changed
→ where impact was delivered
→ and which trade-offs required a decision

Use it as a recap, not as a requirement.


General tips that help more than you think

→ Lead with outcomes, not tasks
→ Name trade-offs instead of hiding them
→ Ask explicitly for decisions or alignment
→ Follow up with a short written summary

Behind the Scenes

My new role requires me to speak more German especially with the users of my product.

Most of them are in Austria, Germany, and Switzerland.

Understanding users is already a core PM skill.
Doing it in a language you’re not fully comfortable with is a whole different challenge.

Some days my brain is juggling:
→ the product problem
→ the language at the same time

It’s intense. And surprisingly exhausting.

If you’ve worked in a second language before, you probably know the feeling.
Any tips? I’d love to hear what helped you.

What do you think?

Do 1:1s with leadership feel clearer now?

Hit reply and tell me:
→ what stresses you most about them
→ or what kind of leadership conversations you’d like help preparing for next

Talk to you next Tuesday,
Maria

Frankfurt am Main, 60311, Germany
Unsubscribe · Preferences

Maria Korteleva

Hi, I’m Maria. For the past 7 years, I’ve been building internal products across FMCG and tech companies.Now, I share everything I’ve learned to help junior PMs master delivery from technical skills to stakeholder communication. Join 80+ Internal PMs who get weekly insights from the Build Internal Products newsletter.

Read more from Maria Korteleva

Hi Reader, Today I want to give you an unfiltered look at what a week as an internal PM actually looks like. Not the LinkedIn version. The real one. Spoiler: I updated servers, got humbled by engineering, and built something I'm proud of. All in one week. Today in 10 minutes you will: See what a real internal PM week looks like (calendar and all) Learn how I protect focus in a meeting-heavy environment See what surprised me and what I'm actually proud of New product, new surprise Last...

Hi Reader, today I am going to share a secret with you on how to stop being the human FAQ for your product. You can set it up in 30 minutes. And it will save you hours. The secret? An AI agent that answers your users before they ping you. Today in 10 minutes you will: Learn what documentation AI agents actually do See the 5 most common enterprise tools and their AI options Follow a step-by-step overview of how I built one Get a ready-to-use prompt to build your own Read the 5 lessons I...

Hi Reader, If you’re constantly getting incidents and tickets from users…and your operations team is stuck reproducing issues without always finding the root cause… You might need to invest in monitoring and observability for your product. And if that sentence already makes you slightly uncomfortable, this newsletter is for you. Today in 10 minutes you will: Learn why monitoring is a product responsibility, not just an ops task Understand the difference between incidents, problems,...