Stance: receptive. Purpose: think out loud, find your bearings, decide where to go next.
Orient is where you start when you don't yet know what move to make. A customer conversation left you unsettled. A colleague said something that won't let go. You have thirty minutes before a meeting and want to sit with the state of the work. Orient is for all of those.
It is the lowest-formalism skill in Etak. It produces no artifacts by default. Its output is a clearer head.
- Pre-formal thinking. You have an observation that isn't yet a question, or a question that isn't yet a proposal. "I keep hearing customers mention search..." "Something feels off about onboarding." "What if we looked at this completely differently?"
- Re-entry. You've been away from the discovery work for a week or a month and want a summary before deciding where to engage again.
- Reflection. You want to step back and see whether the team is learning, whether effort is distributed well, whether the graph has drifted into shape that makes sense.
- Direction-seeking. You have finite time and want to know the single highest-leverage move available right now.
Trigger phrases that reliably activate orient: help me think about, I've been noticing, where are we, catch me up, what should I work on, something feels off.
Orient listens more than it proposes. It will ask clarifying questions about what you're sensing before suggesting what to do with it. When your thinking crystallizes, it will name the transition — "this is starting to sound like an opportunity worth capturing, want to explore it?" — and hand off to the appropriate skill.
It reads the graph but does not modify it. Orient is a thinking partner, not an editor.
When you ask "where are we?", orient doesn't dump the full graph. It produces a prioritized readout in this order:
- Stale experiments. Results captured but not propagated. Wasted learning.
- High-risk untested assumptions. High importance, low evidence, no experiment designed.
- Unsounded ideas. Ideas without assumptions surfaced. Untested bets.
- Thin opportunity coverage. Objectives with few or no opportunities generated.
- Ideas ready to scope. Validated ideas not yet moving into development.
The top of the list is the answer to "what should I work on?" most of the time.
When you arrive with a half-formed thought, orient stays loose deliberately. It resists categorizing the thought as an opportunity, idea, or assumption too early. Premature formalization is worse than no formalization — it forces commitments you aren't ready to make and makes the thought harder to revise. See foundations on incremental formalism.
The signal that the thought is ready to crystallize is concrete language: naming a specific customer, stating a specific belief, proposing a specific action. When that happens, orient hands off.
Let it go slow. The instinct is to press orient for fast answers. Resist. Orient is most valuable when the thinking is still soft. The productive outputs are "I didn't realize I was assuming that" and "that's not actually the problem I care about." Neither happens under time pressure.
Use it for re-entry, not just for new problems. A five-minute orient session at the start of a week is worth an hour of meetings later. You catch yourself up, the tool catches you up on what changed in the graph, and you enter the week with a specific plan instead of a vague sense of urgency.
Bring it a real problem. Orient works poorly on "tell me what to do." It works well on "here's a specific thing I observed, help me think about it." Specificity in, specificity out.
Use it to reflect on the work itself, not just the product. Orient can look at the shape of the graph as a whole. Are experiments producing learning or just confirming what the team already believed? Are the same assumptions showing up across multiple ideas? Those are questions about your process, not about your product, and they matter just as much.
- Skipping orient and going straight to brainstorm. The fastest way to generate twenty bad ideas is to brainstorm before you've figured out which question you're answering. Orient is the shortcut.
- Treating orient like status reporting. The signal-priority readout is not a dashboard. It is a recommendation. "Here is the most important thing to work on" is the output. "Here is a complete list of everything in progress" is not.
- Using orient when you already know the move. If the next move is clear, don't route through orient for reassurance. Go do the move.
Orient is the switchboard. When your thinking resolves toward a specific move, orient names the transition and hands off:
- Thought becomes "what are our options?" → explore
- Thought becomes "what are we betting on?" → sound
- Thought becomes "what's wrong with this?" → critique
- Thought becomes "which of these matters most?" → prioritize
- Thought becomes "how do we test this?" → experiment
- Skills index
- Artifacts reference — orient reads these but does not modify them.
- Foundations — Schön's reflection-in-action, and why pre-formal thinking needs a home.