Consumers direct intelligence

Monday morning, a household opens the Meal Companion and says: "use the spinach by Wednesday and keep Tuesday light, we are both working late." They are not clicking vegetable priority sliders or opening busy evening settings panels. They are directing. They state what should change about the week and expect the product to compile that into plan state.

That is different from operating software. Operating means learning the product map. Directing means staying in the domain language while the system gathers, generates, and acts within declared bounds. When direction works, the household stays in the kitchen conversation. When direction fails, each utterance becomes an isolated prompt, a new chat reply with no durable effect, or a full regeneration that erases accepted work.

Helpful context: Intelligence-native products describes the structural shift this note assumes. Intent over instructions and point and fix are the interaction patterns that make direction practical.

Direction is not configuration spaghetti

Configuration spaghetti hides intent inside nested settings. Direction without structure hides intent inside chat. Both failures leave households unable to see what changed or contest what was assumed. Honest direction compiles utterances into state objects with schema, visibility, and editability. A redirect about spinach updates context flags, triggers replan where the constraint binds, and preserves meals already accepted. The household sees a diff. They can approve, reject, or patch locally. Dishonest direction declares human control while arranging for passive acceptance theatre. The Collaboration Contract and visible thinking keep direction real.

The product surface changes as a consequence. The blank page gives way to a low-cognitive first draft. Configuration panels give way to conversation for intent, while exact constraints stay exact. Recommendation becomes more central than mere response. Collaboration modes must match what the interface claims. Builders still own the architecture underneath. Named cognitive units, authority, memory forms, and evaluation remain inspectable to the team even when the interface feels simple. Intelligence beneath the surface describes that split.

The originating sentence shows direction at its most compressed. "Plan dinners for four this week. Tuesday and Thursday are busy. Use the spinach before Wednesday and avoid meals we ate last week." That sentence is direction in household language. The product compiles it into interpreted week, constraint flags, and a provisional plan the household can review. Direction does not mean the product guesses silently. It means the household speaks in domain terms while the system owns procedure inference until the person disagrees. When disagreement arrives, point and fix keeps correction local. When scope is unclear, targeted questions beat invention.

What direction looks like in the household planner

"Use spinach by Wednesday" is intent that updates context for this run, triggers replan where the constraint binds, preserves accepted meals on other days, and shows what changed so the household can contest or approve. If the product responds with seven new meals and no diff, direction collapsed into regeneration theatre. If the product replies "got it" and appends a chat line, direction collapsed into transcript theatre.

Direction also respects authority. Grocery purchase still needs approval. Medical diet questions still defer to people with standing. Direction compiles into bounds, not into permission the product invents.

Wednesday evening the household says "guests are coming Friday, keep the rest of the week as accepted." Honest direction updates guest context, revisits Friday's meal, preserves other days, and shows a diff before apply. The household approves or patches locally. Direction also works when the household refuses. They reject Friday's suggestion and ask for something vegetarian. The product records the rejection as signal, offers alternatives, and does not silently revert on the next run.

The Meal Companion loop runs plan, act, observe, review, revise, repeat. Direction enters at review. The household accepts a meal, patches Tuesday, redirects spinach use, or refuses a purchase recommendation. Each act of direction compiles to state the next iteration reads deterministically. When direction stops at the chat layer, the loop breaks. CritiquePlan runs on stale context. RecommendMealSubstitution proposes against outdated constraints. The product sounds responsive while behaving amnesiac.

Consumers increasingly direct intelligence instead of operating feature maps alone.

Thoughtware: Designing in the Intelligence Age · Ch. 3

How direction differs from delegation

Delegation assigns a task and walks away. Direction stays engaged. The household reviews the plan, patches Tuesday, approves grocery spend, and promotes mushroom dislike when ready. The product prepares and proposes within granted authority. The person retains ownership where values, irreversibility, or unsettled terrain require it. See co-pilot the decision for the allocation framework.

Products that treat one utterance as permanent permission violate direction. Products that require form navigation for every tweak also violate direction. Honest direction keeps the person in review mode with inspectable state underneath. Direction is the user-facing half of the Collaboration Contract: the product prepares within bounds, the person guides, reviews, and owns authority where required. See sharing judgment for allocation detail.

Onboarding that teaches outcome sentences rather than feature tours reflects this distinction. Settings that expose endorsed knowledge and policy complement direction rather than replace it. Support playbooks that map relational complaints to memory and contract failures treat direction as an architectural concern. Enterprise products face the same pattern at scale: a clerk directs invoice resolution in domain language, a manager reviews exceptions, authority boundaries stay explicit, and direction without audit becomes risky.

Failure modes to design against

Isolated prompts treat each message as a fresh start, and the household re-explains busy Tuesday every week. Transcript theatre appends chat lines without state change. Regeneration theatre replaces the whole plan when one evening fails. Ceremonial direction shows approve buttons while hiding assumptions the household cannot contest. Each failure has an architectural owner. Isolated prompts lack working state. Transcript theatre lacks conversation becomes state. Regeneration theatre lacks persistence before regeneration. Ceremonial direction lacks contestability.

The mistake of fake controls compounds these failures. Approve buttons that do not reveal assumptions train passive acceptance. Regenerate buttons that erase accepted work train avoidance. Direction requires controls that match the Collaboration Contract. See passive acceptance theatre for the failure mode product teams confuse with simplicity.

Direction fails in small ways that feel large to households. The product acknowledges an utterance but applies it to the wrong day. The product updates chat tone but not working state. The product applies a week-level exception as permanent law. Each failure is fixable when teams treat direction as compilation to typed objects with diffs, not as sentiment analysis on messages. The Weekly Meal Companion succeeds when every direction utterance passes a simple test: name the state fields that changed, show the diff, preserve accepted work outside the change set, respect authority on purchase and medical deferral.

Measuring whether direction compiled

Product metrics for direction include correction latency, patch fidelity, override rates, and whether utterances produce durable state. Vanity metrics on message count miss whether direction compiled. Tracking utterance-to-state latency, the percent of utterances that produce inspectable diffs, override rate after direction, and re-ask rate for facts direction already settled reveals whether the product channels direction honestly.

If message volume rises while diff rate stays flat, the product is a chatbot, not a direction channel. "Direction compiled" is the metric that separates intelligence-native posture from feature AI.

Enterprise direction follows the same measurement pattern. Clerks say "escalate to vendor with partial credit." Managers say "hold until legal review." Direction compiles to queue state, assignment, and approval flags. Audit records who directed what. The pattern matches the kitchen: domain language in, structured state out, authority respected throughout.

Quarterly audits ask whether new features reintroduced feature-map navigation for tasks that households already phrase as outcomes. Each regression is a direction failure even when the new screen looks modern.

What to do next

The central test for direction is whether an utterance produces a state diff or only a chat line. Mapping primary user utterances to the state objects they update reveals whether direction is designed or remains a conversational gesture. The architectural connections run in both directions: intent over instructions describes how the originating sentence compiles to working state, while point and fix ensures that correction stays local after direction lands. Understanding how users judge the relationship over time connects direction to the broader trust question.

See co-pilot the decision and the rise of Thoughtware.

Read next: Products judged like people.