MDIA1007 Chap.7 Test Cycle Two: Evidence and Decisions
Test Cycle Two: Evidence and Decisions
Test Cycle Two takes the revised venture into a stronger evidence setting. The captured template requires a different critical assumption, five interviews and one additional experiment, while the toolkit specifies early-adopter participants. This chapter shows how interview meaning, observed action and experimental comparison can converge or conflict.
Conclusions remain bounded to the recruited people and conditions, and the final decision identifies what is supported, what remains unresolved and which next action the evidence has earned.
What this chapter covers
- 01
Early-adopter recruitment from hypothesis criteria
- 02
A different critical assumption for the second cycle
- 03
Five interviews that explain context and motives
- 04
An additional experiment that creates observable comparison
- 05
Triangulation without inflating weak signals
- 06
A bounded final venture decision
Worked example · free
Synthesising interest and a trust barrier
- +1Keep sources distinct: interviews support problem salience, attempts show behavioural interest and hesitation reveals a trust barrier.
- +1Apply the predeclared criterion to reservation behaviour without converting enthusiastic comments into extra actions.
- +1Continue in the tested niche while designing a clearer verified handover experiment and reporting trust as unresolved.
Key terms
- Test Cycle Two
- The Week Eight early-adopter cycle using five interviews and an additional experiment.
- Early-Adopter Criteria
- Recruitment conditions showing that participants experience the target problem with sufficient relevance or urgency.
- Additional Experiment
- A test beyond the interviews designed to produce behaviour or comparison relevant to the second hypothesis.
- Evidence Triangulation
- Comparison of methods that reveal different aspects of the same venture question.
- Bounded Conclusion
- A decision whose scope does not exceed the tested audience, behaviour and conditions.
Test Cycle Two: Evidence and Decisions FAQ
Who qualifies as an early adopter?
Use criteria derived from the problem and hypothesis, such as recent experience, frequency, urgency or an active workaround. Convenience and enthusiasm for the team are not enough. Record how each recruit meets the criteria so the report can explain why the evidence is relevant.
What should the additional experiment do?
It should answer a question that interviews cannot settle by themselves. The experiment might create a behavioural commitment or compare two versions while holding the audience stable. Choose it because it distinguishes plausible explanations, not because a preferred tool makes it visually impressive.
How should conflicting evidence be handled?
Preserve the conflict. Stated willingness and absent action may point to price, trust or timing barriers. Report what each method showed, decide which bears more directly on the tested assumption and design the next step around the unresolved gap rather than averaging everything into a positive sentiment.
Does Cycle Two have to support continuing the venture?
No. Continue, pivot again and stop are all defensible when the decision follows the stated criteria and evidence boundary. A negative or ambiguous result can demonstrate stronger entrepreneurial judgement than a positive claim built from weak signals. Explain what the cycle changed about confidence in the assumption, which result carried the most weight and what uncertainty remains.
The final recommendation should address the venture in the tested context, not reward the team for effort or predict an untested market future.
Assessment move
Start by proving that the second assumption is genuinely different from the first and follows from the version-two decision. Write recruitment criteria before contacting participants, then note how every interviewee fits them. Create an interview guide around recent behaviour and one additional experiment around an observable action or controlled comparison.
Use the same precommitment discipline as Cycle One: hypothesis, method, metric, support criterion and fail condition before results. During analysis, make a three-column table for interview meaning, observed behaviour and experimental result. Highlight convergence and conflict without converting all evidence into one score. Finish with a bounded claim naming the tested context, unresolved barrier and next action.
Draft the AT2 conclusion from this table so the final pitch cannot overstate the cycle. Build an eligibility checklist from recency, frequency, urgency and active-workaround criteria, then practise explaining why a convenient participant does or does not qualify. Invent one convergent and one conflicting set of interview and experiment results.
For each set, state which method bears most directly on the assumption and what remains unresolved. Write continue, pivot and stop conclusions using the same evidence, then reject the versions that exceed its boundary. End by transferring only verified facts into a one-page cycle record that can be used consistently across the report, pitch and prototype narrative.
Working through Test Cycle Two: Evidence and Decisions in MDIA1007? Sia is AskSia’s AI Management tutor — ask any MDIA1007 Test Cycle Two: Evidence and Decisions 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.
