What good UX starts with and what teams skip when they’re in a rush.

five-planes-of-ux-strategy.png

<aside> <img src="/icons/book_yellow.svg" alt="/icons/book_yellow.svg" width="40px" />

Read The Five Planes of UX Series

Introduction to the five planes of UX — How to align your team from strategy to interface without the chaos.

  1. The strategy plane: start with the right problem — What good UX starts with and what teams skip when they’re in a rush.
  2. The scope plane: define what you’re building — How clear boundaries turn strategy into a plan your team can actually deliver
  3. The structure plane: organize the experience — How structure helps users move through your product without getting lost.
  4. The skeleton plane: shape the experience — How layout, navigation, and hierarchy guide what users notice and do.
  5. The surface plane: make it clear and trustworthy — How visual design earns trust and supports usability. </aside>

The Strategy Plane is where I always start. New product? New feature? Hopping into a messy experience? This is the first layer I reach for.

It helps me get my head around what’s really going on, what we’re solving, who it’s for, and what success actually looks like. Without that clarity, I’ve seen teams waste weeks chasing the wrong outcome or building something no one needs.

Most teams skip this step. They start with an idea, jump into features, and call it progress. But when strategy is missing, alignment falls apart. You end up with scattered decisions, rework, and a product that looks fine but doesn’t deliver.

The foundation of a successful user experience is a clearly articulated strategy.

— Jesse James Garrett

A strong strategy gives the work direction. It pulls everything into focus. It’s how you turn loose ideas into a product that’s worth building.

In this article, I’ll break down what the Strategy Plane is, how to work in it, and the tools, skills, and habits that keep it strong.

What the strategy plane is

The strategy plane defines the foundation of the product. It gets everyone aligned on the problem you’re solving, who you’re solving it for, and what success looks like.

This is where you connect user needs to business goals. It’s not just about being user-centered or checking a box. Strategy gives the work direction. It sets the focus for everything that comes next.

In Inspired, Marty Cagan calls this the foundation of meaningful product work — when product teams deeply understand both the customer problem and the company outcome they’re driving toward.

If this layer is weak or missing, the rest of the work suffers. I’ve seen teams spin on priorities, chase the wrong metrics, or ship something that looks good but solves nothing. When strategy is clear, it’s easier to say no to distractions and yes to what matters.

The important consideration here is to not build the roof of the house before you know the shape of its foundation.

— Jesse James Garrett

This isn’t about making it perfect. It’s about getting the big questions out in the open so the team can move forward with purpose.

How to work in the strategy layer

Working in the strategy layer means slowing down just enough to define what you’re doing and why. That doesn’t mean writing a long brief or running a weeks-long discovery sprint. It means getting clear on a few core things before jumping into solutions.

Here’s what that looks like:

1. Define your outcome.