Documenting design is challenging, as it occurs at various product stages, from strategic conceptualisation to last-minute changes due to engineering limitations. Like Documenting MeetingsDocumenting Meetings
Meeting notes should focus on clear information. Keep them simple so you can remember details later. Every meeting involves people, and conversations usually fall into a few categories. I use these..., it's helpful to track design evolution from a decision perspective.
I previously used a markdown-based change-log Changelog as a consistent communication toolChangelog as a consistent communication tool
Changelogs are a great way of effective communication. It provides a clear idea on what is done, and why it's done. Also, it communicates to the user about the value the new feature adds / problem ... for this. Now, I use a cloud-based spreadsheet for easier collaboration. It's a simple, single sheet focusing on: Component, Decision, Rationale with Date and Link to screenshot or Figma. This format is easier to compile and search. Filtering by component and sorting by date provides clarity on the design's evolution.
- Ship-Show-AskShip-Show-Ask
Ship/Show/Ask is a branching strategy that combines the features of Pull Requests with the option to continue shipping changes. There are three categories of changes in this method. They are Ship ... - Focus on Outcome, not OutputFocus on Outcome, not Output
**Output** is measured based on scope, cost, and time. Where as **Outcome** is measured based on behaviour, satisfaction, and Impact. (Impacts like ROI, Market share, etc., might be lagging indicat... - Save ScreenshotsSave Screenshots
An effective way to document design work, whether for a Design Decision Log or Hype Doc, is to store screenshots. I initially undervalued this system, but it now provides Clarity on small w...
