Nine Grid Thinking

Stop treating the nine-grid as a report card. Your director isn’t asking for a ranking—he’s asking for a trajectory. Start with the center square: each employee’s current system (their role, results, behaviors). Then move down to subsystems: what specific skills, habits, or routines are driving those results? For the plateauing employee, check if their subsystem is stale—are they reusing last year’s playbook? For the volunteer, look for new subsystems forming (cross-functional fluency, stakeholder management).

Now go up to the supersystem: what’s changing in your regional structure, market demands, or team composition? The volunteer is already probing that supersystem; the plateauer may be blind to it. Then shift time. Past: how fast did each climb to their current level, and through what subsystems? Future: what subsystems will regional managers need in 18 months—P&L ownership, conflict resolution, strategic hiring? Map each employee against that future, not today’s job description.

The plateauer may have deep past mastery but no future expansion. The volunteer may be shallow now but compounding. The nine-grid forces you to ask: which one is a subsystem problem (trainable) versus a supersystem mismatch (role change)? Present both as trajectories, not verdicts.

Stop treating the glitch as the problem—it's the symptom. Run the nine-grid before you touch code.

Start at the center: the current system is the rider app's checkout flow. Now drop to the subsystem level: what's inside that flow? Payment tokenization, GPS handoff, order-confirmation payloads. Is one of these failing under load? Then rise to the supersystem: the dispatch engine, the restaurant's order queue, the rider's phone OS version, even cellular coverage in your busiest zones. A 1-star surge during peak hours often traces to a supersystem bottleneck—dispatch flooding the app with concurrent requests, or the app retrying against a throttled payment gateway.

Now sweep time. Past: what changed in the last two weeks? A dispatch algorithm tweak? A new carrier contract? Future: what happens at 7 PM next Friday when order volume doubles? The glitch may be a preview of a capacity ceiling.

The whack-a-mole feeling means you're patching at the system level while the root cause lives one level up or one step back in time. Before coding, map all nine cells with your team—write down what you know, flag what you don't. Then pick the highest-leverage fix, not the loudest bug. That's how you stop the surge and the next one.

You are right to push past the checklist reflex—that is treating a symptom, not the system. Let us run the nine-grid on this.

Start at the center: the current medication administration process on your night shift. Now move down to the subsystem: the individual steps—prescription entry, pharmacy verification, nurse double-check, patient identification. Which step silently degrades at 2 a.m.? Move up to the supersystem: the hospital's shift-change culture, staffing ratios, the electronic health record's alert fatigue, even the physical layout of floors that forces handoffs.

Now sweep the time axis. Past: How did this workflow look six months ago? Did a new EHR update or a staffing policy change introduce a hidden dependency? Future: What happens in six months when you add a new wing or the pharmacy goes to barcode scanning? The near-miss is often a signal that a past change and a future constraint are colliding in the present.

The actionable move: map the handoff between floors and the pharmacy database update as two separate subsystems, then trace one medication from order to administration across all three time frames. You will likely find the root cause lives in the intersection—where the nurse's verbal handoff meets the pharmacy's timestamped database. Fix that seam, not the checklist. That is where your leverage is.