Answer the question
In order to leave comments, you need to log in
Design rules for a multi-page service. How to organize it?
Hello.
There is a cloud service with 10+ pages and their number is increasing.
There are 2 designers.
There is an active development of the service, the introduction of new styles, elements, pages, redesigns.
We work in Figma.
Some new pages break previously defined styles.
I don't have time to check everything in detail. In addition, there is an active development of design and we need some kind of "channel" for informing designers, while so that they do not have mess in their heads. That is, verbally informing is not effective.
Creating a set of rules by which designers could control and navigate themselves could improve performance.
But how to do that?
Describe in a word document? Maybe there is some kind of system, methodology?
What can you recommend to read on this topic?
Answer the question
In order to leave comments, you need to log in
There is such a thing called guidelines ... They are usually made by the art director.
This is a detailed instruction on what is possible and what is not, how and why. Where are the indents, the sizes of headings, subheadings, etc.
+ Components in Figma solve this problem.
Roughly speaking, this is an extensive, but very clear framework within which a designer can work.
Hi,
in short: hire a design lead.
Your question is about setting up processes, and out of the context of the rest of the project team.
After all, most likely, FE, BU, and BA teams interact with designers.
And do not throw them out of the process - they also need to be disassembled with the current screens, take them to work or discuss. They should also be included here.
Description and adjustment of the process on the project is the work of the lead team.
He is responsible for efficiency, delivering results and meeting deadlines.
And this will affect not only the organization of the file in Figma, but also the sprint plan - who, when and at what time meets to discuss new, old and other things.
Usually, an approximate flow is described on the wiki: stages, responsible people, order of meetings.
Often BA helps with this by the way.
And so they can advise a lot of things, but each project and team is a little bit unique and not everything will work for you, what worked, for example, for my team.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question