Stop Calling It Youth Empowerment Until Young People Can Build Something Real

African technology events often end with a powerful photograph: rows of young people receiving certificates, organisers congratulating participants and speakers urging everyone to become innovators. Celebration matters. So does hope. But the more difficult question begins when the room empties.

What can those participants actually do on Monday morning? Do they have access to a device? A mentor who reviews their mistakes? A project they can demonstrate? A realistic path to earning income without misrepresenting their experience?

If the answer is no, we should be careful about describing a workshop as a completed employment solution.

The gap between learning a tool and solving a problem

A person may watch lessons about Python without ever cleaning a messy dataset. Someone may learn the words 'cloud architecture' without configuring permissions or recovering a failed deployment. A participant may build a beautiful design mock-up without asking whether an ordinary user can complete the task.

These are not failures of young people. They reveal a problem in how some training programmes define achievement.

Across East Africa, young builders work in many settings: universities, community groups, startups, public institutions and self-directed online communities. Their routes differ enormously. Rather than importing one fashionable curriculum for everyone, training should begin with the work people want to do and the resources they actually have.

A useful programme has three stages

First: foundations. Teach how to ask clear questions, test assumptions, protect information and communicate results. For a developer, that includes basic debugging and version control. For an analyst, it includes data definitions and checking numbers. For a designer, it includes accessibility and feedback.

Second: supervised application. Ask learners to tackle a realistic but safely scoped problem. They might create an appointment reminder for a community organisation using synthetic data, audit the accessibility of a public webpage, or prepare a transparent stock-tracking template for a small retailer.

Third: evidence and transition. Help participants document their decisions, explain their mistakes and present work to a reviewer. Provide references, realistic career guidance and connections to internships or paid projects where opportunities genuinely exist.

Certificates can recognise progress, but a certificate should never be used as a substitute for demonstrated skill.

Give people access to equipment and time

A training provider can offer free classes while leaving participants to pay for data, electricity and transport. That means free tuition does not necessarily equal equal access.

If a programme claims to welcome people from outside major cities, it should consider loan devices, offline learning materials, accessible training locations or travel support. These are budget decisions, not motivational slogans.

A credible initiative should also pay mentors for sustained attention where possible. An expert who spends an hour every week reviewing a learner's project can have a different effect from a famous speaker who gives one inspiring talk.

Measure results without making false promises

Counting registrations is easy. Measuring project completion, employment quality, repeat participation and the ability to explain technical choices requires more work.

Training organisations should publish clear definitions. A 'graduate' might mean someone who attended sessions, passed a knowledge assessment or completed a reviewed project. These are all potentially useful milestones, but they are not interchangeable.

Similarly, someone who receives a one-day freelance payment should not automatically be counted as having obtained a permanent technology career.

A 60-day community challenge

A community group could invite participants to choose one local problem that can be tackled lawfully and safely. The first two weeks are for interviewing stakeholders with consent and defining success. The next four are for building and testing a small solution. The final two are for documentation, demonstrations and independent feedback.

No one needs to release a commercial app. A well-documented prototype, verified spreadsheet workflow or accessible public-information page can be a strong achievement.

At the end, ask each participant to explain what failed and what they would change. Those reflections teach more than a perfectly edited promotional video.

A responsibility shared by employers

Organisations that complain about 'unemployable graduates' should examine their own hiring practices. Are junior roles truly junior? Can candidates show a portfolio instead of listing impossible years of experience? Is feedback clear? Are internships supervised and lawful?

A healthy talent ecosystem cannot depend entirely on young workers financing their own training while businesses demand finished professionals.

The question for our community: What small project, supervised by a real mentor, would teach more than the next certificate programme in your city?

ITBank Community Voices — editorial perspective. The programme described is a suggested model, not a claim that these outcomes have been achieved by a named organisation.