Manager, Technical Documentation, Research & Development

Role Purpose & Context

Role Summary

As our Manager, Technical Documentation, R&D, you'll be setting the vision for how we handle all our technical content, from early-stage research protocols to regulatory submission dossiers. You'll lead a team of talented writers, making sure they're not just producing documents, but actually solving critical information problems for our scientists and engineers. This role sits right at the heart of our R&D efforts, making sure that every breakthrough is properly recorded, understood, and compliant. When this role is done well, our R&D teams move faster, our regulatory submissions are smoother, and new hires get up to speed in weeks, not months. When it's not, we risk costly delays, compliance issues, and frustrated scientists. The challenge is balancing the cutting-edge chaos of R&D with the rigid demands of documentation and regulation. The reward? Seeing your team's work directly accelerate scientific discovery and bring new products to market, safely and efficiently.

Reporting Structure

• Reports to: Director, R&D Content Strategy & Operations
• Direct reports: Typically 3-8 Technical Documentation Specialists (L2-L4)
• Matrix relationships: Principal Information Architect, R&D, Head of Technical Content, R&D, Lead Technical Publications Manager, Life Sciences,

Key Stakeholders

Internal:

• R&D Project Leads (Chemistry, Biology, Engineering)
• Regulatory Affairs Team
• Quality Assurance & Compliance Department
• R&D IT and Systems Teams
• Legal & Intellectual Property Department
• Training & Onboarding Teams

External:

• Regulatory Bodies (e.g., MHRA, EMA, FDA)
• External Research Partners & CROs (Contract Research Organisations)
• Industry Standard Bodies
• Technology Vendors (e.g., CCMS, EDMS providers)

Organisational Impact

Scope: This role directly shapes our organisation's ability to capture, disseminate, and protect its intellectual property and scientific knowledge. You'll be the architect of our R&D documentation strategy, which means you're directly influencing our compliance posture, research velocity, and ultimately, our success in bringing innovative products to market. Get it right, and we're a well-oiled machine; get it wrong, and we're facing delays, fines, and lost opportunities.

Performance Metrics

Quantitative Metrics

1. Metric: Regulatory Submission Efficiency
2. Desc: Eliminate documentation-related queries or delays in regulatory filings.
3. Target: Zero documentation-related queries in 90% of regulatory filings
4. Freq: Per submission cycle (e.g., quarterly, annually)
5. Example: For the Q2 drug trial submission, there were no questions from the MHRA related to the clarity or completeness of our technical documentation, compared to 3-4 queries in previous cycles.
6. Metric: SME Time Optimisation
7. Desc: Decrease the average time Subject Matter Experts spend reviewing documents.
8. Target: 30% reduction in average SME review time per document
9. Freq: Monthly/Quarterly, tracked via review system data
10. Example: Our average SME review time for a complex protocol dropped from 5 hours to 3.5 hours after implementing new review workflows and improving document clarity.
11. Metric: Content Reuse Rate
12. Desc: Increase the percentage of content reused across different document types or product variants.
13. Target: Achieve >60% content reuse across major R&D programmes
14. Freq: Quarterly, measured by CCMS analytics
15. Example: When creating documentation for our new gene therapy platform, 65% of the content for the related SOPs and training materials was pulled from existing, approved source topics.
16. Metric: Onboarding Acceleration for R&D Personnel
17. Desc: Reduce the time it takes for new R&D staff (e.g., lab technicians, junior scientists) to become productive, specifically due to improved documentation.
18. Target: 25% reduction in time-to-productivity for new R&D hires, attributed to documentation
19. Freq: Quarterly, via HR onboarding surveys and manager feedback
20. Example: New lab technicians now report feeling confident in performing core procedures within 3 weeks, down from 4 weeks, largely thanks to clearer, more accessible SOPs developed by your team.
21. Metric: Documentation Toolchain ROI
22. Desc: Demonstrate the return on investment for new documentation tools or systems.
23. Target: 2x ROI on investment in new CCMS/Docs-as-Code pipeline within 36 months
24. Freq: Annually, through cost-benefit analysis
25. Example: After 24 months, our new authoring platform has shown a 1.5x ROI, driven by reduced authoring hours and fewer regulatory resubmissions, putting us on track for the 2x target.

Qualitative Metrics

1. Metric: Strategic Partnership with R&D Leadership
2. Desc: Your team is seen as a crucial strategic partner, not just a service provider, by R&D leads.
3. Evidence: You're regularly invited to early-stage project planning meetings, R&D leadership actively seeks your input on information architecture for new programmes, and your team's recommendations on documentation strategy are frequently adopted. They'll come to you asking 'how should we document this?' before they even start.
4. Metric: Team Development & Morale
5. Desc: Your direct reports are growing, feel supported, and are engaged in their work.
6. Evidence: High retention rates within your team, positive feedback in annual engagement surveys, visible skill progression in individual contributors, and successful internal promotions. Your team members are actively mentoring others and taking on more complex challenges.
7. Metric: Documentation Quality & Usability
8. Desc: R&D users consistently find the documentation accurate, easy to understand, and readily accessible.
9. Evidence: Anecdotal feedback from scientists and engineers praising document clarity, low rates of internal support tickets related to documentation confusion, and positive comments in user satisfaction surveys for internal knowledge bases. People actually *use* the documentation, rather than asking a colleague.
10. Metric: Cross-Functional Collaboration
11. Desc: Your team effectively collaborates with other departments (e.g., Regulatory, Quality, IT) to streamline documentation workflows.
12. Evidence: Successful joint projects with other teams, shared process improvements that benefit multiple departments, and positive feedback from cross-functional peers regarding your team's responsiveness and ability to work together to solve problems. You're seen as someone who gets things done, not just writes about them.

Primary Traits

• Trait: Strategic Information Architect
• Manifestation: You don't just see a document; you see its place in a larger ecosystem. You're the one who asks 'how does this connect to our regulatory submission?' or 'how can we structure this so it's reusable for the next product variant?' You're designing the blueprint for how information flows and is consumed, not just filling in the blanks. You'll spot the gaps in our current knowledge management approach and propose a coherent solution.
• Benefit: In R&D, information isn't just data; it's our intellectual property and our pathway to market. Without a clear, well-designed information architecture, we end up with silos, inconsistencies, and compliance risks that can cost us millions and delay critical projects. Your ability to think systemically ensures our documentation is a strategic asset, not just a necessary evil.
• Trait: Empathetic Leader & Coach
• Manifestation: You're genuinely invested in your team's growth, spending time coaching them through tricky SME interviews or complex authoring challenges. You know when to step in and when to let them figure it out, offering guidance rather than dictates. You'll advocate for your team, shielding them from unreasonable demands, and celebrating their wins. You're the sort of manager people want to work for, because they know you've got their back.
• Benefit: Technical documentation in R&D is tough work, often under pressure. A strong, supportive leader is crucial for retaining top talent and building a high-performing team. Your ability to inspire, develop, and protect your team ensures we have the expertise and resilience needed to tackle our ambitious research goals. Without this, we'd see burnout and high turnover, which we simply can't afford.
• Trait: Pragmatic Problem Solver
• Manifestation: You're brilliant at finding practical solutions to messy, real-world problems. When a scientist says 'I need this document in three different formats by yesterday,' you don't just say 'no'; you figure out the fastest, most effective way to get them what they actually need, even if it means bending the rules a little (within compliance, of course). You're not afraid to challenge the status quo if there's a better, more efficient way to get things done. You'll cut through the noise to get to the root of a documentation bottleneck.
• Benefit: R&D is full of unexpected twists and turns. We need someone who can navigate ambiguity and deliver tangible results, even when the path isn't clear. Being pragmatic means you can balance perfection with progress, ensuring we meet our deadlines without compromising quality or compliance. If you're too rigid, we'll get stuck; if you're too loose, we'll have problems. You find that sweet spot.

Supporting Traits

• Trait: Resilient
• Desc: You can handle the inevitable setbacks, shifting priorities, and occasional frustrations that come with managing a team and dealing with complex R&D projects, bouncing back quickly.
• Trait: Influential Communicator
• Desc: You're great at getting buy-in from senior leaders and cross-functional teams, explaining complex documentation strategies in a way that resonates with their priorities.
• Trait: Technologically Curious
• Desc: You have a genuine interest in emerging documentation tools, AI applications, and R&D technologies, always looking for ways to improve our processes.
• Trait: Organisational Awareness
• Desc: You understand the political landscape and power dynamics within a large R&D organisation, helping you navigate complex stakeholder relationships effectively.

Primary Motivators

1. Motivator: Building & Shaping
2. Daily: You'll spend your days designing new content models, setting up new team workflows, and recruiting and developing your team. You're not just maintaining; you're actively constructing the future of R&D documentation here.
3. Motivator: Impact & Influence
4. Daily: Your decisions will directly affect how our R&D teams operate, how quickly new products get to market, and our overall compliance posture. You'll be influencing senior leaders and shaping the strategic direction of information management.
5. Motivator: Solving Complex Problems
6. Daily: You'll be tackling high-level challenges like integrating documentation across disparate R&D systems, standardising terminology across different scientific disciplines, and ensuring global regulatory compliance. These aren't simple fixes.

Potential Demotivators

Honestly, this role isn't for everyone. You'll be managing people, which means dealing with personality clashes, performance issues, and career aspirations that might not always align with the team's needs. You'll also be responsible for the overall output of your team, meaning their mistakes are ultimately yours. You'll spend a fair bit of time in meetings, trying to get different R&D leads to agree on a common approach, which can feel like herding cats. You won't be doing much hands-on writing yourself, so if you love being deep in the content, you might find that frustrating. And yes, you'll still have to fight the perception that documentation is an afterthought, even at this level.

Common Frustrations

1. Being the 'chief cat herder' for cross-functional alignment on documentation standards.
2. Dealing with the political fallout when a major documentation initiative hits a roadblock.
3. Having to justify the value of documentation tools and processes to budget-conscious R&D leaders.
4. The constant tension between scientific innovation (move fast, break things) and regulatory compliance (slow, meticulous, audit-ready).
5. Spending more time on team management and strategic planning than on actual content creation.

What Role Doesn't Offer

1. A quiet, solitary writing role – you'll be leading and collaborating constantly.
2. A chance to avoid difficult conversations about performance or process adherence.
3. A role where all your projects go smoothly and are adopted without resistance.
4. A 'set it and forget it' environment; the R&D landscape changes constantly, and so will your strategy.

ADHD Positives

1. The strategic, big-picture thinking required for information architecture can be a strength, as it taps into a natural ability to connect disparate ideas.
2. Leading a team means you can delegate routine tasks, freeing you up for more dynamic problem-solving and innovation.
3. The constant need to adapt and respond to new R&D projects can provide stimulating variety, preventing boredom.

ADHD Challenges and Accommodations

1. Managing multiple direct reports and complex projects requires strong organisational skills; we can provide tools and coaching for task management and prioritisation.
2. Long, strategic meetings might be challenging for attention; feel free to stand, take notes digitally, or request short breaks.
3. We can help structure your day to include dedicated 'deep work' blocks alongside your management responsibilities, minimising interruptions.

Dyslexia Positives

1. Excellent verbal communication skills and a strong ability to think visually (e.g., for information architecture diagrams) are highly valued.
2. A strategic mindset often excels at understanding complex systems and identifying patterns, which is critical for designing documentation structures.
3. Leading a team means you can rely on your reports for detailed proofreading and editing, playing to your strengths in strategy and oversight.

Dyslexia Challenges and Accommodations

1. Proofreading and detailed text-based reviews might be challenging; we can provide advanced grammar and spell-checking tools, and assign a dedicated editor or peer reviewer for final checks.
2. We can offer assistive technologies like text-to-speech software and provide documents in dyslexia-friendly formats.
3. Focus on visual communication (diagrams, flowcharts) and clear, concise language will be encouraged across the team.

Autism Positives

1. A deep, analytical approach to understanding complex technical systems and designing logical information structures is a huge asset here.
2. A preference for clear, direct communication and adherence to established processes (like GDP) can be highly beneficial in a regulated R&D environment.
3. The ability to spot inconsistencies and advocate for precise terminology is crucial for maintaining documentation quality and compliance.

Autism Challenges and Accommodations

1. Navigating complex social dynamics in cross-functional meetings or managing team conflicts might require extra support; we can offer coaching on communication styles and conflict resolution.
2. Unexpected changes in project scope or priorities can be unsettling; we aim for clear communication of changes and their rationale as early as possible.
3. We can provide a consistent work environment, clear expectations for communication, and opportunities for focused work without constant interruptions.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Manager, Technical Documentation, R&D (L5)
2. Responsibilities: Set the strategic vision and roadmap for R&D technical documentation, aligning it with overall R&D and business objectives for the next 1-3 years. This means thinking beyond the next document to the entire content ecosystem.
3. Lead, mentor, and develop a team of Technical Documentation Specialists (L2-L4), providing regular coaching, performance reviews, and career guidance. You'll be responsible for their growth and ensuring they're hitting their stride.
4. Architect and implement scalable information architectures and content models (e.g., DITA, topic-based authoring) that support single-sourcing and multi-channel publishing for diverse R&D content. This isn't just theory; you'll make it happen.
5. Own the budget for documentation tools, software licenses, and external contractors (typically £50K-£500K annually), making smart investment decisions that deliver clear ROI. You'll justify every penny.
6. Drive the adoption of Docs-as-Code principles and automation within the R&D documentation workflow, working closely with R&D IT and engineering teams to integrate documentation into the development lifecycle. This means pushing for efficiency.
7. Establish and enforce Good Documentation Practices (GDP) and other relevant regulatory standards (e.g., GxP, ISO) across all R&D documentation, ensuring audit-readiness and compliance. We can't compromise here.
8. Represent the R&D documentation function in cross-functional leadership meetings, influencing decisions related to knowledge management, regulatory strategy, and R&D project planning. You'll be a voice at the table.
9. Supervision: You'll be largely self-directed, managing your own objectives and your team's output. Your Director will provide quarterly strategic alignment and support for major organisational decisions. Day-to-day, you're the boss.
10. Decision: Full authority for your function: budget allocation up to £500K, hiring and firing decisions for your team, vendor selection for documentation tools up to £100K. Strategic direction for the entire R&D documentation function. Any decisions impacting company-wide policy or requiring significant capital expenditure (e.g., a new enterprise EDMS) will need Director and potentially C-suite alignment.
11. Success: Your team consistently delivers high-quality, compliant documentation on time. R&D leadership sees your team as an indispensable strategic partner. You've successfully implemented key initiatives (e.g., new content models, automation) that have demonstrably improved efficiency and reduced risk. Your team members are growing and engaged.

Decision-Making Authority

• Type: Team Hiring & Performance
• Entry: No authority; provides input on candidate fit.
• Mid: Provides detailed feedback on candidate technical skills; may participate in interviews.
• Senior: Recommends candidates, conducts final interviews, provides detailed performance feedback.
• Type: Documentation Strategy & Information Architecture
• Entry: Follows established templates and guidelines.
• Mid: Proposes minor improvements to existing templates or content structures.
• Senior: Designs and implements information architecture for specific programmes; makes recommendations for broader strategy.
• Type: Tool & Vendor Selection
• Entry: Uses assigned tools.
• Mid: Suggests features for existing tools; flags limitations.
• Senior: Evaluates specific tools for project needs; contributes to vendor selection criteria.
• Type: Budget Allocation
• Entry: No budget authority.
• Mid: No budget authority.
• Senior: Recommends budget needs for specific projects (e.g., contractor hours).

Competency Requirements

Foundation Skills (Transferable)

Beyond the technical know-how, you'll need a solid set of leadership and strategic skills to thrive in this role. It's about guiding people, solving problems, and communicating effectively at all levels.

• Category: Leadership & People Management
• Skills: Coaching and Mentoring: Guiding junior team members, identifying development needs, and fostering their growth.
• Performance Management: Setting clear expectations, providing constructive feedback, and addressing performance issues.
• Team Building: Cultivating a positive, collaborative, and high-performing team culture.
• Conflict Resolution: Mediating disagreements within the team or with external stakeholders.
• Category: Strategic Thinking & Planning
• Skills: Roadmap Development: Creating a clear, actionable plan for the R&D documentation function over 1-3 years.
• Resource Allocation: Effectively managing budget, headcount, and external contractors to meet objectives.
• Risk Management: Identifying potential documentation-related risks (e.g., compliance, IP) and developing mitigation strategies.
• Organisational Design: Structuring your team and processes for optimal efficiency and scalability.
• Category: Communication & Influence
• Skills: Executive Presentation: Clearly articulating complex documentation strategies and their business impact to senior leadership.
• Negotiation: Gaining buy-in from reluctant stakeholders or negotiating with vendors.
• Cross-functional Collaboration: Building strong relationships and fostering cooperation with R&D, Regulatory, Quality, and IT teams.
• Active Listening: Truly understanding the needs and concerns of your team and stakeholders.
• Category: Problem Solving & Decision Making
• Skills: Complex Problem Analysis: Breaking down large, ambiguous documentation challenges into manageable components.
• Strategic Decision Making: Making informed choices that balance short-term needs with long-term strategic goals.
• Root Cause Analysis: Identifying the underlying reasons for documentation inefficiencies or issues.
• Adaptability: Adjusting plans and strategies in response to changing R&D priorities or market conditions.

Functional Skills (Role-Specific Technical)

You'll need a deep understanding of documentation methodologies and how they apply specifically to the R&D world. This isn't just about knowing the tools; it's about knowing how to use them strategically to solve real problems.

Technical Competencies

• Skill: DITA (Darwin Information Typing Architecture)
• Desc: Deep expertise in topic-based authoring principles (Concept, Task, Reference), content reuse strategies, and DITA specialisation. You'll be designing and implementing DITA-based content models, even if we're not using a pure DITA tool.
• Level: Expert
• Skill: Good Documentation Practice (GDP) & ALCOA+
• Desc: Comprehensive understanding and practical application of GDP, including ALCOA+ principles (Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, Available). You'll be the ultimate authority on compliance for your team.
• Level: Expert
• Skill: Information Architecture (IA)
• Desc: Advanced ability to design scalable, intuitive, and compliant content structures for complex R&D documentation, from internal knowledge bases to formal regulatory submission dossiers (e.g., CTD, eCTD). This includes taxonomy, metadata, and navigation design.
• Level: Expert
• Skill: Minimalism & User-Centred Design
• Desc: The discipline of writing just enough information for the user to succeed, ruthlessly cutting extraneous detail. You'll champion user-centred design principles to ensure documentation meets the actual needs of scientists, engineers, and regulators.
• Level: Advanced
• Skill: Docs-as-Code & CI/CD
• Desc: Architectural understanding and practical experience implementing Docs-as-Code pipelines, including Git-based version control, automated builds, and continuous integration/continuous deployment (CI/CD) for documentation. You'll be integrating documentation into the software development lifecycle.
• Level: Advanced
• Skill: Single-Source Authoring & Content Strategy
• Desc: Strategic expertise in creating content once and publishing it to multiple formats (e.g., PDF, HTML5, XML) from a single master source, ensuring consistency, efficiency, and reduced maintenance. You'll be designing and managing the overall content strategy.
• Level: Expert

Digital Tools

• Tool: MadCap Flare / Adobe FrameMaker
• Level: Architect
• Usage: Evaluating, selecting, and architecting the single-sourcing strategy using these or similar authoring platforms. Designing complex project templates, managing variables, and overseeing output transformations for the team.
• Tool: Confluence & Jira
• Level: Architect
• Usage: Designing and governing Confluence space information architecture for R&D knowledge management. Integrating Jira/Confluence with other enterprise systems and setting governance policies for collaborative documentation.
• Tool: Git (via GitHub/GitLab)
• Level: Architect
• Usage: Implementing and managing a full 'Docs-as-Code' pipeline, including CI/CD for automated doc builds and deployments. Setting branching strategies and overseeing pull request workflows for the team.
• Tool: Veeva Vault / MasterControl (EDMS)
• Level: Architect
• Usage: Designing and managing the document lifecycle and review workflows within the Electronic Document Management System (EDMS). Serving as the business owner for the platform and ensuring GxP compliance.
• Tool: Visio / BioRender / ChemDraw
• Level: Advanced
• Usage: Establishing the visual language and standards for all technical illustrations and diagrams across R&D. Selecting and managing enterprise licenses for diagramming tools and guiding the team on best practices.
• Tool: Benchling / Labguru (ELN)
• Level: Advanced
• Usage: Working with R&D IT to define metadata standards and integration points between the Electronic Lab Notebook (ELN) and documentation systems. Ensuring efficient extraction of source material for documentation.

Industry Knowledge

• Area: R&D Lifecycle (Drug Discovery to Commercialisation)
• Desc: Deep understanding of the entire R&D pipeline, from early-stage research and preclinical development to clinical trials, regulatory approval, and post-market surveillance. You'll know where documentation fits into each stage.
• Area: Scientific & Engineering Principles
• Desc: A solid grasp of fundamental scientific (e.g., chemistry, biology, pharmacology) and engineering concepts relevant to our specific research areas. You don't need to be a PhD, but you need to understand the science your team is documenting.
• Area: Intellectual Property (IP) Documentation
• Desc: Understanding the role of documentation in protecting intellectual property, including patent applications, lab notebooks, and invention disclosures. You'll ensure your team's work supports our IP strategy.

Regulatory Compliance Regulations

• Reg: GxP (Good x Practice, e.g., GLP, GCP, GMP)
• Usage: You'll be the primary expert for your team on GxP requirements for documentation, ensuring all processes and outputs are fully compliant for regulatory submissions and audits. This includes understanding audit trails, version control, and data integrity.
• Reg: ISO 9001, ISO 13485 (Medical Devices)
• Usage: Understanding how documentation contributes to quality management systems, particularly for medical device development. You'll ensure our documentation processes align with these international standards.
• Reg: Data Integrity (ALCOA+ principles)
• Usage: Championing and enforcing data integrity principles across all R&D documentation, ensuring that data is attributable, legible, contemporaneously recorded, original, and accurate. This is non-negotiable for regulatory compliance.

Essential Prerequisites

• Extensive experience (10+ years) in technical documentation within a regulated R&D environment (e.g., pharmaceuticals, biotech, medical devices).
• Demonstrable experience leading and managing a team of technical writers or information developers.
• Proven track record of designing and implementing complex information architectures and content strategies.
• Hands-on experience with at least one major Component Content Management System (CCMS) like MadCap Flare, Paligo, or similar.
• Strong understanding of regulatory requirements for R&D documentation (e.g., GxP, ISO).
• Experience with version control systems like Git for documentation management.

Career Pathway Context

You should have already mastered the core technical writing skills and led significant documentation projects. This role is about stepping up to manage people, strategy, and budget, rather than just individual contributions. Think of it as moving from 'doing' to 'enabling' and 'directing'.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: AI-Driven Content Orchestration
• Why: AI isn't just for drafting anymore; it's becoming central to how we manage, personalise, and deliver content at scale. Competitors are already using AI to dynamically generate content variants and manage content lifecycles, and we need to be there too.
• Concepts: [{'concept_name': 'Generative AI for Content Creation', 'description': 'Understanding how LLMs can be used beyond first drafts, for content summarisation, rephrasing for different audiences, and even generating new content topics.'}, {'concept_name': 'AI-powered Content Personalisation', 'description': 'Exploring how AI can tailor documentation delivery based on user role, project, or even individual learning preferences.'}, {'concept_name': 'Semantic Content Tagging & Search', 'description': 'Using AI to automatically tag and categorise content with rich metadata, improving discoverability and reuse across vast R&D repositories.'}, {'concept_name': 'AI for Compliance & Risk Detection', 'description': 'Leveraging AI to proactively identify potential compliance issues, inconsistencies, or ambiguities in documentation before they become problems.'}]
• Prepare: This quarter: Pilot an AI-powered content analysis tool (e.g., Acrolinx) to audit existing documentation for consistency and compliance.
• Next 6 months: Develop a proof-of-concept for using generative AI to create a specific type of R&D documentation (e.g., a simplified protocol from a complex one).
• Month 9-12: Research and evaluate enterprise-grade AI content platforms that can integrate with our existing CCMS/EDMS.
• Ongoing: Encourage your team to experiment with AI tools for daily tasks and share best practices internally.
• QuickWin: Start using AI tools (like ChatGPT or Claude) for summarising long research papers, generating meeting agendas, or drafting initial email communications to free up your strategic thinking time.

Advancing Technical Skills

• Skill: Advanced Content Engineering & Toolchain Integration
• Why: The trend towards highly automated, integrated documentation toolchains means you need to understand how all the pieces fit together. Your role shifts from using tools to designing and managing the entire content engineering ecosystem.
• Concepts: [{'concept_name': 'API-First Documentation', 'description': 'Understanding how documentation can be generated and consumed via APIs, enabling dynamic content delivery to various platforms and applications.'}, {'concept_name': 'Microservices for Content Delivery', 'description': 'Exploring how content can be broken into microservices for greater flexibility, scalability, and integration with other R&D systems.'}, {'concept_name': 'Headless CMS & Component Content Management', 'description': 'Deep dive into headless CMS architectures and advanced CCMS features for managing granular content components and their reuse across the enterprise.'}, {'concept_name': 'DevOps for Documentation', 'description': 'Applying DevOps principles (automation, collaboration, continuous delivery) to the entire documentation lifecycle, from authoring to publishing.'}]
• Prepare: This quarter: Work closely with R&D IT to map out our current documentation toolchain and identify integration gaps.
• Next 6 months: Lead a project to integrate our CCMS with our ELN or a regulatory submission system using APIs.
• Month 9-12: Explore industry best practices for content engineering and present a proposal for a future-state documentation architecture.
• Ongoing: Stay current with new releases and features of our core documentation platforms and related R&D software.
• QuickWin: Identify one manual step in your team's current publishing workflow and automate it using a simple script or existing tool integration.

Education Requirements

• Level: Minimum
• Req: A Bachelor's degree in a scientific, engineering, technical communication, or related field.
• Alts: Equivalent practical experience (e.g., 15+ years in technical documentation within R&D) will be considered if supported by a strong portfolio and leadership track record.
• Level: Preferred
• Req: A Master's degree or PhD in a scientific discipline, or a Master's in Technical Communication, Information Science, or a related field.
• Alts: N/A

Experience Requirements

You'll need roughly 12-16 years of progressive experience in technical documentation, with at least 5-7 years specifically in a regulated Research & Development environment. This must include a minimum of 3-5 years in a formal leadership or management role, overseeing a team of technical writers or information architects. We're looking for someone who has genuinely 'been there, done that' when it comes to managing complex R&D documentation programmes and leading people.

Preferred Certifications

• Cert: Certified Professional Technical Communicator (CPTC)
• Prod: Society for Technical Communication (STC)
• Usage: Demonstrates a broad understanding of technical communication principles and best practices, relevant for leading a team.
• Cert: DITA Specialist/Architect Certification
• Prod: Various (e.g., LearningDITA, specific tool vendors)
• Usage: Validates expertise in DITA, crucial for designing and implementing advanced content models and single-sourcing strategies.
• Cert: Project Management Professional (PMP)
• Prod: Project Management Institute (PMI)
• Usage: Useful for managing complex documentation projects, resources, and timelines within an R&D context.

Recommended Activities

• Attending industry conferences focused on content strategy, technical communication, or R&D information management (e.g., LavaCon, STC Summit, Pharma Documentation Conferences).
• Participating in professional organisations like the Society for Technical Communication (STC) or relevant life sciences associations.
• Enrolling in advanced courses or workshops on AI in content, content engineering, or regulatory affairs.
• Regularly reading industry publications and thought leadership pieces to stay abreast of trends and best practices.

Career Progression Pathways

Entry Paths to This Role

• Path: Senior Technical Writer (L3) to Manager (L5)
• Time: Roughly 3-5 years as a Senior Technical Writer.
• Path: Lead Technical Writer / Staff Information Architect (L4) to Manager (L5)
• Time: Roughly 2-3 years as a Lead/Staff Information Architect.
• Path: Technical Manager from Related R&D Discipline
• Time: Highly variable, depending on prior experience, but typically 1-3 years in a transitional role or with significant self-study.

Career Progression From This Role

• Pathway: Director, R&D Content Strategy & Operations (L6)
• Time: 3-5 years in the Manager role.

Long Term Vision Potential Roles

• Title: VP, Scientific & Technical Communications (L7)
• Time: 5-10 years from Manager level.
• Title: Chief Knowledge Officer (CKO)
• Time: 10-15 years from Manager level.
• Title: Head of R&D Operations
• Time: 8-12 years from Manager level.

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.