09/05/2026
Evidence Can Tell You What Not to Build
One of the most useful things evidence can do is tell you not to build something.
When you are working on a system that touches buyers, producers, logistics, technology and community organizations, it is easy to assume every promising relationship should become another integration or another layer.
Sometimes the better result is learning where the system should stop.
A conversation can show that an organization already has a workflow it wants to protect, that the proposed interface creates more work instead of less, or simply that the problem is being described in language that does not match how participants experience it.
That is still progress.
At INDYpendent Bytes, I want the operating model to get narrower as the evidence gets stronger—not larger just because more possibilities appear.
The goal is not to make every early assumption work. It is to keep testing until what remains is practical for the people expected to make the system function.