Service Design at MACBIS

When product teams are only focused on designing their own products, they are doing product-driven design and development. This siloed way of working can lead to duplication of efforts, a poor end-user experience, and a lack of cohesive processes in an organization.

Product-driven Design and Development. A hand-drawn illustration of five groups of people, each holding a different shape. They represent different product teams, each focused on designing and developing their own product.

Image credit: HCDU

There is so much value in product teams collaborating across the organization to create a cohesive service for end users. This is why we argue for integrated product and service design, which is when:

A hand-drawn illustration representing integrated product and service design. Product teams and their products are on a path, representing a larger user journey. Dashed lines connect the products to shared backend systems and data.

Image credit: HCDU

Based on this idea of integrated product and service design, the MACBIS HCD Unification (HCDU) team takes the following service design approach at MACBIS:

Applying Service Design to Your Project

A hand-drawn illustration representing the users of MACBIS products. CMS users include CMCS leadership, DSG leadership and staff, CMCS policy and operations groups, and CMS policy and operations groups. Non-CMS users include state staff, state IT and data vendors, and researchers and advocacy groups.

An overview of different users related to MACBIS products. Image credit: HCDU