Articles on how to document findings after tests and make further product decisions under uncertainty. This category helps teams choose between iteration, retesting, changing the hypothesis, or abandoning an idea.
A prototype is not a miniature product. It is a decision tool — something you build specifically so an assumption you cannot see stops being invisible. The moment a user fumbles with a control, hesitates before confirming an action, or simply cannot find the thing you assumed was obvious, the assumption becomes a fact you can act on. The hard part isn’t building that moment. It’s knowing what to do the morning after.
A test just wrapped. The numbers are in front of the team, someone opens with “well, this basically confirms what we thought,” and within ten minutes the meeting has quietly turned into a defense of the idea everyone liked before the test even started. Nobody voted for that outcome. It just happened — because the human brain is built to skip the hard part of deciding and go straight to the comfortable part of agreeing.
You’ve probably run the numbers already. A mid-level IT hire costs somewhere in the £35,000–£45,000 range annually, and the managed service provider quote sitting in your inbox looks steeper on a monthly basis. Case closed, right? Except that comparison is a bit like comparing the price of a car to the price of a taxi ride and concluding the car is always cheaper — you’ve only counted the fuel, not the insurance, the repairs, the parking, or the years it sits idle in the driveway. When founders and small teams make IT staffing decisions this way, they’re not comparing costs. They’re comparing two different categories of financial and operational risk and pretending they’re the same number.
A stealth search sounds like the responsible move — quietly line up a replacement before anyone gets hurt, keep the team steady, avoid the drama of an open opening. Then the LinkedIn headline gets noticed, the candidate pool turns out to be three people your board already knew, and the VP you were trying to protect finds out anyway. What looked like discretion turns into the worst version of both an open search and a secret one.
Every founder eventually hits the same wall: too many signals, too little certainty, and a backlog full of ideas that all sound plausible. The instinct is to ask “what should we build next?” But there’s a sharper question hiding underneath it — one that Columbia Business School strategist Rita McGrath puts to CEOs before they touch a roadmap at all: what is this company actually centered on?
A founder runs a two-week test on a new onboarding flow. The numbers come back mixed — engagement up slightly, but a handful of users seem confused. In the debrief, one product manager wants to ship it. Another has doubts but says nothing, because the last time she pushed back, the conversation got tense and nothing changed anyway. The team ships. Three months later, they’re trying to figure out why adoption stalled — and nobody remembers that someone already saw it coming.
