Community Organisation Programme
From a community technology challenge to a governed, testable and locally owned response.
This programme helps community organisations move from an unbounded request for an app, database or platform to a validated service challenge, responsible requirements, tested response, accountable operating model and staged investment decision.
Quick facts
The regional delivery model is a target. No cohort location has been formally approved and published.
The challenge
Community technology projects can begin with a product preference before the service need, users, information flows, risks and long-term owner are properly understood. This creates expensive systems, fragmented processes, unsafe data practices and supplier dependency.
Community Technology Catalyst makes the decision process explicit. It allows process improvement, configuration, procurement, bounded build work—or a responsible no-build recommendation—to emerge from evidence.
Intended participants
Entry criteria and exclusions stay on the page rather than behind a toggle, so nobody applies for a programme that cannot help them.
The organisation must:
Capabilities
Frame technology work around a validated community or organisational outcome.
Map service delivery, information flows, decisions, controls and failure points.
Define functional, accessibility, security, safeguarding and operational requirements.
Compare build, buy, configure and improve-current-process options using full cost and dependency.
Create a bounded prototype or configuration and test it against approved acceptance criteria.
Establish governance, support, data stewardship, budget, documentation and exit arrangements.
The five-day intensive
A day is not complete because it was attended. Each day ends at a gate that has to be passed before the next stage of work begins.
Day outcome: Each organisation leaves with a validated problem boundary tied to a real service outcome and named ownership.
Approved Challenge Brief, community/service experience map and evidence plan.
The sponsor and service owner approve mandate, outcome, scope, ownership, measures and stop conditions before solution design.
Day outcome: Organisations expose how work and information really move, including informal workarounds and risk.
Service blueprint, information map, risk register and initial treatments.
A validated current-state workflow, category-level information map, high-risk treatments and residual-risk decision-maker are present.
Day outcome: Organisations define what a response must achieve before comparing products or approving build work.
User/access contexts, prioritised requirements, option scorecard and prototype decision.
No prototype begins without approved user contexts, must-have requirements, risk constraints, an option decision and an owner.
Day outcome: Each organisation produces evidence about a response, not a polished but untested demonstration.
Non-production prototype or process configuration, test records, decision log and evidence review.
Critical acceptance criteria pass or have approved treatment, and the prototype remains explicitly labelled non-production.
Day outcome: The intervention leaves the workshop with accountable ownership, an affordable roadmap and a documented exit path.
Operating model, control schedule, costed roadmap, decision pack and handover.
Completion requires an approved decision pack, explicit residual risks, named owners, a costed next stage and a non-production label unless separate deployment approval exists.
Capstone
Each participating organisation completes a Technology Catalyst Decision Pack. Any prototype inside it remains explicitly non-production until separately approved, tested, resourced and owned.
The full cycle
| Period | Phase | Required result |
|---|---|---|
| Months 1–2 | Partnership and co-design | Regional partners, governance, community participation and funding envelope agreed. |
| Month 3 | Select organisations | Up to six organisations pass mandate, readiness, safeguarding and ownership gates. |
| Months 4–5 | Discovery and baseline | Service evidence, stakeholder input and current-state measures validated. |
| Month 6 | Five-day catalyst intensive | Up to 18 representatives produce an approved intervention concept and decision pack. |
| Months 7–10 | Prototype and implement | Time-boxed prototype cycles, user/community testing and partner decisions recorded. |
| Months 11–12 | Adoption and capability transfer | Internal owners operate the intervention and recovery/continuity routes. |
| Month 13 | Regional learning | Cross-organisation review separates reusable patterns from local conditions. |
| Month 14 | Independent review | Service, access, risk, sustainability and ownership evidence verified. |
| Month 15 | Exit or scale decision | Handover, archive and close/remediate/extend decision approved. |
Cohort sizes and representative numbers are proposed cycle targets, not organisations already supported.
Assessment and completion
Ubuntu Gale records completion, demonstrated competence and portfolio evidence. It does not describe any programme as an accredited qualification.
The organisation must provide:
A responsible no-build decision may be a successful outcome.
Coaching and follow-through
The decision pack is the start of the implementation cycle, not the end of it.
Ubuntu Gale programmes use fictional, synthetic, anonymised or safely aggregated information during workshop activity. Participants do not expose passwords, recovery codes, production credentials or sensitive personal information. Accessibility, low-bandwidth access, safeguarding, cybersecurity basics, source attribution and responsible AI use are designed into the work rather than left to a final checklist.
Intended measures and evidence
These are the measures the programme assesses. They are not results already achieved.
Participation, completion, demonstrated competence, implementation, adoption and outcome evidence are reported separately. See the public evidence ladder
Limits
Frequently asked
No. The five-day catalyst intensive sits inside a 15-month cycle covering partnership co-design, organisation selection, discovery and baseline, prototype and implementation, adoption, regional learning, independent review and an exit or scale decision.
No. The programme exists precisely to test that. It begins with the service outcome and evidence, then compares build, buy, configure and improve-current-process options before any prototype work is approved.
You leave with a tested non-production prototype or process configuration, test evidence and a costed roadmap. Production deployment requires separate approval, testing, security, operational support and accountability.
Only synthetic, anonymised or safely aggregated data. Beneficiary names, case details, identity numbers, medical information and credentials must not be brought into workshop exercises.
Two or three representatives — an executive sponsor, a service owner and an operating or data owner where feasible. The sponsor and service owner must attend the required decision gates.
Next steps
Every route below leads to the same enquiry form, which asks only for what your role needs.
For community organisations, NGOs and social initiatives with a mandate and an evidenced service challenge.
Continue — Register interestFor funders able to support regional delivery, organisational participation and independent review.
Continue — Fund a catalyst cohortFor delivery and specialist partners contributing facilitation, technical, safeguarding or data expertise.
Continue — Join the delivery network