Only this pageAll pages
Powered by GitBook
1 of 42

Digital Service Toolkit

Loading...

Loading...

Loading...

Loading...

Digital Service Teams

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Digital Maturity Stages

Loading...

Loading...

Loading...

Loading...

Assess Your Readiness

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

ALIGN YOUR STAKEHOLDERS

Loading...

Loading...

Loading...

Loading...

Loading...

Launch Your Digital Team

Loading...

Loading...

Loading...

Loading...

Loading...

Resources

Loading...

Loading...

Digital Service Team Overview

Learn what digital service teams do, how they're structured, and how to build one that fits your government

What is a Digital Service Team?

A digital service team helps governments design, build, and improve services that are easier to use, more effective, and better aligned with user needs.

While the goal is consistent, the structure and approach can look very different across governments.

Different forms of digital service teams

This work may exist under different names, including:

  • Digital service teams

  • Innovation teams

  • CX (customer experience) offices

  • Modernization or transformation units

These teams can sit in different parts of government, depending on their purpose and authority. You may find them in a mayor or governor’s office, within central IT, embedded in a specific agency or service area, or even within communications or operations teams.

Digital Service Team
Model
Details

These examples show how digital service teams can operate through executive, enterprise, or hybrid models.

Explore how digital service teams can be structured, funded, staffed, and supported to fit your government’s goals, capacity, and constraints.

Use these resources to choose a team model, identify the capabilities, funding, and support it needs, and determine how AI tools could increase its delivery capacity.

Hybrid and team

CODE PA is housed within Information Technology in Pennsylvania’s Office of Administration, but its executive director reports to both the Commonwealth CIO and the Governor’s Director of Digital Strategy. This combines enterprise placement and cross-agency support with executive sponsorship and direction.

  • New York City Public Interest Technology (PIT) Crew

    Executive digital delivery initiative

    Launched by the Mayor and led through the Office of Technology and Innovation, the PIT Crew brings together product, design, engineering, research, and data experts to address administration priorities. The teams work across agencies on accelerated timelines to deliver visible results.

    Colorado Digital Service

    Enterprise digital delivery team

    Housed within the Governor’s Office of Information Technology, the team partners with agencies across state government to improve complex services. Its placement within central IT and cross-agency role align primarily with the enterprise model.

    South Bend Digital Services

    Enterprise digital service team

    Established as part of South Bend’s broader effort to centralize technology and strengthen innovation, service delivery, and data-informed improvement. It operates as a citywide shared service connected to the city’s broader technology and operational functions.

    Some teams focus on delivering specific products. Others support agencies across the organization with design, technology, and strategy.

    Examples include:

    The right approach for your government's digital service team depends on what you need to accomplish, where it can operate effectively, and how it can be supported over time.

    What You'll Find in This Section

    Putting it all together

    Want help building your Digital Service Team? Request support here

    Digital service team models
    Example Digital Service Team
    Graphic illustrating the core functions of a Digital Service Team. Four connected cards represent the team's progression: In-house expertise, which includes human-centered design and development, agile product management, and data-informed decision-making; Have a mandate, emphasizing leadership or legislative support; Deliver, focused on directly delivering or supporting public-facing government services; and Scale, highlighting the creation of guides, processes, infrastructure, communities of practice, and broader engagement across the digital service ecosystem. The first two cards are dark blue under the heading Digital Service Teams, while the last two are bright blue beneath the heading Create public-facing government services, visually separating organizational capabilities from service delivery and scaling.

    About the Digital Service Toolkit

    This toolkit provides practical guidance to help governments plan, launch, and grow effective digital service teams

    Why we built this Toolkit

    Governments are often expected to improve digital services without a dedicated team or a clear starting point. For example, a city updating its website or establishing responsible AI practices may need to determine which roles and skills are needed, who should lead the work, how departments will collaborate, and what can realistically be accomplished with available resources. This toolkit provides leaders driving this work with practical guidance for structuring, staffing, launching, and growing a team to meet those needs.

    U.S. Digital Response offers pro bono support to help governments build digital service teams and capabilities, so anytime to discuss how we can help.

    Who it’s for

    Anyone responsible for improving or delivering digital services, including:

    • Government leaders

    • IT, product, and operations teams

    • Program and service owners

    • HR, talent, and workforce leaders

    Use the toolkit based on where you are today, focus on what’s realistic, and build your digital service capabilities over time.

    The toolkit is organized into 5 main sections plus a resource section that provide a step-by-step approach to planning, launching, and growing effective digital services.

    1

    Explore what digital service teams do, compare how they can be structured, and identify the roles and approach that best fit your government’s needs.

    2

    Identify your organization’s current stage of digital maturity and determine which capabilities and improvements to prioritize next.

    3

    Examine your directive, organizational structure, existing people and systems, and history with change to identify gaps, constraints, and opportunities.

    4
    Item
    Details

    This field guide was born from a combination of experiences supporting digital transformation teams across U.S. federal, state, and city governments and generally recognized best practices for creating optimal employee experiences for digital talent. Content was developed in collaboration with , who have deep experience in hiring, recruiting, human resources, operations, and strategy.

    Digital Service Team Models

    Choose the model that best fits your goals, structure, and constraints

    The two most common digital service team models are executive and enterprise teams, though some governments combine elements of both in a hybrid model. These models describe where a digital service team sits and how it operates across government. Each comes with tradeoffs in speed, scope, sustainability, and influence, which we outline below.

    Understanding the difference between these models will help you:

    • Set realistic expectations for what your team can achieve

    • Align your structure with your goals

    • Avoid common pitfalls when launching or scaling digital services

    Code Pennsylvania (CodePA)
    executive
    enterprise

    Bring key stakeholders together to review findings, agree on priorities, clarify ownership, and define next steps.

    5

    Define an initial problem and scope, assemble the team, establish ownership and measures of success, and build support for sustaining the work.

    6

    Access downloadable checklists, workshop materials, templates, examples, and guides to support planning and implementation.

    Light/Dark Mode

    Use this toggle at the bottom of each page to switch between modes.

    Feedback

    Use the Was this helpful? feature on the bottom of each page to leave us feedback.

    Contact

    If you have questions or need further assistance, navigate to the section for ways to reach out.

    Navigation

    Use the sidebar on the left of each page to access different sections of the toolkit.

    Overviews

    Each section has an overview page that includes a definition of the topic, who's generally involved in that work, and what's covered in the section.

    Search

    Utilize the search bar to quickly find specific information or keywords.

    Interactive Elements

    Look for links and embedded tools to access additional content and to download copies of resources.

    Helpful Tips

    Look for this icon throughout the Toolkit for helpful insights and tips

    How to use the Toolkit

    Toolkit sections

    Digital Service Models

    Digital Maturity Stages

    Assess Your Readinesss

    How to Navigate

    Content development

    US Digital Response's
    Verge Talent Partners
    contact USDR for support
    Infographic titled “Your Path Through the Digital Service Toolkit,” showing a flexible three-phase journey: Learn and Explore digital service teams, models, roles, funding, success factors, and maturity; Assess and Align by examining organizational context, documenting the current state, learning from history, assessing risk, and engaging stakeholders; and Decide, Launch, and Evolve by defining the team’s purpose, model, placement, capabilities, resources, governance, and launch plan. A note emphasizes that users can move through the Toolkit at their own pace and revisit sections as their needs and capacity grow.
    Infographic explaining the purpose of the Digital Services Toolkit. At the top, a government building and web interface icon accompanies the message: "Governments are doing important work with limited time, resources, and capacity." Below, a section titled "We built this toolkit to help." explains that the toolkit provides practical, real-world guidance for building the teams, capabilities, and foundations needed to deliver modern digital public services. Three illustrated focus areas are presented in columns: Build Digital Service Teams, Hire Effectively, and Strengthen Capabilities, each with a simple blue icon and a brief description. The graphic uses a clean, minimalist layout with blue accents, generous white space, and subtle dividers to emphasize clarity and readability.

    Executive teams sit within top-level leadership offices (e.g., a governor’s, mayor’s, or agency head’s office). Their placement gives them the visibility and influence to challenge existing approaches, test new ideas, and drive change across organizational boundaries.

    To turn that influence into sustainable services, executive teams need strong partnerships with IT, program teams, and operational staff who provide technical expertise, service knowledge, infrastructure, and ongoing support.

    • Moving quickly on high-priority initiatives

    • Testing new approaches and demonstrating what is possible

    • Driving coordination across departments or agencies

    • Delivering visible, short- to medium-term results

    • Greater flexibility to challenge existing processes and introduce new approaches

    • Faster decision-making and execution

    • Strong authority to remove barriers across teams

    • Clear alignment with leadership priorities

    • May be less stable during leadership transitions

    • Priorities can shift with political or executive direction

    • May become disconnected from technical and operational teams

    • Can be difficult to sustain long-term or system-wide improvements without an operational home and ongoing funding

    Enterprise teams sit within operational parts of government (e.g., central IT, shared services, administration, or an innovation office) They support multiple departments and build digital service capacity that can continue through leadership changes.

    It's critical that these teams have an executive champion. A dotted-line relationship to an executive leader can help protect the team’s priorities, reinforce its cross-government mandate, and remove barriers. This complements the critical role of IT while giving the digital service team enough space to work across product, research, design, technology, and service operations.

    • Building long-term digital service capacity

    • Supporting multiple departments

    • Establishing shared tools, practices, or services

    • Improving services that require sustained operational support

    • More stable and less tied to political cycles

    • Connected to critical technical infrastructure and expertise

    • Better positioned to maintain services over time

    • Able to establish consistent practices across government

    • Existing processes may be designed for traditional IT operations rather than iterative, user-centered delivery

    • Digital service priorities may be deprioritized within a larger operational portfolio

    • Departments may view the team as a technology provider instead of a partner in improving services

    • Cross-department work may move slowly without executive support

    Hybrid teams combine elements of the executive and enterprise models. They may have executive sponsorship and authority while operating within, or in close partnership with, an operational department.

    • Balancing near-term priorities with long-term capacity

    • Moving work across organizational boundaries

    • Supporting both high-priority initiatives and ongoing services

    • Combines executive influence with operational stability

    • Can move quickly while building lasting capabilities

    • Connects leadership priorities with organization-wide needs

    • Roles, ownership, and decision-making can be unclear

    • Requires strong coordination between executive and operational leaders

    • Competing priorities can make it harder to maintain focus and accountability

    Executive and Enterprise Models

    Teams in either model can to support research, design, development, analysis, and other parts of the work. This changes how the team works, not where it sits organizationally.

    Executive team

    Best for:

    Strengths:

    Tradeoffs:

    Enterprise team

    Best for:

    Strengths:

    Tradeoffs:

    Hybrid team

    Best for:

    Strengths:

    Tradeoffs:

    Choosing the Right Model for You

    Identify a starting point based on your priorities, support, structure, funding, and capacity

    How to Choose the Right Model for Your Org

    The right model depends on what the team needs to accomplish and the conditions it needs to succeed. Regardless of the model, the team needs clear authority, executive support, and an organizational structure that enables resident-focused, iterative work across government.

    Use the decision tree to identify a possible starting point, then use the questions below to test whether it fits your needs now and over time. The assessment and stakeholder alignment sections will help you gather the information and perspectives needed to choose.

    Both models can support resident-centered digital service delivery. The right model for your government is the one that gives the team the authority, support, partnerships, and resources needed to work effectively.

    Many organizations begin with a team following the executive model to build momentum, then transition to or add an enterprise model as their capacity and demand grow.

    Test the Model Against Your Needs and Conditions

    Work through the six questions below to assess how well each model fits your government. No single answer will determine the right model. Look across your answers to identify which model has the strongest overall fit and what may need to change for it to work.

    1

    What does the team need to accomplish first?

    An executive model may be a stronger fit if the team needs to:

    • Deliver a small number of urgent or highly visible priorities

    • Work across departmental boundaries

    • Demonstrate value quickly

    • Address challenges that require executive attention

    An enterprise model may be a stronger fit if the team needs to:

    • Support multiple departments over time

    • Establish shared tools, standards, or services

    • Improve how digital services are delivered across the organization

    • Build capacity that can continue through leadership changes

    2

    Both models require visible leadership support. Executive sponsorship gives the team authority to work across organizational boundaries, resolve barriers, and introduce new ways of delivering services.

    An executive team usually relies directly on a mayor, city manager, governor, agency secretary, or other senior leader to set priorities and bring departments together.

    An enterprise team may operate farther from executive leadership, but it still needs a senior sponsor who can reinforce its authority, support cross-department coordination, and protect its ability to work in resident-focused and iterative ways.

    Ask:

    • Who will set or approve the team’s priorities?

    3

    An executive model may fit when the team can sit within a mayor’s, governor’s, county executive’s, or agency administrator’s office.

    An enterprise model may fit within central IT, shared services, administration, innovation, or performance management. IT can be a critical partner, providing technical expertise, systems knowledge, security, infrastructure, and procurement support.

    Ask:

    • Where could the team be housed?

    • What decisions could it make independently?

    4

    An executive model may begin with funding controlled by an executive office or dedicated to specific leadership priorities. This can support a quick launch but may be vulnerable to budget or leadership changes.

    An enterprise model may rely on an ongoing appropriation, shared-services funding, cost recovery, or a combination of sources. These approaches can provide continuity but may also create more coordination and administrative requirements.

    Ask:

    • Is funding available for a defined initiative or for ongoing operations?

    • Who controls the funding?

    5

    Build on the people and capabilities already in place. Engage existing IT teams early because their technical knowledge, operational responsibilities, and understanding of current systems will be essential regardless of the team’s model or placement.

    Look for staff or teams working in:

    • Technology and application development

    • Data and analytics

    • Service design and user research

    6

    That is common. Your government may need rapid results but lack a strong executive sponsor. It may want long-term capacity but not yet have a stable organizational home or ongoing funding.

    When the conditions do not align:

    • Focus on the most important outcome for the team’s first phase

    • Document what the preferred model would require to succeed

    • Identify which conditions already exist and which need to be established

    The model you choose does not need to be permanent. Start with an approach that fits your current needs and capacity, then adapt as demand, support, and resources grow. Here are some examples of where governments can start:

    USDR Talent Toolkit

    An accompanying resource to help government leaders and hiring managers attract, build, and retain high-performing digital service teams with practical guidance and resources.

    Check out the separate for practical guidance and ready-to-use resources for building and supporting a strong digital workforce. It draws on USDR’s experience supporting state, local, and federal government partners.

    Use the Digital Service Toolkit to determine what kind of team to build, how to structure and launch it, and which roles and capabilities it needs. Once you are ready to build that team, turn to the Talent Toolkit for practical guidance on developing job descriptions, hiring, compensation, onboarding, employee development, and team culture.

    The Toolkit follows the employee lifecycle, helping you think holistically about building and sustaining a digital team. It includes guidance on:

    • Attracting and hiring talent

    Welcome

    Welcome to the USDR Digital Service Toolkit! This resource provides practical guidance, examples, and tools to help you plan, launch, and grow a government digital service team.

    These sections explain U.S. Digital Response's (USDR) recommended frameworks for team organization and digital maturity, helping you determine the right fit for your organization.

    use AI tools to augment their delivery
    Comparison table showing two types of Digital Service Teams: Executive and Enterprise. The graphic compares the models across three categories: Location, Speed & Scope, and Budget. Executive teams sit within top-level executive offices, focus on leadership priorities, move quickly with executive authority but may have shorter lifespans due to leadership changes, and are funded through the executive office. Enterprise teams sit within operational or enterprise IT organizations, support multiple divisions and cross-agency work, provide greater continuity for long-term initiatives but may implement change more slowly, and are commonly funded through fee-for-service, appropriated funding, or cost recovery models. The information is presented in a clean, two-column comparison with simple organizational chart icons and blue section dividers.
    Who can resolve disagreements between departments?
  • Who can navigate procurement, staffing, policy, or technology barriers, or bring together the people needed to help move the work forward?

  • Will that support remain available when leadership changes?

  • Would departments see the team as a partner?

  • Could its organizational home support staff, funding, and operations over time?

  • Is the funding tied to a particular leader, program, or deadline?

  • Will departments be expected to pay for the team’s services?

  • Accessibility

  • Communications and web content

  • Innovation and performance improvement

  • Project, program, or product management

  • Consider starting with a limited pilot before committing to a permanent structure

  • Revisit the decision with the stakeholders who will fund, support, and work with the team

  • Consider the outcomes expected during the team’s first 12 to 18 months.

    Who can give the team direction and remove barriers?

    Where can the team operate effectively?

    If housed in IT, the team needs clear authority and enough operational autonomy to work across departments, conduct user research, test ideas, and improve services iteratively around resident and staff needs. This allows the team to maintain its distinct delivery approach while working in close partnership with IT.

    How will the work be funded?

    What capacity already exists?

    What if the answers point in different directions?

    Example Starting Points

    A city needs immediate results and long-term capacity

    The city could begin with an executive team focused on a few high-priority services while planning for a permanent enterprise capability. Over time, the city might transition the team, add an enterprise team, or combine elements of both models.

    A county wants to improve digital services across many departments

    Central IT already provides shared technology services, ongoing funding is available, and leaders want to establish common practices for research, design, and delivery. An enterprise model may offer the continuity and organizational reach needed.

    A governor wants to improve several high-priority services

    The work crosses multiple state agencies, needs visible progress within the first year, and has strong support from the governor and chief of staff. An executive model may provide the focus and cross-agency coordination needed to build momentum.

    Decision tree titled “Choosing the Right Model for Right Now.” It asks what the government most needs the team to do now. Delivering urgent or highly visible priorities leads to the Executive Model, which is best for speed, focused priorities, and cross-department action. Building lasting capacity across departments leads to the Enterprise Model, which is best for continuity, shared capacity, and organization-wide support. If both are needed, prioritizing momentum leads to the Executive Model, while prioritizing long-term capacity leads to the Enterprise Model.
    Compensation and offers
  • Onboarding new hires

  • Learning and development

  • Culture and team engagement

  • Inclusive hiring and workplace practices

  • Working effectively with HR

  • Talent Toolkit Overview

    How the Toolkits Work Together

    What the Talent Toolkit Covers

    USDR Talent Toolkit

    Digital Service Toolkit Sections

    Explore additional pro-bono support offerings for governments.

    Contact
    Align Your Stakeholders
    Launch Your Digital Team
    Resources

    Each section includes practical steps, examples, and templates you can adapt to your organization.

    Digital Service Teams

    What they do and how they're structured

    Digital Maturity Stages

    Where you are today and what to focus on next

    Assess Your Readiness

    Identify strengths, gaps & next steps

    Align Your Stakeholders

    Build alignment & agree on priorities

    Launch Your Digital Team

    How to build & sustain your team

    Resources & References

    Helpful templates, guides & tools

    U.S. Digital Response
    Banner for the US Digital Response Digital Services Toolkit on a dark navy background. The US Digital Response logo appears in the upper left. Centered across the banner is a row of bold geometric icons in blue and orange—including circles, steps, an hourglass, a starburst, a triangle, and a grid of squares—representing the toolkit's visual identity. The title "Digital Services Toolkit" appears in large white text below the icons.
    Banner for the US Digital Response Digital Services Toolkit on a dark navy background. The US Digital Response logo appears in the upper left. Centered across the banner is a row of bold geometric icons in blue and orange—including circles, steps, an hourglass, a starburst, a triangle, and a grid of squares—representing the toolkit's visual identity. The title "Digital Services Toolkit" appears in large white text below the icons.
    Cover
    Icon of four solid blue circles arranged in a 2×2 grid on a dark navy background. The simple geometric design is used as a visual symbol in the Digital Services Toolkit.
    Cover
    Icon of an orange staircase with four ascending steps on a dark navy background. The simple geometric design symbolizes growth, progression, or increasing maturity and is used as a visual element in the Digital Services Toolkit.
    Cover
    Icon of a blue hourglass shape on a dark navy background. The simple geometric design symbolizes time, pacing, or sustained delivery and is used as a visual element in the Digital Services Toolkit.
    Cover
    Icon of an orange eight-point starburst on a dark navy background. The simple geometric design symbolizes innovation, ideas, or impact and is used as a visual element in the Digital Services Toolkit.
    Cover
    Icon of a solid blue triangle on a dark navy background. The simple geometric design symbolizes direction, focus, or momentum and is used as a visual element in the Digital Services Toolkit.
    Cover
    Icon of nine small orange squares arranged in a 3×3 grid on a dark navy background. The simple geometric design symbolizes organization, structure, or scalable systems and is used as a visual element in the Digital Services Toolkit.

    Funding can influence what the team is able to prioritize and how long it can operate. Reference for more specific guidance.

    Existing capacity may reveal a natural home for an enterprise team, potential partners for an executive team, or gaps that either model will need to address.

    Digital Service Funding

    Digital Service Team Funding

    Common funding approaches and staffing cost estimates for a digital service team

    Funding Approaches

    You've probably figured out that there's no one-size-fits-all funding model for a digital service team. The right approach depends on the team's role, placement in your organization, and your government's budget structure.

    The Beeck Center for Social Impact + Innovation’s Digital Service Teams 101: A Guide for State and Local Governments provides a practical overview of sustainable funding approaches. It identifies general fund appropriations and cost recovery as two common models, with project-based funding often used to launch, expand, or supplement a team. Many teams combine these approaches to balance stability and flexibility.

    Adapted from the Digital Gov Hub’s Digital Service Teams 101: A Guide for State and Local Governments, licensed under

    Staffing Costs

    Staffing will likely be your largest ongoing cost and a central consideration when seeking approval for the digital service team and planning future budget requests.

    An initial digital service team of two to six dedicated staff may cost approximately $500,000 to $1.8 million annually, including salaries, benefits, tools, and basic operating expenses. This planning range assumes compensation near the upper end of the state and local government workforce because digital service teams tend to rely on specialized talent. Actual costs will vary based on the roles needed, staff seniority, location, and infrastructure already available.

    provides staffing recommendations and common roles in a digital service team.

    Planning for ongoing funding

    Your initial funding may cover hiring and launching the team, but if it is time-limited, identify which costs it can support and when you will need another funding source. Start planning for recurring funding early so you can retain staff and continue the team’s work.

    explains how recurring funding can support the team’s long-term stability.

    Key Roles in a Digital Service Team
    CC BY 4.0
    Diagram showing two common digital service team funding models: general fund appropriations provide a stable annual budget for long-term planning, while cost recovery uses partner-agency payments for specific projects. Project-based funding, such as grants, philanthropy, or one-time appropriations, can supplement either model but is rarely sufficient long term; many teams combine funding sources.
    Codifying Your Team

    Conditions for AI-Augmented Team Success

    Put the tools, infrastructure, organizational support, and funding in place for the team to deliver and grow

    Confirm Your Government Can Support the Team

    After identifying a possible team structure, use the following conditions to determine whether your government can support it. Some foundations may already exist, while others will need to be established before the team begins building production solutions.

    If your government cannot provide the required tools, infrastructure, funding, or specialist support, narrow the initial scope, add the missing support, or select a different team structure. Strengthen these foundations before the team takes on more complex or higher-risk work.

    Put the Foundations in Place

    AI tools can increase the team’s capacity, but the team still needs a secure and supported environment for turning its work into reliable services.

    1

    Approved tools and clear guidance

    Give the team access to AI tools that are approved for its work. Establish clear guidance about which tools it can use, what information can be entered into them, which uses require additional approval, and how AI-generated work should be reviewed.

    See the for a practical example addressing privacy, transparency, human review, accountability, risk levels, and tool approval.

    2

    Secure infrastructure and appropriate access

    Provide a secure environment where the team can work with permitted files, data, and systems and test solutions safely. Establish who can approve access and integrations and how data will be protected throughout delivery.

    3

    Identify the security, privacy, accessibility, legal, procurement, cloud, data, and other specialists who can support the team. Involve them early and establish when reviews will occur and who can make final decisions.

    4

    Define how the team will move its work through testing, review, approval, deployment, monitoring, and maintenance. Before launching, confirm who will own, operate, and improve the service over time.

    5

    Provide a sponsor who can remove barriers, enough funding and time to deliver responsibly, and clear relationships with the departments the team supports. Plan for what will happen after initial project funding or temporary support ends.

    The cost of an AI-augmented team depends on its size, staffing model, technical needs, and access to existing infrastructure and specialists.

    These figures are planning estimates, not fixed budgets. Costs will vary based on compensation, benefits, staffing model, location, technical needs, and existing infrastructure.

    Team Structure
    Primary Considerations
    Cost Estimate

    The budget should account for:

    • Staff salaries and benefits

    • Contractors or shared specialists

    • AI tools and other software

    • Cloud and technical infrastructure

    • Review, testing, monitoring, maintenance, and user support

    Estimate the time needed to understand user needs, build and test solutions, complete reviews, manage integrations, and launch new work. Then account for monitoring, maintenance, user support, and unexpected issues across everything the team already operates.

    The capacity left after those commitments determines how much new work the team can responsibly take on. If there is not enough capacity to maintain existing services without reducing their quality or reliability, delay new work or add support.

    Before the team begins delivering work, define how you will determine whether it is creating value. Do not set expectations based only on how many tools it produces.

    Measures of value may include:

    • Improved outcomes for users

    • Fewer unnecessary steps or less staff workload

    • Accessible and reliable services

    • Clear ownership and continued improvement after launch

    • Knowledge and components that are reused in future work

    After each project, document what the team learned about users, workflows, systems, approvals, procurement, and operations. Identify agreements, processes, designs, and technical components that could be reused.

    Over time, this knowledge can shorten future timelines, help the team identify risks earlier, and improve decisions about when to build, buy, or work with a vendor. It also prepares the team to take on more complex work and advise the broader organization on larger modernization efforts.

    Example Digital Service Team

    How the City of South Bend, IN built and scaled a centralized digital service function through organizational transformation, service design, and strategic IT integration.

  • Training and professional development

  • Greater ability to deliver future work with internal staff

  • Cross-functional pair

    Two experienced team members, approved AI tools, technical infrastructure, and access to shared specialists

    ~$500,000/yr or less when approved platforms, infrastructure, and review processes already exist

    Expanded trio

    A third team member who adds capacity or fills the team’s most important capability gap

    Often under $1 million/yr, depending on compensation, benefits, contracting, and technical needs.

    Multidisciplinary team

    More dedicated specialists, deeper technical and operational capacity, complex infrastructure, and ongoing support and maintenance

    Requires a larger investment based on the number of dedicated specialists and the complexity of the services it operates

    Review processes and specialist support

    A path to production and ongoing ownership

    Establish the path to production early. Do not wait until a prototype is complete to determine whether the government can approve, operate, and maintain it.

    Sustained organizational support

    Plan for Cost, Capacity, and Value

    Estimate the cost

    AI tool licenses are only one part of the investment. Experienced staff and the infrastructure needed to operate reliable services will usually account for much more of the cost.

    Plan sustainable delivery capacity

    The three areas do not require equal amounts of capacity. Decide how much to reserve for each based on the services the team supports and the demands and risks of the work.

    Plan how you will measure value

    Build long-term value

    Example of reusable knowledge

    After building a benefits application tool, the team can document how it accessed eligibility data, completed privacy and security reviews, met accessibility requirements, and integrated with existing systems. It can then adapt the approved data-sharing agreement, security documentation, accessibility checklist, integration design, and technical components for future projects instead of creating each one from scratch.

    City of San José’s AI Guidelines and Policies
    Alt text: Diagram showing a team’s total available capacity divided into three areas: ongoing support, unexpected work, and new delivery. It advises teams to protect capacity for support, reserve room for unexpected needs, and use the remaining capacity for new digital service work.

    Over the past decade, the City of South Bend has undergone a significant transformation in how it organizes and delivers technology and digital services. What began as an effort to modernize and centralize IT evolved into a broader strategy focused on innovation, digital service delivery, and data-driven improvement. The following timeline highlights key organizational changes, leadership transitions, and the factors that shaped the city's current technology structure.

    • 2013: Mayor hires a contractor to serve as Innovation Director.

    • 2015: Role becomes Chief Innovation Officer (CIO) and assumes oversight of the Information Technology office within Administration and Finance.

    • 2016–2018: Innovation functions are formalized into dedicated groups:

      • Applications and Business Analytics

      • Infrastructure and Service Maintenance

    • 2018: Original CIO departs and a new CIO is hired.

    • 2024: The city launches a broader digital services initiative.

      • Subsequent reorganization: A third vertical, Digital Services, is established.

        • Key leadership roles included the Director of Digital Services and Chief Digital Officer.

    • Capacity constraints and broad, unrelated responsibilities contributed to staff turnover.

    • Leadership reviewed services, projects, and operational responsibilities across the organization and created the Digital Services function to better distribute work and align resources.

    • The original Business Analytics group evolved into a dedicated Data & Performance function focused on performance management and process improvement.

    • Historically, IT operations were decentralized across city departments. One of the original CIO's primary goals was to establish a centralized, citywide IT function.

    Divisions include:

    • Centralized Infrastructure, Project Management, and Services

    • Performance & Innovation

    • Digital Services

    • Digital Integrations and Development

    • Customer Services & Success

    The Digital Services team sits within centralized IT under the Digital vertical.

    The Customer Services & Success is also centralized within IT. It serves as a central point for resident questions and service requests, helping departments work from consistent information about customer needs and service activity.

    Building the team required significant political capital and justification, especially when adding staff.

    Technical funding that previously existed in other departmental budgets was gradually reallocated into the centralized organization. However:

    • The team does not fully control its own budget size.

    • It does not necessarily have a dedicated budget line.

    • Leadership can make recommendations but cannot easily expand or reduce funding independently.

    The team has tripled in size since its formation, though leadership still feels the organization is operating at roughly half the staffing level it truly needs.

    Strong centralized infrastructure (enterprise) was identified as a key enabler of Digital Services' success. Key observations included:

    • Foundational systems matter more than where a team sits in the organization.

    • Organizational flexibility allows leaders to assign the right people to the right problems regardless of departmental boundaries.

    • Clean, reliable data and adequate staffing are more important than where a team sits on an organizational chart.

    • Placement inside or outside of IT can significantly affect implementation, particularly during service launch and delivery.

    • Digital communications and marketing often become politically sensitive, which can limit a digital services team's authority even when it owns the underlying tools.

    The organization takes a deliberate approach to building new tools, recognizing that each system requires ongoing support and maintenance throughout its lifecycle.

    As a result, the team typically engages when internal customers have clearly defined needs and are ready to partner on solutions.

    Additional lessons learned:

    • “Don’t promise the moon.” Underpromise and over deliver.

    • Own process improvement work whenever possible and make that ownership clear across the organization.

    • Position the team as thought partners in user experience and service delivery.

    • Neutrality helped the team successfully facilitate conversations across departments.

    • Guidance from Denver’s influenced some of their process improvement work.

    • Ownership is important because many departments do not want to own ongoing operational improvements.

    Digital Services housed the team’s product and design roles, while developers sat within a separate Applications function under the same Chief Digital Officer. Close collaboration across these groups enabled more effective delivery. Leadership also valued critical thinking, not just technical skills, when hiring.

    Foundational engineering capacity was viewed as particularly important, including roles such as:

    • Platform or base engineer

    • Front-end engineer

    Government level

    Local (city)

    Year formed

    2018

    Team framework

    Enterprise (city-wide shared service)

    Mandate and structure

    No formal mandate, long-term goals connected to operational support

    Funding model

    South Bend, IN Digital Services

    Overview

    Seal of the City of South Bend, Indiana centered on a dark blue background. The circular seal features a waving American flag above the word "PEACE," with golden rays extending outward behind it and clouds at the base. The outer ring reads "The City of South Bend, Indiana" with "1865" at the bottom, indicating the city's incorporation year.

    Gradual centralization of tech funding split between departments through a priority-based budgeting approach

    Background

    Organizational evolution timeline

    Key drivers for reorganization

    Additional organizational context

    Organization & team structure

    Current org structure

    Funding model

    Enterprise team structure

    Advice & lessons learned

    Team composition & capabilities

    Build engineering capacity into the team early so it can test ideas, deliver solutions, and maintain them after launch.

    PEAK Academy
    Organizational chart showing the Information and Technology (I&T) divisions for the City of South Bend. At the top is the Chief Innovation Officer, with the Chief Digital Officer and Chief Technology Officer reporting beneath. The Chief Digital Officer oversees Digital Integrations & Development and Digital Services, while the Chief Technology Officer oversees Enterprise Services & Software and Infrastructure. Four additional divisions report to the Chief Innovation Officer: Data & Performance, Civic Innovation, Customer Service & Success, and Project Management. The Digital Services division is highlighted in blue to distinguish it from the other dark blue organizational units.
    Detailed organizational chart for the City of South Bend's Information and Technology (I&T) department. The Chief Innovation Officer oversees multiple divisions, including the Chief Digital Officer, Chief Technology Officer, Project Management, Data & Performance, Civic Innovation, and Customer Service & Success. The chart shows reporting relationships from division directors to managers and staff roles. The Digital Services branch under the Chief Digital Officer is highlighted in light blue and includes a Director of Digital Services overseeing a Web Manager, Product Manager, and Solutions Designer. All other divisions are shown in dark blue and include teams responsible for applications, enterprise software, infrastructure, GIS, customer service, project management, and civic innovation. The highlighted Digital Services branch distinguishes the digital service team from the broader I&T organization.

    Structuring an AI-Augmented Team

    Compare three ways to organize people and capabilities based on the work, available funding, and support within your government

    Confirm Who Will Cover Each Core Capability

    AI tools can help a smaller team do more, but they do not replace the capabilities needed to understand problems, make decisions, and deliver reliable services.

    Before choosing a team structure, determine who will lead or own each of the five areas below. Assess whether they have the experience and capacity to take responsibility for it, then identify any shared or specialist support they will need.

    1

    Product management and outcomes

    Identify the problem to solve, define the desired outcomes, prioritize the work, and track whether the solution creates value

    2

    User research and design

    Research user needs, test ideas with users, and apply what the team learns to make the service accessible and easy to use

    3

    Make technical decisions, turn priorities into working solutions, test them before launch, and plan for deployment, monitoring, and maintenance

    4

    Involve subject matter experts and frontline staff who understand the service, its operational realities, and the policy constraints affecting delivery

    5

    Determine which security, privacy, accessibility, data, legal, and procurement requirements apply, then establish who will advise, review, and approve the work

    The following structures assume that team members can use approved AI tools in their delivery work and have a viable path from prototype to production. Without those conditions, the same capabilities are still needed, but the team may not achieve the capacity described below.

    Structure Profile
    Team composition
    Best Suited For
    • Cross-functional product manager/researcher

    • Cross-functional engineer/data analyst

    These combinations are examples, not fixed job titles. Each person brings complementary capabilities and contributes across multiple parts of delivery.

    Use a cross-functional pair for a focused, lower-risk improvement when approved AI tools, review processes, and a path to production are already available.

    This structure works best when the work involves a limited number of users and workflows, few integrations, limited sensitive data, and manageable consequences if the service fails.

    • Prototyping and testing a focused idea

    • Improving a document or internal workflow

    • Improving one part of an existing public service

    • Building a tool with few integrations

    • Delivering an improvement the team can reasonably operate and maintain

    • Cross-functional product manager/researcher

    • Cross-functional engineer/data analyst

    • A third team member selected to fill the most important capability gap

    Depending on the work, the third person might bring additional design, research, product management, engineering, data, content, service design, or subject matter expertise.

    Use an expanded trio when funding supports a third team member and the work involves more users, workflows, integrations, or operational demands than a pair can reasonably manage.

    This structure is best suited for a larger or medium-risk project that requires greater delivery capacity, deeper expertise, or more extensive research, testing, review, and ongoing support.

    • A service involving multiple user groups or workflows

    • Work requiring deeper research, design, or accessibility testing

    • A solution connecting to existing government systems

    • A medium-risk service requiring additional review and support

    A multidisciplinary team may include dedicated or shared responsibility for:

    • Product management and outcomes

    • User research and design

    • Technical delivery and engineering leadership

    • Service and policy expertise

    • Security, privacy, accessibility, data, procurement, and operations

    These capabilities do not always require separate positions, but critical services need enough dedicated capacity and specialist depth to cover them reliably.

    Use a multidisciplinary team for a critical, high-risk, or system-of-record service that requires dedicated technical, design, operational, and risk-management expertise.

    This structure is best suited for services involving sensitive or regulated data, complex integrations, significant policy constraints, multiple user groups, or serious consequences if the service fails.

    A multidisciplinary team may be a good fit for:

    • Critical public-facing services

    • Systems of record

    • Services involving sensitive or regulated data

    • Work with complex integrations or infrastructure

    • Services requiring continuous monitoring, support, and maintenance

    You may be assembling a new team or introducing AI tools to an existing one. Use the questions below to decide how current staff can work together, where additional capacity or specialist support is needed, and whether the initial scope fits the team you can sustain.

    1. What will the team deliver?

      • Identify the users and workflows involved, required integrations, sensitive data, and consequences if the service fails

    2. Which core capabilities can current staff cover?

      • Identify who can lead product and outcomes, research and design, technical delivery, service and policy expertise, and responsible delivery

    Consider your answers together. These profiles can help you organize an existing team, add capacity, or assemble a new one:

    • A may fit when the work is focused and lower risk, two people can cover the core capabilities, and shared specialists and production processes are available

    • An may fit when the work requires more delivery capacity or the team has an important capability gap that a third person can fill

    • A may fit when the service is critical or high risk and requires dedicated capacity, deeper specialist expertise, or ongoing operational support

    Contact USDR for Support

    Connect with USDR to get support, share feedback, or learn how we can help your government build and grow digital service teams.

    (USDR) helps governments at all levels attract and retain skilled technologists to work on critical public services.

    If you have any questions or have feedback on this Toolkit, please send us a note at . You can also leave feedback on each page by using the Was this helpful? feature.

    With guidance and support, we empower agencies to build high-performing teams that utilize technology to transform how governments serve people.

    USDR Contact Information

    Contact USDR here if you're interested in talent engagement support for your government organization.

    Sign up for the USDR Newsletter to receive new perspectives and resources monthly.

    Questions or Feedback

    Case Studies

    The City of Baltimore partnered with USDR to recruit and hire a new digital service team with a foundation for future growth.

    USDR helped Multnomah County build out their web and digital experience team.

    U.S. Digital Response
    info@usdigitalresponse.org
    Multiple related improvements being delivered together
  • Projects with significant security, privacy, accessibility, or operational risks

  • How many people can you fund, and for how long?

    • Distinguish short-term project funding from ongoing capacity to operate and maintain the service

  • Can the team use AI tools and move from prototype to production?

    • Confirm that the team has access to approved AI tools, secure infrastructure, and established processes for testing, deployment, monitoring, and maintenance

  • Which specialists can support the team?

    • Identify who can provide security, privacy, accessibility, procurement, legal, cloud, or data expertise and when they need to be involved

  • Cross-functional pair

    Two people combine complementary capabilities, such as product management and research or engineering and data analysis

    A focused, lower-risk improvement with a limited number of users and workflows, few integrations, and manageable consequences if the service fails

    Expanded trio

    A cross functional pair plus a third person who adds delivery capacity or fills the team’s most important capability gap, such as design, engineering, data, or service expertise

    A larger or medium-risk service involving more users, multiple workflows, some system integrations, or more extensive research, testing, and operational support

    Multidisciplinary team

    Dedicated specialists cover product, research and design, engineering, service expertise, data, operations, and responsible delivery

    A critical or high-risk service involving sensitive data, complex integrations, policy requirements, systems of record, or significant consequences if the service fails

    Technical delivery

    Service and policy expertise

    Responsible delivery

    These five areas do not require five separate positions. One team member may cover multiple areas, but you should identify who is responsible for each and where specialist support is needed.

    AI-Augmented Team Structure Profiles

    Start with the smallest structure that can responsibly deliver and maintain the service. Add capacity or dedicated specialists as the number of users and workflows, technical complexity, operational demands, or consequences of failure increase.

    Cross-functional pair

    Who is on the team

    When to use this structure

    A cross-functional pair may be a good fit for:

    Using AI tools to reduce routine work gives the team more space to understand user needs, make outcome-oriented decisions, review the quality of its work, and iterate based on feedback.

    Expanded trio

    Who is on the team

    When to use this structure

    An expanded trio may be a good fit for:

    The reason to add a third person is not simply to separate product management from design. A dedicated designer or researcher may help the team take on broader work, but the third position should provide the capability the project needs most.

    Multidisciplinary team

    Who is on the team

    When to use this structure

    AI tools can increase the team’s capacity across research, design, development, testing, analysis, and documentation. They do not reduce the dedicated capabilities or specialist support required to operate a critical service responsibly.

    Choosing an AI-Augmented Team Structure

    Match the structure to the work

    AI tools can augment any of these structures. The work and the capabilities needed to deliver it responsibly should determine how the team is organized.

    Examples of choosing a team structure

    Example 1: Cross-functional pair

    Project: Improve the online status-checking experience for permit applicants

    1. What will the team deliver?

      • A mobile-friendly status page that helps residents and small businesses understand where an application is, what is needed next, and who to contact. It uses data from an existing permitting system but does not change the system of record

    2. Which capabilities can current staff cover?

      • A product manager can also conduct research and map the applicant journey. An engineer can analyze permitting data, prototype the experience, and build the integration. Permitting staff provide service and policy expertise

    3. How many people can you fund, and for how long?

      • Funding supports two full-time team members for one year, including time to monitor and improve the service after launch

    4. Can the team use AI tools and move from prototype to production?

      • The team has approved AI and cloud tools, access to the permitting system’s API, and established processes for reviewing AI-generated work, testing, deployment, monitoring, and maintenance

    5. Which specialists can support the team?

      • Accessibility, security, privacy, and permitting-system specialists can review the work at defined points

    Selected structure:

    Example 2: Expanded trio

    Project: Create a single application for several resident assistance programs

    1. What will the team deliver?

      • An accessible application that helps residents find and apply for several related programs without submitting the same information repeatedly. The service spans multiple departments, handles personal information, and connects to existing case-management systems

    2. Which capabilities can current staff cover?

      • A product manager can lead outcomes and coordinate departments. A designer-researcher can conduct research with residents and frontline staff, test the application, and improve accessibility. An engineer can prototype, build integrations, and lead technical delivery

    3. How many people can you fund, and for how long?

      • Funding supports three full-time team members for two years, with identified funding for continued operation and improvement

    4. Can the team use AI tools and move from prototype to production?

      • The team has approved AI and cloud tools for research, prototyping, and development. Before launch, it must complete data-sharing agreements, integrate with existing case-management systems, and confirm how the service will be supported and maintained

    5. Which specialists can support the team?

      • Privacy, security, accessibility, legal, data, and program specialists can participate in discovery, design reviews, and launch approval

    Selected structure:

    Example 3: Multidisciplinary team

    Project: Modernize an unemployment benefits application and case-management service

    1. What will the team deliver?

      • A public application and staff-facing case-management experience supporting eligibility, document submission, status updates, and ongoing communication. The service handles highly sensitive data, integrates with multiple systems of record, and directly affects access to essential benefits

    2. Which capabilities can current staff cover?

      • Program staff provide policy and operational expertise. Dedicated product, research, design, content, engineering, data, platform, accessibility, and service-operations capabilities are also needed

    3. How many people can you fund, and for how long?

      • Multi-year funding supports a dedicated delivery team and the staff required to operate, maintain, and improve the service after launch

    4. Can the team use AI tools and move from prototype to production?

      • The team has approved AI tools with clear restrictions for sensitive data and an established production environment. It must also strengthen integration testing, monitoring, incident response, data governance, phased releases, and long-term maintenance

    5. Which specialists can support the team?

      • Security, privacy, accessibility, legal, procurement, fraud prevention, cloud, data governance, and change-management specialists need to participate throughout delivery

    Selected structure:

    Executive, enterprise, and hybrid teams can all use these structures. Your team model determines where the team sits, while these options describe how people and capabilities can be organized around the work.

    cross-functional pair
    expanded trio
    multidisciplinary team
    Infographic comparing three AI-augmented delivery structures. A cross-functional pair combines product and research with engineering and data capabilities and is best for focused, lower-risk improvements. An expanded trio adds a third person to increase capacity or fill a priority capability gap and is best for larger or medium-risk services. A multidisciplinary team includes dedicated specialists in product, research and design, engineering, service expertise, data, operations, and responsible delivery and is best for critical, high-risk, or system-of-record services.

    The team is improving a focused part of an existing service rather than replacing the permitting system. Two cross-functional team members can use approved AI tools to increase their capacity and deliver the improvement with targeted specialist support.

    Approved AI tools can help the team work across research, design, development, and testing, but the service involves more users, workflows, and organizational coordination than a pair can reasonably manage. A third team member provides the additional capacity needed for a larger, medium-risk project.

    AI tools can increase the team’s capacity, but this critical service still requires dedicated specialists to manage its policy, data, integration, security, and operational requirements. A smaller team would not have enough capacity or specialist depth to deliver and operate it responsibly.

    Cross-functional pair
    Expanded trio
    Multidisciplinary team

    Key Roles in a Digital Service Team

    The roles you need depend on what your team is focused on and how it grows over time

    How to Think About Roles

    Digital service teams are built around a mix of skills, not just job titles. The roles you prioritize should reflect the problems you’re solving, the services you’re delivering, and your current level of maturity.

    Core roles and capabilities

    Most digital service teams include a mix of:

    • User experience (UX) and research

    • Product or service management

    • Engineering or technical delivery

    • Data and analytics

    • Subject matter expertise

    On smaller teams, one person may cover complementary roles, such as product management and research or engineering and data analysis. AI tools can help them complete tasks across those roles more efficiently. As the team takes on larger, more complex, or higher-risk services, it may need more dedicated specialists.

    Successfully hiring for digital service roles starts with understanding the capabilities your team needs most.

    Use the table below to identify which role best matches your team's needs.

    If you need help with...
    Consider hiring a...

    Most digital service teams in government focus on three core areas: user experience, data, and innovation and delivery. Together, these capabilities ensure services meet user needs, are informed by data, and can be built, improved, and delivered reliably at scale.

    Build your team based on your current needs, then grow and specialize as your services mature.

    Digital Maturity Stage
    Team shape
    User experience roles
    Data roles
    Innovation & delivery roles

    Prioritizing work and defining outcomes

    Product Manager

    Understanding user needs

    User Researcher

    Designing digital experiences

    UX Designer

    Improving end-to-end services

    Service Designer

    Creating accessible content

    Small, generalist team. Roles are combined or informal

    Design/research handled by generalists

    Limited or no dedicated UX roles

    Minimal data use- Basic reporting or ad hoc analysis

    1–2 people driving delivery

    Product, engineering, and delivery often combined

    Emerging team with clearer responsibilities

    provides guidance on combining capabilities, choosing a team structure, and determining when dedicated specialists are needed to use AI tools effectively.

    Determining what roles you need

    How Digital Service Roles Evolve Over Time

    provides more context on the stages below and explains how your organization’s maturity may influence which roles make sense for your digital service team.

    Diagram titled “Digital Service Teams Bring Together Multiple Capabilities.” A multidisciplinary team collaborating around a digital service is connected to five capabilities: UX and research, product management, engineering, data and analytics, and subject matter expertise. The right mix depends on the services, problems, and team’s maturity.

    Content Designer

    Accessibility compliance

    Accessibility Specialist

    Building software

    Software Engineer

    Technical architecture

    Technical Lead

    Managing engineering teams

    Engineering Manager

    Infrastructure and deployment

    Platform / DevOps Engineer

    Reporting and performance measurement

    Data Analyst

    Data pipelines and infrastructure

    Data Engineer

    Improving accessibility and equitable access

    Accessibility Specialist

    Early UX or service design support- Some user research introduced

    Basic analytics and reporting

    Early use of data to inform decisions

    Dedicated product or delivery lead

    Initial engineering support

    More structured planning and iteration

    Dedicated roles and consistent team structure

    User researcher, designer, or service designer roles defined

    Consistent UX practices

    Data analyst role established

    Regular tracking of performance and outcomes

    Product manager, engineers, and delivery roles clearly defined

    Consistent ways of working

    Multiple teams or expanded capacity across the organization

    Specialized roles (e.g., content design, accessibility)

    UX embedded across teams

    Data engineering and advanced analytics

    Shared metrics across services

    Multiple product teams

    Technical leadership and coordination roles

    Support for multiple initiatives

    Mature, multidisciplinary teams with leadership and career paths

    Full UX discipline (research, service design, content, accessibility)

    UX leadership roles

    Advanced data capabilities (engineering, science, performance)

    Data drives strategy and improvement

    Strong product and engineering leadership

    Continuous delivery and improvement

    Cross-org and cross-agency collaboration

    Exploring
    Organizing
    AI-Augmented Delivery
    Stages of Digital Maturity
    Standardizing
    Scaling
    Leading

    Hiring Resources

    Example role descriptions, job postings, interview guides, and evaluation tools for building high-performing digital service teams.

    Job Announcement Examples

    • Job Announcement Examples (USDR Talent Toolkit)

    • Digital Government Hub Resource Library (Beeck Center)

      • Searchable database with examples for a variety of roles

    Interview Guides

    This guide helps you hire UX Designers and UX Researchers at all levels with role descriptions, job postings, interview guides, and evaluation rubrics.

    The USDR Talent Toolkit has a collection in Docs and Word formats. Here are additional resources from the Talent Toolkit to assist in your hiring efforts:

    UX Hiring Guide

    Talent Toolkit Hiring Templates & Guides

    Interview Structure and Guides (USDR Talent Toolkit)
    downloadable hiring resources
    Job Boards List
    Social Media Campaign Template
    User Experience Hiring Guide (USDR).pdf
    PDF · 1MB
    Open

    Stages of Digital Maturity

    Understand where you are today and what to focus on next to build effective digital teams

    Identify Your Current Stage

    Use this page to identify the stage that best reflects your organization today, then use the guidance to prioritize your next steps. Most organizations will see elements of themselves across multiple stages. That’s expected. Use this model as a guide, not a checklist.

    Digital Maturity Model

    This model outlines five stages of organizational maturity in delivering digital services. Each stage describes common characteristics, priorities, and practical next steps for strengthening your organization’s capabilities and digital service function.

    How a digital service team fits

    A dedicated digital service team is not required to advance through these stages. Digital capabilities may be centralized within one team, distributed across departments, or supported through a hybrid approach. A dedicated team can help coordinate and strengthen these capabilities as the organization matures.

    helps you match how you launch and grow your digital service team to your organization’s current maturity

    Funding models and digital maturity

    Digital maturity is not tied to a specific funding model. It increases as funding becomes more predictable, coordinated, and aligned with long-term priorities. See Digital Service Team Funding for common funding approaches and how they can work together.

    Below the model, you’ll find more detail about each stage, guidance for progressing, and considerations for .

    Stage
    Budget
    Team Structure
    Work & Practices
    Coordination & Reach
    Outcomes & Impact

    Ownership: Who is responsible for this work, and who sets direction?

    1. Assign clear ownership for digital work, even if it is part-time

    2. Establish a basic team structure and reporting line

    3. Document how recent work has been delivered

    Stage
    Budget
    Team Structure
    Work & Practices
    Coordination & Reach
    Outcomes & Impact

    Autonomy vs. consistency: When should teams standardize how they work, and where should they retain flexibility?

    1. Define team roles and responsibilities

    2. Establish and document ways of working (e.g., planning, delivery, research)

    3. Pilot and refine standard practices across projects

    Stage
    Budget
    Team Structure
    Work & Practices
    Coordination & Reach
    Outcomes & Impact

    Reliance on individuals vs. systems: Can the organization depend on shared processes rather than individual effort?

    1. Implement shared templates, tools, and delivery processes across teams

    2. Reinforce consistent use of standards through management support

    3. Strengthen coordination across teams and stakeholders

    Stage
    Budget
    Team Structure
    Work & Practices
    Coordination & Reach
    Outcomes & Impact

    Navigating Constraints: How can the organization expand work across departments without slowing delivery?

    1. Integrate digital work into long-term planning and governance structures

    2. Establish cross-department collaboration mechanisms (e.g., shared roadmaps, prioritization forums)

    3. Expand capacity to support multiple teams or initiatives

    Stage
    Budget
    Team Structure
    Work & Practices
    Coordination & Reach
    Outcomes & Impact

    Growth: Where should the organization focus next to keep improving and leading?

    1. Invest in continuous improvement and innovation

    2. Share practices, tools, and lessons learned with other organizations

    3. Mentor and support other teams or agencies

    Identify where digital work is already happening
  • Support early experimentation and learning

  • Reduce reliance on borrowed or ad hoc staff

    1. Identify where digital work is happening and reduce reliance on borrowed or ad hoc staff

    2. Assess current hiring practices and identify gaps in targeting digital skill sets

    1. Perfect processes

    2. Scaling across the organization

    3. Formal governance

    Create space for teams to test and improve approaches
    1. Begin hiring for key digital roles (e.g., product, design, engineering)

    2. Start improving hiring practices, even if they are not yet consistent

    3. Identify gaps in internal support for developing digital skills

    1. Scaling to other departments

    2. Over-engineering standards

    3. Forcing uniformity too early

    Build role specialization while maintaining shared practices
    1. Implement structured and consistent hiring processes across roles

    2. Define roles, competencies, and leveling for digital positions

    3. Introduce onboarding and training to support skill development

    4. Align hiring with workforce planning and long-term needs

    1. Constant reinvention of practices

    2. Expanding too quickly across the organization

    3. Chasing innovation for its own sake

    Continuously improve practices based on outcomes and feedback

    1. Build and maintain recruiting pipelines for ongoing hiring

    2. Establish structured development opportunities (e.g., training, mentorship, career progression)

    1. Scaling to other departments

    2. Over-engineering standards

    3. Forcing uniformity too early

    Expand influence through partnerships and cross-government collaboration
    1. Use data to continuously improve hiring and development practices

    2. Create clear career pathways to support retention and growth

    3. Invest in internal talent development and strengthen your reputation as an employer of choice

    1. Defending existing processes

    2. Optimizing only within your organization

    3. Staying comfortable

    Exploring

    No dedicated budget for digital service work

    Work is funded informally or absorbed within existing team budgets

    No dedicated digital team; work is handled within existing teams as needed

    Digital work is not owned by a specific function or leader

    Each project is run differently, with little documentation or reuse of practices (e.g., no consistent use of user research, roadmaps, or agile rituals)

    Work is contained within a single team or department, with little to no involvement from others

    Success depends on individual effort; similar projects often produce very different results in timeline, quality, and usability

    Organizing

    Project-based or department funding supports work case by case.

    No consistent or coordinated funding model is in place.

    A small, executive team or function is formed with clear ownership

    Digital work begins to be separated from general IT or program work

    Practices like sprint planning, user research, or backlogs are introduced, but teams apply them inconsistently across projects

    Cross-team work happens on an ad hoc basis and requires manual coordination (e.g., meetings, emails, personal relationships)

    Some projects are delivered successfully, but timelines, quality, and user experience vary significantly between efforts

    Standardizing

    General fund, cost-recovery, or hybrid funding begins to support regular operations.

    Funding is more predictable but still tied to short-term cycles.

    Cross-functional teams (e.g., product, design, engineering) are established

    Teams are structured around delivering digital services, not just functions

    Teams consistently use shared practices, templates, and tools (e.g., intake processes, roadmaps, design standards)

    Projects regularly involve multiple teams or stakeholders, with defined processes for collaboration and handoffs

    Delivery is more predictable; teams can estimate timelines and produce consistent levels of quality across projects

    Scaling

    General fund, cost-recovery, or hybrid funding reliably supports ongoing work.

    Project funding supports expansion and other planned initiatives.

    Multiple teams or a executive digital service support work across departments

    Clear ownership, governance, and engagement models define how teams work with others

    Standard practices are adapted for different contexts (e.g., large programs vs. small projects) and continuously improved based on experience

    Cross-department collaboration is planned and embedded in how work gets done (e.g., shared roadmaps, joint prioritization, governance forums)

    Work delivers measurable outcomes (e.g., improved service delivery, reduced processing time, increased user satisfaction) across the organization

    Leading

    Stable funding supports ongoing operations and long-term investment.

    Funding models enable continuous improvement, innovation, and scaling.

    Digital teams operate as an enabling function across the organization

    Structures support coaching, platforms, and shared services beyond direct delivery

    Practices are continuously refined using data and feedback, and new approaches are tested and adopted proactively

    The organization collaborates across agencies or levels of government and contributes to shared initiatives or standards

    The organization consistently delivers high-quality digital services and is recognized as a leader or model for others

    Knowing your current stage is only the beginning. The next page explains what each stage means in practice and how to tailor your approach to launching a digital service team.

    Digital Service Team at Each Stage
    launching or growing a digital service team
    Exploring
    Infographic titled "Digital Services Maturity Model" showing five stages of digital service maturity as ascending steps: Exploring, Organizing, Standardizing, Scaling, and Leading. Each stage describes the characteristics of an organization's digital service capabilities and the actions needed to progress to the next level. The model begins with ad hoc digital work that lacks dedicated teams, funding, or ownership and progresses toward consistent, organization-wide delivery of high-quality digital services with shared standards, measurable outcomes, mentorship, and cross-government collaboration. A dotted diagonal line labeled "How to progress" illustrates continuous improvement across the stages. The graphic uses a stepped layout with light blue panels and blue headings to emphasize increasing maturity over time.
    Organizing
    Standardizing
    Scaling
    Leading

    AI-Augmented Team Delivery

    How a small digital service team can use AI to increase their delivery capacity

    How AI Fits Into Your Team

    AI augmentation is not a separate digital service team model. Executive, enterprise, and hybrid teams can all use AI tools as part of how they research, design, build, test, analyze, and document their work.

    AI tools can help cross-functional team members contribute across more parts of delivery and reduce time spent on routine tasks. They do not replace the people or expertise needed to understand problems, make decisions, and deliver reliable services.

    The next page explains the capabilities the team still needs and how they can be organized within different team structures.

    Using AI tools to accelerate the work gives the team more space to focus on user needs, make outcome-oriented decisions, check the quality of its work, and iterate based on feedback.

    Recent shifts enabling AI-augmented delivery

    Since 2024, two shifts have expanded what smaller digital service teams can realistically build, launch, and maintain:

    1. AI development tools — Claude Code, Gemini CLI, Codex, and similar — can support more routine coding, testing, and analysis work

    2. Government cloud platforms increasingly support iterative development, testing, and deployment

    AI tools can help a small digital service team increase its capacity, but they can also introduce new delivery, quality, and sustainability risks. Weigh both before deciding how the team will use them.

    Potential Benefits
    Potential Risks

    Local government can be a strong environment for an AI-augmented team. Local governments manage many focused workflows that affect residents and staff. They may also have more flexibility when selecting approved tools and shorter approval pathways for some projects.

    These services may offer opportunities to reduce manual work, simplify processes, improve access to information, support staff, or test an idea before making a larger investment. The team structure needed will depend on the work’s users, workflows, data, integrations, operational demands, and consequences of failure.

    Digital Maturity Overview

    Understand your organization’s current capabilities so you can launch and grow a digital service team effectively

    What is Digital Maturity?

    Digital maturity describes how well your organization is equipped to design, build, and improve user-centered digital services, including websites, online applications, internal tools, and other technology-enabled services for residents and employees.

    It reflects how your organization approaches:

    • Team structure and roles

    • Ways of working

    • Hiring and workforce capacity

    • Funding and governance

    A dedicated digital service team is NOT required for digital maturity. These capabilities may be centralized within a team, distributed across departments, or supported through a hybrid approach. A digital service team can bring them together, strengthen them, and help apply them more consistently across government.

    Your organization’s maturity shapes the kind of digital service team it can realistically launch and support. Without the right foundations, a team may face unclear ownership, limited capacity, slow decisions, and difficulty sustaining what it delivers.

    Understanding your org's digital maturity helps you:

    • Set realistic expectations for the team

    • Choose an appropriate scope and structure

    • Identify capabilities that need to be strengthened

    • Reduce delivery and sustainability risks

    You do not need advanced digital maturity to launch a digital service team. Start with an approach that fits your current capabilities, then strengthen the team as it demonstrates value and the organization matures.

    • Earlier stages: Launch a small team around one or two high-impact projects while building foundational capabilities

    • Later stages: Expand the team’s capacity and deliver across multiple services using more consistent practices

    • Advanced stages: Continuously improve services, support partners across government, and help drive organization-wide transformation

    Learn about the different stages of digital maturity and how understanding your organization's current stage can help guide your strategy, priorities, and decision-making.

    Use these resources to launch a team that fits your organization’s current capabilities while building toward greater capacity and impact over time.

    The most important changes are replacing “launching services” with “your team launch” and making maturity directly inform the team’s scope, structure, expectations, and growth.

    Assessment Overview

    This is the discovery phase for launching a digital service team. Go beyond a high-level view of digital maturity to assess your organization’s context, capabilities, constraints, and opportunities

    Moving From Learning to Action

    The previous sections introduced digital service team models, key success factors, and stages of digital maturity. Now, you’ll apply that guidance by gathering information through research, reports, interviews, and stakeholder conversations to assess your organization’s current state and readiness.

    Compare different perspectives and look for recurring themes, concerns, and opportunities that can inform what to prioritize and how to move forward.

    Pay attention to the stories people share about past efforts and how work gets done. This institutional knowledge can reveal important context that formal documents may not capture.

    What You'll Find in This Section

    Use what you learn to create a shared, evidence-based understanding of your government’s starting point. Stakeholders will use this foundation to validate findings, align on priorities, and decide what to do next.

    Helps a small team prototype and deliver more quickly

    Delivery may move faster than security, privacy, accessibility, procurement, or approval processes

    Allows cross-functional staff to contribute across more parts of the work

    A small team may become dependent on one highly technical person

    Reduces time spent on routine analysis, documentation, and development tasks

    AI-generated work may introduce errors or quality issues without careful review

    Creates an opportunity to demonstrate value before expanding the team

    Prototypes may become unsupported production tools without clear ownership and maintenance

    Builds internal knowledge about users, workflows, data, and technology

    Together, these shifts make it more realistic for a small digital service team to build, launch, and maintain focused workflow improvements that previously required more staff or outside support.

    Potential benefits and risks

    Where AI-Augmented Teams Can Make an Impact

    The will help you assess those factors and choose a team structure that can responsibly deliver and maintain the work.

    Infographic showing that AI-augmented delivery can increase capacity within executive or enterprise team models without changing the team’s placement, priorities, authority, or required safeguards. AI can accelerate research synthesis, prototyping, coding, testing, analysis, and documentation.

    As digital maturity grows, teams can deliver more consistently, take on more complex work, and improve services at a broader scale.

    Why it matters

    Applying Maturity to Your Team Launch

    What You'll Find in This Section

    Putting it all together

    Want help building your Digital Service Team?

    Stages of Digital Maturity
    Digital Services at Each Stage

    Putting it all together

    Want help building your Digital Service Team?

    Understand the organizational structure
    Build a current-state inventory
    Assess risk and history
    Request support here

    Teams may automate a flawed process before fully understanding the problem

    Reduces reliance on vendors for some smaller tools and improvements

    Staff may be expected to cover too many capabilities without enough time or expertise

    next page
    Infographic showing eight local government services that can benefit from AI-augmented teams: parks and recreation, transit, sanitation, code enforcement, public works, permitting, public records requests, and internal operations. A cityscape with trees, a bench, and a bus appears below the service icons.
    Request support here
    Infographic titled "Key Areas of Digital Maturity" highlighting four foundational components of organizational digital maturity. Four evenly spaced sections feature simple blue icons with bold headings and brief descriptions. Team structure and roles focuses on defining the right organizational structure and responsibilities to deliver digital services. Ways of working emphasizes using proven practices to collaborate, deliver, and continuously improve. Hiring and workforce capacity highlights attracting, hiring, and retaining the talent and skills needed for success. Funding and governance focuses on securing resources and establishing governance to support long-term impact. The graphic uses a clean, minimalist layout with a white background, subtle blue icon circles, thin vertical dividers, and a consistent blue color palette.

    Digital Service Team at Each Stage

    Match how you launch and grow your digital service team to your organization’s current maturity.

    Launching a Digital Service Team Based on Your Current Stage

    You don't need advanced digital maturity or a fully staffed team to begin. Start with a team structure, scope, and level of investment that fit your current capabilities. As the team demonstrates value and shows what is possible, you can strengthen its capabilities, expand its work, and build support for its long-term growth.

    Teams at any maturity stage can use approved AI tools to increase their capacity. Start with work that fits your current technical environment, data access, security and privacy requirements, and path to production.

    See for guidance on choosing an approach that fits your team’s capabilities.

    Digital work is ad hoc, with limited structure and unclear ownership

    1

    How to approach the team

    Begin by assigning ownership and bringing together a small group around one focused need. The team may rely on existing staff or short-term support while it tests a more coordinated approach.

    2
    • Assign a clear owner for the team or function

    • Bring together existing staff with complementary skills

    • Start with one focused service, workflow, or internal tool

    • Keep the scope manageable and document what the team learns

    3
    • Delivering something useful without waiting for perfect conditions

    • Showing what a digital service team can make possible

    • Building support for dedicated staff and funding

    An initial team and basic practices are beginning to take shape.

    1

    Establish a small, cross-functional team with a clear purpose, reporting line, and initial dedicated roles. The team may still rely on contractors, borrowed staff, or departmental partners to fill capability gaps.

    2
    • Define the team’s responsibilities and initial scope

    • Introduce basic planning, research, and delivery practices

    The team has defined roles, shared practices, and more predictable support.

    1

    Strengthen the team’s cross-functional capabilities and establish consistent ways of working. Create enough structure to support predictable delivery without preventing teams from adapting to different needs.

    2
    • Define roles, responsibilities, and career expectations

    • Use shared processes, tools, and standards

    Digital service capacity is expanding across the organization.

    1

    Launching becomes an organization-wide effort that aligns with strategic priorities and supports multiple teams.

    2
    • Support multiple services, workflow tools, or initiatives at once

    • Develop specialized roles and shared capabilities

    Digital services are continuously improved and influence work beyond the organizationDigital teams strengthen capabilities within and beyond the organization.

    1

    Position the digital service function to support direct delivery while also helping other teams improve how they work. Continue developing shared services, coaching, platforms, and specialized expertise.

    2
    • Help departments strengthen their own digital practices

    • Test and adopt new approaches based on evidence

    Build relationships with programs and other key partners

  • Use early services and workflow tools to refine how the team works

  • 3
    • Clarifying how the team operates

    • Reducing reliance on informal staffing

    • Building credibility through successful work

    Create a consistent approach to selecting and delivering work

  • Onboard new staff into established team practices

  • 3
    • Strengthening consistency across projects

    • Reducing reliance on individual knowledge

    • Developing the team’s long-term capabilities

    Coordinate priorities and resources across departments

  • Provide shared standards, platforms, and infrastructure

  • 3
    • Expanding capacity without losing quality

    • Clarifying coordination across teams

    • Reducing duplication and sharing what works

    Partner across agencies or jurisdictions on shared challenges

  • Share tools, practices, and lessons with other governments

  • 3
    • Sustaining a strong internal digital function

    • Continuously improving team capabilities

    • Supporting broader government transformation

    What's reasonable

    Focus on

    How to approach the team

    What's reasonable

    How to approach the team

    What's reasonable

    How to approach the team

    What's reasonable

    How to approach the team

    What's reasonable

    No matter your organization’s stage, the team still needs a clear purpose, defined ownership, cross-functional capabilities, and organizational support.

    AI-Augmented Delivery
    Exploring

    Focus on

    Focus on

    Focus on

    Focus on

    Organizing
    Standardizing
    Scaling
    Leading

    Determine Your Digital Maturity

    Assess your government's digital maturity and identify where to focus next

    The is a five-minute assessment that helps government teams understand their current digital service capabilities across funding, team structure, ways of working, coordination and reach, and outcomes and impact.

    After answering five questions, you’ll receive a digital maturity profile, practical next steps for each focus area, examples to help you take action, and recommended resources.

    USDR does not store your Digital Maturity Finder responses or results unless you opt in to share them with us.

    We’ll never sell your information or share it with anyone else. Your answers to the five digital maturity questions generate your results, and any additional information is completely optional.

    Digital Maturity Finder

    About the Digital Maturity Finder

    The results and recommendations are based on the Digital Service Toolkit and were developed with support from ChatGPT.

    Data & Privacy

    Open the Assessment
    Digital Maturity Finder
    U.S. Digital Response Privacy Policy

    Process for Assessing

    Assess your organization’s directive, structure, current state, and history to build a grounded understanding of where you are starting.

    What You'll Assess in this Discovery Period

    Use the structured discovery process provided here to understand your organization’s starting point, identify important gaps, and prepare stakeholders to make informed decisions.

    The process covers four areas presented in a suggested order, but you can move between them as new information emerges.

    1

    Clarify what is driving the work, what outcomes are expected, who has authority, and what funding or accountability requirements may shape the effort.

    2

    Understand where digital services fit within the organization, how decisions are made, and which teams, leaders, and partners need to be involved.

    3

    Document the people, services, systems, tools, processes, and vendors already supporting the work. This provides a practical view of existing capabilities, gaps, and dependencies.

    4

    Learn from previous efforts and understand how your organization approaches risk and change. Consider past successes, challenges, stakeholder concerns, and institutional norms that may affect the path forward.

    Visit to download the Information Gathering Starter Guide in your preferred format. Use this guide to capture key information throughout the discovery process. You’ll know you’ve gathered enough information to identify and prioritize opportunities when any remaining gaps are unlikely to significantly change your understanding of the current state.

    There’s a lot of information listed in this section, and some of it won’t be available or easy to track down. Make notes when you find these gaps and continue onward; think about how they impact your view of the organization as a whole.

    Download the Information Gathering Starter Guide

    This discovery period is about context, not solutions. The goal is to leave with a grounded understanding of where you are starting and what will shape the path forward.

    Getting unstuck

    Want help building your Digital Service Team?

    Templates & Tools
    Digital Service Directive
    Organizational Structure
    Current State Inventory
    Risk and History
    Request support here

    Assess Risk and History

    Get a clearer picture of how your government thinks about risk, change, and past efforts.

    Keep Your Assessment Focused

    Conversations about organizational history and risk can surface a wide range of experiences and concerns. Encourage candid input, but focus the discussion on what will help you understand how your government responds to change, which risks could affect the digital service effort, and what may be needed to build support.

    Use the for targeted questions that can help frame these conversations and keep your discovery focused.

    Examine past efforts

    Launching a digital service team will introduce new ways of working and affect existing processes. Even if your government has not created this type of team before, it has likely managed other changes that can offer useful lessons.

    These experiences become part of your government’s institutional memory and may shape how people respond to a new digital service effort.

    Examples in a government might include:

    • Launching a new website, permitting system, or 311 platform

    • Replacing financial, HR, or case management software

    • Centralizing services previously managed by individual departments or agencies

    • Introducing new data, accessibility, or cybersecurity requirements

    • Creating an innovation, performance, or customer experience office

    Assess your organization's risk tolerance, meaning how much uncertainty or change it is willing to accept and what conditions need to be in place before moving forward.

    Risk tolerance may vary across the organization. For example, city leaders may focus on public trust and political impact, while legal, procurement, security, and program teams may focus on compliance, operations, or service continuity.

    Explore:

    • Which risks receive the most attention

    • How new ideas are reviewed and approved

    • What information leaders need before supporting change

    • Whether pilots and small-scale testing are encouraged

    Conduct one-on-one or small-group interviews to understand how previous change efforts were experienced, which risks or concerns could affect the digital service effort, and what would help build support.

    Include people with different roles and perspectives, such as department or agency leaders, frontline staff, IT, legal, procurement, communications, and people involved in previous change efforts.

    For a 30-minute conversation, prepare two or three broad questions and use follow-up questions to explore what matters most to each participant. Bring a notetaker when possible so you can focus on the conversation.

    • What experience have you had with digital services in this government?

    • Which past initiatives does this effort remind you of?

    • What went well during those efforts, and what created challenges?

    • How could a digital service team support or affect your work?

    After the interviews, review your notes and group similar feedback into recurring themes. Pay attention to where stakeholders agree, where perspectives differ, and which concerns could affect the work.

    Create a short summary that identifies:

    • Build on: Past approaches, relationships, and capabilities that supported success

    • Avoid or address: Previous challenges and concerns that could create barriers

    • Plan around: Risks that could influence the team’s scope, placement, pace, or delivery approach

    • Keep involved: Stakeholders whose support, expertise, or approval will be important

    Bring your summary of past efforts, risks, concerns, and key stakeholders into . You’ll use these findings to build shared understanding, confirm priorities, and identify a path forward.

    What has caused previous efforts to slow down or stop
  • Who can help address concerns and keep the work moving

  • What feels clear or unclear about the directive?
  • What concerns would need to be addressed for you to support this effort?

  • Which governments or digital service teams do you think are doing this work well?

  • What are your hopes and concerns for this work?

  • Explore further: Questions that require more research or discussion

    Identify what helped these efforts succeed, what created challenges, and how those experiences could affect the current effort.

    Identify risks and concerns

    Use what you’ve learned about past efforts, risks, and concerns to shape your stakeholder conversations and identify areas that require deeper exploration.

    Gather Perspectives on Risk and Past Change

    Sample interview questions

    Example Stakeholder Conversation

    Context

    A city exploring a digital service team interviews its IT director to understand how the new team could complement the department’s existing responsibilities.

    Interview

    Interviewer: How could a digital service team support or affect IT’s work?

    IT Director: Departments often come to us with a solution already selected, such as a new application or website feature. We can evaluate the technology, security, and integration requirements, but we do not always have the capacity to determine whether the proposed solution addresses the underlying service problem.

    Interviewer: Where could a digital service team add value?

    IT Director: The team could work with departments earlier to understand user needs, map the service, and test possible improvements before a technology decision is made. That would give IT clearer requirements and reduce the risk of investing in the wrong solution.

    Interviewer: What concerns would need to be addressed?

    IT Director: We would need clear responsibilities so the digital service team does not duplicate IT’s work or make technical commitments without our involvement. IT should participate early when security, data, infrastructure, integrations, or ongoing maintenance are involved.

    Interviewer: What would help you support the effort?

    IT Director: Start with one department and a manageable service. Define how the teams will work together, involve our technical staff during discovery, and evaluate the results before expanding.

    This conversation identifies how a digital service team could complement IT, where responsibilities need clarification, and the organization’s preference for testing the approach through a focused pilot before expanding it.

    Identify Themes and Key Takeaways

    Use this summary in the stakeholder alignment process to validate what you learned, address different perspectives, and begin setting priorities.

    Prepare for stakeholder alignment

    Align Your Stakeholders
    Information Gathering Starter Guide
    Infographic titled "Example of Themes and Key Takeaways" showing how stakeholder interview findings can be grouped into actionable themes. A simple city skyline icon appears in the upper left, followed by the subtitle, "Here's what we heard from stakeholders across departments." The main content is organized into five color-coded columns representing example findings: Build on (green) highlights existing strengths such as cross-department partnerships, leadership support, and digital infrastructure; Avoid or address (red) identifies barriers including slow approvals, unclear requirements, and siloed communication; Plan around (gold) outlines risks such as budget constraints, staffing limitations, and legacy systems; Keep involved (blue) lists key stakeholders including City Council, department leaders, IT and security, and community partners; and Explore further (purple) captures open questions that require additional research or discussion. A small illustration of a diverse team collaborating around a laptop at the bottom reinforces that the themes were synthesized from stakeholder conversations. The graphic uses a clean, minimalist layout with rounded cards, simple icons, and a soft blue-accented design.

    What This Reveals

    Current State Inventory

    Document the services, systems, capabilities, and resources already supporting digital service delivery

    Decide What Your Inventory Should Cover

    Document the services, systems, people, capabilities, and resources most relevant to your digital service effort. Start with the priorities established through your directive or discovery work rather than trying to inventory your entire organization.

    The amount of information you collect will depend on your organization’s digital maturity and the scope of the effort. Focus on what stakeholders need to understand the current state, identify gaps, and make informed decisions.

    Use the to organize your findings, document sources, and identify information that still needs to be gathered.

    Build Your Current-State Inventory

    1

    Define the scope of your inventory

    Use your directive, priorities, and discovery findings to:

    • Name the services or processes you will review

    • List the departments, agencies, and teams involved in delivering them

    • Identify the residents, employees, businesses, or other groups who use them

    • Note which information is available, where it can be found, and what still needs to be gathered

    2

    For each service or process in scope, document:

    • Services and users: List who uses the service, how they access it, service volume, common pain points, and accessibility barriers

    • Tools, systems, and data: List the websites, applications, forms, systems, and data sources involved, including their purpose, owner, connections, and known limitations

    • Ownership and support: Name who owns the service, maintains its systems, approves changes, and provides operational support, including vendors and contractors

    3

    Compare what you documented with the , expectations, and available resources. If the directive is still developing, use the priorities and intended outcomes established so far.

    Use the completed inventory to:

    • Note which services, systems, capabilities, and partnerships already support the directive

    • Identify missing or underused capabilities, including gaps in ownership, skills, staffing, funding, and operational support

    Create a concise summary of the current state, key findings, and unresolved questions. Focus on the information stakeholders will need to understand the current environment, discuss priorities, and make informed decisions.

    Bring this summary into , where participants can validate the findings, identify priorities, and determine what should happen next.

  • Workforce and capabilities: Record the employees and contractors involved, including their roles, skills, available capacity, and relevant digital, IT, innovation, and service-delivery leadership job descriptions

    • See how other governments have defined digital leadership roles through examples from Maryland, Columbus, Portland, and Hennepin County

  • Resources and dependencies: Record available funding, contract or renewal dates, infrastructure needs, approval requirements, and other factors that could affect delivery

  • Flag delays, confusion, repeated work, and accessibility barriers
  • Identify duplicate tools, disconnected systems, manual handoffs, and overlapping responsibilities

  • List approvals, contracts, and technology dependencies that could slow or block progress

  • Record unanswered questions and who can help resolve them

  • The scope may range from a few priority services to an organization-wide review, depending on the effort and your organization’s digital maturity.

    Document the current state

    Evaluate the current state against your directive

    Prepare for Stakeholder Alignment

    directive’s goals
    Align Your Stakeholders
    Information Gathering Starter Guide

    When available, record service volume, processing time, completion rates, support requests, costs, and system usage. Note the source and time period for each measure, and identify where data is unavailable.

    Treat these as preliminary findings. Stakeholders will help validate and prioritize them during the alignment process.

    Alignment Workshop

    Use this alignment framework to help stakeholders review findings, align on priorities, and define a clear path forward

    Why Hold an Alignment Workshop?

    You’ve gathered information about your organization’s goals, stakeholders, current capabilities, and history. Now it’s time to bring the right people together to review what you’ve learned, build a shared understanding, and agree on a path forward.

    Through structured discussion and prioritization, this workshop helps your organization turn discovery findings into clear decisions and actionable next steps.

    Workshop at a glance

    • When to use it

      • After completing your current-state assessment and before making major decisions about launching or strengthening a digital service team.

    • Who to involve

      • Decision-makers and representatives from the teams that will influence, support, deliver, or be affected by the work. This may include leadership, IT, program teams, operations, HR, procurement, and service owners.

    • Time commitment

      • Plan for approximately four hours across at least two sessions. A common structure is one 2.5 hour working session followed by a 1.5 hour decision-making session.

    • How maturity affects the workshop

      • The workshop structure can be used at any maturity stage, but the findings, priorities, and next steps should reflect your organization’s current capabilities and readiness.

    By the end of the workshop, participants should:

    Visit to download the Workshop Organizer and Facilitation Guide in your preferred format. Use these resources together to plan and lead a stakeholder workshop, review assessment findings, confirm priorities, assign ownership, and define next steps for launching your digital service team.

    The provides more detailed guidance for selecting participants, structuring the sessions, preparing attendees, and facilitating each activity

    What you'll accomplish

    Download the Workshop Organizer & Facilitation Guide

    Templates & Tools
    next page

    Organization Structure

    Understand how your government is structured and where digital services work will fit

    Understand Your Government's Current Structure

    Where a digital service team sits within your organization can affect its authority, access to resources, relationships, and ability to work across government. Understanding your government’s current structure will help you identify where the team could operate effectively and which leaders, departments, and agencies would need to support it.

    Review your government’s most recent organizational chart to understand:

    • Which departments or agencies deliver services directly to residents

    • Where shared functions such as IT, HR, procurement, finance, and communications are located

    • How department or agency leaders connect to executive leaders and governing bodies, such as:

      • City: Mayor, city manager, or city council

      • County: County executive, administrator, or county commission

      • State: Governor, cabinet officials, or other statewide leaders

    • Which teams support work across multiple departments or agencies

    • How decisions involving more than one department or agency are coordinated

    Once you have a good understanding of the formal structure, look more closely at the people, capabilities, and potential partners already supporting digital services.

    Look across your government to identify:

    • Who manages websites, online applications, data systems, and other digital tools

    • Who works directly with residents or staff to understand and improve services

    • Where product, research, design, accessibility, engineering, and delivery skills exist

    • Which teams could provide expertise, approvals, or operational support

    Use what you learned about your organization’s structure, capabilities, and potential partners to identify one or two realistic placement options for the digital service team.

    Revisit to consider how an executive, enterprise, or hybrid model could operate within your organization. For each option, document:

    1. Where the team could be located

    2. The benefits and limitations of that placement

    3. The authority and resources the team would have

    4. The leaders, departments, or agencies whose support would be needed

    Which capabilities are missing, limited, or difficult to access

    Focus on the parts of the organization most likely to support, influence, or be affected by digital services work.

    Example Government Structure Findings

    A city may find that IT manages technology centrally, individual departments oversee their own services, and the city manager’s office coordinates priorities involving multiple departments. These relationships can help identify where a digital service team could be located and how it would work across the organization.

    In this example, the city manager’s office could be a strong placement option if the team needs to coordinate work across departments, provided it maintains a close partnership with IT.

    Identify Existing Capabilities, Partners, and Gaps

    This will help you identify who should be involved, which existing capabilities the team can use, and what additional roles or support may be needed.

    Example Existing Capabilities and Partners

    A city may find that communications manages the public website and content, IT maintains applications and infrastructure, individual departments oversee service delivery, and an innovation or performance team conducts research and improves processes.

    These groups could become important partners for the digital service team. Mapping their capabilities may also reveal overlaps and gaps, such as a need for additional product management, user research, service design, accessibility, or delivery expertise.

    Develop Initial Placement Options

    You do not need to select a final model or placement yet. These options will help stakeholders compare tradeoffs and provide a starting point for discussion.

    Examples of Digital Service Team Fit
    1. A city focused on a small number of mayoral priorities might place the team in the mayor’s office, giving it strong executive support and the ability to move quickly across departments.

    2. A state seeking to improve services across multiple agencies might place the team within central IT or a statewide administrative agency, providing consistent access to agencies, shared systems, and enterprise resources.

    Digital Service Team Models

    See for an overview of the capabilities the team may need.

    Infographic titled “Identify Capabilities, Partners, and Gaps” with three columns. Existing work and capabilities include digital tools and systems, service ownership and delivery, resident and staff research, and product, design, and technical skills. Partners and enablers include expertise, approvals, operational support, and cross-department coordination. Gaps include missing skills, limited capacity, limited access to support, and unclear ownership.
    Key Roles in a Digital Service Team

    Digital Service Directive

    Assess and strengthen the authority, expectations, support, and resources behind your digital services work

    What is a Directive?

    A directive establishes the purpose and authority behind a digital service team. It may take the form of a charter, mission statement, executive order, legislation, budget provision, or another formal or informal mandate.

    Example Digital Service Directive

    The City Manager directs the Department of Innovation and Technology to establish a cross-functional digital service team that improves how residents and employees access and use city services.

    The team will begin by identifying and improving one high-impact service that creates significant challenges for residents or staff. It will work with the responsible department to conduct user research, simplify processes, test solutions, and deliver measurable improvements.

    The team is authorized to:

    • Work across departments and access relevant service information

    When your organization is ready to give the digital service team a more durable mandate, recurring funding, or formal organizational placement, review .

    How directives relate to digital maturity

    A directive can support digital services at any stage of digital maturity. Earlier-stage organizations may begin with an informal mandate or a narrow directive focused on a specific service or pilot. As digital capabilities grow, directives may evolve to establish broader authority, more predictable resources, and clearer governance.

    A formal directive does not determine an organization’s digital maturity. What matters is whether its expectations are realistic given the organization’s current capabilities, funding, staffing, and support.

    What is driving the effort?

    Digital service team efforts begin in different ways, from an established directive or informal mandate to priorities that are still taking shape. Your role may be to build momentum around an emerging idea or turn a leader’s direction into action.

    Wherever you are starting, these questions will help you strengthen the authority, expectations, support, and resources behind the effort.

    Directive: Review or Develop

    1

    Source and authority

    • Who is sponsoring or authorizing the effort?

    • Who is championing the work or investing political capital in its success?

    • Who will expect updates on progress or outcomes?

    • Is the directive formal, informal, or still being developed?

    • If it is still being developed, who has the authority to approve or establish it?

    2
    • What is the team expected to accomplish?

    • Which office, team, or individual will be accountable for the work?

    • What outcomes are expected, and how will they be measured?

    3
    • Which leaders and stakeholders support the effort?

    • Who can help remove barriers or secure resources?

    • Is support concentrated with one leader or shared across the organization?

    Funding may already be established as part of the directive, or it may still need to be identified and approved. Review for additional guidance on funding approaches, common sources, and tradeoffs.

    1
    • Where does the funding come from?

    • Is it assigned to a particular budget, program, or line item?

    • Can funding be moved or used across departments?

    Compare the directive’s expectations with the funding, staffing, skills, organizational support, and time available or reasonably expected. Document any gaps and identify what would be needed to deliver the work successfully.

    If the effort depends on employees contributing limited time alongside their primary responsibilities, adjust the scope, timeline, or resources accordingly.

    Are any current practices expected to change or end?
  • Are important expectations implied but not documented?

  • If expectations are still being defined, who needs to help shape or approve them?

  • How could leadership or organizational changes affect that support?
  • Where is additional support or alignment needed?

  • Who controls spending decisions?
    2

    Funding uses and restrictions

    • What expenses can the funding support, such as salaries, benefits, software, hardware, facilities, or contracts?

    • Are there restrictions on how or where it can be spent?

    • How long will the funding remain available?

    • Will unspent funding expire?

    • Can the funding be renewed, and what conditions or approvals would apply?

    Conduct research with residents and city employees

  • Recommend changes to policies, processes, and technology

  • Develop and test digital service improvements

  • Coordinate with legal, procurement, communications, accessibility, and security teams

  • The Chief Innovation Officer will oversee the initiative and provide quarterly progress updates to the City Manager. The department responsible for each service will remain accountable for its ongoing operation and maintenance.

    Funding and Resources

    Initial funding will support staffing, research, technology, and implementation for a 12-month pilot.

    Success will be measured through:

    • Service completion rates

    • Processing times

    • User satisfaction

    • Staff workload

    • Other outcomes appropriate to the selected service

    At the end of the pilot, the City Manager’s Office will review the results and determine whether to continue, expand, or adjust the initiative.

    Expectations and outcomes

    Leadership and stakeholder support

    Funding: Review or Plan

    Funding sources

    Assess Whether Capacity Matches Expectations

    Use these findings to strengthen the directive and set realistic expectations with sponsors and stakeholders before moving forward.

    City Digital Service Initiative

    Purpose

    Initial Focus

    Authority

    Digital Service Team Funding
    Codifying Your Team
    Infographic titled "Digital Service Directive" illustrating how a directive provides the authority for a digital service team. A central document labeled "Directive" is connected to six possible sources: Charter, Mission Statement, Executive Order, Legislation, Budget Provision, and Other Formal or Informal Mandate. An arrow flows from the directive to a diverse digital service team collaborating around a laptop, representing the team operating under the directive's authority. Two callout boxes highlight the directive's purpose: "Provides authority and alignment" and "Guides the work and decisions." The graphic uses a clean blue color palette, minimalist icons, dotted connector lines, and a simple hub-and-spoke layout to show how different forms of organizational authority support digital service work.

    Ownership and Accountability

    Measures of Success

    Review and Next Steps

    Alignment Overview

    Bring stakeholders together to build a shared understanding of your current state, agree on priorities, and decide how to move forward

    What is Stakeholder Alignment?

    Stakeholder alignment is the process of bringing together the people who influence, support, deliver, or are affected by your team's digital services work.

    After gathering information and assessing your current state, alignment helps stakeholders make sense of what you learned, surface different perspectives, and reach agreement on a realistic direction.

    Why it matters

    Launching a digital service team often requires coordination across leadership, technology, programs, operations, procurement, HR, and other teams. Without alignment, unclear priorities, competing expectations, and unresolved concerns can slow progress.

    Building alignment helps you:

    1. Create a shared understanding of where things stand today

    2. Identify common goals, concerns, and opportunities

    3. Agree on the most important priorities

    4. Clarify ownership and decision-making authority

    5. Establish a realistic starting point for action

    Use these resources to turn what you learned during your current-state assessment into a shared direction. Alignment is not a one-time activity. Continue bringing stakeholders together as priorities evolve, new information emerges, and your digital services work moves forward.

    What You’ll Find in This Section

    Putting it all together

    Want help building your Digital Service Team?

    Plan the Alignment Workshop
    Facilitate the Alignment Workshop
    Infographic titled "Stakeholder Alignment" showing four groups of people connected to a central Digital Services Work hub. At the center is a laptop icon representing digital services. Four surrounding stakeholder groups are connected with dotted lines: Influencers, illustrated by two people in discussion with a speech bubble, representing those who provide input, set direction, or make decisions; Supports, illustrated by a person giving a thumbs-up with a heart icon, representing those who champion the work, remove barriers, or provide resources; Deliverers, illustrated by a person working on a laptop with a gear icon, representing those who build, manage, or operate digital services and solutions; and Affected, illustrated by a resident with community icons, representing people who use or experience digital services and are impacted by the outcomes. The graphic uses a clean blue monochromatic color palette, simple vector illustrations, and a hub-and-spoke layout to emphasize how different stakeholder groups contribute to successful digital services.
    Define Your Vision
    Request support here

    Plan the Alignment Workshop

    Set up a focused, well-structured session that brings the right people together to align and make decisions

    What Planning the Workshop Should Achieve

    • Ensure the right people are involved

    • Determine who will organize and facilitate the workshop

    • Set clear expectations for participation

    • Create the conditions for productive discussion and decision-making

    Plan for at least two sessions. A third session may be needed when decisions are complex, participants have competing priorities, or additional input is required.

    Planning Steps & Guidance

    1

    Visit to download the Workshop Organizer and Facilitation Guide in your preferred format. The Workshop Organizer will help organize details as you plan the workshop to present your findings, recommendations, and define a future state with clear next steps.

    Navigate to the for guidance on facilitating the workshop.

    2

    Identify who to invite

    Tips:

    • Limit attendees from any one team to keep the group balanced

    • Include voices that may not typically be in the room

    • Bring together people who need to hear from each other

    3

    Structure your sessions

    4

    Prepare participants

    Tips:

    • Reinforce that this is a working session, not a presentation

    • Encourage participants to limit distractions (e.g., laptops, phones)

    5

    Align on a shared foundation

    6

    Set the tone

    Tips:

    • Reinforce that the goal is alignment first, then prioritization

    • Be prepared to guide the conversation back on track if it gets stuck or goes off topic

    Choose the Right Facilitator

    Need support? USDR may be able to provide neutral support with planning, organizing, or facilitating your alignment workshop. Contact USDR to discuss how we can help!

    Download the Workshop Organizer & Facilitation Guide

    Templates & Tools
    next page

    Tips:

    • Schedule sessions close together to maintain momentum

    • Secure time early, especially for senior stakeholders

    Tips:

    • Don’t rely on pre-reading alone. Plan to briefly review key concepts during the session

    • Use simple, consistent language to avoid confusion

    Facilitate the Workshop

    Run a structured session to align on your current state and prioritize what to do next

    What You'll Accomplish

    By the end of the workshop sessions, participants should:

    The workshop will take a total of ~3-5 hours over 2-3 sessions. The times below are recommended minimums:

    Visit to download the Workshop Organizer and Facilitation Guide in your preferred format. The Facilitation Guide provides a practical run-of-show for aligning on the current state, prioritizing what matters, and turning discussion into action.

    • Schedule regular check-ins to review progress

    • Celebrate early wins to maintain momentum

    • Revisit priorities as needs evolve

    • Treat digital transformation as an ongoing practice, not a one-time exercise

    with guidance from the next page

    Suggested agenda for workshop sessions

    Exercise 1 Hopes and fears (30 minutes)

    Goal: Surface perspectives and build trust

    How to run it:

    Tips:

    • Set a clear scope to stay focused

    • Move forward if discussion gets stuck

    Exercise 2 Present findings (30 minutes)

    Goal: Align on the current state

    How to run it:

    Tips:

    • Focus on patterns, not details

    • Invite reactions to build alignment

    Exercise 3 Prioritize (60 minutes)

    Goal: Focus on high-impact next steps

    How to run it:

    Tips:

    • Move quickly

    • Note disagreements and keep going

    • Rebalance if everything clusters

    • Where are we today?

    • Where do we want to be?

    • What should start, stop, or continue?

    • How will we measure progress?

    Exercise 4 Finalize Decisions (90 minutes)

    Goal: Confirm priorities, assign ownership, and define the path forward

    How to run it:

    Tips:

    • Focus on decisions rather than reopening discussions

    • Keep the conversation action-oriented

    • Document commitments before the meeting ends

    • Capture parking lot items for future discussion

    1
    2

    For a two-session format, complete Exercises 1–3 during the first session and Exercise 4 during a follow-up session.

    Download the Workshop Organizer & Facilitation Guide

    Keep momentum

    Templates & Tools
    Define Your Vision
  • 3

    Define actions

    4

    Define how you’ll measure progress

    Tips:

    • Choose measures you can realistically track

    • Revisit and adjust as you learn

    5

    Align on structure and support

    Tips:

    • Ensure accountability is clear

    • Align leadership early to avoid delays

    6

    Set immediate next steps

    Tips:

    • Keep momentum by acting quickly on early priorities

    • Treat this as an iterative process, not a one-time plan

    Discuss:

    Output

    Key decisions and next steps

    Re-confirm your current and future state

    Share from prior session:

    Tips:

    • If your current future state weren't well established in exercise 3, define and confirm them before proceeding to the next topics

    Identify priority areas

    Output:

    Example 2×2 prioritization matrix with Value (importance) on the vertical axis and Effort (time, cost, complexity) on the horizontal axis. The matrix is divided into four quadrants: High Value / Low Effort – Start / Do First, High Value / High Effort – Plan / Prioritize, Low Value / Low Effort – Consider / Fill In, and Low Value / High Effort – Defer / Avoid. Colored dots represent grouped themes or opportunities placed within each quadrant based on their relative value and effort. A legend at the bottom indicates that each dot represents a theme or opportunity. The graphic uses a clean, minimalist design with blue axis labels and soft blue, green, gray, and red quadrant backgrounds.

    Tips:

    • Choose a mix of high-impact and achievable efforts

    • Avoid trying to do too much at once

    Checklist for Launch

    A practical checklist to help your government plan, launch, and sustain a digital service based on your organization's capacity, constraints, and goals

    Use this checklist to turn the decisions from earlier sections of the toolkit into a realistic plan for launching your digital service team. You do not need perfect conditions or a fully staffed team to begin. Start with a clear purpose and manageable scope, then build the structure and support the team needs to begin delivering value.

    Visit to download this checklist as a Google Doc, Word document, or PDF.

    Tips:

    • Keep actions specific and realistic

    • Assign clear owners where possible

    Identify the funding, staff, tools, and organizational support available now
    • Define the long-term result the team should help create

    • Identify who the team will serve and the value it should provide

    • Choose an executive, enterprise, or hybrid model

    • Confirm where the team will sit and who it will report to

    • Use the team’s to clarify its mandate, decision-making authority, and escalation path

    • Identify an executive sponsor who can champion the team and remove barriers

    Use the Alignment Workshop to work through these decisions with the people whose support, expertise, or approval the team will need.

    If the team will use AI-augmented delivery, confirm that approved AI tools, review processes, technical infrastructure, and a path from prototype to production are available.

    Revisit Foundations for Success as you establish how the team will deliver, make decisions, and support its work over time.

    The Keep the Momentum Going section provides additional guidance for reviewing progress, keeping stakeholders engaged, and adjusting priorities over time.

    Before beginning the team’s work, confirm that it has:

    Digital Service Team Launch Checklist for Governments

    Launching a team is not a single event. Establish what the team needs to begin delivering value, learn through its early work, and grow over time.

    Checklist

    Downloadable copy

    1. Assess your starting conditions

    Template & Tools
    digital maturity stage
    Current State Inventory
    Animated illustration of three checklist items being checked on a laptop screen, followed by a rocket launching upward and growing as it exits the screen.Animated illustration of three checklist items being checked on a laptop screen, followed by a rocket launching upward and growing as it exits the screen.

    Why this matters: Launch the team for your current conditions, not an ideal future state.

    2. Confirm the team's purpose and position

    Avoid: Launching a general-purpose technology team without a clear reason for its workAvoid: Launching a general-purpose technology team without a clear purpose or mandate.

    3. Align ownership and stakeholders

    Avoid: Moving forward while fundamental questions about purpose, ownership, or priorities remain unresolved.

    4. Choose the initial work

    Start with: Work that allows the team to deliver something useful, learn, and demonstrate value.

    5. Assemble the team

    Key principle: A small team may combine roles, but every required capability still needs a clear owner.

    6. Establish delivery and operating practices

    Critical: Plan to operate and improve the work after its initial release.

    7. Launch, learn, and adjust

    Early success: Deliver something useful, show what the team can make possible, and learn what it needs to work effectively.

    8. Measure value and plan for growth

    Early success: Deliver something useful, show what the team can make possible, and learn what it needs to work effectively.

    Ready to Begin?

    Want help building your Digital Service Team?

    Foundations for Success

    Understand the team, organizational, and delivery foundations that help digital service teams create meaningful results and build lasting capacity

    What Helps Teams Succeed

    Successful digital service teams need a clear purpose, defined ownership, the right capabilities, effective ways of working, and organizational support. Together, these foundations shape your organization’s digital maturity by strengthening both how the team is established and how consistently it can deliver effective services.

    You do not need to have everything in place before you begin. Focus on what your team needs now, then strengthen these areas as it learns and grows.

    Set a clear direction

    A shared direction helps the team focus its efforts and make consistent decisions.

    Start with a clear, manageable scope

    Define the initial problem or service the team will focus on, why it matters, and what outcome you want to achieve. Choose a scope that reflects the team’s authority, capacity, and available resources.

    What this looks like:

    • The team can clearly explain the problem it is addressing

    • The work focuses on a defined service or user need

    • Success is expressed as an outcome, not simply the launch of a tool

    • The initial scope is small enough to deliver and learn from

    Clarify who is accountable for the team and its work. Define responsibilities across program, product, and technical areas, including who can make decisions, resolve disagreements, and remove barriers.

    What this looks like:

    • One person or team is accountable for the work

    • Owners are identified for product, program, and technical decisions

    • Decision-making and escalation paths are clear

    • Ownership continues after an individual service launches

    Shape the team’s priorities around the needs of the people who use, deliver, and operate government services. Program staff, service owners, and users should help identify the problems the team takes on and inform its approach.

    What this looks like:

    • Team priorities reflect user and service needs

    • Users, program staff, and service owners help shape decisions

    • Technical work supports intended user and service outcomes

    • Policies, processes, and operational constraints are considered

    Bring together the capabilities needed to understand the problem, design an effective response, deliver it, and support it over time. Individuals may cover multiple responsibilities, especially on smaller teams.

    Review for more guidance on the roles and capabilities your team may need.

    What this looks like:

    • Product, design, research, engineering, and subject matter expertise are represented

    • Responsibilities are defined even when people cover multiple roles

    • Program and operational staff participate throughout the work

    • The team engages legal, procurement, communications, accessibility, and other partners when their expertise or approval is needed

    Engage residents, staff, businesses, or other users throughout the work. Test assumptions early, release manageable improvements, and use feedback to guide what happens next.

    What this looks like:

    • Users are involved before major decisions are made

    • Ideas are tested before the team invests heavily in them

    • The team releases small, usable improvements instead of waiting for a complete solution

    • User feedback and performance data inform ongoing improvements

    Identify leaders who can champion the team, reinforce its purpose, and remove organizational barriers. Confirm that the team has realistic access to the funding, staffing, tools, and operational support needed for its initial scope.

    What this looks like:

    • An executive sponsor actively supports the team

    • Leaders communicate consistent expectations about its purpose and priorities

    • Funding and staffing reflect the expected scope

    • The team has a clear path for approvals and escalation

    Connect discovery, design, development, implementation, and ongoing operations. Consider rollout, communications, training, support, maintenance, and continued improvement from the beginning, even if every detail has not yet been determined.

    What this looks like:

    • Operational teams are involved before launch

    • Training, communications, accessibility, and support are considered early

    • Long-term maintenance and service ownership are assigned

    • The team reviews user and operational outcomes to prioritize improvements

    You may already have some of these foundations in place, while others will develop as your team gains experience and demonstrates value. Focus first on what the team needs to deliver effectively now, then strengthen its practices, support, and capacity as its work and maturity grow.

    Define Your Vision

    Create a shared statement that guides what your digital service team will do, who it will serve, and how it will create value.

    A vision describes the future your team wants to help create. It explains what should be different for residents, employees, or government departments if the team succeeds. The goals and priorities established during the will help shape this vision.

    The vision should be ambitious enough to provide long-term direction and focused enough to guide priorities and decisions. It helps stakeholders understand what the team is working toward and determine which opportunities will move the organization closer to that future.

    In a vision describes the future you want to see. Missions are the specific efforts you undertake to move toward it.

    • Vision: Residents can access government services easily, regardless of their abilities, language, or technical experience

    • Mission: Redesign the city’s benefits application using user research, accessibility testing, and plain-language content

    directive
    Plan for ongoing funding
    long-term codification
    Request support here
    The team defines the problem before selecting a solution
    Vendor work includes documentation, knowledge transfer, and continued internal ownership

    A focused scope helps the team make decisions, demonstrate value early, and build momentum for future growth.

    Establish clear ownership & authority

    Clear ownership reduces delays, strengthens accountability, and prevents the work from becoming dependent on informal relationships.

    Center the team's work on user and service needs

    Technology can enable better services, but it cannot resolve unclear processes, responsibilities, or service needs on its own.

    Build for effective delivery

    Build a cross-functional team

    Cross-functional teams reduce handoffs and allow different perspectives to shape the work from the beginning.

    Work in a user-centered and iterative way

    This approach reduces the risk of building the wrong solution and helps the team improve its delivery practices as it learns.

    Support long-term success

    Secure leadership support and resources

    Leadership support is most effective when it comes with the authority and resources needed to act.

    Plan for the full service lifecycle

    Planning across the service lifecycle helps the team maintain what it delivers and improve services over time.

    Strengthen the foundations over time

    Key Roles in a Digital Service Team
    Infographic titled "Cross-Functional Teams" illustrating a diverse team collaborating around a table with a laptop, notes, and planning materials. Above the team, five connected capability areas are shown with simple icons and short descriptions: Research (understand needs), Design (create user-centered solutions), Product (define problems and prioritize), Engineering (build scalable solutions), and Subject Matter Expertise (provide domain knowledge). Below the team, a row labeled "Involve key partners when needed" highlights supporting functions with icons for Legal, Procurement, Communications, Accessibility, and Other Partners. Dotted lines connect the capability areas and supporting partners to the central team, emphasizing collaboration across disciplines. The graphic uses a clean blue color palette, flat vector illustrations, and a minimalist layout to show how cross-functional teams bring together the expertise needed to deliver effective digital services.

    Use findings from your readiness assessment and stakeholder conversations as a starting point. The vision should reflect shared needs and desired outcomes, not just the views of the team’s sponsor or founding members.

    1

    Review What You Learned

    Findings from your assessment to focus on:

    • The directive and expectations behind the effort

    • Recurring challenges with government services

    • Needs expressed by residents and employees

    • Gaps in current capabilities

    • Organizational priorities

    • Lessons from previous change efforts

    • Outcomes a digital service team could help achieve

    2

    Ask stakeholders:

    • Who should benefit from the team’s work?

    • What should be different for those people in the future?

    • What outcomes should the team help make possible?

    3

    Use the answers to develop one or more short vision statements.

    A simple structure is:

    Our vision is a government where [people served] can [desired experience or outcome].

    Another option is:

    We envision government services that are [intended qualities or outcomes] for [people served].

    4

    Review the draft against the following questions:

    • Does it describe a desired future rather than the team’s activities?

    • Does it clearly identify who should benefit?

    • Is it focused on outcomes rather than tools or projects?

    5

    Ask the appropriate sponsor and stakeholders to confirm the vision. Document any questions that still need to be resolved.

    Use the vision to guide:

    • Missions and project selection

    • Strategic priorities

    • Team capabilities and hiring decisions

    These are representative examples that your government can adapt to its context.

    During assessment and alignment, a city learns that:

    • Residents struggle to understand and complete city processes

    • Departments have difficulty improving services across organizational boundaries

    • Staff frequently rely on manual workarounds

    • Technology projects often begin before user needs are understood

    • The initial team will have limited capacity and no authority to replace departmental ownership

    A city where residents can easily access public services and employees can deliver them through simple, accessible, and effective processes.

    The city wants a future where:

    • Residents and employees both benefit from service improvements

    • Services are simple and accessible

    • User needs guide decisions

    • Departments work together to improve services

    • Technology supports better outcomes rather than driving the work

    What Is a Digital Service Team Vision and Why Does it Matter?

    Without a clear mission, your team risks becoming a general-purpose technology resource or taking on unrelated requests that exceed its capacity.

    How is this different from a mission?

    Example

    alignment workshop
    Scott Kubie’s “VMT Framework,”

    A single vision can guide multiple missions over time. Each mission has defined activities, responsibilities, and timelines.

    Develop the Mission With Stakeholders

    Vision Statement Examples

    Digital Delivery Team

    Departments consistently deliver reliable, accessible, and user-centered digital services that produce measurable improvements for the people who use and operate them.

    Executive Innovation Team

    Government can respond effectively to urgent challenges that require coordination across departments and disciplines.

    Small Pilot Team

    Residents and staff experience practical improvements to government services that address their most significant challenges.

    Digital Capacity Team

    Government teams have the practices, capabilities, and shared tools needed to continuously improve public services.

    Resident Experience Team

    Residents can easily find, understand, and access government services, including people who face the greatest barriers.

    Internal Services Team

    Government employees have simple tools and processes that allow them to spend less time on administrative work and more time serving the public.

    Citywide Service Improvement Team

    Residents and employees experience public services that are simple, accessible, and easy to deliver across city departments.

    Community-centered Digital Service Team

    Communities, especially those historically underserved, help shape government services that are accessible, understandable, and responsive to their needs.

    Example vision development process

    What stakeholders identify

    Draft vision

    What this vision helps clarify

    The vision does not determine the team’s first mission or project. It provides a shared outcome for evaluating which opportunities will move the city closer to the future it wants to create.

    What qualities should define the future experience of government services?

    Is it ambitious enough to provide long-term direction?

  • Is it focused enough to guide priorities?

  • Is it connected to outcomes the team can meaningfully influence?

  • Could multiple projects or missions support it?

  • Can stakeholders explain it in similar terms?

  • Partner and stakeholder expectations

  • Measures of progress

  • Communications about the team

  • Future decisions about growth and funding

  • Look for needs and desired outcomes that appear across departments or stakeholder perspectives.

    Define who benefits and what should change

    Draft the statement

    The exact wording matters less than whether the statement creates a shared and useful picture of the future.

    Test the statement

    Confirm and use it

    This emphasizes service quality and measurable outcomes.

    This fits an executive model focused on high-priority challenges that cross organizational boundaries.

    This provides a realistic direction for a small team beginning with limited capacity.

    This fits a team focused on enabling departments rather than directly owning every delivery effort.

    This centers the vision on a simpler and more equitable resident experience.

    This centers the vision on internal operations and the employee experience.

    This fits an enterprise team that supports service improvement across multiple departments.

    This gives community participation and equity a central role in the desired future.

    Encourage participants to focus on lasting outcomes rather than individual projects, team activities, or preferred technologies.

    If almost any outcome could fit under the vision, it may be too broad. If it describes a specific project or activity, it may be a mission rather than a vision.

    The vision can evolve as the team and organization learn, but changes should be intentional and discussed with the people accountable for the team’s direction.

    Launch Overview

    Turn your priorities into action by launching a digital service team that fits your organization’s needs, capacity, and constraints

    From alignment to action

    By this point, you have assessed your current state, gathered input from stakeholders, and identified where to focus. Now it is time to put those decisions into practice.

    Launching does not require perfect conditions or a fully staffed team. Start with a clear problem, a manageable scope, and an approach that reflects your organization’s current digital maturity. The goal is to deliver something useful, learn from the experience, and build from there.

    What a successful launch requires

    Every digital service team launch is different, but successful teams share a common foundation. Before launching, clearly define the team’s purpose, determine its initial scope, identify the roles it needs, establish ownership, engage key stakeholders, and consider how it can deliver value and grow over time.

    What You'll Find in This Section

    Use these resources as a flexible guide, not a rigid process. Focus on the steps that matter most for your organization today, make ownership and next steps clear, and continue improving as you learn.

    Putting it all together

    Want help building your Digital Service Team?

    Launch Checklist
    Keep the Momentum Going
    Codifying the Digital Service
    Infographic titled "What a successful launch requires" presenting six core foundations for launching a digital service. The graphic is arranged as a 2-by-3 grid of illustrated cards using a clean blue color palette. The six foundations are: a clearly defined problem and intended outcomes (target icon), realistic scope based on available capacity and resources (checklist and chart icon), clear ownership and decision-making authority (team with leader icon), a cross-functional team with the capabilities needed to deliver (diverse team collaborating around a laptop), early and ongoing input from users and stakeholders (two people speaking with chat bubbles), and a plan for rollout, support, measurement, and improvement (rocket surrounded by planning and measurement icons). A subtle city skyline runs along the bottom of the graphic with a laptop launching a rocket, reinforcing the idea of successfully launching a digital service. The overall design uses simple icons, minimal text, and a clear layout to highlight the key ingredients for a successful launch.
    Request support here

    Keep the Momentum Going

    Sustain progress by regularly revisiting priorities, tracking outcomes, and adapting as you learn

    Recognize progress and keep moving forward

    You're already doing great with all the efforts that you've made to get here! Meaningful change in government usually happens gradually, and building a digital service will definitely not be a straight line.

    Take time to reflect on what's working, where you're encountering challenges, and what you're learning along the way. These moments of reflection can help you maintain momentum, make informed adjustments, and continue moving toward your goals.

    Stay aligned and engaged

    Keep stakeholders informed

    • Share regular updates on progress, challenges, and key decisions

    • Create space for ongoing input and feedback

    • Reinforce shared ownership of outcomes

    • Bring stakeholders back together at least twice a year, ideally quarterly

    • Review progress against priorities and commitments

    • Revisit assumptions and emerging needs

    • Revisit the measures you defined and assess progress

    • Identify what's improving, what's stalled, and where additional support is needed

    • Compare results against your intended outcomes

    • Gather feedback from stakeholders, teams, and users

    • Discuss what's working well, what isn't, and why

    • Identify lessons learned and opportunities for improvement

    • Refine priorities and actions based on what you've learned

    • Add, remove, or shift focus as needs evolve

    • Update plans to reflect new information and changing circumstances

    • Position digital services as a long-term organizational capability, not a one-time project

    • Continue building relationships across teams

    • Maintain focus on the outcomes you're trying to achieve

    • Acknowledge milestones and accomplishments

    • Share stories of impact and improvement

    • Recognize the contributions of teams and stakeholders

    Every improvement, no matter how small, is a step toward delivering better services for the people you serve. Celebrating progress can help sustain energy and commitment over the long term. Keep it going!!

    Codifying Your Team

    When and how to establish your digital service team as a permanent part of your organization

    What Is Codification?

    Digital service teams often begin as temporary responses to an immediate need. Codification formally establishes the team’s long-term role through its mission, authority, funding, or organizational placement.

    Depending on your government, this might include a permanent budget allocation, an executive order, legislation, an organizational restructuring, or another formal action that gives the team a long-term role.

    Why it matters

    Beginning as a temporary initiative can help a team launch quickly and demonstrate value, but it can also leave the team vulnerable to leadership transitions, budget reductions, or organizational changes.

    Formalizing the team provides greater stability by clarifying its mission, authority, funding, and long-term role. It also supports future planning, helps attract and retain talent, and allows the team to continue improving government services as leadership and organizational priorities change.

    How codification fits into digital maturity

    Codification is not a separate stage of digital maturity or something every team should pursue immediately. During the Exploring and Organizing stages, teams should focus on delivering value, building trust, and establishing their role. As they move into Standardizing and Scaling, recurring funding, clearer governance, and formal organizational placement become more important. At the Leading stage, these foundations help sustain the team and its influence across government.

    Signs Your Team Is Ready

    Most organizations should focus on demonstrating value before pursuing codification. You may be ready when your team has:

    Delivered measurable improvements through successful projects

    Examples:

    • Reduced processing times or administrative burden

    • Improved resident satisfaction or service quality

    Built trust and strong partnerships across departments

    Examples:

    • Agencies regularly seek the team's expertise

    • Departments involve the team early in new initiatives

    Established a sustainable funding approach

    Examples:

    • Secured recurring budget appropriations

    • Implemented a cost-recovery or hybrid funding model

    Defined a clear mission and long-term role

    Examples:

    • Documented the team's purpose and responsibilities

    • Clarified governance and decision-making authority

    Demonstrated ongoing demand for its services

    Examples:

    • Maintains a consistent pipeline of projects

    • Receives requests from multiple departments

    Earned support from organizational leadership

    Examples:

    • Executive leaders champion the team's work

    • Budget officials support continued investment

    Assess Readiness for Codification

    These following questions are not intended to determine whether a team should be codified. It is meant to help identify gaps in impact, funding, stakeholder support, or organizational integration that may need to be addressed before pursuing codification:

    Codification can happen through one or more formal actions that establish your team's long-term role within the organization. Common approaches include:

    • Permanent budget appropriations

    • Executive orders or administrative directives

    • Legislation or local ordinances

    • Organizational restructuring

    • Formal governance or oversight structures

    Codification is rarely the result of a single successful project. It happens by consistently demonstrating value, building trust, and showing how the team improves services for residents and supports agencies across government.

    Continue measuring and communicating your impact, strengthening partnerships, and building support among executives, budget leaders, and elected officials.

    Sample Progress Update Template

    What we've accomplished

    • Key milestones reached

    • Notable successes

    What we're working on next

    • Current priorities

    • Upcoming activities

    Challenges or risks

    • Issues affecting progress

    • Support or decisions needed

    How you can help

    • Feedback requested

    • Decisions needed from stakeholders

    Keep updates concise and tailored to your audience

    Schedule regular check-ins

    Sample Quarterly Check-in Agenda

    Duration: 60–90 minutes Participants: Key stakeholders, decision-makers, team leads, and anyone responsible for advancing priority actions

    1. Review progress (15–20 minutes)

    • What progress have we made since the last check-in?

    • What milestones or accomplishments should we celebrate?

    • How are we performing against our goals and measures?

    2. Discuss challenges and lessons learned (15–20 minutes)

    • What obstacles or risks have emerged?

    • What isn't working as expected?

    • What have we learned that should inform our next steps?

    3. Gather feedback and identify opportunities (15–20 minutes)

    • What feedback have we received from staff, users, or stakeholders?

    • Have priorities, needs, or constraints changed?

    • Are there new opportunities worth exploring?

    4. Adjust priorities and actions (15–20 minutes)

    • What should we continue, stop, start, or change?

    • Do any goals, measures, or timelines need to be updated?

    • What actions should be prioritized before the next check-in?

    5. Confirm ownership and next steps (5–10 minutes)

    • Who is responsible for each action item?

    • What decisions were made?

    • When will we meet again

    Schedule these sessions in advance and include decision-makers whenever possible

    Learn from progress

    Track and review progress

    Focus on learning and adjust measures that are no longer useful

    Reflect and reassess

    Sample Reflection Questions
    • What's working well that we should continue?

    • What's not working as expected?

    • What have we learned since our last review?

    • What feedback are we hearing from users and stakeholders?

    • What should we start, stop, or change moving forward?

    Look for patterns and root causes, not just symptoms

    Adapt and sustain momentum

    Adapt and iterate

    Expect priorities to evolve and treat this as continuous improvement

    Reinforce this as ongoing work

    Use each check-in to strengthen alignment and connect progress to broader goals

    Celebrate wins and keep moving forward

    Increased digital adoption or operational efficiency
    The team is viewed as a trusted partner rather than a project resource
    Reduced reliance on one-time funding or grants
    Established how the team supports departments across government
    Has a clear process for prioritizing incoming work
    Elected leaders recognize the team's long-term value
    Questions to Ask

    Impact

    • Has the team delivered measurable improvements to government services?

    • Can you clearly articulate the value the team has created for residents, agencies, or staff?

    • Do you have examples and metrics that demonstrate success?

    Demand

    • Are multiple agencies seeking support from the team?

    • Does the team have a growing pipeline of work?

    • Would agencies notice a significant gap if the team no longer existed?

    • Does the team have a stable funding source?

    • Are key roles filled with permanent staff rather than temporary resources?

    • Is there a plan for leadership succession and knowledge transfer?

    • Do agency leaders support the team's continued existence?

    • Are budget, procurement, and human resources leaders familiar with the team's value?

    • Do elected officials or executive leaders view the team as strategically important?

    • Have digital practices such as product management, user research, and agile delivery been adopted beyond the team itself?

    • Is the team viewed as a core government function rather than a temporary initiative?

    • Is there a clear vision for the team's long-term role?

    Ways to Formalize Your Team

    Codification often happens in stages, with a team first established through an executive directive, later receiving recurring funding, and eventually becoming a permanent part of the organization.

    Keep building momentum

    As your team's mission, governance, and funding mature, formalizing the team can help ensure its work continues through future leadership, organizational, and budget changes.

    Infographic titled "Ways to Formalize Your Team" illustrating how an existing digital service team can become permanently established through one or more formal organizational actions. On the left, a diverse team collaborates around a laptop under the heading "Your Existing Team," with the caption "A team that is delivering value and ready to be established for the long term." In the center, five stacked cards labeled "Formalization Approaches" show common mechanisms: Permanent budget appropriations, Executive orders or administrative directives, Legislation or local ordinances, Organizational restructuring, and Formal governance or oversight structures. Blue connector lines and arrows indicate that any combination of these approaches can lead to the outcome on the right: "Permanently Established Team," showing the same team alongside a shield icon, with the caption "A recognized, stable team with a clear role, authority, and resources to deliver lasting impact." A callout at the bottom reinforces the message: "Governments often use more than one approach over time." The graphic uses a clean blue color palette, simple vector illustrations, rounded cards, and a city skyline along the bottom to emphasize that there is no single path to formalizing a digital service team.

    Sustainability

    Support

    Organizational Integration

    Templates & Tools

    Access and download copies that you can use for your digital service development

    Information Gathering Starter Guide

    Use this guide to capture and organize key information about your organization’s directive, structure, current state, risks, and history during the discovery process. It can help you identify gaps and develop a grounded understanding of your organization’s readiness.

    Learn how to use this guide in the .

    Google Doc

    • Preview the file

    • Create a copy that you can edit

    Word Doc

    Information Gathering Starter Guide [USDR Digital Service Toolkit].docx
    682KB
    Open

    PDF

    Information Gathering Starter Guide [USDR Digital Service Toolkit].pdf
    PDF · 141KB
    Open

    Workshop Planner

    Use this planner and facilitation guide to organize your alignment workshop, prepare participants, structure productive discussions, and document priorities and next steps.

    Google Doc

    Word Doc

    PDF


    Use this checklist to turn decisions from across the toolkit into a realistic plan for launching and sustaining your digital service team. It covers the team’s purpose, stakeholders, initial work, staffing, operating practices, measurement, and plans for growth.

    Google Doc

    Word Doc

    PDF

    Learn how to use this guide in the .

    Launch Checklist

    Learn how to use this resource in the .

    Preview the file
    Create a copy that you can edit
    Preview the file
    Create a copy that you can edit
    Process for Assessing section
    Workshop Planner & Facilitation Guide [USDR Digital Service Toolkit].docx
    1MB
    Open
    Workshop Planner & Facilitation Guide [USDR Digital Service Toolkit].pdf
    PDF · 910KB
    Open
    Digital Service Launch Checklist for Government Teams.docx
    685KB
    Open
    Digital Service Launch Checklist for Government Teams.pdf
    PDF · 120KB
    Open
    Alignment Workshop section
    Checklist for Launch section

    Helpful Resources and Articles

    State of Colorado OIT 2026 Strategic Reset - North Start document

    (slide deck)

    Colorado becomes first state to commit to the product model at scale

    Resources

    Digital Service Guides

    State of Colorado Digital Service IT Transformation

    Articles

    Want help building your Digital Service Team?

    Digital Service Teams 101: A Guide for State and Local Governments
    USDS Digital Services Playbook
    State of Colorado OIT Operating Model
    The Digital Service Was Never the Point:
    OIT 2026 Strategic Reset - North Star.pdf
    PDF · 339KB
    Open
    Organize to Deliver_ OITs Operating Model.pptx.pdf
    PDF · 1MB
    Open
    Request support here