Understand the work
Map the task, the working environment and what a useful improvement would look like.
OUR APPROACH
A defined problem, a considered concept and an agreed way to learn. We use these foundations to structure development conversations.
Map the task, the working environment and what a useful improvement would look like.
Explore the mechanical and control requirements against a clear project brief.
Agree what to observe, who will participate and how the findings will be recorded.
Review the results and define a realistic next stage, scope and responsibilities.
WHAT EACH STAGE SHOULD PRODUCE
What task matters? What constraints are fixed? Who owns the decision?
A concise, agreed problem brief.
Which concepts are worth considering? Which assumptions need checking?
A bounded development scope.
What will be observed? Who will record it? What conditions apply?
An evaluation plan and evidence record.
What did the evaluation establish? What is still unresolved?
A decision and proposed next-stage responsibilities.
COMMERCIAL CLARITY
Every application has its own level of uncertainty. A useful engagement defines deliverables, assumptions, responsibilities, timing and commercial terms before development starts.
Technical feasibility, demonstration availability and the extent of any support are discussed for the particular project. An initial enquiry does not commit either party to a delivery date or a result.
Read about planning a pilotLET’S DEFINE THE NEXT STEP