Bill
SB 242
Establish MDDS inside DoIT as a permanent unit to lead state digital services with user-centered design, accessibility, multilingual support, and consolidated procurement.
Status summary
- Sponsor / origin: Departmental bill requested by the Department of Information Technology (DoIT). Cross‑file: HB 221.
- Enactment / effective date: Bill takes effect July 1, 2025.
- Fiscal impact: Department of Legislative Services (DLS) projects no direct State or local fiscal effect; DoIT estimates minimal/no impact on small businesses.
Purpose and intent
- Codify the Maryland Digital Service (MDDS) inside the Department of Information Technology as a centralized, permanent unit to improve how state agencies design, build, operate, and procure digital services for residents and staff.
- Institutionalize user‑centered design, accessibility (including multilingual support), product management, and modern software development practices across State government.
Key provisions
- Statutory placement: Adds a new Subtitle 9 (sections 3.5‑901 through 3.5‑905) to the State Finance & Procurement Article to create MDDS within DoIT.
- Mission and duties:
- Assist state units to prioritize development/procurement of user‑friendly, accessible, multilingual digital platforms.
- Work collaboratively to consolidate and streamline Maryland websites and digital applications to reduce redundancy, complexity, and maintenance costs.
- Prioritize projects that are financially efficient and that deliver measurable benefits to residents.
- Oversee implementation of user‑centered design principles, accessibility standards, and digital service best practices across agencies.
- Leadership: The Secretary of Information Technology must appoint a Chief Digital Experience Officer (CDEO) to lead MDDS.
- Agency collaboration requirement: State units must collaborate with MDDS to align digital initiatives and funding with State priorities and the Statewide IT Master Plan.
Who is affected
- Primary: Department of Information Technology and other State agencies (policy, project prioritization, procurement and program alignment).
- Secondary: Maryland residents and agency staff — expected to benefit from more accessible, user‑friendly, and consolidated digital services.
- Small businesses / vendors: DLS and DoIT expect minimal to no direct impact; MDDS may change how agencies buy and manage digital work, potentially altering vendor procurement practices over time.
Policy context and background
- MDDS already existed in practice: DoIT hired a CDEO in August 2023 and officially created MDDS in January 2024; the office currently has about 20 staff and is modeled on the U.S. Digital Service.
- DoIT’s rationale: Building in‑house digital expertise and standardizing practices can reduce reliance on costly vendor solutions and avoid poor investments; DoIT has argued past fragmentation cost the State significant funds.
Procedural / timeline notes
- Departmental bill with DLS fiscal & policy note (First Reader: Jan 14, 2025).
- Codifies existing functions rather than creating a large new program; DLS projects no direct state/local fiscal effect.
- Effective date: July 1, 2025 (statutory implementation date).
Implications (brief)
- Operationally formalizes a central digital capability intended to improve service quality, accessibility, and cost‑effectiveness of Maryland’s digital offerings.
- Requires agency coordination and may influence future IT procurement, project selection, and website consolidation efforts.
Compiled from official sources — confirm details with the bill’s official record.
Sign in to ask a question.
