Innovation Processes and Technology Management

Introduction and Context

Mechatronics projects combine mechanics, electronics, control, software, sensing, communication, and manufacturing. Their success therefore depends on more than technical performance. A technically elegant product may fail because it solves an unimportant problem, reaches the market too late, exceeds its cost target, or cannot be manufactured and supported reliably.

Innovation management provides a structured way to transform needs and opportunities into valuable products, services, processes, or business models. Technology management connects this creative process with decisions about technological capability, investment, intellectual property, suppliers, skills, timing, and risk. In mechatronics, these decisions are especially important because changes in one subsystem often affect the whole system. For example, changing a motor may require changes to the power electronics, controller, mechanical structure, thermal design, software, and safety assessment.

Innovation processes should not be understood as rigid linear sequences. They are controlled learning systems. Teams formulate assumptions, generate alternatives, test the most uncertain assumptions, review evidence, and allocate resources progressively. The frameworks in this chapter—design thinking, stage-gate, lean startup, open innovation, portfolio selection, technology roadmapping, cost–benefit analysis, risk assessment, and resource planning—support different parts of that process.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain how innovation differs from invention and routine improvement.
2. Apply design thinking and lean-startup principles to mechatronics opportunities.
3. Design stage-gate decisions and select suitable evidence for each gate.
4. Evaluate internal and external innovation using open-innovation principles.
5. Prioritize projects using portfolio, cost–benefit, and risk-analysis methods.
6. Construct a technology roadmap linking markets, products, and capabilities.
7. Plan resources while accounting for technical dependencies and uncertainty.
8. Recognize ethical, regulatory, intellectual-property, and cybersecurity implications.

1. Innovation as a Managed System

An invention is a new technical idea or device. Innovation occurs when an idea is implemented and creates recognized value. Value may be economic, social, environmental, operational, or scientific. A new robot prototype is an invention; a robot that is safely manufactured, purchased, used, maintained, and economically justified is an innovation.

Important types include:

• Product innovation: a new or improved robot, actuator, sensor, controller, or integrated system.
• Process innovation: a better assembly, calibration, testing, or maintenance method.
• Business-model innovation: a new way to deliver and capture value, such as robotics-as-a-service.
• Incremental innovation: improvement in efficiency, reliability, cost, or usability.
• Radical or discontinuous innovation: a substantial change in technology or application.
• Architectural innovation: rearrangement of relationships among existing components.

A useful systems perspective is:

This is a conceptual relationship, not a universal physical law. It emphasizes that a technically valuable idea has limited practical impact if users will not adopt it or the organization cannot deliver it reliably.

Innovation management must address three linked questions:

1. Desirability: Does a real user or organization need it?
2. Feasibility: Can it be built, operated, regulated, and supported?
3. Viability: Can it create sufficient value relative to its cost and risk?

These questions should be revisited throughout development rather than answered only at the beginning.

2. Design Thinking for Mechatronics

Design thinking is a human-centred approach to uncertain problems. A common formulation includes empathize, define, ideate, prototype, and test. The stages are iterative rather than strictly sequential.

Empathize and define

Teams observe users in their actual environment, conduct interviews, examine workarounds, and identify constraints. In industrial automation, for example, an operator may say that a robot is “slow,” while observation reveals that the actual problem is frequent fault recovery and difficult changeover.

A well-formed problem statement identifies the user, context, need, and constraint without prematurely prescribing a technology:

Small-batch assembly operators need to change product fixtures quickly and safely because current changeovers interrupt production and require specialist support.

Requirements should distinguish:

• Functional requirements: what the system must do.
• Performance requirements: how well it must do it.
• Constraints: limits involving cost, size, energy, standards, or environment.
• Quality attributes: reliability, maintainability, usability, safety, and cybersecurity.

Requirements should be testable. “The system must be user-friendly” is weak; “a trained operator shall complete fixture changeover in less than five minutes without tools” is more useful, provided the measurement procedure is defined.

Ideation and prototyping

Ideation generates alternatives before premature commitment. Methods include brainstorming, morphological charts, analogy, biomimicry, and function–means analysis. A morphological chart might list alternative methods for sensing, actuation, transmission, control, and user interaction.

A prototype is an instrument for learning, not necessarily a small final product. A cardboard mock-up can test access and ergonomics; a simulation can test control logic; a breadboard can test sensing; and a limited pilot can test workflow and adoption. Prototypes should be designed around explicit questions:

• What uncertainty is being investigated?
• What evidence will support or reject the concept?
• What is the cheapest credible test?
• What safety controls are required?

Design thinking is valuable when needs are ambiguous, but it can become superficial if teams produce ideas without measurable requirements, technical verification, or economic analysis.

3. Lean Startup and Evidence-Based Learning

Lean startup applies experimentation to uncertain products and markets. Its central cycle is build–measure–learn. A team identifies assumptions, builds a minimum viable product (MVP), measures relevant behaviour, and decides whether to persevere, modify the concept, or stop.

For mechatronics, an MVP is not automatically an unsafe or incomplete machine. It may be a restricted demonstrator, simulation, test rig, or human-assisted service that tests the most important assumption while protecting users.

An assumption should be expressed in measurable form. For example:

At least 70% of trained operators will complete a guided calibration task within ten minutes, with no more than one instruction request.

The team must define the sample, test conditions, success threshold, and decision rule before observing results. Otherwise, evidence may be interpreted selectively.

Useful measures include task time, error frequency, repeatability, willingness to pay, downtime reduction, energy consumption, and service-call frequency. Vanity measures—such as website visits without evidence of purchasing intent—should not determine engineering decisions.

Lean methods are strongest when uncertainty concerns user behaviour, workflow, or business assumptions. They do not replace formal verification, validation, safety analysis, or regulatory approval.

4. Stage-Gate Development

Stage-gate is a governance model that divides development into stages separated by decision gates. A typical mechatronics process is:

1. Opportunity discovery
2. Concept definition
3. Feasibility and proof of principle
4. Engineering development
5. Prototype verification and pilot validation
6. Production launch and post-launch review

At each gate, decision-makers review evidence and choose among go, hold, recycle, or kill. A gate should not be a ceremonial presentation. It should define entry criteria, decision authority, evidence, and consequences.

Stage-gate controls commitment, but excessive gates can slow innovation. Governance should be proportional to risk. A low-risk software interface may need a faster process than an autonomous mobile robot operating near people.

5. Open Innovation and Collaboration

Open innovation uses purposeful flows of knowledge across organizational boundaries. External knowledge may enter through suppliers, universities, customers, startups, standards bodies, or technology licensing. Internal knowledge may leave through licensing, spin-offs, partnerships, or complementary applications.

Open innovation does not mean sharing everything freely. It requires a deliberate boundary strategy:

• Define what knowledge is core and must be protected.
• Identify what can be acquired or co-developed.
• Establish confidentiality, ownership, licensing, and publication rules.
• Assess partner competence, reliability, cybersecurity, and supply continuity.
• Record interfaces and responsibilities clearly.

For example, a university may develop a novel tactile sensor while an industrial firm contributes packaging, electronics, testing, and market access. The collaboration succeeds only if performance claims, data rights, intellectual property, and integration responsibilities are explicit.

Intellectual property includes patents, designs, copyright, trade secrets, and know-how. Engineers should involve appropriate specialists before public disclosure because disclosure may affect patentability. Open-source software and hardware can accelerate development, but licenses create obligations that must be tracked in the product supply chain.

6. Portfolio Selection and Strategic Fit

Organizations rarely have enough resources to pursue every attractive project. Portfolio management considers projects collectively rather than ranking each project in isolation. A balanced portfolio may include short-term incremental improvements, medium-term platform projects, and high-risk exploratory opportunities.

A simple weighted-scoring model is:

Here, S_j is the score of project j, w_i is the weight of criterion i, and r_ij is the normalized rating of project j on criterion i. Ratings must use a defined scale, such as 0 to 5. The method assumes criteria are sufficiently independent and that weighted addition is an acceptable approximation.

Possible criteria are strategic fit, customer value, technical feasibility, regulatory readiness, expected return, sustainability, and time to impact. A high score does not guarantee selection. A project may be rejected because it consumes a scarce specialist, duplicates another project, or exposes the organization to unacceptable safety risk.

For financial analysis, net present value is commonly used:

I₀ is the initial investment, CF_t is the net cash flow in period t, r is the discount rate per period, and T is the analysis horizon. Cash flows and the discount rate must use the same time period. A positive NPV indicates value under the specified assumptions; it does not remove technical or strategic uncertainty.

A simple benefit–cost ratio is:

where PV denotes present value. Benefits and costs should include development, equipment, training, maintenance, energy, downtime, disposal, and compliance where relevant. Intangible effects should be identified separately rather than assigned unjustified precision.

7. Technology Roadmapping

A technology roadmap aligns three dimensions over time:

1. Market and societal needs: customer problems, regulations, sustainability expectations.
2. Products and services: offerings that address those needs.
3. Technologies and capabilities: components, algorithms, manufacturing methods, skills, and partnerships.

A roadmap exposes timing mismatches. A product launch may depend on a sensor that will not reach required reliability until a later date, or on a cybersecurity capability that the organization does not yet possess.

Roadmap development normally involves scanning the environment, identifying technology gaps, estimating maturity, defining milestones, and assigning owners. Technology readiness levels can support communication, but readiness is multidimensional. A component demonstrated in a laboratory may still lack manufacturability, maintainability, safety evidence, or supply-chain maturity.

Roadmaps should be living documents. They need trigger points such as competitor action, a regulation change, failure to meet a prototype target, or the availability of a substitute technology. Scenario planning is preferable to treating one forecast as certain.

8. Risk Assessment in Innovation Projects

Risk is commonly described as the effect of uncertainty on objectives. A risk register should state the cause, uncertain event, consequence, owner, response, and monitoring indicator.

A qualitative matrix classifies likelihood and consequence. A semi-quantitative priority number may be calculated as:

where L, C, and D are ordinal ratings for likelihood, consequence, and difficulty of detection. This is a screening device, not a probability law. Multiplication of ordinal scores can hide important differences; a catastrophic low-frequency hazard must not be dismissed merely because its numerical product is moderate.

For risks with credible probability and monetary consequence, expected monetary value is:

where p_k is the probability of scenario k, C_k is its monetary consequence, and the probabilities sum to 1 across mutually exclusive scenarios. EMV supports comparison under uncertainty but does not capture risk attitude, catastrophic harm, or distributional effects.

Mechatronics risk categories include technical integration, component obsolescence, supply interruption, cybersecurity, safety, regulatory non-compliance, schedule, cost, environmental impact, and user acceptance. Responses include avoiding, reducing, transferring, sharing, accepting, or exploiting risk. Safety risks require hazard analysis and engineered safeguards; they cannot be managed solely through insurance or warnings.

9. Resource Planning and Technical Dependencies

Resource planning translates a selected portfolio into people, equipment, time, budget, data, and facilities. A work breakdown structure decomposes deliverables into work packages. A responsibility assignment matrix clarifies who is responsible, accountable, consulted, and informed.

Mechatronics schedules must account for dependencies. Mechanical packaging may precede cable design; sensor selection may affect controller design; software integration may require stable interfaces; and environmental testing may require a near-final enclosure.

If activities form a critical path, the project duration is governed by the longest dependent sequence. Adding people does not automatically shorten it, especially when tasks require scarce expertise or communication overhead. Resource leveling may extend the schedule but produce a more realistic plan.

Budget planning should include contingency. A useful distinction is:

• Known costs: estimated from quotations or established rates.
• Contingency: allowance for identified uncertainty.
• Management reserve: controlled provision for unforeseen scope or events.

Resource decisions should also consider lifecycle capability. A prototype team may build a system that the manufacturing, service, or cybersecurity teams cannot sustain. Design reviews should therefore include downstream functions early.

10. Integrated Worked Example

Consider an illustrative project to develop an autonomous indoor transport robot for a hospital. The proposed value is reduced movement of supplies by nursing staff. The robot must navigate corridors, avoid people, deliver carts, and integrate with building access systems.

Background and problem

Interviews reveal that staff spend substantial time transporting routine items, but they are concerned about obstruction, infection control, and the effort required to recover a stalled robot. The initial idea—“build an autonomous robot”—is reformulated as a need for dependable, hygienic, low-interruption transport.

Analysis and concept alternatives

The team compares three concepts: a fully autonomous robot, a robot using fixed infrastructure markers, and a supervised robot with remote assistance. A weighted score uses customer value (0.30), technical feasibility (0.25), safety readiness (0.25), and implementation cost (0.20). Ratings are from 0 to 5.

For the supervised concept, the score is 0.30×3 + 0.25×5 + 0.25×4 + 0.20×4 = 4.00. This does not prove that it is the best final product. It indicates that it is a strong starting point for reducing uncertainty.

Lean experiment and stage gate

Instead of building a complete robot, the team uses a limited vehicle in a controlled hospital corridor with a trained remote supervisor. The experiment measures delivery completion, intervention frequency, near misses, cleaning time, and staff acceptance. A gate criterion is that at least 95% of scheduled deliveries are completed, no unacceptable safety event occurs, and median intervention time remains below an agreed threshold.

If results are poor because corridors are crowded, the team may modify the operating window, redesign human–robot signalling, or stop the concept. It should not simply increase the marketing claim.

Risk and business analysis

A risk register identifies collision, loss of communication, contamination, battery failure, and access-control failure. Technical controls include speed limitation, independent emergency stopping, obstacle detection, safe-state behaviour, battery monitoring, logging, and manual recovery procedures.

The business case includes robot cost, charging infrastructure, integration, training, maintenance, cleaning, and avoided staff time. Benefits must not be counted as full savings unless staffing or workload can actually be changed. A pilot may therefore be justified first as a capacity and service-quality project rather than solely as a labour-reduction project.

Outcome and learning points

The illustrative case demonstrates that innovation management changes the sequence of decisions. The team first validates the service problem, then selects a controllable experiment, integrates safety and operations early, and commits resources gradually. The final design may differ from the original autonomous-robot concept, but it is more likely to create usable value.

11. Ethics, Governance, and Contemporary Practice

Innovation decisions can distribute benefits and harms unevenly. Engineers should consider accessibility, worker displacement, surveillance, environmental impact, repairability, and the possibility that system errors affect vulnerable users. Data collected by connected machines must have a legitimate purpose, controlled access, retention rules, and appropriate protection.

AI-enabled mechatronics introduces additional concerns: biased training data, unpredictable edge cases, explainability, model drift, adversarial interference, and responsibility for automated decisions. AI should be treated as a component within a governed system. Validation must include representative operating conditions, failure modes, human override, cybersecurity, and monitoring after deployment.

Regulatory obligations vary by jurisdiction but commonly concern machinery safety, electrical safety, electromagnetic compatibility, radio equipment, data protection, occupational safety, and product liability. Compliance should be planned from the concept stage. A late compliance review may reveal that the architecture cannot meet required safeguards.

Sustainable technology management includes energy use, material selection, product lifetime, modular repair, remanufacturing, recycling, and supply-chain impacts. A product with excellent operating efficiency may still have poor overall sustainability if it is difficult to repair or depends on scarce materials.

Challenges and Limitations of the Frameworks

No framework eliminates uncertainty. Design thinking may generate attractive but technically infeasible concepts. Lean startup may overemphasize rapid experiments and underinvest in reliability. Stage-gate may become bureaucratic. Weighted scoring can create false numerical confidence. NPV depends on uncertain forecasts and discount assumptions. Roadmaps can become obsolete. Risk matrices may conceal low-probability catastrophic events. Open innovation can create intellectual-property and integration problems.

The appropriate response is not to abandon frameworks, but to make assumptions visible, use multiple forms of evidence, involve diverse expertise, and revisit decisions. Quantitative tools should support judgement rather than replace it.

Best-Practice Checklist

• Begin with a validated problem, not a preferred technology.
• State assumptions and define evidence before testing.
• Use prototypes to answer specific questions.
• Apply safety, cybersecurity, and regulatory thinking early.
• Make gate criteria explicit and proportional to risk.
• Balance short-term improvements with longer-term options.
• Treat intellectual property and data governance as design issues.
• Include manufacturing, service, users, and suppliers in reviews.
• Use financial models with sensitivity analysis and transparent assumptions.
• Maintain a living roadmap and risk register.
• Record rejected alternatives and the evidence behind decisions.

Chapter Summary

Innovation in mechatronics is the disciplined transformation of needs and opportunities into valuable, deployable, and supportable systems. Design thinking helps teams understand users and frame the right problem. Lean startup methods test uncertain assumptions through controlled experiments. Stage-gate governance manages progressive commitment, while open innovation provides access to external knowledge and capabilities.

Portfolio selection balances strategic fit, value, feasibility, risk, and resource constraints. Weighted scoring, NPV, benefit–cost analysis, and EMV provide useful decision support when assumptions and limitations are explicit. Technology roadmaps connect market needs with products and capabilities over time. Risk assessment and resource planning ensure that technical, safety, organizational, and lifecycle issues are addressed rather than postponed.

Effective technology management is therefore both analytical and interpretive. It combines evidence, engineering judgement, economic reasoning, ethical responsibility, and organizational coordination. The strongest innovation process is not the one with the most documents; it is the one that learns early, commits carefully, protects people, and delivers sustainable value.

Key Terms

Innovation: Implementation of an idea that creates recognized value.

Invention: A new technical idea, method, or device.

Design thinking: Human-centred, iterative problem-solving approach.

Minimum viable product: The smallest responsible offering or prototype that tests a critical assumption.

Stage-gate: Development process divided by formal evidence-based decision points.

Open innovation: Purposeful use of internal and external knowledge flows.

Portfolio management: Collective selection and balancing of projects.

Technology roadmap: Time-oriented link among needs, products, and technologies.

Weighted scoring: Decision method combining criterion weights and project ratings.

Net present value: Present value of future net cash flows minus initial investment.

Benefit–cost ratio: Present value of benefits divided by present value of costs.

Risk register: Structured record of risks, causes, effects, owners, and responses.

Expected monetary value: Probability-weighted monetary consequence across scenarios.

Critical path: Longest dependent sequence determining minimum project duration.

Requirements: Testable statements of system functions, performance, and constraints.

Verification: Evidence that a system meets specified requirements.

Validation: Evidence that the system meets its intended real-world need.

Intellectual property: Legally protectable creations, information, and know-how.

Technology readiness: Degree to which a technology has been demonstrated in relevant contexts.

Review Questions

Short Answer Questions

1. Distinguish invention from innovation using a mechatronics example.
2. What are the three dimensions of desirability, feasibility, and viability?
3. State the purpose of a stage-gate decision.
4. Why should an MVP for a physical system not compromise safety?
5. What information should a risk register contain?

Long Answer Questions

1. Explain how design thinking and lean startup can be combined in a robotics project.
2. Discuss the advantages and limitations of weighted-scoring models for portfolio selection.
3. Explain how a technology roadmap supports strategic technology management.
4. Compare internal development, supplier collaboration, and open innovation.
5. Discuss why lifecycle, regulatory, and ethical issues should be addressed early in mechatronics innovation.

Analytical / Application Questions

1. Construct a weighted-scoring model for three concepts for an automated inspection system. Select criteria, justify weights, calculate scores, and discuss limitations.
2. Develop a risk register for an autonomous mobile robot operating near workers. Propose technical and organizational responses for the highest-priority risks.
3. Prepare a stage-gate and experiment plan for a smart energy-monitoring device. Identify the riskiest assumptions, evidence required, gate criteria, and resource implications.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes innovation from invention?

A. Innovation is always based on a patented technology.

B. Innovation implements an idea to create recognized value.

C. Innovation is limited to scientific discoveries.

D. Innovation occurs only when a product is radically new.

Correct Answer: B. Innovation implements an idea to create recognized value.

Question 2

What is the primary purpose of an MVP in lean startup practice?

A. To represent the complete production design

B. To avoid all engineering testing

C. To test a critical assumption with limited resources

D. To maximize the number of product features

Correct Answer: C. To test a critical assumption with limited resources

Question 3

At a stage gate, which decision is normally appropriate when evidence is insufficient but the concept may be viable?

A. Automatically launch

B. Hold or recycle the project

C. Ignore the evidence

D. Increase scope without review

Correct Answer: B. Hold or recycle the project

Question 4

In the weighted-scoring formula, what does w_i represent?

A. The project cost

B. The rating of project j

C. The weight assigned to criterion i

D. The project completion time

Correct Answer: C. The weight assigned to criterion i

Question 5

Using weights 0.5 and 0.5, a project rated 4 and 2 on two criteria has a weighted score of:

A. 2

B. 3

C. 4

D. 6

Correct Answer: B. 3

Question 6

Which item is a technology-roadmap layer?

A. Market and societal needs

B. Employee attendance only

C. Office floor area only

D. Historical financial statements only

Correct Answer: A. Market and societal needs

Question 7

What does a positive NPV indicate under the stated assumptions?

A. The project has no technical risk.

B. The project is guaranteed to succeed.

C. The present value of net returns exceeds the initial investment.

D. The project requires no further testing.

Correct Answer: C. The present value of net returns exceeds the initial investment.

Question 8

Which limitation applies to a risk-priority number formed by multiplying ordinal ratings?

A. It is a physical law of failure.

B. It can conceal important differences between ordinal scores.

C. It cannot include consequence ratings.

D. It automatically captures ethical harm.

Correct Answer: B. It can conceal important differences between ordinal scores.

Question 9

Which activity is most consistent with open innovation?

A. Refusing all external technical knowledge

B. Using a university-developed sensor under a defined collaboration agreement

C. Sharing confidential designs without controls

D. Eliminating intellectual-property review

Correct Answer: B. Using a university-developed sensor under a defined collaboration agreement

Question 10

Why is adding personnel not guaranteed to shorten a mechatronics project?

A. All engineering work is independent.

B. Dependencies, scarce skills, and communication overhead may limit progress.

C. Personnel cannot work on prototypes.

D. Schedules are unrelated to resources.

Correct Answer: B. Dependencies, scarce skills, and communication overhead may limit progress.