Tom Dell'Aringa The diagram’s vocabulary has strength in it’s simplicity to tell stories and trigger discussions at a certain level and of a certain type. I think your suggestion that I think such data is needless is without merit. Such storytelling could (and in my own experience has been customized to) overlay adoption detail: depth or breadth of…
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).