Lesson 1: Identifying Authentic Problems & Stakeholder Requirements
Developing a complex digital outcome to solve a real-world problem for NCEA Level 3 Digital Technologies.
🎯 Ngā Whāinga Akoranga | Learning Intentions
Criteria for a complex digital outcome under Level 3 Digital Technology (relational database, web application API integration, component interactivity, accessibility), user-centred design, and stakeholder brief formulation.
Formulate a formal project brief, conduct stakeholder interviews, specify functional requirements, and establish end-user acceptance criteria.
🎥 Media Anchor & Pedagogical Scaffold
The Single Biggest Reason Why Start-Ups Succeed | Bill Gross | TED
Video Clip: “The Single Biggest Reason Why Start-Ups Succeed | Bill Gross | TED” — 6 min 41 s.
🧠 1. Before Viewing (Activate & Predict)
What transforms a basic coding project into a Level 3 'Complex Digital Outcome' that solves a real-world community need?
👁️ 2. During Viewing (Watch With a Job)
- Watch the full 6-min clip and note the five factors Gross ranks — which one ranks #1 and why does it matter for your project brief?
- Consider: does your proposed digital outcome address a genuine, unmet stakeholder need, or is it a solution looking for a problem?
- Identify one real-world community, school, or business problem that would benefit from a complex web application outcome.
🗣️ 3. After Viewing & Kaiako Move (Process & Apply)
Kaiako Move: Guide students through interviewing school staff, local businesses, or community groups to identify genuine software needs.
Immediate Task: Complete Section 1 of your Level 3 Digital Tech Portfolio: Authentic Problem Brief & Stakeholder Interview Log.
⚡ Whakaoho | Do Now: "Easy to Use" Is Not a Requirement
Two minutes: rewrite it as something you could actually test. A specific action, by a specific user, within a specific limit.
If your rewrite still contains a word like intuitive, clean or fast, it is still an opinion. Requirements nobody can test are the single most common reason a project fails its acceptance check.
📖 Activity 1: Interview for the Problem, Then Write Testable Criteria
Interview, do not survey (13 min). Walk your stakeholder through one real task they currently do. Ask what they do, then what goes wrong, then what they do when it goes wrong. Do not ask which features they want — people describe solutions they have already seen, not the problem they actually have.
Convert it to criteria (12 min). Write six acceptance criteria in the form: given [situation], when [action], then [observable result]. Each one has to be checkable by someone else without asking you what you meant by it.
📝 Activity 2: Level 3 Digital Technology Portfolio Task & Merit/Excellence Scaffolding (20 mins)
Portfolio Section 1. Submit: (1) a project brief naming the problem, the end user, and what makes this outcome complex — which of relational data, API integration, component interactivity and accessibility it will demonstrate; (2) interview notes that keep the problem separate from the solution the stakeholder suggested; (3) six testable acceptance criteria in given/when/then form.
🏫 Kaiako Planning & Pedagogy Notes
NCEA Level 3 Alignment: Direct preparation for Level 3 Digital Technology (Develop a complex digital outcome to solve a specified problem). Emphasise systematic testing, stakeholder feedback loops, and technical code refinement for Merit/Excellence grades.