The letter
Consulting · Teaching · Mentoring · Speaking
Jacob Mziya
Lilongwe, Malawi
Dear reader,
People write to me for three kinds of help. Each begins the same way — with a conversation about what is actually going on — and each ends with something that keeps working after I've left the room.
Systems that institutions can depend on
For governments, public programmes, NGOs and growing businesses whose important work runs on software that has become hard to change — or that doesn't exist yet.
- A systems review: architecture, data, operations and the people around them, with a plain written account of why things are hard and what to do first.
- Design and modernisation of the platform itself — data models, migrations, APIs, deployment, monitoring — the kind of work behind the Social Cash Transfer MIS.
- Digital foundations for growing organisations through MonityIO: cloud infrastructure, workspaces, websites and workflows that hold together as you scale.
- Bringing AI into an existing organisation in a way that genuinely helps, rather than adding another tool nobody owns.
It usually runs: a conversation → a short diagnostic → a written recommendation → then either I build it with your team, or you take the plan and run.
Workshops, training and lectures
For engineering and ICT teams, leadership teams, universities and programmes that want their people to think in systems, not just tools.
- Systems thinking for digital transformation — for leaders and programme teams who have to decide, not code.
- Building software for institutions that can't afford to fail — for engineers: legacy modernisation, data migration, deployment and monitoring, done carefully.
- Practical engineering sessions — Java and Spring Boot, TypeScript, infrastructure and pipelines — taught from real systems rather than slides.
- Guest lectures and short courses for universities and training programmes.
Formats: a half-day or full-day workshop, a multi-week course, or a single lecture. In a room in Malawi, or online anywhere.
For engineers and founders
For engineers who want to grow from writing code into designing systems, and founders building their first real systems who want a thinking partner rather than a vendor.
- Recurring conversations about the work in front of you — architecture, decisions, careers.
- Reviews of designs and code, with the reasoning written down so it compounds.
- An honest outside view when something feels wrong and nobody can name it yet.
I take a few people at a time so each gets real attention. Write with where you are and where you're trying to get to.
Conferences, universities, leadership offsites. Talks designed like systems: one idea, built to survive the walk back to the office.
Systems thinking for digital transformation
Why most transformation projects fail, and the systems lens that changes the odds.
Technology in institutions that can't afford to fail
Building and modernising software inside governments, NGOs and critical services — where mistakes have consequences.
AI inside an existing organisation
Taking AI seriously without chasing every trend: where it genuinely fits, and what has to be true first.
Not sure which of these fits? Write anyway. Most of the best work I've done started with a conversation that didn't yet have a name.
Yours,
Jacob