Careers drift the same way. People work harder, stay busy, optimize tasks, and still stall. Not because they lack drive, but because their internal map is fuzzy.
This post turns “three coordinates” into a 90-day system you can run. It’s written for two tracks:
- Senior ICs (architects/engineers) leveling up to bigger scope
- Managers aiming for director
The cast
A playbook needs a cast. This one has four roles:
Enforces Clarity
Turns intent into a system.
Executes
Always "busy". Gets pulled into everything.
Protects
Risk, governance, reputation.
Cadence
If it's not written, it doesn't exist.
Scene 1: The quarterly review that changes the tone
The Operator walks into the review with a calm confidence.
“I’m shipping. I’m on every escalation. People rely on me.”
The PM doesn’t argue. The PM asks one question:
“Can you state your current coordinates, your destination, and your path, in one minute each?”
Silence.
Not because the Operator is weak. Because the Operator has never been forced to write the map.
The Architect sets a rule for the next 90 days:
Scene 2: A case file that shows why coordinates matter
The Architect pulls out a case file. Not to idolize people. To show mechanics.
Drift happens silently when coordinates aren't fixed.
Case File: The doorway conversation that reset a company’s map
In late 2007, Facebook had scale but no business engine. The product was working. The model was not.
At a Christmas party in December 2007, Mark Zuckerberg met Sheryl Sandberg, then a senior leader at Google. In a later profile, Zuckerberg recalled they talked for “probably an hour” by the door.
A few months later, Sandberg joined Facebook as COO, starting March 24, 2008. Financially, Facebook’s early years were not “inevitable success.” Facebook’s S-1 financials show that in 2008 it had $272M revenue and a $56M loss.
Then the system changed. Not by working harder, but by making direction explicit. Sandberg’s role focused on building the business and operating model to scale revenue and operations.
Debrief: The three coordinates hiding inside the case file
- Coordinate 1, Baseline (reality, not vibes): Millions of users and attention. Weak monetization. No durable operating model.
- Coordinate 2, Target (destination with constraints): Build a real business without breaking the product’s trust and growth.
- Coordinate 3, Path (execution loop + drift correction): Build a revenue engine, build an org cadence, measure, iterate.
Punchline: busy work didn’t fix the company. A clear map did.
Coordinate 1: Baseline
Most professionals plan from a story. Stories are comforting. Stories also protect self-deception. A baseline is a one-page snapshot of reality. No spin. Just data.
Baseline Snapshot
A) Role reality
- What I actually do (top 5):
- Decisions I own vs execute:
- What I'm known for:
- What I should stop doing:
B) Capability (rate 1–5)
- Domain depth:
- Architecture / judgment:
- Execution ownership:
- Communication:
- Influence:
- Leadership:
C) Proof inventory (evidence, not potential)
- 3 shipped outcomes (include numbers):
- 2 artifacts I can show (doc/deck/repo/case study):
- 2 references who can vouch for impact:
D) Constraints
- Hours/week available:
- Location/time zone:
- Non-negotiables:
- Risk tolerance (low/med/high):
E) Friction log (last 30 days)
- Top 3 recurring blockers:
- Top 3 energy drains:
- Top 3 tasks that felt unusually easy:Coordinate 2: Target Spec
Most goals fail because they are slogans ("I want growth"). A usable destination is a spec you can evaluate as true or false in 12–18 months.
Target Spec
- Target role title(s) (1–2):
- Scope I want to own (ownership, not tasks):
- Domain focus:
- Constraints (remote/hybrid, travel, hours, location):
- "No list" (what I refuse to do for 90 days):
Ownership boundary (critical)
- I OWN:
- I INFLUENCE:
- I DO NOT OWN:
Proof required (pick 5)
1)
2)
3)
4)
5)The JD-to-Plan Method
Step 1: Extract 5 outcome pillars. Copy a JD. Group repeated verbs into pillars like "enterprise delivery", "executive influence", or "security posture".
Step 2: Convert each pillar into Proof. Proof = Artifact + Metric + Story.
Step 3: Convert proof into weekly shipping. Commit to shipping one deliverable every week tied to those pillars.
Coordinate 3: Execution Loop
A plan you write once is a wish list. A path is a loop: ship, measure, correct, repeat.
90-day Execution Loop
Objective (90 days): one measurable sentence.
Key Results (3–5):
1) Ship X proof artifacts mapped to the target pillars
2) Create X executive narratives (1-pager or 5 slides)
3) Run X feedback cycles (peer/mentor/mock)
4) Build X reusable assets (templates/patterns/accelerators)
Weekly cadence (calendar it)
- Mon (30 min): choose one deliverable for the week
- Wed (15 min): unblock or cut scope by 50%
- Fri (30 min): score the week and commit next deliverable
- Month-end (60 min): reset KRs and delete low-ROI workThe Leverage Move
Senior scope requires leverage. Leverage comes from assets others can reuse. If you solve the same problem twice, convert it into an asset.
Need this system ready-to-go?
I've packaged these templates, the drift calculator, and the asset examples into a single kit.
Download the Career Navigation KitIncludes Templates, Checklists, and Example Proof Cards.
The Drift Score
Every Friday, score each item 0–2. Total /20. If you are under 10/20 for two weeks, reduce to 3 pillars.
- Target spec is written and constrained
- Ownership boundary is written
- I shipped a tangible deliverable this week
- Proof inventory is updated
- External feedback happened in the last 14 days
- 90-day objective and measurable KRs exist
- Weekly review happened
- “No list” is enforced
- I can explain the path in 60 seconds
- One recurring blocker was reduced
Quick Start
- Write the Baseline Snapshot (30 minutes).
- Write the Target Spec with ownership boundary (30 minutes).
- Pick one target JD and extract 5 pillars (15 minutes).
- Choose one pillar and ship one Level 1 asset this week.
- Run the Drift Score every Friday.
Ready to operationalize your journey?
I help organizations and architects turn stalled initiatives into execution engines.