Reading this book is to streamline the site of the Exploration Management Center. The book is also very short, more than 180 pages, get rid of half of the figure, the text is estimated less than 100 pages. The contents of the book are summarized in 8 words: Delete, organize, hide, transfer.
Watercress score 8.4:https://book.douban.com/subject/5394309/
Turing's interactive design series currently has 28 (really plenty): https://book.douban.com/series/5907
The 1th chapter is easy to say
Complex products are unsustainable: the more features you add, the more difficult it is to discover new features that are truly valuable to users.
In the design of technical products, there are at least three angles: managers, engineers and users. "Our users are primarily management leaders, but they don't like complex web design."
The 2nd Chapter clearly recognizes
To understand the user, you first need to go out of the office, first to the user to use your software where to do a survey, to know that they use your software is often what happens. If it is in an open office, there will be a lot of mutual interference: talk, phone, sms, mail. "Our mobile apps will be more in the boardroom" "It looks like we need to go to the Exploration Management center and talk to a few more people."
There are three types of users: expert users (willing to explore your product or service, and will give you various suggestions for improvement), casual users (just try it), mainstream users (not because of your technology to use your product, but to use your product to complete one of his tasks). Sometimes, it's best to turn a blind eye to expert users. "Our software users are not very much, this does not apply", to mainstream users and design.
Mainstream users |
Expert users |
Finish the work immediately |
Set your own preferences first. |
Think easy to manipulate is the most valuable |
Care about the precise control. |
Get the results you want |
Want to see the perfect result |
Afraid to spoil something. |
There's the urge to dismantle all the inquisitive |
I think it's just right. |
I think we have to match exactly. |
Want to see examples and stories |
Want to see the principle |
Consider "What are users doing?" ”。 Tell stories (time, place, people, what, how, why), describe the user experience. "Imagine the management of exploration to the Office, open the computer, browse the exploration site ..."
To be simple, be sure to set your goals higher and not use regular availability goals. "Can you just click on the link once to get the content that the user cares about?" Can not one click on the front page directly on the display? The key well has been hit to the destination level, is not directly the production of the well to push the dynamic to the management of the mobile phone? 】
Come up with a concise, clear, complete description, or even a description of a sentence.
Share the core design ideas with each member of the team.
The 3rd Chapter simple four strategy
In order to simplify the remote control as an example, four chapters are divided into four strategies: delete, organize, hide, transfer.
Delete----Remove any unnecessary buttons until they are reduced to no more.
Organizations----divide buttons into groups according to meaningful criteria.
Hide----Put the buttons that are not the most important on the slide and avoid distracting the user.
Transfer----A button that retains the most basic functionality on the remote control, transferring the other controls to the menu on the TV screen, transferring complexity from the remote control to the TV.
4th Chapter Delete
Remove unnecessary features, pay attention to the core experience, do not leave the incomplete function, delete it directly; don't speculate that the user may be like this, "the function is so much more slowly"; To listen to the customer's opinion, but never blindly, want to please all users at any time is impossible; prioritize features.
An example of streamlining a website is worth learning. Don't give users too many choices, don't distract users, set smart defaults, and don't set too many options.
is the revision before, after the revision is.
Remove elements that cause visual confusion:
- Use a blank or slight background color to divide the page instead of using a line
- Use as little emphasis as possible.
- Do not use thick black lines, uniform, light-colored line better.
- Control the level of information. No more than 3 layers (title, sub-title, and body)
- Reduce the change in element size.
- Reduce the change in element shape.
Delete text: Remove half of the text from each page, then delete half of the rest.
Streamline sentences: Use prepositions, do not use verbs in the ongoing style, with the active sentence, do not use the passive sentence, delete the uninteresting opening, straight to the point. Cut the crap.
Be careful not to cut too much, lose control, the elevator in the Apple Store is a negative (a button is not, let people helpless).
Chapter 5th Organization
"7±2 law", generally not more than 6 groups.
Use of generally accepted classification standards.
Don't think about the search feature: Organize your content effectively before you think about how to design your search. "If users like to use full-text search, it seems that the classification of the site is not reasonable"
By time, space is usually the user's familiar organizational way.
6th Chapter Hidden
Hide the "less common but not less" features. The "Personalization" feature is best for hiding the "
Divide the information into small pieces and display them in stages.
Timely appearance.
Give some hints and clues so that users can find hidden features.
7th Chapter Transfer
Transfer between devices. "Put some functions on the mobile side, some functions on the PC side"
transferred to the user. "Custom Folder" and so on, let the user to set it yourself "
Sometimes it's a simplification to have a feature that has multiple uses.
The highest level of simplification, should be experts and mainstream users will feel it very useful, such as kitchen knives, piano. "The novice and expert tools are the same, and the resulting works are vastly different." 】
The processing of unstructured data. "Allows users to easily load data!!! 】
The 8th chapter of the final exhortations
Stubborn complexity: Any application can have some complexity that cannot be eliminated. The key question is: Who will face these complexities? At this point, it is often not asked "how can this function be designed to be simpler", but asked "Where should we put this complexity?" ”
Spend half a day designing a solution that solves seemingly trivial problems, perhaps eliminating thousands of angry users.
Original Book Directory:
Copyright Disclaimer: Free Reprint-Non-commercial-non-derivative-maintain attribution (Creative Commons 3.0 license)
Shen Longbin's program Life
Original link: http://www.cnblogs.com/speeding/p/simple-and-usable.html
2016 6th: Simplicity first-interactive design four strategies