A federal agency’s leadership development, rebuilt from the framework up.
A leadership development framework scaled to a federal health agency of 6,700 employees, designed to outlast any single program and to give the organization a measurable way to know whether it is producing leaders.
Engagement led by Bryan Miles prior to establishing MaestroVox Advisors.
- Leadership development framework built for 6,700 employees
- Competency architecture spanning GS-13 through SES
- LTEM-grounded impact measurement established
- Workforce Resilience office being built to own the framework
The context.
A large federal health agency with more than 6,700 employees and a leadership tier that had grown faster than the infrastructure to develop it. The agency had training. It had classes. What it didn’t have was a coherent leadership development framework: a connected architecture that built skill deliberately across levels, measured what actually changed, and gave the organization a way to know whether its investment in developing leaders was producing leaders worth the investment.
What existed was a collection of disconnected programs, each designed in isolation, none of them building toward a shared picture of what leadership capability at this agency was supposed to look like. Leaders could attend. Check the box. Leave largely unchanged.
The ask was to fix that. The real work turned out to be building the conditions that make fixing it possible.
What the diagnostic found.
Three gaps underneath the presenting problem.
The first was architectural. There was no framework defining what leadership looked like at different levels: no shared language, no developmental progression, no way to distinguish between a GS-13 team lead and an SES executive in terms of what each needed to build and why. Programs existed in a vacuum because there was nothing to connect them to.
The second was methodological. The existing programs were content-delivery vehicles. Sit in a room, receive information, leave. The research on adult development is unambiguous about what that produces: familiarity and vocabulary, not skill. The agency was spending significant resources on development that couldn’t produce the outcome it was designed for, and had no mechanism to know it.
The third was measurement. There was no way to track whether anything was changing. Satisfaction surveys at the end of a class are not evidence of development. They are evidence that people appreciated the class. Without behavioral measurement, the agency couldn’t distinguish between programs that worked and programs that felt good.
The work.
The engagement ran across three interconnected workstreams over multiple years.
Framework design
Bryan designed a leadership development framework scaled to an organization of 6,700: defining leadership competencies and developmental expectations from front-line supervisors through senior career executives. The framework gave the agency a shared architecture: what skill looks like at each level, what the developmental progression from one level to the next requires, and how individual programs connect to the larger picture. For the first time, a manager attending a program could see where it fit in their development and what came next.
Program development and delivery
From the framework, Bryan designed and delivered a curriculum of skill-building programs: classes, tools, and structured practice experiences built around the competency architecture. The design principle throughout was deliberate practice over content delivery. Participants doing something, not watching something. Programs were built around real decisions, real challenges, and real work already in front of the leaders attending them. Micro-skill development, structured reflection, and application in actual job conditions were the design standards, not engagement scores.
Impact measurement architecture
The third workstream was the one most organizations skip. Bryan built an L&D impact measurement plan grounded in the Learning-Transfer Evaluation Model: a research-based evaluation framework designed to measure behavioral change and learning transfer, not just participant satisfaction. LTEM distinguishes between what learners remember, what they can demonstrate, and what they actually do differently on the job, a distinction most federal training programs have never made explicit. The measurement architecture established assessment touchpoints before and after development experiences, tracked behavioral indicators at multiple intervals post-program, and gave the agency a data-grounded basis for evaluating which programs were producing real change. The next evolution of the measurement work, planned to incorporate Lectica’s Leadership Decision Making Assessment for leaders engaged in sustained coaching, is currently in development.
What changed.
At the program level: a connected curriculum where disconnected classes had existed before. Leaders at every level had a clear developmental pathway, programs designed to build skill rather than deliver content, and the tools to practice new behavior inside their actual work.
At the organizational level: a measurement framework grounded in LTEM that gave the agency a rigorous way to distinguish between development that produced behavioral change and development that produced good feedback scores. For a federal agency spending public funds on workforce development, that distinction carries real accountability weight.
At the leadership level: evidence of behavioral change in the cohorts who completed sustained development experiences alongside the program work. Leaders who entered unable to articulate their own developmental edge left with growth plans, skill-building structures, and the self-observation capacity to know when they were practicing and when they were defaulting.
What held.
The framework is designed to outlast any individual program or external engagement. That was the design intent from the start: not to deliver development, but to build the agency’s internal capacity to sustain and extend it. The work sits inside the agency’s Workforce Resilience office, which is being built out to own, maintain, and evolve the framework over time. Bryan continues to work alongside that office as the capability is established, not as the permanent solution, but as the partner helping the organization become its own solution.
That’s the principle that runs through every MaestroVox engagement. The goal is never to be needed forever. It’s to leave something behind that holds.
If your development investment isn’t producing what you can point to,
that’s where we start.
Most engagements start with a 30-minute call. We’ll listen, ask a few sharp questions, and be honest about whether we’re the right partner. If we are, we’ll propose a path. If we’re not, we’ll point you toward someone who is.