Growth for an unpredictable career

Stop planning careers. Navigate growth.

Giving people the clarity to steer their own development and the language to connect personal growth to organizational direction.

Just as a GPS helps you navigate to a destination, the Individual GPS Framework (Goal, Positioning, Strategy) helps you navigate your professional growth: where you're headed, where you are, and how you prefer to get there.

Navigating personal growth with Individual GPS

Three questions. Three time horizons. Applied to who you're becoming.

Individual GPS asks three questions about your growth:
Goal describes the professional you're growing into: Where am I growing toward?
Positioning measures how equipped you are right now: How close am I?
Strategy resolves trade-offs in how you develop: How do I prefer to grow?
Individual GPS gives your development direction and structure without prescribing a path. You own it. Your People Lead supports it.
Example: You want to become the kind of engineer who designs systems, not just builds features. That's your Goal. Right now you can implement designs others create, but you've never led an architecture decision. That's your Positioning. You learn best through real projects with a sparring partner, not through courses. That's your Strategy. When a growth approach isn't working, you try a different one. You don't change the destination. You don't pretend you're further along than you are.

The Cycle Individual GPS

Most organizations already run in cycles: sprints, quarters, trimesters. The cycle individual GPS aligns your growth to the rhythm you're already working in.

Time Horizon
How long is this growth commitment?		 Goal
Where am I growing toward?		 Positioning
How close am I?		 Strategy
How do I prefer to grow?
Cycle matches org cycle
Build one specific capability this cycle. Concrete enough to verify.
What specific capability you're building this cycle. Derived from the most important gap between where you are and where you need to be (for yourself and for the work). (Think: a learning objective.)
format: plain text
"Lead an architecture decision end-to-end this trimester, including the documentation and the presentation to the team."
Current skill level → target skill level on 1–3 specific skills. Observable behavior, not self-reported confidence. "Can I do X independently?" not "Do I feel ready for X?" (Think: skill matrix levels.)
format: current → target
System design: I Know → I Am Skilled. Technical writing: I Am Skilled → I Mastered. Facilitation: not started → I Know.
What learning approaches you're choosing and what you're deliberately not doing. Trade-offs, not a to-do list. (Think: how you prefer to learn.)
format: preferences + trade-offs
Learn through pairing with [senior engineer], not through courses. Prioritize depth in system design over breadth. Volunteer for the billing architecture decision as the primary learning vehicle.

The same pattern, two more time horizons

The cycle individual GPS doesn't exist in isolation. The same three questions apply to your long-term direction and your daily work, forming a fractal pattern:

Infinite Individual GPS gives long-term direction: the professional you're becoming.

Cycle Individual GPS builds one concrete capability within a bounded time frame.

Immediate Individual GPS makes the learning in every task intentional.

Each level nests into the one above. An immediate growth intention serves a cycle growth strategy. A cycle growth goal addresses the most important gap on the way to the infinite aspiration. The metaphor stays the same. The scope changes.

Time Horizon
How long is this growth commitment?		 Goal
Where am I growing toward?		 Positioning
How close am I?		 Strategy
How do I prefer to grow?
Infinite near-permanent
The long game. The professional you're becoming. Persists across cycles and roles.
The kind of professional you want to be known as. Not a job title. A description of the contribution you want to make and the capabilities that enable it. This rarely changes. When it does, it's a significant life event. (Think: professional identity.)
format: plain text
"I design organizations where people do their best work. I'm the person leaders call when coordination is broken and they don't know why."
The single number that tells you over time whether you're becoming the professional you described. Must be independently observable, not self-reported. (Think: One Metric That Matters from Lean Startup, applied to your growth.)
format: single metric
Number of organizations where I redesigned coordination and the design is still running a year later.
Your reinforcing growth loop. The pattern that compounds your development over time. (Think: a personal flywheel.)
format: reinforcing loop
Take on complex problems → Learn through failure → Teach what I learned → Get trusted with harder problems → …
Cycle matches org cycle
Build one specific capability this cycle. Concrete enough to verify.
What specific capability you're building this cycle. Derived from the most important gap between where you are and where you need to be (for yourself and for the work). (Think: a learning objective.)
format: plain text
"Lead an architecture decision end-to-end this trimester, including the documentation and the presentation to the team."
Current skill level → target skill level on 1–3 specific skills. Observable behavior, not self-reported confidence. (Think: skill matrix levels.)
format: current → target
System design: I Know → I Am Skilled. Technical writing: I Am Skilled → I Mastered. Facilitation: not started → I Know.
What learning approaches you're choosing and what you're deliberately not doing. Trade-offs, not a to-do list. (Think: how you prefer to learn.)
format: preferences + trade-offs
Learn through pairing with [senior engineer], not through courses. Prioritize depth in system design over breadth. Volunteer for the billing architecture decision as the primary learning vehicle.
Immediate hours – days
Make learning intentional in every task. One line on the same artifact as your task GPS.
What you're learning by doing this task. Not a separate exercise: one line added to the task itself. Links to the cycle growth strategy it serves. (Think: a learning intention.)
format: one line
"I'm also building system design thinking through this task. First time scoping a service boundary on my own."
What you can do now vs. what you'll be equipped to do when this task is done. (Think: before and after.)
format: before → after
Before: I've only seen service boundaries defined by others. After: I've defined one myself, made trade-offs, and can explain why.
How you're approaching this task to maximize learning. The choice between the safe route (deliver fast, learn little) and the stretch route (slower, builds capability). (Think: deliberate practice.)
format: approach choice
I'll draft the service boundary myself first, then review with [senior engineer], rather than having them define it and me implementing.
The fractal advantage for growth. People who make their learning intentions explicit on daily tasks will recognize the same pattern when they set quarterly growth goals or articulate a long-term professional aspiration. The framework teaches itself through use. Growth stops feeling like a separate activity bolted onto work, because it's embedded in the same structure.
When growth stalls, adapt in this order:
1
Change the learning approach
Try a different way to grow. Cheapest to change.
2
Adjust the skill target
Reduce ambition based on what you learned about yourself.
3
Rethink the growth direction
Only if you learned something fundamental. Most expensive.
Each step is more expensive than the last, so exhaust the cheaper options first. You own these changes. Your People Lead is a sparring partner, not a gatekeeper.
Who owns it
You
You write it, adapt it, and are accountable for following through. This is your GPS. No one else can write it for you, because no one else knows where you want to go.
Lead
Your People Lead is a sparring partner. They challenge your self-assessment, help you find growth terrain in the work, and hold you accountable for the commitments you made to yourself. They don't set your goals.
Org
The organization provides the terrain. Work that stretches you, access to people you can learn from, and enough slack to take the slower route when it builds capability.
The skill matrix as positioning tool
A skill matrix maps the capabilities required in a function across four levels: I Know, I Am Skilled, I Mastered, I Teach. It provides the shared vocabulary for positioning at the cycle level. Your self-assessment on the matrix is your starting location. Your target level is where you're headed.
Principles
01
Each time horizon nests into the one above. An immediate learning intention serves a cycle growth strategy. A cycle growth goal addresses a gap on the way to the infinite aspiration. Growth becomes coherent across scales.
02
Growth is self-chosen. Imposed development goals create compliance, not capability. When you choose what to grow toward, the motivation is intrinsic and the learning sticks.
03
Observable over self-reported. "I handled this situation independently" beats "I feel confident about this." Positioning works when it's grounded in evidence, not narrative.
04
Growth is part of the work, not a perk. Every task is both a delivery opportunity and a learning opportunity. Individual GPS makes the learning side explicit.
05
Roles evolve with people. When someone's individual GPS outgrows their current role, that's a signal to expand the role or find a better fit. Growth doesn't require leaving.

The skill matrix

The skill matrix is the positioning tool for Individual GPS. It maps the capabilities required in a function across four levels of proficiency. Each person places themselves on the matrix for each skill, creating a shared picture of where they stand and where they're growing.

The four levels describe observable capability, not seniority or tenure:

I Know — You understand the basics and can apply the skill with guidance.
I Am Skilled — You perform the skill independently and handle routine complexity.
I Mastered — You handle complex situations, make trade-offs, and others seek your judgment.
I Teach — You develop others in this skill and shape how the function practices it.
Example: Engineering function — one person's self-assessment
This engineer is assessing their current level and setting a cycle target for system design.
System design Code quality Technical writing Facilitation Debugging
I Teach
I Mastered
I Am Skilled
I Know
Current level
Cycle target

This person's cycle GPS writes itself from the matrix: system design from I Know to I Am Skilled, technical writing from I Am Skilled to I Mastered, facilitation from not started to I Know. The matrix makes the gap visible and the target concrete.

Who creates the skill matrix? The function lead drafts the initial list of skills based on what the function actually needs. The list stays deliberately short (5–8 skills) and is reviewed each cycle. People self-assess. Peers and the People Lead can challenge the assessment. The matrix is a conversation tool, not a performance rating.

Organizational GPS navigates what you produce together. Individual GPS navigates who you become. The two connect through a simple principle: your growth makes you more capable of contributing to the team's goals, and the team's goals give you real terrain to grow on.

Running Individual GPS

The operational guide. How to set growth goals, check in on progress, and reflect on what you learned.

Individual GPS runs on the same cycle rhythm as the organization. The growth cycle piggybacks on existing structures: 1:1s, sprint retrospectives, and cycle reviews. No additional meetings required.

The growth cycle

Every cycle follows the same rhythm:

Start of cycle
Goal setting
During cycle
Check-in
During cycle
Check-in
End of cycle
Reflection
↩ Reflection informs next cycle's goal setting

Growth check-ins happen inside existing 1:1s. Not as an agenda takeover: five minutes at the start or end is enough. The People Lead's job is to keep the conversation honest, not to evaluate.

Growth goal setting

At the start of each cycle, review your infinite individual GPS and the team's cycle GPS, then set your growth goals in four steps. Start from where you are, not from where you want to be.

1
P Positioning (Current)
"Where am I honestly right now?"
Self-assess on the skills that matter for this cycle's work. Use the skill matrix as a starting point, but ground it in recent evidence: what did you actually do in the last cycle, and what does that tell you about your capabilities?
2
G Goal
"What capability would make the biggest difference?"
Pick the growth goal that addresses the most important gap. Ideally, this is where your personal aspiration and the team's needs overlap. That overlap is where growth becomes meaningful, not bureaucratic.
3
P Positioning (Target)
"What will I be able to do by the end of this cycle that I can't do now?"
Describe the target in behavioral terms. Not "feel more confident about X" but "independently handle Y." Use the skill matrix levels. One level up in one skill is a serious achievement. Two levels up is unrealistic for most cycle lengths.
4
S Strategy
"How will I actually learn this?"
Choose your learning approach and state what you're not doing. Most learning happens through actually doing the thing you want to learn (roughly 70%), some through learning from your peers (20%), little through formal study (10%). State which tasks in the upcoming cycle will be your growth vehicles, and who you'll learn from.
The ownership test. Before finalizing your individual GPS, ask: is this something I genuinely want, or something I think my People Lead wants to hear? If you wrote it to satisfy someone else, it won't survive contact with real work. Growth goals that come from obligation get dropped at the first deadline.
Why start with positioning, not the goal? Because you can't set a meaningful growth target without knowing where you actually stand. Self-assessment surfaces the gaps that matter. The goal becomes a response to what those gaps tell you, not an aspiration disconnected from reality.

Growth check-in

Growth check-ins happen inside existing 1:1s. Five minutes is enough. The purpose isn't tracking: it's keeping the growth intention alive against the pull of daily delivery pressure. When growth gets squeezed out by deadlines repeatedly, that itself is worth discussing.

A check-in follows three steps:

1
P Positioning (Current)
What happened since last time? Did I get to practice what I planned? What evidence do I have that I'm building this capability?
2
S Strategy
Is the learning approach working? Am I actually learning through the vehicles I chose, or am I defaulting to safe, familiar work? Do I need a different approach?
3
G Goal
Is this still the right thing to grow toward, given what I've learned about myself and the work? Has something changed that makes a different growth goal more important?
The People Lead's role during check-ins. Challenge gently. When someone says "I think I'm making progress," ask for the evidence. When someone says "I didn't have time for growth this cycle," explore whether that's a capacity problem or an avoidance signal. The goal is honesty, not comfort.

Growth reflection

At the end of each cycle, reflect on what happened. This is the most valuable part: the learning from learning. Growth reflection happens in a dedicated 1:1 (30–60 minutes) or as the primary topic of a regular 1:1 at cycle end.

1
P Positioning (Achieved)
Where did I actually land? What can I do now that I couldn't do at the start of this cycle? What's the behavioral evidence?
2
S Strategy (Lessons)
What worked and what didn't? Which learning approaches actually built capability, and which ones felt productive but weren't? What will I do differently next cycle?
3
G Goal (Review)
Did I reach the goal? Was it the right goal? What surprised me about my own development? What does this tell me about my infinite aspiration?
Celebrate. Growth in capability is harder to feel than shipping a feature. Make it visible. Update the skill matrix. Name specifically what changed. The resulting energy sustains the next cycle better than a sense of "not enough" ever could.
Reflection informs the next cycle. Those who grew as planned set a more ambitious target. Those who fell short with good reasons adjust their approach or their ambition. A pattern of stalling without adjustment needs a structural conversation: is this really your goal, or is the environment not providing the terrain?

Keeping growth alive

The minimum. If you don't think about your growth goals for weeks at a time, they're not real. The most common failure mode: growth goals are set with intention, forgotten in daily delivery, and "rediscovered" at cycle's end with disappointment.
Embed in tasks
immediate GPS · daily
When you start a task, add one line: "I'm also building [skill] through this." When you finish, note what you learned. This turns delivery into deliberate practice.
Surface in 1:1s
check-ins · every 1–4 weeks
Bring your individual GPS to every 1:1. Five minutes is enough. Your People Lead keeps you honest: "Where's the evidence? What did you actually try?"
Connect to the long game
infinite GPS · every cycle
At cycle boundaries, zoom out: does your cycle growth goal still serve your infinite aspiration? Are you on a path that leads where you actually want to go?

Getting started

1
Introduce Individual GPS in 1:1s
Start with People Leads. Walk them through the framework and have them write their own individual GPS first. You can't guide someone through a process you haven't experienced yourself.
2
Start with cycle GPS only
Don't introduce all three time horizons at once. Start with one cycle growth goal per person. Keep it simple. The infinite and immediate levels come later, once the cycle pattern is familiar.
3
Use the skill matrix as the positioning tool
If your function already has a skill matrix, use it. If not, draft one with the function lead. The matrix provides the shared vocabulary for growth conversations. Without it, positioning stays vague.
4
Add the immediate level gradually
Begin with a sprint retrospective prompt: "What did you learn this sprint?" Once people are used to reflecting on learning, invite them to state learning intentions at the start of tasks. Don't mandate it. Let the pattern spread through example.
5
Introduce the infinite level when it's needed
The infinite individual GPS matters most when someone is at a crossroads: unsure about their direction, outgrowing their role, or unclear about what to invest in next. It's a conversation tool for those moments, not a form to fill out on day one.

Connecting Individual GPS to Organizational GPS

Two systems, one structure. Where personal growth and organizational direction meet.

Individual GPS and organizational GPS are separate frameworks. Individual GPS is about who you're becoming. Organizational GPS is about what you're producing together. They use the same structure (Goal, Positioning, Strategy across three time horizons) because the thinking pattern is the same. But the content is different.

The power is in the connection. Two interface points link them:

Interface 1: Cycle alignment

During cycle goal setting, each person identifies 1–3 growth goals that the cycle's work enables. The question that creates the link: "Given the team's cycle GPS, what can I learn by contributing to it?"

Team Cycle GPS
What we're producing this cycle
provides terrain →
← builds capability
Individual Cycle GPS
What I'm learning this cycle

Review these for fit: "Does this cycle's work actually give you terrain to grow on? If not, let's adjust either your growth goal or your task allocation." The strongest growth goals sit at the overlap between what the organization needs and what the individual wants to become.

Interface 2: Immediate embedding

When someone writes their immediate organizational GPS for a task, they add one line for their individual GPS: what they're learning through this task.

Example: one task, both lenses

Org GPS: "Marketing site explains what we do to a first-time visitor."
Individual GPS: "I'm building copywriting skills through this: first time translating technical capability into user-facing language."

Same task. Two orientations. One produces the deliverable. The other produces the capability.

This also makes visible when someone is always doing what they're already good at (no growth) or always stretching beyond their current capability (risking delivery). Both are signals worth discussing.

The meaning equation

Organizational GPS alone produces orientation: you know what you're working toward. Individual GPS alone produces self-awareness: you know who you're becoming.

Combined, they produce meaning: I'm working toward something the organization needs, and the way I'm doing it is making me the person I want to become.

This is the reason the same GPS structure works at both levels: not because individual growth is organizational alignment in miniature, but because people who see their growth reflected in the work they do will bring more to it than people who treat growth as a separate exercise.

The fractal onboarding path

If you're introducing both GPS frameworks, start with the individual level. People learn "goal, positioning, strategy" as a thinking pattern applied to their own growth. Then introduce organizational GPS. The pattern is already familiar: the same structure, applied to a different scope.

This is the opposite of how most frameworks roll out (top-down, company first). It works because the individual level is the lowest-stakes environment to learn the pattern. Someone who has practiced GPS on their own development will intuitively understand team and company GPS when they encounter it.

Individual GPS can start before organizational GPS is in place. People can set growth goals, check in during 1:1s, and reflect at cycle's end without any company-level GPS existing yet. The organizational layer adds alignment. The individual layer adds meaning. You can build them in either order.