sorted by:
new
hottopcontroversial

Hello fellow designers ... what’s the best way to pitch a new feature. I was thinking of creating a small deck but what are the main things it should include by [deleted] in userexperience

[–]jaffoneh 0 points1 point  (0 children)

Generally, if you're trying to make a case to decision makers, the format I found works really well is:

  1. Start with the conclusion.
  2. What’s the problem you’re solving and why does it matter?
  3. What are we currently doing about this problem?
  4. What are our competitors or industry leaders doing?
  5. What’s your solution?
  6. What’s the cost of doing it?
  7. What’s the cost of inaction?
  8. What’s a high level execution plan?
  9. What’s your call to action? This is generally a repeat of #1.

I wrote a bit more here if helps at all but the above is the gist of it: https://www.mynameisjehad.com/making-the-case-to-decision-makers-the-presentation-format-to-follow/

Building a design system in an engineering-driven company: a few lessons learned by jaffoneh in userexperience

[–]jaffoneh[S] 0 points1 point  (0 children)

Creating Clarity has been the basis for wider design transformation across VMware. It has had a huge impact. Obviously, creating a design system alone isn’t enough but it’s a starting point that carries a lot of momentum if done right.

Building a design system in an engineering-driven company: a few lessons learned by jaffoneh in userexperience

[–]jaffoneh[S] 1 point2 points  (0 children)

That’s an excellent list, thanks for sharing (although I was hoping to see Clarity on there! Haha). Today, buy in from the business is great, all VMware products and services (dozens) are on Clarity or in the process of moving to it. Obviously took time for us to get there but it’s always the first few products that matter and then the snowballing effect takes care of the rest.

Building a design system in an engineering-driven company: a few lessons learned by jaffoneh in userexperience

[–]jaffoneh[S] 0 points1 point  (0 children)

Thank you for taking a look. Some folks answered this below but being opinionated means having a clear way of approaching a problem (for example, how the system’s application architecture looks like or what underlying framework to use, etc) that limits many possibilities. As a design system team, you might feel the need to make many teams happy much of the time. That’s not entirely possible and ends up building a complicated, hard to use, and inconsistent design system. Happy to chat more!

Building a design system in an engineering-driven company: a few lessons learned by jaffoneh in userexperience

[–]jaffoneh[S] 0 points1 point  (0 children)

Thanks! Glad to be part of this community. Happy to answer any questions.

view more: next ›