design-express

Design Express (the On-Ramp)

The full Designpowers pipeline is powerful and the right tool for real work — but it's a lot to commit to in someone's first three minutes, especially for a designer new to the terminal. Express is the on-ramp: the fastest possible loop from "I have a thing" or "I want a small thing" to "here's something useful," in plain language, then a clear door into the full team.

Express is a gateway, not a bypass. Designpowers' whole thesis is process over guessing — its anti-patterns explicitly name "this is too small to need discovery" and "let me just quickly build this" as failures. Express does not contradict that. It is a taster that pulls people into the process, with three lines held firm:

1. Accessibility is never skipped. It's "not a phase" — it stays in even here. No express output ships an inaccessible result.
2. Express output is always labelled "a starting point, not a finished design." Never presented as done.
3. The upward bridge is the point. Every express result ends by offering the full team. Conversion into the real workflow is the goal, not a quick exit from it.

When to Use

• A first-time user who seems hesitant, or explicitly wants something quick ("just take a quick look", "can you knock together a…", "I only have a minute")
• A designer new to the terminal who freezes at the full pipeline
• Offered proactively to first-time users right after the guided walkthrough (see using-designpowers)

Do NOT use for:

• Returning users (taste profile exists) — they know the system; route them to the Build or Review lane.
• Real project work — once the user is engaged, move up to the full pipeline. Express is the first two minutes, not the whole job.

If you're unsure whether someone wants express or the full thing, default to offering express to first-timers and the full lanes to everyone else.

Plain-Language Rule (applies to everything below)

Express talks like a helpful colleague, not a spec.