Cases & Experiments

Lab

A living timeline of build-in-public cases, experiment outcomes, and the lessons worth carrying forward.

Recent case timeline

Short, honest entries keep the lab useful. Each case records what changed, what happened, and what the next builder can borrow.

2026-04-18

Reframed the site around the solo-builder loop

Shifted the information architecture so the product story reads as discover, equip, navigate, ship, and connect.

Tools: Next.js, next-intl, product writing
Status: Shipped
Result: The site now has a clearer user journey instead of five disconnected pages.
Lesson: Navigation gets easier when every page has one job in the loop.

2026-04-16

Turned the tool page into a curated compass

Moved away from a generic grid and defined roles, best-fit moments, and solo gains for every pick.

Tools: Product curation, IA, copy design
Status: Validated
Result: The page became easier to scan and more opinionated without getting bloated.
Lesson: A short list with judgment is more useful than a giant directory without context.

2026-04-13

Defined the first downloadable OPC asset

Packaged the weekly operating loop into a compact PDF so the framework can travel outside the website.

Tools: Compass system, PDF asset, content packaging
Status: Learning
Result: The roadmap now has a tangible starter artifact instead of only page copy.
Lesson: A framework feels more real when people can put it beside their weekly review.

2026-04-10

Created the first lab-entry format

Standardized how experiments get logged so wins, misses, and next moves are visible in one place.

Tools: Lab template, review structure, editorial pass
Status: Running
Result: The project now has a repeatable way to show work instead of random update notes.
Lesson: A simple logging ritual is often the bridge between shipping once and shipping repeatedly.

The lab does not only celebrate wins. It also keeps the misses visible so the system gets wiser instead of noisier.

Win log

Keep the small proofs that deserve to become templates, habits, or public examples.

Kill log

Track the ideas, tools, and workflows that looked exciting but did not survive contact with real work.

Placeholder: loading.