Loading the lesson
Loading the lesson
Search AllRounder.ai
Search the courses, subjects, tracks, games and features, or jump straight to a page.
Search the courses, subjects, tracks, games and features, or jump straight to a page.
Learn it your way
A short class with Sarah and her students. The other ways are under More.
Sign up free to listen. Transcripts are free to read.
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.
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.
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.
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.
Keeping track of what changes are made during the design process.
Clarifying why a particular change was necessary helps inform future decisions.
Documenting how and when changes were tested ensures that the design is validated against real user feedback.
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.'
WHT for every change, it's not a game! What, How, Test is the right name!
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.
WHT: W for What was changed, H for How it was tested, T for Test results.
WHT: Documenting design changes is easy to remember using this acronym—What, How, Test!
Term
What does documenting changes help track?
Click to flip
Term
Why is rationale important in design documentation?
Click to flip
Choices made regarding the features and design of a product based on user feedback and testing results.
The process of recording design changes, reasons for those changes, and testing results.
A method used to evaluate a product by testing it with real users.
A prototype that is more advanced than a low-fidelity prototype but not yet a final version, often allowing for interaction.
This section emphasizes the importance of documenting design decisions made during the iterative design process to ensure clarity on what changes were made, the implications of those changes, and the testing methods used.
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.
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:
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.