CS Interview Coach

By grade

Making Effective Decisions SEO Example Answers (Civil Service)

Published · Last updated


The SEO calibration adds two demands a tidy decision answer cannot meet. The unpopular descriptor stops being decorative: the panel wants a decision that cost you something with people who mattered.

And challenge changes direction. At HEO you survive it; at SEO the descriptors expect you to invite it, building dissent into the decision before making it, precisely because at this grade your decisions are big enough to be wrong expensively.

So the strongest SEO evidence has an uncomfortable shape: a call you made against the room's preference, with the room's best arguments deliberately heard first, and a risk you carried with your name on it.

What SEO panels score on this behaviour

Unpopularity with real people attached. Not "some were sceptical" but a named role, a sponsor or a senior stakeholder or your own team, who wanted the other outcome and said so. The disagreement is your evidence, so keep it at full strength.

Challenge invited before the decision. The sceptic asked to make the counter-case, the assumptions stress-tested by people motivated to break them. This descriptor separates SEO answers more reliably than any other in the behaviour.

Evidence from a range of sources, weighed against each other. Data plus frontline insight plus stakeholder input, including where they conflicted and which you trusted more, and why.

A risk carried, with a tripwire. What you accepted could go wrong, what you watched to know if it was, and what you would have done. Confidence without a monitoring mechanism reads as bravado.

Questions this appears as

  • "Tell me about a difficult or unpopular decision you made."
  • "Describe a decision where the evidence pointed against the popular option."
  • "Tell me about a time you had to decide between competing priorities or interests."
  • "How have you handled making a decision you knew others would disagree with?"

Probes to expect: "Who disagreed and what did you do about it?", "What would have changed your mind?", "How did you know the decision was working?"

Fail vs pass at SEO: the same pilot

FailVersion 1: tidy and evidence-based, scores around 4/7 at SEO

"My team was six months into a twelve-month pilot of a new digital appointment-booking channel, and I was responsible for its evaluation. When I reviewed the mid-point data, the picture was clear: uptake was well below forecast, around 60% of digital bookings still generated a follow-up phone call, and the cost per transaction was running above the channel it was meant to replace. I did a thorough analysis (usage data, customer feedback, cost modelling) and concluded the pilot wasn't delivering and was unlikely to recover in the second six months. I recommended to the programme board that we end the pilot early and redirect the remaining budget into improving the phone service, and I presented the evidence clearly, covering the options, costs and risks. The board accepted my recommendation, the pilot was closed down in an orderly way, and the redirected budget funded improvements that measurably reduced call waiting times. It wasn't an easy message, but the evidence spoke for itself."

Competent, evidenced, and suspiciously smooth. Read it at SEO calibration: who was unhappy? A six-month-old pilot has a sponsor, a delivery team and believers, and in this telling they have all evaporated behind "the board accepted my recommendation". No challenge is invited anywhere. The closing line, that the evidence spoke for itself, is the tell, because evidence never speaks for itself to people invested in the other answer. The decision-making is real but frictionless, which at SEO reads as either a sanitised story or a low-stakes one. A 4.

PassVersion 2: the same pilot, around 6/7

"Six months into a twelve-month pilot of a digital appointment-booking channel, my mid-point evaluation showed trouble: uptake well below forecast, 60% of digital bookings generating a follow-up call, cost per transaction above the channel it was meant to replace. The complication was that the pilot wasn't an orphan — our G6 had sponsored it publicly, a supplier relationship and two staff secondments were built around it, and the delivery team had put real craft into it. Recommending early closure meant telling people I respected that their year's work should stop, on my analysis. So before deciding anything, I invited the strongest possible challenge to my own reading. I asked the pilot's delivery lead — the person with most reason to prove me wrong — to spend a week making the best evidence-based case for continuing, with full access to my analysis. His counter-case was genuinely useful: he showed the follow-up-call rate was concentrated in two booking types and falling month on month, and argued the channel was six weeks of fixes from viability. That changed the shape of my decision but not its direction — I tested his trajectory against the remaining budget and it required everything to go right with nothing left for the phone-service improvements we knew worked. I decided to recommend closure, and I built his analysis into the recommendation honestly rather than burying it: here is the best case for continuing, here is why I still conclude we should stop, here is the risk I'm accepting — that the trajectory he identified was real and we're closing a channel that would have come good. I attached a tripwire to my own risk: the two booking types he'd flagged would be offered digitally within the existing main website instead, so if demand was real we'd see it and could rebuild on evidence. The G6 didn't hide her disappointment, and pushed hard in the board meeting on sunk investment; I acknowledged the cost plainly and held the line on the distinction that mattered — the money spent was gone whichever way we decided; only the money remaining was actually on the table. The board closed the pilot. The delivery lead told me afterwards the process was the fairest hearing a losing argument could get, and asked to work on the phone-service improvements — which, funded by the redirected budget, cut average waits by a third. The tripwire, eighteen months on, has shown modest digital demand for exactly one of the two booking types, and a scoped rebuild for that single journey is in next year's plan — which I count as the original decision working, not failing: we stopped the expensive version and kept the learning."

The annotation:

  1. The unpopularity has names and weight. A G6 sponsor, a supplier, secondments and a proud delivery team. The cost of the decision is established before the decision is made. Version 1's board is an audience; Version 2's is a room with stakes in it.
  2. Challenge is invited, structurally. The delivery lead, the person with most reason to prove the candidate wrong, is commissioned to make the counter-case with full data access. This is the SEO descriptor performed at full strength, and the single biggest scoring difference between the versions.
  3. The challenge changes the decision's shape. His analysis is genuinely absorbed, with the two booking types surviving as a tripwire, rather than theatrically heard. Invited challenge that alters nothing is theatre; this is the real thing.
  4. The risk is owned with a mechanism. "The risk I'm accepting... here's the tripwire" is confidence with instrumentation, and the eighteen-month coda shows the mechanism working and the candidate scoring it honestly.
  5. The sunk-cost argument, held under pressure. The exchange with the disappointed G6 is the confidence-in-unpopular-decisions descriptor in a single move: respectful, plain, and unmoved on the one distinction that mattered.
  6. The losing side's dignity is part of the craft. The counter-case presented honestly in the recommendation, and the delivery lead asking to join the next piece of work. Decisions at SEO have to leave the organisation functional, and panels notice answers that understand that.

Calibrating either side of SEO

At HEO, Version 1 tightened, with the decision clearly owned within delegation, is scoring evidence. At G7, the calibration shifts to decisions on genuinely incomplete evidence, where waiting is itself the expensive option. Behaviour-wide guidance is in the Making Effective Decisions pillar.

SEO-specific mistakes on this behaviour

  1. The frictionless close. "The board accepted my recommendation" with nobody unhappy anywhere. Restore the disappointed sponsor, because they are your evidence.
  2. Challenge survived, never invited. Announcing and defending is HEO-shaped. Show the dissent you commissioned before deciding.
  3. "The evidence spoke for itself." It did not, and the sentence erases exactly the persuasion and confidence the descriptors score.
  4. Risk named, not carried. Listing risks in a paper is analysis. Accepting one with a tripwire and your name on it is the SEO mark.
  5. The counter-case strawmanned. If the best argument against you was weak, the decision was easy and the evidence thin.
  6. No answer to "what would have changed your mind?" Prepare it. A genuine answer proves the decision was reasoned rather than rationalised.

Common questions

Practise before the real thing

Reading how panels score is step one. The candidates who pass are the ones who practised saying their answers out loud — and got scored feedback against the official Civil Service Behaviours framework before interview day.

Start Practising FreeStart a practice session

3 free practice questions · No card needed · Cancel anytime