Thinking
What’s happening isn’t always the problem.
Symptoms are easy to spot. Systems take longer to understand.
We spend our time on the second part.
We watch the handoffs, exceptions, incentives, and workarounds. We listen to what people say the problem is, then look at what the system is actually producing.
Because the quality of what you build depends on the quality of what you understand first.
Look closer
Keep looking and you find the workaround underneath it. The incentives behind it. The assumptions nobody revisits. The systems that make the same problem happen again.
That’s where things get interesting.
A better answer does not always mean more technology, more features, or more process.
The answer is rarely one feature. Durable improvement often requires the pieces around the problem to work together—workflow, judgment, incentives, trust, information, and accountability.
Sometimes it means removing ambiguity. Connecting what has been fragmented. Putting judgment closer to the moment it is needed. Giving someone clear ownership of an outcome that previously belonged to everyone and no one.
We look for the point where those pieces can be recomposed into a better system—one that makes the work easier to understand, more reliable to perform, and more valuable to the person on the other side of it.
Better is not what looks more advanced.
Better is what works better.
We aren’t particularly attached to software, services, marketplaces, or any other category.
We’re attached to good answers.
We follow the problem far enough to understand what it actually requires. Then we choose the form that gives the answer its best chance to work.
A clever concept is not the finish line. The answer has to become usable, trustworthy, and durable enough to enter real operating life.
The form follows the problem.
See the L3 view →