Inn0v8

Agree the objectives, scope, and measures of success with relevant stakeholders.

1. 1.1

   Kick-off meeting

   Bring together the relevant stakeholders and departments.

2. 1.2

   Define objectives and scope

   Establish the intended outcomes, project boundaries, and measures of success.

3. 1.3

   Circulate for comment

   Share the objectives and scope with relevant stakeholders, gather feedback, and refine them.

4. 1.4

   Sign off objectives

   Obtain agreement on the project objectives and scope.

Review internal knowledge and external research, then amend the objectives where necessary.

1. 2.1

   Internal research

   Review existing knowledge, previous work, resources, and capabilities relevant to the objectives in 1.4.

2. 2.2

   External research

   Investigate user needs, industry developments, competing solutions, and available technologies.

3. 2.3

   Amend objectives if necessary

   Use the research findings to revise the objectives and scope agreed in 1.4. Obtain renewed agreement where changes are made.

Break the project into systems, detail and sign off their requirements, and define the market approach.

1. 3.1

   Break the project into systems

   Identify the main systems that make up the proposed product or solution.

2. 3.2

   Define broad system requirements

   Establish high-level requirements for each system using the objectives agreed in 1.4, including any revisions agreed in 2.3.

3. 3.3

   Detail and finalise system requirements

   Hold a design requirements meeting with relevant stakeholders to detail the requirements from 3.2, including system interfaces and measurable acceptance criteria.

4. 3.4

   Sign off design requirements

   Obtain approval of the requirements finalised in 3.3 for each system.

5. 3.5

   Define the market approach

   Identify intended users or customers, target markets, positioning, marketing tools, and the proposed launch approach, informed by the research in Step 2.

Generate and compare system concepts, select one solution, and justify its fit with organisational capabilities.

1. 4.1

   Generate ideas for each system

   Explore possible ways to meet the system requirements signed off in 3.4.

2. 4.2

   Form concepts

   Combine ideas into coherent concepts, considering how the systems will work together.

3. 4.3

   Screen and shortlist concepts

   Compare concepts against 3.4 and select two or three promising options where practical.

4. 4.4

   Develop concept representations

   Use basic 3D models, sketches, mock-ups, or equivalent representations to establish the layout and operation of the shortlisted concepts.

5. 4.5

   Evaluate and select one concept

   Compare the concepts against the objectives in 1.4, as revised in 2.3, and the requirements in 3.4. Select the preferred concept.

6. 4.6

   Justify the selected concept

   Document why the concept selected in 4.5 is suitable, including its fit with the organisation's delivery, operational, and support capabilities.

Develop systems and subsystems, reduce design risks, select standard items, and compile the design records.

1. 5.1

   Break systems into subsystems

   Develop the selected concept from 4.5 into subsystems, defining their functions and interfaces within the systems identified in 3.1.

2. 5.2

   Assess and reduce design risks

   Conduct a risk assessment and eliminate or reduce risks through design. Revisit the assessment as the design develops.

3. 5.3

   Complete the detailed design

   Develop each system and subsystem according to the requirements signed off in 3.4, incorporating the risk controls identified in 5.2.

4. 5.4

   Specify standard items

   Identify suitable off-the-shelf components or other standard elements required by the detailed design.

5. 5.5

   Confirm availability

   Check the availability, lead times, and suitability of the items selected in 5.4. Revise selections or the design where necessary.

6. 5.6

   Check the final design

   Verify that the detailed design meets the requirements signed off in 3.4 and resolve identified gaps.

7. 5.7

   Compile the design summary

   Document the design approach, key decisions, and how the systems and subsystems work together.

8. 5.8

   Compile technical specifications

   Record the solution's technical characteristics, performance, and operating limits based on the design reviewed in 5.6.

Where required, build and test prototypes against the agreed requirements, refine them, and repeat.

1. 6.1

   Define prototype requirements

   List the detailed requirements to be assessed, based on 3.4 and the uncertainties or risks identified during Step 5.

2. 6.2

   Define the test scope and boundaries

   Identify the physical items, systems, subsystems, and test conditions needed to assess the requirements in 6.1.

3. 6.3

   Develop the prototype model

   Build a 3D model or equivalent representation using the detailed design from Step 5 and the prototype scope defined in 6.2, where required.

4. 6.4

   Review the prototype model

   Check the model against the applicable requirements in 3.4 and the prototype requirements in 6.1.

5. 6.5

   Prepare prototype fabrication drawings

   Complete the drawings and supporting build instructions using the reviewed model from 6.4, or the detailed design from Step 5 where no prototype model is needed.

6. 6.6

   Build the prototype

   Fabricate and assemble the prototype according to the drawings and instructions prepared in 6.5.

7. 6.7

   Test the prototype

   Evaluate it against the requirements in 6.1, within the conditions defined in 6.2, and record the results.

8. 6.8

   Approve or refine

   Use the results from 6.7 to approve the tested system, subsystem, and concept, or incorporate changes and repeat the relevant activities in 6.3 to 6.7. Update the affected design records and specifications in Step 5.

9. 6.9

   Repeat for each prototype

   Apply 6.1 to 6.8 to each additional prototype required.

Finalise designs and models, record residual risks, and complete the documentation needed for delivery.

1. 7.1

   Finalise the solution definition

   Complete the final designs, models, specifications, or process descriptions from Step 5, incorporating the approved changes from Step 6 where applicable.

2. 7.2

   Complete the final risk review

   Update the assessment from 5.2 for the final solution in 7.1. Record residual risks in a risk register or matrix, including controls and responsible parties.

3. 7.3

   Prepare delivery documentation

   Complete the drawings, build instructions, deployment details, or equivalent information needed to reproduce or deliver the final solution defined in 7.1.

Finalise specifications, confirm readiness, prepare support and marketing materials, and hand over.

1. 8.1

   Finalise specifications and project summary

   Update the design summary from 5.7 and technical specifications from 5.8 to reflect the final solution in 7.1, and obtain the relevant approval.

2. 8.2

   Conduct a stakeholder readiness review

   Review the final solution and documentation from Step 7 with relevant departments. Confirm operational readiness, responsibilities, and management of the residual risks recorded in 7.2.

3. 8.3

   Prepare user and support information

   Complete applicable installation, operating, and maintenance instructions, spare parts or supporting resource lists, and relevant precautions identified in 7.2.

4. 8.4

   Prepare marketing and training materials

   Develop brochures, demonstrations, videos, or training content using the market approach from 3.5 and the final information from 8.1 and 8.3.

5. 8.5

   Publish and hand over

   Store the approved documentation and materials from Steps 7 and 8 in the appropriate systems, and complete the handover to the responsible teams.

Set rollout targets, assign responsibilities, identify initial customers or users, and begin sales or implementation.

1. 9.1

   Set rollout targets

   Define initial sales, adoption, or implementation targets using the objectives from 1.4, as revised in 2.3, and the market approach from 3.5.

2. 9.2

   Assign responsibilities

   Confirm ownership of sales, rollout, and initial customer or user support, building on the handover completed in 8.5.

3. 9.3

   Identify initial customers or users

   Select the first audiences in line with the market approach in 3.5 and the targets in 9.1.

4. 9.4

   Plan introduction activities

   Identify suitable channels, demonstrations, events, or direct engagement for the audiences in 9.3, using the materials prepared in 8.4.

5. 9.5

   Begin sales or implementation

   Introduce the solution once the readiness review in 8.2 and handover in 8.5 are complete. Track progress against 9.1 and capture initial feedback.