The PM role
How product managers lead without authority
In this lesson5 sections
An unofficial lesson drawing on the methods in the The Product Manager Role chapter of Cracking the PM Interview by Gayle Laakmann McDowell and Jackie Bavaro (2014). PracHub is not affiliated with the authors or publisher. Buy the book
Nobody on a product team reports to the product manager, so interviewers want to see how you get engineers, designers and other teams to back a plan they could ignore. That skill comes up in behavioral rounds and in follow-ups to almost any case, often without the word "influence" being said.
One invented situation runs through this lesson. You're the PM for a scheduling app that heating, cooling and plumbing companies use to send technicians to jobs. Marco, a sales lead, has told a regional HVAC company with 140 technicians that offline mode will be ready in three weeks. Their technicians lose signal in basements and on rural sites, and the contract comes up for renewal next quarter. Priya and Sam, the two mobile engineers who would build it, estimate six weeks.
Marco and the three-week promise
Picture opening stand-up with "Marco promised three weeks, so offline ships in three weeks." Priya and Sam might nod, but for six weeks they'll judge whether the sync code is safe to trust with a technician's notes, and an order buys the nod, not the judgment. Often you get a quiet yes to a date nobody believes, or an argument in front of the team, and goodwill you'll need later is gone.
The order has nothing behind it, either. Priya and Sam report to an engineering manager, who sets their week, writes their reviews and will back their estimate over your date. Marco reports to the head of sales. You can't take anyone off on-call or tell Marco what to promise. People like to call the PM the CEO of a product, and this is where the comparison breaks: nobody in this story works for you.
What you can do is make your plan the one people want to follow. It starts with a result everyone can picture: a technician in a basement with no bars who can still pull up the gate code and the boiler's service history. Marco can take that to the customer, and Priya and Sam can build toward it. The plan holds because it gets Marco his signed renewal and gets Priya and Sam sync code that won't page them at night over lost data.
When Marco is annoyed that you won't confirm his date:
"If we squeeze full offline into three weeks, the risk is a sync bug that loses a technician's notes, and that would hurt the renewal more than a later date. What I think we can get by week three is every job's details readable offline. Can we take that to the customer together on Thursday?"
You started from his goal and gave him something he can sell. What you never do is agree to his date behind the engineers' backs, or tell the customer full offline "should be doable" in three weeks when the people building it said six. Once engineers learn that you make the promises and they're expected to keep them, their estimates get padded and your plans meet suspicion.
To practise this step, try Influencing Without Authority: Winning Commitment From a Partner Team, then Turning a Resistant Colleague Into a Trusted Ally: Influence Without Authority. Use your own story for each, sketched in five lines before you say it aloud.
Influencing Without Authority: Winning Commitment From a Partner Team
A behavioral product manager interview question about influencing a team outside your reporting line.
Turning a Resistant Colleague Into a Trusted Ally: Influence Without Authority
A behavioral question asking a product manager to describe turning a colleague who opposed them into a trusted ally.
The dispatchers and the crews
Last spring the same HVAC company asked for a CSV export of the weekly schedule, about a week of work. Instead, you spent a morning beside two of their dispatchers. Every Friday they checked each technician's booked jobs against finish times texted in from site, then typed the hours worked into payroll by hand: about three hours, with an overtime mistake every few weeks. An export would list booked slots, not hours worked, so most lines would still need fixing. What they wanted was correct paychecks without the Friday re-keying, so the team added clock-in and clock-out to each job and sent those hours straight to payroll.
A request tells you where it hurts, rarely what to build: it's the customer's guess at a solution, made without knowing what your product could do. So ask what the person will do with the thing they asked for, and what happens today without it. Then watch them do the task, because what people do and what they describe often differ.
You did the same on offline mode before writing the spec. A day with one crew showed that in the basement they needed to read: the address, the gate code, the equipment's service history, the checklist. They typed their notes later in the van, once they had signal. Most of the need was reading, which is what makes a week-three version possible.
To practise this step, try Amazon PM behavioral: how you uncover real customer needs, shown through an example with a story of your own.
The dispatchers come back when full two-way sync raises a hard question: what happens when a technician edits a job offline and a dispatcher edits the same job before the phone reconnects? Marco, Priya and Sam will be in the meeting. The customer's dispatchers won't, and neither will your support team, who'll take the calls if a technician's notes go missing. Their side reaches the room only if you carry it in.
Before the meeting, you pull last month's logs, which show both sides touching the same job within an hour about 3 times per 100 jobs, and call two of the customer's dispatchers to ask what they change and why. Then you settle on a rule for deciding: whoever is closest to the facts wins. The technician's notes, parts used and photos stand, because they were on site. The dispatcher owns time and assignment. When both change the same field, the app keeps both versions and flags the job.
Your one-page proposal has three options. "Latest edit wins" is simplest, but a technician's notes can vanish without anyone knowing. "Dispatch always wins" keeps the office in control and throws away what happened on site. Splitting by field follows who knows what, and Priya estimates it at four extra days. You recommend the split and say plainly what it costs. A write-up of what each person said adds nothing the room didn't have. A recommendation gives it something to push against, and the push often improves it.
Leaving the meeting isn't the finish. Say Sam suspects field-by-field merging hides more risk than four days, and the room breaks up undecided. Find out what he doubts and bring back what answers it, such as last month's conflicting edits replayed under each rule to show whose notes each would have lost. The recommendation has done its job once the split is in the build.
Priya, Sam and the week-three build
Your recommendation, to Marco and the engineering manager:
"I recommend read-only offline for all 140 technicians at the end of week three, and full two-way sync in week seven. I'd also take Priya and Sam off on-call until then, which covers the four days the field-by-field conflict rule adds. The cost is a week's delay on full sync, and technicians still type their notes once they're back in signal."
The read-only part is the engineers' plan, not your guess. It came from asking Priya and Sam what's inside the six weeks and what a smaller version would take. Storing jobs on the phone is the first piece of full sync anyway. They put it at two weeks, plus a week of testing on the customer's older phones, and shipping it separately adds about a week to the full version. Questioning an estimate this way is yours to do; overruling it isn't.
Set that against the renewal. On the full plan, the customer gets full offline in week six and nothing in week three, with the contract up next quarter and Marco's three weeks already promised. Read-only first makes every job readable offline by the end of week three, which covers what the crew needed in the basement. The customer pays for it in notes that still need signal until week seven. Taking Priya and Sam off on-call is the engineering manager's call, so it goes in as an ask. It buys days, not weeks, which is why it pays for the conflict rule and not for Marco's date.
Priya and Sam also choose how jobs are stored on the phone. What you need from them is the effect of that choice, such as how many days of jobs fit on an older phone. Which storage library delivers it is theirs to pick.
To practise who owns what when work gets sized, answer Making an Engineering Team's Work Estimates Reliable as a Walmart Product Manager, then mark which parts of your answer you claimed and which you left to the engineers.
Three days after you send the offline spec, you open the first build. The app stores today's jobs only. Your spec said "cache the technician's jobs", and Sam read it the obvious way. But this customer's crews get their first job the night before and drive out at 6am through areas with no signal.
That gap is yours, and closing it takes more than a better sentence. Rewrite the line, then spend ten minutes at a whiteboard walking Sam through one technician's day. Next, check the build the way a technician would meet it: put it on your phone, drive into an underground car park and use it there. The drive shows what the happy path skips. Dispatch reassigns a job while the technician is offline. A technician spends two days out of signal on a rural job, and the stored jobs go stale. The login session expires while the phone is offline. You're finished when the build does what the technician needs, not when the spec goes out.
Nor does code close every part of the gap. If no one explains "read-only" to 140 technicians, the first they'll hear of it is a greyed-out notes field in a basement, then a call to support from a crawl space. Sales has moved on to the next deal and the customer success manager is stretched across 60 accounts, so that gap is yours too: you write a one-page guide and join the customer's Monday crew meeting by video.
The login case isn't your team's to fix. Login belongs to the identity team, whose roadmap is full, and a longer offline session is a security call for them. Take it to their PM in week one, written up, not in week three as an emergency.
To practise who settles what with engineers, try PM Collaboration with Engineering: Decision Rights, Trade-offs and Disagreements.
Yara and the offline indicator
Yara, the designer, owns the indicator that tells a technician the app is offline. Her first version is a small crossed-out cloud in the top bar. Your worry is the first case from the car park: a technician opens a job that dispatch changed while they were out of signal, and doesn't notice they're reading an old copy. Redrawing her screen would be quicker, and it would also tell Yara that her job is to trace your sketches. So you bring the worry, not a mock-up, to design review:
"My concern is a job that dispatch moved while the technician was offline. When I watched technicians on site, they looked at the phone for two or three seconds at a time, often with gloves on. Could we test whether they'd catch the icon in that time?"
Yara might make the icon bigger, add a "last updated 3 hours ago" line to every job, or run a quick test and show you it's fine. How the indicator looks and how hard it is to miss are her call. If she weighs your point and keeps the icon, back her in front of the team.
What you carried in was a fact about the technician and a question, not a drawing. How much of a feature's behavior the designer settles, rather than the PM, differs by team (see what a product manager does), but how a screen looks and feels to use is the designer's almost everywhere.
AI tools now let a PM build a clickable offline screen in an afternoon. Shown as a question ("could it work something like this?"), that helps. Handed over as the answer, it takes the decision from the people who own it.
To practise this step, try Behavioral: How You Partner With Designers From Problem Framing to Launch. For an open disagreement, add PM Behavioral: Working Through Conflict With an Engineer, Designer or Peer.
Behavioral: How You Partner With Designers From Problem Framing to Launch
A behavioral product manager interview question about how the candidate partners with design teams from problem framing through launch.
PM Behavioral: Working Through Conflict With an Engineer, Designer or Peer
A behavioral product manager question about how you resolve a disagreement with a colleague such as an engineer, designer or fellow PM.
How behavioral rounds test this
Interviewers rarely ask "how do you lead without authority?" in those words. They ask about a time you needed a team that didn't report to you, a disagreement with an engineer or designer, a date you couldn't hit, or a customer request you didn't build as asked.
When you practise, listen to your own verbs. "I redrew the designer's screen" takes a call that was hers; "I showed her that technicians glance at the phone for two or three seconds" gives her what she needs to make it. "I wrote up what everyone said" leaves the room where it started; "I recommended splitting by field and said what it cost" gives it something to push against.
For the shape of a story, see the STAR method. Leadership and influence, stakeholder management and conflict and difficult situations go deeper.
For a date story of your own, take PM behavioral: reducing launch scope to hit a date and handling what was deferred and tell it aloud in under two minutes.