MGMT8005 Chap.4 Value-Function Taxonomy and Pattern Tests
Value-Function Taxonomy and Pattern Tests
The captured Week 2 framework distinguishes four kinds of business-model knowledge. Archetypes describe broad architectures. Patterns describe recurring multi-component mechanisms. Levers change one model component. Methods describe ways of working.
The taxonomy matters because digital-innovation proposals often promote a successful tactic, tool or company example to a “pattern” without demonstrating its causal structure or transferability.
If the idea is a lever, specify which component it changes and how it interacts with the rest of the model. If it is a method, explain what uncertainty it helps reduce. If it is a pattern, prove the five tests.
If it is an archetype, show the wider architecture and the patterns that operate within it. Accurate scope prevents inflated claims and directs evidence.
A lever can be the best strategic intervention even though it is smaller than an archetype. A method can unlock learning without creating value by itself. The taxonomy does not reward the largest label.
It helps the analyst choose the unit of analysis and avoid mixing a process, mechanism and whole model in one comparison.
Rewrite the proposal as a sentence with a subject and causal verb. “We will use subscriptions” claims a revenue-component choice and should be tested as a lever.
“A low-friction free tier generates usage learning that converts a defined segment into a premium service” claims an interdependent mechanism and may deserve pattern testing. “We will prototype the conversion boundary” names a method. “We will become a multilateral marketplace” claims a whole architecture. This translation prevents labels from outrunning evidence.
It also makes disagreement productive: reviewers can challenge the claimed scope, missing component or mechanism instead of arguing about terminology. When evidence is thin, retain candidate status and state what observation would support promotion or require reclassification. A narrow, well-supported claim is strategically more useful than an expansive category that hides the next decision.
Record the classification owner and review trigger.
An archetype captures a broad way that a business model creates, delivers and captures value. It may organise customers, assets, transactions and revenue through a recognisable architecture. Because it operates at high scope, it can contain several patterns, levers and methods.
The analyst should not treat a named company as the archetype or assume every instance has identical details.
A marketplace archetype, for example, coordinates distinct sides and typically needs discovery, trust, matching, transaction and governance. Its revenue may be commission, subscription or another mechanism; those variations do not erase the architecture.
Conversely, a company with a website and two participant groups is not automatically a marketplace if it buys inventory and resells as a retailer.
They allow a team to compare a product sale, subscription service, marketplace or outcome model at the architectural level. The comparison should cover value locus, core activity, scarce resource, risk, capture and control.
It can reveal that adopting an archetype would require capabilities and governance far beyond a front-end redesign.
Do not select it because a successful firm uses it. Test whether the target job, transaction, data, frequency, risk and participant behaviour support the architecture. If only one component transfers, classify that intervention as a lever or pattern instead.
This protects a proposal from copying scale-dependent economics into an unsuitable setting.
A retailer, marketplace and outcome service may address a similar customer job but organise risk differently. The retailer controls inventory and bears demand risk; the marketplace governs participant quality and matching; the outcome service assumes responsibility for performance and must influence use.
Compare the scarce resource, core decision, cash timing and failure owner in each architecture. This reveals the organisational change hidden by an archetype choice. Moving from sale to outcome is not a pricing edit if it requires monitoring, intervention rights and shared measurement. Moving to a marketplace is not a website edit if the firm must attract sides and arbitrate disputes.
The target should adopt the architecture only when its capabilities, transaction conditions and governance rights can support the new bottleneck.
A genuine business-model pattern is more than a repeated feature.
It combines several components whose interaction explains value creation and capture, recurs across industries, can compose with other patterns and cannot be reduced to independent levers without losing the mechanism. Those requirements make pattern claims falsifiable.
Suppose a model offers a free basic service and charges for advanced capability. Price tiers alone are not enough.
The pattern may require a low-friction entry proposition, a conversion boundary, cost structure, usage learning and a premium job that a subset values. Removing one component can break acquisition, conversion or economics. Show the dependencies with verbs and evidence.
Seeing the same move in several firms in one industry may reflect convention or shared regulation.
The captured test requires recurrence across at least three industries. The analyst should compare the mechanism, not merely the label. Different pricing language can express the same pattern, while the same word “freemium” can hide different causal structures.
A pattern that explains adoption but not capture is incomplete. A referral loop may acquire users, yet the model still needs a viable value and revenue path.
Conversely, a fee is not a pattern unless connected to value creation and behaviour. State who gains, why the configuration changes action and how resources return to sustain it.
Use rows for industries and columns for actor, contribution, value change, capture and necessary components. A genuine cross-industry claim should preserve the causal verbs even when the objects differ.
For example, a participation mechanism might lower acquisition by giving an existing user a reason to invite a new user who receives immediate value; capture follows only if the enlarged use creates sustainable revenue or lower cost. If one industry relies instead on paid advertising or regulation, surface similarity should not count as recurrence. Include at least one near miss.
Counterexamples help specify the pattern's boundary and prevent a universal claim. The matrix should also record whether removal of each component changes creation or capture, making non-decomposability observable rather than asserted.
What this chapter covers
- 01
Archetype
- 02
business-model pattern
- 03
lever
- 04
method
- 05
non-decomposability
- 06
composability
- 07
Evidence, alternatives and governance
- 08
Original worked application and chapter synthesis
AskSia-authored practice weighting (not an official mark scheme): Value-Function Taxonomy and Pattern Tests
- 2 AskSia pointsDefine the focal decision and apply Archetype precisely.
- 2 AskSia pointsUse evidence to test business-model pattern rather than assert the label.
- 2 AskSia pointsTrace the mechanism through lever and the affected actor.
- 2 AskSia pointsCompare the nearest alternative and state a boundary using method.
- 2 AskSia pointsRecommend a bounded next decision with owner, validation, counter-metric and stop rule.
Key terms
- Archetype
- A broad business-model architecture that may contain several patterns, levers and methods.
- business-model pattern
- A recurring, cross-industry, interdependent configuration that creates and captures value.
- lever
- A deliberate change to one business-model component with system consequences.
- method
- A way of investigating, designing or implementing rather than a value mechanism itself.
- non-decomposability
- The condition that a pattern loses its mechanism when separated into independent choices.
- composability
- The ability of a pattern to combine with other patterns in a wider business model.
Value-Function Taxonomy and Pattern Tests FAQ
What does Archetype mean in this guide?
A broad business-model architecture that may contain several patterns, levers and methods.
What does business-model pattern mean in this guide?
A recurring, cross-industry, interdependent configuration that creates and captures value.
What does lever mean in this guide?
A deliberate change to one business-model component with system consequences.
What does method mean in this guide?
A way of investigating, designing or implementing rather than a value mechanism itself.
What does non-decomposability mean in this guide?
The condition that a pattern loses its mechanism when separated into independent choices.
What is the nearest mistake to avoid?
Do not use Value-Function Taxonomy and Pattern Tests as a label detached from actor, action, evidence and outcome. Apply the chapter's mechanism and state what would change the conclusion.
Are the worked examples official Macquarie questions or marking schemes?
No. They are independently authored AskSia learning drills. The 10 points are an AskSia planning scaffold, not official marks, questions, answers or rubric criteria.
How should this chapter be used in assessment work?
Verify the current iLearn brief, use company-specific evidence, apply only the concepts that explain the mechanism and preserve individual or group authorship required by the task.
Assessment move
Patterns may compete for the same data, attention, trust or operational capacity. A referral loop that maximises invites can degrade a curated network. A usage-based capture mechanism can discourage the behaviour needed for data learning. Map shared scarce resources and feedback before recommending a portfolio.
Assign owners and measures to the combined model, not only each pattern.
Monitor whether local optimisation damages overall value creation or capture. A portfolio decision should include stop, adapt and rollback triggers because interaction risk appears only after composition.
Draw the participant action encouraged by each mechanism and identify whether the actions reinforce or compete.
A free tier may increase demand and data, but if it also raises low-quality supply, marketplace trust can fall and premium conversion can weaken. The data-learning loop may improve ranking, yet sellers may perceive the ranking as opaque and multi-home.
Assign a measurable outcome to the combined system, such as successful trusted matches, rather than letting each team maximise sign-ups, model engagement or conversion separately. Stage the composition so one interaction can be observed at a time. Rollback should preserve participant records and rights.
Composition succeeds when the mechanisms remain individually defensible and jointly improve the model without shifting hidden costs to a weaker side. Include one distributional counter-metric.
Classify the candidate at the smallest defensible scope. If it claims pattern status, test all five criteria with mechanisms and counterevidence.
Explain how it fits the target business model and interacts with other patterns or levers. Finish with an evidence-generating next decision, not a promotional conclusion.
The taxonomy tells the team what kind of business-model idea it is evaluating. It does not yet test whether strategy, model and organisational capacity are aligned.
The Spartan Stance chapter treats nine dimensions as an integrated profile and diagnoses imbalance through causal symptoms rather than chasing a high score on every axis.
If a candidate fails a gate, state the best remaining category and revise the recommendation. A failed non-decomposability test can yield a portfolio of levers that should be tested separately.
A failed recurrence test can yield an industry-specific configuration whose local evidence remains valuable. A method can be retained to reduce uncertainty without being credited with value creation. This move protects both analytical honesty and practical momentum.
End with a proof plan proportionate to the category: architecture coherence for an archetype, five-gate mechanism evidence for a pattern, behavioural and system consequences for a lever, or inference validity for a method. The category should make the next decision clearer, not merely tidy the vocabulary.
Before closing, state the unit of analysis, strongest passed test, weakest or unknown test, target-context adaptation and stop condition. Those five statements make the reasoning auditable and stop the synthesis from collapsing back into promotional pattern language. Cite the evidence state for every gate.
Working through Value-Function Taxonomy and Pattern Tests in MGMT8005? Sia is AskSia’s AI Management tutor — ask any MGMT8005 Value-Function Taxonomy and Pattern Tests question and get a clear, step-by-step explanation grounded in how MGMT8005 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
