The working library / 87 articles
System Maps — Page 3
Processes you can follow: clear inputs, decisions, handoffs and ways to assess the result.
Field Notes explore an idea. System Maps lay out a process. Build Logs show the work behind it.
Browse topics
25–35 of 35 articles
System Maps · Better decisions · 2 min read
Past effort cannot make the next step worthwhile.
Review a struggling project using its remaining costs, realistic alternatives and current evidence.
System Maps · Better decisions · 2 min read
Make the downside legible before calling it a smart risk.
Design experiments around reversibility, exposure and what you need to learn.
System Maps · Better decisions · 2 min read
Different teams can be right about different parts.
Combine partial views before choosing a business-wide fix.
System Maps · Business operations · 2 min read
Protect the return to focus, not just the focus block.
Make interruptions less costly by preserving context and setting clear response expectations.
System Maps · Founder notes · 2 min read
A goal needs an operating rhythm.
Connect the result you want with a weekly practice and an honest review.
System Maps · Founder notes · 2 min read
Attach the new habit to something that already happens.
Use a stable cue and a small action to make a useful routine easier to remember.
System Maps · Founder notes · 2 min read
Change the cue, not just the resolution.
Inspect the environment around a repeated behaviour before relying on willpower.
System Maps · Growth & acquisition · 2 min read
Test the assumption before building the company around it.
Find the customer behaviour on which the idea depends and design a small, credible test.
System Maps · Better decisions · 2 min read
Review the belief that used to make you successful.
Look for assumptions that have become invisible because they were once reliable.
System Maps · Creative & production · 2 min read
One recording can support several useful pieces.
Build a repurposing workflow around complete ideas instead of arbitrary clip lengths.
System Maps · Creative & production · 2 min read
Make completion visible.
Design the end of a product or service interaction so people know what happened and what comes next.
Follow a question
Explore the collections.
Built from my working notes, scripts and documented projects, with AI assistance in adapting and organising the library. Research and published case studies are linked in the articles.
How this library was built RSS feed