Working Notes

A collection of public notes exploring design, products, language, and ideas. Some are detailed, some are rough, and many are still taking shape.

You don't need all devices to make good coffee
Writing is part of thinking
Version one is for learning
Use real content early
Tracking changes behaviour
Systems emerge through use
Small projects survive
Reading is not note taking
Question fiction like non-fiction
Paper slows thinking
One notebook system
Most projects take longer than expected
Keep unfinished ideas
Generalists have advantages
Focus requires subtraction
Focus is a skill
Files outlive software
Design is the process of elimination
Customers reveal reality
Convenience has tradeoffs
Collect examples before noticing patterns
Borrow ideas not workflows
Audience and customers are different
An antilibrary is a form of inventory
Look for rabbit holes
Focus on outcome, not output
Disconnect to connect
Ship-Show-Ask
Good meeting checklist
Draw over the screenshot
Third dimension to Eisenhower Matrix
Stop spending time on wireframing
Meetings are not the place to surprise people
Lots of inputs and a strong filter
Writing the way you think
Better thinking over better note-taking
Create to give
Building a boring task list
Accessibility is the first rule of functionality
Software design should be opinionated
LNO Framework
Design system branching in Figma
Fat-marker method
Pick your tools that serve purpose
Do less
Note titles are APIs for thought
Changelog as a consistent communication tool
Documenting meetings
Lego-like structure
Implementing a design system
Breadboarding over wireframes
Hype Doc
Keep user experience discussions at the product level
Credit your team
Explaining the obvious
Design debt as a performance indicator
Solve the problem not the feature
Notes grow in value when written to evolve
Write notes for yourself by default
Slam it shut and move on
You don't have to be the first with an opinion
Save screenshots
Non-linear note making