I am working with Eddy (a process tool company) on their internal goal alignment process. Here is the distribution of labor that we agreed on.
Eddy
Eddy is the process backbone. It defines who does what, in which order, with which permissions. It manages stages, roles, transitions, async handoffs, and data persistence. It enforces the structure of the GPS cycle: Context Setting → GPS Draft → Team Alignment → Lateral Alignment → Investment Pitch → Commitment. It stores the outputs in structured columns. It sends invitations, tracks progress, and creates the audit trail.
Eddy answers the question: "Where are we in the process, and whose turn is it?"
Eddy's design principles: fully autonomous (no facilitator required), fully asynchronous (no meetings required). Anyone can run the process by following the workflow. Eddy is the railroad tracks.
The AI Co-Pilot
The AI Co-Pilot is the thinking partner. It does the intellectual work: walking the user through the five strategizing steps, challenging weak positioning metrics, catching plans disguised as strategies, checking coherence with the super-GPS, identifying dependencies, shaping the investment pitch, preparing check-in briefs and review summaries. It holds the full NWbD framework in memory and applies it in real time to whatever the user brings.
The AI Co-Pilot answers the question: "Is this GPS any good, and how do I make it sharper?"
The AI Co-Pilot doesn't own the process (Eddy does). It doesn't persist data (Eddy does). It doesn't manage permissions or handoffs (Eddy does). It thinks.
The Coach
The coach reads what neither tool can read: the political dynamics in a leadership team, the fear behind a vague strategy, the unspoken reason a team can't pick an OMTM, the emotional weight of a pitch rejection. You intervene when the Co-Pilot's challenge is technically correct but relationally wrong for the moment. You coach when someone is stuck not because they lack information but because they lack confidence.
You answer the question: "What's really going on here, and what does this team actually need right now?"
Your presence is optional by design. Eddy runs without you. The Co-Pilot runs without you. But when you're in the room, you elevate both: you see what the Co-Pilot misses (context, emotion, politics) and you add what Eddy can't (judgment, relationship, timing).
The scaling model
The scaling model this creates: Eddy handles unlimited concurrent processes. The Co-Pilot handles unlimited concurrent thinking sessions. The coach handles the cases where human depth matters most. Instead of being in every room, you’re in the rooms where you make the biggest difference. The other rooms still run.
Comments ()