CMI Level 5 and Level 7 EPA Practice
Assessor Q&A Practice
David Agyei · Shropshire Council · 18 June 2026
22 questions as a fresh-eyes assessor would ask them (A–Z within each section), drawn directly from your portfolio and coursework. Model answers are written in your voice. Press Play on any card to listen, or use Play All to run through the full set hands-free.
AM2: Project Presentation and Q&A
Questions an assessor would ask after watching your presentation, based on the proposal, ToR, cost avoidance model, and meeting records.
"You've presented a cost avoidance figure of £390,000. How confident are you in that number and what would it take for it to become real?"
The £390,000 is an illustrative proxy, not a forecast, and I want to be precise about that distinction. I used ADASS and PSSRU unit cost benchmarks applied against the volume and case-type data from SWANN to model a directionally credible estimate. The honest limitation is that those are national averages, and Shropshire's rural geography, elderly population profile, and above-average complexity mean local costs may diverge from the national mean in ways I cannot predict without council-specific data. What would make the figure real is the Phase 2 portal itself. Once referrals are tracked end-to-end, we can measure the cost of cases that went through early intervention against those that did not. At that point we move from proxy to actual. The £390,000 justifies the investment in building the measurement capability. It is not a guaranteed return, and I have labelled it as illustrative throughout the proposal precisely because I think presenting a proxy as a confirmed figure would be a credibility risk, not an asset. The strongest thing I can say about it is: it is directionally credible, it is transparently sourced, and the whole point of Phase 2 is to replace it with something real.
"The Terms of Reference list the strategic owner as TBC with a target confirmation date of 30 May. That date has passed. Who is accountable for this project?"
Fill in before Wednesday: confirm the name and date of the confirmed strategic owner, or the current escalation status if still unresolved.
The TBC in the ToR reflects a deliberate governance decision rather than an oversight. At the time of drafting, confirmation was pending a scheduled conversation. I documented it explicitly as a RAID risk with a target date of 30 May, rather than leaving it as an empty field, because the lesson from Phase 1 is that governance gaps managed quietly become blockers later. The strategic owner role in ToR Section 5 remains to be formally confirmed as of the assessment date. This is not an oversight; it was documented explicitly as a live RAID risk with a target confirmation date of 30 May, precisely because the lesson from Phase 1 is that governance gaps managed quietly become blockers. Lisa Middleton, as Commissioning Officer and chair of the SWANN partnership, holds the senior accountability for the programme. My role as Senior BA provides the governance design and project management function; the executive accountability for the programme outcome sits with the Commissioning Officer, and that is clear in the ToR. What I would say about the approach is that naming a gap formally and setting a target date is better governance than either filling it prematurely with the wrong name or pretending it does not exist. The senior accountability sits with Lisa Middleton as Commissioning Officer and chair of the SWANN partnership. My role is Senior Business Analyst providing project management for the SPoR, and that distinction matters: I hold the analytical and governance design responsibility, not the executive accountability for the programme outcome.
"At the 27 May partnership meeting, 31 referrals were confirmed with no SLA. What is happening to those families right now?"
Fill in before Wednesday: current count as of 18 June and the status of outstanding encrypted referrals.
That is the right question to ask and I want to be direct about it. I surfaced the 31 outstanding referrals explicitly at the 27 May partnership meeting rather than managing them operationally without visibility, because these are families who already sought help once and a second failure has both a human cost and a reputational one for the council. What I have since established is that the root cause was a technical blockage in the original mailbox setup. Incoming referrals were encrypted in a way that prevented Customer Services from accessing them. The fix was creating a dedicated Swan mailbox giving Jim and Chelsea the access needed to unencrypt and process referrals. Kate Hobbs worked through the outstanding backlog, specifically the encrypted emails for Shropshire Mental Health. As of 2 June 2026, 13 referrals remained outstanding for Shropshire Mental Health; the Live Well Shropshire referrals (missed since 17 May due to the mailbox crossover) had been resolved. By 10 June 2026, at the Phase 2 requirements workshop, it was confirmed that the 13 were not dependent on further action from Customer Services: the team had completed their referral role and Shropshire Mental Health were responding to residents. I will confirm the final count on 18 June before this assessment. There are no formal SLAs built into the system, which is itself a Phase 2 design requirement now on the record. A further operational issue surfaced in early June: a subset of referrals were being sent to SWANN providers that were not appropriate for the service, including care home residents and cases requiring complex mental health input beyond the service's skill level. Chelsea Pallen introduced a quality check to address this: before any referral is sent to a provider, advisors now check with Chelsea first. This is a direct operational improvement driven by the team in response to evidence from the ground. It is additional evidence that the Phase 2 referral form and provider access design must include clearer eligibility criteria so that screening happens at the point of referral, not after. The portal, once live, makes response times measurable and accountable. The interim period is a genuine gap and I have not pretended otherwise.
"You chose concurrent workstreams rather than running them in sequence. What problems did that create and how did you manage them?"
Concurrent workstreams created dependency risk that sequential delivery would not have produced. The most significant instance was that the data governance workstream needed to define mandatory referral data fields before the portal build workstream could finalise the form structure. When those two streams moved at different speeds, we had a period of rework on the form design. My response was to introduce a dependency check into the sprint retrospective cycle, which gave the team a consistent point to surface conflicts before they became blockers rather than after. I also introduced a plan-on-a-page document to give all stakeholders visibility of the concurrent priorities without having to track individual workstream details. If I were doing this again, I would map the cross-workstream dependencies more granularly at the start rather than managing them reactively. I still believe concurrent was the right call given the financial pressure on the council and the cost of delay, but the dependency mapping is a lesson I would apply earlier and more explicitly. That is the kind of trade-off I think distinguishes a considered project decision from simply choosing the faster option.
"Walk me through your theory of change. How exactly does a digital referral portal translate into financial savings for Shropshire Council?"
The theory of change has three linked steps and it is important to be clear about what is evidenced now versus what depends on future delivery. Step one: the portal creates a single tracked entry point for referrals. For the first time the partnership can see who is referring whom, at what point in a family's journey, and whether providers are responding within any agreed timeframe. That step is a governance and infrastructure change, and I can evidence that Phase 2 is designed to deliver it. Step two: that visibility enables earlier identification of families who need support before their needs escalate to statutory intervention, specifically care proceedings or emergency placements, which carry significantly higher unit costs as evidenced by the ADASS and PSSRU benchmarks I applied. Step three: the reduction in high-cost escalations generates the cost avoidance. The critical assumption in that chain is that early identification actually changes outcomes, and that is supported by the evidence base underpinning SWANN as a model. Where I want to be honest with you is that I cannot yet evidence step three. That requires the portal to be live and a longitudinal dataset to build. What I can evidence is that steps one and two are structurally in place and that the design is grounded in a credible theory rather than an aspiration.
"You chose an Agile sprint approach. Public sector governance does not work in two-week sprints. How did you actually make that work?"
Agile, as I applied it, was not pure Scrum and I want to be clear about that distinction. The reason I chose an Agile approach in the first place is that the requirements were genuinely emergent: the team could not specify the data governance model or the referral form fields until we had begun mapping the existing process and involving the providers. A waterfall approach would have locked in the wrong solution before we had enough information to design the right one. What I adapted was the interface with governance. Sprint velocity and retrospectives were internal team rhythms. What I presented to the SWANN partnership and to governance was milestone language they recognised: plan-on-a-page, key priorities, workstream status. So the delivery method was Agile; the reporting language was milestone-based. The limitation I would acknowledge honestly is that this hybrid approach diluted some of the benefits of Agile, particularly the ability to pivot quickly, because I was still bound by the expectations of a fixed project boundary and approval timelines. That is an inherent tension in applying Agile to public sector transformation and I do not think there is a clean answer to it, only a pragmatic adaptation.
"Tell me about a specific moment in this project where a stakeholder questioned your approach and how you responded."
A specific example was in early June when Kate Hobbs, the Senior CRM Applications Officer, emailed to ask whether a planned meeting was actually necessary. Her team was under significant pressure and she was rightfully questioning the value of a session before the requirements workshop had taken place. My instinct was not to defend the meeting, it was to respond to her underlying concern about workload and value. I replied with a proposed agenda that was explicitly 30 minutes maximum and tied directly to four outcomes: closing outstanding action points from Lisa's notes, agreeing the interim referral process, addressing the encryption issue, and defining what we needed to take into the requirements workshop so we did not lose momentum. I named what the session was for and gave her a clear basis to judge whether it was worth her time. She attended and we resolved three outstanding issues that had been blocking progress. The learning I take from that is that a stakeholder who questions your meeting is not being obstructive. They are telling you that the value is not yet visible to them. The professional response is to make the value visible, not to defend your schedule. That is a lesson in stakeholder management that I think applies well beyond this project.
"What is the single thing you would do differently if you were starting Phase 2 again from scratch?"
I would negotiate dedicated project management resource at the outset rather than absorbing that function myself alongside the analytical, governance design, and stakeholder leadership responsibilities. In practice, I was managing upwards to the SWANN partnership, outwards to providers including British Red Cross, Shropshire Mental Health Support, Community Resource, and Live Well Shropshire, inwards to the CRM team, and also doing the financial modelling, the data governance design, and the requirements framing. That breadth meant I was in the right conversations but sometimes not going as deep as the complexity warranted. A dedicated project manager would have owned the logistics, the meeting scheduling, and the action tracking, freeing me to do the strategic analysis and relationship work at a higher quality. The broader lesson I take is that the Senior BA and PM roles in a project of this complexity are genuinely distinct functions and conflating them is a risk to both. I did not name that gap early enough. I am naming it now as a learning because I think it is the most honest answer to your question.
"Pippa Murphy's testimony notes a developmental area around strategic horizon scanning. Can you give me a concrete example of how your practice has changed as a result?"
Pippa's observation was specific and I took it seriously: she noted that I was strong at operational analysis and evidence-based influencing within the current project boundary, but that I sometimes needed prompting to look at the wider system context and the longer-term strategic implications of what I was doing. The concrete change in my practice is that I now begin any significant piece of analysis by asking what this means in five years rather than five months before I go into the detail. The most visible application of that shift is in how I framed the SWANN Phase 2 financial case. My initial instinct was to present it as a project cost with a corresponding benefit. After Pippa's feedback, I reframed it as the cost of building a measurement capability that Shropshire Council will need regardless of the specific intervention model. That shift from what does this project cost to what does this capability enable is, I believe, the strategic move she was pointing to. I would not tell you the development is complete. Horizon scanning is a practice rather than a destination, and Pippa's developmental note remains something I am actively working on. What has changed is that it is now a deliberate part of how I approach a problem rather than something I need to be prompted towards.
"You used national benchmarks from ADASS and PSSRU. What is the specific risk of applying national averages to a council in financial special measures with its own particular pressures?"
The honest answer is that national averages smooth out variation in ways that matter for Shropshire specifically. Shropshire has a rural geography with dispersed settlement, an above-average elderly population, and a case complexity profile that differs from the national mean in ways that are difficult to quantify without local data. Those factors could push unit costs in either direction relative to the national benchmark. The risk is therefore that the £390,000 estimate either overstates the saving if Shropshire's patterns are less favourable than the national baseline, or understates it if the concentration of complexity means the escalation differential is actually higher here. I cannot tell you which way it goes without the data. That is precisely the argument for building the infrastructure first. The proxy model gives a directionally credible case for investment, and I would not accept the suggestion that a proxy is not worth building. It is the only credible basis for investment in the absence of local data, and the whole design of Phase 2 is to generate that local data so we can replace the proxy with an actual. What I can say with confidence is that the methodology is transparent, the sourcing is published, and I have not presented it as something more certain than it is.
AM1: Professional Discussion
Questions probing your KSB evidence across the portfolio. Assessor has read all witness testimonies and the Evidence Locator Document.
"Tell me about a time you influenced a significant outcome without formal authority. What made it work and what would you do differently?"
The clearest example is the As-Is Meetings Mapping project within the Families First Partnership programme. I had no line authority over Director Shaw, the Assistant Director, or the Programme Manager. My only lever was the quality and credibility of the analysis. I engaged over 73 members of staff across the Children's Services system to generate a dataset that was difficult to ignore: between £770,000 and £851,000 in annual meeting costs, which I translated into a figure of 12.5 to 14 full-time social worker equivalents to make the human cost tangible rather than just financial. The outcome was that Director Shaw voluntarily committed to reviewing his own meeting attendance, the Health and Wellbeing Board adopted the methodology cross-organisationally, and Charlotte Saywell described it in her testimony as a great piece of work. What made it work was the data doing the influencing rather than my positional authority, because I had none. What I would do differently is build the influencing strategy more explicitly from the start rather than relying on data quality alone. The analysis was strong enough to carry the argument here, but I was somewhat fortunate in that. In a more politically contested context, I would need to be more deliberate about identifying who needs to be brought along before the data lands, not after.
"Shanda Reid has provided a witness testimony about your coaching practice. Describe your coaching approach and tell me what evidence you have that it actually made a difference to people."
My coaching practice is grounded in the GROW model and a fundamentally non-directive, person-centred approach. I have been a voluntary coach with the West Midlands Coaching Pool for over five years, working with 15 coachees across that period. I hold a Level 5 coaching qualification, and my CPD has included systemic coaching, wellbeing coaching, and coaching for career transitions. Shanda Reid's testimony is valuable to me precisely because she is independent of Shropshire Council and observed my practice directly. She can speak to my competence in a way that an internal colleague cannot. The evidence of impact that I find most significant is specific: two of my coachees returned to substantive work after periods of burnout, and six received promotions or significant career moves during or following our coaching relationship. I want to be honest about what I can and cannot claim from that evidence. The causal chain between coaching and career outcome cannot be proven the way a clinical trial would prove it. What I can say is that both coachees in the burnout cases explicitly identified our coaching conversations as the turning point in their decisions to return. That is the strongest evidence I have and I think it is meaningful. The limitation I acknowledge in my own practice is that the GROW model works best when the coachee has sufficient readiness and self-awareness to use the non-directive space well. In the burnout cases I had to shift to a more scaffolded and directive approach, which required me to consciously override my default style. That flexibility is what I consider the most important learning of my coaching practice so far.
"How do you approach stakeholder management when you are working across organisational boundaries with no shared line management?"
I use Mendelow's Power/Interest Matrix as an analytical starting point, but in practice I have found the more useful tool is understanding the nature of the engagement rather than just its location on the grid. In a multi-agency partnership like SWANN, involving British Red Cross, Shropshire Mental Health Support, Community Resource, Live Well Shropshire, and the ICB alongside the council, the resistance I encounter is rarely active opposition. It is more often passive non-engagement, which is actually harder to manage because it is invisible until something fails. My approach is to find the shared language that makes non-engagement costly. In the SWANN context, that shared language is financial: the £121 million emergency is a burning platform every partner organisation understands because many of them also face funding pressure. Beyond the shared language, I invest in relationships rather than just governance structures. Governance creates the space for partnership; relationships determine what happens in that space. The SWANN partnership meetings are the formal mechanism. The conversations with Katie Done on digital content, with Jim Ford on customer services, and with Kate Hobbs on CRM are where the actual intelligence about what is and is not working comes from. The limitation I would name is that informal relationship networks reflect existing power structures, and I have to be deliberate about including voices that are not naturally in that network.
"What does the evidence in your portfolio, taken as a whole, tell us about your leadership approach?"
I think the portfolio makes two things visible. The first is that my leadership operates primarily through analytical credibility and relationship investment rather than through positional authority. That is not simply a circumstance of my role; it is a deliberate choice about where influence is most durable. The As-Is Meetings Mapping, the SWANN Phase 2 design, and the coaching practice are all examples of the same underlying approach: use evidence and relationship to create the conditions for change, rather than relying on a mandate that may not exist or may not hold. The second thing the portfolio shows is the development from operational to strategic thinking that Steve Humphrey described in his testimony, specifically that shift from focusing on the task in front of me to asking what system this task sits within and what it means beyond the immediate project. The anti-racism forum I co-facilitated is evidence of a different dimension of leadership: public, values-based, and carrying professional risk. I think that matters as evidence of behaviour under pressure, not just competence under favourable conditions. What the portfolio does not show, and I want to be honest about this, is deep experience of budget accountability at an organisational level. My financial capability is strong at the analytical end. The direct accountability as budget holder is something I am working to develop in my next role.
"What evidence do you have that you have developed as a leader and manager over the course of this programme? What has actually changed in your practice?"
The most credible evidence of development comes from people who knew me before the programme and have observed change directly. Steve Humphrey described my development specifically as moving from an operational to a strategic viewpoint, which maps to the capability I was deliberately working on and is externally validated. That shift is visible in practice: I now begin analysis with the system question before the task question. Pippa Murphy's developmental note about strategic horizon scanning is also evidence of development in a different way: it shows the programme has created genuine self-awareness about a gap rather than just confirming existing strengths. The CPD record shows deliberate investment in systemic coaching, wellbeing, and career transitions, specifically because I identified gaps in my individual coaching practice and chose to address them. The anti-racism forum co-facilitation is evidence of a willingness to lead publicly on values that carry personal and professional risk, which I think is different in kind from technical skill development. What I want to be honest about is that development of this kind is not linear. The programme has not resolved every gap. My work on strategic horizon scanning is ongoing, and the financial accountability dimension is something I am actively working towards. I think naming those gaps is itself evidence of the kind of self-awareness that the programme is designed to develop.
"Describe a time when you had to manage significant operational complexity. What was your approach and what did you learn?"
The SWANN Phase 2 project is the clearest example, specifically the period in late May and early June 2026 when I was managing concurrent technical issues in the existing system alongside the Phase 2 design work. The referral feedback loop had broken down due to a mailbox encryption issue: referrals were arriving but customer services could not access them because the original shared mailbox had not been configured to allow Jim and Chelsea to unencrypt incoming emails. At the same time, I was chairing requirements discussions with providers and managing the planning for the requirements workshop. My approach was to triage the operational issues explicitly rather than allowing them to consume the Phase 2 design work. I created a structured agenda that separated what needed to happen in the next 48 hours from what needed to happen in the next six weeks, and I communicated that distinction clearly to the team including Kate Hobbs and Lisa Middleton. The learning I take from that period is that in a project where Phase 1 issues are still active and Phase 2 is being designed simultaneously, the risk of context-switching without a clear triage framework is very high. The plan-on-a-page document I created was a direct response to that risk: a single place where anyone could see what the concurrent priorities were without having to hold all the context in their head. Lisa Middleton, the Commissioning Officer, responded to that document by noting that the governance framework I had put in place represented an important step in strengthening arrangements that had not previously been formally established. That external validation matters to me: it confirms that what I produced was not just useful internally but recognised as filling a genuine gap in the partnership's governance infrastructure.
"You have seven witness testimonies. What do they tell us, taken together, that none of them tells us individually?"
Taken individually, each testimony speaks to a specific context: Charlotte Saywell on analytical capability and upward influencing, Shanda Reid on coaching competence from an independent vantage point, Emily Goodhead and Claire Allen on operational management and people development, Sunanda Bailey and Leanne Morrissey on stakeholder engagement and communication, and Pippa Murphy on strategic development with the developmental note I have spoken about. Taken together, they do something that no single testimony can: they triangulate across different relationships, different organisational contexts, and different time periods. What that triangulation shows is that the capabilities are consistent rather than situation-specific. Charlotte Saywell and Shanda Reid do not know each other and are not in the same organisation, yet they are independently describing the same fundamental characteristic, which is that my practice creates conditions for change in others rather than delivering change through authority. That is a consistent pattern, not a single performance. The testimony that adds the most to the set, in my view, is Pippa Murphy's, specifically because it is the most honest one. The developmental note about strategic horizon scanning means the portfolio is not a set of endorsements. It is a set of observations from people who have actually worked with me, and that includes the gaps as well as the strengths. I think that makes it more credible, not less.
"Describe a time when your approach to a professional situation changed as a direct result of something you had learned, either from the programme or from experience."
The most significant change in practice I can point to is in my coaching work, specifically the shift I made when working with coachees in burnout. My default approach is non-directive and GROW-model based, which assumes the coachee has the capacity and self-awareness to use an open question well. In the two burnout cases in my coaching pool work, I discovered that that assumption did not hold. A coachee in burnout does not always have the cognitive or emotional resource to respond productively to an open question about their goals. Applying my default style would have been technically correct and practically counterproductive. What I changed was my entry point. I moved to a more scaffolded and directive approach in the early stages, offering frameworks and structure rather than questions and space, and then progressively stepping back as the coachee's capacity returned. That required me to consciously override a habit I had built over five years of practice, which is harder than learning a new skill. The learning that drove the change was partly from my CPD in wellbeing coaching, which gave me the theoretical framework for why burnout affects coaching receptivity, and partly from the experience of watching my approach not work and having to adapt in real time. I think the willingness to notice that something is not working and change course, rather than persist with a method that is not serving the person in front of you, is the most important thing a coach or a leader can do.
Curveball Questions
The questions designed to probe contradictions, gaps, or test whether you can hold your position under pressure. These are the ones that separate Distinction from Merit.
"Phase 1 of SWANN failed. You were not part of Phase 1, but you are now leading Phase 2. Why should we believe Phase 2 will be different?"
That is a fair challenge and I want to take it seriously rather than defend against it. Phase 1 failed for a specific reason: it attempted to build a technology solution before the governance and data infrastructure were in place to support it. The portal was built but the data did not flow into it because the referral pathways were not defined, the accountability for data entry had not been assigned, and the cross-agency agreement about what constituted a SWANN referral had not been settled. The Phase 2 design addresses those failures directly: the first workstream is data governance, not portal build. We do not start the technology until the governance is in place. That is a materially different design principle. What I also want to be honest about is that the challenge Phase 1 experienced has not entirely gone away. We are still navigating SLA definition, data sharing agreements across providers, and the absence of formal response time commitments. Those are live risks in the RAID log, not closed items. The honest answer to your question is that I cannot guarantee Phase 2 will succeed. No project that depends on multi-agency behaviour change in a financially pressured system comes with a guarantee. What I can say is that the design of Phase 2 is explicitly informed by the failure analysis of Phase 1, and I have named the residual risks publicly rather than managing them quietly. That is a materially different starting point and I believe it gives Phase 2 a better chance of delivering, without being able to promise it will. One thing I want to name proactively: the Lessons Learned Log in the project tracker was not formally populated during the EPA window. That reflects the pace of delivery, not an absence of learning. The 23 June meeting with Lisa Middleton is the right moment to formalise those lessons with the full partnership rather than document them unilaterally. I would flag this myself before an assessor raises it.
"Your project is still in progress. How can you evidence outcomes and impact when the outcomes have not actually happened yet?"
This is a genuine tension in my portfolio and I want to address it directly rather than work around it. My response has two parts. The first is that the CMI framework asks for evidence of competence, not evidence of project completion. The quality of the analysis, the stakeholder management decisions, the governance design, and the project approach are all independently assessable right now, regardless of whether the portal ever goes live. A well-constructed business case with a credible financial model is evidence of analytical competence even if the project is later cancelled. The second part is that there are interim outcomes already evidenced that are not prospective. The As-Is Meetings Mapping is a completed piece of work that produced a concrete output influencing real organisational behaviour: Director Shaw's voluntary commitment to reviewing his meeting attendance and the Health and Wellbeing Board's cross-organisational adoption of the methodology. Those have happened. The coaching outcomes, two people returning from burnout and six career progressions, have happened. The professional discussion discussions I led, the partnership I built with the ICB commissioning lead and the voluntary sector providers: those relationships exist. What has not yet happened is the Phase 2 portal going live and generating the longitudinal data that would confirm the cost avoidance model. I am clear about that distinction and I think being clear about it is itself evidence of the kind of analytical rigour the CMI standard is looking for.
"You mention Director Shaw committed to reviewing his meeting attendance after your analysis. But did he actually change his behaviour, or did he just say he would?"
That is an important evidential distinction and I should be precise about it. The evidence I have is that Director Shaw made a verbal commitment in a documented meeting, which Charlotte Saywell captured in the FFP Comms Update. What I do not have is a longitudinal dataset tracking his meeting attendance before and after that commitment. So the honest answer is that I have evidence of a stated intention to change behaviour, documented by a third party, not confirmed evidence of sustained behavioural change over time. I want to acknowledge that gap rather than overstate what the evidence shows. What I would say in support of the significance of that commitment is that a Director voluntarily, publicly, and on the record committing to reviewing his own attendance is in itself meaningful. It is not the same as an informal conversation or a polite acknowledgement. It reflects a shift in how the data was being received, from interesting to actionable. And the HWBB adopting the methodology cross-organisationally is a structural outcome that goes beyond the Director's individual commitment. But on the specific question of sustained behavioural change: I cannot take the evidence further than the documented commitment. I think it is important to say so, and I think an assessor asking me to be precise about the strength of my evidence is exactly the right challenge to make.
"Which KSB area in your portfolio are you least confident about and why?"
Financial management at the budget accountability level. My financial capability is strong at the analytical end: the proxy costing methodology, the options appraisal, the cost-benefit framing, the translation of financial data into language that senior stakeholders can act on. What is less developed in my practice is the experience of holding a substantial budget as an accountable budget holder in my own right: setting it, monitoring against it, managing variances, and reporting on it to a finance committee. My exposure to financial management has been through the project financial case and through analytical support to budget holders, rather than through direct accountability for a budget. I have named this in my CPD planning and it is something I am actively working to address as I move towards more senior roles. I think it is more credible to name a genuine gap honestly than to claim strength across every dimension. No senior manager at this stage of their development has equal depth across all KSBs, and I would be doing the CMI framework a disservice if I presented an evidence set that pretended otherwise. The gap is real, it is named, and I have a plan for developing it. That, I think, is what a self-aware and professionally responsible manager looks like.