Recognition highlights delivery—not its sole cause
NASCIO's September 2026 announcement named 31 State IT Recognition finalists from nearly 140 submissions. Its annual conference was scheduled for September 27–30 in San Diego. Conference dates. The program highlights real examples of technology used to solve public-sector problems, including AI, cybersecurity, and enterprise delivery. An award shortlist is useful for finding peers to learn from; it is not a representative sample proving that workforce is the only reason other states struggle. Ask how the recognized teams staffed their work, which roles remained internal, how they managed vendors, and what operating costs continued after launch. The transferable lesson is likely to include people, governance, architecture, and funding—not simply the product selected. NASCIO: 2026 State IT Recognition finalists.
Measure the hiring pipeline
Hiring architecture can create predictable friction for technical roles. Classification approvals, salary bands, screening rules, and long gaps between interview stages can cause a state to lose qualified candidates. Measure the local pipeline before choosing a remedy. A vacancy may remain open because the description attracts the wrong applicants, a compensation offer is uncompetitive, the process is slow, or the role is not funded consistently. Each cause requires a different intervention.
Public service can offer meaningful mission, benefits, and stability, but those advantages vary by person and employer; they do not remove the need to design a credible offer.
Compensation is one part of the offer
Compensation matters, particularly for specialized cybersecurity, cloud, data science, and AI roles. The right comparison depends on geography, seniority, benefits, work arrangement, and actual responsibilities. Compare the actual roles the state needs to fill; a national salary average or job-posting count can conceal differences in seniority, location, and skill. Likewise, some classification or pay changes require legislation, while others may be within existing administrative authority. HR and budget leaders should establish which changes are possible locally. Track declined offers and exit reasons alongside salary comparisons.
Training opportunities, manageable workloads, clear career paths, and technically meaningful work can strengthen retention even when pay cannot immediately match every private-sector offer.
Digital service teams still need a staffing model
Digital service teams can clarify demand for product, design, engineering, and delivery skills. They can also create better conditions for those skills to improve services. Their hiring rules, however, depend on how the state established the team; not every unit faces identical civil-service constraints. A new team name does not solve recruitment by itself. Specify permanent and time-limited roles, reporting relationships, decision rights, and how the team will work with agencies after an initial project. A successful pilot that leaves no one responsible for maintenance is not sustained capacity.
The organizational model should support both delivery and succession, with a practical plan for who retains knowledge when a fellowship, vendor engagement, or administration ends.
Combine reforms instead of searching for one fix
NASCIO's 2024 CIO survey provides a grounded set of options: respondents identified reskilling, remote work, removal of some degree requirements, and better alignment of titles and descriptions with the market among impactful actions. That is reported experience, not causal proof of an identical result everywhere. Skills-based assessment can broaden the candidate pool when it tests the abilities the work actually requires. Fellowships and residency programs, including models such as Coding it Forward, can create entry routes, but they need supervision and a transition plan. Reclassification can make the role intelligible to candidates.
Combine these measures with career development and succession planning, and measure which changes improve qualification, acceptance, performance, and retention.
Procure capacity without surrendering decisions
For state technology buyers, workforce is one of the major delivery risks to address alongside architecture, funding, governance, and procurement. Tools may be commercially available while the state still lacks people to configure, evaluate, secure, and sustain them. Partnerships can provide specialized capacity, but the state must retain enough expertise to direct the work and judge its quality. That differs from handing off all decisions and discovering at renewal that the vendor owns the only usable knowledge. Build internal counterparts, documentation, operational training, and exit readiness into the engagement.
The objective is durable decision-making capacity that survives staff, vendor, and administration changes, not the appearance of a fully staffed organization on the launch date.
Separate an unfilled role from an unworkable offer
Consider a hypothetical security-engineering vacancy that has remained open through several posting cycles. The agency assumes it needs a higher salary band. Before selecting that remedy, examine where qualified applicants leave the process. Few qualified applications may indicate a misleading description, unnecessary prerequisites or an unattractive offer. Candidates withdrawing after long interview gaps point to a different problem. Accepted offers followed by early departures require a look at the work people actually encounter.
Use evidence the agency can collect responsibly: the dates of hiring stages, the skills needed, applicant withdrawal reasons when provided and structured feedback from recent hires. Do not infer a candidate's motives from silence. Compare similar roles and separate roles for which a required clearance, license or specialized background legitimately affects the timeline.
HR and technical leaders can then choose a bounded change. Revise a description that names outdated duties. Remove an unnecessary credential where rules permit. Schedule interviews promptly if delay is losing candidates. Review compensation where comparable-role evidence supports that concern. Some changes need higher approval; identify that dependency rather than promising a hiring manager authority they do not have.
Price the temporary bridge and the permanent responsibility
A modernization program may need capacity before a hiring reform can take effect. Contracted expertise, shared services or a term-limited appointment can bridge the gap, but the program still needs to decide what happens when that arrangement ends.
For a specialist supporting an integration, define the deliverable and its receiving owner. Require documentation, tests and access arrangements appropriate to the service. Schedule a handoff exercise while the specialist is still available. If the internal team cannot diagnose a representative failure or obtain support, record that as an unresolved operating dependency rather than declaring the knowledge transferred.
The bridge may appropriately remain an external service when demand is intermittent or highly specialized. In that case, retain enough internal judgment to specify the work, assess quality and authorize changes. Where demand is continuous, compare the full operating cost and continuity risk of repeated temporary engagements with developing permanent capability.
Track whether the chosen intervention improved the actual constraint: qualified applicants, offer acceptance, time to effective contribution, retention or service coverage. Filling a position quickly is not success if the employee cannot access the tools or authority needed to perform it. The staffing decision belongs in the delivery plan because its value is demonstrated by work the agency can now execute and sustain.
Find the bottleneck, then choose the intervention
HR, program, and technology leaders can use the same measures to distinguish a slow process from a weak offer or a poorly defined role.
- Map the hiring funnel. Track days from authorization to posting, qualified applications, interview, offer, acceptance, and start date by role.
- Review classifications with practitioners. Use recognizable job descriptions, actual skills, and work-sample assessments; remove credentials that are not necessary for the work.
- Measure the whole offer. Compare pay, benefits, flexibility, mission, learning, promotion paths, and reasons candidates decline.
- Build state capability into partner work. Assign an internal counterpart, require documentation and knowledge transfer, and test whether the team can operate the service at handover.
- Tie staffing to delivery gates. Do not approve a launch without named owners for security, accessibility, product decisions, incident response, and ongoing maintenance.
Sources and further reading
- NASCIO: conference schedule
- NASCIO: 2026 State IT Recognition finalists
- NASCIO: 2024 State CIO Survey, workforce findings
Spartan X's staffing and program execution capabilities are relevant here because capacity is more than filling a vacancy. The engagement needs clear responsibilities, useful knowledge transfer, and enough retained expertise for the state to remain in control.
