5.4 - Documenting Design Decisions
Enroll to start learning
Youβve not yet enrolled in this course. Please enroll for free to listen to audio lessons, classroom podcasts and take practice test.
Interactive Audio Lesson
Listen to a student-teacher conversation explaining the topic in a relatable way.
Importance of Documenting Design Decisions
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Today, we're going to discuss why documenting our design decisions is crucial. Can anyone tell me why we should keep track of changes we make?
Itβs because we need to remember what we changed in the design!
That's right! Additionally, documenting reasons and outcomes helps us evaluate what works and what doesnβt. What could happen if we don't document our decisions?
We might repeat the same mistakes or forget good changes we made.
Exactly! This is why we will focus on three main points when documenting: what was changed, why it was changed, and how it was tested. Let's make this memorable by using the acronym 'WHT' for What, How, and Test. Can you remember that?
WHT! What, How, Test! Got it!
Great! Understanding this will help us become better designers.
What to Include in Documentation
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Now that we understand the importance of documentation, letβs discuss what exactly we should include. What are some examples of what we might document?
We could write down specific design changes we made!
That's very true! Documenting specific changes is essential. Can someone give me an example of how to phrase that?
Like saying, 'I changed the color of the button from blue to green.'
Exactly! Another aspect is why we made that change. Let's brainstorm why changing the color might be important. How could we phrase that?
We could say, 'The blue button blended in too much with the background.'
Perfect! Just like that! So remember, itβs key to note both the changes and the reasons behind them.
How to Test and Adapt Design Changes
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Letβs move on to how we test our design changes. What do we do after weβve made adjustments?
We need to test them to see if they work better!
Exactly! Testing is critical. Can someone explain how we should document our testing process?
We could say, 'Tested with six participants using a mid-fidelity prototype.'
Great! So, keep in mind that we need to provide a clear description of how we tested our design changes to understand their impact.
So we got What, How, and Test for documentation!
Correct! Remember WHT throughout your design process.
Practical Application: Documenting a Design Change
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Now letβs apply what we have learned! Suppose we decided to change the icon for the help button to make it clearer. How would we document this?
We could write: 'What: Changed icon design for the help button to a question mark.'
Excellent start! What comes next?
Why: 'Users reported confusion with the previous help icon.'
Perfect! And how would we finish it?
How: 'Tested this change with user feedback in round three session.'
Thatβs it! Fantastic teamwork! Keep practicing documenting like thisβit will make you better designers.
Introduction & Overview
Read summaries of the section's main ideas at different levels of detail.
Quick Overview
Standard
Documenting design decisions is a critical part of the design cycle. This ensures a logical progression in design iterations, clarifies the rationale behind changes, and reflects on user feedback. By systematically documenting what was changed, why it was changed, and how it was tested, designers can keep track of improvements and ensure informed decision-making.
Detailed
Documenting Design Decisions
It is essential to meticulously document every change made during the design iteration process. This section outlines the three main elements of documenting design decisions:
- What was changed: Clearly state the modifications, for example, "Moved the settings icon and labeled it."
- Why it was changed: Justify the change with relevant user feedback or usability issues, e.g., "Users struggled to identify the gear iconβwe increased the success rate from 2 out of 6 to 6 out of 6."
- How it was tested: Describe the testing process used, such as, "Tested in Round 2 with a mid-fidelity prototype."
By maintaining detailed records of these aspects, designers can track their iterative decision-making logic, assess the effectiveness of changes, and enhance overall user experience. This documentation serves as both a reference for future projects and a communication tool for stakeholders.
Audio Book
Dive deep into the subject with an immersive audiobook experience.
What Changes Were Made
Chapter 1 of 4
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
For each change:
β What was changed: βMoved settings icon and labeled it.β
Detailed Explanation
This part emphasizes the importance of clearly documenting what specific changes were made to the design during the iterative process. For each adjustment, designers should state exactly what was modified. By doing this, it helps to keep track of the evolution of the design and provides a clear reference for future evaluations.
Examples & Analogies
Think of this like a recipe book where you note down adjustments for each dish you prepare. If you add a pinch of salt or switch the heating method, writing it down allows you to recreate that dish in the future or share it with a friend who might want to try it.
Why Changes Were Made
Chapter 2 of 4
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β Why: βUsers struggled to identify the gear iconβwe increased success from 2/6 to 6/6.β
Detailed Explanation
This section highlights the rationale behind each design change. Itβs crucial to document why a specific change was implemented, which often revolves around user feedback or encounters with challenges. This reflection helps clarify the design reasoning and demonstrates how user testing directly informs design modifications, showcasing a user-centered approach.
Examples & Analogies
Imagine youβre adjusting a classroom layout based on student feedback. If students complain that they canβt see the board from their desks, noting that you rearranged the seats for better visibility is crucial. This lets everyone understand why the classroom setup changed based on their experiences.
How Changes Were Tested
Chapter 3 of 4
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β How tested: βRound 2 mid-fidelity test.β
Detailed Explanation
Documenting how each change was tested is essential for transparency in the design process. This includes specifying which test cycle or method was used to gather user feedback after changes were implemented. This information allows designers to evaluate whether the changes had the desired effect and helps inform future testing approaches.
Examples & Analogies
Think of a scientist writing down their experiments. Just as they detail each method and observation to validate findings, designers keep a record of their testing methods to understand how effective their revisions were, just like an experiment confirming a hypothesis.
Importance of Documentation
Chapter 4 of 4
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
This documentation tracks your iterative decision-making logic.
Detailed Explanation
The final point stresses the overall importance of documentation in the design process. By tracking all design decisions, their reasons, and testing methods, designers create a clear narrative of their journey. This transparency is beneficial not only for reflectively assessing their own work but also for communicating with team members, stakeholders, or future project designers, ensuring that the evolution of the design is clear and understandable.
Examples & Analogies
Imagine keeping a journal of your learning progress in school. By documenting what you learned, what worked, and what didnβt, you can easily reflect on your growth over time, and give valuable insights to your teachers or classmates who might face similar challenges in their learning.
Key Concepts
-
Documenting Changes: Keeping track of what changes are made during the design process.
-
Rationale for Changes: Clarifying why a particular change was necessary helps inform future decisions.
-
Testing Changes: Documenting how and when changes were tested ensures that the design is validated against real user feedback.
Examples & Applications
An example of documenting a change could be: 'Changed the font size for better readability because users found it too small in the previous version.'
Another example could be documenting testing results, such as: 'The help button icon was tested during user sessions, resulting in increased user satisfaction from 3/5 to 5/5 ratings.'
Memory Aids
Interactive tools to help you remember key concepts
Rhymes
WHT for every change, it's not a game! What, How, Test is the right name!
Stories
Imagine two designers working on a project. One keeps a detailed journal of their changes and reasons, while the other does not. When they present their project, the first designer easily explains their choices, while the second struggles to recall why they chose certain elements.
Memory Tools
WHT: W for What was changed, H for How it was tested, T for Test results.
Acronyms
WHT
Documenting design changes is easy to remember using this acronymβWhat
How
Test!
Flash Cards
Glossary
- Design Decisions
Choices made regarding the features and design of a product based on user feedback and testing results.
- Documentation
The process of recording design changes, reasons for those changes, and testing results.
- Usability Test
A method used to evaluate a product by testing it with real users.
- MidFidelity Prototype
A prototype that is more advanced than a low-fidelity prototype but not yet a final version, often allowing for interaction.
Reference links
Supplementary resources to enhance your learning experience.