From Richard: Innovation

Eighty-seven percent of new products fail. We celebrate the 13% as genius. We rarely autopsy the 87%. I’ve spent the last decade in that autopsy room, and I can tell you the cause of death is almost never a bad idea. It’s a profound misreading of the cognitive terrain.

Innovation isn’t a lightning strike of inspiration. It’s a forensic discipline. It begins with Pattern Recognition—the cognitive dimension dedicated to distinguishing signal from noise. Most people see noise. They see market reports, customer complaints, competitor moves, and call it chaos. The innovator sees the faint, repeating signal buried within. They see the why behind the what.

I saw it in the hiring data years ago. Companies were hemorrhaging talent, blaming “cognitive resonance.” That was the noise. The signal was a consistent mismatch between the cognitive demands of a role and the cognitive wiring of the person placed in it. They were trying to solve a resonance problem with a personality quiz. That pattern recognition became the bedrock of Morphic Fit. We didn’t build a better personality test. We built a Demand Signature analyzer for roles and a Cognitive Heat Map for people. The innovation was in reframing the entire problem.

But seeing the pattern is only the first act. The second is modeling its consequences, which requires Strategic Foresight. This is where most innovators stumble. They prototype a solution to the immediate problem without modeling the second and third-order effects. Will this new process create a bottleneck elsewhere? Does this efficiency gain erode a critical human connection? Does this solution work in Kingston and Kampala?

When we built Wukr Wire, our trade intelligence platform, the obvious solution was to aggregate data. But data aggregation is noise. The strategic question was: what cognitive dimension does a Caribbean agri-exporter or a West African manufacturer need to activate to navigate volatile supply chains? It’s Adaptive Reasoning—decision quality under novel conditions. Our platform isn’t just a data feed; it’s a scaffold for better Adaptive Reasoning, contextualizing signals against local infrastructure, policy shifts, and cultural business rhythms. We foresaw that flooding people with undigested global data would paralyze, not empower.

This is the work of the Architect archetype. The Architect doesn’t just have an idea; they build the system in which the idea can reliably operate. They think in frameworks, in load-bearing walls and cognitive plumbing. Building Morphic Fit was an Architect’s task—creating a methodology that others could use to build their own teams. The trap is to fall in love with the beautiful blueprint and forget the soil it must be built upon.

I learned this in a pitch meeting in Lagos. We had a elegant solution for matching tech talent. A local founder listened patiently, then said, “Your model assumes stable internet for the assessment. Our first filter is, can they get to a cybercafé with power?” The soil—the actual operating environment—demanded a different design. Innovation that ignores the cognitive and infrastructural reality of a market is just colonialism with a beta tag.

So, how do you innovate with rigor? Here’s what the data from thousands of profiles has taught me:

1. Start with the Demand Signature. Before you ideate, map the cognitive requirements of the problem space. What dimension is most taxed? Pattern Recognition? Execution Drive? Your solution must elevate that dimension.

2. Stress-Test with Foresight. For every feature or decision, ask: “And then what?” Model the consequences two steps out. If your innovation requires a Navigator archetype to operate it, but your team is full of Executors, you have a resonance problem baked in.

3. Build for the Soil, Not the Greenhouse. The most elegant framework is useless if it can’t withstand the ambient conditions—be they infrastructural, cultural, or cognitive. Test your assumptions in the messy reality of your target market.

The next time you see a wave of innovation in your sector, don’t just look at the product. Look for the pattern it’s responding to. Ask what consequence it’s ignoring. Ask yourself: Is this an Architect’s blueprint, or just a beautiful sketch?