ENG5100 Chap.4 Innovation, Creativity and Problem Solving

Innovation, Creativity and Problem Solving

Innovation starts with a frame: what problem is being solved, for whom, within which boundary and according to which evidence. Frames highlight some causes and hide others. A request for a faster inspection tool can conceal a deeper coordination, trust or maintenance-planning problem.

Write the current frame and its assumptions before generating solutions.

Problem exploration combines observation, interviews, process data, incident evidence and stakeholder experience. Need statements should describe the user, circumstance and desired outcome without embedding a favourite technology. Ask what people currently do, where workarounds occur and which constraint produces consequence.

A loud request may be a proposed solution rather than the underlying need.

Divergent thinking produces meaningfully different options across technology, process, policy and business model. Premature evaluation converges on familiar ideas. Separate generation from selection, use analogies and constraint changes, and include a do-nothing or improve-current-system comparator.

More sticky notes are not valuable if every idea is one variant of the same frame.

Convergence needs explicit criteria linked to stakeholder value, feasibility, safety, strategic fit and adoption. Weighting can help structure discussion but can create false precision. Test whether the recommendation changes under defensible weights.

A critical safety or ethical criterion may be a threshold rather than a tradeable score.

A minimum viable experiment is the smallest ethical test that can reduce a decision-critical uncertainty. It is not always a minimum product. A mock workflow can test comprehension, a concierge process can test demand, a bench rig can test a technical limit and a simulation can test capacity.

Name the hypothesis, prediction, measure and stop rule.

Technical feasibility, desirability and viability interact. An accurate sensor can fail if alerts do not fit operator decisions. A desired service can fail if maintenance capability is absent. A profitable model can create unacceptable safety or equity effects.

Innovation evidence should connect the entire use system.

Worked pilot: sensors are installed successfully and detect anomalies, so the team declares success. Operators receive too many non-actionable alerts and create spreadsheets outside the system. The next experiment should measure alert precision, decision time, workload, escalation and prevented failure, while co-designing thresholds with operators.

Installation proves deployment, not value.

Adoption depends on relative advantage, compatibility, complexity, trialability, observability, trust and local champions, among other factors. These are hypotheses to investigate rather than a checklist guarantee. Procurement, training, incentives and data governance can dominate the technology.

Map who must change behaviour and what they need to believe or control.

Innovation governance includes portfolio fit and kill criteria. Continuing every pilot wastes capability and turns sunk cost into strategy. Record the assumption each experiment addresses, evidence obtained and decision: iterate, integrate, scale, pause or stop.

Stopping after disconfirming evidence can be a successful innovation outcome.

Creativity improves when constraints are examined rather than merely removed. Safety, regulation and physical limits can stimulate different architectures, while inherited organisational constraints may be negotiable. Classify each constraint as fixed, uncertain or assumed.

Generate options by reversing assumptions, changing scale, decoupling functions or shifting timing. Then reapply non-negotiable duties before experimentation.

An innovation portfolio should balance horizon, uncertainty and capability. Multiple small experiments can diversify learning, but fragmentation can exhaust operators and governance.

Define shared infrastructure, decision gates and a maximum burden on participating teams. Scale only when evidence is reproducible and the organisation can absorb the change without degrading current critical service.

Scale evidence should include repeatability beyond the pilot team and a credible owner for the capability once exceptional project support ends.

What this chapter covers

• 01

  problem frame

• 02

  divergent thinking

• 03

  minimum viable experiment

• 04

  move from a contested problem frame through divergent options, experiments and adoption evidence without confusing novelty with value

• 05

  Novelty, patentability or technical feasibility does not establish customer value, organisational fit or responsible adoption.

Redesign a sensor pilot

Key terms

problem frame

The selected description of what the problem is, for whom and within which system boundary.

divergent thinking

Generation of multiple meaningfully different possibilities before premature selection.

minimum viable experiment

The smallest ethical test capable of reducing a decision-critical uncertainty.

Innovation, Creativity and Problem Solving FAQ

Assessment move

Reconstruct one decision trace, challenge its strongest assumption, apply a changed stakeholder or risk condition and state the review trigger.

Working through Innovation, Creativity and Problem Solving in ENG5100? Sia is AskSia’s AI Engineering Management tutor — ask any ENG5100 Innovation, Creativity and Problem Solving question and get a clear, step-by-step explanation grounded in how ENG5100 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.