A strategy that many teams adopt in order to get buy-in from stakeholders is to build a proof-of-concept, or “guerrilla design system”, that hints at what their team would be capable of if they were granted a proper budget. Getting approval and funding is one of the biggest challenges of creating a design system. One of the key milestones at the beginning of the journey is getting top-down business approval to unlock the time and budget required to build a design system. Maintenance - making sure that the system lasts.Adoption - getting people to use and contribute to the system.Birth - convincing stakeholders and getting the design system funded.It’s the very thing that enables a design system to progress through the three crucial stages that are necessary for it to succeed: A style guide is no longer an afterthought, but the cornerstone of a successful design system workflow. Design system documentation sites like the ones you can create with zeroheight are no longer just aesthetic artefacts-they’re a foundational part of how design gets communicated and delivered at a company. By the time the next iteration comes along, the product has moved on, and the documentation is no longer relevant. Without a design system underpinning a product, creating pretty documentation after-the-fact is a waste of time and resources. Clients and stakeholders just didn’t see the value of meticulously explaining your thought processes and the decisions behind your design work, once the work had already been completed and shipped. For a long time, design pattern documentation was an after-thought, tacked on at the end of projects as a nice-to-have, or abandoned altogether because of a looming deadline.
0 kommentar(er)
