Navigating Public Sector Innovation: Customer Discovery Without the Career Cliff Edge

What You Should Actually Do

The idea of stepping away from a stable public sector role to pursue an unproven concept can trigger a profound sense of fear. It’s not just about financial security; it’s about identity, purpose, and the perceived risk of failure. Before we talk tactics, acknowledge that feeling. It’s natural to want certainty, especially when your work has often been about providing stability for others. But what if you could gain significant certainty without taking the full leap?

This is where lean validation comes in. Your goal isn't to build a perfect product; it's to gather irrefutable evidence that your public sector solution is truly needed and desired. Think of it as a series of small, reversible experiments.

Here's how to approach customer discovery without burning your bridges:

1. Define Your Riskiest Assumption (The "Leap of Faith" Assumption): What absolutely must be true for your idea to succeed? Is it that government agencies lack a specific tool? That citizens are frustrated by a particular process? Don't assume; identify the core belief you're operating on. This is your first hypothesis to test.

2. Identify Your "Early Adopters" (The Problem-Havers): In the public sector, these aren't just "customers." They are the program managers, policy analysts, community leaders, or even citizens who are most acutely experiencing the problem your solution addresses. They are the ones actively seeking workarounds or expressing frustration. Where do they gather? What professional networks do they belong to?

3. Conduct Problem-Centric Interviews (Not Solution Pitches): This is critical. Your aim is not to sell your idea, but to understand their world. Ask open-ended questions about their challenges, their current processes, and how they cope. "Tell me about the last time you tried to achieve X. What was difficult about it?" "What tools do you currently use for Y, and what frustrates you about them?" Listen for their pain points, their workarounds, and their emotional responses. Remember Rob Fitzpatrick's advice: talk about their life, not your idea. Do they actually have the problem you think they have?

4. Prototype the Smallest Possible Solution (The "Minimum Viable Product" of Information): This isn't code; it might be a detailed mock-up, a flowchart, or even a simple landing page explaining the proposed service. The goal is to see if people would engage with it. Would they sign up for more information? Would they agree to a demo? This tests demand without requiring a full build.

5. Seek "Pre-Commitments," Not Just "Likes": A "that's a great idea!" is nice, but it's not validation. True validation comes when someone is willing to commit a scarce resource – their time, their reputation, or even a small amount of money – to your solution. Could you get a letter of intent from an agency? An agreement to pilot a small program? This is where the rubber meets the road.

What would you discover if you focused entirely on understanding the problem, rather than perfecting your solution?