Building a documentation practice
I have done this twice, at Tavisca and at Miro: deciding the structure, the templates, the owners, the review cadence, and the versioning from nothing, and documenting the process so that it survives a handover.
Information architecture and standards
I decide the categories, standardize the formats, and organize content so it can be found, reused, and scaled across teams, in XML and DITA where reuse matters. I set and enforce the standards, templates, terminology, and review workflows around it.
Docs-as-code and release velocity
Markdown and MDX in Git, GitHub workflows, versioned documentation, and linting in the pipeline, so documentation ships with the release rather than trailing it.
Explaining AI and agent-based concepts
I use Claude and Claude Code daily, build multi-step LLM pipelines with structured outputs and evals, and work with agentic AI and RAG systems. I structure content so retrieval works for AI assistants as well as people, and write about it for non-expert audiences.
Technical and customer-facing documentation
Product documentation, API reference, Help Center and knowledge base content, release notes, SOPs, onboarding guides, and training material. I work in instructional design myself, so collaborating with designers and trainers is familiar from both sides.
Education and certifications
Bachelor of Arts, English, Indira Gandhi National Open University (IGNOU), India.
Design Thinking (Stanford University Graduate School of Business), Information Mapping (TechDoc), Certified Usability Analyst (Human Factors International), PRINCE2 Agile Foundation & Practitioner (AXELOS), Certified ScrumMaster and Certified Scrum Product Owner (Scrum Alliance), Data Visualisation & Storytelling (Growth Tribe), Professional Diploma in Digital Marketing (Digital Marketing Institute), and Salesforce Trailhead Ranger.
In progress: Claude Certified Architect (Foundations), AI Governance Professional (IAPP AIGP)