Draft v2 - For Review
The Updraft Standard
The bar every screen, flow and component must clear before it ships.
TeamUpdraft - March 2026
Why This Exists
A customer once described using our plugins as "drinking from a firehose." That is the gap we are closing.
We have 7 million active installs and some of the most powerful WordPress tools on the market. The technology is world-class. But too many of our screens are overwhelming, full of jargon, and laid out for developers rather than the people who actually use them every day.
We used to call this "iPod" - borrowing Apple's language to describe what we wanted.
We are done borrowing. This is The Updraft Standard.
Software people actually want to open every morning.
What It Applies To
The Standard applies to every individual piece of UI that goes through review:
- A single settings screen
- An onboarding step or wizard flow
- A modal, dialog or confirmation
- A dashboard card or widget
- A notification, error state or empty state
- Any component a user will see and interact with
Think small. Review small. Ship small. Iterate fast.
The Seven Principles
- Obvious in 10 seconds. A user managing 50 sites does not have time to decode your screen. If they cannot tell what it does and what to do next within 10 seconds, it does not meet the Standard.
- Works before you configure it. Smart defaults. Auto-detection where possible. The screen does the thinking so the user does not have to. Configuration is available but never required up front.
- Power behind the door. We do not dumb things down. Advanced options exist - but they live behind a clearly marked toggle, never mixed in with the basics. Simple by default, powerful on demand.
- Every element earns its place. If something is on screen, it is there because it solves a real user problem or drives a business outcome. No filler. No "we built it because we could."
- The screen guides you. There is a clear visual hierarchy - what to look at first, what action to take, where to go next. The layout tells a story, not a phone book.
- Human language only. No jargon. No developer shorthand. If the label would confuse someone who is not a developer, rewrite it.
- It should make you smile. Great software isn't just functional - it rewards you. A confetti burst when a backup completes. A satisfying animation when you toggle something on. A witty empty state instead of a grey void. These moments are not polish - they are the difference between a tool people tolerate and one they love.
The 5-Point Test
Before any screen or flow moves to development, it must answer YES to all five:
- Can someone understand this screen and take action within 10 seconds?
- Does it show only what the user needs at this step? (Everything else behind a toggle or on another screen)
- Is every label written in plain English? (No jargon. If your mum would not understand it, rewrite it.)
- Does the layout guide the user toward the right next action? (Clear hierarchy, obvious CTA, logical flow)
- Would you enjoy using this screen every day? Not just tolerate it - actually look forward to it?
If any answer is "no" or "not sure" - it has not met the Standard yet.
How Feedback Works
Everyone involved in a review is encouraged to give honest feedback - on principles, usability, and yes, on taste. How a button looks, how a screen feels, whether the spacing is right - that stuff matters. Good design is functional AND beautiful.
The one rule: all feedback must be specific enough to act on.
Good feedback (principle): "This fails Test #3 - 'Gzip compression' means nothing to a non-technical user. Suggest 'Speed boost' or similar."
Good feedback (taste): "The border radius on these cards feels too sharp for our design system - try 12px to match the rest of the UI."
Not useful: "I don't like it" / "It doesn't feel right" / "Not good enough"
Gut feel is valuable for spotting problems. But vague feedback with no direction creates loops. If something feels off, take a moment to identify what feels off and what you would change. That is feedback the designer can actually use.
Who has final say and how reviews run is covered in the ReviewOS Process document.
What the Standard Is Not
- A reskin. Applying new colours to the same confusing layout does not meet the Standard. A polished firehose is still a firehose.
- Dumbing down. We serve agencies and developers who pay for power. The Standard means the simple path is default and the powerful path is one click away - not that we remove features.
- One person's taste. The Standard is a shared, written set of principles - not a veto card. Nobody blocks a design by saying "not good enough" without referencing which test it fails.
- A reason to delay. The Standard exists to ship better work faster, not to create review bottlenecks. Small pieces, quick reviews, keep moving.
- All business, no soul. Clarity without personality is a spreadsheet. We want people to enjoy using our products - that means room for wit, warmth, and the occasional surprise.
The Firehose Checklist
Red flags to spot and kill in any screen:
- The screen feels busy or overwhelming at first glance - too much competing for attention
- Technical jargon in any user-facing label
- No clear "what do I do first?" visual hierarchy
- Settings grouped by technical category rather than user task
- Nothing works until the user fills in settings - no smart defaults doing the heavy lifting
- No clear business reason for the element to exist
- The screen looks different but the actual user experience has not improved
- Advanced and basic options mixed together on the same level
Two or more? It is a firehose. Send it back.
Spark Check - before shipping, ask:
- ✦ Is there at least one moment that could make a user smile?
- ✦ Are success states celebrated, not just confirmed? (confetti > grey tick)
- ✦ Do empty states feel inviting rather than broken?
- ✦ Do transitions and animations feel smooth and intentional?
- ✦ Would you screenshot this and show someone?
Who this is for: Everyone involved in designing, reviewing, building or approving UI at TeamUpdraft. Developers, product managers, UX designers, support, leadership.
This is not a suggestion. This is The Updraft Standard.
The Updraft Standard: clear, obvious, human, earned, guided.