The process of bringing a product or service to market is long and iterative, and it’s not uncommon for the design team to disengage before it’s complete. Often the design team will move on to other projects after delivering documentation to a team of manufacturers or developers. When new constraints and opportunities arise, the team responsible for implementation makes decisions that were left to the design team before, often losing sight of the original intention.
Design assurance seeks to mitigate the risks of compromise by continuing to involve design throughout production. By providing a process with regular reviews and open channels of conversation, design assurance provides consistency when new opportunities are considered, when new constraints arise, and when existing designs need to be extended for new circumstances. It also ensures that what gets built matches the intention of the design team, not just the documentation.Buy from Amazon Buy Elsewhere
Once per sprint, the Observations Suite development team sits with the design team to review the build. The design team then focuses on the relevant features, providing detailed feedback to the development team about misalignments.
How do we communicate a complex system without hundreds of pages of documentation?
How much documentation is too much documenation? How do we communicate dynamic designs?
What do engineers and developers need to bring a product to life?
Where do we put ideas and features that we don't have time or budget for?