Insight Before Idea. Idea Before Execution.
11 July 2026 · 6 min read
Most of the money I have watched disappear on projects did not vanish during the hard part. It vanished at the very beginning, in a friendly room, when a good idea arrived before anyone had earned the right to have it. The idea was not the problem. The order was. We had reached for a solution before we understood what we were actually solving.
There is an order of operations that quietly protects a budget, and it runs in one direction only. Insight before idea. Idea before execution. Skip a step and you do not save time, you borrow it, and the interest is paid later in rework, in scope creep, and in the slow erosion of a team's belief that the plan was ever right.
Insight is a true thing you have understood. An idea is a thing you propose to build. Execution is the building itself. Do them in that order and money follows understanding. Do them backwards and you fund confidence instead of truth, which is the single most expensive mistake in the room.
An idea is cheap. The insight underneath it is not.
Anyone can produce an idea. Ideas are abundant, they arrive uninvited, and they feel wonderful because they carry the promise of action without the cost of it. Insight is different. Insight is the true thing you have understood about the audience, the market, or the problem, and it is found rather than invented. It takes listening, it takes admitting what you do not yet know, and it rarely announces itself in a meeting.
The trap is that an idea can be beautifully executed and still be wrong, because it was never anchored to an insight in the first place. I have seen teams ship a flawless answer to a question nobody was asking. The craft was real. The waste was total. When I work through this on podcasting projects, the pattern repeats: the format, the artwork and the schedule are all decided before anyone can say plainly why a listener would choose this show over silence.
The meeting that breaks the order
Here is where it usually goes wrong. A room fills up, the pressure to look decisive builds, and someone offers a confident idea. The energy shifts. Heads nod. The idea is now the centre of gravity, and every following minute is spent refining it rather than testing whether it deserved to exist. The quiet person who was still trying to understand the real problem has, without anyone meaning it, been overruled by momentum.
Meetings reward the person with the answer, not the person with the better question. That is the flaw. Insight work is slow, uncertain and slightly uncomfortable, and it does not perform well in a room that wants a decision by the end of the hour. So the group skips it, commits to execution, and calls the speed a win. It is not a win. It is a deferred bill, and the amount grows every week the wrong thing is built.
A day spent on insight removes weeks of building the wrong thing. The order feels slower in the meeting and much faster on the invoice.
How to protect the order in practice
The fix is not a longer process, it is a stricter sequence. Before anyone is allowed to propose an idea, insist on one plain sentence that states the problem in language a stranger would recognise. If the room cannot agree on that sentence, you are not ready for ideas, and every idea offered until then is a guess wearing the costume of a plan. Write the sentence on the wall. Let it be the thing an idea has to answer to.
I also separate the meetings on purpose. The insight conversation and the idea conversation should not share an hour, because the moment an idea appears the insight work stops. Keeping them apart is how I keep the work that survives a busy week from being crowded out by the work that merely feels urgent. Understanding first, always, even when the calendar disagrees.
Advisory and delivery, one system
This order is also how I keep advice and delivery honest with each other. My role is to help find the insight and pressure-test the idea before a cent is committed to execution. Then my team at TIM Africa builds it, and because the sequence was respected, they are building the right thing rather than a confident guess. The result is that execution stops being the stage where budgets go to die and becomes the stage where understanding finally pays off.
Questions people ask
What is the difference between an insight and an idea?
An insight is a true thing you have understood about the world or the audience. An idea is a proposed thing you might make. Insight is found, an idea is invented. The insight tells you whether the idea is worth building at all.
Why do meetings so often break this order?
Because meetings reward the person with the confident idea in the room, not the quiet person still asking what is actually true. Momentum feels like progress, so the group skips the uncomfortable insight stage and commits to execution far too early.
How do I know when I have enough insight to move on?
When you can state the problem in one plain sentence that a stranger would recognise, and when the people closest to the audience nod rather than argue. If the room is still debating what the problem is, you are not ready for ideas yet.
Does this order slow projects down?
It slows the start and speeds up everything after it. A day spent on insight removes weeks of building the wrong thing. The order feels slower in the meeting and much faster on the invoice.
Get the order right before the budget moves.
Strategy from me, delivery from my team at TIM Africa.