# What to expect from your first 30 days with a design partner

- Link: https://s9studio.com/insights/first-30-days/
- Published: 2026-06-29T09:00:00+01:00
- Author: S9 Studio

A new partnership does not need to begin with a complicated process. It needs a 
clear understanding of the work, access to the right context, and a shared view 
of what progress should look like. The exact pace will depend on the project, but
a few early conversations help set the direction.

## Get aligned

Start with the business, the people using the product, and the decisions already
in motion. Existing research, customer feedback, working files, and technical context
help a design partner understand what has brought the team to this point.

Agree on the practical details too: who gives feedback, who makes final decisions,
and where conversations should happen. Clear expectations make it easier to spend
time on the work itself.

## Find the priorities

A new perspective usually reveals more possibilities than a team can pursue at once.
An initial review can help separate immediate friction from larger opportunities,
while identifying the questions that need more evidence.

Choose a small, understandable starting point. It might be a key journey, a visual
foundation, or a recurring interface pattern. The important thing is to connect 
that choice to a clear purpose and a realistic next step.

> The first month should make the next step clearer for everyone.

## Make it tangible

Early work should give the team something useful to discuss. A journey map, a low-
detail concept, or a focused visual exploration can make assumptions visible without
suggesting every decision is already settled.

Use those first reviews to learn how the team thinks. Specific questions and constructive
feedback help the design direction become more grounded, while showing which decisions
are ready to develop further.

## Set the rhythm

By the end of the first month, the working relationship should be easier to understand.
Priorities, review points, and responsibilities need to be visible, along with a
record of what has been learned and decided.

The next phase should follow from that shared understanding. This is an example 
of a useful starting rhythm rather than a fixed delivery promise: the right approach
stays responsive to the scale, constraints, and needs of the work.

## What to establish early

 * A shared view of the goals, constraints, and people involved.
 * A focused starting priority and useful early design work.
 * A clear review rhythm, decision process, and next step.