Way
A way is a name for a change a user is going through, picked out by the activity itself: "filing taxes," "inviting teammates," "checking inbox." It names the doing rather than the before-and-after contrast between where the user started and where they end up. Ways come at any scale, from "cooking breakfast" down to "flipping the pancake."
Definition
A transition summarized by activity — what's being done, the process — paired with difference, which summarizes the same transition by the condition-delta between the starting state and the resulting state.
Way and difference as aspects of one transition
Every transition can be summarized two ways. The way picks out the activity: "grilling," "freezing," "warming up," "making pancakes." The difference picks out the contrast between endpoints: "raw to cooked," "{surface=raw, interior=cold} to {surface=seared, interior=hot}." Both apply to every transition. They run on orthogonal axes of summary — activity versus endpoint-contrast — and the analyst invokes whichever aspect surfaces what's needed.
Granularity is a separate axis from aspect. A way can be coarse ("cooking dinner") or fine ("sear-top"); a difference can be coarse ("hungry to fed") or fine ("{glucose=low} to {glucose=normal}"). Coarseness lives at the transition scoping layer; aspect lives at the way/difference layer. The two axes don't constrain each other.
How way-naming compresses
A way-name like "making pancakes" points at a parent activity that contains many sub-steps — mixing batter, heating the pan, pouring, flipping — without enumerating them. The name compresses child activities into a single parent-scope handle. The name summarizes the scope; the committed structure underneath — completion criteria, differences — defines what the cluster contains. The name has to be faithful to that commitment, not the reverse.
Compression governed by scope fidelity is what separates a useful way-name from hot-air. A way like "engaging meaningfully" sustains itself by convention without any specifiable difference-structure underneath; the name persists because it sounds coherent, not because the cluster has commitments. Hot-air ways pass without resistance until the framework asks what condition-deltas would have to obtain for the way to apply, and the absence surfaces.
The aspect toggle as methodological pair
Ways and differences support different operations in framework work. Qualitative investigation surfaces ways — users describe what they were doing in activity-vocabulary, and the analyst's job is to cluster those descriptions and name the cluster at a scope-level useful for downstream apparatus. Completion criteria and verification, by contrast, operate on differences — condition-deltas, not activity-names.
The aspect toggle alternates between the two aspects and treats disagreements between them as diagnostic. Where activity-naming and condition-naming come apart, fidelity or sub-step structure needs work. Way-naming alone lets hot-air pass; difference-specification alone freezes on ideation without usable vocabulary. The toggle is what produces and maintains fidelity at the naming layer.
Example
A user grilling a steak. The way is "grilling" — the activity, the process, named at the parent scope that contains lighting the grill, seasoning the meat, placing it on the grate, flipping at the right time, removing at the right doneness. The difference on the same transition is "{steak=raw, interior=cold} to {steak=seared, interior=hot at chosen doneness}" — the condition-delta between endpoints.
The two summarize the same transition from different angles. Each is faithful to the transition; neither replaces the other. Working only in way-mode lets "grilling well" pass without specifying what differentiates well-grilled from poorly-grilled. Working only in difference-mode loses the activity-vocabulary that lets the analyst ask a user what they were doing.