WHAT WE DO
-
Purpose: Focused teaching for leaders and teams—big or small room, on-site or virtual. Popular topics:
Closed-Loop Handoffs (in one page)
Onboarding OS (3-week ramp to contribution)
Resilience for short-staffed days
Tactical Positivity (standards without drama)
AI as Systems Translator (from SOPs to usable tools)
Run-of-Show Ops (calmer tech week)
People: shared language, coaching scripts, recognition rhythm.
Systems: one-page standards, checklists, facilitation guides, 30-day action plan.
Formats: 60–90-min keynote • half-day • full-day • exec advisory (4 sessions).
Deliverables: topic one-pager, facilitation script, 30-day plan.
-
Purpose: 2–6 weeks inside a real team to implement one big idea and prove it works.
Sprint types: Handoff Standard · Resilience · Onboarding (~3-week ramp) · Standardization (field ops)
People: coaching language, huddle scripts, Tactical Positivity (recognize → request → inspect).
Systems: one-page standard at point-of-use, visual controls, inspection cadence, quick-reference cards.
Signals: checklist completion • handoff verification • time-to-proficiency • on-time starts • error/callback rate • adoption %.
Deliverables: standard + point-of-use card, huddle script, audit loop, after action review templates.
Timeline: Week 0 Observe/Diagnose → Weeks 1–2 build/train → Weeks 3–4 run/inspect → optional Weeks 5–6 tune/hand-off.
-
Purpose: When you need more than one fix—run ODRI (Observe → Diagnose → Recommend → Implement) end-to-end, layering wins without bloat (6–12 weeks).
People: role clarity, feedback rituals, recognition cadence, interface norms.
Systems: small portfolio of SOPs/playbooks, onboarding kit, resilience kit, simple leader scoreboard.
Outcomes: do more with less without burning people out; reliability and morale up.
Deliverables: roadmap, working standards, training, inspections, adoption board.
-
Purpose: Often installed during Sprints/Uplift, Core Modules increase team efficacy across multiple domains.
SOP & Playbook Development (with Onboarding) often installed during Sprints/Uplift
People: train-the-trainer, buddy system, weekly skills demos.
Systems: one-page standards at point-of-use, role scorecards, minimum-competency matrices, day-by-day ramp.
Outcome: ~3-week path to contribution; first-week errors ↓.
Resilience Protocol
People: pre-shift huddles, cross-coverage behaviors, calm comms.
Systems: cross-coverage matrix, calendar pre-blocks, critical-checks list, visible day-flow board.
Outcome: on-time starts ↑; reschedules ↓ on short-staffed days.
We borrow what works from theatre and technical diving—tight communication, clear roles, and rehearsal-grade checklists—and translate it for high-stakes teams.
Our Method? Observe → Diagnose → Recommend → Implement (ODRI): watch real work, name failure modes, pick one big idea to test, train people, install the system, and measure weekly.