Stop 08 · Technical Fluency for PMsTopics · 6/11

Working Effectively With Engineers

In short

Engineers don't need a boss for the code. They need a partner who brings clear problems, shares context, and protects their focus time.

Bringing a clear problem and context, being open to technical trade-offs you didn't anticipate, and protecting engineering time from constant interruption — trust is built incrementally, not assumed.

The purple blob points to a sore arm while a friendly doctor listens with a stethoscope.

Think of it like this

Visiting the doctor

You tell the doctor "my arm hurts when I lift it, since Tuesday". You don't walk in demanding a specific tablet. The doctor knows more about medicine. Describe the symptoms well, then trust their expertise.

Watch it happen

Bringing a problem, not a solution

Engineer

search feels slow

1/5PM shares the problem with evidence: 30% of searches take over 3 seconds.

The big ideas

What you need to know

Share the why

Context on users and goals lets engineers suggest better, cheaper solutions.

Protect focus time

Batch questions and avoid pinging every hour. Deep work needs long blocks.

Involve them early

Bring engineers into discovery. They spot feasibility problems before they're expensive.

Credit generously

Celebrate the team's work in public. Take the blame yourself when plans go wrong.

Save yourself the pain

Common mistakes

Oops

Writing "add a Redis cache" in the ticket.

Do this instead

Write the problem and the target. Let engineers choose the approach.

Oops

Changing priorities mid-sprint without explanation.

Do this instead

If you must change, explain why and agree what drops out.

Your mission

Rewrite three tickets

~20 min

Quick check

What's the most useful thing a PM can give engineers at the start of a feature?

Go deeper

1Ask an engineer what makes a PM easy vs difficult to work with, and take notes.
2Practice presenting a problem without prescribing the technical solution.
3Learn to say 'I don't know, let's find out together' instead of guessing on technical questions.