Ayomide Yissa · Documentation & Systems · Lagos, Nigeria
A bit about me
As a writer, I'm curious about how complex systems work and I love explaining them clearly. Over time, that curiosity expanded beyond writing into the systems behind it: how documentation is structured, how information flows, and why things break as organisations grow. Today I work at the intersection of documentation, information architecture, and business operations — always asking the same question: can this be clearer?
Two things I do
Documentation & Information Architecture
I design how organisations structure and deliver information. Creating dev docs, API references, knowledge bases. I don't just write docs, I understand how it fits into the bigger picture.
Docs-as-Code · Diataxis · Taxonomy
Systems & Operations Design
I design the systems that organisations run on—structuring how information is organised, how work flows, and how processes scale as things grow. I design systems that are structured, repeatable, and built for long-term use.
HubSpot · Zapier · Airtable · Apps Script
Selected work
Systems & Ops · Case study
Progress Report Automation System
Designed a complete student reporting system — from defining what "progress" meant organisationally, to automated PDF generation.
Systems & Ops · Case study
Revenue Operations Infrastructure
Architected the full RevOps stack for a $2M+ organisation — connecting every stage from first inquiry to fulfilment.
Documentation · API reference
Finance API Documentation
Full API reference, authentication guide, and endpoint documentation for a financial data product.
Documentation · Open source
NBA-API Package Documentation
Designed and published community documentation for the NBA-API Python package, filling a gap in the open source project.
IA Audit · Coming soon
Information Architecture Audit in progress
A full IA review of a real product — current structure, where users get lost, and a proposed redesign.
I'm looking for a full-time remote role — as an information architect, technical writer, or operations specialist — helping teams bring structure and clarity to how information is organised and how work gets done.
A selection of documentation projects, systems I've designed, and operational infrastructure I've built. Case studies go into the thinking behind the work, not just the output.
Systems & Ops · Case study
Progress Report Automation System
An education company had no standardised way to communicate student progress to parents. Reporting was inconsistent, manual, and disconnected from what was actually happening in the classroom. I designed the system end-to-end — starting with the hardest part: defining what "progress" actually meant across the organisation.
Systems & Ops · Case study
Revenue Operations Infrastructure
A fast-growing edutech company had disconnected tools and no unified view of their customer pipeline. I designed and implemented the full revenue operations stack — connecting inquiry, consultation, enrolment, and fulfilment into a single coherent system for an organisation with over $2M in lifetime revenue.
Documentation · API reference
Finance API Documentation
Full API reference documentation for a financial data product — including authentication flows, endpoint references, parameter tables, and example responses. Built in Gitbook with a focus on developer usability.
Documentation · Open source
NBA-API Package Documentation
Community documentation for the NBA-API Python package — an open source project that lacked a proper reference. Designed the IA, wrote the guides and endpoint references, and deployed the site. Also wrote an accompanying tutorial on using the package.
Documentation · Open source contribution
MindsDB IBM-db2 Integration Docs
Contributed the IBM-db2 integration documentation to the MindsDB open source project — covering setup, configuration, and usage with the MindsDB AI layer.
IA Audit · In progress
Information Architecture Audit coming soon
A full IA review of a real product — mapping the current structure, identifying where users get lost, and proposing a redesigned architecture with before/after diagrams.
Articles on documentation strategy, knowledge base design, systems thinking, and operations. I write to figure things out as much as to explain them.
KnowledgeOwl · Documentation strategy
Calculating the ROI of Documentation
How to measure the business value of documentation — and make the case for investing in it properly.
KnowledgeOwl · Knowledge base design
Help Centers as the Foundation of Excellent Service
Why a well-structured help centre isn't a support tool — it's a product decision with company-wide implications.
KnowledgeOwl · Documentation craft
Optimizing Visuals in Technical Documentation
When images help, when they hurt, and how to make the call.
Ayo's Notebook · Operations thinking
Stakeholder Management
What I've learned about managing up, across, and through — from inside the work.
Ayo's Notebook · Systems thinking
Measuring Before Change Matters More Than You Think
Why the baseline you establish before making a change is often more valuable than the measurement you take after.
Hashnode · Technical writing
Predictive Maintenance with Machine Learning
Process, challenges, and insights from documenting a complex ML application for a non-specialist audience.
Five years across writing, systems, and operations — and still asking the same question.
I started my career as a writer — curious about how complex things worked and obsessed with explaining them clearly. That instinct led me into technical writing, where I discovered something more interesting than writing itself: the systems underneath the words.
Documentation lives inside processes. A knowledge base is only as good as the information architecture holding it together. A tutorial only makes sense if the product workflow it describes actually works. The more I wrote, the more I found myself redesigning the systems I was documenting.
Over the past five years, that instinct has taken me from writing API references and developer guides to building the operational infrastructure that organisations run on — CRM pipelines, workflow automations, progress-tracking systems. I've come into early-stage companies and created the structure that didn't exist yet: the frameworks, the tools, the processes, the documentation.
Along the way I interned on what's considered the best-selling technical writing manual of all time at Boffin Education, contributed to open source documentation projects including MindsDB and The Good Docs Project, and have been a regular contributor to KnowledgeOwl — writing about documentation strategy and knowledge base design.
I think of myself as someone who connects the dots. I take a complex system, ask why it isn't clearer, and build something that makes it so. I'm at the stage of my career where I want to go deep — to join a team with real structure, bring everything I've learned, and grow into the best version of what I do.
What I'm looking for
A full-time role — as an information architect, technical writer, or operations specialist — at an organisation that's clear about where it's going and serious about developing its people.
Role titles that fit what I do: Information Architect, Documentation Engineer, Technical Writer, Knowledge Systems Lead, Technical Program Manager, Operations Specialist. I'm more interested in the problem than the title.
Tools & skills
Documentation & IA
Operations & Systems