My work at CDW
I worked as a Technical Solutions Specialist at CDW UK from 2021 to 2022, focusing on creating technical documentation and sales materials that helped enterprise customers understand complex IT solutions. My role was translating technical specifications into business language that procurement teams and IT directors could actually use to make informed decisions.
Understanding the enterprise sales challenge
Working at CDW taught me that enterprise technology sales is fundamentally different from the developer-focused documentation I had been writing. Enterprise customers aren't implementing technology for its own sake - they're solving specific business problems under tight regulatory and operational constraints.
The documentation challenge was helping customers understand not just what technology could do, but how it would work in their specific environment with their existing systems, compliance requirements, and operational realities.
Writing for multiple decision makers
Unlike the docs engineering I had done at Atlas Copco or would later do at Ably, CDW documentation needed to serve multiple audiences simultaneously. A single cloud migration project might involve IT directors, compliance officers, finance teams, and technical implementers - each with different concerns and information needs.
I developed a modular documentation approach that provided different levels of detail for different roles while maintaining consistency across the overall solution architecture. This experience later influenced how I approached developer journey mapping at Ably.
Cloud platform documentation approach
My biggest focus was on cloud migration services documentation. Enterprise cloud migrations are complex projects involving risk assessment, compliance mapping, and operational continuity planning.
I created documentation frameworks that could be customized for different industries while maintaining technical consistency. Each framework included assessment templates, migration runbooks, risk matrices, and cost optimization guides that sales teams could adapt for specific customer situations.
The writing process required understanding not just the technical implementation, but the business case justification that customers needed to present to their leadership teams. This taught me to think about documentation as enabling decision-making, not just explaining technical processes.
Cybersecurity documentation challenges
Security implementations presented unique documentation challenges because every organization has different risk tolerances and regulatory requirements. I created documentation for CDW's cybersecurity consulting that could be customized for different sectors.
The approach required mapping technical security implementations to specific compliance frameworks like ISO 27001, NIST, and PCI DSS. This was similar to the systematic diagnostic approach I had developed at Atlas Copco, but applied to regulatory compliance rather than manufacturing troubleshooting.
Connecting technical depth with business outcomes
The most valuable documentation I created was material that connected technical capabilities to measurable business outcomes. Enterprise customers needed to justify technology investments with concrete ROI projections and risk reduction metrics.
I developed templates for solution architecture documentation that showed customers exactly what they would receive, with realistic project timelines and honest risk assessments. This transparency helped build the trust necessary for complex enterprise sales cycles.
Supporting the sales process
Unlike pure docs engineering, my CDW work required understanding how documentation fits into the sales process. Technical materials needed to support proposal development, customer education, and post-sale implementation planning.
I created reusable content libraries that sales teams could adapt for different customer situations without starting from scratch each time. This improved proposal quality and consistency while reducing preparation time for complex technical sales.
Industry-specific adaptation
Enterprise customers in different industries have fundamentally different operational requirements. Financial services organizations operate under strict regulatory oversight, healthcare providers must protect patient data, and manufacturing companies need to integrate operational technology with information systems.
I developed sector-specific frameworks that addressed these unique requirements while maintaining technical consistency across CDW's service delivery. This modular approach later influenced how I thought about content restructuring and information architecture at Ably.
Microsoft ecosystem specialization
During my time at CDW, Microsoft dominated the enterprise market with Office 365 and Azure. I specialized in creating documentation for Microsoft ecosystem implementations, including migration strategies, hybrid identity solutions, and integrated security approaches.
This specialization taught me the importance of understanding vendor ecosystems and how different technologies integrate in practice, not just in theory. These lessons proved valuable when I later worked on cross-platform API documentation at Couchbase.
Results and business impact
The documentation frameworks I developed had measurable impact on CDW's sales process. Standardized technical materials improved proposal quality, reduced preparation time, and increased win rates by helping customers understand complex solutions more clearly.
More importantly, the documentation improved implementation success rates by setting clear expectations and providing practical guidance that customers could follow during project execution. This showed me how good docs engineering directly impacts business outcomes in enterprise environments.
Enterprise writing lessons
Working at CDW taught me that docs engineering in enterprise sales is fundamentally about building confidence. When customers are investing millions in technology implementations, they need to believe that the vendor truly understands their operational realities and can deliver successful outcomes.
The documentation skills I developed at CDW - modular content architecture, audience-specific information design, and business outcome orientation - became central to how I approached all subsequent docs engineering projects. These principles proved essential when I later worked on developer experience optimization at Ably.