The work, in nine pillars

How the work goes

I start by mapping how work moves today, not how the policy says it does: interviews with the people closest to it, a read of what already exists, and a current-state map you can point at in a room. Then we design the fix together, in the open, and I stay through the part where people start using it.

What you keep

• A current-state map of how work moves today
• An operating model with decision rights named by stage
• A RACI your team ratified, not one I handed you
• The rollout plan, and the language to explain it

How the work goes

I look at the whole machine rather than one course: how learning gets requested, sized, built, launched, and measured. Then I build the operating system underneath it, so your team stops improvising and starts compounding.

What you keep

• An intake-to-launch process with visible stages
• Quality gates and a reusable design standard
• A measurement approach leadership will believe
• Templates so the next program starts halfway built

How the work goes

I treat adoption as the finish line, not launch day. That means communications, enablement, decision logs, and reinforcement built into the plan from the start, plus honest coaching for sponsors about what visible support actually requires of them.

What you keep

• A change plan sequenced to real capacity
• Communications and enablement materials
• A decision log that survives the transition
• Reinforcement through the first weeks of real use

How the work goes

I design the session before I run it: what decision it exists to make, who must be in the room, and what has to be true for people to speak honestly. In English, Spanish, or both, from small leadership teams to rooms of a hundred or more.

What you keep

• A designed agenda with the decision named up front
• Facilitated sessions, virtual or in person
• Synthesis with decisions and owners written down
• A follow-through plan, so the energy does not evaporate

How the work goes

I find where knowledge actually lives, decide where it should live, and build the structure that makes it findable in minutes instead of days. Then I make maintaining it somebody's named job, because unowned documentation goes stale within a quarter.

What you keep

• A knowledge structure with a home for every kind of answer
• Standards and templates for capturing new knowledge
• The first set of documented processes, written with your team
• A review cadence and a named owner

How the work goes

I start with your workflows, not the tools. I find where AI genuinely helps, design the prompts, agents, and automations around your real knowledge, and run the change management so they become habits. I will also tell you plainly where AI is the wrong answer.

What you keep

• A ranked map of where AI pays off and where it does not
• Working automations and prompt systems built on your knowledge
• Guardrails and a use policy your team helped write
• Enablement, so the tools still get used after I leave

How the work goes

This work moves at the pace of trust, and I plan for that pace rather than fighting it. Community-centered engagement, honest listening, and facilitation that makes room for the people who usually get consulted last. Bilingual delivery wherever the community needs it.

What you keep

• Engagement designed with the community, not for it
• A shared vision people recognize themselves in
• Language and narrative your team can use consistently
• Structures that keep the commitment alive after the launch

How the work goes

I build the operational backbone that lets mission and money move together: the calendar, the controls, the reporting rhythm, and the documentation that makes an audit uneventful. Fractional leadership is available when you need the function run, not only designed.

What you keep

• A reporting calendar with owners and real lead times
• Grant and compliance tracking that survives turnover
• Documented procedures for the recurring work
• Optional fractional leadership through a transition

How the work goes

We start with the workflow the site has to serve: who arrives, what they need, and what should happen after they act. I design and build from there: public pages, the admin dashboard, portals, booking, and intake. You review working software every week rather than mockups. At handover your team gets plain-language documentation, a walkthrough recording, and the keys, and I stay available for the first month of questions.

What you keep

• A fast, accessible, genuinely beautiful public site
• An admin dashboard for pipeline, bookings, and content
• Automated intake, follow-up, and reporting
• Full handover, plain-language documentation, and the keys