Discovery Is Not a Phase
Treating understanding as a gate to pass through — rather than a muscle to keep using — is how confident teams build the wrong thing.
The two-week lie
Most projects begin with a discovery phase that ends on schedule regardless of what was discovered. The findings deck is delivered, the build begins, and from that moment new information is treated as scope creep rather than signal. But the most important things a team learns about a problem almost always surface during the build — when real users touch real screens and real data breaks real assumptions.
The most important things a team learns about a problem surface during the build — when real data breaks real assumptions.
Budget for being wrong
We structure engagements so that roughly one day in ten remains discovery for the duration — user sessions, operational shadowing, assumption audits. It feels expensive until you price the alternative: weeks of polished work on a premise that died quietly in month two. The teams that ship the right thing aren't the ones that guessed right at the start; they're the ones that noticed fastest when they hadn't.
If this sounds like a conversation your team is having, we should have it together.