How clear boundaries turn strategy into a plan your team can actually deliver.

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.

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

Scope is where strategy starts to get real.

You’ve aligned on the problem. You’ve got a clear outcome. Now you need to decide what you’re actually going to build — and just as important, what you’re not.

This is where teams start to spin. Someone adds “just one more feature.” Stakeholders chime in with ideas. Engineers want to future-proof. Designers want to fix five other things while they’re in there. Before you know it, the work bloats. Deadlines slip. The original problem gets buried.

The scope of the product is directly influenced by the strategy behind it.

— Jesse James Garrett, The Elements of User Experience

You can’t define scope in a vacuum. It’s the bridge between why you’re building and how it’s going to work.

When you do it well, scope brings clarity. It gives the team something solid to build on. It helps you say no to distractions and yes to what matters.

In this article, we’ll break down what the scope plane is, how to define it, and what tools, skills, and habits help teams stay focused.

What the scope plane is

The scope plane is where you define the boundaries. What’s in, what’s out, and what it all needs to do.

It sits between strategy and structure. You’re not designing yet — you’re getting specific about the functionality and content that will support the user and business goals you already defined.

Jesse James Garrett breaks it into two parts:

Functional specs — What features will the product include? What behaviors and interactions are expected?
Content requirements — What types of information need to show up? Think descriptions, media, help text, or supporting materials.

It’s the same layer where Melissa Perri sees teams slip into what she calls the “build trap” — shipping features with no real connection to user or business outcomes. Getting clear on scope helps you avoid that pattern.

This is the layer where trade-offs happen. You balance user needs with business objectives. You say no to things that don’t serve the strategy. And you write things down clearly so the whole team knows what’s being built.

When teams skip this layer or treat it like a wishlist, things get messy. Scope creeps. Decisions get revisited. Structure and design suffer. But when the scope is clear, the rest of the work gets a lot smoother.