A few years ago, I joined Airbnb when I graduated from the Human-Computer Interaction program at the University of Michigan. Before that, I only had two internship jobs. As a graduate, my qualifications and knowledge are still shallow. I learned a set of interaction design and research processes in school, which is nothing more than some steps such as research, competitive product analysis, user portraits, user testing, etc. . When doing projects in school, there is often a whole semester, applying these processes to make some designs. So at the time, it seemed that the designer had nothing more than some processes and documents, then made a low-fidelity and high-fidelity design prototype, and finally gave a set of design annotations to the engineer, and you were done.
I was very excited when I first started working and felt that there are so many things that could be changed now - everything here and there. With this mentality, I have also done a lot of designs, and in retrospect, the things I have made are very fragmented. One of the projects was particularly impressive to me. It was when I wanted to redesign Airbnb's listing details page and thought I had a lot of good ideas. Last year the project was brought back to product planning and another designer in our group, Sunny, took over the project. From the perspective of her entire design process, it is really different from the way I took in the past, and I also learned a lot from it. She will think from the information structure, the user's decision-making process, etc., and actually use charts and words to explain and communicate the entire idea and process. This step is a key step for designers to communicate with the team why they want to do such a design and strive to reach an agreement.
△ From Sunny | From information structure to wireframe to final high fidelity
With the growth of experience, it is also obvious that designing is not the end of giving some flowcharts and designs. Those I learned in school are all tools, and the core is to use these learned tools to solve problems encountered in practical work, to help myself and the group to think. These processes of thinking and communication require some auxiliary "outputs" to make b2b data their presentation more logical, efficient, and persuasive.
Design briefs are usually used for relatively large design projects. By completing an introduction document, you can record what problems the design is to solve, and at the same time, you can help yourself to think and answer some questions during the filling process. Sometimes I feel that I have some ideas, so I directly start the design exploration, but the process is a bit rushed. If you take a step back and ask yourself some such questions, you will have some more mature and systematic directions in your mind, and the design will be more clear. Usually the design brief will include: Vision, Problem statement, Opportunity, Target audience, Use cases, etc.
Design context ( Context )
In a corporate environment, designers often collaborate with other designers, product managers, engineers, etc. Meetings are a way to communicate ideas, but beyond that, there are tools for sharing designs online, like Redpen, invision. When other people come to your design sharing page, how to clearly understand: