What we do when there's no known solution
Most briefs arrive as a wish, not a spec. Here's the method we use to turn an unsolved problem into a buildable bridge.
A client rarely hands us a specification. They hand us a feeling: something here is harder than it should be. The work of the first week is turning that feeling into a problem you can actually point at.
Name the gap before the solution
We resist the urge to whiteboard features. Instead we map the current path step by painful step — where the work waits, who it waits on, and what it costs. The gap is almost never where people expect.
“If you can describe the gap in one sentence, you can usually build the bridge in six weeks.”
Borrow from adjacent solved problems
“No known solution” rarely means no solution exists anywhere. It means no one has assembled the pieces for this shape of problem. Our job is the assembly — and increasingly, AI is one of the pieces.
- Classify, summarize, and route — the unglamorous middle of most workflows.
- Draft the first version of anything a human then approves.
- Watch for the edge cases a rules engine would miss.
The bridge is built. The team crosses it. And the thing that felt impossibly hard three weeks ago becomes a Tuesday.