04 / Knowledge
Ideas made useful.
Notes from building products, leading teams, teaching design, and building companies. No recycled advice. Only ideas tested through real work.
Featured
Product · 8 min
Stop designing screens. Start designing decisions.
Most design problems are not screen problems. They are decision problems wearing a visual disguise.
All notes
Leadership · 9 min
A design team does not need more meetings. It needs a critique system.
More review time does not create better work. Clear standards, visible decisions, and useful feedback do.
Read note →
AI · 10 min
AI products do not earn trust by sounding intelligent.
They earn trust by being useful, understandable, correct enough, and easy to control.
Read note →
Systems · 8 min
Products fail when the operating model stays invisible.
Teams do not need perfect process. They need a shared view of how decisions get made.
Read note →
Learning · 7 min
Teaching design through decisions, not decoration.
Students improve faster when they can explain why they made a choice, not just show what they made.
Read note →
Founder · 11 min
Building Growing With Kid with less money than most teams spend on tools.
Constraints did not make the work easier. They forced the product to become clearer.
Read note →
Frameworks
Methods I actually use in the room.
01
Decision Stack
Work the decision, not the layout. The screen usually becomes simpler.
Read in the note →
02
Critique System
Quality visible before the review starts. Opinion with a meeting link is not a craft system.
Read in the note →
03
AI Trust Stack
Fluency is not competence. Trust is a product surface.
Read in the note →
04
Product Operating Model
Products fail when nobody can see who decides, when, and with what evidence.
Read in the note →
05
Visible Learning Loop
Students improve faster when they can explain why they made a choice.
Read in the note →
06
Product Filter
Ship the smallest thing that answers three questions. Constraint is the editor.
Read in the note →
Founder OS