15 January 2026
Summary:
Think smarter before you start
In this article, you’ll learn how Edward de Bono’s Six Thinking Hats can sharpen decision-making, reduce confusion, and unlock creativity in media training. We’ll apply the method to a real DBMoJo-style case: designing a pan-African media school that blends content creation, AI, and local ownership. Expect a practical framework, clear prompts, and a roadmap you can steal for your next project.
Content
What Six Thinking Hats means in Mobile Journalism
Mobile Journalism often runs on a fast rhythm: shoot → edit → publish. That speed is a gift — until it becomes a trap. When everything is urgent, teams default to familiar patterns, and “brainstorming” turns into a noisy carousel of opinions (with one person steering and everyone else hanging on).
The Six Thinking Hats method offers a simple reset. Instead of debating randomly, you guide the team through six modes of thinking, one at a time. It’s like switching camera lenses: the scene stays the same but meaning changes. And suddenly your project stops being a foggy idea and becomes something you can actually build.
In DBMoJo terms: it’s having six inner editors. One checks facts, one listens to emotions, one hunts risks, one spots value, one plays with wild ideas, and one keeps the whole production on schedule.
Don’t switch teammates when stuck — switch hats.
Why it matters for Africa-focused media training
Africa is not a single “context” — it’s a mosaic of languages, realities, infrastructures, and creative energy. Any training initiative that ignores that diversity risks becoming a well-intentioned suitcase full of tools that don’t fit the local locks.
That’s why thinking structure matters before curriculum structure. The hats help you avoid two classic mistakes: importing a ready-made model or staying stuck in endless discussion. The method forces balance: hope gets a microphone, risk gets a seat at the table, and facts stop being “vibes”.
Most importantly: it supports local ownership. If you run the hats with local voices leading the process, the “project for Africa” becomes “Africa building for Africa” — with smart allies, not external heroes.
Case study: DBMoJo School for Africa
Let’s imagine the goal: a bold initiative bringing together young creators from different African countries, training them in modern storytelling, mobile journalism workflows, and AI-assisted creation — with DBMoJo spirit: practical, joyful, professional, human-centred.
Idea: DBMoJo School for Africa — content creation + AI + DBMoJo mindset.
But here’s the real question: how do you shape it so it’s not just inspiring… but sustainable? How do you blend vision with local context, and energy with logistics?
You don’t start by writing a programme. You start by putting on hats.
White Hat: facts, data, information
White Hat thinking is the calm producer with a clipboard. No drama, no hype — just: What do we know? What do we need to know? What’s missing?
We know there is huge diversity in languages, economies, access to devices, and educational structures. We also know smartphone and internet adoption is growing fast — but unevenly — and that AI tools are becoming part of the global content workflow (whether we like it or not).
White Hat questions to ask before anything else:
🔹 Which countries/regions have the strongest local capacity to host and scale training?
🔹 What’s the real situation with connectivity, power supply, and device availability?
🔹 Who are the existing local trainers (Salesians + lay collaborators + media pros)?
🔹 What content formats dominate locally (Reels, WhatsApp video, YouTube, radio hybrids)?
🔹 What data do we need: internet penetration, social media usage, language distribution, cost of travel, safety?
White Hat output is simple: a short “project reality check” document. Without it, the project runs on enthusiasm alone — and enthusiasm is a great engine, but it’s terrible at accounting.
Red Hat: emotions, intuition, gut reactions
Red Hat is the heart in the room — and it matters. Because projects don’t fail only on budgets; they fail on trust, identity, and unspoken fears.
Here the team names what it feels — without needing to justify it. Excitement, hope, doubt, worry about cultural mismatch, fear of appearing “foreign”, desire for local voice, pride in the creative potential across the continent.
Red Hat truths worth saying out loud:
🔹 “This is big. It feels risky. But it feels necessary.”
🔹 “We don’t want to run a project about Africa without Africa leading it.”
🔹 “There’s a deep hunger for modern storytelling skills that don’t erase local identity.”
🔹 “This could empower a generation — if it stays human and contextual.”
Red Hat prevents a common leadership illusion: thinking everyone is “on board” just because nobody objects. Sometimes people stay silent not because they agree — but because they don’t feel safe to disagree.
Black Hat: criticism, risk, caution
Black Hat is the inner sceptic — the one who saves you from expensive optimism. Not to kill the idea, but to protect it from reality.
Risks to face early:
🔹 Connectivity issues and uneven access to devices / software
🔹 Language barriers (English, French, Portuguese, plus local languages)
🔹 A digital divide inside the group (some advanced, some beginners)
🔹 A “Western framework” that doesn’t fit local storytelling cultures
🔹 One-off workshops with no follow-up (training that evaporates)
🔹 Funding fragility and unclear long-term ownership
🔹 Local institutional complexities (permissions, leadership support, politics)
Black Hat output should become: a risk map + mitigation plan. If you can’t name the risks, you can’t manage them. And unmanaged risks don’t disappear — they just show up later wearing sunglasses and chaos.
Yellow Hat: potential, opportunities, hope
Yellow Hat is the sun on the storyboard. It asks: What’s the value? What becomes possible if this works?
The upside is huge. A pan-African DBMoJo school could create trainers who multiply skills locally. It can form a network that shares resources, supports peers, and builds a shared quality standard — without crushing local style.
Yellow Hat opportunities:
🔹 A first pan-African DBMoJo training pathway with trainers-of-trainers
🔹 Real skills: mobile video, design, storytelling, publishing, AI workflows
🔹 A self-driven network that keeps learning beyond the workshop
🔹 A new generation of media leaders who serve local youth culture in its own language
🔹 Cross-border collaboration: shared campaigns, shared formats, shared learning
Yellow Hat keeps the project from shrinking into “safe but small”. It reminds the team why the effort is worth it.
Green Hat: creativity, new ideas, out-of-the-box
Green Hat is the creative lab. It asks: What if we did this differently? It breaks the “traditional school” assumption and designs a model that fits real constraints.
Green Hat options for DBMoJo Africa:
🔹 Hybrid structure: local hubs + online mentorship (not everything needs travel)
🔹 A multilingual DBMoJo Toolkit: templates, prompts, lesson plans, micro-exercises
🔹 Open resource design: adaptable modules rather than one fixed curriculum
🔹 Mentorship network: external experts as allies, not stars of the show
🔹 Partnerships with media institutions for learning exchange (not dependency)
🔹 Micro-credentials / badges for modules (motivation + structure)
Green Hat is also where you design the “joy factor”. Because learning sticks better when it feels like building something — not surviving something.
Blue Hat: organisation, strategy, process
Blue Hat is the director calling “action” — and “cut”. It structures the thinking, assigns next steps, and turns hats into a timeline. And this is a practical roadmap:
🔸Phase 1 — Diagnosis
Local listening sessions + needs audit + mapping trainers and infrastructure.
🔸Phase 2 — Pilot
Hybrid training for a small cohort (e.g., 20 trainers). Starter kit + clear outcomes + feedback loop.
🔸Phase 3 — Network & Platform
Launch a pan-African DBMoJo community space: resources, peer review, joint projects.
🔸Phase 4 — Expansion
Scale via regional hubs, not one central location. Let it travel.
🔸Phase 5 — Evaluation & Co-Creation
After each cycle: local teams refine the next one. The programme evolves with the people, not above them.
Blue Hat is where good intentions become governance. Without it, you don’t have a project — you have a motivational poster.
FAQ
1) Can Six Thinking Hats work with multicultural teams?
Yes — it’s built for that. The method creates equal space for different styles of thinking, reducing dominance and confusion.
2) How long should a hats session take?
A focused session can work in 45–90 minutes. For complex projects, run several shorter sessions across phases.
3) Do we need to use all six hats every time?
Not always, but it’s recommended for big decisions. At minimum: White + Black + Yellow + Blue.
4) How do we avoid the “Western framework” risk?
Let local voices lead the process and co-create the model. Use the hats locally, not only in headquarters meetings.
One idea, six angles, one stronger plan.
Takeaways
In a world that screams ‘faster, more, louder’, De Bono’s hats whisper: “think smarter.” The Six Thinking Hats aren’t just coaching tools — they’re a mental map for clarity, creativity and collaboration.
We used the hats before planning the DBMoJo School for Africa. Because better projects start with better thinking.
For MoJo creators, it’s a way to shape sharper stories. For leaders — a method to make wise, inclusive decisions. For communities — a way to ensure every voice is heard, one at a time.
Edward de Bono didn’t just help people think more. He helped them think differently.
So put on your hat — and make space for lateral thinking. Stop digging in the same place. If there’s still no water… then it’s time to dig somewhere else.
#DBMoJo #MobileJournalism #DigitalMissionaries #ShapingTomorrow
Find us on Facebook and Instagram
Read more on our blog:
The Secret Ingredients of a Great Trainer
Push In – a Step into History
Speak Like a Leader
Pull Out Shot
Gen Styles
Dutch Angle