COMM1120 Chap.4 Prototype Learning, User Value, Persuasive Pitches
Prototype Learning, User Value, Persuasive Pitches
A prototype makes an uncertainty testable. Its fidelity should match the question: a sketch can test sequence, a role-play can test service hand-offs, and a paper interface can expose navigation or comprehension issues.
Feedback becomes useful when the team distinguishes observation from interpretation and records why an iteration was made.
A persuasive pitch aligns an implied audience with a relevant need, solution, development evidence, value proposition and specific ask. Personas should contain only details that affect decisions. Different audiences require different evidence and actions.
What this chapter covers
- 01
Write the test before building the prototype
- 02
Translate feedback into reasoned iteration
- 03
Connect personas to a value proposition
- 04
Narrow the pitch toward a specific ask
- 05
Coordinate timing, transitions and questions
Worked example · free
Turn a test into an iteration
- +1Record the comprehension failure.
- +1Interpret the failure at the choice point.
- +1Revise role language and time information.
- +1Retest explanation without coaching.
Key terms
- Prototype
- A preliminary representation built to answer a question before greater implementation commitment.
- Iteration
- A revision justified by observation, feedback or other evidence.
- Persona
- A data-informed profile containing characteristics that affect a design or communication decision.
- Value proposition
- A concise relationship between a defined user, need, benefit and credible mechanism.
- The ask
- A specific action or commitment requested from the pitch audience.
Prototype Learning, User Value, Persuasive Pitches FAQ
How detailed should a prototype be?
Use only the detail required to test the current uncertainty. Extra fidelity costs time and can make teams defend work because it looks finished rather than because evidence supports it, so begin with the leanest credible representation.
Should every piece of feedback cause a change?
No. Interpret feedback against the problem definition, target user and test question. Look for patterns, behavioural evidence and consequential contradictions rather than treating every preference as an instruction.
What makes a persona useful?
A persona is useful when its needs, goals, constraints or context change a solution or communication choice. Decorative biography adds detail without improving judgement or testing a relevant assumption.
How should a pitch end?
End with a bounded ask naming the actor, action or resource, and what it enables. The preceding evidence should make that request credible and relevant to the implied audience.
Assessment move
For every prototype, write the uncertain belief, participant, task, observation and disconfirming signal. Keep a version log linking evidence to each change. Rehearse the pitch by asking which audience question every section answers and remove material that does not advance the ask. Prepare a test card before building.
State the assumption in one sentence, choose the lowest-fidelity representation that can expose it, define a realistic participant task, and decide what behaviour would weaken the idea. During testing, record pauses, reversals, questions, workarounds and completion before asking for opinions. Do not coach unless the purpose of the test is to evaluate instruction.
Afterward, separate notes into observation, interpretation and possible response. Require the team to name why a proposed change addresses the observation. Preserve successful elements instead of rebuilding everything after each comment. A version table should show what changed, what evidence prompted it and what the next test will examine.
For persona and value work, delete any biographical detail that does not change access, priority, communication or use. Complete the sentence: for this person in this situation, the response provides this benefit through this mechanism. Then challenge the claim with one limitation or competing need. Build the pitch backward from the ask.
Specify the audience, action, resource and purpose; list the evidence the audience would need before agreeing; then order the problem, solution, development and value sections to supply that evidence. Rehearse once for logic without slides and once for timing with slides. Give each speaker ownership of reasoning, not merely equal text.
Prepare concise Q&A responses for the weakest assumption, largest constraint, evidence boundary and next test. A strong response can acknowledge uncertainty while explaining how the team would resolve it. End by removing any feature, statistic or story that does not support audience value or make the ask more credible. Record a silent rehearsal and review it from the implied audience perspective.
Note where the need becomes clear, where proof arrives, where jargon interrupts comprehension and whether the requested action is feasible. Ask another person to state the value proposition and ask from memory. If either is unclear, adjust the sequence before adding detail. Use the final timed run to protect space for the close and likely questions.
Confirm that each speaker can explain the evidence behind the shared recommendation.
Working through Prototype Learning, User Value, Persuasive Pitches in COMM1120? Sia is AskSia’s AI Management tutor — ask any COMM1120 Prototype Learning, User Value, Persuasive Pitches question and get a clear, step-by-step explanation grounded in how COMM1120 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
