What makes
software useful?
Notes on the problems we choose, the products we build, and the decisions behind our software companies.
LATEST ESSAY / Company buildingGrowth the business can support.
Ambition needs an operating foundation that can carry the promises a company makes.
Read the essayFrom the studio.
22 ESSAYS / THE STUDIO JOURNAL
A useful dashboard leaves room for unknowns.
The difference between a clear operating picture and a reassuring collection of numbers is often the treatment of missing information.
Write decisions so work can continue.
A short decision record can preserve the reasoning, responsibility, and boundaries that a status update leaves out.
The best lead is not always the loudest signal.
For recruiting-client research, source quality and account fit matter more than the apparent volume of hiring activity.
The discipline of leaving things out.
A stronger product is often the result of clearer choices about what belongs in the experience.
A client handoff needs an acceptance test.
A folder full of files can still leave a project blocked. The missing ingredient is often agreement about what counts as usable.
Context should travel with the work.
A useful handoff preserves decisions, sources, and open questions—not simply the largest possible transcript.
Give every company a reason to exist.
A venture studio earns its coherence through clear company purposes and deliberate allocation of attention.
Software exits are part of the product.
A renewal decision is incomplete until the team understands what it would take to leave.
Payment follow-through with clarity.
A useful receivables workflow separates the facts, the agreed next step, and the communication that follows.
The work before the work.
Project readiness is a design problem. Better inputs can make the start of a client engagement clearer for everyone involved.
Renewals are decisions, not just dates.
A calendar reminder is a beginning. A useful renewal process gives someone enough context to make a considered choice.
Support is where a product explains itself.
The moment someone gets stuck reveals whether the product’s promises have an operating system behind them.
An interesting idea is only the beginning.
The distance between a compelling concept and a useful company is covered by a series of specific, sometimes unglamorous decisions.
A payment promise is not a payment.
Keeping promises, receipts, and disputes separate makes payment follow-through more accurate and more respectful.
Automate the repeatable. Protect the judgment.
Good automation makes routine work dependable and consequential decisions easier to inspect.
When a research source goes stale.
Research quality depends on knowing when the evidence was checked and what a change in the source means.
Price the responsibility you take on.
A clear commercial offer begins with the outcome, the boundaries, and the ongoing work behind it.
The cost of a small change.
A request can be easy to describe and still create substantial work across a project.
Onboarding is the first delivery.
The opening minutes of a product should help someone accomplish something worth returning for.
The brief is a product decision.
A useful brief identifies what the work must resolve—and gives the team permission to leave other things alone.
The first customer changes the question.
A useful early customer relationship turns assumptions into specific choices about the product.