AI capacity building
The gap is not technological. It is methodological. Staff experiment individually, without shared protocols, without understanding what happens to the data they feed into external tools. This programme builds the framework your organisation is missing. The training is tailor-made for your actual workflows, delivered at your pace.
// the real problem
It's not that your teams don't use AI. They do. Individually, inconsistently, and often without knowing what happens to the data they feed into external tools.
Beneficiary data entered into ChatGPT because someone needed a quick translation and didn't think it through. No protocol. No shared understanding of where the data goes.
Five staff writing the same sitrep five different ways. None using the prompt structure that would cut preparation time in half. The efficiency gains AI should deliver aren't materialising.
AI outputs treated as final. Hallucinations in donor reports, incorrect figures in logistics summaries, no verification step. The tool is used. The methodology isn't.
Zero institutional memory. When the person who figured it out leaves, the knowledge leaves with them. No shared prompt library. No internal reference. Nothing that survives a staff rotation.
// engagement formats
Every format is built from your actual documents and workflows. It is not adapted from a generic catalogue. The depth of the engagement depends on what your organisation needs and what it is ready for.
A focused entry point for teams that want to understand what AI can and cannot do before committing to a full programme. AI landscape, hallucination risks, data protection basics and a first live exercise on your own documents.
One department, one day. A 30-minute pre-session scoping with the department head defines which tasks to target — sitreps, financial summaries, procurement files, field reports. Every exercise runs on your actual files. The session produces a prompt library your team uses the following week.
Compliance before productivity. Foundation before specialisation. Two all-staff sessions establish the shared language and data protection baseline. Six department modules build the specific workflows. A closing session produces the institutional reference your organisation needs to sustain adoption independently.
// 10-week programme
The order is not arbitrary. Compliance before productivity. Shared language before department-specific toolkits. Foundation before specialisation. Each layer depends on the one before it.
// specialised modules
"A finance module built on generic templates wastes three hours. A finance module built on your actual reporting formats changes how the team works the following week."
Budget tracking, financial reporting, variance analysis, donor financial templates. AI-assisted drafting of financial summaries and reconciliation notes without exposing sensitive figures to external tools.
Waybills, stock reports, supply chain documentation, movement tracking summaries. Structuring and synthesising logistics data at speed — without manual reformatting.
RFQ drafting, supplier communication, procurement reports, compliance documentation. Accelerating the document cycle without losing audit-trail quality.
Sitreps, 5W/4W matrices, proposal narratives, indicator tracking, field reports. The highest documentation workload in any humanitarian mission — and the clearest gain from structured AI-assisted drafting.
Meeting prep, stakeholder briefs, talking points, inter-agency communication. Synthesising inputs from multiple partners into coherent, sendable outputs in minutes rather than hours.
Technical report drafting, literature synthesis, guidelines adaptation, training materials. For technical staff who carry significant writing workloads — and who can reclaim that time without sacrificing quality.
// who this is for
This programme is not for tech teams. It is for the people who write the sitreps, manage the budgets, coordinate the supply chains — and who have been told AI is useful without ever being shown exactly how, and without anyone explaining what to do when it gets the data wrong.
// what this is not
Built for another audience and rebranded. No sitrep examples. No 4W files. No understanding of donor templates or beneficiary data obligations. Participants leave knowing what AI is. Not how their organisation should use it.
Every exercise runs on documents your teams produce. Every prompt is tested against your reporting formats. Every module produces a deliverable your organisation owns permanently. Participants leave with a working toolkit, not a certificate.
Kanon builds and transfers. It does not manage. The prompt libraries, the reference guide, the data protocols. Everything is yours at handover. The programme is designed to make itself unnecessary.
At the end of the programme, your organisation has the shared language, the department-specific toolkits, and the internal protocols to sustain AI adoption without external support. Staff rotations don't reset the clock. The knowledge stays.
// start here
A short message: your sector, team size, and the documentation workload that costs your teams the most time. That's enough to scope a first conversation. No form. No pitch deck. A direct exchange about whether this programme fits your context.
Response within 24 hours. For the 10-week programme, a scoping call with your operations or HR lead is the natural next step. For a half-day or department module, a brief exchange is usually enough.