The work
The moments we design
What we learn from the people inside the business.
- Business goals
- Operational constraints
- Technical limits
- Sales and support knowledge
- Legal and compliance needs
- Who decides what
- Conflicting opinions
- Existing research and data
- Success measures
- Risks and assumptions
- A shared problem statement
- What to build first
The problem
Sounds familiar?
If 2 or more of these ring true, talk to the business before designing.
{{ countLabel }}
Proof
“She asks strong questions, communicates fast, works smoothly in Slack and Linear, and delivers high-quality Figma designs that fit our design system.”
- Upwork Job Success
- 100%
- Regular clients
- 10+
- Recognized by
- Dribbble Select
Ways to start
2 ways to start
Align a team on a new product, or on a big change.
-
# New product
Align the team
Capture goals, constraints and knowledge before work starts.
- Stakeholder interviews
- Goals and constraints
- Shared problem statement
- Short findings report
-
# Big change
Untangle opinions
Bring conflicting views together before a redesign or major feature.
- Stakeholder interviews
- Where views differ
- Decisions to make
- Short findings report
01Who do you interview?
The people with goals, knowledge or veto power: leadership, sales, support, engineering, operations and anyone else who shapes the product.
02How long does a project take?
It depends on the scope. Once we’ve seen the full picture, we’ll share a rough timeline.
03How many interviews do you run?
Usually 4 to 10, depending on the size of the team and the decision.
04What do we get at the end?
A short report with goals, constraints, open questions and where people disagree.
05Can this happen alongside user research?
Yes. The two work well together: one shows what the business needs, the other what users need.