SIEN6004 Chap.3 Innovation Types and Strategic Fit
Innovation Types and Strategic Fit
This chapter uses Pisano's two-dimensional matrix to distinguish routine, disruptive, radical and architectural innovation. One axis asks whether technical competences are existing or new; the other asks whether the business model remains usable or must change. The classification is made from the perspective of a focal organisation and matters only when it changes governance, metrics, capability building or experimentation.
What this chapter covers
- 01
Technical competence axis
- 02
Business-model change axis
- 03
Routine and radical innovation
- 04
Disruptive and architectural innovation
- 05
Portfolio balance and organisational response
Worked example · free
Classify a subscription service
- +1Name the focal firm.
- +1Assess technical change.
- +1Assess business-model change.
- +1Draw the management consequence.
Key terms
- Architectural innovation
- Innovation requiring both new technical competences and a new business model.
- Routine innovation
- Innovation that uses existing technical competences and the existing business model.
Innovation Types and Strategic Fit FAQ
What are the matrix axes?
They are the degree of change in technical competence and the degree of change in the business model used to create and capture value for the focal organisation. Both axes must be supported with separate case evidence.
Can one innovation have different classifications?
Yes. Classification is relative to the focal organisation's existing competences and business model, so the same offer may challenge firms differently and require different structures. Always state whose existing position defines the comparison.
Why balance routine and breakthrough work?
Routine improvement maintains platforms, customers and cash flows that can support more uncertain radical or architectural exploration while preserving learning from current operations. Portfolio balance also protects organisational learning and option value.
How should a disputed classification be resolved?
Place the evidence for technical competence and business-model change in separate columns, then identify the single fact most likely to move the case into a neighbouring cell. Compare the management response before and after that move. If the recommendation remains identical, the classification may not be doing useful analytical work.
A sound answer connects the category to resource allocation, measures, team structure or experimentation while stating what the current evidence leaves uncertain.
Assessment move
Draw the matrix from memory, label the two axes and define all four cells without examples first. Then classify cases only after writing evidence for each axis. Always name the focal organisation because the same offer can be routine for one firm and architectural for another. Create a bank of original cases where only the business model changes, only technical competence changes, both change or neither changes substantially.
For each case, add a management implication concerning structure, measures, partners or experimentation. This final step stops the matrix becoming a vocabulary exercise. Apply the method to the semester project by asking which existing capabilities can be reused and which BMC blocks must change. Revisit the classification when the project uncovers a new technical dependency or a different payer, channel or revenue mechanism.
For portfolio understanding, place several initiatives on one matrix and explain the pattern rather than assuming variety is automatically good. Routine work can protect customer relationships and cash flows; more uncertain work can explore future capabilities and models. Before the theory quiz, practise a four-sentence answer: focal firm, technical evidence, business-model evidence and management consequence.
Before submitting project work, confirm that any use of disruptive refers to business-model change rather than excitement, popularity or market impact. Build fluency by classifying the same proposal from the perspective of three different organisations. Write the technical competences and business model of each focal firm before placing the proposal in the matrix.
This shows why a cell is relational rather than an intrinsic property of a product. For every classification, add the organisational problem it predicts: routine work may need disciplined execution, radical work needs technical learning, disruptive work needs protection from existing revenue logic, and architectural work must manage both forms of uncertainty.
Create a short evidence table for staff skills, assets, customer relationships, payer, channel, pricing and revenue. Do not let one dramatic fact determine both axes. Apply the matrix to the project whenever a new partner or revenue path is proposed, because those changes may alter the business-model diagnosis.
Compare the project portfolio with current capabilities and cash needs, then explain whether concentration in one cell is intentional. Before the quiz, practise concise classifications in which the final sentence recommends a measure or structure suited to the cell. Before the report, check that disruptive is never used merely to mean novel, successful or threatening.
Ask what evidence would move the proposal into a neighbouring cell and whether the team has designed a test for that uncertainty. Close revision by teaching the matrix aloud without named examples, then inventing a new example for every cell. That sequence verifies that the framework, rather than a memorised company story, is doing the analytical work.
Working through Innovation Types and Strategic Fit in SIEN6004? Sia is AskSia’s AI Management tutor — ask any SIEN6004 Innovation Types and Strategic Fit question and get a clear, step-by-step explanation grounded in how SIEN6004 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.