± Revenues, Fails, & Emergence
May 2, 2019
Design Systems that Bring Revenue
Design systems are essential for digital products’ internal teams. There’s a major difference with enterprise products — the level of impact a system has externally.
Ok. What now?
There’s a big difference between those design systems and others by Salesforce, IBM, Shopify, Automattic, Dropbox, GE Digital and Google. These software companies have a customer community building applications on their developer platforms. The customer economy relies on and thrives with resources like design systems. Enterprise design systems are being built for both internal use and for customers.
Of course. And so ...
Admins, consultants and partners will all be customizing Salesforce. They will rely on Salesforce’s Lightning Design System to build their applications. IDC reports every dollar Salesforce receives, the economy building applications on the platform will receive $5.18 by 2022.
My opinion is that the system design are not just some accelators. It is a part of the machine of the maintains the A - Z of an organization experience.
Design system teams have enormous responsibility when both customers and internal teams are reliant on their system.
Design systems don’t bring in revenue themselves, but they benefit platform adoption. Adoption ties to revenue. This means systems are becoming more of a product than an internal tool to help productivity. Will this help or hurt the future of design systems?
Una Kravets takes some time to consider the implementation of design systems, and how and why they might not succeed. Don’t let your design system be like a New Year’s resolution that starts off well but fades by the Spring. With appropriate care it should start to blossom as the snow melts away.
...
If we see an object in its entirety before we see the individual parts, then the object as a whole needs to precede the component parts. The design system must be predicated on an initial, overarching direction, in this case the whole.
How SAP Fiori Can Help Transform User Experience?
Role-based. Role-based design focuses on eliminating ambiguity. Let your users remove unnecessary clutter irrelevant to their role so that users can navigate within platform with confidence.
Adaptivity refers to predicting user needs and fine-tuning workflows to be flexible in terms of adding new features.
Coherent. Apply the same solution to the same problem, As simple as that. Apply intuitive approach across all contexts.
Find the good sense between “insufficient” and ” too much” and don’t overwhelm your UI with nice-to-have stuff.
The best way to build the emotional connection between user interface and SAP user is to design it beautifully – fortunately UI Theme Designer for SAP offers great opportunities for customization.
There is no final deliverable in such a system; only an ever-evolving artifact that designers and product managers use to establish common ground. The yearly edition of the dictionary comes from a time when publishing was a process that resulted in a fixed artifact: a printed book. We need not be beholden to such constraints: A design system ought to be a dynamic, ever-evolving information environment. (A meta-information environment, since it will be used to produce other information environments; much as dictionaries and grammars are meta-books.)