How to work with a designer

If you want to use the designer language, please stop saying those metrics and change the user.

In fact, most of the cases, "indicator" and "user" meaning is not too far away. For example, you might want to set a goal to increase the conversion rate of the registration page by X, and the other is: you want to remove the barriers that prevent users from registering and using products. But you see, "saying" here becomes important-making it easier for users to register vs. optimize the conversion rate of the registration process. The former talks about the value of the user, the latter is the company's success in order to generate the demand. The mindset of the designer is generally more biased towards the user side.

　　Give a few chestnuts:

Can I increase the click rate of this button?=> how can we let users know how simple this intimate new feature is?

We hope that this change will not impact on the indicators. => we need to make sure that this change doesn't make it difficult for users to use.

Come on, raise the viral spread factor.!=> encourages users who like this feature to share it with their friends.

Each designer has its own strengths, and these strengths need to be used to solve the right problem.

Every designer is different, even the "All-Star" designer has different ideas about the problem, because the design includes:

　　visual Design: does this category contain fonts, contrasts, hierarchies, "Old things look good?" and so on. Did you see the right place? are the details in the past or sloppy? The most important thing is whether the visual design is systematic.

　　Interactive Design: is it easy for users to do X? is the navigation system doing well? Do transformations and animations make apps more intuitive?

　　Product Design: is this design successful in solving the problem? Is this design working? Is there a clear vision for the product?

Some designers are surprised by visual performance, but have little experience with interactive design, and some designers can make smart product strategies, but they are weaker at execution level. Every design area has very difficult problems to solve, it is very important to pick out the right designer to solve the problem. You can't just replace a designer, but expect a new designer to act like your predecessor on the project. In general, to make a good design, you have to be exhaustive. If you can only have one designer, then it's better to be a generalist than to be strong in a certain way, but if you have a team of designers, it might work to get a lot of expertise in the field.

The more senior designers, the more they should be responsible for solving abstract problems.

To further illustrate, I use the following several levels and corresponding responsibilities as examples:

　　designer Level One: design a form for users to edit their personal files. This is clear-assuming that users have personal files to edit, the solution is to design a table on demand.

　　designer Level Two: design a good interface for users to edit their personal files. The solution can be a table, a WYSIWYG (WYSIWYG) editor, or a pop-up window.

　　Designer Level Three (wide): design a system for editing personal files, publishing articles, changing settings, and so on. Now we're talking not just about editing personal files, but about having a flexible editorial system that runs across the entire app.

　　designer Level Three (deep): design a way for users to "want" to update their personal files. Here, what we're talking about is that designers need to ask themselves: Why should users update their personal files? When to update? How to properly deliver such a request (please user Update profile)?

　　Designer Level Four: for the app to design a solution that can improve the authenticity of the user, "edit personal files" may not be our focus at all, perhaps a system that allows users to test each other (Peer-review) will be better.

　　designer Grade Five: to be able to discover the biggest problem for app/company/website, and design a solution. At the highest level, the top designers will be able to promote a product vision.

In other words, if a senior designer has a deep grasp of the product's strategy and vision, they will show a high degree of productivity. Conversely, if a senior designer is assigned a rookie level task (e.g. design a form), but he does not think that the table is the best way to solve the problem, he will not only be unhappy, he may also be poor. Getting caught up in this tension is the source of the team's morale: the more senior designers, the more frustrated they feel if they can't fully identify with the product's vision or strategy.

　The more time a designer spends with other designers, the better the work becomes (the designer himself)

It is one of the best ways for the designer to make comments on other designer works. If a designer always works alone and never communicates his work with his peers, it is almost guaranteed that their design will be worse than the results of regular communication. This is why designers are encouraged to work more with other designers during the development phase of the project (the design is constantly changing) and are encouraged to work with the engineers only during the execution phase of the project (when the main design is finalized and execution becomes more important).

The effort and value that designers pay for their work is hard to measure.

This is because a designer's goal is to achieve a quality experience-not just one face of the product, but the whole experience, and it can stand the test of time. Let's talk about clutter (clutter), from the qualitative point of view, we usually think that clutter is bad, then the design to add to what extent it will become "too messy"? It's hard to quantify. Similarly, the newly added design is unlikely to affect users immediately, but slowly, like the waves at 1.1 points to the cliff, the more things, one day users will find your site becomes messy. It's too late to have other, cleaner, minimalist apps popping up to solve your app's problems.

Similarly, designers often push for consistency between a app or a different part of the system. Perhaps this looks too picky, because at the functional level, if the process of uploading photos is consistent, is that enough?

The problem is that users are not just uploading photos. They may also upload videos, which can be confusing if they are designed to be completely separate from the way they are uploaded and filmed. It can be painful for users to upload photos or videos. Imagine if your computer's "file" options are different in each program, some at the top left, at the top right, bottom, or anywhere, and it's definitely a nightmare.

Indeed, sometimes designers lose control of weight and balance. Designers tend to pay too much attention to personal experience and despise the whole. In the same way, designers are sometimes not the target users of the product, but they will use their personal experience as an indicator and decide where to focus. (Of course, what I'm talking about here doesn't necessarily apply to all designers.) However, in fact, because design has been changing, short-term quantitative indicators have gone up and down, difficult to assess, such as the user's trust, understanding, and long-term feelings and joy-will be driven by the designers have a positive impact, but it is difficult to quantify the number.

　　What the designer cares about most is the details.

Really, you want to make the designer blush and get dizzy? Simulate each pixel in place, set a high standard, do not take the bad, in order to complete a small detail to take a step further, or spend a night to do those who set the Ming is to please the user's things. Every designer I know is very happy to sacrifice the night and the weekend with the product managers and engineers who respect the value of the design, and work together to achieve what each of us believes in, what everyone in the team wants to do, the good, the first-class, the real level of the product.