Skip to content
Back to work

Selected strategic work · Concept / Prototype

KSA + EAAS Throughline

A Cross Functional Growth Architecture

Strategic presentation + pilot concept · June 2026

One shared growth story connecting how people develop capability with how organizations enable that capability to produce stronger action, service, trust, and impact.

Purpose
Cross functional strategic alignment
My Role
Framework integration, strategy, presentation, and pilot design
Format
Executive presentation + pilot concept

The strategic problem

Growth was happening across multiple functions, but there was no common language connecting the work.

  • Professional Development

    develops capability

  • Leadership

    sets expectations

  • Communications

    reinforces meaning

  • Marketing

    shapes external narrative

  • Service

    turns capability into experience

  • Community Impact

    shows whether the promise is being realized

The throughline

KSA

How people grow

  1. Information
  2. Knowledge
  3. Skill
  4. Judgment
  5. Aptitude
  6. Alignment
  7. Growth

EAAS

How the organization sustains that growth

  1. Access
  2. Practice
  3. Support
  4. Feedback
  5. Reinforcement
  6. Enablement

Organizational expression

What that capability produces

  1. Action
  2. Service
  3. Experience
  4. Trust
  5. Impact

What the deck proposed

  • Shared Language

    Give participating functions a common vocabulary for discussing growth and capability.

  • Cross Functional Throughline

    Connect internal learning, leadership behavior, communications, service, and public impact.

  • Stakeholder Conversation

    Use structured questions to identify where the throughline currently breaks.

  • Pilot

    Test whether multiple functions can use the same growth story to plan and communicate improvement.

Strategic presentation concept

Structural reconstruction

  • Cover

    KSA + EAAS Throughline

    Strategic presentation · pilot concept

    Status
    Concept / prototype
    Format
    Strategic presentation and pilot concept
    Design role
    Throughline, presentation, pilot design, stakeholder guidance

    The presentation cover. It proposes one shared language across professional development, communications, marketing, leadership, and service quality.

  • Connected growth story

    The throughline view: how capability work, action, alignment, and public trust are described as one connected story.

  • Pilot

    Pilot concept structure

    • Shared languageOne vocabulary the participating functions all agree to use.
    • Stakeholder questionsDiscussion prompts that surface where the story currently breaks.
    • Meeting guidanceHow the cross-functional conversation is run and recorded.
    • Proposed outcomeDemonstrate that training, communications, and marketing can carry one growth story.

    Selected interior pages describing the proposed cross-functional pilot.

  • Detail

    Why a throughline

    “Improvement work that is described three different ways never accumulates into anything a leader can see.”
    • Concept / prototype
    • Cross-functional strategy
    • No outcomes claimed

    Close-up of the argument the deck is built to make.

These views are structural reconstructions of the presentation concept, not images of the source slides.

What I contributed

I originated the throughline, connected KSA and EAAS into one strategic narrative, authored the presentation, designed the proposed pilot, and developed the stakeholder discussion structure.

  • Capability Architecture
  • Cross Functional Strategy
  • Executive Communication
  • Organizational Enablement
  • Framework Development
Read the KSA Flow case study

Authenticated from the original presentation source created June 1, 2026. The source credit has been normalized to Joel Birch for public presentation. Selected details have been anonymized to protect organizational confidentiality. Additional materials may be reviewed during a portfolio conversation.

Contact

Want the reasoning behind this work?

Every sample here sits inside a diagnosis. I am happy to walk through the problem it was built to solve.