Notes from the work

I do not write ESG or sustainability reports to decorate a website. I write them so a programme manager, a donor, and an operations lead can make the same decision with the same facts. If the document cannot survive a Monday morning meeting, it has already failed.

Too many organisations treat reporting as a compliance ritual. They collect last year’s numbers, polish the language, and file the PDF. Then operations continue exactly as before. That is not reporting. That is theatre. Real reporting names what moved, what stalled, and what you will change in the next quarter.

Trust between partners is operational, not sentimental. Teams do not stay aligned on goodwill. They stay aligned on deliverables, meeting notes, and honest status. Name the output. Name the owner. Name the date. The same rule holds whether you are coordinating across borders or running a single site.

Frameworks matter when they force discipline. GRI, donor logframes, and internal dashboards are useful in that role. They are useless when they become a second job the field team cannot feed. Start from the data you already generate — registers, farm records, procurement files — and map those sources to the indicators a board or funder actually asks for. You do not invent a parallel universe of metrics. You make the existing system speak clearly.

Separate “sustainability” from operations and you will get a pretty annex that nobody uses when the real work starts. Labour, inputs, compliance, and cash belong in the same notebook. If you want a report I will stand behind, bring me the programme, the partners, and the books. I will cut the filler, keep the evidence, and leave you with a document your team can run.

Impact is not a feeling. Impact is a change you can show: who joined, who saved, who planted differently, who kept a business open. I build monitoring systems that capture those facts at the point of work, not three months later in a hotel workshop.

A glossy “lives touched” figure without a register is not M&E. It is advertising. Scale only holds if you know who is still in, what is performing, and which activities changed practice. If you cannot answer those three questions from your own records, you do not have an impact system. You have a story.

A practical system has four parts. First, a theory of change you can say out loud in the languages your teams actually use. Second, a short set of indicators tied to activities you already run. Third, tools people will fill — paper or digital, as long as they are used. Fourth, a review rhythm: weekly for operations, monthly for programme leads, quarterly for partners and funders. I do not add dashboards until those four are working.

If your measurement ignores the room where the work happens, you will miss the real risks — dropout, elite capture, weak record-keeping — and you will still produce a beautiful annual report. Curriculum without follow-up is a workshop. Follow-up without data is a rumour. Track completion, application, and the next bottleneck: market, capital, or skills.

Bring me a programme that needs to prove results. I will build the framework, train the people who collect the data, and use the numbers to manage. That is monitoring and evaluation as operations — which is the only version that lasts.

Trust is not a communications product. Trust is what happens when people see you keep time, share information, and own mistakes in front of them. I treat stakeholder engagement as project infrastructure, equal to budget and workplans.

Time zones, languages, and institutional cultures will fracture a programme unless someone holds the calendar, the agenda, and the follow-up. I hold that line. Deliverables and reporting stay on schedule because the rooms stay honest. Partners who hear last do not stay partners.

I use a simple map. Who decides. Who implements. Who is affected. Who funds. Who can block. Then I set a cadence that matches power: community groups need regular, local contact; regional bodies need formal forums; international offices need concise written updates. Mixing those audiences in one generic newsletter is how you lose all of them.

Community-level work demands the same spine. People trust you when you show up, speak plainly, and deliver what you promised. Working in the languages people actually use is not a courtesy. It is the job. A closing photo and a vague communique are not outcomes. Owners and next steps are.

If your “stakeholder strategy” lives only in a proposal annex, you do not have one. Hire someone who will run the meetings, keep the list current, and tell you when a partner is slipping. That is the work I do.

I respect a climate pledge the day it changes seed, water, labour, or land use. Until then it is a press statement. East African agriculture already lives with delayed rains, input costs, and market swings. The response is not another workshop on “awareness.” The response is operations.

Practice is the test. Soil, diversity, water, and production methods only count if people keep them after the trainer leaves. I do not sell silver bullets. I install habits and follow-up. Partnerships matter when they strengthen that field work. They do not matter when they add logos to a banner.

Commercial production has to stay viable or the climate plan dies with the season. Budgeting, planning, bookkeeping, compliance, workforce, and market expansion are climate tools whether the donor language says so or not. A farm that cannot plan labour or inputs will not adapt. A farm that tracks costs and yields can change a practice and see what it did.

Water and health sit in the same frame. Clean water and dignified work are climate and public-health infrastructure. Treat them as side projects and you will keep writing the same proposal. Human, animal, and environmental health do not wait for your organogram. Put the work in the plan and the budget, with owners — not slogans.

If you want climate results, put them in the workplan. I will help you do that. Leave the pledges for the people who do not have to harvest.

I am hired to make organisations run. Sustainability that cannot survive contact with payroll, procurement, and planting calendars is not strategy. It is branding. I refuse to separate “the real work” from “the impact work.” They are the same ledger.

The business case is straightforward. Waste money on confused roles and you lose margin. Miss compliance and you lose the licence to operate. Ignore staff development and you lose the season. Serve a market you have not mapped and you sit on stock. Those failures are expensive in agribusiness and fatal in programmes that promised results to communities and funders. I fix them with planning, not with posters.

Sustainability is a farm that can pay people, buy inputs, and sell. It is partners who still answer the next call because the last one produced output. It is households with a mechanism and a skill they still use after the project year ends. If it does not show up in the budget, the roster, and the harvest, it is not strategy.

I use a tight sequence. Discovery: what is actually happening, not what the last proposal claimed. Strategy: a plan with owners and dates. Implementation: I stay close enough to see slippage. Optimization: we measure and we cut what does not work. Resource mobilisation belongs inside this system. A grant you cannot absorb and report against is a liability, not a win.

If you want competitive advantage, run a tighter operation and tell the truth about results. I will help you do both. I will not help you paste sustainability onto a weak core and hope the market does not notice.

A supply chain is not a slogan about “from farm to market.” It is a sequence of people, prices, quality checks, and transport that either holds or breaks. I start by drawing that sequence on one page. If you cannot name your suppliers, your offtakers, and the cash gap between them, you are guessing.

Partnerships with suppliers and distributors are operations, not networking. A handshake without volume, quality specs, and payment terms is not a partnership. It is a risk you have not priced. Inputs must arrive, labour must be rostered, and goods must leave at a grade a buyer will pay for. Miss any link and the rest of the plan is decoration.

Rural enterprises fail less often on “motivation” than on the chain around them: seed, tools, aggregation, and a buyer who pays on time. Capacity-building that ignores the chain produces certificates. Capacity-building that maps the chain produces businesses that still exist at the next harvest.

The same is true of information and services. If procurement is slow and knowledge is trapped in inboxes, the programme stalls. Visibility is the first control: who supplied last month, what failed quality, where stock sits, when cash went out and when it came back. I put that in simple records before I talk about software. Tools follow discipline. Discipline does not follow a new app.

If your chain is leaking — quality, time, or trust — I will map it with the people who move the goods and I will close the gaps that matter. Global complexity is not an excuse. You still own the links you can see. See them. Run them.