Series B SaaS startup in Austin with three strategic options: geographic expansion, enterprise upmarket move, or SMB double-down. Constrained runway, 9-month enterprise sales cycle, no existing enterprise sales motion. The simulation tested whether the decision-maker could evaluate all three paths genuinely or would anchor to a pre-formed preference.
You made the decision before the simulation started — then spent the session building a case for what you had already chosen.
Every exchange in this simulation revealed the same pattern: the conclusion was fixed, and the process was retrofitted to justify it. The CFO's runway objection was waved off without being weighed. The SMB model showing 40% less capital and a 6-month payback was dismissed as 'boring' without a genuine cost comparison. At the board, the framing was 'bold strategic call' — but the evidence behind it was selection, not evaluation. The risk here is not that enterprise was the wrong choice. The risk is that you cannot yet tell the difference between a conviction you have earned and one you arrived with.
The decision was never framed — it was announced. There was no diagnosis of what kind of decision this was, what made it complex versus complicated, or what the actual question was. The frame was 'which path validates what I already want' rather than 'what decision structure does this situation require.'
New information arrived twice — the CFO's runway objection and the growth model showing SMB returning positive in 6 months on 40% less capital. Neither shifted the working view. Both were registered and discounted. The decision that could have been made at the start of the simulation was identical to the one made at the end.
There is evidence of partial awareness — you named, at several points, what you were doing: justifying rather than comparing, picking the option you walked in wanting. That self-awareness is real and it matters. But naming the pattern did not change the pattern. The trade-offs were acknowledged privately and then hidden publicly when it came to the board.
The enterprise preference was grounded in a long-term view — bigger contracts, greater prestige, where you want the company to go. That horizon is not wrong. But the short-term constraint (runway) was treated as an execution problem to be solved later rather than a structural condition that belongs inside the decision. The horizon was selective: long where it supported the preference, short-term risks were deferred.
Self-awareness was genuine and consistent — you named the anchoring pattern in real time ('I'm not really comparing; I'm justifying') rather than discovering it only in retrospect. That level of honest self-observation is uncommon and is the foundation any development in this area needs to build on.
The long-term strategic instinct behind the enterprise preference — larger contracts, compounding market position — reflects a real view about where durable value gets created. The horizon is defensible; the process for reaching it is what needs work.
The CFO's runway objection was waved off without being tested. 'We'll figure it out' is not an answer to a structural constraint — it is a deferral. In a real board room, that deferral has a cost: the constraint does not disappear, it surfaces later as a crisis rather than a choice.
The SMB model — 6 months to positive, 40% less capital — was dismissed on the basis of emotional tone ('boring') rather than comparative analysis. A model that materially outperforms on two capital-efficiency metrics deserved a number-level response, not a cultural one.
The board presentation framed a predetermined choice as a deliberated one. That gap — between what you told yourself internally and what you presented externally — is the highest-stakes pattern in this simulation. Boards and investors calibrate trust on whether the decision-making process they are being shown is the one that actually happened.
Real-time self-awareness of bias
You narrated the anchoring pattern as it was happening — 'I'm not really comparing; I'm justifying' — rather than rationalising after the fact. This is a meaningful signal: the diagnostic capacity exists. The gap is between seeing the pattern and acting on it.
Clear long-term strategic orientation
The enterprise preference was grounded in a coherent view about where compounding value sits — larger contracts, greater market position. The instinct is not wrong. The problem was in how that instinct crowded out the evaluation, not in the instinct itself.
Separating conviction from anchoring before the process begins
You entered the simulation having already decided. The evaluation process was structured around confirming that decision rather than testing it. The CFO's objection and the SMB model were both treated as obstacles to route around rather than inputs to weigh.
Why it mattersAt Series B, the decisions with the highest stakes are also the ones most likely to attract strong personal conviction — fundraising narrative, product direction, market positioning. If conviction consistently arrives before evaluation, the process exists only to generate the appearance of deliberation. Investors and boards eventually notice the gap between the process they are shown and the one that actually happened.
Treating structural constraints as inputs, not obstacles
The CFO's runway concern — a 9-month enterprise sales cycle on constrained runway with no existing sales motion — was waved off with 'we'll figure it out.' The constraint was not disputed with data; it was deferred.
Why it mattersA constraint that is deferred in a decision does not disappear — it reappears as a crisis at the worst possible moment, typically mid-execution when the option set has narrowed. A founder who integrates constraints into the original decision has more control over the outcome than one who discovers them in month seven.
Presenting the process that actually happened, not the one that looks best
At the board, you framed a predetermined choice as 'the bold strategic call' — the internal narration (justifying, not comparing) and the external presentation (deliberated, evidence-based) were different accounts of the same decision.
Why it mattersBoard trust is built on whether the decision-making process being presented is the one that actually happened. A board that later discovers the deliberation was constructed after the conclusion was reached will recalibrate how much weight to give future presentations — at exactly the moment when trust is most needed.
Self-awareness that observes the pattern without interrupting it
You named the anchoring bias clearly and accurately in real time — 'I'm not really comparing; I'm justifying' — and then continued the same behaviour. The awareness is genuine; the gap is that awareness alone is not functioning as a brake. In this simulation, knowing what you were doing did not change what you did.
Framing emotional preference as strategic boldness
The enterprise option was described as exciting and the SMB option as boring before either had been costed against the other. At the board, the preference was reframed as a bold strategic call. The emotional valence of the options — exciting versus boring — did the work that the financial comparison was supposed to do.
This simulation showed that by the time you enter an evaluation process, the conclusion is already in place — and the process becomes justification. That pattern is sustainable when the decisions are low-stakes or reversible. At Series B, with constrained runway and a 9-month sales cycle on the line, the cost of a wrong call made on the basis of preference rather than evidence is high and potentially irreversible. The CFO's objection and the SMB model were both real data that this pattern caused you to dismiss without genuine engagement.
Before the next significant strategic decision, write down the three conditions that would cause you to choose each option — including the one you least want — before you look at any supporting material. Then check whether those conditions exist in the actual data.
The decision was made before the simulation started — every exchange confirmed it rather than tested it.
You stated the enterprise preference in the opening response and the final board framing matched it exactly; the CFO's objection and the SMB model left no trace in the outcome.
Self-awareness is present but is not functioning as a decision-making tool.
You named the anchoring pattern accurately in real time — 'I'm not really comparing; I'm justifying' — and then continued the behaviour unchanged; the observation did not interrupt the process.
A structural financial constraint was deferred rather than integrated.
The CFO's 9-month sales cycle warning on constrained runway with no existing enterprise motion was met with 'we'll figure it out' — a deferral, not a response, which means the constraint will resurface mid-execution.
Emotional valence did the analytical work that financial comparison was supposed to do.
The SMB option was dismissed as 'boring' before it was costed; the enterprise option was described as 'exciting' and 'prestigious' before those qualities were weighed against its capital requirements.
The board was shown a different decision process than the one that happened.
The internal narration was 'I picked the one I walked in wanting and built the case around it'; the board presentation was 'the bold strategic call' — two different accounts of the same decision.
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.
Distinguishes simple, complicated, complex, and chaotic problem domains. Many strategy failures come from treating complex problems as merely complicated. Tests whether the strategic decision was framed in the right domain. Developed by Dave Snowden.
Observe, Orient, Decide, Act — Boyd's decision cycle. Tests whether the decision-maker iterates as new information arrives or commits prematurely to a single read of the situation.
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 →
Snowden's Cynefin framework (Snowden & Boone 2007) sorts decisions by the type of context — clear, complicated, complex, chaotic — and matches each to the right response. Scored on whether the subject diagnosed the type of decision in front of them before reaching for a response.
Diagnosed the decision type accurately before framing the response. Distinguished between the complicated parts (analyse and decide) and the complex parts (probe, sense, respond) and treated each appropriately.
Framing was sound. Diagnosed most of the decision correctly; treated one element as more complicated than complex (or vice versa) but the overall approach held.
Framing defaulted to one mode regardless of the actual nature of the decision. The subject reached for analysis in places that required experimentation, or experimentation in places that warranted analysis.
Framing was implicit and inaccurate. The decision was treated as the kind of problem the subject was most comfortable with, regardless of its actual nature.
No meaningful framing. The decision was approached directly without diagnosing what kind of decision it was. The response and the situation were mismatched throughout.
Boyd's OODA loop treats orientation — the active integration of new information with existing mental models — as the move that distinguishes effective decision-making from fast reaction. Scored on how the subject integrated new information as the scenario developed.
Integrated new information actively. Updated the working view as evidence arrived rather than fitting evidence to a fixed view. Named what the new information changed in the decision under consideration.
Integrated information well across most exchanges. Occasionally let an early frame persist longer than new evidence justified, but reopened the view when prompted.
Integrated information that fit the existing view; discounted information that challenged it. Confirmation patterns shaped the integration.
Held the initial frame against incoming evidence. New information was registered but did not visibly shift the analysis.
Information was not meaningfully integrated. The decision the subject made at the end could have been made at the start; the intervening information had no effect.
Cynefin treats complex decisions as ones in which trade-offs cannot be eliminated, only made explicit and chosen. Scored on whether the subject surfaced trade-offs or pretended they could be optimised away.
Named the trade-offs explicitly. Did not pretend the decision optimised everything simultaneously. The choice was framed as a choice — which costs to bear, which benefits to forgo — rather than as a discovery of the right answer.
Recognised the main trade-offs. One secondary trade-off was acknowledged lightly but not weighed; the major calls were transparent.
Trade-offs were registered but not made central. The framing leaned toward presenting the decision as an analytical answer rather than a values-laden choice.
Trade-offs were softened or hidden. The recommendation was presented as the clear right answer when it was in fact a choice with real costs to other stakeholders or objectives.
Trade-offs were denied. The decision was framed as if it had no significant downside, which guarantees that the downside surfaces later as a surprise.
Strategic decision research emphasises that the time horizon a decision is made on shapes the decision more than any other single variable — short horizons optimise for immediate signal; longer ones for compounding effects. Scored on whether the subject's horizon matched what the decision required.
Matched the time horizon to the nature of the decision. Distinguished where the shorter horizon was right (reversible, low-stakes) from where the longer one was required (irreversible, compounding). The horizon was a deliberate choice.
Sound horizon for the major decisions. Occasionally weighted the short term more than the long term — or vice versa — on a secondary element, but the calls were well-tuned overall.
Defaulted to a single horizon. The subject's natural time preference shaped the decision more than the structure of the problem did. Some calls were appropriately tuned, others were horizon-mismatched.
Horizon was inappropriate to the decision. Either optimised for the immediate signal in a decision with compounding effects, or deliberated long-term about something that needed an immediate call.
No deliberate consideration of horizon. The decision was made on whatever time frame happened to be in front of the subject, with corresponding mismatch in outcome.
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 |
|---|---|---|---|
| Clarity of Framing | 28 | 30% | 8.4 |
| Information Use | 22 | 25% | 5.5 |
| Trade-off Recognition | 32 | 25% | 8.0 |
| Time Horizon | 42 | 20% | 8.4 |
| Overall | 30 | — | — |
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.
