Behaviours
Developing Self and Others: Civil Service Examples That Score
Published
Developing Self and Others is the behaviour candidates prepare least and misread most. The standard answer is an earnest tour of the candidate's own development — courses completed, a qualification in progress, feedback sought and acted on. All true, all worthy, and from HEO upward it caps around a 3, because the marks aren't where the candidate is looking. Read the descriptors at HEO/SEO: identify capability gaps for yourself and your team, coach, mentor and develop other colleagues, support succession planning, use different personal needs to develop others. The behaviour's centre of gravity is the second half of its name. Your own learning is the warm-up act; what the panel is waiting for is evidence that someone else can do something today because of you.
What panels are actually scoring
A capability gap, diagnosed. Not "I noticed he was struggling" — what specifically couldn't be done, by whom, and how you knew. The diagnosis is where judgement shows: the difference between "she needed a confidence boost" and "she could run the analysis but couldn't defend it in front of stakeholders, so the gap was the meeting, not the maths."
An intervention you chose, with a because. Coaching, structured exposure, pairing, delegation with support — the mark is in matching the method to the gap. Sending someone on a course is the intervention that requires no thought; panels hear it as such.
Capability transferred, not dependence created. The end state that scores is the other person doing the thing without you. If your story ends with them still coming to you, you've built a helpdesk, not capability.
Your own development with a purpose. Own-learning evidence lifts an answer when it's targeted — a gap identified against what your role or team needed next, closed deliberately, applied visibly. A list of courses attended is CV filler spoken aloud.
The questions panels actually ask
- "Tell me about a time you helped develop a colleague or team member."
- "How have you identified and addressed a skills gap in your team?"
- "Describe a time you coached or mentored someone."
- "Tell me about a piece of feedback that changed how you work." (The own-development variant — answer with the change, not the feedback.)
- "How do you approach your own professional development?" (Weakest question in the set — still answer with purpose and application, not a course list.)
Probing follow-ups: "How did you know that was the gap?", "Why that approach rather than training?", "Can they do it without you now?" — diagnosis, method-match, transfer. The three marks above, hunted in order.
Fail vs pass: the same colleague at 3 and at 6
A realistic HEO-level answer. Same events in both versions.
FailVersion 1 — scores around 3/7
"A colleague in my team returned from eighteen months of extended leave to find we'd moved to a completely new case management system while she was away, and she was really struggling — everything she'd been quick at now took her three times as long, and I could see it was knocking her confidence. I take developing others seriously, so I made time to support her. I sat with her whenever she got stuck, talked her through the parts of the system she found confusing, and reassured her that everyone had found the transition difficult at first. I also shared the user guides and pointed her to the training modules on the intranet. Over the following couple of months she gradually got back up to speed, and she thanked me for being so patient with her. Separately, I keep my own development up to date — I completed a project management qualification last year and I regularly attend our profession's lunch-and-learn sessions."
Read it as a panel member. Kind, genuine, and almost unscoreable. "Sat with her whenever she got stuck" is reactive help with no structure — and it quietly means the colleague's recovery ran on the candidate's availability. There's no diagnosis (which parts of the system? why those?), no chosen method (helping, guides and intranet links are the default toolkit, unexamined), and the result is "gradually got back up to speed" — time passing, with the candidate nearby. Then the own-development coda: a qualification and lunch-and-learns, connected to nothing. The panel hears a supportive colleague, which is not the behaviour being scored. A 3.
PassVersion 2 — the same colleague, around 6/7
"A colleague returned from eighteen months of leave to find we'd replaced the case management system while she was away. Rather than just helping when she got stuck, I spent one afternoon watching her work a normal caseload, because I wanted to know where the time was actually going. It wasn't where either of us assumed — she'd taught herself the basic navigation fine, but the new system automated three decisions the old one had left to caseworkers, and she was manually re-checking each one because she didn't trust logic she couldn't see. That reframed the gap: not system training, but understanding what the automation did and when to override it — which the intranet modules didn't cover at all. So I structured three short sessions around exactly that, each one working real cases from her own queue, and after each session she kept a one-line log of every automated decision she'd accepted without re-checking, so she could see her own trust building in numbers. I deliberately stopped sitting with her after the third session — the point was her judgement, not my presence — but we kept a weekly fifteen-minute check-in until she called it unnecessary, which took five weeks. Her case times came back to her pre-leave level within two months, and the diagnosis outlived her: I realised the automation-trust gap would hit every returner and every new starter, so I wrote it up as a one-page 'what the system decides for you' explainer, which our team now issues on day one — the team lead credited it with cutting the settling-in period for the two starters since. It also changed my own development plan: watching how much the diagnosis mattered, I asked to shadow our learning and development business partner on a training needs analysis, and I've since run one for my own team's data skills."
What changed:
- Diagnosis before intervention. The afternoon of observation produces the story's hinge: the gap isn't what it looked like. Everything scoreable downstream flows from that one deliberate act.
- Method matched to gap, with a because. Real cases from her own queue, sessions built around automation logic, a self-logged trust measure — each choice reasoned, none of it the default toolkit.
- Dependence deliberately ended. "I stopped sitting with her after the third session — the point was her judgement" is the transfer mark, stated in one line. Version 1's patience builds reliance; Version 2 engineers her independence.
- The individual fix becomes team capability. The day-one explainer moves the evidence from developing a colleague to developing the organisation — descriptor language at HEO/SEO, and the move that separates a 5 from a 6.
- Own development, earned by the story. The shadowing request grows out of the events and gets applied ("I've since run one"). Compare Version 1's orphaned qualification.
- Results with numbers and a witness. Pre-leave case times in two months; a team lead crediting the explainer. Capability change, evidenced.
How Developing Self and Others changes by grade
- EO: identifying gaps in your own and the team's skills, meeting development objectives, sharing knowledge with colleagues. A well-structured version of teaching a colleague something scores strongly — the "others" weight is lighter here. Calibration in the EO guide.
- HEO: coaching and mentoring appear explicitly, alongside capability gaps for you and your team and support for succession planning. Version 2 above is pitched here. See the HEO guide.
- SEO: same descriptor band, calibrated up — development that serves delivery of future work, inclusive development across different personal needs, and reflection that improves the team's performance, not just yours. The SEO guide and SEO interview hub cover the shift.
- G7: the descriptors move to conditions and culture — development opportunities available to all regardless of background, teams learning from each other, role-modelled continuous learning. Coaching one person brilliantly is HEO/SEO evidence at G7; the panel wants capability built across a team or function. Full calibration in the G7 guide.
Common mistakes that cap your score
- The course list. Your own training, enumerated. From HEO up this is the fastest route to a 3 in the whole framework.
- Kindness as evidence. Patience, reassurance and being available are virtues, not development. The panel scores capability change.
- No diagnosis. Helping with the presenting problem rather than finding the actual gap. The observation step in Version 2 is one afternoon — and worth two marks.
- Dependence dressed as support. "They still come to me with questions" is the opposite of the transfer evidence the descriptors describe.
- Development that dies with the individual. If the gap you found exists across the team, show the systemic fix — that's where HEO becomes SEO evidence.
- Feedback theatre. "I always seek feedback" scores nothing. One piece of feedback, one changed behaviour, one visible result scores.
The events in most people's development stories are already good enough — the diagnosis, the transfer moment and the team-level fix are usually in there, untold. If you want to see where your version lands on the 1–7 scale before a panel decides for you, run it through a scored mock: the AI coach marks against the same grade descriptors, three sessions free, with the full 250+ question bank on membership.
Common questions
It covers continuous learning and development — for you, your colleagues and the organisation. From HEO up the weight sits firmly on developing others: identifying capability gaps, coaching, mentoring and building team capability.
No. Informal coaching, buddying a new starter, teaching a colleague a skill, structuring someone's exposure to new work — panels score the development you caused, not the label on the arrangement.
Partly. Own-development evidence works as a strand — a gap you identified and closed with a purpose — but from HEO upward an answer that is only about you caps around a 3–4. The marks are in developing others.
Weak on its own. Booking a course is administration. The evidence is in diagnosing the gap, choosing the intervention, and what changed in someone's capability afterwards.
Show the person doing independently what they previously couldn't — a task handed over, a responsibility they now own, an error rate that fell. Capability change is the result panels can score.
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 Free3 free practice questions · No card needed · Cancel anytime