Skip to main content

Personal Strategy: Career Anchors, Sustainable Pace, Visibility

What This Concept Is​

A personal strategy is a short written artifact naming three things:

  • Career anchor. Edgar Schein's term for the core value that will not move under pressure. Common engineering anchors: technical/functional competence, autonomy, pure challenge, service/cause, lifestyle balance, entrepreneurship, managerial competence, security.
  • Sustainable pace. The working pattern you can hold for years, not months. Named in concrete rules - working hours, on-call tolerance, travel load, number of open projects.
  • Visibility plan. How the right people learn what you have done, without self-promotion theater. Usually some mix of artifacts, conference talks, internal presentations, and named stakeholders who see your work.

The strategy is yours. Nobody else is going to write it for you, and no career ladder is a substitute for it.

Why It Matters Here​

Staff+ engineers who do not have a personal strategy tend to get the career they stumbled into, not the one they wanted. Symptoms:

  • drifting into a role that optimizes for organizational convenience rather than the engineer's own anchor (e.g., a pure-challenge anchor ends up in a stable ops role)
  • working unsustainably for two years, then leaving the industry instead of the company
  • doing excellent invisible work; being passed over for promotion; feeling resentful; repeating
  • being recruited into a manager role for compensation reasons while the anchor is technical

A personal strategy will not protect you from organizational decisions, but it will give you a clear answer to "is this offer / project / role worth accepting?" The people without that clarity say yes to everything and then wonder why they are exhausted.

Concrete Example​

Short personal strategy for a fictional Staff engineer:

Career anchor. Technical/functional competence with a secondary anchor in autonomy. I do not want to be a manager in the next three years, even for compensation. Depth over breadth.

18-month goal. Principal engineer title or equivalent; lead the paved-road RFC through acceptance; publish one external talk or post.

Sustainable pace rules.

  • No more than two on-call rotations per quarter.
  • Working hours cap at 45/week sustained, with ≤2 peak weeks per quarter.
  • One large written artifact per quarter (strategy memo, RFC, or conference talk).
  • One week fully offline per quarter; phone off.
  • At most three active projects at a time.

Visibility plan.

  • One cross-team RFC per quarter, signed.
  • One internal tech-talk per six months.
  • One external post or talk per year.
  • Named sponsors: [manager], [skip-level], [VP of platform]. 1:1 with each quarterly.

Review triggers. If I hit two 55-hour weeks in a row, or two quarters without a large written artifact, reopen this document.

Notice: no vague language, no motivational framing. Every item is observable, and the document has review triggers like a strategy doc (Concept 5).

Detecting a Failing Personal Strategy Early​

A personal strategy fails quietly. The symptoms look like normal senior-IC burnout, but the root cause is strategy-level. Watch for these early signals, in order:

  • You cannot name your anchor without hedging. "I think it's maybe technical competence, but also I like leading?" Drift in progress; the anchor needs a conversation.
  • Your calendar for the last month contradicts your stated strategy. The quickest lie detector: if your strategy says "depth over breadth" and your calendar shows 14 different projects, the strategy is aspirational, not operational.
  • You said yes to a role change for compensation reasons with no matching anchor shift. A pure-technical anchor accepting a manager role "because of the pay bump" is how the next burnout is scheduled.
  • You have not had a 1:1 with a named sponsor in a quarter. Sponsors lapse when not maintained; a strategy where the visibility plan is idle is a strategy that will surprise you at next promo cycle.
  • You are answering "what are you optimizing for?" differently in each 1:1. You are telling each listener what they want to hear; the strategy doc exists precisely so you can give the same answer to everyone.

Any one of these is a prompt to reopen the document, not a reason for alarm. A personal strategy that gets reopened twice a year is a living document; one that stays unchanged for three years has usually been forgotten rather than accomplished.

Common Confusion / Misconception​

"Personal strategy is self-help." No, if it is done right. A real personal strategy has the same structure as any other strategy: diagnosis (where am I, what is my anchor), policy (what I will and will not do), action (concrete quarterly moves), tradeoffs (what I give up).

"Visibility means self-promotion." The difference: self-promotion is performative ("let me tell you how I helped"); visibility is evidentiary (the written artifact exists, named stakeholders saw it). Good visibility happens because the work is written down and circulated, not because the engineer is loud on Slack.

"Sustainable pace means slowing down." Not necessarily. Sustainable pace means being honest about which pattern of work you can hold for five years. For some engineers that is 40 hours; for others it is 55 with an unbroken week off per quarter. The number is less important than whether you can actually hold it.

"Career anchors are static." They drift slowly over careers - typically on decade-scale shifts. But within a single role (2-4 years) they are usually stable. Knowing your current anchor is more useful than claiming to have re-examined it last week.

"The right people will notice good work eventually." Sometimes. More often, the right people notice people whose names are in their mental rolodex - people who wrote the RFC they read, gave the talk they attended, were recommended by a peer. Visibility is how you land in that rolodex.

How To Use It​

Write a one-page personal strategy every year. Reopen on triggers.

  1. Name your anchor. Schein's list is a good starting point; pick one, secondary optional.
  2. Name an 18-month goal. Specific. Role, artifact, or scope.
  3. Name sustainable-pace rules. Numbers, not vibes. Observable.
  4. Name a visibility plan. Artifacts and named sponsors, not "more posts."
  5. Name review triggers. Conditions under which you will reopen the document.

Check Yourself​

  1. What is a career anchor and why does it matter?
  2. Name one observable (non-vague) rule in a sustainable-pace plan.
  3. What is the difference between self-promotion and visibility?

Mini Drill or Application​

Write your own personal strategy. One page. The sections:

  • Career anchor (1-2 sentences; pick from Schein's list if unsure)
  • 18-month goal (1-2 sentences; must be specific)
  • Sustainable-pace rules (5-8 lines, each observable)
  • Visibility plan (5-8 lines, artifacts + named sponsors)
  • Review triggers (2-3 lines)

Then share it - or part of it - with a trusted peer or mentor. The social-proof step is the point; a personal strategy no one else knows about is almost as invisible as no plan at all.

The Anti-Goals: What You Will Not Do​

A personal strategy is stronger when it explicitly names anti-goals - the roles, projects, or patterns you will decline. Anti-goals are to your personal strategy what anti-scope is to an engineering strategy: they do most of the work. Examples for different archetypes:

  • Tech Lead anti-goals. "No TLM (Tech-Lead-Manager) transitions in 2026 even for comp; no acquiring an embedded team outside Platform; no single projects longer than 2 quarters before revisiting fit."
  • Architect anti-goals. "No direct reports; no calendar days with more than 3 design reviews; no ownership of a specific service for more than 6 months - I review, I do not own."
  • Solver anti-goals. "No recurring commitments outside the rescue; no sprint ceremonies during a rescue; leave within 30 days of stabilization."
  • Right-Hand anti-goals. "No taking on another partner executive concurrently; no writing code on sprint cadence; no project ownership with a delivery date unless the exec is accountable."

Anti-goals are unusually hard to write because they require rejecting things that others will frame as promotions. A personal strategy with clear anti-goals is how a senior IC politely refuses a TLM role, declines a second Right-Hand partnership, or leaves a solved project without drifting into owning it.

Transfer / Where This Shows Up Later​

Personal strategy is the meta-level to which the entire module collapses:

  • Archetype and altitude (Concepts 1-2). Your anchor interacts with your archetype. A pure-technical-competence anchor inside a Right-Hand archetype is a structural mismatch; your personal strategy surfaces it.
  • Leverage (Concept 3). Your visibility plan is a leverage move on your own career; anti-goals are leverage against over-commitment.
  • Strategy artifacts (Concepts 4-6). Your personal strategy is Rumelt's kernel applied to you: diagnose current state, pick a guiding policy, name 3-5 actions.
  • Influence (Concepts 7-9). Your named sponsors (from Concept 13) are the Accountable stakeholders in your personal strategy; your manager is the first pre-read.
  • Communication (Concepts 10-12). Your visibility plan is an audience-aware-explanation exercise applied to your own work.
  • Sponsorship and feedback (Concepts 13-14). You are both a sponsor and a sponsoree; feedback is how your strategy stays honest.
  • Semester 8 and beyond. M1-M4 each generate opportunities you will accept or decline based on your strategy. Semester 10 M5 on staff+ career explicitly operationalizes this module - your personal strategy from this concept is the input artifact.

Read This Only If Stuck​