Snapdocs · Senior Technical Writer
Building product knowledge and improving the user experience
Overview
When I joined Snapdocs, the company was transitioning from a mobile notary platform to an end-to-end real estate closing platform just as demand for digital closing solutions surged. I was hired to build the company's first comprehensive product knowledge base — documenting the real estate closing lifecycle, the roles of each party, and how Snapdocs streamlined the process.
As I immersed myself in the product and user workflows, my scope expanded beyond documentation into UX writing, release management, and cross-functional enablement. The goal was to make both an unfamiliar industry and an evolving platform easier for users to understand, navigate, and adopt.
01. The challenge: Scaling a complex product for an unfamiliar industry
Real estate closings are high-stakes transactions involving four or more parties, state-specific compliance requirements, and in-person, online, or hybrid closing methods. Coordinating and reviewing the legal documents required to transfer property ownership leaves zero room for error, as minor mistakes can result in significant financial losses.
As Snapdocs scaled to support the entire closing lifecycle, the company faced three core friction points:
- Industry & workflow learning curves: Rapid hiring meant many new employees had little experience with real estate closings, while traditional lenders and settlement companies needed guidance to adapt their established operations to digital workflows.
- Product usability: As the platform expanded to support more complex transactions, users needed clearer in-product guidance to navigate each stage of a closing and understand required actions.
- Rapid product changes: Frequent releases meant internal teams and customers needed reliable documentation, hands-on testing, and clear communication to keep pace with platform updates.
It needed a shared foundation of product knowledge and a better way to help people understand and navigate the entire closing process.
02. The strategy: Connecting product knowledge, user experience, and release readiness
I approached the work from both sides of the product experience: helping people understand the platform through structured knowledge and making the platform easier to use through product improvements.
Build the first end-to-end product knowledge base
I built Snapdocs' first comprehensive knowledge base in Confluence, organizing content around the end-to-end transaction lifecycle, party responsibilities, and state-specific compliance rather than isolated product features. By connecting industry fundamentals with practical product workflows, the resource served as a single source of truth for employee onboarding, customer education, and Snapdocs' expansion into new states.
Improve the user experience through contextual guidance
While mapping customer workflows, I identified recurring usability gaps and points of friction. I partnered with Product Design to bring guidance directly into the product — helping users see where they were in the closing process, what needed to happen next, and how to complete each task without leaving their workflow.
Connect release documentation with QA and customer enablement
To keep internal teams and customers aligned during rapid release cycles, I built a release workflow that tied documentation directly to product readiness:
- Release notes & customer comms: Published detailed release notes explaining new features and workflow impacts so customers could prepare for changes and train their internal teams.
- Support & QA readiness: Developed hands-on test cases for Support and partnered with QA on testing across closing scenarios to validate functionality before launch.
Redesign the email notification experience
Users were experiencing notification overload, receiving frequent emails without a clear sense of transaction status or required next steps. I overhauled the notification system to eliminate redundant messages and surface actionable status updates — helping multiple parties coordinate smoothly across a single closing.
03. The outcome: Establishing a foundation for product adoption and growth
My work established the knowledge architecture and communication workflows Snapdocs needed to scale into an end-to-end closing platform during a period of rapid growth:
- Product knowledge architecture: Launched the company's first comprehensive knowledge base, accelerating new-hire onboarding, customer adoption, and multi-state expansion.
- UX writing & product thinking: Partnered with Product Design to turn documentation insights into contextual in-product guidance that reduced workflow friction.
- Release management & enablement: Connected release notes with QA regression testing and Support training, ensuring internal teams and customers were prepared for frequent updates.
- Clearer user communication: Simplified the email notification experience to reduce message volume and clarify transaction status and required actions across multi-party workflows.
What this project demonstrates
- Product knowledge architecture: Turning a complex industry and product into an organized, scalable knowledge system.
- UX writing and product thinking: Using documentation insights to identify usability gaps and influence product design.
- Cross-functional collaboration: Working across Product Design, QA, Support, and customer-facing teams to improve the product experience.
- Release management and enablement: Connecting product documentation, testing, internal readiness, and customer communication.
- End-to-end ownership: Going beyond documentation delivery to improve how people understand, navigate, and adopt a complex product.