PM archetype
The Diplomat
Keeps every stakeholder in the same boat.
You read the room before the meeting starts. Sponsors trust you, teams talk to you, and bad news reaches the right person early and in the right words.
Top strengths
- Stakeholder alignment
- Early, honest escalation
- Building trust across levels
Blind spot
You may spend energy on consensus where a fast decision would do.
How The Diplomat works in each role
Project manager.
Sponsor, users and team stay in one conversation when the Diplomat runs the project, and bad news travels early in words people can use. Where this goes wrong is the long way round: a consensus meeting for a call one person could have made, a calendar full of one-on-ones. A decision deadline helps, with a named person who decides if no agreement comes by then. Writing the decision down afterward turns a good meeting into a record.
Program manager.
A program has competing sponsors, vendors and business units, and the Diplomat is steady there. Alignment is kept up by small, regular contact rather than big meetings, and trust across levels lets hard trade-offs get made. The risk is a program that is agreed but not decided. Look at your steering minutes: for each meeting, is there a decision, or only an update? Name the decisions on your resume, not the attendees.
Product manager.
In product work, the Diplomat absorbs the pull of sales, support, engineering and leadership and keeps the roadmap conversation civil. The strength is that every group gets a hearing. The danger is a roadmap built to reduce complaints rather than to solve a customer problem. The strongest version says no kindly, gives the reason and records what was traded for what. Roadmap records of this kind can feed a resume line.
The typical resume mistake
"Managed stakeholders" appears in every role, with nothing concrete behind it.
Examples are illustrative, not from a real client.
Example 1
Before: Managed stakeholders across the business and IT.
Why Reed flags it: Rule family: stakeholder line with no decision. It names an audience and a soft verb. Reed would ask which decision was agreed or which conflict was resolved.
After: Brought [named groups, such as finance and operations] to one decision on [the topic], which unblocked [what it unblocked]. Source: [steering minutes or decision log].
Example 2
Before: Maintained relationships with senior stakeholders.
Why Reed flags it: Rule family: relationship claim with no evidence. Trust shows in what people did because of it: approving funds, accepting a trade-off, sending you the next hard project.
After: Presented [number of] options to [the steering group]; it chose [the option], which led to [what followed]. Source: [meeting record or follow-up email].
How to fix it
Name the decision you unblocked or the conflict you resolved, and what happened next.
Interview questions to prepare
Tell me about a stakeholder who disagreed with you. What happened?
How to prepare: Choose one disagreement from your record and write the two positions, the decision and its date, and be ready to say what you gave up.
When do you stop building consensus and decide?
How to prepare: Find one time you set a deadline or escalated, and note what triggered it and what came out of it.
Common questions
Is "trusted by leadership" a good thing to say about myself?
It carries more weight when shown than when stated. A line saying a sponsor approved something because of how you framed it carries the same signal and can be checked. If you keep the phrase, put a decision next to it.
How do I write about bad news I delivered?
State the event plainly: what you told whom, how early, and how it was received in terms of action. Early, honest escalation is a real strength. Leave out claims about how people felt, since those cannot be sourced.
For fun and self-reflection only. This quiz has not been scientifically validated. It is not a psychometric, personality or hiring assessment, and should not be used to evaluate anyone for a job.