CS Interview Coach

By grade

Making Effective Decisions HEO Example Answers (Civil Service)

Published


Making Effective Decisions has the cleanest failure signature of any behaviour at HEO: the candidate does everything except decide. The analysis is thorough, the options are laid out, the risks are identified — and then the answer's climactic sentence is "I presented these options to my manager, who agreed we should go with option two." The candidate hears diligence. The panel hears the exact moment the behaviour being scored was handed to someone else. At HEO the descriptors are explicit — understand your own level of responsibility, display confidence when making difficult decisions, even if they prove to be unpopular — and the difference between a 3 and a 6 is usually a single question: at the moment of choice, whose finger was on the button?

What HEO panels score on this behaviour

A decision that was yours. Made within your delegation, or a recommendation pressed with a clear position — not a menu handed upward. "I decided" or "I recommended X and made the case for it" both score; "I presented the options" doesn't.

Evidence weighed, not just gathered. The descriptors say analyse a range of relevant, credible information — the mark is in showing what the evidence changed about your thinking, including the option it killed.

The rejected option, named. A decision only exists relative to what you didn't do. One sentence on the credible alternative and why it lost is worth more than a paragraph of extra context.

Discomfort survived. Timeliness under uncertainty, a stakeholder who disagreed, a call you'd have to defend. Comfortable decisions carry no HEO evidence.

Questions this appears as

  • "Tell me about a difficult decision you've made at work."
  • "Describe a decision you made without all the information you wanted."
  • "Tell me about a time your decision was challenged or unpopular."
  • "How have you used evidence to reach a decision?"

Probes to expect: "Why was that decision yours to make?", "What was the alternative?", "Who disagreed?", "What would you have done if it had gone wrong?"

Fail vs pass at HEO: the same mailout

FailVersion 1 — owned the analysis, not the decision. Scores around 3/7

"We were about to issue a bulk mailout to around 12,000 customers about a change to how they submit their annual returns. The letters were printed and scheduled for collection when I spotted, during a final check, that a batch of them quoted an incorrect deadline date because of a data merge error. I immediately investigated the scale of the problem — I ran a query against the mailing data and established that around 2,300 letters were affected, all in one regional batch. I then worked out the options: recall and reprint the affected batch, which would delay the whole mailout by at least a week; send everything and follow up the affected customers with a correction letter; or hold just the affected batch and send the rest. I assessed the costs, risks and timescales of each option and put them to my manager with my analysis. She decided we should hold the affected batch and send the rest, which is what we did. The corrected letters went out five days later, and my thorough checking was credited with catching the issue before it caused real problems."

Everything about this is competent — the catch, the quantification, the options analysis. And the behaviour under assessment happens in someone else's head. Read the pivotal sentence again: "She decided." The candidate built the entire decision and then gave it away, and the answer even signposts the wrong achievement — "my thorough checking" — as if the behaviour were Managing a Quality Service. At EO, presenting analysed options upward is exactly right. At HEO, it's a 3 with excellent production values.

PassVersion 2 — the same mailout, around 6/7

"We were about to issue a bulk mailout to 12,000 customers about a change to annual return submissions when, during a final check, I spotted that a data merge error had put the wrong deadline date on part of the print run. The letters were scheduled for collection at 4pm — so the first thing I established was what was actually mine to decide, and holding a batch within our print schedule sat inside my delegation; only scrapping the full run would have needed escalation. I quantified the problem fast: a query against the mailing data showed 2,300 letters affected, all one regional batch. That gave me three options, and I gave myself until 2pm to choose, because a slow right answer would become a wrong one at collection time. Recalling everything punished 9,700 customers with a week's delay for an error that didn't touch them — I rejected it in minutes. The genuinely close call was between sending everything with a correction letter to follow, and holding the affected batch. Sending-plus-correcting was cheaper and faster, but I checked what the wrong date would actually cause: customers who acted on it would miss the real deadline and trigger automatic reminders and potential penalties — harm a correction letter arriving days later couldn't reliably prevent, especially for customers who act on the first letter they open. So I decided: hold the 2,300, send the 9,700 on schedule, reprint the batch with a short covering line acknowledging the delay. Our print coordinator disagreed — splitting a run created manual work at their end and they pushed to send everything with corrections. I held the decision and gave them my reasoning: their week of manual handling was real, but it was recoverable; penalty notices to customers who followed our own letter weren't. I informed my manager of the decision and the reasoning at 2:15 — informed, not asked — and she backed it. The 9,700 went out on time, the corrected batch followed in five days with zero deadline-related complaints or penalty cases from the affected region, and I added a merge-field verification step to the pre-print checklist so the class of error can't reach a final check again."

The annotation:

  1. Remit established first. "What was actually mine to decide" is the understand your own level of responsibility descriptor, performed rather than claimed — and it's what makes "I decided" legitimate instead of grandiose.
  2. A self-imposed clock. Deciding by 2pm because collection was at 4 evidences timeliness — the descriptor candidates most often leave to implication.
  3. The close option, killed with evidence. The send-plus-correct option isn't strawmanned; it's genuinely cheaper, and it loses on a checked consequence (penalties a correction can't reliably prevent). That's analyse credible information, not gathering — weighing.
  4. Someone disagreed, and the decision held. The print coordinator gives the answer its even if unpopular descriptor — and the reasoning offered ("recoverable vs not recoverable") shows confidence rather than stubbornness.
  5. "Informed, not asked." Three words that relocate the entire behaviour from Version 1. The manager still appears — where a manager belongs in an HEO decision.
  6. The result proves the judgement. Zero penalty cases from the affected region tests the actual risk the decision was built on — plus a checklist fix so the decision never needs making again.

Calibrating either side of HEO

At EO, Version 1's shape — analyse, involve the right people, escalate cleanly — is close to correct. At SEO, Version 2 needs more: decisions whose consequences run across teams or sustained periods, challenge invited into the decision rather than just survived, and stakes that make the discomfort real at a senior table. The full grade ladder is in the Making Effective Decisions pillar.

HEO-specific mistakes on this behaviour

  1. The handover sentence. "...which I put to my manager, who decided." Restructure or choose different evidence — this single sentence caps more HEO decision answers than everything else combined.
  2. Options without a verdict. Listing three options proves analysis; the descriptor needs the choice and its because.
  3. No rejected alternative. If nothing credible was turned down, no decision was made — just a task completed.
  4. Universal agreement. The unpopular descriptor can't be ticked by a story where everyone nodded. Keep the disagree-er in.
  5. Slow-motion decisiveness. Weeks of deliberation on a time-sensitive call reads as the timeliness descriptor failing. Show the clock.
  6. Deciding above your remit. The inverse failure — claiming calls that were never yours invites the "why was that your decision?" probe with no good answer. Establish the delegation first, as Version 2 does.

If Making Effective Decisions is on your advert — and at HEO it almost always is — get the answer scored before the panel does it: the AI coach marks against the real HEO descriptors and tells you whose finger was on the button in your telling. Three sessions free; the HEO Complete Guide calibrates every behaviour to this grade.

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 Free

3 free practice questions · No card needed · Cancel anytime