How to Interview Government Employees About Problems

Government employees will talk candidly about broken workflows and real, felt operational pain — this population is often genuinely eager to discuss problems they deal with daily — but getting good signal requires respecting two specific considerations most other B2B discovery interviews don't involve: procurement sensitivities (a government employee needs to be careful not to appear to be favoring a specific vendor before any formal process begins) and public-records rules (communications with government employees can, in many jurisdictions, become subject to public-records requests). Interviewing this population well means recruiting through the right channels, structuring conversations to respect these specific sensitivities, and synthesizing findings with an accurate understanding of who actually holds budget authority versus who simply described the problem.

Quick Answer: Recruit government employees through professional associations specific to their role (city managers, public works directors, permitting officials each have their own associations), conferences, and warm referrals, similar to other regulated-buyer populations covered elsewhere on this site. Frame your outreach and questions around understanding the problem generally, not around your specific product, to avoid triggering procurement-fairness concerns before any formal process exists. Recognize that public-sector email and other communications can, in many jurisdictions, be subject to public-records requests, and communicate accordingly.

Prerequisites: Stakeholder Table

Step 1: Recruit Through Professional Associations and Warm Referrals

Recruit through the specific professional association relevant to your target role — city/county management associations, public works associations, and role-specific professional groups all hold regular events and maintain active online communities — and prioritize warm referrals once you have a few initial contacts, since government employees, like the professionally guarded populations covered in this site's other regulated-industry interview guides, respond considerably better to a warm introduction than cold outreach.

Step 2: Structure Conversations to Respect Procurement Fairness

Frame your outreach and interview questions around understanding the underlying operational problem generally, not around evaluating your specific product — asking "how do you currently handle X" rather than "would you buy my specific product for X" both produces better discovery signal and avoids the appearance of pre-selling to an individual employee in a way that could raise fairness concerns if a formal competitive process begins later; this distinction matters more in government contexts than in most private-sector B2B discovery, given the public-fairness expectations government purchasing processes are generally built around.

Step 3: Ask About Specific, Recent Workflow Events

Anchor questions in a specific, recent example — "walk me through the last time a permit application got stuck or delayed" — rather than general questions about departmental challenges, following the same Mom Test discipline used throughout this site's interview guides, adapted to a population whose day-to-day work often involves highly specific, process-bound workflows that respond well to this kind of concrete, event-anchored questioning.

Step 4: Synthesize With an Accurate Read on Budget Authority

When synthesizing findings, explicitly separate "described a real, specific pain point" from "holds or influences real budget authority to address it" — a line staff member's account of a broken workflow is genuinely valuable discovery signal, but converting that signal into a real sales opportunity requires separately confirming, per Step 1's stakeholder table, who actually controls the relevant budget, a distinction covered in more depth in govtech validation mistakes regarding the common error of confusing staff enthusiasm with budget authority.

Worked Example: Ten Interviews on Permit-Processing Pain

A founder considering a permitting workflow tool recruited ten government employees across several cities through a public works professional association, including a mix of permitting clerks, department managers, and one procurement official willing to speak generally about the process. Anchoring each interview in a specific recent permit that had experienced delay, seven of the ten described a consistent, specific pattern: permits requiring sign-off from multiple departments (fire, zoning, building) frequently stalled because there was no clear, visible tracking of which department currently held the file, leading to permits sitting unprocessed for days without anyone realizing whose desk they were actually on.

The procurement official's conversation, kept deliberately general per Step 2's framing, revealed that permitting software purchases at cities this size typically moved through either a formal RFP process for a comprehensive platform replacement or a smaller pilot arrangement for a narrower tool — directly informing the founder's subsequent go-to-market decision to pursue the narrower pilot path covered in landing a pilot with a city government rather than attempting to compete for a larger, formal RFP as an early-stage company without an established government sales track record yet.

Mistakes: Framing That Triggers Procurement Lockout

A common, costly mistake is framing discovery conversations in a way that reads as product-specific pre-selling to an individual government employee before any formal evaluation process exists — some jurisdictions have specific rules about this kind of pre-solicitation vendor contact, and even where no formal rule is violated, an employee who senses they're being asked to informally commit or show favoritism before a fair process begins may become guarded or decline further conversation entirely, exactly the opposite of the open, candid discovery conversation Step 2's general-problem framing is designed to produce; when in doubt about a specific jurisdiction's rules, ask directly, and default toward general, problem-focused framing rather than product-specific pitching during early discovery.

Key Takeaways

• Government employees are often genuinely willing to discuss real, felt operational pain candidly through the right recruiting channels and appropriate framing.
• Frame discovery conversations around understanding the problem, not pitching your product, to respect procurement-fairness expectations and avoid triggering employee caution.
• Anchor questions in specific, recent workflow events, following the same concrete, event-based interview discipline used across this site's other regulated-population interview guides.
• Separate "described real pain" from "holds real budget authority" explicitly during synthesis. These are genuinely different findings requiring separate confirmation.
• Be aware that government communications can be subject to public-records requests in many jurisdictions — communicate professionally and appropriately with this in mind.

Frequently Asked Questions

Are there legal restrictions on contacting government employees before a formal procurement process begins?

Rules vary by jurisdiction and sometimes by the specific type of procurement involved — general discovery conversations focused on understanding problems, rather than pre-selling a specific product, are broadly acceptable in most contexts, but always ask your government contact directly about their specific jurisdiction's rules if you're uncertain, rather than assuming a blanket rule applies uniformly everywhere.

How is this different from interviewing employees at a private company?

The core Mom Test discipline transfers directly, but government interviews add the specific procurement-fairness and public-records considerations covered in this article, which have no close equivalent in most private-sector discovery interviews — a private-sector employee generally faces no comparable fairness-related restriction on discussing a vendor's product informally before a purchase decision.

Should I record government interviews given public-records considerations?

Ask explicitly for permission before recording, exactly as you would with any interview subject, and be aware that a recording, like other communications, could potentially become subject to a public-records request in some jurisdictions depending on local rules — when in doubt, ask your contact directly about their jurisdiction's specific practices, and consider that written notes summarizing key findings (without exact quotes attributed to a specific named individual, unless that's been explicitly agreed) may be a more comfortable format for some government employees who are aware of, and cautious about, this consideration even when no rule is technically being violated by either party in the actual conversation itself.

How many government employees should I aim to interview before drawing conclusions?

Eight to twelve is a reasonable starting range for a specific department or workflow area, similar to the sample sizes referenced throughout this site's other discovery-interview content, though given how much workflow variation can exist between individual cities or agencies even within the same general government level, consider spreading your sample across a few different jurisdictions rather than concentrating entirely within a single city or department, since a pattern confirmed across several genuinely independent government entities is considerably stronger evidence of a broadly addressable problem than the same finding repeated only within one specific organization's own particular, potentially idiosyncratic workflow and culture.

What if a government employee seems hesitant to speak candidly at all?

Some hesitation is normal, particularly from employees at agencies with a more formal internal culture around external communication — reassure them explicitly that you're researching general problems rather than asking them to endorse or commit to anything, offer to keep specific comments unattributed in any notes you might later reference publicly, and if hesitation persists despite this reassurance, respect it and move on to another contact rather than pushing further, since a single reluctant conversation is a poor use of relationship capital compared to the many other, more willing contacts available through the recruiting channels covered in Step 1.