Screens you can build from
Every state of every screen in the scope: empty, loading, error, and the one with 4,000 rows.
How I work
What you get when you hire me, in detail: the files, the rhythm of a sprint, where the hours go and what happens after I leave.
Booking work from March
Services and rates
What you'll have at the end
Real files in your workspace, not a presentation. Each one is something your team can use the next morning.
300
Strings, written
A typical sprint ships about 300 labels, hints and errors, ready to paste.
Research notes, in plain words
What I heard, what I think it means and what I'd do first.
A flow map
Every path through the flow on one page, with the edge cases named.
A small, named system
Tokens and components your engineers can keep using after I leave.
A six-week sprint, week by week
Shorter sprints drop the second round of research; the rhythm stays the same.
- Week 1
Listen
Five calls with customers and a day with your support inbox. I write down what I hear before I draw anything.
- Week 2
Map
The flow on one page, with every path and edge case named. We agree on it before screens.
- Weeks 3 and 4
Draw and write Most of the work
Screens and words together, shared as they happen, with a video every Friday.
- Week 5
Test
Five more customers try a clickable version. We fix what trips them up.
- Week 6
Hand off
An hour with your engineers, annotated files and a month of answers.
Where the time goes
From my own time tracking. Less of it is drawing than people expect.
Show the data
| Phase | Hours |
|---|---|
| Screens and states | 44 |
| Flows | 26 |
| Research | 18 |
| Words | 12 |
| Handoff | 10 |
1,610 hours
- Client work 62%
- Writing 13%
- Research visits 11%
- Admin 9%
- Learning 5%
Show the data
| Activity | Share |
|---|---|
| Client work | 62% |
| Writing | 13% |
| Research visits | 11% |
| Admin | 9% |
| Learning | 5% |
The practice, in four numbers
- Years independent
- 11
- Since leaving an in-house team in 2015.
- Clients at a time
- 2
- Never more, so you get real attention.
- Typical project
- 8 wks
- From kickoff to handoff.
- Reply time
- 2 days
- Working days, every email.
Tools and habits
Paper first
Every flow starts as a sketch in a notebook. Cheaper to throw away.
Your design tool, not mine
I work in whatever your team already uses, in your workspace.
Close to the code
I read your front end and can open a small pull request for copy changes.
Sound like the right rhythm?
Book thirty minutes and tell me about the flow that worries you most.