9 Programme Design Mistakes ThatCan Fail Cape Flats Communities

There is a particular kind of programme that looks excellent in a proposal.

The outcomes are clear.

The slides are polished.

The curriculum is complete.

The funder is satisfied.

Then the programme enters a real community and begins to struggle.

Attendance drops.

Participants arrive late.

Digital activities do not work as expected.

Recruitment takes longer.

Facilitators start adapting material on the fly.

The team concludes that the community is “difficult to engage”.

Sometimes the community is not the problem.

Sometimes the design failed to understand the community.

I am Cape Town based and Cape Flats rooted. My own journey through learning and development began as a participant before I became a practitioner, designer, team lead, programme leader and consultant. That progression has made one principle central to how I work:

Understand before you design.

What is Cape Flats programme design?

Cape Flats programme design means building learning, skills and community interventions around the actual people, places, barriers, strengths and opportunity pathways within Cape Flats communities. It is not a separate technical methodology. It is programme design that takes local context seriously enough to influence decisions.

That local context is diverse.

Mitchells Plain is not Bonteheuwel.

Bonteheuwel is not Khayelitsha.

Khayelitsha is not Athlone.

Even two neighbourhoods inside the same broader area may have different networks, transport patterns, community organisations and participant experiences.

Localisation begins when we stop treating “community” as a single category.

1. Designing before listening

This is the foundational mistake.

The programme begins with content rather than context.

Someone identifies a problem, chooses a curriculum and only then goes looking for participants.

Human-centred programme design reverses that sequence.

Before deciding what the programme should teach, ask:

• Who are the participants?
• What are they already doing?
• What do they want?
• What is getting in the way?
• What do they already know?
• What resources exist locally?
• What does opportunity look like after the programme?

This does not mean participants must design every element.

It means the programme should be informed by the people expected to live with its consequences.

The Western Cape Government’s Planet Youth initiative in Mitchells Plain offers a useful example of context-led thinking. It uses local data and community dialogue with families, caregivers, teachers and young people to shape responses rather than assuming one generic intervention will fit every area. Source: Western Cape Government

2. Treating the Cape Flats as one community

“The Cape Flats” is useful geographic shorthand.

It is not one lived experience.

A programme that works in one area may need adaptation somewhere else.

Different communities have different:

• transport routes
• local organisations
• schools
• faith networks
• employer access
• safety patterns
• languages
• digital access
• existing services
• social networks

A good programme design consultant in Cape Town should be uncomfortable with copy-and-paste delivery.

Consistency matters.

So does context.

The question is not “How do we make every site identical?”

It is:

What must remain consistent, and what must be allowed to adapt?

3. Ignoring transport and physical access

A programme can be free and still be expensive to attend.

Transport is part of programme design.

If a participant must spend money they do not have to reach a venue, that affects attendance.

If the final session ends after safe transport options become limited, that affects participation.

If a job interview is across the city, that affects progression.

The Western Cape Government has explicitly recognised transport cost as a barrier through its Getting YOU to Work programme. Participation has been especially strong in communities including Khayelitsha, Gugulethu, Mitchells Plain and Blue Downs. Source: Western Cape Government

This is an important reminder:

A “motivation problem” may actually be an access problem.

Good programme teams investigate before they label.

4. Assuming digital access means digital readiness

Many programmes have become more digital.

That can improve reach and flexibility.

It can also create exclusion.

Someone having a smartphone does not automatically mean they have:

• enough data
• enough storage
• a reliable device
• a quiet place to learn
• an email address they use confidently
• document-upload skills
• confidence with unfamiliar platforms

During COVID-19 restrictions, I worked with mobile-first WhatsApp micro-courses. The format was not glamorous. It was useful because it respected the access conditions participants were actually facing.

That experience stayed with me.

Technology should reduce friction.

If it creates more friction than the content, the delivery model needs attention.

5. Importing language and examples without localisation

Localisation is not adding a Cape Town photograph to an international workbook.

Examples carry assumptions.

Language carries assumptions.

Case studies carry assumptions.

A small-business exercise built around access to credit cards, stable connectivity, private transport or formal retail premises may unintentionally distance itself from participants whose businesses operate differently.

The answer is not to lower the learning standard.

It is to make the learning legible.

A good local example can help someone understand a global concept.

A bad example can make a simple concept feel foreign.

This is why Programme Localisation should be treated as design work, not cosmetic editing.

6. Recruiting participants without building trust

Recruitment is often treated as administration.

In communities, it is frequently relationship work.

Who is inviting people?

Do participants trust the organisation?

Do they understand what is being offered?

Have they experienced programmes that promised more than they delivered?

Does the recruitment message match the actual programme?

Community mobilisation should not oversell.

If a programme is training, call it training.

If it creates a pathway but cannot guarantee employment, say so.

Trust becomes fragile when recruitment language promises an outcome the programme cannot control.

The programme starts before the first workshop.

It starts with the first promise.

7. Under-resourcing facilitators

A facilitator can rescue a weak programme design for a while.

That can hide the design problem.

Good facilitators adapt examples, support participants, explain confusing content, manage difficult group dynamics and fill gaps in the material.

If the organisation depends on this invisible labour, the programme may look stronger than its systems actually are.

Then the facilitator leaves.

And the quality leaves with them.

Cape Flats community programmes often require facilitators to do more than present. They may become translators of context, relationship builders, problem solvers and bridges between participants and programme systems.

That work needs:

• preparation time
• local understanding
• clear resources
• realistic workloads
• support
• feedback channels
• facilitator development

Do not build “world-class” delivery on unpaid adaptation.

8. Treating training as the finish line

Training is an activity.

Opportunity is a pathway.

They are not the same thing.

A programme can teach entrepreneurship without creating market access.

It can teach work readiness without employer relationships.

It can teach digital skills without access to devices after the programme.

It can teach financial literacy without helping participants navigate the financial products or decisions they actually face.

Ask:

What does this learning connect to?

The answer may be employment, enterprise, further learning, mentorship, a network, another programme or a practical project.

If nothing sits after the training, participants may leave with more knowledge but no stronger route forward.

9. Measuring reach instead of movement

It is easy to report:

“300 people attended.”

It is harder to report:

“Here is what changed.”

That does not mean every community programme needs a complicated impact evaluation.

It means the measurement should match the claim.

If the programme promises skills, measure learning or application.

If it promises employability, measure progression indicators.

If it promises enterprise development, look beyond attendance.

If it promises confidence, define what that means and how it will be understood.

Reach is important.

Movement is more important.

What better Cape Flats programme design looks like

For me, better Cape Flats programme design begins with dignity.

Participants are not blank slates.

Communities are not problems waiting for outsiders to solve them.

Facilitators are not disposable delivery capacity.

Local context is not decoration.

A stronger process looks like this:

1. Listen
2. Understand
3. Design
4. Mobilise
5. Deliver
6. Enable
7. Connect
8. Measure
9. Learn
10. Improve
11. Scale

The sequence keeps the person visible.

It also helps organisations resist the pressure to rush straight from funding to delivery.

Sometimes the most important design decision is the one made before the first slide exists.

Related support

Explore Programme Design Consulting, Community Development Consulting and Programme Localisation.

For real programme evidence, see ReCha and Mishqah’s Community work.

Related reading: the nine signs a skills programme is measuring reach instead of impact.