Socure · Lead Technical Writer
Leading documentation operations through infrastructure and product transformation
Overview
At Socure, Technical Writers were embedded within vertical cross-functional teams, but there was no formal documentation leader overseeing the broader documentation function.
As Lead Technical Writer, I took ownership beyond content development. I managed the documentation infrastructure, maintained platform dependencies, coordinated Docusaurus upgrades, and owned the CI/CD workflows supporting documentation authoring and publishing. This also meant working closely with engineering to ensure broader DevOps changes did not disrupt documentation operations.
As Socure expanded its offerings into FedRAMP-authorized environments, I established and maintained a separate documentation site for government customers. This introduced additional coordination with SMEs to ensure commercial product releases and FedRAMP-authorized capabilities were accurately reflected in their respective documentation experiences.
Later, following Socure's acquisition of Effectiv, the company began transitioning customers to its new RiskOS platform. With only three weeks before the holiday period, I took on the challenge of quickly learning the new platform while engineers were still adapting and integrating it into Socure's ecosystem. I designed the new documentation experience, established its information architecture and customer onboarding flows, and continuously validated documentation against the latest product changes.
These experiences required me to operate across documentation engineering, product knowledge, quality assurance, compliance requirements, and customer experience.
Project at a glance
| Area | Details |
|---|---|
| Role | Lead Technical Writer |
| Documentation platform | Docusaurus |
| Platform evaluation | ReadMe and alternative documentation solutions |
| Infrastructure | GitLab, Docker, Jenkins |
| Scope | Documentation infrastructure, dependencies, upgrades, CI/CD, content strategy, and publishing operations |
| Documentation environments | Commercial and FedRAMP |
| Product transformation | Effectiv acquisition and transition to RiskOS |
| Key responsibilities | Platform ownership, infrastructure maintenance, information architecture, SME coordination, product validation, and customer onboarding |
01. The challenge: Documentation without dedicated ownership
At Socure, Technical Writers were embedded in vertical cross-functional teams, allowing them to work closely with their respective Product and Engineering stakeholders.
However, there was no formal documentation leader responsible for the shared infrastructure, publishing operations, and broader documentation platform strategy.
I stepped into that gap, taking responsibility for keeping the documentation ecosystem operational while supporting the needs of individual product teams.
Fragmented infrastructure ownership
The documentation sites were built using Docusaurus, an open-source documentation framework that required ongoing maintenance and technical ownership.
- Platform dependencies needed regular maintenance and upgrades.
- Docusaurus version upgrades required someone to manage the associated changes.
- CI/CD workflows involved GitLab, Docker, and Jenkins.
- Infrastructure changes made by engineering could unintentionally disrupt documentation authoring and publishing.
Publishing workflow dependencies
Jenkins configuration was a recurring bottleneck, as engineers unfamiliar with the documentation workflow occasionally made changes that broke publishing until someone tracked down the issue. Without dedicated ownership of the infrastructure, even small adjustments could stall documentation updates.
Expanding compliance requirements
Following Socure's FedRAMP authorization, the company needed a separate documentation experience for government customers.
Commercial product releases did not automatically mean the same capabilities were available to FedRAMP customers. Maintaining accurate documentation across both environments required ongoing coordination with SMEs to understand product availability and authorization status.
Major product transformation
Following the acquisition of Effectiv, Socure was moving toward a new product architecture under RiskOS.
The company wanted to begin onboarding customers to the new platform, creating an immediate need for a new documentation experience. However, the product was still being adapted and integrated into Socure's platform, with engineers actively developing and changing functionality while I was learning it.
With only three weeks before the holiday period, I had to quickly develop an understanding of the platform while its implementation was still evolving. What I learned one day could become outdated the next as engineers introduced changes to functionality and workflows.
This meant documentation development was happening alongside active product development. I needed to continuously validate my understanding against the latest implementation, test workflows, identify discrepancies, and follow up with engineers to understand changes.
In many ways, I was acting as an additional QA layer, ensuring the documentation I was building kept pace with the product as it evolved.
02. Infrastructure ownership: Keeping documentation operations running
I took ownership of maintaining and upgrading the documentation infrastructure alongside my regular technical writing responsibilities.
This included managing the Docusaurus implementation and the supporting workflows that allowed writers to author, review, and publish documentation.
What I owned
- Managed Docusaurus dependencies and upgrades to newer versions.
- Maintained the documentation platform and its underlying configuration.
- Managed the CI/CD workflows involving GitLab, Docker, and Jenkins.
- Coordinated with engineering on infrastructure changes that could affect documentation operations.
- Investigated and resolved publishing disruptions caused by configuration changes.
- Ensured documentation authoring and publishing workflows remained operational as the broader DevOps environment evolved.
Protecting the publishing workflow
Documentation publishing relied on shared infrastructure that was not always owned or well understood by engineers modifying it. For example, engineers unfamiliar with Jenkins's role in the publishing pipeline could unintentionally introduce configuration changes that halted documentation releases completely.
I stepped in to map these dependencies, diagnose disruptions, and coordinate fixes to restore publishing. Beyond one-off troubleshooting, this meant actively protecting the release pipeline from unintended infrastructure shifts so documentation operations remained a reliable part of the engineering environment.
03. FedRAMP documentation: Supporting separate customer environments
When Socure achieved FedRAMP authorization, I established a second documentation site dedicated to FedRAMP customers, hosted under a separate domain.
Maintaining both sites introduced an additional layer of product coordination. Commercial product releases did not automatically mean that the same features were available or authorized for FedRAMP customers. I needed to work closely with SMEs to understand the authorization status of new features and ensure documentation accurately reflected the capabilities available in each environment.
What I did
- Established a separate documentation site for FedRAMP customers.
- Maintained documentation across commercial and FedRAMP environments.
- Coordinated with SMEs to understand product feature availability and authorization status.
- Monitored commercial product releases to identify capabilities that might also become available to FedRAMP customers.
- Ensured documentation reflected the appropriate product capabilities for each customer environment.
This required treating documentation as part of the product release and compliance process rather than simply publishing the same content across multiple sites.
The two-site model also reinforced the importance of maintaining clear communication between Technical Writing, Product, and Engineering.
04. Product transformation: Documenting RiskOS while the product was evolving
Following Socure's acquisition of Effectiv, the company's product architecture was undergoing a significant transformation.
Socure wanted to begin onboarding customers to its new RiskOS platform. This created an immediate documentation challenge: the new platform needed a customer-facing documentation experience, but I had very limited time to understand the product.
With only three weeks before the holiday period, I took on the responsibility of learning the new platform and establishing its documentation foundation.
Rapid product discovery
Effectiv's documentation did not come over as part of a formal content migration, so I began by reviewing whatever existing materials were available to build a baseline understanding of the product. From there, I explored RiskOS hands-on to map out its architecture, functionality, and customer workflows.
Because the product was still being adapted to Socure's platform, engineers were actively reshaping features and integration details at the same time I was trying to learn and document them. This created a moving target where product knowledge gained one day could become outdated the next.
Documentation as an extension of QA
Because the platform was constantly shifting, documentation became an iterative validation loop running alongside engineering development rather than a linear writing phase.
What I did:
- Tested evolving features directly in the product to catch discrepancies between early specs, my previous notes, and the latest implementation.
- Followed up on active code changes to clarify edge cases, verify expected behavior, and keep drafts aligned with ongoing integration work.
- Structured the content hierarchy and customer onboarding flows to reflect how RiskOS actually functioned within Socure's ecosystem.
- Revised and re-verified documentation iteratively as features stabilized ahead of launch.
Designing around customer onboarding
Documenting RiskOS meant more than explaining individual features; it required organizing the entire documentation experience around how a new customer actually adopts the platform.
Taking ownership of the information architecture and onboarding flows, I translated complex, newly integrated workflows into a logical learning path. By structuring content around real implementation milestones rather than internal system architecture, I helped customers navigate setup and integration steps clearly from day one.
05. Platform strategy: Evaluating long-term sustainability
While maintaining the existing Docusaurus infrastructure, I also recognized the need to evaluate whether an open-source documentation framework remained the right long-term solution for Socure.
Docusaurus provided flexibility and control, but it also required ongoing ownership of dependencies, upgrades, infrastructure, and publishing workflows.
Given the organization's evolving documentation requirements, I researched alternative documentation platforms that could better support the capabilities the company needed while potentially reducing the maintenance burden.
ReadMe was among the platforms I evaluated.
What I considered
- Documentation authoring and content management capabilities.
- Publishing workflows and infrastructure requirements.
- Platform maintenance and upgrade responsibilities.
- Features needed to support evolving product documentation.
- Long-term sustainability and ownership.
The evaluation was intended to give the organization options beyond continuing to maintain an internally managed open-source implementation.
What happened afterward
After my departure, the RiskOS documentation site was eventually migrated from Docusaurus to ReadMe.
This reinforced an important lesson in documentation platform strategy: choosing a platform isn't just about its capabilities at launch. It also requires considering who will own its infrastructure, maintenance, and evolution over time.
06. The outcome: Documentation supporting business transformation
My work at Socure extended across infrastructure operations, compliance documentation, and a major product transition.
The contributions established a foundation for documentation to evolve alongside the company's engineering and business requirements.
Dedicated ownership of documentation infrastructure
Docusaurus dependencies, upgrades, and publishing workflows had dedicated ownership, helping maintain continuity as engineering teams made changes to the broader DevOps environment.
Separate documentation for FedRAMP customers
Established a dedicated documentation site under a separate domain to support government customers, with ongoing coordination to ensure product capabilities were accurately represented across commercial and FedRAMP environments.
Documentation readiness for RiskOS
Rapidly developed product knowledge following the Effectiv acquisition and established the information architecture and customer onboarding flows for the new RiskOS documentation experience.
Documentation aligned with active product development
Worked alongside engineers as RiskOS was being adapted to Socure's platform, continuously testing functionality, validating product behavior, and updating documentation to reflect ongoing changes.
Long-term platform evaluation
Researched alternative documentation platforms, including ReadMe, to help the organization assess the trade-offs between maintaining open-source infrastructure and adopting a hosted documentation solution.
More than content ownership
The work expanded the scope of Technical Writing beyond content creation into infrastructure management, operational continuity, platform strategy, quality assurance, and customer experience.
What this project demonstrates
This project reflects how I approach documentation as a product and take ownership beyond the boundaries of traditional technical writing.
- Documentation leadership: Taking responsibility for shared documentation operations and infrastructure in an organization without a formal documentation leader.
- Infrastructure ownership: Managing Docusaurus dependencies, upgrades, and CI/CD workflows involving GitLab, Docker, and Jenkins.
- Operational reliability: Understanding infrastructure dependencies and protecting documentation authoring and publishing from unintended changes.
- Compliance awareness: Establishing and maintaining separate documentation experiences for commercial and FedRAMP customers.
- Cross-functional collaboration: Working with Engineering and SMEs to maintain product accuracy and coordinate infrastructure changes.
- Product adaptability: Quickly developing expertise in a new platform following a major acquisition.
- Quality assurance: Validating product behavior and keeping documentation synchronized with an actively evolving implementation.
- Customer experience: Designing information architecture and onboarding flows around the needs of RiskOS customers.
- Platform strategy: Evaluating documentation solutions based on both product capabilities and long-term operational sustainability.