Framework of Metacognition

"Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" - T.S. Eliot

"Think about yourselves and your lives. Logic would follow that to plan for a positive future - a future that you want - you need a clear understanding of where and what you are now.

That's how business works - the best businesses have a mission statement, a crystal-clear vision of what they want to achieve, but the only way they get there is through a clear understanding of where they are now, what resources they have, and what they're capable of. This allows them to strategise and, step by step, cater every decision to get them to where they want to be.

In the same way that businesses do this existential analysis of where they are, we need to do this, too.

We too need an understanding of where and what we are, what resources we have, and what we're capable of, so that we can prioritise and step-by-step get to where we want to be."

This quote from my TEDx talk explaining my line of business/personal thinking is the domain of metacognition: thinking about the way we think. And this knowledge of ourselves, our existence and our place within it, is explored in the topic of metaphysics. This refers to how you make the calls that shape your work and your life. Examined closely, we see that the most fulfilling decisions we make were those that were based on a clear understanding of what we found important at the time. By contrast, the less effective decisions were usually reactions to whatever was loudest at the time.

"What matters to me, and what evidence might change the direction I have chosen?"

There has always been noise. AI makes it possible to build, write and ship more than a team can meaningfully evaluate. I find it useful to make my filtering criteria explicit: what matters, what evidence I have and which assumptions I need to question. That is a working practice, rather than a promise that introspection alone will identify the right choice.

For me, fulfilment has often come from understanding what I find important and giving it a useful expression. That enquiry runs through my fiction books, The Proposition and The Meaning of Life. The Untold Story of Adam and Eve is the story within the latter. I organise my enquiry through five questions: Who am I? Where am I going? Why do I exist? How should I be? What should I do? They are a personal route into a large subject, rather than a reduction of all religion, spirituality or philosophy to one hierarchy.

"People don't buy what you do; they buy why you do it." - Simon Sinek

The Framework of Metacognition begins two questions deeper than the Why. The first is Who - the values and principles a person or company actually holds. The second is what formed the Who - the experiences - observations, lessons, problems, challenges - that inspired those values in the first place. The Why grows from both. The chain then continues through mission, strategy and execution - all the way to what actually gets produced. I have visualised this layout in the shape of a "tree" of knowledge. Soil and roots below the surface, the trunk and branches above it, and finally the fruits, the products and services that are the natural expression of everything beneath them. Through these seven layers, what a person builds remains connected to what they believe, and vice versa. This aligned approach to life is where I believe personal fulfilment and outer success comes from; to not be defined by what you do, but shaped by what you create.

Simon Sinek's Golden Circle theory (Why, How, What) is one influence on this approach: explaining a purpose can make a product story easier to understand. Customers also choose on practical grounds such as usefulness, price and trust. A coherent belief still needs a product that meets a real need.

These realisations are the backbone of this framework and, as such, form the way I make strategically-aligned product decisions. I've since outlined my AI-Native Product OS through this same first-principles derived approach - achieving systemic clarity in a rapidly evolving product and technology landscape.

I use this framework at personal and professional scales. For myself, it connects what I have experienced with what I choose to create. For a company, it can help trace a founding problem through values and strategy into a product. The analogy is useful without making the two situations identical. These seven layers are prompts to examine, with the examples below illustrating possible choices and intended outcomes.

Making the connections explicit helps me inspect and discuss a choice. When an output disappoints, I can examine its execution and then work back through the assumptions that shaped it. This is one diagnostic aid; it cannot identify a cause without customer, market and operational evidence.

I start by asking whether a decision serves the direction we intended. A product can drift because of execution, a mistaken strategy, changed market conditions or an assumption about customers that was never true. The investigation can change the tactics, the mission or the vision itself. The tree is a way to organise that inquiry, not a rule that the roots must always stay fixed.

A roadmap is an ordered list of what to build next, and an order is only as defensible as the criterion that produced it. Left implicit, that criterion defaults to whatever is loudest: the largest customer, the newest competitor, the most recent escalation. The framework makes the criterion explicit. An item's priority is how directly it serves the layer above it - traced up through strategy and mission to the vision, values, and founding problem beneath them. A roadmap built this way can be defended by derivation rather than by authority, because each item carries the reason it exists.

The framework also helps me explain what to cut: does the proposal serve the mission, and what evidence makes that worth pursuing now? Alignment does not settle the answer by itself. A customer need, delivery constraint or failed experiment may show that our strategy needs to change. I use the chain to make those disagreements inspectable, including the possibility that the direction is wrong.

The AI-Native Product Thesis is itself a worked example of this: it is structured and argued using the Framework of Metacognition, traced from a founding problem up to the product practice it proposes. If you want to see the chain applied end to end, read it next.

I return to Eliot’s question because collecting more information does not necessarily improve a decision. My aim is to make the purpose, assumptions and evidence easier to inspect, then revise them when reality disagrees. This method helps me hold that conversation; it does not establish a universal account of wisdom or guarantee fulfilment or commercial success.