The Duct Tape Test: Finding Demand in Workarounds
Updated
Knowledge on this page was mainly distilled from Critical Demand Signals Nobody Talks About.
Why Workarounds Beat Wishes and Complaints
Community signals form a hierarchy. Wishes ("someone should build X") cost zero effort and mean almost nothing. Complaints ("I'm frustrated with X") are better but often point toward feature requests for existing tools. Workarounds ("I've been using tool A plus tool B to kinda do thing C") are the gold standard, because the person has already crossed the activation-energy threshold from annoyance to action.
Running the Duct Tape Test
Look for three conditions before committing to a product idea:
- Different wrong tools. Multiple people solving the same problem with different tools. If everyone uses the same tool, you are looking at a feature request, not a new product opportunity.
- Barely functional solutions. The workaround works well enough to keep using but is fragile enough to curse at. People will not abandon something that is "fine."
- Independent invention. People arrived at similar workarounds without coordinating. When the same pattern emerges independently, you are seeing genuine structural demand.
Check Adjacent Spaces
Do not limit your search to your exact niche. When people in related fields independently hack together the same kind of solution from completely different tools, the problem is structural. Zapier's founders found integration pain across Evernote, Salesforce, and Dropbox forums. ConvertKit's Nathan Barry saw professional bloggers frankensteining Mailchimp with WordPress plugins and manual tagging. No single community asked for the product. Dozens independently proved the demand.
Read the Shape, Not Just the Existence
A workaround's shape tells you what to build first. Someone stringing together three tools is not asking you to replace all three. They might love two of them. What they hate is the glue: the manual step, the copy-paste, the thing that breaks at 2 AM. Build the bridge that fixes the painful seam, not a general replacement that competes with tools people already like.
Q&A
What is the duct tape test?
It is a pre-build validation method that looks for people who have jury-rigged solutions from tools never designed for the job. You check for three conditions: multiple people using different wrong tools, solutions that barely work, and independent invention. All three together indicate urgent, unmet demand.
Why are workarounds stronger demand signals than complaints?
Workarounds prove someone invested real time and effort to solve the problem. Complaints only prove annoyance, and they often point toward feature requests for existing products rather than opportunities for new ones. The activation energy required to build a workaround filters out mild inconveniences and surfaces genuine urgency.
What does 'independent invention' mean in this context?
It means multiple people arrived at similar workaround solutions without coordinating or copying each other. When the same pattern emerges independently across different people or communities, you are seeing structural demand rather than one person's quirky workflow. This is one of the strongest indicators that a real market exists.
How do adjacent-space workarounds help validate demand?
When people in related but different fields build the same kind of brittle solution from completely different tools, the problem transcends any single niche. Zapier was validated this way: no single community asked for it, but dozens of communities were independently duct-taping app integrations together. Adjacent-space signals confirm the problem is structural, not personal.
What mistake do founders make after spotting a workaround?
The most common mistake is building a general replacement for all the tools in the workaround instead of fixing the painful seam between them. Someone using three tools does not necessarily want to abandon all three. They hate the glue, the manual step that breaks. Building a complete replacement creates adoption friction against tools people already like.
What if the workaround is so embedded nobody recognizes it as one?
Some workarounds become invisible because they have existed longer than anyone has been paying attention: spreadsheets doing database jobs, browser tabs pinned as dashboards, manual Monday-morning processes. These represent the deepest demand because the friction is normalized. If you can spot one, you are looking at demand so deep the market does not know it has it.
Does the duct tape test work for category-creating products?
Not well. Nobody was jury-rigging an iPhone in 2006. The duct tape test is designed for discovering existing demand, not creating new categories. At the indie scale, most successful products solve problems people are already working around rather than inventing entirely new behaviors.
How does urgency relate to workarounds?
Urgency is the filter that separates real opportunities from interesting observations. If people tolerate the problem without building workarounds, urgency is low. If they invest significant time duct-taping together brittle solutions, urgency is high. The presence and complexity of workarounds is a direct proxy for how urgently people need a better answer.