Problem Solving
How better questions lead to better decisions
Important ideas often move forward because they sound convincing, not because the evidence is strong enough. The cost of that habit is familiar: time spent on the wrong build, budget committed before the question is clear, and teams arguing from different versions of the truth.
Genesis Nodes is built for that moment. It does not replace the decision. It makes the assumption, the evidence and the remaining uncertainty visible enough for people to judge what to do next.
Start with what you already believe
Most teams do not lack opinions. They lack a shared list of the beliefs the idea depends on. Until those beliefs are written down, evidence has nowhere to land.
Write the claim in one sentence. If the team cannot agree the sentence, they are not ready to gather evidence.
A useful first list
Ask only four questions at the start:
- Who is this for, and what changes for them?
- Can we deliver it with the capabilities we actually have?
- Is there a sustainable reason to fund it?
- Should we pursue it, and under what conditions?
Those questions map to desirability, feasibility, viability and responsibility. They stop a team from proving one attractive angle while ignoring the rest.
Then decide what would change your mind
Evidence is only useful if the team has already said what would strengthen or weaken the case. Otherwise people collect material that confirms the idea they already prefer.
A practical sequence looks like this:
- Name the assumption.
- Say what evidence would support it, and what would contradict it.
- Gather only that evidence.
- Record the gap as clearly as the finding.
If you want a fuller walkthrough of the product process, see
How it works. The site page is the public version of the same six stages.
Leave the judgement with people
The output should be something a decision-maker can interrogate: what is known, what is not, and whether the next step is to proceed, adjust, test or stop. That is the point of the Intelligence Curator. It structures the reasoning. It does not hide the uncertainty.
Technology strengthens judgement. It does not replace it.
If a recommendation cannot be traced back to the assumptions and evidence, it is not ready to publish. That rule is as useful inside a workshop as it is inside the product.