Decide what a page should do — before design begins

This helps teams get clear on what users need, what to say first, and how to structure the experience — all before a single component gets picked.

Start buildingSee the blocksRead the framework

---

The idea

Before you write a single word or pick a single component, answer three questions:

1

What is the user trying to figure out?

2

What does the content need to do about it?

3

What should they see first?

That's content blocking. A simple shift — from starting with layout to starting with meaning.

---

Before vs after

Before

• "Let's add a chart, a banner, and a CTA"
• "Content gets figured out after the design is already done"

After

• "What is the user trying to figure out?"
• "What do they need to hear first?"
• "OK, now what components support that?"