User experience design process and documentation refers to

Blue Design (www.lanlanwork.com) is a dedicated and in-depth interface design company to provide an effective UI interface design, BS interface design, CS interface design, ipad interface design, packaging design, icon customization, user experience, interactive design, web site for the desired outstanding domestic and foreign enterprises. Construction, Graphic design services

Source: Speckyboy

if you want to subscribe to this blog content, automatically sent to your mailbox every day, please click here.

Document authoring contributes to product concept formation, design, creation, and performance measurement. However, the purpose of writing a document should not be solely for product maintenance. After all, nothing in writing can compare with the real product experience.

As the minimalist user experience advocate, Jeff Gothelf, described in an article in Smashing magazine, the detailed delivery of the user experience as a reference for the future is largely useless from the completion of the production. In today's era of simplicity and flexibility, the key to user experience should be the core of the product, not the overall delivery result. Whether you choose a simple or detailed process, the key is to ensure that the document helps the design move forward (not just a lagging indicator).

The following is an overview of product design development documentation, individual elements, and phases. Different companies have different product development and documentation processes (such as Spotify, see "Using Spotify to build a minimized product available"), but many of the deliverables below are partly common to most companies.

The method that we choose is the best way to use, you can choose according to your own situation.

respective relationship

In terms of product design documentation, theory and practice are completely different. We all know the basic principles of user-centric design. We can also recognize the whole process of different research methods, prototyping stages and documentation techniques from a variety of methods. However, you will often ask yourself the question: How does it work in practice?

Photo Source: The Design Process.

Simply put, the document is designed to complement the design process rather than simply as a complement to the design process. Before delving into it, let's take a quick look at the documentation work during product design development from a macro perspective. Below, we introduce the links between the various steps of the design documentation from a practical standpoint:

1. During the initial phase of the product definition, you need to brainstorm with all the people involved about the product and how the project will work. Brainstorming may bring a set of start-up plans, a streamlined framework, and a series of early conceptual maps and models.

2. Start the survey below and at this stage your team needs to refine all assumptions and fill in the blanks. This phase may vary depending on the complexity of the product, the timing, the level of knowledge available, and other factors. On the whole, however, it is beneficial to conduct competitive market analysis and perform customer surveys. If you have a ready-made product, it can be helpful to review analytical techniques, heuristics, content, product backgrounds, and user testing.

3. During the analysis phase, product marketing data collected as of now can provide the basis for user features, experience maps, and required documents such as functional spreadsheets and user task matrices prioritized by priority. At this point in time, product definitions, product priorities, and product plans have been defined and prepared to become more formal design deliverables. As discussed in user experience design process and documentation, sketches and flowcharts can also be produced continuously during this period.

4. The results of this phase will lead to the use of scenarios, concept maps and models to enter the design phase. Common document types include sketches, wireframes, prototypes, Task flowcharts, and design specifications. For example, the competitive analysis and user features obtained during the research and analysis phase will be applied to models, concept maps, and usage scenarios. This, in turn, affects intermediate or advanced deliverables such as wireframes, storyboards, and detailed models. Some companies view the research, analysis, and design phases as a large process, as shown in this overview.

5. In the implementation phase, a combination of code and design resources is required to produce products that conform to the design specifications.

6. At the time of the actual product release, support records, bug reports, and other analytical techniques are also required to continue to drive the product through successive versions of iterations and upgrades. In subsequent production models, it is necessary to continuously generate and monitor data in the form of analysis and reporting to ensure a successful continuation.

7. Finally, continuous measurements and iterations in the production environment through performance index tables and analytical techniques ensure continuous data-driven product improvement.

Read the full text >>

User experience design process and documentation refers to