Defining the Requirements for a Pattern Library Tool
Running workshops to reveal a journey map to inform the requirements for designing a new tool
The organization needs a central repository for design patterns that are repeatedly required across projects. Currently, these components are created from scratch each time by the UX team, the creative team, and the tech team.
Skills: User Research, User Flows, Requirements Gathering, Workshop Facilitation, Journey Mapping
Output: Interview Guide, List of prioritized requirements
Team: Project manager, developer, key executive stakeholders
Timeline: 2 weeks
I was brought onto the project at the discovery phase to conduct research to inform the specific requirements for the tool to work at Klick - currently nothing like it exists. Thinking back on my challenging experiences of implementing new tools and processes, I wanted to look at every step of these teams’ existing workflows to ensure we’re able to fit the tool into and/or consider how we may address differences.
I created a guide (see guide) for each section of the workshop that laddered up to our end goal of identifying specific requirements. Another purpose of workshop was to get buy-in through co-creation from the teams that would ultimately use the tool. I conducted a workshop with representatives from each of the key user groups: UX designer, creative design lead, and developer.
We mapped out the specific steps taken on a typical website development project and identified key areas for process improvement, creating a journey map. The guide helped us keep on track and remained relatively tactical as workshops often derail with the users’ many other process improvement suggestions irrelevant to the pattern library tool. Even as an extrovert, I’ve found myself censored at meetings where different energies collide. To encourage authentic participation, I used the “silent gather” method often, allowing all personality types to think. We concluded the workshop with a sketching exercise. This helps participants understand parts of the UX process and encourages them to think about the problem, too, getting further buy-in.
The Output & Impact
Based on the very detailed journey map developed during the workshop, I created a list of requirements (see list of requirements) the tool needed to maximize its utility. With the larger team, we synthesized the various workshops we ran to consolidate and prioritize requirements in terms of “must-have” and “nice-to-have” for the success of the first iteration of the platform. By involving key stakeholders in the workshop process, we had secured preliminary buy-in for the roll-out.