Find the real question.
Research is useful when it changes what gets built.
I ask a lot of “why” questions. Then I make something and see if I was right.
I like staying close to a problem, from the first messy conversations through prototypes, feedback, implementation, and whatever needs fixing next. A rationale helps, but it doesn't make a design correct. People using it get the final vote.
Values.
Make it tangible early.
A prototype creates a better conversation than a polished explanation.
Stay for the messy part.
Edge cases, content, and implementation are part of the design.
Let feedback change it.
Change one thing. Pay attention. Let what happens next inform the work.
Room to
be curious.
Fast laps, long runs, open air. And time to slow down and actually look at something.
Karting is where I first noticed how fast good feedback can be. Change one thing, take another lap, and you know almost right away whether it worked.
Read what I’m thinking aboutA couple of
moments along the way.
From making the work
to sharing it.
