mindit-consequence

mindit-consequence

The fourth of the eight forces. Run this when the question is "what does this foreclose, and what does it open."

The force

Every design decision opens some doors and closes others. Some closures are visible: a destructive delete button removes data. Most closures are invisible: a choice of data model now means a redesign in six months. A default that nudges 70 percent of users one direction shapes the company's product strategy. A consent flow written today defines what the company can do with user data forever.

Consequence asks: of the doors this design closes, which ones did the team know they were closing?

When to run this

• The user is about to ship a destructive flow (deletion, cancellation, payment, account changes).
• The user is choosing a default (default sort order, default privacy setting, default plan).
• The user mentions data: what gets stored, what gets exposed, who can see it, how long it is kept.
• The user uses words like "irreversible," "side effect," "knock-on," "future," "blocks us from," or "locks us in."
• The user is choosing between two architectures or two information models and asks for a review.

How to analyze

1. Surface the action. What does this design do? What does it cause to happen, both immediately and downstream? Write it out plainly.

2. Walk the five dimensions. For each criterion below, ask: what is this design closing or opening on this axis?

3. Look for invisible closures. Most consequence failures are not in the obvious "delete account" button. They are in defaults, in data models, in what the design assumes the next feature can do.

4. Surface unmade decisions. "What happens if the user changes their mind in three months" is often unmade. Surface it. Do not invent the answer.

5. Check anti-patterns.yaml.

6. Write the artifact.

Rubric

Criterion	Weight	What you are scoring
Reversibility	0.20	Can the user undo what this design lets them do? Within what time window? With what cost?
Path foreclosure	0.20	Does this design make other user paths harder, slower, or impossible? (Often by adding friction to one path or removing it entirely.)
Data implications	0.20	What gets stored as a result of this design? Who can see it? How is it deleted? Is the answer to all three known?
Future-design lock-in	0.20	Does this design constrain what the team can do in the next version? (Information architecture, naming, defaults, data shape.)
Second-order effects	0.20	What knock-on effects on adjacent features, the support team, the data team, or other surfaces?