The Skills.
Twelve skills around a single shape. Each owns one side — its own color, its own position, its own counterweight on the far side of the wheel.
-
Ambition
Ceiling-raising. Bet-making.
Ambition is the refusal to plan from constraints.
What Ambition brings to a team
Ambition is the drive to raise the ceiling of what a team considers possible. On a team, it shows up as:
- A number that embarrasses the room. Naming the bigger figure first and making it the new baseline.
- “What would have to be true?” Converting “impossible” into a working question instead of a door closing.
- Inevitability as a recruiting tool. Attracting talent, capital, and attention as a side effect of goal size.
- Momentum where hesitation used to be. Treating deliberation as a tax and planning from desire instead of budget.
- A default altitude above the tactical. Refusing to let the team disappear into the week.
When Ambition goes unchecked
Ambition without counterweight becomes pressure without direction. Goals get larger, standards get louder, and the team runs harder at targets that were never the right ones. At its worst, unchecked Ambition produces churn — people burning out on crusades they don’t believe in, shipping mediocrity at volume to hit numbers that prove nothing. Ambition that never stops and listens becomes tyranny dressed as vision.
Tensions
- With Taste. Ambition wants scale; Taste wants standard. Unreconciled, Ambition ships mediocrity at volume while Taste makes beautiful things nobody uses.
- With Craft. Ambition drives forward; Craft wants to finish the current thing. Ambition accepts rough edges to hit the window; Craft refuses the rough edges even if the window closes.
- With Intuition. Ambition insists on what could be; Intuition knows what usually is. Ambition projects inevitability; Intuition remembers every time the gut said no.
-
Strategy
Board-seeing. Leverage-finding.
Strategy is the art of choosing which battles to skip.
What Strategy brings to a team
Strategy is the ability to see the whole board while everyone else is focused on the piece in their hand. On a team, it shows up as:
- The full field of play, held at once. The competitive, organizational, and temporal picture, all on the same desk.
- Leverage. Locating the places where small inputs produce outsized outcomes — and spending energy there, not elsewhere.
- Sequenced moves. Ordering decisions so each one sets up the next instead of standing alone.
- Protection from noise. Filtering out the tactical work that doesn’t ladder up to anything that matters.
- A short list. Turning the long menu of things the team could do into the few it actually should.
When Strategy goes unchecked
Strategy without counterweight becomes planning as performance. Decks get longer, frameworks get more elegant, and the team spends more time mapping the landscape than moving through it. At its worst, unchecked Strategy over-intellectualizes execution, treating craft as beneath it and speed as indiscriminate. A perfect plan that never ships is indistinguishable from no plan at all.
Tensions
- With Craft. Strategy decides what matters; Craft insists the details are what matter. Strategy sees the week spent on the wrong feature; Craft saw the week that proved the team could do the work at all.
- With Architecture. Strategy chooses which game to play; Architecture optimizes the structure of the current one. Strategy asks whether the structure is worth keeping; Architecture asks whether the game is worth re-engineering.
- With Taste. Strategy trades off to win the war; Taste refuses to lose any battle. Strategy treats standard as a cost; Taste treats standard as the product.
-
Vision
Future-casting. Inevitability-projecting.
Vision is describing the future vividly enough that others start planning for it.
What Vision brings to a team
Vision is an almost physical sense of where things are heading and a willingness to act as though the future has already arrived. On a team, it shows up as:
- A destination worth the trip. Giving the team a place to point at that’s bigger than the next milestone.
- Calls that look crazy now and obvious later. Making bets the roadmap can’t yet defend.
- Conviction strong enough to carry thin evidence. Rallying people to a pull, not a push.
- License for the long horizon. Permission to work on things that won’t pay back this quarter.
- Orientation through ambiguity. Anchoring strategy to where the puck is going, not where it is.
When Vision goes unchecked
Vision without counterweight becomes prophecy without practice. The roadmap is beautiful; the ship dates slip. Teams exhaust themselves chasing a destination that keeps moving because the visionary keeps seeing further. At its worst, unchecked Vision leaves structural chaos behind it — systems that never got built, promises that never got kept, charisma covering for incompleteness. The future nobody builds is just a wish.
Tensions
- With Architecture. Vision sees what should exist; Architecture asks how it will hold. Vision treats structure as friction; Architecture treats vision without structure as fantasy.
- With Rigor. Vision runs on conviction; Rigor runs on evidence. Vision makes the leap the data can’t justify yet; Rigor refuses the leap the data hasn’t confirmed.
- With Craft. Vision points at the horizon; Craft works the object on the bench. Vision treats finishing as slow; Craft treats the horizon as a distraction from what’s actually being made.
-
Storytelling
Meaning-making. Arc-building.
Storytelling is the difference between information and belief.
What Storytelling brings to a team
Storytelling is the instinct for making people feel before they think, and for framing work so it lands where it needs to. On a team, it shows up as:
- Meaning, not just information. Framing the work so people feel why it matters, not just what it does.
- Customers turned into heroes; features turned into commitments. The basic trick that separates a pitch from a promise.
- Strategy made tangible enough to rally around. Translating abstractions into something a team can actually point at.
- Messaging that lands because it was built from listening. Copy that isn’t clever — it’s true, and the audience can tell.
- A company identity that survives the next pivot. A narrative load-bearing enough to hold shape under change.
When Storytelling goes unchecked
Storytelling without counterweight becomes narrative that outruns the product. The pitch promises what the thing doesn’t yet deliver. At its worst, unchecked Storytelling falls in love with a beautiful story that isn’t true — or isn’t provable — and the team optimizes for the arc instead of the outcome. A compelling story told about the wrong thing is just a more expensive kind of lie.
Tensions
- With Rigor. Storytelling wants the arc; Rigor wants the evidence. Storytelling simplifies to land; Rigor distrusts anything simple enough to land.
- With Velocity. Storytelling wants to frame before shipping; Velocity wants to ship and frame later. Storytelling sees unframed work as wasted; Velocity sees unshipped work as wasted.
- With Architecture. Storytelling explains the product in stakes; Architecture explains it in systems. Storytelling finds the diagram inert; Architecture finds the metaphor lossy.
-
Empathy
Room-reading. Need-surfacing.
Empathy is hearing what the user didn't know how to ask for.
What Empathy brings to a team
Empathy is a sensitivity to what people need, feel, and haven’t quite figured out how to say. On a team, it shows up as:
- Frustration noticed before it’s spoken. Reading the room early enough to change it.
- The user in the meeting, even when the user isn’t. Representing the person the team is serving when that person has no seat at the table.
- Latent needs made articulable. Saying back what customers haven’t yet figured out how to request.
- Support that builds relationships, not just closes tickets. Turning the transaction into trust the product can borrow against later.
- A short distance between the team and the people it affects. Refusing to let the customer dissolve into a persona deck.
When Empathy goes unchecked
Empathy without counterweight becomes paralysis by understanding. One more interview, one more perspective, one more round of listening — the team never acts because it can’t bear to act without perfect comprehension. At its worst, unchecked Empathy treats speed as cruelty, when the user struggling with the product is struggling right now. Endless listening is its own form of neglect.
Tensions
- With Velocity. Empathy wants to slow down and understand; Velocity wants to ship and find out. Empathy treats speed as trampling; Velocity treats understanding as delay.
- With Discovery. Empathy listens deeply to who’s here; Discovery wanders toward who isn’t. Empathy stays with the known user; Discovery keeps asking whether the known user is the right one.
- With Rigor. Empathy trusts what the room told it; Rigor wants the number that confirms it. Empathy finds the metric reductive; Rigor finds the anecdote insufficient.
-
Intuition
Pattern-reading. Gut-trusting.
Intuition is compressed expertise arriving as feeling.
What Intuition brings to a team
Intuition is a finely calibrated instrument built from an enormous library of absorbed patterns, most of which never got written down. On a team, it shows up as:
- Answers ahead of evidence. Reaching the right call before the full case has been assembled.
- A pattern library built from everything the team has seen, shipped, and read. Most of it invisible until the moment it’s needed.
- The wrong note caught in the room. Noticing the decision that reads fine on paper and smells off in person.
- Calibration, quietly delivered. Anchoring the team’s default expectations to what usually happens next.
- Shortcuts through analysis paralysis. Skipping deliberation when the shape of the problem is already familiar.
When Intuition goes unchecked
Intuition without counterweight becomes conviction disguised as insight. Calls get made fast, data gets waved off, and the pattern library stops being refreshed. At its worst, unchecked Intuition makes the same mistakes with increasing confidence — the gut that used to be right becomes the gut that remembers being right. A closed system always confirms itself.
Tensions
- With Discovery. Intuition has already decided; Discovery wants more inputs. Intuition treats inquiry as hesitation; Discovery treats certainty as premature closure.
- With Ambition. Intuition knows what’s likely; Ambition insists on what could be. Intuition says the pattern predicts a ceiling; Ambition refuses the ceiling the pattern predicts.
- With Velocity. Intuition wants to wait for the signal to resolve; Velocity wants to ship and let the signal emerge. Intuition distrusts motion without reading; Velocity distrusts reading without motion.
-
Taste
Quality-sensing. Bar-raising.
Taste is knowing what right feels like before you can explain why it's wrong.
What Taste brings to a team
Taste is the ability to recognize quality across disciplines, even without producing the work itself. On a team, it shows up as:
- The flaw caught six months before users would have. Spotting the cheapness in the draft, not the review cycle.
- Cross-disciplinary judgment. Knowing the copy is off, the architecture won’t hold, or the design undermines the story — without being the writer, the engineer, or the designer.
- A standard held without being shouted. Pulling the team’s average upward without anyone being told to try harder.
- Right-answer convergence in the room. Settling debates before the team ships, measures, and discovers the work felt cheap.
- Output people actually remember. The reason competent execution occasionally becomes work worth a second look.
When Taste goes unchecked
Taste without counterweight becomes a bottleneck disguised as a standard. Shipping slows. Work-in-progress stops surfacing because feedback always feels like a verdict. At its worst, unchecked Taste critiques everything and finishes nothing — a curator where the team needed a builder. Quality unexpressed is quality wasted.
Tensions
- With Ambition. Ambition wants scale; Taste wants standard. Unreconciled, one produces beautiful small things while the other ships mediocrity at volume.
- With Discovery. Discovery opens doors; Taste closes them. Discovery generates the noise Taste needs to filter; Taste rejects the options Discovery needs to keep alive a little longer.
- With Strategy. Strategy trades off; Taste refuses to. Strategy knows which battles to skip; Taste insists every battle it fights is won completely.
-
Craft
Material-fluent. Seam-closing.
Craft is the belief that the work is the work.
What Craft brings to a team
Craft is deep fluency in the actual material — code, copy, pixels, product — and the conviction that meaning lives in the object itself. On a team, it shows up as:
- The gap between “functional” and “finished,” closed. Refusing to ship with the seams showing.
- Pride in the object, whether or not the care is seen. Treating the work as a permanent record of who made it.
- A standard pulled up by example, not lecture. Raising the team’s average without a process document or a pep talk.
- Constraints turned into creative inputs. Knowing the material well enough that the walls become raw material instead of edges.
- Plans and talk turned into a thing that actually works. Closing the distance between intention and artifact.
When Craft goes unchecked
Craft without counterweight becomes polish without purpose. Hours disappear into features nobody needed, rewrites nobody asked for, and refinements nobody will notice. At its worst, unchecked Craft produces beautiful artifacts shipped too late to matter — a week spent on the wrong feature while the window closes. Mastery applied to the wrong object is still the wrong object, just lovingly made.
Tensions
- With Strategy. Craft wants the object to be excellent; Strategy wants the right object. Craft can spend a week on the wrong feature; Strategy wanted the feature skipped entirely.
- With Vision. Craft sees what’s in front of it; Vision sees what’s next. Craft refines the current form; Vision questions whether the current form should exist at all.
- With Ambition. Craft finishes one thing well; Ambition wants ten things bigger. Craft treats haste as disrespect for the material; Ambition treats perfection as disrespect for the window.
-
Architecture
System-seeing. Load-bearing.
Architecture is the work of making the second version possible.
What Architecture brings to a team
Architecture is the instinct to see the system — its dependencies, its failure modes, its implications three integrations downstream. On a team, it shows up as:
- Second-order consequences, surfaced early. Finding the implications before they find the team.
- Structures that bear the loads you haven’t hit yet. Designing for the traffic, the team size, and the edge cases still in the future.
- Primitives instead of one-offs. Turning repeated decisions into patterns the team can reuse without rediscovering.
- Complexity treated as a budget, not a pile. Spending it deliberately instead of letting it accumulate until nobody can move.
- A lower cost of change. Making the next pivot cheaper than the last one.
When Architecture goes unchecked
Architecture without counterweight becomes infrastructure for products that don’t exist. The team frameworks, abstracts, and refactors toward a future that never arrives. At its worst, unchecked Architecture produces elegant systems solving problems nobody has — the team ships a platform when the market wanted a feature. Load-bearing structures are only valuable if something is ever built on them.
Tensions
- With Vision. Architecture wants to know how it works; Vision wants to know why it should exist. Architecture stabilizes assumptions; Vision bets the assumptions are wrong.
- With Storytelling. Architecture speaks in systems; Storytelling speaks in stakes. Architecture treats narrative as decoration; Storytelling treats unexplained systems as invisible.
- With Strategy. Architecture optimizes the structure; Strategy decides whether the structure is worth keeping. Architecture refines the current game; Strategy knows when to change games.
-
Rigor
Vibe-distrusting. Folklore-debunking.
Rigor is the discipline of making reality legible.
What Rigor brings to a team
Rigor is a distrust of vibes when numbers are available, and a refusal to call “it felt right” a decision. On a team, it shows up as:
- Measurement where there were vibes. Installing the instrumentation the team’s been flying without.
- Folklore converted to root cause. Turning “this always breaks” into something the team can actually fix.
- Failure caught in staging, not in the wild. Moving breakage earlier — to review, to test, to the design doc.
- A definition of done that survives the deadline. Holding the standard when everyone else is quietly lowering it.
- Quality as the path of least resistance. Building processes that make the right thing the easy thing.
When Rigor goes unchecked
Rigor without counterweight becomes ceremony. Dashboards multiply, reviews proliferate, and the team spends more time reporting on the work than doing it. At its worst, unchecked Rigor punishes bold moves — every experiment is over-instrumented, every decision deferred for more evidence, every judgment call demoted to a meeting. Process becomes a place to hide. A team that measures everything ships nothing.
Tensions
- With Storytelling. Rigor wants the spreadsheet; Storytelling wants the arc. Rigor sees narrative as distortion; Storytelling sees numbers nobody remembers as waste.
- With Vision. Rigor wants evidence; Vision runs on conviction. Rigor refuses the leap the data hasn’t confirmed; Vision refuses the data that will arrive too late.
- With Empathy. Rigor trusts the metric; Empathy trusts the room. Rigor wants the study; Empathy heard what the study was going to say six weeks ago.
-
Velocity
Momentum-making. Loop-closing.
Velocity is the belief that learning compounds.
What Velocity brings to a team
Velocity is a bias for action grounded in the conviction that the team that learns fastest wins. On a team, it shows up as:
- Shipped beats theoretical. Putting the current version in front of real users and letting the argument end there.
- Momentum as a moat. Staying in motion while competitors stall on their second decision meeting.
- “Roughly right today” over “precisely right later.” Making rough drafts acceptable so the finished ones ever exist.
- Iteration as strategy. Treating the next version as guaranteed, not contingent on permission.
- Feedback loops closed before the signal goes cold. Shrinking the distance between decision and evidence to something a human can actually act on.
When Velocity goes unchecked
Velocity without counterweight becomes motion mistaken for progress. The team ships, ships again, and ships louder — piling up features users didn’t ask for and debt nobody’s paying down. At its worst, unchecked Velocity outruns its own understanding, scaling mistakes faster than it learns from them and steamrolling the people it was supposed to be serving. Speed without direction is just distance from the starting line.
Tensions
- With Empathy. Velocity wants to act; Empathy wants to listen. Velocity treats hesitation as cost; Empathy treats it as care. Velocity trusts the user will adapt; Empathy knows who the user already isn’t.
- With Intuition. Velocity ships to surface the signal; Intuition already read the signal and said wait. Velocity calls that reading hesitation; Intuition calls the shipping reckless.
- With Storytelling. Velocity ships the feature; Storytelling asks what the feature means. Velocity treats narrative as overhead; Storytelling knows that unframed work lands nowhere.
-
Discovery
Signal-finding. Frontier-walking.
Discovery is the refusal to work from yesterday's map.
What Discovery brings to a team
Discovery is the instinct for signal where the rest of the room has agreed there’s only noise. On a team, it shows up as:
- The vein before anyone knows there’s a mine. Finding the opportunity the market hasn’t named yet.
- Better problems, not better answers. Reframing the question before the team commits to solving the wrong one.
- Conversations nobody else would bother with. Talking to the users the competition stopped calling and the segments everyone else wrote off.
- A pipeline the competition hasn’t noticed yet. Stocking the team with signals that haven’t shown up in a dashboard.
- An allergy to inherited belief. Refusing to run this quarter on last quarter’s assumptions.
When Discovery goes unchecked
Discovery without counterweight becomes perpetual exploration. One more interview, one more segment, one more adjacent market — the search never converges because the search was the point. At its worst, unchecked Discovery generates insights nobody acts on and optionality the team never exercises, leaving a team that knows everything and has done nothing. A maze of open doors is still a maze.
Tensions
- With Intuition. Discovery wants more inputs; Intuition has already decided. Discovery treats certainty as premature; Intuition treats inquiry as hesitation.
- With Taste. Discovery opens options; Taste closes them. Discovery produces the noise Taste filters; Taste rejects the options Discovery wants to keep alive a little longer.
- With Empathy. Discovery seeks the new; Empathy listens to who’s already here. Discovery chases the next segment; Empathy asks whether the current one has been fully heard.