Context Engineering

Summary: Once the behavior is selected, we must ensure it happens. We do not rely on willpower. We engineer the context (physical, digital, social) so that the behavior is the only logical outcome.

The Core Insight

Friction Determines Fate. Small amounts of friction kill behaviors faster than lack of motivation. We must smooth the path to near-zero resistance.

Engineering Levels

1. Default Architecture

• Opt-Out vs Opt-In: Make the target behavior the default state. (e.g., “Camera ON” at start of call).
• Pre-Population: Never ask a user for data you already have.

2. The “In-Stream” Trigger

Place the trigger directly in the user’s existing flow (identified in the Behavioral Audit).

• Bad: Send an email asking them to log into a portal.
• Good: Put the “Approve” button inside the email or Slack message.

3. Physical Constraints

Use “Forcing Functions.”

• ATM Example: You must take your card before cash is dispensed. The machine physically enforces the “Remember Card” behavior.
• Digital Example: You cannot hit “Submit” until the file is attached.

Output

A Context Spec. A set of design requirements for the product team that removes decision fatigue and friction.