The Architect’s Mindset: Deconstruction & The ‘Why’

Author

Mbiarrambang Alain

Published

March 9, 2026

Theme: “Why are we here?” & First Principles Thinking.

Welcome to the first session of the Solution Architect program. Before we write a single line of code, we must understand the landscape we are building for. In Africa, technology succeeds not because it is “advanced,” but because it solves a fundamental human friction.

1. The Philosophy: Code is a Tool

As a Solution Architect, your goal is not to write code; your goal is to solve problems. Code is merely the hammer you use to build the house.

We use First Principles Thinking—a mode of inquiry championed by innovators like Elon Musk. Instead of reasoning by analogy (“We should build an Uber for X because Uber worked in the US”), we reason from first principles:

  1. Identify the core truth (Physics/Reality).
  2. Deconstruct the problem into its fundamental parts.
  3. Reassemble a solution from the ground up.

2. The “Trust Gap”

PaveWay’s Mission

Why does PaveWay exist? We aren’t just a payments company. We are solving the “Trust Gap.”

In many African markets, commerce is friction-heavy because strangers do not trust each other.

Case Study: Architecting Trust

Question: Why does “Pay on Delivery” (PoD) exist and dominate African e-commerce?

The Lazy Answer: “People like cash.” The Architect’s Answer: “There is a lack of trust.”

Customers don’t trust that the goods will arrive. Merchants don’t trust that the customer will pay. PoD is a manual “Escrow” system where the delivery bike acts as the trusted middleman.

Architectural Challenge: How do we digitize this? A copy-paste solution from the US (Credit Cards) fails here because it assumes high trust. A Solution Architect builds Escrow Logic into the system: holding funds until delivery is confirmed. We architect for the context of low trust.


3. Exercise: The “5 Whys”

To solve a problem, you must find its root cause. We use the “5 Whys” technique.

Example: Traffic in Douala

  1. Why is there traffic?
    • Because cars are moving slowly at Bonaberi.
  2. Why are they moving slowly?
    • Because the road is narrow and full of potholes.
  3. Why is the road full of potholes?
    • Because heavy trucks use this road daily.
  4. Why do heavy trucks use this road?
    • Because it’s the only route to the Port.
  5. Why is it the only route?
    • Root Cause: Poor urban planning and lack of alternative logistics infrastructure.

Solution: Building a “Traffic App” won’t fix the potholes. The architectural solution might be logistics optimization or alternative transport modes, not just a navigation map.


4. Student Activity (1 Hour)

Step 1: Break into Pairs Identify one “Broken” system in your local community (e.g., Hospital waiting lines, School fee payments, Bus tickets).

Step 2: The 5 Whys Analysis Apply the 5 Whys to your chosen problem until you find the root cause.

Step 3: Draft a Problem Statement Do not propose a solution (e.g., “We will build an app”). Write a clear Problem Statement.

  • Bad: “People need an app to pay school fees.”
  • Good: “Parents spend 4 hours in line at the bank to pay fees because the school’s reconciliation process is manual and requires a physical receipt.”

5. Homework

Read: PaveWay’s “North Star” Manifesto (Executive Summary).

Task: Identify 3 technical architectural decisions PaveWay made based on the African context.

Continue Learning: The Napkin Architecture