Bound the discovery
Agree on what we need to learn, and when to decide.
A brief that records the goal, scope, constraints, and decision owner.
THE METHOD / FROM QUESTION TO DELIVERY
A clear process makes a recommendation easier to assess. Here is how we define a task, test the difficult part, and agree on the evidence needed to accept the result.
FIVE WORKING RULES
Agree on what we need to learn, and when to decide.
A brief that records the goal, scope, constraints, and decision owner.
Try a small, focused test before a large build or purchase.
A test result, sample review, or feasibility finding with its limitations.
Separate evidence from assumptions. Record unanswered questions and who will resolve them.
A visible list of unknowns, dependencies, and reasons to stop or change course.
Write down what the result must do and how it will be checked.
Acceptance criteria agreed before implementation or supplier commitment.
Inspect the delivered artifact or the agreed evidence, not just a progress report.
A handover that states what passed, what remains open, and who operates it next.
THE SAME METHOD / TWO DIFFERENT JOBS
Illustrative sequences, not completed engagements or promised outcomes.
A team needs to find specific information across a set of documents.
COMMERCIAL STAGES
Understand technical requirements, resources, costs, and risks. Decide whether further work is justified.
Agree on architecture or sourcing requirements, responsibilities, fees, and acceptance criteria.
Deploy or coordinate delivery, hand over the work, and define any ongoing training or support.
A USEFUL NEXT STEP
We can start by identifying the assumption that needs testing first.
Start a conversation