I have a standardized design system-specific survey used across clients that we’ll customize to the inquiry to how they establish or monitor their system practice. So, yes, it’s design system specific.
That Discover precedes other steps is natural and doesn’t imply a lack of perpetual discovery. Just as these steps can be concurrent per feature, so can steps be concurrent across features too, intensely discovering two or three features while documenting four other features simultaneously.
I’m not talking about a single button. To design, build, QA – and, get a design community to agree on – all those types, variations, states, and behaviors to be accessible, functional, precise, and more is a non-trivial exercise. There’s much time involved in that. Based on my experience, the duration for that endeavor usually exceeds 200 hours.
I have conducted the workshop for as few as 3 or 4 and as many as nearly 100 cross-disciplinary staff (ideally an equal mix of design and engineering, plus product, content, research and other disciplines).
The primary objectives are to gather data and surface often very divergent views on what…
Thanks for your response.
Ideally, yes. Additionally, one of those five system teams depicted sought to cultivate a deep, mutually beneficial relationship with the research team, using the system site to publish research outputs tagged with system concerns (e.g., Color or Buttons).
I’ve replaced gender specific iconography with a genderless icon for all people. The specificity did not serve the narrative of the story.
The use of gender specific iconography began via a cue by Jina Anne – a leader and advocate for respectful conduct in our community – using such iconography in her article The Salesforce…
Nice article! That said, I’m struck by a few things.
Design systems (back then, “component libraries”) were used throughout the 2000s, and even at least as early as Dell.com’s library of “atoms and molecules” in 1999 created in partnership with Frog Design. Cisco, Sun Microsystems, Yahoo…
It’s less common for component-specific concerns of larger spacing to arise: a custom homepage’s row, a video player’s theater mode, a long form text’s inset relative to displays above and below. Those concerns are both rare and not reusable, so we encapsulate each within a component’s — or page build’s—styles separate from the distributed library.
Nemrut, thanks for your perspective. I think characterizing it as expensive waste depends on how your view of cost relative to value.
In our case, I recall – but can’t tease apart the numbers within our timekeeping – that the effort cost a person-week (40hrs) of time to coordinate and setup, and then person-day or two a…