How SkillHeart works: four pillars, one pathway

Four pillars described one after another are four boxes. What makes them a system is the route through them, so the route comes first.

Academy, Readiness, Labs and Network are not a menu of separate products to choose between. They are the four functions a single model needs in order to work: train, validate, practise, connect. The number stays at four because it describes how the model works rather than what happens to be on offer at any given moment.

The pathway

Stripped of the labels, the model runs through seven stages.

1. Discovery. Establishing where someone actually is and what they need, so that what follows is not generic.
2. Training. Building a specific, usable skill rather than a general introduction that has to be relearned properly later.
3. Practice. Using the skill, because a skill nobody has used is not yet a skill anyone can rely on.
4. Validation. Assessing the practice, because practice only counts for anything if it can be measured.
5. Verifiable experience. Producing something a third party can trust, which is the only reason validation matters.
6. Community. Turning a single credential into an ongoing set of relationships rather than a one-off transaction.
7. Opportunity. Professional or entrepreneurial, and what the six stages before it were building toward.

Each stage exists because the one before it is not enough on its own. Removing any of them does not shorten the pathway so much as break it.

The mistake worth naming is treating the pillars as optional additions to whichever one seems most valuable at the time, usually training. It is an understandable mistake: training is the most visible pillar, the easiest to package and the one most people already associate with closing a skills gap. But a pathway with training and community, and nothing in between to validate or apply what was learned, is not a shorter version of the model. It is a weaker one that happens to share two of its four parts.

The four pillars

Each of those stages has to be delivered by something, and that is what the pillars are for. They are set out here in the order the pathway meets them.

Academy

Academy is the training function: practical digital skills, AI-assisted workflows and the standards international teams use, built around employability rather than a stack of certificates. It is where the training stage happens, the point at which someone gains a specific, usable skill instead of a general introduction they will have to relearn properly later, on the job and under worse conditions.

What Academy needs before it can start is content: a curriculum, mentors and workshops built to a standard worth putting a name behind, rather than assembled quickly from material already available elsewhere for free.

Readiness

Readiness is the validation function: a way to measure and document what someone can actually do, so that ability does not depend on knowing the right person to vouch for it. Where Academy builds a skill, Readiness turns having learned something into something a company, a university or a mentor can check.

Breadth matters here more than producing a small number of highly specialised experts. The IFC estimated in 2019 that around 70% of the digital-skills jobs it studied in Sub-Saharan Africa would require only basic digital skills rather than advanced specialisation. Readiness is built around that shape of the problem: proving competence broadly and reliably, rather than certifying a handful of standout cases and leaving everyone else unaccounted for.

A readiness score is never an absolute truth and never a hiring guarantee. What Readiness needs before it can start is an assessment method that has been tested rather than designed on paper, because a score that turned out to be unreliable would damage trust more than offering no score at all.

Labs

Labs is the practice function: real projects in real teams, using the tools and workflows professional teams run on, covering the full cycle from problem research through design, build, testing and deployment, and then measuring whether any of it worked. This is where practice and verifiable experience happen together, because the evidence that matters is generated by doing the work rather than by describing it afterwards.

Labs needs real problems worth solving and teams capable of shipping them, which is a harder precondition than it sounds. A manufactured project teaches less than a real one, and the difference is usually visible from the outside.

Network

Network is the connective function: an international community linking talent, mentors, universities and companies, which is what turns the preparation built by the first three pillars into an actual opportunity. Without it, Academy, Readiness and Labs could each work and still leave someone with nowhere to take what they had built. It is also where the four kinds of partner the model depends on meet each other.

What Network needs is trust between the people on either side of it, and trust is not something a platform switches on. It is built relationship by relationship, which is slower than most models of this kind are willing to admit.

What each pillar needs before it starts

None of the four is waiting on the same thing, and that is worth saying plainly rather than folding it into a single vague promise of something coming soon. Academy needs content built to a standard worth publishing. Readiness needs a method that has been tested rather than designed. Labs needs real problems and teams able to deliver on them. Network needs trust, earned case by case.

One precondition is already met. Access to the tooling professional work depends on, including cloud infrastructure, AI tooling, observability, analytics and project management software, is in place rather than waiting on a later phase. Some of it the association pays for and the rest comes from technology providers that support the work. It is not a perk. Limited access to modern tools is one of the barriers named in the diagnosis this model answers, and it is also the thing a free course cannot match without money.

No dates are attached to the remaining preconditions. A date would imply a level of certainty about content, testing and trust-building that does not exist yet, and stating one would put a status ahead of where things actually stand. The programmes built on this methodology each carry their own status, kept current separately from this entry, because that list will change and the explanation of how the model works will not.

In short

• Academy, Readiness, Labs and Network are a method rather than a product catalogue. They exist to train, validate, practise and connect.
• A seven-stage pathway, from discovery through training, practice, validation, verifiable experience and community to opportunity, is what makes the four pillars one system instead of four boxes.
• Every pillar is in preparation and none is running yet. Each is waiting on a different precondition, and none of them carries a date.
• Readiness matters because a taught skill and a documented, verifiable skill are not the same thing, and the model proves competence broadly rather than certifying a small elite.
• Access to professional tooling is the one precondition already met, ahead of everything else described here.