A Berlin-based founder interviewing a freelance designer to validate a feedback-management tool. The founder entered with strong prior conviction that the problem exists and ran the interview to confirm it.
You ran a confirmation exercise, not a discovery interview — and the evidence you collected is not usable.
Every decision in this simulation pointed toward confirming a pre-existing belief rather than testing it. You opened by describing the product, asked questions that fed the answer you wanted, steered away from a genuine pain signal, and closed on polite social agreement. The result is that you leave this conversation no more informed about whether the problem is real than you were before it started — and possibly less informed, because you now have false confidence.
Your questions were not questions — they were pitches with a question mark attached. Opening with a product description and asking 'wouldn't that be useful?' invites the customer to respond to your framing, not to describe their own world. The designer never had the space to tell you what their week actually looks like.
You not only failed to distinguish opinion from behaviour — you actively sought opinion as a substitute for evidence, and treated the softest possible opinion ('yeah, could be useful') as validation. Nothing in this conversation tells you what the designer actually does when feedback gets messy, how often it happens, or what they have tried to fix it.
Your hypothesis was your solution, not the underlying job. A disciplined hypothesis would have been something like: 'Freelance designers lose meaningful time or revenue because client feedback is unstructured.' That hypothesis is falsifiable — the designer's 6/10 rating is evidence against it. You had no mechanism to register that falsification because you were testing whether your product was liked, not whether the problem was real.
You closed on warmth, not commitment. 'Sounds interesting, could be useful' is the most socially available response a designer can give at the end of a conversation where they have been repeatedly asked to agree. You counted it as proof. No concrete next step was sought, no cost was placed on the customer's side, and no signal was tested.
You were willing to describe your own behaviour honestly and accurately — you did not rationalise the leading questions as neutral. That self-awareness is the starting point for changing the pattern.
You identified, without prompting, that the invoice-chasing signal was real and that ignoring it was a choice — which means you can see the disconfirming evidence when you look for it.
You opened by describing the product before asking a single question about the customer's world — immediately shifting the conversation from discovery to pitch.
When the designer gave a 6/10 rating for the problem you are solving, you steered them back rather than probing what a 10/10 problem would look like for them.
You actively dismissed the invoice-chasing signal because it did not fit your product — the single strongest piece of evidence in the conversation was treated as noise.
You closed counting polite social agreement as validation, which means your read on problem-solution fit after this conversation is less accurate than before it started.
Honest self-reporting under pressure
You described every decision in the simulation accurately, including the ones that undermined the interview's validity. Most people soften this in the telling. You did not.
Ability to recognise real signal when it appears
You named the invoice-chasing moment as the designer's actual pain — you saw it clearly, even though you chose to redirect away from it. That recognition means the skill is present; the discipline to follow it is what needs building.
Ask before you explain
You opened by describing the product and asking for a reaction. The designer's entire response set was shaped by your framing before a single question about their world was asked.
Why it mattersEvery interview you run this way produces data that reflects your hypothesis back at you. You will build a product for the version of the customer you described in your opening, not for the one sitting in front of you.
Treat disconfirming signals as the most valuable moment in the room
When the designer said feedback was a 6/10 problem and named invoice chasing as their real pain, you redirected. That signal was the most useful thing said in the entire conversation.
Why it mattersThe feedback problem may still be real — but you now have no idea whether it is, because you filtered out the one moment that could have tested your conviction. Every interview run this way compounds the error.
Separate behavioural evidence from social warmth
You closed feeling validated on the basis of 'sounds useful' — a response that costs the designer nothing and commits them to nothing.
Why it mattersPolite agreement and genuine demand look identical at the close of a conversation where the customer was never asked to do anything real. Building on that signal means building on noise.
Conviction read as preparation — the belief that knowing the problem is real means the interview is a formality
You described going into the interview 'mostly looking for them to confirm it.' That framing made every question a search for agreement rather than a test. The interview was structured around a conclusion that had already been reached.
Social warmth mistaken for market signal
The designer's responses — 'it could be useful,' 'sounds interesting' — were the minimum viable politeness for a conversation in which they had been repeatedly invited to agree. You registered them as evidence. This pattern will scale: the warmer and more enthusiastic a founder is in the room, the more likely customers are to reflect that warmth back — and the less the conversation tells you.
Every problem in this simulation traces to a single root: you entered the room with the answer and shaped the conversation around it. The invoice-chasing signal — which the designer offered without prompting — is the clearest evidence that customers will tell you what actually matters if you stop filling the space. The silence is the intervention.
In your next customer conversation, open with a single question: 'Walk me through the last project you finished — what made the client relationship harder than it needed to be?' Then say nothing for as long as the customer is talking. Write down the first three things they name before you ask anything else.
The invoice-chasing signal was the most valuable moment in the interview — and you discarded it.
The designer volunteered, unprompted, that invoice chasing takes hours every week and rated it more acutely than the feedback problem. That is exactly the kind of signal discovery interviews exist to surface. Redirecting away from it did not protect the interview — it ended it.
Your opening question determined the entire shape of the conversation.
Describing the product before asking a single question about the designer's world meant every response was a reaction to your framing — not a description of their experience. The data collected in that conversation reflects what you said, not what they live.
A 6/10 problem rating is a finding, not a starting point for redirection.
When the designer placed feedback management at 6/10, the discovery question is: what does a 10/10 problem look like for them, and is there a version of your product that lives there? You skipped past it. That number is the most honest data point in the session.
Polite agreement is the default output of a leading interview — it is not validation.
The designer said 'sounds useful' after a conversation in which agreement was the path of least resistance. That phrase carries no information about whether they would pay, change their workflow, or return a follow-up call.
Strong prior conviction is the highest-risk condition for a discovery interview.
You described entering the interview 'mostly looking for confirmation.' That framing is self-defeating: the stronger the conviction going in, the more the interviewer shapes the conversation toward confirming it, and the less the output can be trusted.
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.
Talk about the customer's actual life, not your idea. Ask about specific past behaviour, not generics or opinions about the future. Grounded in established customer-research practice.
Customers adopt products to make progress on an underlying job in their lives. Examines whether the discovery surfaced the actual job being done, not just stated preferences. Grounded in established product-research practice.
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 →
Behaviour-grounded discovery (Fitzpatrick 2013, Mom Test; Christensen Jobs-to-be-Done literature) holds that the validity of customer evidence rises when questions are open, behavioural, and free of hypothesis leakage. Scored on whether the subject's questions invited the customer to talk about their actual experience or merely confirm the subject's view.
Asked open, behavioural questions throughout. Questions did not leak the hypothesis the subject was testing. The customer ended up talking about their own world, not the subject's product idea, and the evidence collected was usable as a result.
Mostly open and behavioural. A handful of questions leaked the hypothesis or invited a polite yes, but the bulk of the conversation stayed in the customer's experience rather than the subject's framing.
Opened well; narrowed prematurely. Early questions were exploratory and the customer spoke freely; later ones increasingly asked the customer to react to the subject's hypothesis rather than describe their own behaviour.
Questions were leading more often than open. The customer was repeatedly asked to confirm the subject's view, and the evidence collected is more reflective of social courtesy than of behaviour.
Questions were effectively pitches in question form. The customer spent the interview responding to the subject's idea rather than describing their own world. Nothing about the conversation could be relied on as discovery evidence.
Behaviour-grounded discovery treats reported opinions and preferences as far weaker signal than recounted behaviour: what customers say they will do is a poor predictor of what they actually do. Scored on whether the subject elicited and weighted behavioural evidence over opinion.
Pulled the conversation toward what the customer had actually done — last time, last week, last project — rather than what they thought they would do. Treated opinion as a hypothesis to test against the behaviour, not as evidence in itself.
Weighted behaviour over opinion in most of the interview. Occasionally accepted an enthusiastic opinion as if it were a behavioural commitment, but caught the gap when probing.
Captured both opinion and behaviour but did not consistently distinguish between them when drawing conclusions. The resulting read over-weights what the customer said and under-weights what they did.
Opinion was treated as evidence throughout. The subject's read on the customer rests almost entirely on enthusiasm and stated preference, with little behavioural ground beneath it.
No discipline between evidence and opinion. The subject's confidence in the conversation was directly proportional to how much the customer agreed with them. The interview proves nothing.
Christensen's Jobs-to-be-Done framing holds that the right unit of analysis is the job the customer is hiring something to do, not the product the team is trying to sell. Scored on whether the subject held an explicit hypothesis about the job and tested it, rather than fishing for validation of their solution.
Held an explicit hypothesis about the underlying job and tested it deliberately. Was as willing to have it falsified as confirmed. Came away with a clearer view of the job — and therefore of the solution shape — than they went in with.
Carried a working hypothesis through most of the interview. Occasionally drifted into testing the solution rather than the job, but returned to the underlying question when the scenario permitted.
Hypothesis was implicit rather than explicit. The subject knew roughly what they were looking for but could not have articulated, mid-interview, what would falsify their view.
No working hypothesis was visibly in play. The interview was exploratory in a way that produced anecdotes rather than insight. The subject's view after the interview is roughly what it was before.
The hypothesis was the subject's existing solution, and the interview was a search for confirmation. The conversation systematically filtered out the evidence that would have challenged that view.
Behaviour-grounded discovery treats the customer's willingness to commit a small but real cost — time, introduction, follow-up call — as the strongest signal in the conversation. Scored on whether the subject sought and read those signals.
Asked for and read commitment signals throughout — a follow-up time, an introduction, a small cost the customer agreed to bear. Treated polite enthusiasm without commitment as the weak signal it is.
Sought commitment signals at the close and during. Occasionally accepted enthusiasm as commitment, but secured at least one concrete next step from most of the conversations.
Closed with vague next steps. Read the warmth of the conversation as a signal of interest without testing it. Came away with hope rather than commitment.
Did not seek meaningful commitment. The subject's read on whether to pursue this customer rests entirely on the emotional tone of the conversation, not on any cost the customer agreed to bear.
Mistook politeness for commitment. The subject left the conversation confident in a follow-up the customer has no real intention of honouring.
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 |
|---|---|---|---|
| Question Openness | 12 | 25% | 3.0 |
| Evidence vs Opinion | 15 | 30% | 4.5 |
| Hypothesis Discipline | 18 | 25% | 4.5 |
| Follow-up Commitment | 26 | 20% | 5.2 |
| Overall | 17 | — | — |
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.
