# Hiring a COO: a strong candidate, but the CEO will not let go

**FICTIONAL EXAMPLE · COMPLETED ASSESSMENT SCENARIO.** Every person, organisation, quotation, assessment response, document, observation and event in this report is invented. It demonstrates the proposed reporting approach, not a real engagement, validated prediction or client outcome. No real participant data or test scores are used. The conclusions are illustrative human advisory views; the client retains its decision.

**Executive Dynamics · Nora Vale · Fieldnorth, B2B software · CEO: Elliot Shaw · CFO: Mira Chen · Operations lead: Leo Grant**

## 2-minute brief

**Recommendation: do not hire Nora into this COO role under the current conditions.** She has the relevant people-leadership strengths. The problem is compatibility with the CEO's actual way of working: Elliot wants her to own delivery while he keeps the right to reverse everyday decisions privately. The final discussion confirmed that he is not yet willing to change this.

**What working with Nora could feel like:** clear priorities, thoughtful challenge and fewer promises the team cannot keep. She gives people credit, accepts specific criticism and can develop another leader's judgement. Under repeated interference, however, she is likely to add checks and become controlling. The team would have two centres of authority.

**What happens if this hiring fails?** Nora carries responsibility without power; managers receive competing instructions; missed commitments become arguments about who overruled whom. Strong leaders may stop deciding or leave. The company could pay for a COO and still operate through the founder.

**The uncomfortable finding:** a capable candidate cannot compensate for a manager who will not give her the job advertised. This is a relationship problem already present in the evidence, not a prediction that Nora would fail in every COO role.

**Her own risk:** Nora gives loyal colleagues too many chances. The assessment found a completed performance decision, but also avoidable work carried by others while she delayed it. A fair, supportive style can still protect favourites for too long.

**Next decision:** pause this appointment. Elliot should first demonstrate that delegated decisions stand, including one he dislikes. If that changes, revisit the match against the same role. Do not ask Nora to prove herself by quietly doing two people's jobs.

## The CEO and leadership team came first

The first interview was with Elliot, the CEO and future manager. We examined how decisions were actually made before asking Nora how she liked to lead. Mira and Leo were also assessed for their own patterns, not just asked whether they liked the candidate.

The company needs a COO because customer promises, delivery capacity and financial forecasts no longer join up. Elliot wants to spend less time resolving disputes. Yet the examples he supplied showed him continuing to give individual teams instructions after an operating decision had been agreed.

We defined the job clearly: the COO owns operating priorities, delivery accountability and the development of functional leaders. Elliot owns strategy and major commercial choices. Routine exceptions should go through the COO; a material strategic disagreement needs one shared decision.

In the exercise, Elliot accepted that arrangement. In the final role discussion, he reserved an unrestricted right to change any customer priority directly: “If I think the customer needs it, I need to be able to call the team.” Asked whether he would first resolve the difference with Nora, he declined to make that commitment. Two recent decision records showed the same practice after earlier delegation promises.

This changed the recommendation. The candidate had been assessed against a genuine COO job. The CEO was offering responsibility with revocable authority. A senior coordinator might work in that structure; hiring a COO to end founder dependence would be a different proposition.

## What the assessment covered

Alma-supported assessments explored motivation, preferred ways of working, relationships and behaviour under pressure. MindFrame interviews used work examples and follow-up questions to understand the person behind the answers. The framework draws on psychology, organisational psychology and applied neuroscience relevant to people management; this does not make a particular interview conclusion a scientifically proven prediction.

The evidence included a capacity exercise, a CEO-override scenario, two previous-colleague accounts, decision notes and leadership-review records. We followed the difficult performance-management example through to its outcome and tested the proposed authority agreement with Elliot before the final recommendation.

The focus was soft competencies: judgement with people, credit and blame, response to criticism, authority, fairness, trust and team compatibility. The employer still assesses functional expertise, commercial results and hard skills through its own process.

A polished interview answer was not enough. We compared what Nora said, what she did in an exercise and what others described. Where these differed, the report explains the difference. Motives are interpretations to test, not access to someone's private thoughts.

## The person before the position

### What matters to Nora

Nora takes pride in being dependable. She describes her best work as a team keeping promises without a heroic recovery. In one example she chose an unglamorous capacity improvement over a prominent launch assignment. This supports a practical motive: making the organisation work matters more to her than being its public face.

That is not evidence that recognition means nothing to her. She reacts strongly when careful work is casually overridden. Part of that reaction protects the team; part may protect her identity as the person whose judgement can be trusted. When challenged about this, she recognised both possibilities.

Her values fit a company that wants clear commitments and honest limits. They fit less well where leaders prize constant improvisation and treat agreed responsibilities as optional. Neither preference alone makes someone a good or bad executive. Here, the mismatch affects whether she can do the job.

### Vanity, credit and team-first behaviour

Nora gave a previous team lead credit for an improvement she had sponsored, including in a senior review where she could have claimed it herself. A colleague described her correcting a CEO who attributed the result only to Nora. That is concrete team-first behaviour.

We also checked what happened when somebody else made a sound decision differently from her. In the exercise she let Leo's recommendation stand and explained its strengths. A previous colleague supplied a similar example, alongside a less flattering one in which she rewrote a presentation before a board meeting.

The evidence does not support making vanity the central concern. It does support a narrower risk: when her reputation is exposed, she may take control of how the work is presented. Team members could retain the task but lose the chance to learn or be seen. The useful question is who keeps ownership when the stakes rise.

### Criticism, public challenge and admitting mistakes

Nora responds well to a specific challenge. When Mira identified an unsupported assumption, she changed the proposal and named the correction. When challenged broadly as “controlling,” she first explained her good intentions. Only after the effect was made concrete did she acknowledge the impact.

Working with her should be easier for someone able to say, “You changed my decision after agreeing it was mine,” than for someone relying on hints. That is also a leadership responsibility for Nora: quieter colleagues should not need to be unusually assertive to keep their authority.

There was no observed ridicule, retaliation or attempt to humiliate a critic in the completed scenarios. This is useful counterevidence to a concern about self-important or narcissistic behaviour. It is not a clinical judgement or proof that such behaviour could never occur. Repeated responses to dissent matter more than an attractive personality label.

### Pressure and the experience of being managed by her

When accountability is unclear, Nora schedules another review, asks for another update and joins the problem personally. She means to make the situation safer. A capable report may instead feel watched or corrected before having the chance to act.

The counterexample is important: where ownership was explicit, she left a disputed decision with its owner and backed it publicly. Difficulty alone did not trigger takeover; uncertainty about who was responsible did.

On a normal week, a report could expect clear priorities and thoughtful help. In a bad month, the same person might experience frequent check-ins and less room to make a judgement. In this company, Elliot's overrides would repeatedly create the uncertainty that brings out that pattern.

### Loyalty, fairness and blame

Nora publicly defended a service director after a failed launch because the team had warned that the promised capacity did not exist. She corrected the account in front of the same leaders who had heard the blame. That action made early disclosure more worthwhile.

In another case she gave a long-serving manager repeated extensions after missed commitments. Records showed no new evidence that another extension would help. Two colleagues kept absorbing the work. Nora eventually removed the management responsibility, but acknowledged that shared history had delayed her.

This is the report's clearest warning about her own leadership. She can be fair in principle and unequal in practice when loyalty is involved. The person she protects gets patience; everyone else pays for it. A team-first intention is insufficient if the team's burden keeps growing.

### Relationships over time

Nora builds trust through follow-through, remembering commitments and helping people prepare. She is unlikely to create instant warmth with everyone, but colleagues should know where they stand when the role is clear.

A risk develops when she becomes the person who quietly resolves every tension. People may value her support while avoiding their own difficult conversations. Long-term success requires more than being liked or indispensable: colleagues need to become more capable without her.

Her best environment allows challenge, keeps ownership visible and treats changed priorities as real decisions. Her worst environment demands accountability, rewards private exceptions and then criticises her for adding control.

## Two executive decisions that changed the reading

### Can she hold a valued colleague accountable?

A respected manager repeatedly missed follow-ups. Nora's first account emphasised the support offered and the person's earlier contribution. Review records showed repeated extensions; a previous report described taking on unfinished work without a clear end date.

We checked the outcome. Nora eventually separated past contribution from current responsibility, agreed one final supported commitment and transferred the management role when it was missed. She explained the change without attacking the person.

This ruled out the simple claim that she cannot make a difficult people decision. It also ruled out treating the delay as harmless kindness. Her own account accepted that loyalty had influenced the extra chances. For her next role, performance reviews need a clear point at which support ends or responsibility changes, applied equally to influential insiders.

### Can she say no to the CEO, and will the CEO accept it?

In the exercise, Elliot proposed an attractive customer exception that displaced two existing implementations. Nora asked Leo for his recommendation, brought Mira into the financial assumptions and set out the cost of each option. When Elliot requested one reassuring date, she retained the uncertainty and explained what would resolve it.

She then protected existing commitments and offered a smaller pilot. Leo kept ownership of the plan. This was useful evidence of upward challenge without taking the whole decision back herself.

The final manager interview changed the picture. Elliot accepted her reasoning but would not accept a lasting restriction on his own direct instructions. He described bypassing the COO as necessary flexibility. Asked about the resulting accountability, he still expected Nora to deliver the overall plan.

The exercise showed that Nora can challenge him. The completed follow-up showed that her challenge would not reliably protect her authority. **Do not proceed under the present conditions.** It would be misleading to turn a manager's refusal to delegate into another development task for the candidate.

## The people around her: own patterns and interaction loops

These are the relationship patterns assessed and the changes a later appointment would require. They are not agreements already accepted by the CEO.

### Elliot Shaw · CEO and appointing manager

**How he works:** energised by opportunities, thinks aloud and changes direction when market information arrives. He experiences a newly surfaced option as learning; others sometimes experience it as a decision already made.

**What happens between them:** Elliot announces an opportunity → Nora converts it into an operating commitment → he experiences constraint and speaks directly to a team → she tightens coordination. Both can conclude the other does not trust them.

**Required change:** label exploration versus commitment; keep one shared decision record; review genuine exceptions together. Elliot owns stopping informal reversals. Nora owns preserving room for exploration before applying delivery constraints.

### Mira Chen · CFO and executive peer

**How she works:** values traceability and a stable distinction between known facts and assumptions. Under uncertainty, she asks for narrower ranges before endorsing a forecast.

**What happens between them:** Mira requests precision → Nora negotiates stronger commitments from operations → fragile estimates appear firm → later revisions reduce Mira’s trust. Their shared desire for reliability can manufacture apparent certainty.

**Required change:** publish assumptions, ranges and dates for new evidence. Mira accepts bounded uncertainty; Nora resists extracting certainty that teams cannot substantiate. Track forecast explanations, not merely whether a number stayed unchanged.

### Leo Grant · Operations lead and prospective direct report

**How he works:** practical, proud of customer recoveries, quick to volunteer help. He prefers resolving a problem to exposing it while incomplete.

**What happens between them:** Leo rescues privately → Nora sees the problem late → she joins closely → he receives less practice owning a difficult trade-off. The pair can deliver today while weakening tomorrow’s leadership capacity.

**Required change:** Leo presents the issue, options and recommendation before recovery begins; Nora specifies the decision boundary and leaves him ownership. Review exceptions without rewarding last-minute heroics disproportionately.

## Executive mandate and accountability map

This is the authority the intended COO job requires. Elliot has not accepted it in practice, which is why the appointment is paused.

| Decision or responsibility | Owner and boundary | Evidence that the arrangement is working |
|---|---|---|
| Operating capacity and sequencing | Nora, within the agreed business priorities and resource envelope | Teams receive one priority order; exceptions name the work displaced. |
| Strategy and material commercial departure | Elliot, with operational and financial consequences explicit | A strategic change is recognised as a change, not disguised as a small delivery request. |
| Delivery decisions within a function | Leo or the relevant leader | The leader decides and explains the reasoning; Nora does not rewrite a sound answer. |
| Forecast assumptions | Mira and Nora supply the shared account; underlying owners retain the evidence | Ranges and dependencies survive the board summary; confidence is not manufactured through pressure. |
| Senior-leader performance | Nora for her reports, using consistent evidence and a stated review point | History and personal sacrifice are recognised without indefinitely postponing consequences. |
| Unresolved CEO/COO disagreement | One agreed route for unresolved disagreements, with one instruction after the decision | Teams are not asked to choose between private instructions. |

The map addresses the work design. It does not replace formal governance documents. The appointment discussion should confirm that the agreed responsibilities correspond to authority the CEO is prepared to transfer in practice.

## Culture: what her behaviour would teach the company

### Does she make it safe to tell the truth?

Nora protected a leader who had raised a real capacity problem before a failed launch. That gives the team a reason to speak early. She also corrected an assumption when challenged. Both behaviours could support psychological safety: people can raise concerns, admit uncertainty and challenge a plan without being personally punished.

There is a limit. Extra checking after an uncomfortable surprise can teach people that bringing a problem creates more supervision. Delayed action on a favoured colleague can teach them that candour matters less than personal history. Psychological safety is therefore a question about repeated behaviour, not a badge awarded to a warm or calm leader.

### What the team could feel after six months

**If the relationship works:** leaders bring bad news early, make decisions inside clear boundaries and receive credit for their judgement. Nora makes pressure discussable and distributes it fairly. Strong standards and a safe environment can coexist.

**If the current arrangement continues:** Elliot promises, Nora checks, managers wait for the second answer. Nora appears more controlling; Elliot calls her inflexible. Team members spend time managing the relationship above them instead of serving customers.

The second pattern is supported by the existing decision examples and the final authority discussion. It is why this report recommends stopping the appointment now, rather than selling an onboarding plan as the cure.

## A practical 30 / 60 / 90-day playbook

This is a decision plan for a paused appointment. It is not a recommendation to hire now and hope the relationship improves.

| When | Owner | Action | What would count as progress |
|---|---|---|---|
| Now | Elliot and hiring lead | Tell Nora the current authority gap and pause the appointment | No offer describes a COO remit the CEO will not transfer. |
| Days 1–30 | Elliot | Give the current operating lead a defined set of real decisions | A decision Elliot dislikes stands unless a pre-agreed escalation condition is met. |
| Days 1–30 | Mira and operating lead | Record priority changes and who authorised them | Informal instructions are visible, including their cost to existing commitments. |
| Days 31–60 | Hiring lead and Elliot | Review actual decisions and the experience of affected leaders | Evidence shows changed manager behaviour, not a rewritten job description alone. |
| If the role changes | Nora and hiring lead | Revisit compatibility with the real remit and evidence | Both can state what Nora owns and how disagreement ends. |
| First 90 days after any later appointment | Nora and leadership team | Review ownership, treatment of loyal colleagues and early disclosure | Leaders retain decisions, standards are consistent and bad news arrives before recovery is needed. |

Nora may reasonably choose not to wait. The assessment does not imply that the company should hold a candidate in uncertainty while it works out whether it wants a COO.

## Advisory conclusion and remaining limits

**Nora looks capable of the intended role. The current manager relationship is not compatible with that role. Do not proceed under the conditions confirmed in this assessment.**

The case does not turn on a low personality score or an allegation about Elliot's character. It turns on a specific contradiction: Nora must own delivery while Elliot retains a private route to change the decisions that determine delivery. Nora's tendency to respond with more coordination would probably intensify the conflict.

The strongest counterargument is that early-stage CEOs need flexibility. They do. The issue is whether flexibility has a clear owner and an honest consequence, or creates competing instructions. Elliot can retain final strategic authority without keeping every operating decision informally reversible.

The employer remains responsible for hard-skill, financial and commercial evaluation. This report adds the depth hiring teams often lack time to develop: what it could feel like to work with this person, what each side would bring out in the other, and why a strong individual may still be the wrong appointment in a particular environment.

**Illustrated scope:** Executive Dynamics, from €10,000 plus applicable VAT, covering the candidate, manager and two additional assessed colleagues with a deeper leadership assessment. Each additional assessed colleague is €500; a fully assessed executive is a separate scope.

## Deeper reading: twelve MindFrame inquiries

These work-focused questions connect Nora's motives and patterns to the compatibility assessment. They explain the reasoning; they do not produce a clinical diagnosis or a guaranteed forecast.

### 1. Identity
“I make the promise match what we can deliver.” Nora’s stewardship is personally meaningful. The bounded market pilot shows that it can coexist with deliberate uncertainty.

### 2. Others’ perceptions
Reliable and fair were recurrent descriptions. A colleague found her calm manner difficult to read before a more prescriptive recap. Composure does not automatically make a boundary visible.

### 3. Group role
Nora organises decisions and dependencies early. She can restore orientation quickly, but should distinguish a meeting for exploration from one intended to commit resources.

### 4. Misunderstanding
“I need the disagreement to be explicit.” Her follow-up choice closed with acknowledged dissent. That demonstrates a capability to decide without obtaining universal relational reassurance.

### 5. Multiplying others
A leader used her trade-off method independently. Other records showed her rewriting recommendations under visibility pressure. The important measure is ownership retained when the outcome matters.

### 6. Toward and away
She wants to build an operating team and leave perpetual recovery work behind. The current role gives responsibility without dependable authority. Her wish to end recovery work would not be met by accepting it.

### 7. Resources
Nora prioritised frontline leadership and handovers. During allocation, she protected a capability investment while accepting a narrower launch. Her stated priority influenced an actual trade-off.

### 8. Best and worst
At best, owners decide with early disclosure. At worst, Nora tracks every exception. More exceptions on her own list are a useful warning before visible conflict appears.

### 9. Friction
Confident promises with unowned consequences irritate her. She recognised the commercial opportunity before rejecting its delivery promise. The final manager discussion showed that reasonable challenge alone would not protect her authority.

### 10. Being wrong
Nora revised an allocation after new evidence, then initially explained why her earlier view was reasonable. She subsequently acknowledged the impact directly; repair needed both sentences.

### 11. Starting and finishing
Written owners are useful, but a project is not fully transferred if people still seek Nora’s approval. Completion includes removing unnecessary dependence on her.

### 12. Future failure
“The CEO wanted relief, but not a different way of deciding.” Nora also named her own part: accepting uncertain authority and compensating through personal effort.