MDIA1007 Chap.6 Pivots, Experiments and Version Two
Pivots, Experiments and Version Two
Week Seven asks students to recalibrate the venture, consider pivots and launch version two. This chapter distinguishes a strategic pivot from a cosmetic redesign and shows how supported, mixed or weakened evidence calls for different levels of change. A change ledger records what moved, what stayed constant and which result justified the decision.
Version two is framed as a new hypothesis for the second test cycle, not as proof that the revised direction already works.
What this chapter covers
- 01
Supported, mixed and weakened first-cycle evidence
- 02
Repairing a compromised test before abandoning a belief
- 03
Perseverance supported by evidence rather than sunk work
- 04
Pivots in audience, problem, channel or mechanism
- 05
Constants that preserve comparison between versions
- 06
A stronger behavioural signal for Cycle Two
Worked example · free
Narrowing a repair venture around urgent use
- +1Retain the grounded repair problem while recognising that urgency concentrates in commute failures.
- +1Shift the audience and benefit to commuters needing quick fault triage and a nearby availability check.
- +1Keep the explanation style and action tracking stable, then recruit participants who share the urgent context for Cycle Two.
Key terms
- Pivot
- A substantive evidence-backed change to an organising assumption about the venture.
- Perseverance
- Continuation of the current direction because the core belief retains support while another risk becomes the priority.
- Cosmetic Revision
- A surface change that does not alter the venture logic or address the evidence found.
- Change Ledger
- A record of the evidence, changed element, constant elements and new question across versions.
- Counter-Explanation
- A plausible alternative interpretation that a later test should distinguish from the preferred reading.
Pivots, Experiments and Version Two FAQ
What counts as a pivot?
A pivot changes an organising assumption such as the audience, problem, channel, revenue logic or solution mechanism because evidence weakened the earlier direction. A new colour palette or name is not a pivot unless visual identity itself caused the tested failure and the change addresses that finding.
When should a team persevere?
Continue when the core belief still has support and the next uncertainty can be isolated without changing the venture's organising logic. State the evidence that justifies continuation. Perseverance should not mean repeating the same weak test or defending features because the team already invested time in them.
Why record what stayed constant?
Constants make comparisons interpretable. If audience, offer, message and action all change together, a stronger response evaluates the new package but cannot identify which revision mattered. A change ledger protects the report from attributing an improvement to the team's favourite explanation without evidence.
Can a failed first test justify building a bigger prototype?
Only when the evidence shows that missing fidelity prevented the relevant behaviour from occurring. A bigger build is not an automatic answer to weak demand or an unclear niche. Identify the exact limitation, explain why additional fidelity removes it and retain a criterion that can still contradict the belief.
If the first test already presented the value and action clearly, expanding features may increase cost while avoiding the harder decision to revise the audience, proposition or venture direction.
Assessment move
Review Cycle One by writing three competing interpretations of the result. For each reading, identify the level of change it would imply: test repair, iteration, niche adjustment, solution pivot or stop. Choose the interpretation best supported by the combined observation and interview evidence, then write a fair counter-case. Build a version-two ledger with four rows: evidence, change, constants and next assumption.
Audit whether the revision makes the new question easier to answer. Practise distinguishing cosmetic movement from strategic change using product examples and your own prototype history. Before Week Eight, ensure the second hypothesis differs from the first and that recruitment targets the people for whom the revised problem is salient.
Treat version two as a testable claim, never as retrospective proof that the pivot succeeded. Draw a change ladder from test repair through iteration, niche shift, solution pivot and stop. Place three fictional findings on the ladder and defend the smallest change each one warrants.
For your venture, write a before-and-after claim with altered words highlighted, then connect every highlight to a specific observation or interview pattern. List the elements deliberately held constant so the next result remains interpretable. Finally, write the strongest argument against your chosen revision and identify what Cycle Two could reveal if that counter-case is right.
This turns a pivot from a dramatic announcement into an auditable evidence decision.
Working through Pivots, Experiments and Version Two in MDIA1007? Sia is AskSia’s AI Management tutor — ask any MDIA1007 Pivots, Experiments and Version Two question and get a clear, step-by-step explanation grounded in how MDIA1007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
