Designing Effective Wizards: A Multidisciplinary Approach
暫譯: 設計有效的向導:多學科方法

Daina Pupons Wickham, Debra L. Mayhew, Teresa Stoll, Kenneth June Toley III, Shannon Rouiller

買這商品的人也買了...

相關主題

商品描述

  • Users want wizards—but there are no books devoted to wizard design!
  • Nuts-and-bolts guide to designing wizards
  • Includes checklists and examples
  • The complete guide to wizard design.
  • Practical usability and design techniques for successful wizard and software projects

All you need to know to build wizards your users will love:

  • Extensive lists of questions for gathering requirements
  • Iterative design and evaluation techniques
  • Guidelines for general page layout, controls, and navigation
  • Visual design tips and techniques for attractive and enticing wizards
  • Launchpad solutions for linking wizards
  • Advice for interactive feedback, error prevention, error recovery, and on-line help
  • Accommodate any user—experts and novices, worldwide audiences, multiple platforms, plus accessibility for users with special needs!

Designing Effective Wizards: A Multidisciplinary Approach is the first "nuts and bolts" how-to guide for designing wizards that help users perform their tasks. This book brings together key insights from a multidisciplinary team, including usability experts, technical writers, and visual designers—presenting a start-to-finish process for effective wizard design. The authors identify key issues and challenges encountered during the wizard development process, and IBM's best solutions.

Includes...

  • CD-ROM that contains interactive samples to help you explore the concepts of color, typography, layout, navigation, and launchpads for wizards. It also contains the screens from the case-study installation
  • Extensive examples throughout
  • A start-to-finish case study
  • Practical checklists, summaries, and sample forms

Table of Contents

Welcome!
What's different about this book?
Is this book for you?
How to use this book.
The authors and editor.
Acknowledgments.
1. Kicking off the project.

Why plan your project? Is a wizard appropriate for the task? Team skills. Resources and planning. Summary.


2. Gathering requirements.

Why gather requirements? Wizard design requirements. User definition-Who will be using your wizard? Inherent characteristics. Experience and education. Social and cultural characteristics. A technique for creating user definitions-User surveys. Product definition-What will the wizard do? Purpose and scope of the wizard. Technology and tools used to create the final wizard. A technique for gathering product requirements-Focus groups. Task analysis-What will the user be using the wizard for? Underlying structure of the task. Aspects of the task that can be simplified. A technique for gathering task requirements-Task analysis. Work environment-Where, when, and how will the users be using the wizard? Physical environment. Tools used to access the wizard. Social or workflow-related issues. A technique for gathering work environment-related requirements—Observational study. Competitive evaluation—Who else is creating a similar product or wizard? Aspects and features of competitive products or wizards. A technique for evaluating the competition-Competitive analysis. Summary.


3. Applying the iterative design process.

Why follow the iterative design process? Questions to ask before beginning. Overview of the iterative design process. High-level design iterations. High-level design steps. High-level design tests. Low-level design iterations. Low-level design steps. Low-level design tests. Interactive prototype iterations. Interactive prototype design steps. Interactive prototype design tests. Working product iterations. Working product design iteration. Working product design tests. Summary of guidelines discussed in this chapter.


4. Evaluating wizard designs.

Why evaluate wizard designs? Questions to ask before beginning. Usability evaluation techniques. Heuristic evaluation. Design exploration. Design evaluation. Competitive benchmark. Beta or post-release evaluations. Tasks to prepare for usability evaluations. Determine what to test. Recruit and schedule test participants. Prepare documents and questionnaires. Create prototypes. Determine what measures to collect. Conduct pilot tests. Guidelines for conducting usability evaluations. Invite the entire team to participate quietly. Videotape the session as backup. Encourage “talking aloud” . Don't assist the test participant. Consider testing multiple test participants at once. Consider performing remote usability testing. Follow-up tasks for after the usability evaluation. Follow up with thank you notes. Write a summary report. Implement design changes based on your results. Summary of guidelines discussed in this chapter.


5. General wizard design.

Why create wizard design guidelines? Questions to ask before beginning. General wizard guidelines. Overall goals of the design. Writing style. Page count. Page-specific wizard design guidelines. First page. Last page. Guidelines for launching dialogs from wizards. Guidelines for wizards on the Web. Summary of guidelines discussed in this chapter.


6. Navigation.

Why optimize your wizard's navigation? Questions to ask before beginning. Navigation methods. Back and Next buttons only. Tabs. Table of contents. Pull-down menu. Additional navigational options. Methods to help users estimate their progress through the wizard. Where am I now and where can I go? How do I get to the next page? Where have I been? How much do I have left to do? Summary of guidelines discussed in this chapter.


7. Visual design.

Why does your wizard need a good visual design? Questions to ask before beginning. Physical issues. Layout design—Defining your grids. Window size of the wizard. Orientation. Margins. Columns. White space (a divider and a grouping element). Web layout. Typography. Serif and legibility. Attributes and legibility. Choosing a typeface. Color. Color facts. Color on-screen. Using color in wizards. Color on the Web. Images. Types of images. Resolution and color depth. Compression techniques. Image size. Semantics. Summary of guidelines discussed in this chapter.


8. Launchpads and linking wizards.

Why link wizards? Questions to ask before beginning. Methods of linking wizards. Launching one wizard from within another wizard. Launching wizards from launchpads. Design issues for launchpads. The appropriate number of steps for your launchpad. Navigation among wizards, the launchpad, and other supporting dialogs. Dependencies between steps. Progress-related cues. Task progress and dependency cues. Consistency between the launchpad and its wizards. Access to your launchpad. Additional functions that can be supported by a launchpad. Teaching the user the conceptual model of how the product works. Supporting user exploration. Showing users how to do the task without the launchpad. Allowing users to personalize or build their own launchpads. Summary of guidelines discussed in this chapter.


9. Interactive feedback.

Why provide feedback? Questions to ask before beginning. General feedback guidelines. Auditory feedback. Feedback while interacting with the wizard. Feedback for controls. Feedback for subtasks related to the wizard. Feedback at the completion of the wizard. Progress indicators. Billboards. Status line. Confirmation dialogs. Displaying the object that your wizard created. Summary of guidelines discussed in this chapter.


10. Error prevention and recovery.

Why predict, prevent, and recover from errors? Questions to ask before beginning. Predicting errors. Preventing and reducing errors. All categories of user error. Data entry errors. Missing data errors. Misinterpretations of wizard choices. User-is-stuck errors. User-is-mistaken errors. Incorrect wizard assumptions. Other system errors. Recovering from errors. Inform the user that an error occurred. Help the user fix the error. Avoid all destructive actions. Allow users to cancel and reverse actions. Summary of guidelines discussed in this chapter.


11. On-line help.

Why provide help? Questions to ask before beginning. Should you provide help for your wizard? Types of help. Control-level help. Conceptual help. Task help. Implementing help. Pop-up help. Smartfields. Help dialogs. On-line books. Summary of guidelines discussed in this chapter.


12. Experts and novices.

Why design wizards for both experts and novices? Questions to ask before beginning. Designs that support experts and novices. Integrating expert and novice functions in wizards. Separating expert and novice functions in wizards. Guidelines for supporting experts. Provide access keys and shortcut keys. Show expert commands. Summary of guidelines discussed in this chapter.


13. Accessibility.

Why design for accessibility? Questions to ask before beginning. Types of disabilities. Mobility limitations and limited hand use. Cognitive disabilities. Deaf and hard of hearing. Vision impairments. Speech or language disabilities. Combinations. Understanding users with disabilities. Assistive technologies. Screen readers and Web page readers. Screen magnifiers. Speech recognition systems. Specialized keyboards and keyboard aids. Accessibility guidelines. Implement accessibility APIs. Provide accessible names and descriptions. Support easy keyboard and mouse navigation. Provide equivalent alternatives to auditory and visual content. Use redundant cues in your display. Avoid blinking text and flashing objects. Supply orientation and contextual information. Allow user personalization and customization. Design screens that resize cleanly and support older technologies. Provide accessible documentation. Additional sources for guidelines and information. Summary of guidelines discussed in this chapter.


14. Worldwide audiences.

Why design for a worldwide audience? Questions to ask before beginning. Localization versus internationalization. Content translation. Write text that is easily translatable into other languages. Support different word orders across languages. Allow the user to select and change the default language for your wizard. Ensure that your first wizard page is well-translated. Consider providing links to another language version. Account for regional differences in the wizard task. Layout translation. Leave room on the wizard pages for expansion. Provide scroll bars and resizable panes. Input translation. Take advantage of the operating system's resource base. Account for regional differences in names and other words. Use unambiguous controls for date and time formats. Support flexible formatting for numbers, monetary formats, and currency symbols. Account for differences in other data. Graphics for worldwide audiences. Create graphics that are understandable across cultures. Use representative populations. Use checkmarks instead of Xs in check boxes. Limit the file size and color depth of your graphics. Choose colors carefully. Practical concerns. Installation and packaging. Schedule. Sending files for translation. Summary of guidelines discussed in this chapter.


15. Multiple platforms.

Why design for multiple platforms? Questions to ask before beginning. Visual and interface design—Product consistency versus platform consistency. Option 1: Build a unique design. Option 2: Use the features provided by an off-the-shelf solution. Option 3: Emulate an existing platform design. Option 4: Work with a Web browser. Appearance and behavior differences across platforms. Platform and environment nuances. JavaScript in different browsers and browser versions. Text across platforms. Summary of guidelines discussed in this chapter.


16. Case study: Installation wizard.

Gathering requirements. User definition. Product definition. Task analysis. Design considerations. General design. Navigation. Launchpads. Feedback. Error prevention and recovery. On-line help. Worldwide audiences. Iterative design and evaluation. Launchpad: Welcome. Message 1: Missing prerequisites. Software License Agreement. Select Installation Language. Page 1: Select Installation Type. Page 2: Select Components. Message 2: Previous version of product detected. Page 3: Choose Destination Location. Page 4: “Up and running” . Page 5: Summary. Progress indicator: Installing products. Billboards. Confirmation window: Setup Complete.


Appendix A. Worksheet for gathering requirements.
Appendix B. Sample design checklist.
Appendix C. Sample screener questionnaire.
Appendix D. Sample usability participant agreement.
Appendix E. Sample participant instructions.
Appendix F. Sample scenarios for an installation wizard.
Appendix G. Sample post-evaluation questionnaire.
Bibliography.
Index.

商品描述(中文翻譯)

- 使用者想要向導,但沒有專門針對向導設計的書籍!
- 向導設計的基本指南
- 包含檢查清單和範例
- 完整的向導設計指南
- 成功的向導和軟體專案的實用可用性和設計技術

您需要知道的所有內容,以建立使用者會喜愛的向導:
- 廣泛的問題清單以收集需求
- 迭代設計和評估技術
- 一般頁面佈局、控制項和導航的指導方針
- 吸引人且誘人的向導的視覺設計技巧和技術
- 連結向導的啟動解決方案
- 互動反饋、錯誤預防、錯誤恢復和線上幫助的建議
- 照顧所有使用者——專家和新手、全球觀眾、多平台,以及對有特殊需求的使用者的可及性!

《設計有效的向導:多學科方法》是第一本針對設計幫助使用者執行任務的向導的「基本指南」。本書匯集了來自多學科團隊的關鍵見解,包括可用性專家、技術作家和視覺設計師——呈現一個從開始到結束的有效向導設計過程。作者識別了在向導開發過程中遇到的關鍵問題和挑戰,以及 IBM 的最佳解決方案。

包括...
- CD-ROM,包含互動範例,幫助您探索顏色、排版、佈局、導航和向導的啟動平台概念。它還包含案例研究安裝的螢幕
- 廣泛的範例
- 一個從開始到結束的案例研究
- 實用的檢查清單、摘要和範本

**目錄**
歡迎!
這本書有什麼不同?
這本書適合您嗎?
如何使用這本書。
作者和編輯。
致謝。
1. 啟動專案。

為什麼要計劃您的專案?向導是否適合這項任務?團隊技能。資源和計劃。摘要。

2. 收集需求。

為什麼要收集需求?向導設計需求。使用者定義——誰將使用您的向導?固有特徵。經驗和教育。社會和文化特徵。創建使用者定義的技術——使用者調查。產品定義——向導將做什麼?向導的目的和範圍。用於創建最終向導的技術和工具。收集產品需求的技術——焦點小組。任務分析——使用者將使用向導做什麼?任務的基本結構。可以簡化的任務方面。收集任務需求的技術——任務分析。工作環境——使用者將在何時、何地和如何使用向導?物理環境。用於訪問向導的工具。社會或工作流程相關問題。收集工作環境相關需求的技術——觀察研究。競爭評估——誰還在創建類似的產品或向導?競爭產品或向導的方面和特徵。評估競爭的技術——競爭分析。摘要。

3. 應用迭代設計過程。

為什麼要遵循迭代設計過程?開始之前要問的問題。迭代設計過程概述。高層次設計迭代。高層次設計步驟。高層次設計測試。低層次設計迭代。低層次設計步驟。低層次設計測試。互動原型迭代。互動原型設計步驟。互動原型設計測試。工作產品迭代。工作產品設計迭代。工作產品設計測試。本章中討論的指導方針摘要。

4. 評估向導設計。

為什麼要評估向導設計?開始之前要問的問題。可用性評估技術。啟發式評估。設計探索。設計評估。競爭基準。Beta 或發佈後評估。準備可用性評估的任務。確定要測試的內容。招募和安排測試參與者。準備文件和問卷。創建原型。確定要收集的測量。進行試點測試。進行可用性評估的指導方針。邀請整個團隊安靜參加。錄影會議作為備份。鼓勵「大聲思考」。不要協助測試參與者。考慮同時測試多位參與者。考慮進行遠程可用性測試。可用性評估後的後續任務。跟進感謝信。撰寫摘要報告。根據結果實施設計變更。本章中討論的指導方針摘要。

5. 一般向導設計。

為什麼要創建向導設計指導方針?開始之前要問的問題。一般向導指導方針。設計的整體目標。寫作風格。頁數。特定頁面的向導設計指導方針。第一頁。最後一頁。從向導啟動對話框的指導方針。網路上的向導指導方針。本章中討論的指導方針摘要。

6. 導航。

為什麼要優化向導的導航?開始之前要問的問題。導航方法。僅使用返回和下一步按鈕。標籤。目錄。下拉選單。其他導航選項。幫助使用者估計他們在向導中的進度的方法。我現在在哪裡,我可以去哪裡?我如何到達下一頁?我去過哪裡?我還剩下多少工作?本章中討論的指導方針摘要。

7. 視覺設計。

為什麼您的向導需要良好的視覺設計?開始之前要問的問題。物理問題。佈局設計——定義您的網格。向導的視窗大小。方向。邊距。欄位。空白(分隔符和分組元素)。網頁佈局。排版。襯線和可讀性。屬性和可讀性。選擇字體。顏色。顏色事實。螢幕上的顏色。在向導中使用顏色。網頁上的顏色。圖像。圖像類型。解析度和色彩深度。壓縮技術。圖像大小。語義。本章中討論的指導方針摘要。

8. 啟動平台和連結向導。

為什麼要連結向導?開始之前要問的問題。連結向導的方法。從一個向導啟動另一個向導。在啟動平台上啟動向導。啟動平台的設計問題。啟動平台的適當步驟數。向導、啟動平台和其他支援對話框之間的導航。步驟之間的依賴性。進度相關提示。任務進度和依賴提示。啟動平台與其向導之間的一致性。訪問您的啟動平台。啟動平台可以支援的其他功能。教導使用者產品運作的概念模型。支援使用者探索。顯示使用者如何在沒有啟動平台的情況下執行任務。允許使用者個性化或建立自己的啟動平台。本章中討論的指導方針摘要。

9. 互動反饋。

為什麼要提供反饋?開始之前要問的問題。一般反饋指導方針。聽覺反饋。與向導互動時的反饋。控制項的反饋。與向導相關的子任務的反饋。完成向導時的反饋。進度指示器。廣告牌。狀態列。確認對話框。顯示您的向導創建的對象。本章中討論的指導方針摘要。

10. 錯誤預防和恢復。

為什麼要預測、預防和恢復錯誤?開始之前要問的問題。預測錯誤。預防和減少錯誤。所有類別的使用者錯誤。數據輸入錯誤。缺失數據錯誤。對向導選擇的誤解。使用者被卡住的錯誤。使用者錯誤的錯誤。錯誤的向導假設。其他系統錯誤。從錯誤中恢復。告知使用者發生了錯誤。幫助使用者修正錯誤。避免所有破壞性行為。允許使用者取消和撤銷行動。本章中討論的指導方針摘要。

11. 線上幫助。

為什麼要提供幫助?開始之前要問的問題。您是否應該為您的向導提供幫助?幫助的類型。控制層級的幫助。概念性幫助。任務幫助。實施幫助。彈出式幫助。智能欄位。幫助對話框。線上書籍。本章中討論的指導方針摘要。

12. 專家和新手。

為什麼要為專家和新手設計向導?開始之前要問的問題。支持專家和新手的設計。在向導中整合專家和新手功能。在向導中分離專家和新手功能。支持專家的指導方針。提供存取鍵和快捷鍵。顯示專家命令。本章中討論的指導方針摘要。

13. 可及性。

為什麼要設計可及性?開始之前要問的問題。殘疾的類型。行動限制和手部使用有限。認知障礙。聽障和重聽。視力障礙。語言或語音障礙。組合。理解有殘疾的使用者。輔助技術。螢幕閱讀器和網頁閱讀器。螢幕放大器。語音識別系統。專用鍵盤和鍵盤輔助工具。可及性指導方針。實施可及性 API。提供可及的名稱和描述。支援簡單的鍵盤和滑鼠導航。提供聽覺和視覺內容的等效替代方案。在顯示中使用冗餘提示。避免閃爍的文字和閃爍的物體。提供方向和上下文信息。允許使用者個性化和自定義。設計可乾淨調整大小並支援舊技術的螢幕。提供可及的文檔。其他指導方針和信息來源。本章中討論的指導方針摘要。

14. 全球觀眾。

為什麼要為全球觀眾設計?開始之前要問的問題。本地化與國際化。內容翻譯。撰寫易於翻譯成其他語言的文本。支援不同語言的詞序。允許使用者選擇和更改向導的預設語言。確保您的第一個向導頁面翻譯良好。考慮提供另一種語言版本的連結。考慮向導任務中的區域差異。佈局翻譯。在向導頁面上留出擴展的空間。提供滾動條和可調整大小的窗格。輸入翻譯。利用操作系統的資源庫。考慮名稱和其他詞的區域差異。對日期和時間格式使用明確的控制項。支援數字、貨幣格式和貨幣符號的靈活格式。考慮其他數據的差異。針對全球觀眾的圖形。創建在文化上可理解的圖形。使用代表性人群。使用勾選標記。