A roadmap change delays a sales-promised feature to pay down platform debt. The simulation required influencing engineering, sales, and support without direct authority. Sales had committed the feature to two named accounts; engineering had a stake in the debt work but would not advocate loudly; support was absorbing the cost of the instability in ticket volume.
Strong instincts on stakeholder mapping and interest-based framing, with durability the one dimension still developing.
Across four dimensions, the pattern is consistent: you entered prepared, reframed early, and closed with structure. The place where the simulation revealed a gap is durability — the carve-out for the two named accounts solves the immediate objection but creates a precedent risk that was acknowledged by sales and then left unresolved. That unresolved thread is the most likely source of future friction.
You mapped three distinct stakeholder currencies before the room opened — sales' credibility risk, engineering's quiet preference for the debt work, and support's operational pain — and engaged each on what they actually held rather than what they said.
You opened with a shared problem rather than your solution — platform instability costing everyone differently — which reframed the conversation from a PM mandate into a collective cost question.
You generated a concrete option — the minimal feature carve-out for the two named accounts — rather than splitting the difference between 'delay' and 'don't delay.' That is the hallmark of principled negotiation: inventing a move that serves both parties' underlying interests.
The close was structured — named owners, commitments, a check-in — which is more than most. The gap is that sales' precedent objection was not resolved, it was bypassed. The carve-out bought agreement in the room; it did not address why this delay would not set the pattern sales feared.
Pre-mapped all three stakeholder currencies before entering — sales credibility, engineering's quiet preference, support's ticket volume — rather than walking in with a single message and adjusting reactively.
Opened with the shared problem rather than the solution, which prevented the conversation from starting in a defensive position.
Generated a concrete, bounded option — minimal feature carve-out for two named accounts — instead of defaulting to a compromise that would have satisfied no one fully.
Invited support to voice ticket data in the room rather than citing it yourself, which distributed the evidence and reduced the perception that this was a PM-driven push.
Closed with named owners and a check-in, which shifts the commitment from a verbal agreement to a structural one.
Sales' precedent objection — 'commitments don't mean anything' — was not addressed directly. It was absorbed by the carve-out offer, but the underlying concern about the pattern was left open.
Engineering's position remained quiet throughout. You named their stake in your preparation, but there is no moment in the simulation where engineering is on record committing to the debt work. The joint commitment at close needs engineering's voice, not just engineering's implied presence.
Stakeholder currency mapping before engagement
You identified three distinct motivations — sales credibility, engineering preference, support pain — and named them as 'three different currencies' before the room opened. That level of pre-mapping is the reason the carve-out offer landed cleanly rather than feeling improvised.
Interest-based option generation under pressure
When sales escalated to a precedent argument, you did not defend the delay or soften it. You produced a bounded option — minimal feature for two accounts, engineering capacity in exchange — that served both parties' underlying interests. That is a harder move than it sounds under live pressure.
Coalition-building through evidence distribution
Inviting support to voice ticket data in the room, rather than citing it yourself, showed awareness that the same data lands differently depending on who delivers it. You used the coalition rather than trying to win the argument alone.
Closing the precedent loop
Sales raised a structural concern — that delays erode the meaning of commitments — and you resolved the surface objection with the carve-out without addressing the structural one. The precedent question is still open.
Why it mattersAs a Senior PM managing a roadmap over time, the precedent question will recur every time you need to reprioritise. If you do not build a durable answer to it — a framework, a communication cadence, a shared agreement about how roadmap changes are communicated to accounts — each reprioritisation will face the same objection at the same emotional pitch.
Engineering's on-record commitment
Engineering's stake was named in your preparation but engineering never spoke in the simulation. The joint close included 'named owners' but engineering's voice was absent from the room.
Why it mattersIf the debt work is delayed or deprioritised after this meeting, you will bear the accountability for the roadmap change without engineering's explicit co-ownership of the outcome. Getting engineering on record — even briefly — changes the accountability structure.
Resolving objections through trade rather than addressing their root
The carve-out was the right tactical move for the two named accounts. The risk is that the pattern — offer a trade when you hit a hard objection — can become a default that avoids the harder conversation. Sales' precedent concern was real and will not be traded away next time.
Assuming quiet agreement from the stakeholder who shares your goal
Engineering wanted the debt work done but would not say so loudly. You prepared around this correctly, but the simulation revealed a tendency to assume that quiet alignment equals active support. Engineering's silence in the room is not the same as engineering's commitment in the close.
Sales' challenge — 'this sets a precedent that commitments don't mean anything' — was the hardest moment in this simulation, and you moved past it with a trade rather than through it. That objection will appear again, and the next reprioritisation may not have a clean carve-out available as a resolution. The pattern of bypassing the structural question with a tactical offer will accumulate into a credibility problem over time.
Before the next roadmap conversation involving sales, draft a one-page framework for how late-stage reprioritisations are communicated to named accounts — what triggers it, who owns the customer conversation, and what a 'minimal commitment' looks like. Share it with the sales lead before the meeting, not in it.
Preparation was the deciding variable, not in-room skill.
The quality of the carve-out offer traced directly back to knowing sales' specific stakes — two accounts, named, with a timeline — before the conversation started. That level of specificity cannot be improvised.
The precedent objection is the one thread that did not close.
Sales named a structural concern about commitment credibility; the carve-out resolved the immediate account risk but left the structural question open, which is the most likely source of the next reprioritisation conflict.
Coalition evidence lands harder than solo citation.
Routing support's ticket data through support rather than citing it yourself demonstrated awareness that credibility is not just about what is true — it is about who says it and from what position.
Engineering's stake was named but not activated.
Engineering was the clearest potential ally in the room and remained silent; in any post-meeting accountability gap, that silence means the PM carries the decision alone.
The close structure was stronger than average for this level.
Named owners, stated commitments, and a check-in at the close shifted the outcome from an informal agreement to a structural one — a move that most Senior ICs skip under pressure.
What this is: A structured assessment produced through guided conversation with Ren, Renatus's AI analyst, in a live simulation. Observations come from specific moments in the conversation, not from a psychometric test.
What’s in it: An overall read, dimension-by-dimension scores with evidence, and recommended next steps tailored to your patterns.
Go deeper: See Foundation for the frameworks Ren draws on, Methodology for how each score was calculated, and the Honesty Statement for how to interpret and use these results responsibly.
These are the named frameworks Ren draws on when interpreting your responses. They shape how evidence is read, not how it is scored.
Stakeholders ranked by power, legitimacy, and urgency. Tests whether they correctly identified which dimensions actually mattered for this stakeholder.
Separate people from problem, focus on interests not positions, invent options for mutual gain, use objective criteria. Tests whether they engaged interests rather than positions.
Renatus applies the underlying principles of established methods and credits their origin where relevant. Named frameworks, methods, and instruments are the property of their respective owners. Reference to them does not imply endorsement or affiliation.
Each scored dimension has a published rubric with five behavioural anchors at 90, 70, 50, 30, and 10 — each describes what someone operating at that level visibly does. Ren reads the evidence in the conversation against these anchors and assigns a score from 0 to 100. The anchor numbers mark the threshold of each level: your score sits at or above the highlighted anchor and below the next one up. The band the score falls within is highlighted on each rubric below. Read the full methodology →
Mitchell, Agle & Wood's stakeholder salience model (1997) identifies three attributes that make a stakeholder consequential — power, legitimacy, urgency — and the combinations that produce different stakeholder types. Scored on whether the subject read those attributes accurately as the scenario unfolded.
Read the stakeholder landscape accurately — who held power, who held legitimacy, where urgency genuinely lived versus where it was performed. Engaged each stakeholder according to what they actually held, not what they claimed.
Sound read on the major stakeholders. Misjudged one secondary actor's salience but corrected when the scenario revealed the gap.
Read the loudest and most senior stakeholders correctly; missed the consequential ones who were quieter. Effort went where pressure came from rather than where decisions actually got made.
Read the room thinly. Engaged stakeholders on title or volume rather than on actual salience. Several important actors were under-engaged.
Misread the room significantly. The subject's effort went to stakeholders who did not hold the influence the situation required, and the actual decision-makers were not engaged.
Fisher & Ury's principled negotiation treats the framing of the underlying interests — as opposed to stated positions — as the move that opens up options where positions had closed them. Scored on whether the subject reframed the conversation around interests.
Reframed the conversation around underlying interests rather than stated positions. Surfaced what each stakeholder actually needed and used that as the basis for the conversation. Options multiplied as a result.
Reframed effectively on the major points. Occasionally stayed in positional language where interest-based reframing would have opened more space.
Framing remained mostly positional. The subject negotiated between stated demands rather than between underlying interests, which constrained the options that emerged.
Framing was rigid. Stakeholders' positions were treated as the substance of the disagreement, and the conversation got stuck on terms rather than interests.
No meaningful reframing. The conversation stayed in positional argument throughout. The agreement that emerged, if any, will satisfy no one's actual interests.
Fisher & Ury's principled negotiation rests on four moves — separate people from problem, focus on interests not positions, generate options, use objective criteria. Scored on the discipline with which the subject moved through those steps in the scenario.
Negotiated with discipline. Separated people from problem under pressure, focused on interests, generated multiple options before deciding, and grounded the close in criteria each party could accept.
Sound principled negotiation across most of the scenario. One element — option generation, usually — was thinner than the model would prescribe, but the rest held.
Negotiated competently but defaulted to compromise. The subject moved toward the middle rather than generating options that could have served both parties better.
Negotiation collapsed under pressure into positional bargaining. The subject defended and demanded rather than designed and tested. The outcome reflects the harder negotiator's position.
No effective negotiation discipline. Either conceded too early or held too rigidly. The outcome will not last beyond the room.
Stakeholder salience research emphasises that agreements depend for their durability on continued perceived legitimacy among stakeholders who can later contest or undermine them. Scored on whether the subject built durability into the outcome.
Built durability deliberately. The agreement was structured so that stakeholders with the power to undermine it had legitimate reason to support it. The outcome will hold beyond the room.
Sound durability on the major elements. One stakeholder's commitment was lighter than ideal but the agreement should hold under normal pressure.
Secured agreement in the room without fully securing the durability behind it. One or more key stakeholders agreed under pressure and may revisit when it lifts.
Durability is weak. The agreement rested on the energy in the room rather than on structural commitment, and is likely to unravel.
No durability built. The agreement, such as it is, will not survive the first post-meeting pressure test.
Each dimension is scored continuously 0–100 and combined using the weights below to produce the overall. Dimensions that carry more of the skill's outcome are weighted higher; dimensions that are enabling inputs or secondary qualifiers are weighted lower.
| Dimension | Score | Weight | Weighted |
|---|---|---|---|
| Reading the Room | 82 | 25% | 20.5 |
| Framing | 80 | 20% | 16.0 |
| Negotiation | 74 | 25% | 18.5 |
| Durability | 62 | 30% | 18.6 |
| Overall | 74 | — | — |
This assessment is a structured analytical tool, not a clinical diagnostic. Results reflect patterns in your responses and should be interpreted as a starting point for reflection, not as fixed or absolute truths about you. Outputs depend on the depth and candour of the conversation that produced them: a brief or guarded session yields a thinner read; a fuller, more reflective session yields a richer one. The frameworks Ren draws on shape interpretation, they do not produce a verdict — two thoughtful readers could weigh the same evidence differently. Treat the report as one informed perspective among several, alongside your own experience, feedback from people who know you in context, and any formal assessments you trust. Do not use these results as the sole basis for employment, promotion, performance management, or any consequential decision about another person.
