Miguel Divo
18 November 2026
From documentation to design thinking: lessons from Canonical’s Design Academy
Technical Authors at Canonical design experiences: they organize complex information, guide users through unfamiliar systems, and translate technical detail into something people can act on. What changes when they begin thinking like designers?
Eight Technical Authors explored that question through the first Design Academy, a 10-week collaboration between the Design and Documentation teams. Through practical projects, workshops, and mentoring, participants learned to investigate user needs, test assumptions, align stakeholders, and turn research into focused improvements.
Thinking about documentation like a designer
The Design Academy was created to embed design skills within teams beyond the Design function. Technical Authors were a natural first cohort: understanding users, structuring information, and solving communication problems are already fundamental parts of their work.
The program combined design theory with hands-on application. Rather than treating design thinking as an abstract framework, each participant brought a real challenge from their product or documentation area. They worked through user research, problem framing, ideation, and validation, while developing outcomes they could take back to their teams.
The curriculum was developed in collaboration with Documentation leadership and instructors from the Design team, and supported participants through group sessions and individual coaching. Their reflections shared a common theme: the cohort did more than learn the material. Participants quickly applied it to active projects, influenced conversations within their teams, and began sharing the methods with others. As our design instructor Archita Gorle observed, “There’s a real difference between understanding a concept and using it, and this group consistently did both.”
Lesson 1: Learning to stay with the problem
For several participants, the most important change was learning not to move immediately into implementation.
Technical Authors often work close to engineering teams, where practical solutions and delivery pressures naturally dominate discussion. The Academy gave participants methods for slowing down at the right moment: questioning assumptions, gathering evidence, and making sure they understood the user’s problem before deciding what to build.
Andreia Velasco Gomes, Technical Author for SQL, described this as learning to manage the uncertainty of complex problems:
“Design thinking has permanently changed how I think about problem-solving. It taught me not to fear the difficult process of slowly uncovering puzzle pieces, and that it’s normal to not be able to connect them right away.”
Andreia Velasco Gomes
That shift was particularly valuable for Geoffrey Kinyua’s work on the Multipass Command Line Interface (CLI) documentation. He began the Academy with the instinct to replace everything, but through research, he changed his strategy, moving from a broad redesign towards three specific opportunities for improvement. The result was not simply a smaller scope for the documentation. It gave engineering and design stakeholders a clearer basis for discussion, grounded in user feedback and pain points, rather than competing ideas about implementation.
Lesson 2: Making research visible
The Academy introduced participants to visual methods for organizing research and communicating their reasoning. For Technical Authors accustomed to working primarily in text editors, tools such as affinity maps offer a different way to identify patterns, challenge assumptions, and make complex findings easier to discuss. Marek Suchánek, Technical Author for Ubuntu Desktop, found that these methods changed both his individual work and his team conversations:
“Charting your thoughts on an affinity map really does help you examine a problem and share your thinking with other people.”
Marek Suchánek
By using affinity maps, participants became more comfortable questioning the premise of a task. Instead of asking only how documentation should be changed, they could investigate whether the proposed change addressed the right problem at all.
Vladimir Izmalkov, Technical Author for NoSQL, saw a close relationship between design thinking and scientific research, but with a stronger focus on people. His project moved from user pains and hypotheses to interviews, defined scope, and concrete outcomes. Along the way, stakeholder alignment and visualizing evidence helped to make the findings accessible, building support for new ideas as a result.
Lesson 3: How design extends the role of the technical author
Each participant brought the same design process into a different technical context. Artem Konev used the Academy to examine the Workshop project from a new perspective to support his role in documenting it. The process revealed UX gaps that could be reported, discussed, and addressed, while also giving him tools that were useful independently of the wider design thinking framework.
Sharon Koech investigated a mysterious OpenStack problem that went beyond documentation: it turned out to be a fundamental design issue. Through stakeholder engagement and structured discovery, the group identified likely causes and contributed evidence that could influence the roadmap. She has since taken those approaches back to her work with Ceph.
For Sophie Pages, Technical Author for Talent Experience, the program’s strength was its learn-by-doing model. Applying each new method to a live project made an intensive course practical and helped the learning remain connected to real outcomes.
“It was brilliant to have us follow the design training while implementing what we learned on a specific project.”
Sophie Pages
These experiences show how design thinking can extend the role of Technical Authors. Documentation remains a core outcome, but Technical Authors can also help teams frame problems, represent users in planning discussions, and create alignment before implementation begins.
The participants have already started carrying these methods into other areas. Geoffrey Kinyua is applying stakeholder alignment and user-centred problem framing to the Multipass VS Code extension and a new link-checking project. Our design instructors recalled seeing one participant use the program’s methods in an external design and documentation clinic, passing the learning on to others.
This wider application was one of the goals of the Academy. Instructor and UX designer at Canonical, Lukas Serelis, highlighted how participants were not simply trying to complete the course. They wanted to become “a force multiplier” for solving problems within their teams.
For Teodora Mihoc described, completing the programme did not feel like reaching the end of the learning:
“The Design Academy was an arduous climb, but we all reached some top, and the views ahead are enticing.”
Lesson 4: Designing better documentation starts with asking better questions
The first Design Academy demonstrated that design and technical authorship are closely connected disciplines. Both require curiosity about users, comfort with complexity, and the ability to turn evidence into clear, purposeful experiences.
For the participants, design thinking provided more than a set of workshop activities. It changed how they approached ambiguous problems, collaborated with stakeholders, and evaluated possible solutions. It gave them permission to ask harder questions before committing to an answer.
The Academy ended with eight practical projects, but its longer-term value lies in what happens next: Technical Authors bringing user-centred methods into product conversations, sharing them with colleagues, and helping their teams solve the right problems before documenting the results.
Applying design thinking into your own practice
You do not need to be a designer, or run a formal academy, to bring design thinking into your work. Start with a real problem in your domain and make space to understand it before deciding on a solution.
- Begin with user needs: Speak to users, observe where they struggle, and gather evidence before defining the work.
- Question the initial request: A request for a new guide, feature, or workflow may point to a deeper problem. Ask what outcome is needed and for whom.
- Make your thinking visible: Use journey maps, affinity maps, or simple diagrams to organize findings, and help stakeholders examine them together.
- Form and test hypotheses: Treat proposed solutions as ideas to validate, rather than foregone conclusions. Small interviews, prototypes, or usability sessions can reveal whether you are moving in the right direction.
- Invite other disciplines early: Bring design, engineering, product, and documentation perspectives together while the problem is still being framed.
- Start with one project: Apply these methods to a contained piece of work, reflect on what helped, and share the results with your team.
Thinking like a designer does not mean that every design method must be applied at once. Rather, it develops a habit of curiosity: pausing before implementation, making assumptions explicit, and keeping those affected by the work present throughout the process.
This article was produced and published on behalf of the Design Academy team (Lukas Serelis, Archita Gorle, Amy Pattanasethanon, Alorah Harman, Hartmut Obendorf)
Join the Canonical design team
We’re looking for designers who care about craft and how systems work under the hood. At Canonical, design sits at the intersection of UX, engineering, and open source where we shape cohesive, accessible experiences across cloud, desktop, and IoT products.
If you enjoy solving complex problems and turning technical depth into clarity, explore our open roles: canonical.com/careers