May 23, 2023
Documentation. It's a topic that elicits varied responses—some swear by it, while others might dismiss its importance. Working on a remote team, I've come to appreciate its significance in facilitating communication and product management.
When I refer to documentation, I'm not simply talking about developer handoff materials. I'm referring to functional documentation that outlines product features and user interactions in detail, providing a roadmap for project execution.
At Swell, while working on Purchase Links—a feature for shareable, pre-built cart configuration—I made it a priority to document every aspect. From creating and configuring purchase links to managing and sharing them, I detailed each element our merchants could interact with.
Initially intended for our development team's reference, these documents unexpectedly found utility beyond their original scope. Our sales and support teams began leveraging them in customer interactions to effectively communicate upcoming features and gather feedback. Much of our help center content actually originated from these documents.
What began as an internal resource became a cornerstone in our cross-functional collaboration efforts, minimizing the need for extensive meetings and ensuring alignment across departments. Encouraged by this, I've integrated this type of documentation into our design process, recognizing its impact in remote work environments.
In a setting where effective communication is paramount, functional documentation has become a vital tool for bridging gaps and creating creating alignment among distributed team members..
