Hello! We are a team of designers and developers creating Rostelecom's digital design system. What for? There are many products and projects in a large enterprise, and each of them has needs that a design system can cover.
When you start building such a system, it seems to you that the first thing to do is to design all the necessary components. You conduct research, audit current projects and understand that this list of components is what you need, that is, you solve current problems and look a little into the future, assessing what else you may need.
And in the process, the question arises - how will users use the design system? Will they follow all the rules and guides if we put them into the system? If we write detailed manuals, will they be read? And if we don’t write, will there be a lot of questions about the boundaries and correctness of using the components? Which is better: a rigidly fixed instruction or, conversely, no rules?
, , - — , , ? , - . , , . , ( 26 !).
, - — . , , -. , ( ), , - , .
- :
?
— . - , , , , .
- , , -. , UX-, , . - , - , , — . , - .
. , -, — , UX. , -.
, , . , . — ?
, 20/80 — 20% -, 80% — . , -.
, - , , , . , . , — . , , , , . 20/80 — , - 5%, , 80%.
, — . , , - . , — :
— :
: - , , , , . . , - .
—