# UX strategy: frame before you design, the four-week method

> A four-week UX strategy and discovery method: immersion, right-sized research, problem statement, vision, principles, roadmap. Common pitfalls and examples.

- URL: https://vladispala.fr/en/blog/ux-strategy-framing-before-designing/
- Author: Vladimir Spalaikovitch (Vladispala), Senior UX/UI Designer, Product Designer and Digital Art Director, Paris
- Updated: 2026-09-30
- Version française: https://vladispala.fr/blog/ux-strategy-cadrer-avant-de-dessiner/

## Key facts

Framing means deciding which problem you solve, for whom, with what outcome and how success will be measured, before designing. A four-week sprint produces a vision, principles and a roadmap, and keeps you from quickly designing the wrong thing.


Framing means deciding what you are designing before you design it: which problem, for whom, with what expected outcome, under which constraints, and how you will know it worked. A four-week framing sprint produces a vision, principles and a roadmap. It keeps you from quickly designing the wrong thing.

## The cost of not framing

Three situations I have lived through or seen up close:

- Six months of development on a feature demanded by a single large client and used by nobody else.
- An onboarding redesigned three times because nobody had defined what "activated" meant.
- An expert calculator delivered to users who were not experts, then entirely reworked. That is the story of [Climeet](https://vladispala.fr/en/work/climeet/) before the simplified version.

In all three cases, four weeks of framing would have cost less than the fix.

## Week 1: immersion

### Stakeholders

A one-hour interview with each function involved: leadership, product, sales, support, engineering. Three questions: what works, what is blocking, what do you expect from this project. The differences between the answers are the first finding.

### What already exists

A screen-by-screen walkthrough of the current product, a feature inventory, a read of the last three months of support tickets, and an extraction of the available usage data (funnels, retention, task time). A review of three to five competitors to learn the market's conventions.

## Week 2: right-sized user research

The key word is right-sized. Research is scaled to the budget and the risk.

| Budget | Method | What it reveals |
|---|---|---|
| Minimal | Support tickets, reviews, usage data, internal interviews | The most frequent frictions |
| Standard | Five to eight 45-minute user interviews | Vocabulary, workarounds, expectations |
| In-depth | Interviews plus field observation plus a survey | Real usage, segments, frequencies |

Five well-run interviews reveal most of a flow's problems. Beyond eight, you confirm more than you discover. I synthesize with the help of AI to group quotes, then I reread everything: the method is described in [Prompt engineering for designers](https://vladispala.fr/en/blog/prompt-engineering-for-designers/).

## Week 3: articulate and decide

### The problem in one sentence

"HR managers lose an average of two hours per workwear allocation campaign chasing employees who have not entered their size, because the link they receive by email does not tell them how long it will take or why it matters." One verifiable sentence, with a user, a situation, a consequence and a cause. Everyone signs off on it.

### Segments and their critical tasks

Three to five usage profiles, each with its critical tasks, context and frictions. Not marketing personas with a first name and a photo: profiles that settle "the user wants" debates.

### Vision and principles

A one-page vision: what the product does for whom, and what it refuses to do. Then three to five design principles that will guide future trade-offs. Real examples: "never blocking," "first value before first configuration," "one primary action per screen."

### Metrics

What you will measure: activation, conversion, retention, task time, satisfaction, tickets. With the current value when it exists. Without metrics, framing remains an opinion.

## Week 4: roadmap and prototype

### Prioritization

Each opportunity identified is placed on two axes: impact for the user and the business, and effort estimated with the engineering team. The high impact, low effort quadrant becomes phase one. The rest is ordered and dated. And above all: an explicit list of what you will not do.

### Framing prototype

Three to six key screens, in Figma or in code, tested with a few users. Not to produce the final screens, but to test the riskiest assumptions before committing to the full design. This is the deliverable that turns a document into conviction.

## The pitfalls

1. **Framing without engineering**: a roadmap developers discover at the end does not stand a chance.
2. **Confusing framing with a requirements spec**: framing says what and why; it leaves the how to design.
3. **Too much research**: beyond what changes a decision, it is procrastination.
4. **No decision**: a framing that ends with "we should dig deeper" has failed.
5. **Forgetting what you will not do**: the list of things you give up is the most useful deliverable.

## After framing

Design follows naturally: [UX design](https://vladispala.fr/en/expertise/senior-ux-designer-freelance-paris/), [UI and product design](https://vladispala.fr/en/expertise/ui-design-product-design/), [design system](https://vladispala.fr/en/expertise/design-system/). The [UX strategy](https://vladispala.fr/en/expertise/ux-strategy/) page describes the engagement formats. And if you are unsure which profile to hire for this work: [How to choose a freelance UX designer](https://vladispala.fr/en/blog/how-to-choose-a-freelance-ux-designer/).

## Frequently asked questions

### How long does UX framing take?

Two to four weeks for a flow or a mid-sized product. Six to eight weeks when there are several stakeholders, several user segments or a heavy existing product to analyze.

### What does UX framing deliver?

A research synthesis, usage profiles, a map of current and target flows, a one-page product vision, design principles, a prioritized roadmap and, often, a prototype of a few key screens to test the main assumptions.

### Can you frame without talking to users?

You can start: support tickets, usage data, online reviews, internal interviews. But five user interviews reveal what the data does not tell you: vocabulary, workarounds, implicit expectations. Skipping them means deciding blind on the riskiest point.


---

Contact: https://calendar.app.google/1nHYAgzZcMcMqCbV7 · contact@vladispala.fr · https://www.linkedin.com/in/vladispala/
