Vert/horiz toggle
The vert-horiz toggle alternates between two directions of exploration around a chosen step. Vertical moves along scope: what bigger activity this step is part of, and what smaller pieces it breaks down into. Horizontal moves along time: what came before the step, and what comes after.
Definition
Paired with the aspect toggle, a methodological alternation between two exploration modes around a chosen transition: vertical mode moves along scope (toward larger / toward smaller), horizontal mode moves along sequence (before / after).
Vertical moves along scope, horizontal along sequence
The aspect toggle alternates between two aspects of the same transition — way-naming and difference-specification. The vert/horiz toggle works on a different axis, moving to different transitions related to a chosen one.
Vertical mode moves along scope. Toward larger asks what bigger pursuit contains this transition, what parent workflow it serves. Toward smaller asks what sub-transitions constitute it, what mechanical actions execute it.
Horizontal mode moves along sequence. Before asks what state precedes this and what came earlier in the timeline. After asks what state follows and what comes next.
The toggle alternates between vertical and horizontal as exploration modes. Toward-larger / toward-smaller and before / after are the question-positions a chosen mode produces.
The four-quadrant matrix
Aspect (way/difference) and position (vert/horiz) run independently. Crossing them produces four quadrants:
- Way-horiz: activity-naming of prior and subsequent transitions
- Difference-horiz: condition-deltas across sequence — preconditions, postconditions, transformation chains
- Way-vert: activity-naming at larger and smaller scope
- Difference-vert: condition-deltas across scope — parent completion criteria, sub-transition condition-changes, scope-translation
Each quadrant has the same structural integrity. Way-mode work in either vert or horiz position is independently critical, not preliminary work that gets refined into difference-mode. A workflow whose sub-step story doesn't read coherently in way-mode is structurally broken in ways difference-mode specification may not catch. A qualitative interview that only asks difference-mode questions about preconditions misses the way-mode scope work that situates what the user is pursuing.
Why the axes couple
At the deeper structural level, vertical and horizontal aren't fully independent. Larger scope nests more sub-transitions and longer time-spans; smaller scope nests less of both. The matrix's two axes spatialize this single nesting operation as it appears in workflow visualization — vertical for nesting depth, horizontal for timeline span — but the nesting operation couples them. The matrix is scaffolding for the discipline of asking distinct question-positions during transition exploration; the deeper structure is that scope-selection is one operation, not two.
Example
Starting from "sent first invoice" as the named transition, the toggle produces four directions of movement:
- Horizontal, before: "drafted the invoice"
- Horizontal, after: "received payment from client"
- Vertical, toward larger: "got paid for the work"
- Vertical, toward smaller: "clicked the send button"
The aspect toggle then runs on each — naming the parent activity as "getting paid" (way) or as "{work-unpaid} → {work-paid}" (difference), and so on. Across operational sites, way-vert produces different surface forms: in path design, "what bigger pursuit would this workflow serve, in the user's probable perspective?"; in qualitative interviewing, "what was it about getting paid that made invoicing the next thing to do?"