Opportunity-
WEEK 3
recognition
Cycle A STEP-BY-STEP GUIDE TO THIS
WEEK’S CLASS ACITVITIES
PRESENTED BY
THE TEACHING TEAM
Introduction
01
Goal: Run the full opportunity-recognition cycle on a real problem (traffic/congestion).
Use quick research (Google Trends, WEF, MIT Tech Review) to validate whether people would
pay for your idea.
No submission this week — but follow the steps closely (you may be asked to present later).
Quick logistics (do this before you start) 02
Group structure: sub-teams of 5 (two sub-
teams per whole group).
Tools:
Online co-working tools: Canva, Docs, Excel,
Padlet,..,
Credible data source: Google Trends,
McKinsey, World Bank, Statista,...
Presentation: Canvas, Google Slide, Power
Point
Roles (suggested): Co-leader (organizes),
Timekeeper, Secretary, Researcher, Presenter.
Constraint: Solutions should not be framed as
environmental/sustainability projects this week.
STEP 1 — Divergent Thinking (10 min) — Sub-team 03
GOAL: GENERATE LOTS OF PROBLEMS (QUANTITY > QUALITY).
Procedure:
Use Brainwriting 6-3-5 on any platform (e.g.,
Canva, Google Docs).
First 5 mins: Each participant writes down 3
general traffic/congestion problems (no
need to be specific).
e.g., Experienced workers struggle to find jobs
Next 5 mins: Pass problems to the next
person → build on ideas with clearer
symptoms/root causes.
e.g., Mismatch in expectations between employees &
employers; lack of specialized support
Reminder: Don’t evaluate or critique. Focus on
generating ideas in quantity.
STEP 2 — Cluster & Select a Problem (8 min) — 05
Sub-team
NARROW MANY PROBLEMS TO ONE
Goal: COMPELLING PROBLEM PER SUB-TEAM.
[Link] similar problems into clusters (sub-teams make sure to have your
own rationales for cluster)
[Link] member has 1 dot vote to pick the most compelling problem
[Link] cluster with the most votes becomes the selected problem of your
sub-team
[Link]: One chosen problem
[Link]/tips: Co-leader to facilitate team members. Keep clusters tight.
STEP 3 — Evaluate Market
04
Importance (12 min) — Sub-team
GOAL: ASSESS SCALE & URGENCY — IS THIS WORTH PURSUING?
ANSWER THE FOLLOWING QUESTION:
OUTPUT:
WHO EXPERIENCES THIS PROBLEM? (CUSTOMER SEGMENT) PROBLEM STATEMENT WITH CLEAR
BULLETPOINTS: WHO, WHY, HOW
WITH BACK-UP DATA
WHY IS IT PAINFUL?
HOW MANY ARE AFFECTED? TIPS:
(USE AT LEAST ONE QUICK DATA SOURCE — GOOGLE
CITE THE DATASOURCE. REMEMBER
TRENDS, WORLD BANK, MCKINSEY, WEF) TO COPY AND PASTE THE HYPERLINK
STEP 4 — Quick Validation Research (10 05
minutes) - [SUB-TEAM]
IDENTIFY CRITICAL ASSUMPTIONS AND
Goal: DESIGN WAYS TO TEST THEM. Assumption 1: Employers welcome
experienced workers but don’t know how
to reach them.
Procedure:
→ Validate: 3–5 quick HR interviews on
sourcing mid-career talent.
Each sub-team: list 2 key assumptions for
your problem.
For each assumption: outline a quick test
(speed > perfection).
Methods: short interviews, online survey,
Assumption 2: Experienced workers want
small pilot/prototype. a dedicated job site because existing ones
overlook them.
Example
→ Validate: Simple online survey in
Problem: Experienced workers struggle to
LinkedIn/Facebook groups (40+
find new jobs. professionals).
STEP 5— Final Opportunity & 1-Minute
06
Pitch (15 mins) – [Whole-team]
GOAL: COMMUNICATE OPPORTUNITY CLEARLY & PERSUASIVELY
Procedure:
Sub-teams create 2–3 solutions for the chosen problem (5 mins).
Craft a 60-sec pitch (via Canva or any similar platform) including:
1. Hook (insight/statistic)
2. Problem
3. Solution(s)
4. Market size / key data
5. Next step
Presentation: Two sub-teams present their pitch to another sub-
team and QnA
Step 6—Debrief & Reflection (5 mins) 07
Goal: REFLECT ON LEARNING & IDENTIFY IMPROVEMENTS
Procedure:
Whole-class discussion:
• What was the hardest part –
problem finding, validation, or
pitching?
• How could the process be
improved next time?