Frameworks

The Gap-Bridging Discovery Method

· Felix Lenhard

Every business idea that worked — every single one I have seen succeed across two decades of innovation consulting — started in the same place. Not with inspiration. Not with a flash of brilliance. With a gap.

A gap between what exists and what is needed. Between what people are doing and what they wish they could do. Between the current state and the desired state.

The Gap-Bridging Discovery Method is a structured way to find these gaps systematically instead of waiting for inspiration to strike. It works because it looks at reality first and invention second. Most aspiring founders do the opposite — they invent something and then look for someone who needs it. That is backwards.

Find the gap first. Then build the bridge.

The Three Types of Gaps

Not all gaps are created equal. Understanding which type you are looking at determines how you approach building the solution.

Gap Type 1: The Performance Gap

What exists works, but not well enough. The customer has a solution, but it is slow, expensive, complicated, unreliable, or frustrating.

Examples:

  • Spreadsheets for project management (functional but painful at scale)
  • Manual invoicing (works but takes hours)
  • Generic email marketing platforms (do the job but lack features for specific industries)

Performance gaps are the easiest to identify because customers are already vocal about their frustrations. They are using something. They just wish it were better.

The challenge: competition. If the gap is obvious, someone is probably already trying to fill it. Your bridge needs to be meaningfully better — not 10% better. At least 3x better in one dimension that matters to the customer.

Gap Type 2: The Access Gap

A solution exists, but not for everyone. Certain groups are excluded by price, complexity, geography, language, or knowledge.

Examples:

  • Enterprise software that small businesses cannot afford
  • Financial planning available to high-net-worth individuals but not to the middle class
  • Business education in English that is not available in German-speaking markets

Access gaps are powerful because the solution already works — you do not need to prove the concept. You need to make it reachable. Lower the price, simplify the interface, translate it, localize it, or redistribute it through a channel that reaches the underserved group.

The Austrian market is full of access gaps. Services and tools that exist in the US market but have not been adapted for DACH business culture, language, or regulatory environment. I built parts of my consulting practice on exactly this gap — bringing frameworks that worked internationally and adapting them for Austrian founders.

Gap Type 3: The Awareness Gap

The customer does not know a solution could exist. They have accepted the problem as “just how things are.” They are not searching for a solution because they do not believe one is possible.

Examples:

  • Before ride-sharing, most people accepted that getting a taxi required calling a dispatcher
  • Before cloud storage, most people accepted that files lived on one computer
  • Before AI writing tools, most people accepted that content creation required a human for every word

Awareness gaps are the hardest to find and the most valuable to fill. The customer is not looking, which means traditional market research (“what are you searching for?”) will not reveal it. You find awareness gaps by observing behavior — watching what people do, noticing the inefficiencies they do not complain about because they have normalized them.

The Discovery Process: Step by Step

Step 1: Choose Your Observation Domain

You cannot observe gaps everywhere. Choose a specific domain — an industry, a role, a process, a demographic. The narrower, the better.

Ideal domains are ones where you have direct experience or access. If you have worked in restaurants, observe restaurant operations. If you are a freelance designer, observe freelance business management. Your existing knowledge is an advantage — you will notice things an outsider would miss.

Step 2: The Friction Log

Spend one week actively logging every point of friction you observe in your chosen domain. Friction means any moment where someone:

  • Complains about a process
  • Works around a limitation
  • Does something manually that could be faster
  • Spends time on a task that produces no value
  • Expresses frustration, confusion, or resignation

Write each one down with specifics. Not “invoicing is annoying.” Instead: “Maria the freelancer spends 45 minutes every Friday manually creating invoices in Word because she thinks accounting software is too complicated for her three monthly clients.”

The specifics matter. “Invoicing is annoying” is a vague observation. “45 minutes every Friday in Word for three clients” is a gap you can measure and bridge.

Step 3: Quantify the Gap

For each friction point, estimate the cost of the gap:

  • Time cost: How much time does this waste per week/month?
  • Money cost: What is the financial impact?
  • Emotional cost: How much frustration or stress does it create?
  • Opportunity cost: What could the person be doing instead?

The total cost of the gap is the maximum value of your bridge. If the gap costs EUR 500/month in time and frustration, your solution can charge up to that amount and still be a clear win for the customer.

This connects directly to the value equation. The bigger the gap, the more valuable the bridge, and the more you can charge.

Step 4: Validate the Gap with Conversations

Your friction log is a hypothesis. Validate it with real people. Use the 5-conversation sprint to confirm:

  • Is this gap real for more than just the people you observed?
  • Is it painful enough that people would pay to close it?
  • Are current alternatives inadequate?

If three of five people confirm the gap, you have something. If they do not, pick a different friction point from your log and validate again.

Step 5: Design the Minimum Bridge

The bridge does not need to be a complete product. It needs to be the minimum intervention that closes the gap enough that the customer feels the difference.

For the freelancer invoicing problem, the minimum bridge might be a pre-formatted Google Sheets template with formulas that auto-calculate totals and generate a PDF. Not a SaaS platform. Not an app. A template.

The minimum viable experience principle applies: deliver the outcome with the least complexity. You can build a more sophisticated bridge later, after you have confirmed that people cross it.

Gap-Bridging in Practice: A Case from Startup Burgenland

A founder observed that small hotel owners in Burgenland were managing their online reviews manually — checking Google, Booking.com, and TripAdvisor separately, responding to each one individually, and having no system for tracking sentiment over time.

The gap: Fragmented review management for small hospitality businesses.

The friction log revealed: Average hotel owner spent 4-5 hours per week on review management. They missed reviews regularly. Their response time averaged 3-4 days, which hurt their online ranking.

Gap quantification: 4-5 hours/week at an estimated EUR 30/hour = EUR 120-150/month in time. Plus the revenue impact of slower response times and missed reviews — harder to quantify but meaningful.

Validation: Four of five hotel owners confirmed the problem was significant and said they would pay for a solution.

The minimum bridge: A simple dashboard that aggregated reviews from three platforms, sent a daily email digest, and provided response templates. Built in three weeks.

Result: First ten customers within a month. The bridge worked. They later expanded the product, but the initial minimum bridge was enough to validate the business.

Finding Gaps Others Miss

The most valuable gaps are the ones that are invisible to most people. Here is how to see them:

Talk to people who just started. Beginners notice friction that experts have normalized. Ask someone in their first month of freelancing what is confusing. They will give you a list of problems that ten-year freelancers have stopped seeing.

Watch workarounds. When people build elaborate workarounds — spreadsheets that mimic software, physical processes that compensate for digital gaps, informal systems that substitute for formal ones — they are telling you a gap exists. The workaround is proof of demand.

Follow the complaints. Online forums, review sites, and social media are full of people describing gaps. Search for your domain plus “frustrated,” “annoying,” “wish there was,” or “why is there no.” Each complaint is a gap report.

Cross-pollinate from other industries. A solution that is standard in one industry might not exist in another. Healthcare scheduling solved problems that event management still faces. E-commerce checkout optimization could apply to SaaS onboarding. Look at what other industries have built and ask whether it applies to your domain.

Takeaways

The Gap-Bridging Discovery Method replaces waiting for inspiration with a systematic search. Choose a domain. Log the friction. Quantify the gap. Validate with conversations. Design the minimum bridge.

Every successful business exists because it bridges a gap between what is and what could be. The founders who succeed are not the most creative. They are the most observant. They see the gaps that others have accepted as normal.

Start logging friction today. In your own work, in your industry, in the daily complaints of the people around you. The gaps are everywhere. Most people walk past them. You are going to build bridges.

For the broader system of going from gap to product, see ship it ugly for getting to market fast, and the revenue engine for turning the bridge into a business.

discovery opportunity

You might also like

frameworks

The Speed-to-Architecture Transition Guide

When to stop moving fast and start building structure.

frameworks

The Hire-or-Don't-Hire Decision Tree

Before you add headcount, run through this.

frameworks

The Exit Signal Checklist

12 signals that your business is ready to sell, scale, or shift.

frameworks

The Surface-Test-Ship Chapter Format

How every chapter in Subtract to Ship is structured. Use it for your content.

Stay in the Loop

One Insight Per Week.

What I'm building, what's working, what's not — and frameworks you can use on Monday.