Talk about wireframe: Ued and PD for different positioning of wireframe

This week and PD have a "wireframes and http://www.aliyun.com/zixun/aggregation/11647.html" >axure training. This is the demand of several PD, they also want to learn how to design wireframes, so want to more efficient to get started.

There were ued, PD, and I found that there was a lot of discussion about the wireframes, which I thought would be controversial.

One of the PD says, once, the boss asked her to draw a wireframe to show him, she spent a lot of mind on the online block diagram, the results delivered to the interaction designer, the interaction designer did not know how to play, the interaction designer said: You are all so good, I do not know what to draw. After that, the interaction designer was "polished" and delivered to 10243.html "> visual designer, and the visual designer found out that he was out of the play because the visual manuscript was already out and it was colored."

If you can improve the efficiency of the project, this is really good. PD directly draws a confirmation version of the wireframe, and then directly to the visual designer, the interaction is not needed. In many small companies, it does work so well.

Interactive designers said: Interactive designers assume a need for translation work, will be the business needs of PD, imaging, and add some user perspective, to help optimize the product, then translated into a visual designer can understand the language, and finally produce visual manuscript. This is only part of the story, if PD can also be representational and communicated well, why do we need to interact?

However, in the actual work environment, we must admit a prerequisite: the operation of the industry has specialized, each person's energy is limited.

So, the PD, the interaction, and the visual, though all are drawing, what is the difference in painting?

This is one of the pages in this ppt, and is also recognized by the presence of PD and ued.

PD wireframe diagrams are sometimes unavoidable and they need to:

1. Refine your ideas to help you write your needs documents

2. Better communicate your needs to others, such as interaction

3. A number of pre-research projects, the need to allow the boss to endorse and approve

But as PD, it is also concerned that the subsequent delivery to the interaction will affect the interaction. Moreover, everyone has the tendency to pursue perfection, after making a rough version of the wireframe, always feel too shabby, always involuntarily add a lot of details in order to make the first more professional. However, PD needs to focus on "helping to express ideas", responsible for "useful", such as function points, content blocks, business processes, and those with forks are not absolutely not concerned, absolutely not expressed, but need to add "for reference only."

As PD, you think forum A is very important, much more important than plate B, you can zoom in on an online block A and put it in the first place, but "position" and "structure" are not your main control, you have to communicate to the interaction is: plate A is very important, and why, and you do the processing, for reference only. An intelligent interaction will understand your needs and not because you hinder his expression.

Similarly, interaction and vision, although a team, often occurs because of boundary problems, such as: interactive involuntarily added a lot of color and texture, vision does not know how to deal with. Visual changes the structure of the wireframe, causing the interaction to assume that it does not correspond to the logic that it conveys.

So, as an interaction, pay attention to what you need to focus on:

1. Task flow-based on user needs, behavior, analysis of user tasks, as well as task flow, simplifying tasks.

2. Layout/structure--information divided into categories, what kind of layout more easy to use

3. Position/order-what sort of positions are arranged between the sections, what is the order of the user to guide them?

4. Level/weight-the level between the plate and the text

Note that in the expression position/order and level, the interaction can not help to add color to the wireframe, font design, but in the delivery, these are "for reference only." To convey to visual designers, it is still "these are more important than what, should be strengthened, and why". Smart visual designers naturally know how to express rather than feel bound.

To the visual stage, visual designers no matter how much like the visual manuscript, but also need to rethink the positioning, the need to enter the target user characteristics, demand, product style positioning.

I suggest that you keep in touch with the interaction designer when you change the wireframe structure. Last time I was doing a wireframe, and several PD, as well as several of our ued argued for a long time, confirmed the crumbs and search-screen location, and as a result of visual design, visual designers have changed my crumbs to different positions, and this has also been a dispute. Because of the adjustment of these positions, it will affect the functional logic previously identified.

If you have any questions, you are welcome to continue the discussion, so let's do it first ~

SOURCE Address: Http://heidixie.blog.sohu ... 59785390.html