Methods / 05 working frameworksChanelle Henry

Ways to get from messy reality to a useful next move.

Frameworks are thinking tools, not ceremonial diagrams. These five help me locate the real system, translate evidence, account for human capacity, form products, and test demand before enthusiasm becomes expensive.

Explore the methods ↓
01Systems UX02Flare03R → B → B04Product 0 → 105Pre-Sell
01 / Systems UX

Find the system creating the interface problem.

Premise

Interface friction is often inherited from identity rules, organizational language, workflows, incentives, platforms, governance, or service boundaries. Fixing the visible layer alone preserves the source.

Use it when

A “simple UX issue” keeps returning, crosses teams, or changes shape depending on who touches it.

InterfaceInteractionWorkflowServiceOrganizationUnderlying system

Trace friction outward until the explanation becomes more useful than the symptom.

02 / Flare

Design for changing capacity, not an imaginary constant.

Premise

Human capability fluctuates with pain, fatigue, stress, attention, medication, environment, and time. A system that works only at full capacity is structurally inaccessible.

Use it when

People must complete important tasks under cognitive, physical, sensory, or emotional variability.

Low capacityVariableHigh capacity
Reduce memory loadPreserve progressOffer alternate pathsMake re-entry cheap

Capacity is a system input. Stop treating it like user error.

03 / Research → Blueprint → Build

Translate evidence before it hardens into features.

Premise

Research does not become a product merely because findings entered a slide deck. Evidence needs a translation layer connecting behavior, constraints, system decisions, and buildable priorities.

Use it when

A team has insight but no shared product model, or implementation has started before the problem became legible.

Researchbehavior · evidence · constraints
Blueprintmodel · rules · priorities
Buildproduct · workflow · measurement

The blueprint is where evidence becomes an accountable product decision.

04 / Product 0 → 1

Move from an interesting question to a testable product.

Premise

Early products need a disciplined sequence: name the expensive uncertainty, define the smallest useful behavior, create an instrumented experience, and learn before scale turns assumptions into architecture.

Use it when

The opportunity is real enough to explore but too uncertain to justify the whole machine.

0QuestionHypothesisBehaviorPrototypeSignalNext bet1

Build the smallest thing capable of making you change your mind.

05 / Pre-Sell

Test demand before polishing the machine.

Premise

Interest is cheap. Commitment is evidence. Pre-Sell makes the value proposition concrete enough that someone must spend money, time, reputation, access, or attention.

Use it when

A concept has enthusiasm but no proof that anyone will cross a meaningful threshold to get it.

Opinion
Click
Contact
Commitment
Payment / adoption

Move from applause to stakes.

Methods are useful when they sharpen judgment.

The diagram is never the deliverable. The better decision is.

← Back homeNext · Lab →