Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

[TODO] Add core metrics and measures of success


Stakeholder Interviews – Fall 2020

Half hour interviews conducted with six internal staff including: marketing manager, product manager, engineer, engineering manager, accessibility specialist, and ux designer.

Key Takeaways

What aspects of the current workflow do you think could be improved?

  • A more methodical approach to meeting accessibility standards

  • QA is hard to do. We have an undependable staging environment and lack sandboxes for UI testing.

If you had a magic wand and could change one thing about how things work here, what would that thing be?

  • Dedicated engineering time to build accessibility tooling or features.

  • Clearer tie between roadmap and product strategy.

How do you hope the design system will help?

  • Reduce the number of new a11y bugs to less than a quarter of what we generate today

  • New bugs should only happen where there is new innovation

  • Produce software that is optimized for everyone with more sophisticated accessibility features

  • Easy to know what components exist, making it easier to design things based on available patterns. (I would like section of latest updates to the system that I could regularly reference)

What about the design system makes you nervous, apprehensive, or skeptical?

  • Worried that we'll create yet another pattern on top of everything else and fail to unify our interfaces.

What does success look like?

  • Our design system and the products we make with it address the full range of human experience, not just named disabilities.

  • Going to edx.org, hubspot, or wordpress, or the LMS and seeing consistent look and feel

What do you think a design system should not do, or not attempt to do?

  • Should not stymie innovation, though shouldn't encourage reinventing things for no reason.

  • Should not be all things to all people (at first). UI designers should be the the first audience.

What’s going to sink this ship? Fast forward a year from now and the design system initiative is a total failure. Why did it fail?

  • Squads decide it's faster to build things on their own than with the design system.

  • Lack of cross-functional agreement and prioritization to follow through.

What questions should we be asking you that we aren’t?

  • If there are components with no accessible versions available, what do we do?

  • How will we plan and time engineering effort needed to bring this system to life?

  • No labels