Why industry linkage is not a brochure paragraph
I teach and coordinate e-learning work in the Faculty of Computing and Informatics at Makerere University Business School (MUBS). Employers who visit our labs do not ask whether a student can recite the OSI model from memory. They ask whether the graduate can read a ticket, harden a small service, write a clear incident note, and work with a team under time pressure. That gap between lecture theory and workplace tasks is exactly what Competence-Based Education (CBE) is supposed to close.
NCHE lists Industry and Community Linkages among the nine focus areas in its draft minimum standards for CBE, alongside curriculum design, teaching, assessment, faculty support, student support, quality assurance, monitoring and evaluation, and gender and equity mainstreaming: NCHE consultative meeting on CBE reforms (January 2026). From the 2027/2028 academic year, first-year intake is expected only on CBE-aligned programmes. Related: what the 2027 mandate means for computing faculties. This post is a practical linkage ladder for a Ugandan computing faculty, not a hymn to "partnerships" in the abstract.
What NCHE is asking campuses to do
Curriculum under CBE is not meant to be designed only by academics in a closed room. Standards and public reporting stress involvement of practitioners, professional bodies, and community partners. Assessment is expected to give practical skills, competences, and attitudes a larger share of the grade (public summaries often cite at least about half the mark going to continuous, competence-oriented work): Monitor coverage of NCHE CBE rollout remarks.
NCHE's Dr Vincent Ssembatya has also urged universities to secure internship and work-integrated learning partners early, including formal MoUs with government agencies, industry, and private firms, and to scan the local ecosystem for placement sites: KFM: universities urged to secure internship partnerships. That warning matches what I see on the ground. A last-minute scramble for 200 placement letters produces weak supervision and thin evidence. CBE needs regular deployment sites, not a single ceremonial attachment letter in final year.
Step A: Map the local ecosystem
Start within a realistic radius of your campus. For Kampala-based computing programmes that may include banks, telecom and ISP operations, software houses, hospitals' IT units, NGOs with field systems, government registries, and serious SMEs that run real networks. Write four columns: organisation, possible student roles, modules that match, and a named contact. Include community organisations, not only glamorous multinationals. NCHE's own messaging stresses communities where the university sits.
At MUBS, the useful map is ugly and honest: some partners can take two students; some can take twenty; some will only review a curriculum outcome without hosting placements. All three have value if you label them correctly.
Step B: Formalise MoUs that name places and duties
A signed MoU with zero placement capacity is theatre. The document should state:
Approximate seats per semester or year
Supervision duties on both sides
Safety, insurance, and data-handling expectations
How student evidence (logs, demos, reports) will be reviewed
A renewal date
Keep a faculty register of live MoUs versus expired PDFs. Quality assurance should sample whether listed seats were actually used. That is closer to audit discipline than to marketing: planning and evidence habits from the IT/IS audit series.
Step C: Co-create a few module outcomes
Do not invite industry to a one-day "stakeholder workshop" that ends with a group photo and an unchanged syllabus. Pick two or three modules in a programme. Sit with practitioners and rewrite outcomes into observable performance. Example from computing teaching: "Explain encryption" becomes "Configure TLS on a small web service, show certificate checks, and write a one-page risk note for a non-technical manager." Example from information security: "List malware types" becomes "Isolate a suspect host on a lab network, capture basic indicators, and present containment steps in eight minutes."
Professional bodies and alumni mentors help when they speak to tools and failure modes students will meet in the first job, not when they only demand "more theory of the firm." Co-design also protects academic depth: practitioners flag missing workplace tasks; academics keep conceptual coherence and assessment fairness.
Step D: Work-integrated learning during the degree
Ssembatya's public remarks distinguish work-integrated learning during studies from traditional end-of-programme internships, and say institutions need both. Practical patterns that fit a computing faculty:
Live mini-projects: a partner supplies a sanitised problem (helpdesk queue design, basic hardening checklist, small dashboard). Students deliver under module deadlines.
Guest critique: a practitioner marks or co-marks one artefact using a shared rubric.
Short rotations: one or two weeks embedded where logistics allow, with a daily log and a short demo on return.
Community tech support: supervised support for a school or clinic network, with change records students can defend.
These tasks need campus labs that actually boot and an assessment design that values observed work: infrastructure checklist for AI and CBE and assessment redesign under AI pressure.
Step E: Assess with partners, then improve the ladder
Shared rubrics beat vague "industry exposure" marks. Agree what "competent" looks like for a junior role. Collect placement quality scores from students and supervisors every cycle. Close MoUs that never host. Deepen MoUs that give real tickets and honest feedback. Report numbers to the faculty CBE committee: seats offered, seats filled, supervised hours, artefacts co-marked, and graduate feedback where available.
Public reporting also notes large programme-review volumes as institutions realign (on the order of hundreds of programmes under review nationally). Linkage evidence will matter when regulators ask whether a programme can actually deliver work-integrated learning, not only whether the handbook mentions it: Monitor: NCHE reviewing about 700 programmes.
Faculty immersion: stop asking lecturers to teach a workplace they never see
CBE fails when facilitators only know textbook editions. Practical faculty habits:
Short industry attachments or collaborative applied projects during recess terms
Joint research or consultancy with clear teaching feedback loops
Practitioner-led CPD on current tools (cloud ops, SOC basics, payment systems, data protection practice)
This is not anti-academic. It is how you keep Unix, networking, and information security modules honest about what juniors are asked to do in Kampala workplaces.
Equity and community linkages
Gender and equity mainstreaming sits in NCHE's CBE focus areas for a reason. Placement systems that only reward students with personal laptops, airtime, and family contacts will widen gaps. Faculty responses that help: transport stipends where budgets allow, campus-based live projects for students who cannot travel far, clear anti-harassment contacts for placement sites, and community partners closer to student residences. Industry linkage without equity planning is a middle-class filter dressed as reform.
A 90-day linkage sprint for one computing programme
Weeks 1-2: Finish the local ecosystem map; name a linkage owner.
Weeks 3-5: Open or renew at least three MoUs with named seat counts.
Weeks 6-8: Co-rewrite outcomes for two modules with practitioners.
Weeks 9-11: Run one live mini-project and one guest critique; store evidence.
Weeks 12-13: Report seats, artefacts, and problems to the faculty CBE committee; schedule the next cycle.
If AI tools enter workplace tasks, govern disclosure and data rules so students do not paste partner data into public models: internal AI governance for Ugandan universities.
What success looks like for graduates
Success is not a press release about "launching partnerships." Success is a graduate who can show a portfolio of observed tasks, workplace logs, and module artefacts that a supervisor recognises as junior-ready work. Continuity from secondary CBE into tertiary CBE also matters for the incoming cohort: from O-Level to university under Uganda's competence reforms.
NCHE can mandate linkages. Only faculties that map employers, sign honest MoUs, co-write outcomes, host real tasks, and review the numbers will produce market-relevant graduates. That is the industry pillar of CBE as I practise and argue for it at MUBS.