We stand with Ukraine and our team members from Ukraine.

A Community Of Over 740,000

Home ›› Requirements and Specifications ›› Capturing What You’re Not Implementing

Capturing What You’re Not Implementing

by Frank Garofalo
3 min read
Share this post on


Archiving the ideas & artifacts generated during a project so they can be used in future work.

The UX process is usually a creative, exploratory process as you and your fellow project team members go through several activities to further understand the problem at hand and work towards potential solutions. When iterating through the process, a variety of artifacts are typically created. As ideas and concepts are eliminated from a project, don’t discard those ideas or the related artifacts; archive them instead. By archiving the various artifacts of each project, the ideas and concepts generated throughout the life of the project are not discarded and lost. The ideas can be retained and potentially reevaluated for use in future projects or as a starting point for further ideation in future projects.

Early in a project, you and your team may start to exchange concepts through dry-erase board sketches and paper sketches. Capture those ideas and retain them as digital artifacts by taking digital pictures of the board sketches and making scans of the paper sketches. This also applies to any other artifact generated throughout the entire process that is not originally in a digital format.

Most organizations have a method for documenting the UX specifications for a project. These documentation methods usually focus on what is to be included in the project. As you and your team continue to iterate on the specifications through the life of the project, some ideas will be removed. For example, an entire use-case description might be determined to not be significant enough to be accounted for in the project, so the concepts related to that use-case are “scoped out” of the project. However, don’t discard the related artifacts that have been already generated. Those ideas, though not implemented in the current project, could be a viable solution for another future project.

Although, what is included can be equally as important as what has been considered and determine to not be included in the project. This documentation can be useful, perhaps as an appendix to the UX specifications, to highlight decisions made during the UX process with a brief description as to why it was not included in the project. If someone later asks why a design was made in a particular manner, you will have documentation to reference regarding the other concepts considered and the reasoning behind the decision made.

An excellent tool for archiving these artifacts is a wiki. Most wikis maintain a change log for content, and also have tagging and searching capabilities. Each artifact can be associated with the specific project within the wiki as well as tagged with common terminology across all projects. Digital scans of sketches and other documents can be tagged with, for example, the project name as well as a “scoped-out” tag (certainly other tags could be created as well). These tags can then be used in searches within the wiki. This archiving process effectively generates a Knowledge Management Repository of both concepts used in projects and concepts eliminated from projects.

From the lens of Knowledge Management, this method of capturing what has and hasn’t been implemented offers an organization the ability to collect the ideas, concepts, and knowledge of their employees into an organized format.

post authorFrank Garofalo

Frank Garofalo, Frank Garofalo is a user experience architect living in Kansas City. Currently, he has two roles, one running his own company Cyber View, an online media and interactive solutions agency, and second as a User Experience Developer for Garmin International. He started designing and building web sites in 1999. Frank has a Master of Science in Computer Graphics Technology with a specialization in qualitative research for interactive multimedia from Purdue University. His passion lies in producing quality experiences for users by combining creative designs and functional development to achieve a balance of information architecture. You can follow him on Twitter @fgarofalo.


Related Articles

A Masterclass in What to Do (and not to do).

Article by Nate Schloesser
How to NOT Be a Bad Design Manager
  • The article explores the nuances of effective design management by drawing on the experiences and insights of the author.
  • The author provides practical tips and lessons learned from past mistakes to guide design managers in fostering a culture of growth, innovation, and support within their teams.
Share:How to NOT Be a Bad Design Manager
11 min read
Article by Ignacio Parietti
Why Championing Product Design Consultants When I’m the One in Charge of Design?
  • The article discusses the strategic advantages of championing product design consultants in the ever-evolving field of user experience design highlighting the benefits of external expertise.
Share:Why Championing Product Design Consultants When I’m the One in Charge of Design?
4 min read

Cautionary Tales of Dominance to Downfall.

Article by Nate Schloesser
The 7 Deadly Snares of Strategy
  • The article delves into seven critical strategic snares through real-world case studies, offering valuable lessons for businesses in navigating the complex landscape of modern business strategy.
Share:The 7 Deadly Snares of Strategy
9 min read

UX Magazine produces the most popular podcast about conversational AI

Listen to Invisible Machines

This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and