Page Status - Draft
Sub Heading
As digital products scale and cross-functional teams diversify, maintaining a consistent and high-quality user experience becomes more complex—but also more critical. This Design Quality Initiative aims to establish shared standards, processes, and accountability around design excellence across our matrixed organization. By aligning around a common framework, we enable designers, engineers, and product managers to deliver cohesive, accessible, and outcome-driven user experiences—regardless of team structure or project scope.
Main Points
Its not often programs or projects are the same. Repeatable patterns perhaps but team should consider their approach for each request and kickoff. It's ok to adjust and refine as you go. A practice I call massaging the schedule. Schedule are like design visions, a north star and a stake in the ground to go after.

You can't report on health against nothing. Need a goal to measure against, a date is a goal. Milestones are the early indicators for achieveble goals and progress . Product dragging into UX backing engineering into a corner was part of the driver and birth of Agile. In many cases UX is the center of the Product Experiene Process

One of the many with Scrum projects, we know when we get there ... sense of time. 
See my thoughts on Development Frameworks.

UX working towards a g

Decision making - against time

Project toggles - Work vs Resources vs Time




Amazon Tablet Milestones

Business Requirements Document (BRD)
Description

Design Direction
Description

Scorecard + Health
Description
>> Insert Amazon Scorecards
>> Insert Hololens Scorecards, 


Heatmaps
Description

Percentage Complete
Description

Program Review ( Reporting + )
Stakeholders, Actions, Last week, this week, Callouts, Actions item owners

Mozilla Figma Template
>> insert diagram and link to file
Back to Top