process

Who decides what goes in, how changes are proposed, and how the system stays coherent as more people touch it.

SYS·004Design system · Practice

How work gets from a product team into the shared system without either blocking the team or degrading the system.

SYS·007Design system · Practice

Structured feedback against stated objectives, which is a different activity from a decision meeting.

FLOW·001Workflow · Practice

Getting a design built correctly, which works better as a conversation than as a document.

FLOW·002Workflow · Practice

Checking the built thing against the intent, before release rather than after.

FLOW·003Workflow · Practice

Working out what problem to solve before deciding how, which is where most product failure is actually prevented.

FLOW·004Workflow · Practice

Choosing how finished a prototype needs to look, which is decided by the question you are asking rather than by taste.

FLOW·005Workflow · Practice

Deciding what to fix first, using evidence rather than the volume of the most recent complaint.

FLOW·006Workflow · Practice

Turn a pile of research into one statement narrow enough to design against and wide enough to allow more than one answer.

FLOW·007Workflow · Process

Generate enough distinct options that the first idea has to compete, then converge deliberately rather than by exhaustion.

FLOW·008Workflow · Process

Map the decisions, states and exits before drawing screens, because most missing work hides in the branches nobody drew.

FLOW·009Workflow · Process

Work out structure and priority while changes are still cheap, and stop before the fidelity starts answering questions you have not asked.

FLOW·010Workflow · Process

Pick one behavioural measure per goal, pair it with a quality measure, and decide the threshold before you look.

FLOW·011Workflow · Process