Thinking

Ideas that inform how we work.

Not a blog. Not a portfolio. A record of how we think about the problems we help people solve.

01

Why "Move Fast and Break Things" Was Always Bad Advice

Speed and carelessness are different things. The fastest teams are the most deliberate ones.

Read →
02

The Prototype Is the Argument

Product disagreements are competing mental models. The only way to resolve them is to build.

Read →
03

What NASA Gets Right About Product Requirements

The cost of vagueness is paid downstream, and it is always higher than the cost of specificity upstream.

Read →
04

The Best Products Are Designed Backward

Start from the experience you want someone to have, then work backward to the code.

Read →
05

Constraints Are Not Obstacles. They Are the Work.

Constraints are the creative material. Abundance is the enemy of clarity.

Read →
06

Why Every Software Project Needs a Minimum Viable Process

The opposite of no process is not heavy process — it is the smallest set of agreements that lets a team operate.

Read →
07

The Hidden Cost of the Last 10%

The last 10% of scope takes 40% of the time. Shipping discipline is a skill.

Read →
08

Observation Is a Design Tool

The most important design tool is not Figma. It is attention.

Read →
09

MVP vs. Prototype: Which Do You Actually Need?

They answer different questions and fail in different ways. Choosing the wrong one wastes months.

Read →
10

How Much Should an MVP Cost?

“It depends” is a real answer — here is what it depends on, and the ranges that follow.

Read →
11

Product Studio, Freelancer, or In-House: How to Choose

Each is the right answer sometimes. The wrong choice shows up months later as rework.

Read →
12

When Workflow Automation Is Worth Building

Not every manual process should be automated. Here is how to tell which ones pay off.

Read →