Building a collaborative platform for creating, reviewing, and publishing API documentation, designed for how teams actually work.

https://youtu.be/9WD4ODp60jE

Background

Helping people write better technical documentation with a collaborative approach.

Based on our interactions with technical writers, developers, and members of our own team, we figured out that documentation isn’t broken because of tools. it’s broken because no one owns it.

We understood the gaps and found a few ways to bridge them.

My Role

Product Designer

Team

1 Designer, 3 Engineers, 1 Manager

Duration

2 Months (for MVP)


Research & Findings

As part of the research exercise, we contacted writers, developers, and managers. Some shared negative feedback about existing tools in the market, while others mentioned why they don’t document.

image.png

Technical writers

Writers bring clarity, but can’t write without collaborating with developers or product managers.

image.png

Developers

Devs hold the accuracy, but don’t see documentation as part of their job. They just move on to the next sprint.

image.png

Dev Tools

Tools only focus on formatting instead of collaboration, and iterative writing approaches.

image.png

Product Managers

Managers know the business logic, but it’s one of many competing priorities, so context trickles in too late.