MDIA1007 Chap.5 Test Cycle One: Observe and Interview
Test Cycle One: Observe and Interview
Test Cycle One takes place in Week Five and uses observation and interviews to close the first Build-Measure-Learn loop. The course notes that participants may not be early adopters, which limits demand claims but still allows valuable usability and comprehension learning. This chapter keeps observed behaviour, participant explanation and team interpretation separate.
It shows how to complete the first test card, preserve a predeclared decision rule and turn mixed feedback into a specific version-two change without erasing inconvenient evidence.
What this chapter covers
- 01
Test Card One planning before participant sessions
- 02
Neutral observation of pauses, errors and abandonment
- 03
Follow-up interviews about expectations and current behaviour
- 04
Outcome separated from analysis and limitation
- 05
Audience boundary when classmates are not early adopters
- 06
A traceable next step for Week Seven
Worked example · free
Interpreting a button nobody chooses
- +1Record the behaviour: participants reached the action area and did not select it. Do not label that as rejection of alerts.
- +1Add the explanation: inconsistent expectations show a communication problem that compromises the current demand test.
- +1Relabel the action as a specific alert sign-up, hold audience and offer steady, and repeat while preserving the first result.
Key terms
- Test Cycle One
- The Week Five observation and interview cycle used to evaluate the first venture version.
- Neutral Observation
- A factual record of participant actions that avoids assigning motives before follow-up evidence.
- Interview Probe
- A non-leading question used after behaviour to clarify expectations, motives or missing information.
- Outcome Statement
- A concise report of what the test produced before the team explains its meaning.
- Audience Boundary
- The limit placed on a conclusion when participants differ from the intended early-adopter niche.
Test Cycle One: Observe and Interview FAQ
What should observers write down?
Record the task, sequence of actions, pauses, errors, questions, assistance and completion or abandonment. Avoid labels such as confused, uninterested or careless because those words assign motives. Follow-up questions can then explore what the participant expected and why the observed moment occurred.
Why interview after observation?
Observation shows behaviour but cannot always explain it. A short follow-up can reveal missing information, unexpected interpretations or an existing workaround. Asking after the task also reduces the risk that an interviewer coaches the participant and changes the behaviour the team intended to observe.
Can classmates provide useful evidence?
Yes, but the claim must match the audience. Classmates can expose unclear language, navigation or assumptions about prior knowledge even when they are not early adopters. Their willingness to use or pay for the venture is weaker demand evidence if they do not share the target problem context.
When should an observer intervene?
Intervene when safety, consent or an agreed boundary requires it, and record that assistance because it changes what completion means. Otherwise, allow the participant to encounter the task so the notes reflect the artefact rather than coaching. A neutral prompt may clarify what the participant is trying to do without supplying the correct path.
In analysis, separate unaided completion, assisted completion and abandonment, then use follow-up questions to explore expectations without rewriting the behaviour that was actually observed.
Assessment move
Rehearse the cycle with a small everyday task before using your venture prototype. Write the hypothesis, method, metric and criteria, then observe a participant without intervening. Compare your raw notes with the motive words you initially wanted to use. Turn each inference into a follow-up question. After the session, write four separate paragraphs: outcome, analysis, limitation and next step.
Check that the next step follows from the result rather than from the team's pre-existing design preference. For the real cycle, label participants by relevant context rather than by name, preserve conflicting responses and note any assistance. Complete the test card while the evidence is fresh, then carry its exact result into the Week Seven revision discussion.
Create an observation key with columns for task step, action, pause, error, assistance and completion. Watch a short practice task twice: first record only visible behaviour, then draft neutral follow-up questions for moments that need explanation. Mark every word that assigns a motive without participant evidence.
Next, simulate a result that meets the numeric criterion but reveals a serious comprehension problem, and write a decision that preserves both findings. Repeat with a failed action and an interview that offers a plausible method limitation. These contrasts train you to distinguish outcome, explanation and repair instead of forcing all evidence into a single verdict.
Working through Test Cycle One: Observe and Interview in MDIA1007? Sia is AskSia’s AI Management tutor — ask any MDIA1007 Test Cycle One: Observe and Interview 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.
