I stepped into a department head role at a UK manufacturing firm in Birmingham, inheriting a 40-person team left cynical by two failed reorgs, with two of my best engineers — Marcus and Priya — already considering offers elsewhere. On my first all-hands morning, Marcus emailed me at midnight to say he had an offer on the table, then revealed in our conversation that Priya was close to moving too. Two hours after I told forty people I keep my promises, my director Sandra called with a cost-cutting target that put Marcus's name on an HR framework for potential reduction.
You lead with integrity under compounding pressure — but your upward influence needs the same rigour you apply downward.
Across five decision points, every instinct was tested against a harder version of itself — and held. The Marcus confidentiality firewall, the Dean response, the Sandra pushback — each showed a leader who thinks about second-order effects before acting. The gap that emerged is narrower but real: you build trust downward with precision and care, but when pressure came from above, the plan was to argue well rather than to shape the outcome before it arrived.
Your decisions were grounded in principle and tested against consequences. You distinguished between what you knew privately and what you could defend publicly — and held that line even when it made the cost problem harder.
The Marcus framework decision: they explicitly firewalled the confidential disclosure, argued his case on merits anyone could verify, and then accepted that the saving had to come from somewhere else. That's unusually rigorous under pressure.
Their decisions were grounded in principle and tested against consequences. They distinguished between what they knew privately and what they could defend publicly — and held that line even when it made the cost problem harder.
You calibrated every communication to its audience and moment. The Dean response was particularly precise — you offered accountability with a deadline rather than reassurance, which is the only thing that audience could have heard.
Dean's challenge was met with: 'You shouldn't believe me yet' — a reframe that gave a sceptical audience a concrete test rather than asking them to extend trust they had no reason to give.
They calibrated every communication to its audience and moment. The Dean response was particularly precise — they offered accountability with a deadline rather than reassurance, which is the only thing that audience could have heard.
You consistently read individual situations as systemic signals. Marcus and Priya weren't two retention problems — you named them as one credibility problem. The all-hands wasn't a speech — it was evidence. This is systems thinking applied to people, not just process.
After Marcus's disclosure about Priya, they reframed the all-hands as 'the first piece of evidence both of them get about whether to believe me' — and used that to raise the bar on what was committed to in the room.
They consistently read individual situations as systemic signals. Marcus and Priya weren't two retention problems — they named them as one credibility problem. The all-hands wasn't a speech — it was evidence. This is systems thinking applied to people, not just process.
Under direct downward pressure, your thinking sharpened. Under upward pressure from Sandra, the response was sound but reactive — you pushed back well, bought time, and framed the problem correctly. What's less visible is how you'd get ahead of that kind of pressure before it arrives.
Sandra's call came two hours after the all-hands. The response was to argue for room and timing — the right move. The question it leaves open: at what point would this leader flag the tension upward before being handed a framework to execute?
Under direct downward pressure, their thinking sharpened. Under upward pressure from Sandra, the response was sound but reactive — they pushed back well, bought time, and framed the problem correctly. What's less visible is how they would get ahead of that kind of pressure before it arrives.
Prioritised the human signal over the logistics — calling Marcus before touching the all-hands preparation, because a midnight email from a flight-risk engineer is a request for a response, not an FYI.
Handled Marcus's slip about Priya without acting on it — named the betrayal risk immediately and explicitly protected both Marcus's trust and Priya's dignity, choosing to set up a legitimate conversation instead.
Turned Dean's challenge into a credibility mechanism rather than a defensive moment — replacing 'trust me' with a deadline and a test, which is the structural move, not the rhetorical one.
Firewalled the confidential disclosure cleanly when the cost framework arrived — argued Marcus's case on merits anyone could verify, not on private information, even when using that information might have simplified the argument.
Named the second-order cost of losing Marcus in business terms — framing the exception argument around replacement and disruption cost rather than sentiment, which is the justification that survives upward scrutiny.
The tension between the all-hands promise and the cost target was knowable before Sandra called — and it hadn't been surfaced upward first, which meant the response to Sandra was reactive rather than prepared.
The framework for how Yusuf and others would be assessed wasn't named — 'gets a genuine look' is a commitment without a visible process, and the room watching Dean ask his question is also watching how decisions about who goes get made.
The reasoning and planning throughout the simulation was largely self-contained — carefully worked through, but not tested with or shared by anyone until the moment required a response.
Integrity under competing pressures
You held the Marcus confidentiality firewall even when it made the cost problem harder to solve. You didn't use private information as a shield or a weapon — you set it aside and argued on grounds you could defend to anyone.
Trust architecture
Every interaction — Marcus, the all-hands, Priya's planned conversation — was designed to build a specific kind of trust. Not warmth. Credibility. You consistently chose mechanisms over promises.
Precision under public scrutiny
The Dean response was not improvised warmth — it was a precise reframe that gave a sceptical audience a concrete test. That kind of clarity under public scrutiny is hard to manufacture.
Consequential thinking
You repeatedly traced decisions to their second-order effects before acting. The Priya decision — don't act on stolen information — was driven entirely by what the act would signal, not just what it would do.
Proactive upward influence
When Sandra called, the move was to push back, buy time, and build a credible plan — sound. But the tension between the all-hands promise and the cost target was knowable before Sandra called, and it hadn't been surfaced upward first.
Why it mattersAt department head level, the credibility you build downward is only as durable as the room you've created upward. If you're consistently reacting to pressure from above rather than shaping it early, you'll spend your leadership capital defending positions rather than building them.
Explicit criteria for hard trade-offs
Yusuf 'gets a genuine look' and the saving has to come from somewhere — but the framework for how that assessment would be made wasn't named. The rigour applied to Marcus wasn't yet applied to the harder, less sympathetic decisions.
Why it mattersThe people watching Dean ask his question are also watching how you decide who goes. If the process isn't visible and consistent, the outcome — however defensible — looks like the last two reorgs.
The plan stays inside your head longer than it should
Every decision in this simulation was well-reasoned and well-executed — but reasoned and executed largely alone. Marcus, Sandra, the all-hands — each person's needs were thought through carefully, but that thinking wasn't shared or tested with anyone until the moment required a response.
The Sandra call revealed a pattern: the tension between the all-hands commitment and the cost target was visible before Sandra called, but it hadn't been surfaced upward. The response was sound — but it was a defence, not a move you'd planned. At this leadership level, consistently reacting to pressure from above means you're always spending credibility rather than building it.
Before any significant downward commitment, name the upward risk it creates and decide consciously whether to surface it first. This week: identify one tension between what you've promised the team and what you know is coming from above — and raise it with Sandra before she raises it with you.
Integrity holds under compounding pressure — including when protecting it is costly.
The Marcus firewall decision, made under time pressure with a cost target arriving simultaneously, chose defensibility over convenience — the behaviour that makes trust durable.
Credibility mechanisms beat credibility claims — and you know the difference.
The Dean response replaced 'trust me' with 'hold me to this date' — a structural move, not a rhetorical one, and the foundation of everything else in this simulation.
Upward relationships are the next frontier.
The gap between downward precision and upward reactivity is the single highest-leverage development area at this stage of your leadership.
You think in systems — apply it to the organisation above you, not just the team below.
Marcus and Priya were mapped as one credibility problem. The same thinking applied to Sandra and the cost target would have surfaced the tension before it became a crisis.
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.
Applies Hersey and Blanchard's situational leadership model by examining whether direction and support are adjusted to the other person's demonstrated readiness for the task.
Distinguishes between technical problems (known solutions) and adaptive challenges (require learning and behaviour change). The simulation tests whether the leader diagnoses the type of challenge correctly and responds accordingly. Developed by Heifetz and Linsky at Harvard Kennedy School.
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 →
Heifetz & Linsky's adaptive leadership distinction between technical problems (apply existing expertise) and adaptive challenges (require people to change assumptions or behaviour). Scored on whether the subject diagnosed the scenario correctly before acting, and whether their decisions matched the actual nature of the challenge.
Diagnosed the adaptive element early — named what the real problem was beneath the surface symptom — and made decisions that put the work back with the people who had to live with the change. Took responsibility for the call without absorbing the work that wasn't theirs to do.
Made sound calls on the technical pieces and read most of the adaptive signal correctly. Occasionally reached for a technical fix on a problem that needed people to change first, but corrected the approach when the scenario pushed back.
Decided cleanly where the problem was familiar. When the scenario was genuinely ambiguous, treated the adaptive challenge as if it were a technical one — looked for the right answer rather than the right process for finding one with the people involved.
Decisions were reactive to the most recent piece of information rather than to a diagnosis of the whole situation. The work that belonged to others was repeatedly absorbed by the subject; the work that needed a hard call was deferred.
Avoided the adaptive call entirely — reframed the challenge as somebody else's, or as a technical problem that more data would solve. The decisions made did not move the situation forward and in places made it harder for the next person to act.
Hersey & Blanchard's situational leadership model: effective leaders shift between directing, coaching, supporting, and delegating based on the readiness and capability of the people in front of them. Scored on whether the subject matched style to the person and the moment, or defaulted to a single register regardless of who was on the other side.
Read each character in the scenario distinctly — the new manager who needed direction, the senior operator who needed to be trusted — and adjusted register accordingly. Held authority and warmth in the same exchange. The hard message was delivered without being softened past the point of clarity.
Adjusted style across most of the people in the scenario. Occasionally over-directed someone who would have responded to coaching, or supported someone who needed clear instruction — but the miss was small and recoverable in the next exchange.
Communicated clearly in their default register — usually either directive or supportive — and applied it consistently regardless of who they were speaking to. People who matched that style got what they needed; people who didn't were left translating.
Single-register throughout. Either pushed direction onto people who needed room to think, or stayed in coaching mode with people who needed a decision. The hard message, when it came, was either softened past usefulness or delivered with more force than the moment required.
Communication was opaque, mismatched, or absent at the moments it mattered most. Direction wasn't given where it was needed; the hard call wasn't named. The people in the scenario were left to infer the subject's position from what they didn't say.
Heifetz & Linsky's concept of "getting on the balcony" — stepping back from the action to see the whole system, the patterns, and the second-order effects, then returning to the dance floor to act. Scored on whether the subject held both views at once or got pulled fully into the immediate move.
Held the immediate decision and the longer system in view at the same time. Named the second-order effects of the obvious move and weighed them explicitly. Connected the scenario to a pattern the organisation would face again, and chose for the pattern, not just the moment.
Most decisions were traceable to a broader frame the subject was holding. Occasionally narrowed to the tactical question in front of them and lost the balcony view for an exchange or two — but returned to it when the scenario reopened the wider question.
Strategic on familiar ground; tactical when the scenario moved into less familiar terrain. The horizon shortened as the pressure rose. Decisions were defensible in isolation but the thread connecting them was not always visible.
Operated almost entirely on the dance floor. Each decision was made against the most recent input rather than against a held view of where the situation was heading. Second-order effects surfaced only after the scenario flagged them.
No visible balcony view. The strategic question embedded in the scenario was either missed or treated as background noise. Decisions were made one at a time without reference to where they were leading the organisation.
Heifetz & Linsky's idea that adaptive leadership requires holding people in a productive zone of disequilibrium — high enough that the work happens, low enough that the system doesn't break. Scored on how the subject regulated their own state and the temperature in the room as the scenario escalated.
Held steady as the scenario escalated. Regulated their own state visibly enough that it lowered the temperature for the people around them, but not so much that the urgency drained away. The version of the leader in the hardest moment was recognisably the same as the one in the calm.
Mostly steady. Narrowed slightly as the pressure rose — took on more of the work themselves, briefed less — but the shift was small and self-corrected within the scenario. The team in the simulation could still rely on them.
Pressure exposed a default. The subject either absorbed the work that wasn't theirs (lowering the temperature too far, letting others off the hook) or tightened control (raising it past the productive zone). The pattern was visible to the scenario but not always to the subject.
The version of the leader the scenario got under pressure was materially different from the one in the opening — sharper, narrower, harder to predict. Recovery within the scenario was slow and incomplete.
Pressure produced volatility, withdrawal, or both. The temperature in the room moved with the subject's state rather than against it. The scenario absorbed the cost of the subject's regulation rather than the other way around.
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 |
|---|---|---|---|
| Decision Quality | 82 | 30% | 24.6 |
| Communication | 83 | 20% | 16.6 |
| Strategic Thinking | 79 | 25% | 19.8 |
| Pressure Response | 66 | 25% | 16.5 |
| Overall | 77 | — | — |
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.
