Why would I want to read a case study?
Deliverables show what was produced. Case studies explain how it happened.
They explore the challenges that existed, the constraints that shaped decisions, the alternatives that were considered, and the approaches used to deliver sustainable improvements.
Their primary purpose is to answer a single question:
How was the problem solved?
For readers who want to understand how documentation initiatives, developer experiences, and transformation projects evolve in practice, case studies provide insight into the thinking behind the work.
Follow the links below to read more about each case study
Strategy
When Docs become an Ecosystem
This project explored how a large fragmented collection of PDF documents could be transformed into a governed documentation ecosystem.
Through content auditing, audience analysis, information architecture, governance planning, and content strategy, I developed a roadmap for a scalable documentation platform designed around user needs, discoverability, and long-term sustainability.
Transform
Leveraging a Rebrand for Doc Transformation
A corporate rebrand is often viewed as a visual exercise, but this project demonstrated how it can become a catalyst for wider documentation transformation.
Working within a complex documentation ecosystem of more than 50 projects, I used the rebrand as an opportunity to improve navigation, information architecture, content governance, and visual standards.
Develop
Creating Better API Experiences
This forthcoming case study explores the redesign of a REST API documentation ecosystem. It examines the challenges of organising complex technical information, supporting developer needs, and establishing documentation standards that remain sustainable over time.
Key themes: REST APIs, developer docs, developer experience, information architecture and governance.
