Documentation As A Maturity Lever
Organizations at Chapman and Plewes’ stage 3 or early stage 4 of UX maturity have enough UX activity to benefit from capturing what has been done. At this point, the priority shifts from simply doing UX work to preserving the knowledge gained from it. Without documentation, each new project risks repeating the same foundational research, testing the same assumptions, and losing hard-won insights when team members change roles or leave the organization.
Mature UX organizations do not reinvent the wheel each time they start a project. They build efficiency from documented lessons learned and from consistency in how UX is applied across products. The documentation tactics below can be combined to suit your organization’s culture and existing knowledge-sharing infrastructure.
Levels Of Sharing
Manual sharing. One-on-one conversations, group discussions, and emailing reports as attachments or links are the simplest form of knowledge transfer. This approach is the most time-consuming and least scalable, as it relies on word of mouth and on individuals saving and passing along files. Still, these conversations have real value: they let others see your passion for UX and for creating great experiences.
Informal presentations. Lunch-and-learns, one-off presentations, and cross-project meetings focused on UX work help connect people who might not otherwise interact during their day-to-day tasks. Like manual sharing, this takes time and depends on getting the right people in the room. Recording these sessions and sharing the video links extends their reach to those who could not attend.
Catalogued online repositories. File-sharing platforms such as SharePoint, OneDrive, Box, Dropbox, and Google Drive can serve as repositories for UX research and deliverables. UX-specific platforms like Handrail and Productboard also offer storage and collaboration features. Whichever platform you choose, the content is only useful if people know how to access it and how to search it. Repositories require someone to establish and maintain standards for tags and naming conventions. For guidance on what to document and how to structure a repository, resources from UXPin and Nielsen Norman Group provide useful starting points.
Systems and guides. Organizations at the highest levels of UX maturity typically have design standards and design systems in place. As Audrey Hacq notes in her guide, citing Jina Anne, design systems encompass “tools for designers & developers, patterns, components, guidelines” as well as “brand values, shared ways of working, mindset, shared beliefs.”
The main drawback is the effort required to create and maintain such a system. In a low-maturity organization you are unlikely to have the time or mandate to build one. But you can aim for this level of documentation as a long-term goal: as UX becomes more established and resources grow, the value of a design system will eventually outweigh the inertia that makes such a large undertaking difficult to start.
Building The Foundation
You do not need to choose a single approach. Pairing informal live presentations with something more enduring, such as a searchable repository, gives you both immediate reach and lasting value. Whatever method you start with, the goal is to avoid starting from scratch on each new project.
In the earliest stages of UX maturity, you may find yourself responsible for starting the repository yourself. You may not control every area where UX work happens, but you can try to coordinate with others to standardize what gets documented and how. Using a resource like the UXPin list, you can begin documenting what you can now and expand your coverage as resources grow or as other motivated UX practitioners join the organization.
Case Study: Building Capacity In A Low-Maturity Organization
Over eight months, a consultancy team worked with a large pharmaceutical company to build UX capacity and document its UX accomplishments across several product teams. The work included stakeholder and user interviews, product redesigns, and usability testing of current and future designs. The team documented its processes through interview protocols, sketch files, journey maps, research reports, usability testing findings, and decision trees to guide future design work.
The team used all four sharing methods described above:
- Manual sharing: The team worked directly with team members to explain their research protocols and outputs, sharing files in editable formats so they could serve as templates for future projects. Contacts were used to identify people who might benefit from receiving the documents.
- Informal meetings and presentations: Because the company was large and globally distributed, an internal champion was essential for identifying key individuals and teams to present to. Onsite visits enabled impromptu one-on-one conversations. The team tailored each presentation to its audience: tactical usability findings for product teams, and higher-level overviews and near-final designs for executive stakeholders.
- Online repository: Using the company’s standard document storage platforms, the team created a UX-specific repository with user-friendly tags and terminology familiar to staff across the organization. The link was distributed through emails, online forums, and within documents.
- Decision guide: Rather than a full design system, the team created a decision tree for a specific product set. The guide helped determine when a design element needed updating — and if so, whether existing research could inform the change or whether new research and testing were needed. The document was shared with product team members and managers who could advocate for similar guides elsewhere.
The immediate goal was to leave behind a foundation of well-documented, accessible UX outputs, along with a framework for how to continue conducting and documenting UX work. Similar techniques can be adapted to any organization’s needs and culture.
Mentorship As A Maturity Lever
A well-designed mentorship program can do more than grow individual skills. It compounds the investment an organization makes in its UX staff: experienced practitioners deepen their own practice by articulating it, while less experienced staff gain capabilities that expand what UX can take on. Other fields, such as health care and education, already rely on mentorship as a core part of professional development, and UX can benefit the same way.
Because mentorship is a personal relationship, the connection to organizational UX maturity needs to be explicit. Design the program with that outcome in mind, and consider including people from outside traditional UX roles to broaden influence.
Several design questions matter:
- What is the goal?
Define the intended outcomes for the program at both the organizational and participant level — for mentees and for mentors. - Formal or informal?
Decide whether the program will follow structured guidelines or allow outcomes and activities to emerge more loosely. The line between the two is blurry, and borrowing from both sides is encouraged: an informal program can still use a good assessment tool, and a formal one should make room for casual relationship-building conversations.
| Formal | Informal | |
|---|---|---|
| Participant Pool | Predefined roles and positions are able to or required to participate. | Individuals expressing interest are able to participate. |
| Timeline | Set timeline with milestones identified and a predefined end date. | Less structured, milestones are flexible, mentor/mentee determine end date. |
| Goals | Program managers set generic goals, mentor/mentee refine goals using existing structure. Most goals have a relationship to the growth/benefit of the organization and the individuals. | Mentor/Mentee customize goals to the needs of the individuals involved. Goals might not tie directly to the organization's needs. Mentor/Mentee revisit goals and update them to reflect the reality of how the mentee has progressed and other factors impacting the mentee. |
| Assignment | Mentors and mentees are matched through a formalized process. For example, completing a questionnaire that sees who is most aligned, matching based on role/job title, or team/product based. | Mentors and mentees have the opportunity to determine who they match with. For example, prior interactions suggest a potential for positive relationship, offering mentees a brief intro call with a number of potential mentors before deciding who they might want to match with. |
| Activities | Predefined relationship building and education opportunities, for example attending networking events, conferences, review sessions, and trainings. | Participants choose which activities and the frequency. For example, a weekly coffee chat with a monthly review meeting and informal conversations as needed. |
| Outcomes/Assessment | Outcomes and assessment are based on a template and reflect the desired outcomes of the organization. Assessment is formalized and used to determine effectiveness of the program as part of a final evaluation. | Outcomes and assessment are reflective of mentee’s needs and goals that have evolved over the course of the program. Assessment might be informal discussion and reflection. |
Formal and informal programs sit on a spectrum, and the best approach often mixes elements of each.
Participation deserves deliberate thought. Mentorship benefits both parties, so use it to challenge seasoned staff as well as to onboard newer employees. Reverse mentoring — pairing senior staff as mentees with junior staff as mentors — is worth exploring. It can give leadership direct exposure to UX value from colleagues they might not otherwise learn from, turning them into advocates for UX growth.
Regardless of program structure, mentors need training and support. Strong job performance does not automatically translate into strong mentoring. Research on effective mentorship programs also suggests letting mentors and mentees have input into how they are matched.
Case Study: An Informal Mentorship That Grew Organizational UX
The author mentored someone at a media company who was transitioning into a UX research and strategy role. The relationship began as a formal client-consultant engagement, but became a voluntary, informal mentorship as both parties recognized shared goals and the potential for mutual growth.
The key factors of the relationship map to the formal-versus-informal comparison:
- Participant Pool.
Only the two of them were involved. The relationship developed organically from professional interactions rather than from a formal program. - Timeline.
The mentorship lasted about 18 months, well beyond the author’s 12-month consulting engagement with the organization. Its endurance was a sign of genuine value, not obligation. - Goals.
Goals evolved. They began broad — learning common UX processes and research methods — and became increasingly specific as the relationship progressed, such as presenting findings to a particular product team or developing a usability testing protocol. The author worked on the same products as the mentee, which made it possible to turn daily challenges into actionable goals and allowed for frequent micro-goal updates. - Assignment.
They self-assigned. The decision to mentor came after weeks of working together had demonstrated the potential value. - Activities.
Frequent, nearly daily collaboration made the relationship intensive. Activities included informal calls, formal assignments, attending meetings and conferences together, strategy sessions, shared document creation, co-analysis of data, co-working, and conversation over coffee or meals. - Outcomes/Assessment.
Assessment was informal and recurring — ongoing conversations about whether each party was getting what they needed, and open discussion about what to focus on next.
The results were substantial across three levels. The author grew as a practitioner, pushed to explain the reasoning behind methods, recommendations, and stakeholder presentations. The mentee developed enough skill to lead UX work on multiple projects, meeting both the original goals and the micro-goals along the way. The organization gained a more mature UX practice: the mentee justified a budget for an additional hire, expanded UX processes to products that lacked them, and built leadership support through presentations that energized staff around UX growth.
Practical Lessons
Both tactics in this article — knowledge sharing and mentorship — have a low barrier to entry. They cost time and require some tooling for sharing information, but no significant budget. Knowledge sharing can start by documenting what was learned on any UX engagement and making those documents easy to find in the organization’s existing file storage, or by maintaining a distribution list and sending relevant artifacts by email. Mentorship does not require a formal program with elaborate rules. A productive, informal relationship formed here between two people who were already collaborating daily, built on a mutual desire to learn and common goals. An organization that needs more structure can start by considering what a program would look like among existing teammates.
These tactics can be used on their own or combined with the approaches from the earlier article in this series. The final article covers educating both UX and non-UX staff on tools, methods, and principles.
