Discuss Public Service Modernization Before a Solicitation

An agency transformation director often wants to explore modernization support long before a formal solicitation appears. Treat an early conversation as a capability discussion with clear boundaries. Procurement procedures, budget confidentiality, and equal treatment of future bidders shape what the agency shares and what a firm requests. Respect for those boundaries builds credibility. Pressure for private detail damages the conversation and puts the public employee in a difficult position.

Begin with public context. Read the agency website, strategic plan, published performance material, meeting notices, and any prior solicitations related to the service area. Write a short fact sheet using only material open to the public. Include the service involved, the residents or businesses served, stated goals, public milestones, and named offices. Keep a separate page for questions. This simple separation helps your team avoid treating an assumption as agency guidance.

Ask what service process agency leaders hope to improve. A question such as “Where do people encounter delay or confusion today?” invites an operational conversation. Ask who defines the operating requirements and whether a procurement timeline has been announced publicly. Ask which public documents describe the program. Do not seek draft requirements, confidential budget figures, source selection preferences, or informal advice about a future competition. The agency contact should never need to decide whether a friendly conversation has crossed a line.

In a fictional exchange, Mateo leads a department responsible for resident permits. He says, “We expect to issue something next year. Tell me whether your approach guarantees compliance.” Janelle, the business development director, replies, “We explain our delivery approach and the kinds of specialists our firm uses. Your agency and authorized reviewers define compliance requirements. Would a discussion of the present permit journey and the stakeholders who would shape a future scope be appropriate?” Mateo says the program office and procurement contact should join a short capability session.

Janelle’s response does several jobs. She avoids a guarantee. She does not ask Mateo to judge the firm against unpublished criteria. She redirects the conversation toward a service problem visible to residents and agency staff. Her wording also invites the procurement contact early. Procurement staff do more than police a conversation. They help agency colleagues choose a respectful way to gather market context within their own process.

Before the session, Janelle sends an agenda with a narrow purpose. The document says the firm will describe relevant public work, delivery methods, and team roles. Agency participants often describe public service goals and current operating context. The agenda excludes draft procurement material, nonpublic funding detail, and evaluation preferences. The note gives attendees a shared expectation before anyone joins the call. A written agenda also helps when internal colleagues later ask what was discussed.

Use language grounded in observable service work. Instead of saying, “We solve modernization,” say, “Our teams map the steps people take to submit a request, identify handoffs between offices, and test revised service steps with agency staff.” The difference matters. The second statement explains a method without suggesting a preselected answer. If public information indicates a long permit wait, describe how a team would study the handoffs and data involved. Leave the agency’s future choices to its authorized process.

The agency often has several groups with different views. A program manager wants fewer manual tasks. A legal office needs a clear review path. A contact center leader sees repeated questions from residents. A technology group faces limits in older systems. Do not compress those views into one vague statement about digital change. Ask each group what part of the present journey they own, what information they use, and what decision they expect another office to make. These questions produce useful context without asking for protected competition details.

In a fictional capability session, Mateo says residents submit a permit request online but call twice for updates. Priya from the program office says staff reenter information from one system into another. Dana from procurement says no acquisition schedule has been published. Janelle says, “We will stay with the current service experience and public information today. Which handoffs create the repeated calls, and who owns each handoff?” Priya names intake, review, and inspection offices. Janelle writes those names into meeting notes and asks Mateo whether a future process owner should join a later public discussion.

Meeting notes require care. Record public facts, questions asked, materials shared, attendees, and any next step agreed by the agency. Do not add speculation about budget, likely award terms, or internal evaluation views. Send a factual recap to the agency contact after the session when appropriate under their stated process. The recap might say, “You described resident requests for status updates and identified intake and inspection as key handoffs. We shared an approved overview of our service mapping approach. You will advise whether another capability discussion fits your process.”

Your own team needs boundaries too. A delivery leader might hear a public description and begin proposing software, staffing, or a timeline. Pause the rush. Ask what public facts support the suggestion. Ask whether the material is approved for external use. Ask who will review the language before any follow up. The business development director should keep a small library of approved credentials, case descriptions, biographies, and method explanations. Each item needs a source owner and a date for review. A vague folder of old slides leads to unsupported claims.

When an agency asks a difficult question, answer the question inside a safe frame. If someone asks, “What budget should we expect?” say, “We do not have agency scope or funding information. We describe how our teams estimate work after requirements and a procurement process establish the needed detail.” If someone asks which competitor is stronger, decline the comparison and return to your firm’s approved experience. If someone asks for a private meeting before procurement joins, ask whether procurement prefers to participate or provide guidance on the format.

Public modernization discussions also need an honest boundary around authority. Firm staff describe experience and approaches. Agency leaders determine goals, requirements, and selections through their authorized process. Specialists such as counsel, procurement staff, accessibility reviewers, and security staff address their own responsibilities. Do not offer legal, financial, or technical assurances outside the approved material and appropriate expert review. Clear limits make the conversation easier for everyone to trust.

Prepare with a fictional practice situation. Choose a public agency page describing a resident service. Make a two column page. On the left, write facts visible in the public material. On the right, write questions requiring an authorized agency process. Ask a colleague to play Mateo and mention a future solicitation. Open with, “I reviewed your public description of permit services. Would a capability discussion about the current resident journey fit your process?” When the colleague asks for a guarantee, give Janelle’s boundary response. End by writing a one paragraph recap naming only the public service issue, the approved material you shared, and the agency contact who will decide whether a procurement representative joins the next session.