Where the first version takes you

The first version is never the answer. It is the question.

Every assignment that starts without a known destination begins the same way. An idea forms. It is not the result of analysis or certainty. It is a starting direction, the best available response to a brief, a problem, a space that needs filling. It feels like a solution. It is not. It is a door.

The discipline is to walk through it anyway.

Most people hesitate at the first version because it does not feel complete. It is not. That is the point. Completeness is not available at the start. The first version earns the second. The second earns the third. The thinking does not compound in the abstract. It compounds through the work of making something, showing it, questioning it and making something better.

The leader who waits for the right idea before starting will wait longer than the problem allows. The one who starts with the available idea and builds toward the right one will always arrive faster. The first version is not a draft of the answer. It is the mechanism by which the answer becomes findable.

Key Takeaway: The first version is not a draft. It is a discovery mechanism. The thinking that leads to the best idea cannot happen in the abstract, it happens in the process of making something, questioning it and making something better. Start with what you have. The right idea is on the other side of the work, not in front of it.

The first version is not the answer. It is the question that makes the answer possible.

Think Simple · Leadership · Here is How to Think · Vol 4: The Future · Philosophy 2: The Idea Behind the Idea · Section: Where the first version takes you

MarvinPro | December 2025

marvinpro.com

What the early versions do

Early versions do something the final version cannot do. They generate the questions.

The final version, by definition, has already answered them. It looks clean. It looks inevitable. It looks like the only reasonable outcome. But it is clean because the complexity was resolved, inevitable because the earlier versions failed in ways that pointed toward it, and reasonable because the questions it answers were only visible after the early versions raised them.

A stakeholder looks at version one and asks why a particular step exists. That question would not have come up looking at the final version, where the step no longer exists. A department responsible for executing the process flags a conflict with their existing workflow. That conflict only became visible because the early version made the workflow concrete enough to test against. A partner points out a dependency that was not in the brief at all. The brief did not include it because nobody knew it was relevant until the early version created the conditions to discover it.

None of these questions are answerable before the early versions exist. They are not available in the brief. They are not visible in the abstract. They are only visible through the work.

This is not a failure of the first version. It is its function. The early versions are not wrong answers. They are the instruments by which the right questions are found. Without them, the questions stay invisible. And an answer to an invisible question is not a solution. It is a risk that nobody is aware of yet.

Key Takeaway: Early versions surface the questions that only become visible when the work is made concrete. The questions are not a sign that the early versions failed. They are evidence that the early versions worked. Every question raised is a risk removed from the final result.

The early version does not answer the question. It finds it.

Think Simple · Leadership · Here is How to Think · Vol 4: The Future · Philosophy 2: The Idea Behind the Idea · Section: What the early versions do

MarvinPro | December 2025

marvinpro.com

The moment of direction change

At some point in any real creative or strategic process, a version arrives that shows you something the brief never described.

It is not the answer to the original question. It is a better question. The direction that produced it is not the direction that will produce the final result. And yet without the direction that produced it, the better question would never have appeared.

This is the moment most people resist most. The investment in the original direction feels real. The months of work, the stakeholder consultations, the documentation, the accumulated understanding of a path that is now being left behind. The cost of changing direction feels enormous because what was spent is visible and what is gained is not yet.

The calculation is wrong. What was spent was not wasted. It was the price of finding the better question. The versions that led here were not detours. They were the route. The new direction is not a correction of the old one. It is what the old one was always leading toward. The decision to change is not the moment the previous work is abandoned. It is the moment it pays off.

Change direction when the better idea appears. Not when it is certain, not when it is safe, not when everyone has been prepared for the change. Change when the idea is clearly better, because the longer the better idea waits, the more the lesser one hardens into something difficult to move.

Key Takeaway: The direction change is not a failure. It is the return on the investment made in every earlier version. The cost of changing is real and visible. The cost of not changing is less visible and much larger. Change when the better idea appears. The earlier versions made it possible. They have already done their job.

Changing direction is not the moment the previous work is abandoned. It is the moment it pays off.

Think Simple · Leadership · Here is How to Think · Vol 4: The Future · Philosophy 2: The Idea Behind the Idea · Section: The moment of direction change

MarvinPro | December 2025

marvinpro.com

How far to go

Version one starts the process. Version two continues it. The question that is never answered in the brief is when to stop.

The answer is not when the version looks good. Good is available long before the best idea appears. Most processes stop at good because good satisfies the brief, the stakeholder is ready to approve, the deadline is creating pressure and the team has been working on this longer than anyone planned. These are all real pressures. None of them are the right reason to stop.

Stop when the last version produced no new questions. Not when the questions stopped because the version was too vague to test, but when they stopped because the version was precise enough to test and nothing failed. When the stakeholder who always had a comment has no comment. When the department whose workflow was always in conflict finds no conflict. When the partner who always identified a missing dependency identifies none. That is when the version is ready. Not before.

The other signal is the direction change that produces no better idea after it. The change that reveals a new version, and that version raises no new questions, and no further direction change is visible from it. That is also when the work is done. The iteration has reached its natural end.

Most processes end before either of these signals arrives. The budget runs out, the schedule ends, the sponsor loses patience or the team loses energy. When any of these end the process, the result is whatever version happened to exist at that moment. Sometimes that version is the best one. More often it is a version that was still generating questions that nobody was left to answer.

The leader who understands this builds the iteration time into the plan deliberately. Not as contingency. As requirement. The process of finding the idea behind the idea has a minimum duration that cannot be negotiated away without negotiating away the result.

Key Takeaway: The right time to stop iterating is when the last version produced no new questions and no better direction is visible from it. Every stop that comes before that signal is a compromise. Sometimes the compromise is necessary. It should always be a deliberate choice, not a default.

Stop when the last version produces no new questions. Not before.

Think Simple · Leadership · Here is How to Think · Vol 4: The Future · Philosophy 2: The Idea Behind the Idea · Section: How far to go.

MarvinPro | December 2025

marvinpro.com

The complexity behind the simplicity

The best results look simple. They are not easy to produce.

The final version of something built through real thinking is lean, clean, precise. Every element is there for a reason. Nothing is there that does not need to be. A person who sees only the final version sees the result of the process, not the process itself. They see six weeks, not six months. They see the three steps, not the twenty decisions that reduced fourteen steps to three. They see the clean line, not the versions that were too complex, too direct, too cautious or too ornate before the right weight was found.

This creates a specific problem. The clean result makes the process that produced it look unnecessary. If the answer was always three steps, why did it take six months? The person who asks this question has seen the answer without the questions. They do not know that the three steps are three steps because the early versions revealed that four were redundant, two created conflict downstream, one required a dependency that did not exist, and three others were solving for the wrong constraint. The simplicity is the proof that the work was done, not the proof that it was unnecessary.

The leader who understands this does not apologise for the complexity of the process when presenting the simplicity of the outcome. They present both. The clean result deserves to be understood as the product of a process that earned it. The process deserves to be understood as the mechanism that produced a result that would not have been possible any other way.

Key Takeaway: Simplicity in the final result is evidence that the complex work was done, not that it could have been skipped. The clean outcome is the return on the messy process. Present both. The result is the answer. The process is the proof that the answer is right.

The clean result does not mean the process was unnecessary. It means the process was complete.

Think Simple · Leadership · Here is How to Think · Vol 4: The Future · Philosophy 2: The Idea Behind the Idea · Section: The complexity behind the simplicity.

MarvinPro | December 2025

marvinpro.com

A real example

A process design assignment. The brief was clear. The outcome it described was not.

Work began with a first version. It was logical, structured, sequential. It addressed the brief. It was also wrong in ways that were not yet visible, because the questions that would reveal what was wrong had not yet been asked.

Stakeholders reviewed the first version. Departments responsible for execution reviewed it. Partners who would interact with the process reviewed it. Each review raised questions that the brief had not contained. Some questions exposed gaps in the process. Some exposed conflicts with existing workflows. Some exposed dependencies that the brief had not mentioned because nobody knew they were relevant until the first version made them testable.

Version two addressed those questions. Version three addressed what version two revealed. By version four, the direction had changed entirely. The design that had been building on the original assumption was set aside. A new direction, visible only because of the work that had led to it, was started.

The final result was the leanest version of the process that could achieve everything the assignment required. It was clean enough that a person seeing it without context would not have imagined it took six months to produce. It was clean because six months had been spent finding every reason not to do it differently.

The early versions had not failed. They had done exactly what early versions are supposed to do. They had made the final version possible.

The final version was only possible because of every version that preceded it.

Think Simple · Leadership · Here is How to Think · Vol 4: The Future · Philosophy 2: The Idea Behind the Idea · A real example.

MarvinPro | December 2025

marvinpro.com

Chapter Outcome

Start with what you have. The first version is not the answer. It is the beginning of the process by which the answer becomes findable.

Do not wait for the right idea before starting. The right idea is not available at the start. It is available after the early versions have raised the questions that only the work can surface. Build the first version. Show it. Test it. Listen to the questions it generates. Build the second version. Repeat until the direction becomes clear.

When the direction changes, do not resist it. The change is the return on everything built before it. Change fast, without apology, without treating what was spent as a reason to continue in the wrong direction.

When the result is clean and simple, show the process that produced it. Not to justify the time. To demonstrate that the simplicity is real. A simple result that could have been produced without the process is a guess. A simple result that could only have been produced through the process is an answer.

The idea behind the idea is always better than the first idea. It is only reachable by going through the first.

Start where you are. The idea behind the idea is on the other side of the work, not before it.

Think Simple · Leadership · Here is How to Think · Vol 4: The Future · Philosophy 2: The Idea Behind the Idea · Chapter Outcome

MarvinPro | December 2025

marvinpro.com