Fictional example / The decision at a glance
2-minute brief
Our recommendation: choose Alex on the behavioural evidence for this role, this team and the next six months. Alex is more compatible with the immediate need: reduce repeated reliability problems, finish one tightly defined integration and help other engineers make sound decisions.
The honest trade-off: Sam creates customer learning faster and brings more immediate energy into a discussion. Alex brings stronger evidence of dependable closure. Choosing Alex means giving up some of Sam’s useful speed and customer fluency—not pretending Sam has no advantages.
Why Sam is the wrong choice under the current conditions: Sam’s attraction to promising new work meets Dana’s urgency and Ellis’s enthusiasm. Each can encourage the others to say yes before deciding what must stop. That relationship could make an already stretched team less dependable.
What working with each person could feel like: Alex is careful, useful and sometimes hard to read. Sam is accessible, energising and sometimes too quick to commit. Both can share credit, accept feedback and change an answer. They create different pressures around them.
What happens if the hiring fails? With Alex, silence and managerial takeovers could damage trust. With Sam, repeated additions could disappoint customers and leave colleagues carrying unfinished work. Neither risk is solved by choosing the more likeable interviewee.
What Dana must change: protect priorities and stop confusing a quick answer with a reliable commitment. Technical ability remains for the employer to assess. Stronger technical evidence or a genuinely different role could change the combined decision.
Deeper reading: twelve MindFrame inquiries
The manager and team fixed the brief before we compared people
Dana’s first request was for someone who could “take problems off my plate.” We made that concrete before meeting either finalist. Which problems? What authority would the person have? What happened when an engineer challenged a deadline?
The team needed better reliability, one customer integration delivered within agreed limits, and more independent judgement across engineering. New product discovery mattered, but it was not the first priority during this six-month period. The role had no direct reports. Influence and team contribution mattered more than a polished management style.
Dana, Ellis and Robin each completed assessment work about their own patterns. Dana wanted fast visibility. Ellis explored customer possibilities in conversation. Robin protected stable interfaces and closure. Their combined habits sometimes produced a promise without a clear owner or an agreed trade-off.
This is why compatibility belongs in the decision. A high performer can be wrong for the current manager, priorities and working environment. Equally, a manager can create the conditions in which an otherwise suitable hire fails. We assessed the relationship from both sides.
The brief stayed the same for Alex and Sam. We did not choose a preferred personality and rewrite the job around it.
Comparable evidence, different conclusions
Both finalists completed Alma-supported assessment work, a MindFrame interview, the same integration discussion, a written decision note and a follow-up with a new dependency and capacity limit. Both had equivalent time and information. Agreed accounts from previous managers and peers were used to challenge—not merely confirm—the first impression.
We examined everyday behaviour: sharing credit, holding a boundary, admitting a mistake, responding to public disagreement and helping others when that meant giving up control or attention. Motivation and personal values were explored through choices with consequences, not only through what each person said mattered.
We also looked for self-important or narcissistic behaviours such as needing admiration, taking others’ credit, entitlement and reacting badly to a threat to status. This is not a clinical diagnosis. Motives remain interpretations; an attractive explanation does not make a hidden intention a fact.
Confidence is stronger where separate accounts and observed choices agree. Neither an exercise nor an assessment response can show an entire future relationship. The employer retains technical and employment checks.
Alex Moreno: reliability as a personal standard
Motivation and personal values
Alex wants work to remain useful after the conversation ends. Dependable systems, clear reasoning and a colleague able to continue independently recur in Alex’s examples. Mastery and autonomy matter. Public recognition seems less important than respect from people who understand the work.
There is a cost to that identity. An unfinished explanation can feel like falling short of being dependable. Alex may keep investigating to avoid exposing a view that could be wrong. That protects the quality of the answer but can leave the team without information it needs.
Alex wants influence over promises, not just responsibility for repairing their consequences. A senior title without access to planning is unlikely to satisfy that need for long.
Ego, credit and team-first behaviour
The previous peer described Alex accepting a different adequate design and crediting its author. In the assessment, Robin kept the implementation choice after Alex identified one essential safeguard. These are useful signs that Alex can give up personal preference and control.
The strongest counterexample appeared in customer discovery. Alex initially turned the customer’s story into an architectural problem. Expertise took centre stage before the actual need was understood. Alex corrected course when asked to restate the customer’s objective without a solution.
The day-to-day risk is sounding technically superior, especially when trying to be helpful. We found less support for persistent credit-taking or a need for admiration. That distinction has moderate confidence; it should still be tested when a highly visible project challenges Alex’s status.
Criticism, pressure and relationships
Alex changed a recommendation after a mistaken dependency was corrected. Feedback about the late warning first prompted an explanation of intent, then acknowledgement of the effect. Colleagues may hear defensiveness before ownership, even when Alex eventually acts on the feedback.
Under pressure, Alex becomes harder to read. Dana may take silence as loss of control and step in. Alex may experience that as distrust and withdraw further. This is the main compatibility risk.
Alex could also improve psychological safety through patient explanations and an ability to admit uncertainty. That benefit disappears if questioning feels like an examination or colleagues must present a perfect argument before being heard. Alex needs to explain the purpose of a question and make space for incomplete thinking.
What changed during assessment
Alex’s first warning came late. In follow-up, Alex raised the incomplete concern early, asked Dana to choose the protected outcome and proposed a reversible pilot. When Dana offered to take over, Alex kept the task while asking for the decision boundary.
A prior manager described a similar difference between unclear and clear ownership. We therefore see a manageable condition, not a general inability to move quickly. Clear responsibility helps Alex act without waiting to know everything.
Sam Duarte: progress as a way of understanding
Motivation and personal values
Sam wants people to move from a vague problem to something they can try. Customer contact, autonomy and visible progress are strong sources of energy. Sam seems to value being useful in the moment: making a stalled issue feel possible again.
That motivation can quietly become a need to be the person who says yes. A new request offers both learning and appreciation. Sam may experience a firm boundary as letting someone down, even when accepting the request would let another colleague or customer down later.
This is an interpretation supported by the first exercise and prior accounts, not a claim that Sam is secretly manipulative. The question is whether the desire to help and be valued overrides an existing promise.
Ego, credit and the need to be useful
Sam readily brings others into a conversation and makes experimentation less intimidating. The peer account described colleagues gaining confidence through that support. We did not find strong evidence of habitual credit-taking.
There is a subtler risk: remaining the person everyone contacts because Sam is responsive and knows the latest change. What begins as helpful coordination can preserve Sam’s central role and make a handover less complete than it looks.
When a colleague’s slower approach was challenged in discussion, Sam first defended the value of moving quickly. Asked what the colleague was protecting, Sam could restate the constraint and adjust the proposal. That supports perspective-taking, while showing how the first response might leave a more cautious colleague feeling dismissed.
Criticism, pressure and relationships
Sam speaks early and confidently. That helps a room move, but provisional ideas can sound like commitments. Dana may hear reassurance before Sam has examined the workload. Ellis may hear a partner willing to explore. Robin may hear another promise someone else will have to contain.
Feedback is easiest for Sam to use when it leads to a concrete next action. Repeated concerns about closure can first prompt an explanation that the customer need changed. If that explanation repeatedly replaces ownership, colleagues may feel their planning has little value.
Sam can create psychological safety by making it easy to contribute an idea and try something imperfect. Sam can also create pressure by maintaining a pace at which saying “we cannot do that” feels negative. Openness to ideas is not enough; the team must also be able to decline work.
What changed during assessment
Sam offered an additional customer request in the first discussion before naming what it would displace. Later, Sam narrowed the commitment. In the follow-up, Sam asked about priority, restated the existing promise and declined the addition when nothing could move.
A previous product peer described similar improvement after a costly scope change, but also a later completed experiment reopened for promising feedback. Sam can hold a boundary. The remaining concern is how consistently that discipline holds when the next opportunity is attractive.
The follow-up that resolved the material questions
Alex: can care become timely action?
Evidence: the first note buried the requested decision beneath careful analysis. A previous manager described a delayed warning when responsibility was disputed.
Interpretation: Alex may protect the quality of the answer at the expense of the team’s ability to act. Dana’s repeated intervention could make that worse.
Strongest counterexample: in follow-up, Alex raised uncertainty before completing the analysis and proposed a bounded next step. The previous manager also described timely warnings where responsibility was clear.
Decision effect and confidence: confidence is moderate that this team can make the relationship work through clearer ownership and earlier updates. If Dana refuses to change or Alex remains silent despite those changes, the positive recommendation no longer holds.
Sam: can momentum survive a firm boundary?
Evidence: Sam volunteered extra work before pricing its effect. The peer account included a completed experiment reopened for promising feedback.
Interpretation: attractive opportunities can compete with finishing what the team already owes. Dana and Ellis may reinforce this habit rather than contain it.
Strongest counterexample: Sam required recovery conditions before an irreversible migration and declined the extra request in follow-up. A blanket claim of recklessness would be wrong.
Decision effect and confidence: confidence is moderate that this role would demand sustained effort against Sam’s preferred way of contributing. Sam could perform strongly in discovery; the current stabilisation role offers less of that work and more repeated closure.
Are we simply rewarding the quieter candidate?
No. The customer-discovery segment exposed a clear advantage for Sam: Sam framed a useful learning step faster, while Alex initially narrowed the problem to architecture. Alex corrected course, but did not become equally fluent.
That strength is valuable. It is secondary to the work this hire must do first. If the company actually wants open-ended discovery, it should change the brief honestly and reconsider Sam. It should not hire Sam for one role while continuing to judge the person against another.
Decision matrix: what matters most here
| Question the hiring team needs answered | Alex | Sam |
|---|---|---|
| Who is more likely to finish the agreed work? | Stronger evidence of closure and useful handovers. Can over-check before calling a decision complete. | Strong at creating experiments; attractive additions can reopen work. More management effort needed in this role. |
| Who will tell us early when something is wrong? | Initial weakness; changed in follow-up with clear ownership. Needs an explicit expectation of unfinished warnings. | Communicates readily, but enthusiasm can hide uncertainty. Must separate an idea from a promise. |
| Who shares credit and control? | Peer account and exercise support another person retaining ownership and recognition. | Supports others’ confidence; needs to leave a complete handover instead of remaining the informal coordinator. |
| Who accepts challenge? | Corrected a mistaken recommendation. Vague public criticism may produce withdrawal and a written defence. | Can revise after restating the constraint. May first defend momentum and make caution feel obstructive. |
| What pressure might colleagues feel? | Pressure to arrive with a thoroughly reasoned answer. Quiet uncertainty may be hard to read. | Pressure to match the pace and agree to another possibility. Saying no may feel unhelpful. |
| Where is the strongest advantage? | Dependable judgement, closure and reusable reasoning. | Customer fluency, accessibility and fast learning. |
| Fit with this team now | Recommended if Dana changes the takeover pattern and protects early warnings. | Not recommended for the current brief and unchanged team habits. Reconsider for a genuine discovery role. |
- Question the hiring team needs answered
- Who is more likely to finish the agreed work?
- Alex
- Stronger evidence of closure and useful handovers. Can over-check before calling a decision complete.
- Sam
- Strong at creating experiments; attractive additions can reopen work. More management effort needed in this role.
- Question the hiring team needs answered
- Who will tell us early when something is wrong?
- Alex
- Initial weakness; changed in follow-up with clear ownership. Needs an explicit expectation of unfinished warnings.
- Sam
- Communicates readily, but enthusiasm can hide uncertainty. Must separate an idea from a promise.
- Question the hiring team needs answered
- Who shares credit and control?
- Alex
- Peer account and exercise support another person retaining ownership and recognition.
- Sam
- Supports others’ confidence; needs to leave a complete handover instead of remaining the informal coordinator.
- Question the hiring team needs answered
- Who accepts challenge?
- Alex
- Corrected a mistaken recommendation. Vague public criticism may produce withdrawal and a written defence.
- Sam
- Can revise after restating the constraint. May first defend momentum and make caution feel obstructive.
- Question the hiring team needs answered
- What pressure might colleagues feel?
- Alex
- Pressure to arrive with a thoroughly reasoned answer. Quiet uncertainty may be hard to read.
- Sam
- Pressure to match the pace and agree to another possibility. Saying no may feel unhelpful.
- Question the hiring team needs answered
- Where is the strongest advantage?
- Alex
- Dependable judgement, closure and reusable reasoning.
- Sam
- Customer fluency, accessibility and fast learning.
- Question the hiring team needs answered
- Fit with this team now
- Alex
- Recommended if Dana changes the takeover pattern and protects early warnings.
- Sam
- Not recommended for the current brief and unchanged team habits. Reconsider for a genuine discovery role.
These are reasoned comparisons, not numerical personality rankings. Similarity to the current team is not itself a benefit. Alex and Robin’s shared caution creates its own risk of a closed technical circle.
The same manager and peers create different interactions
Dana Price: urgency and visible ownership
Dana can delegate, but uncertainty often invites intervention. With Alex, silence could lead to takeover and less trust. With Sam, a quick positive response could disguise a commitment made before capacity is understood.
Dana needs different questions. For Alex: “What is your current view, and what needs deciding now?” For Sam: “What does this replace, and who has agreed that change?” In both relationships Dana must protect the priority order.
If Dana expects either person to absorb contradictory demands without challenge, neither hiring is well supported. This finding concerns the manager’s contribution to failure as much as the candidate’s.
Ellis Kim: customer proximity and flexible sequencing
Ellis explores possibilities aloud. With Alex, a useful question could be mistaken for resistance. With Sam, mutual enthusiasm could produce a promise neither realised was final.
Ellis should state the customer outcome before suggesting a solution and label the conversation: exploring, planning or committing. Alex must connect concerns to that outcome. Sam must name the displaced work before accepting another request.
Robin Cole: completion and protected boundaries
Robin values stable interfaces and clear ownership. With Alex, comfortable agreement could become a technical group that others find hard to challenge. With Sam, different instincts could become a repeated argument about speed.
Robin must offer an acceptable route forward, not just a veto. Alex must seek input beyond the pair. Sam must show that Robin’s concern was understood before offering another option. No colleague should become the permanent person who compensates for a hire’s least natural habit.
A decision record the hiring team can use
Decision: Alex is the stronger behavioural match for the agreed six-month work. The recommendation depends on clearer ownership and protected early warnings.
Reason: Alex’s motivation and observed choices support dependable closure. The initial visibility concern was investigated and reduced. There is credible evidence of accepting correction, giving credit and leaving others in charge.
What we give up: Sam’s faster customer framing and ability to create energy around a first step. The team must obtain that contribution through Ellis and planned customer exposure for Alex.
Why we are not choosing Sam for this role: Sam could be a strong contributor, but the current manager–product–candidate combination would make repeated new commitments too easy. This is a specific compatibility judgement, not a permanent claim that Sam “does not fit our culture.”
What happens if we choose Sam anyway: the company should acknowledge the extra management demand and genuinely protect the role’s boundaries. A written plan will not help if Dana and Ellis keep rewarding another enthusiastic yes. Selecting Sam while leaving those habits untouched is not our recommendation.
What could change the decision: materially different technical evidence, a real change to the job, or new substantiated work examples. A preference for the more familiar or charismatic person is not new evidence.
Feedback and scope: explain the decision through the work and observed behaviour; do not share one finalist’s private portrait with the other. A two-finalist proposal covers two independent assessments and specifies shared context work. It is not one assessment plus a €500 extra participant. Applicable VAT is additional.
First 90 days: two practical paths
| Period | If Alex joins | If Sam joins | What the team should check |
|---|---|---|---|
| Before starting | Agree early-warning examples and who decides what | Agree commitment authority and what allows scope to change | Dana and the hire can explain the same three examples. |
| Days 1–30 | Share an incomplete concern with a next update time | Name displaced work before accepting a new request | Ellis knows the real promise and uncertainty before updating the customer. |
| Days 1–30 | Dana welcomes the warning without taking over | Dana supports a justified no despite a tempting opportunity | The manager’s behaviour matches the stated agreement. |
| Days 31–60 | Run a bounded experiment without complete certainty | Finish an experiment before opening the attractive extension | Robin sees useful learning and an actual stopping point. |
| Days 31–60 | Leave a colleague’s different adequate answer intact | Hand over an initiative without staying its informal coordinator | The colleague can act independently and receives visible credit. |
| Days 61–90 | Review two warnings and one disagreement | Review two scope choices and one handover | Check what the assessment got wrong as well as what it got right. |
- Period
- Before starting
- If Alex joins
- Agree early-warning examples and who decides what
- If Sam joins
- Agree commitment authority and what allows scope to change
- What the team should check
- Dana and the hire can explain the same three examples.
- Period
- Days 1–30
- If Alex joins
- Share an incomplete concern with a next update time
- If Sam joins
- Name displaced work before accepting a new request
- What the team should check
- Ellis knows the real promise and uncertainty before updating the customer.
- Period
- Days 1–30
- If Alex joins
- Dana welcomes the warning without taking over
- If Sam joins
- Dana supports a justified no despite a tempting opportunity
- What the team should check
- The manager’s behaviour matches the stated agreement.
- Period
- Days 31–60
- If Alex joins
- Run a bounded experiment without complete certainty
- If Sam joins
- Finish an experiment before opening the attractive extension
- What the team should check
- Robin sees useful learning and an actual stopping point.
- Period
- Days 31–60
- If Alex joins
- Leave a colleague’s different adequate answer intact
- If Sam joins
- Hand over an initiative without staying its informal coordinator
- What the team should check
- The colleague can act independently and receives visible credit.
- Period
- Days 61–90
- If Alex joins
- Review two warnings and one disagreement
- If Sam joins
- Review two scope choices and one handover
- What the team should check
- Check what the assessment got wrong as well as what it got right.
Ask the team about the atmosphere as well as delivery: can someone admit an error, disagree with the hire or say a request is unrealistic? The answer may expose a cost that project progress alone conceals.
Deeper reading: twelve MindFrame inquiries
The same work-focused inquiries were explored with both people. They are an interview framework, not a scored personality questionnaire.
1. Identity
Alex wants work to remain dependable without explanation. Sam wants people to learn by trying. Both seek usefulness, but receive a sense of success from different moments in the work.
2. Others’ perceptions
Alex recognises being hard to read; Sam recognises saying yes too quickly. Each changed the relevant action in follow-up. Neither insight alone proves the change will last.
3. Group role
Alex identifies the consequential assumption. Sam finds a customer-visible step. The team needs both contributions, but this particular vacancy has a stronger need for dependable closure.
4. Misunderstanding
Alex’s questions can sound like resistance. Sam’s exploration can sound like a promise. Both accepted responsibility for how others heard them, rather than blaming colleagues entirely.
5. Multiplying others
Alex shares reasoning and can leave another person’s design intact. Sam makes experimentation approachable. For both, the real test is whether the colleague keeps ownership after receiving help.
6. Toward and away
Alex wants influence over reliability and less preventable firefighting. Sam wants fewer stalled handovers and closer customer learning. The present job offers more of Alex’s preferred work.
7. Resources
Alex chose better observability; Sam chose a better experimentation environment. With no extra budget, each named work to stop. Their priorities did not rely entirely on ideal resources.
8. Best and worst
Alex can make uncertainty manageable or handle it privately for too long. Sam can create progress or keep too many possibilities alive. Their effects on colleagues differ.
9. Friction
Alex dislikes unsupported certainty. Sam dislikes objections without a route forward. Both practised describing the legitimate need underneath the behaviour that irritated them.
10. Being wrong
Alex revised a recommendation after a dependency correction. Sam withdrew an additional promise after examining its cost. The changed action matters more than claiming to welcome feedback.
11. Starting and finishing
Alex can extend the evidence-gathering. Sam can move the finish line. In the current stabilisation period, the second habit creates the larger ongoing demand on the team.
12. Future failure
Alex imagines becoming the last approver. Sam imagines incompatible promises made in separate conversations. Both possibilities belong in the working agreement—not in a permanent label attached to the person.