Use when you're trying to define something that doesn't have a name yet — a decision, a relationship between things, a role, a product, a concept. You can feel the shape but can't articulate it. The micro details are present but the macro frame hasn't emerged. This skill helps you cast the net, find the dimensions, and discover what the thing actually IS by exploring it from every angle until the definition writes itself.
Some things don't have names yet because they haven't existed before. A decision where the options aren't A or B but something that hasn't been articulated. A role that combines responsibilities no one has combined. A product that does something no product category describes.
This skill is for those moments. Not to force a name onto something — but to explore it from enough angles that the name (or the definition, or the decision) emerges on its own.
The process: cast the net wide first to find all relevant dimensions, and then across all relevant dimensions. For each dimension, find both the macro (the big picture, the category, the abstraction) and the micro (the specific evidence, the concrete example, the thing that makes it real). The synthesis of macro and micro across enough dimensions begins to reveal the shape. As you explore each dimension, it will become apparent which ones matter and need even deeper dives, vs which ones are actually just noise. This is best discovered through exploratory conversation. Once refined, the shape reveals the name.
Start with whatever you have — even if it's vague. "I feel like my role has changed." "This product doesn't fit its category anymore." "I can't tell if these things should be together or apart." The sensing is the seed.
Don't start with what the thing IS. Start with what it TOUCHES. For a product, that might be: who uses it, what do they use it for, what would they use instead if it didn't exist, what does it make possible that was impossible before. For an organizational decision, it might be: who's affected, what changes if we go left vs right, what stays the same either way, what are we afraid of losing. For a relationship between systems, it might be: where does one end and the other begin, what flows between them, what breaks if you separate them, what simplifies. For a role, it might be: what do you actually do (not your title), who depends on you, what would break if you left, what have you created that didn't exist before.
This step is about breadth — find as many dimensions as possible. Don't go deep yet. Depth comes in Step 3, after you know which dimensions matter.
Each dimension is a line of inquiry. Follow each one far enough to find something surprising — something you didn't expect when you started pulling that thread.
For every dimension you find:
For a product: macro might be "it's an intelligence layer." Micro might be the exact moment a marketing person asks a question in plain English and gets a cross-referenced answer from three systems. For a decision: macro might be "we're choosing between simplicity and power." Micro might be the specific feature that forces the tradeoff. For a team structure: macro might be "this function spans departments." Micro might be the Tuesday meeting where three people discovered they were solving the same problem separately.
Macro without micro is abstract. Micro without macro is a list of facts. The synthesis is understanding.
Not every dimension deserves a deep dive. Notice which ones are producing insight and which are noise. The ones that surprise you, the ones that resist easy answers, the ones where macro and micro don't quite align — those are where the shape lives. Let the others go.
This filtering is best discovered through conversation, not solo analysis. Say what you're seeing. The dimensions that matter will become obvious when you try to explain them.
The most important step. Compare what you've found against existing categories (job titles, product types, organizational structures, whatever framework applies). Where does it fit? Where does it overflow? The overflow is where the new definition lives.
Don't force it into an existing box. Don't throw away the boxes either. Use them as reference points — "it's like X in these ways, but it also does THIS which no X does, and THAT changes the nature of the whole thing."
Is the thing you're looking at a combination of existing things added together? Or is it something where the parts amplify each other — where each dimension makes the others more powerful?
Addition: 1 + 1 + 1 = 3 (a person who does three jobs) Synergy: each dimension feeds the others in real time, creating something qualitatively different from the sum
If it's synergy, the name can't be a compound. It needs to be a single thing that captures the emergent property.
Don't force it. If you've explored enough dimensions with enough depth through exploratory conversation, the right word (or phrase, or framing) tends to appear in the conversation itself — often in something you say without thinking about it. Watch for it. The name is usually already in the room before anyone recognizes it.
Sometimes you can't see the shape by looking at it directly. Your assumptions about what it "should" be keep overriding what it actually IS. When this happens, stop looking at the thing and start looking at what's around it.
In art, negative space is the space around and between subjects. Students are taught to draw the space between the legs of a chair instead of the chair itself — because it bypasses their mental model of "chair" and forces them to see what's actually there. The negative space reveals the positive shape more accurately than looking at the shape directly.
Applied to finding the full shape of anything: define the edges by noticing what it ISN'T.
Example — a product that defies its category:
Looking at it directly, you see: skills, distribution, intelligence, connections, a rubric. You keep naming the parts. Every name is a compound — "AI Skills Ecosystem," "Intelligence Platform" — because you're describing what's inside.
Looking at the negative space — what's around it that ISN'T it:
Each "it's not" reveals an edge. The edges trace a shape: it sits BETWEEN the person and their systems. It's not the systems. It's not the person. It's the space where the person's question meets the system's data and something intelligible comes back.
The positive space gave you parts. The negative space gave you function.
Use this technique when the direct approach produces lists but not understanding.
| What needed a shape | Dimensions explored | What emerged |
|---|---|---|
| An onboarding flow that works but nobody can explain to new hires | What each step actually does, which steps people skip, what questions come up after, what the flow assumes the person already knows | A gap between what the flow covers and what people actually need — the shape was in the questions, not the steps |
| A meeting that keeps getting longer but nobody wants to cancel | Who speaks, who listens, what decisions get made vs deferred, what would happen if it were half the length | Two meetings pretending to be one — the shape was a split, not a fix |
| A tool that different departments describe completely differently | What each department uses it for, what they ignore, what they wish it did, how they'd replace it | Not one tool with many uses — three tools sharing a name. The shape was the boundaries between use cases. |
| A repo that started as one thing and became another | What two contributors each built, horizontal vs vertical, whether the interdependence is complicated or complex | A question for the team: "separate repos, or greater together?" — the question itself was the shape |
| A permission model for non-technical users across departments | Who uses it, what's read-only vs dangerous, how it feels to each department, what HR sees vs what Marketing sees | The permissions define the product — each person's instance takes the shape of their access |
| A process that keeps producing better results but nobody can explain why | The steps, the examples, the failures that informed each step, the pattern across instances | A rubric — not a checklist to follow but a set of dimensions to explore. It grows by being used. |
| A skill that helps define things that don't have names | Positive space (what it does), negative space (what it isn't), synergy vs addition, when it works vs when it doesn't | This skill — still being refined in the moment of its own creation |
Sometimes you cast the net and the shape doesn't emerge. That usually means:
This skill is an instance of the pattern it describes. It was created when the process of finding the shape of skills turned out to be the same process at a different scale — applicable to products, roles, decisions, and anything else that doesn't have a name yet. The skill-creation rubric is an instance of this pattern applied to skills. This skill is the general case.