The Improbability Company Challenge OS — built for Cần Thơ 2030

Active challenge

Mekong household energy-resilience model

Challenge validation

Residential and SME ClimateTech Working prototype, pilot conversations, and feasibility paper

Owner Programme working group

Week 13 Jul

Next gate Validate challenge area and assign faculty supervisor

Risk Local energy data availability and field validation

Sprint readiness

20% ready

Current state is strong enough to scope the student prototype, but still needs field data and faculty confirmation.

Challenge areas 3-5 Validate by mid July

Students per team 3-5 Plus mentor and supervisor

Internal demo 24 Aug Working-group review

Sprint close 26 Sep October Forum: presentation stage

Operating model

Anchor, operator, ecosystem

The host university anchors the sprint; The Improbability Company supplies the operating spine.

Anchor Host university

Institutional anchor; leads challenge identification, faculty engagement, student pathways, and governance. Set by programme admin.

Operator The Improbability Company

Programme delivery, partner orchestration, sprint coordination, and the commercial pathway.

Ecosystem Managed in programme records

Partner and ecosystem relationships are recorded in the database by admin once they are real.

Programme map

90-day sprint and decision gates

The sprint runs 1 July to 26 September 2026. The October Innovation Forum is the selection and presentation stage that follows.

1 Jul Kick-off and governance Operating spine active

6 Jul Challenge definition Draft challenge cards

13 Jul Challenge validation Sprint briefs approved

20 Jul Team formation Teams registered

27 Jul Challenge brief lock Challenge card locked

3 Aug Field discovery Pain and constraints evidenced

10 Aug Prototype plan Prototype scope approved

17 Aug Build sprint Evidence-backed build

24 Aug Internal demo Progress inspected

31 Aug Build iteration Iterated artefact

7 Sep Mid-sprint review Acceleration decision

14 Sep Pilot pathway Pilot options visible

21 Sep Showcase pack and close Sprint closes 26 September

Challenge areas

2026 focus map

Two core pillars and two adjacent streams. Partner records are managed by programme admin in the database.

Core pillar 01 Draft

Enterprise RegTech Managed by programme admin

Workforce compliance workflows adapted for the Vietnamese enterprise context.

Core pillar 02 Draft

Residential / SME ClimateTech Managed by programme admin

Mekong household and SME climate adaptation and energy resilience.

Adjacent stream A Draft

Mekong energy and grid research Managed by programme admin

Distributed energy and grid-support research drawing on faculty expertise where relevant.

Adjacent stream B Draft

AgriTech / AquaTech Managed by programme admin

Mekong agritech and aquatech challenge stream.

Sprint board

Challenge areas moving through gates

Server-backed state: new briefs, evidence, review gates, and team edits persist to the programme database with a full activity history.

Team formation

Student + mentor teams

Each challenge needs 3-5 students, one faculty supervisor, and one engineer mentor.

Challenge engine

Sprint brief builder

Convert a focus area into a student challenge card.

Generated sprint card

Mekong household energy-resilience model

Stakeholder: Mekong households, SMEs, and local energy partners
Context: Residential and SME users need practical resilience models for climate and energy stress in the Mekong context.
Output: Working prototype, two pilot conversations, and feasibility paper

Evidence workspace

Governance, fieldwork, and pilot evidence

Type Challenge Signal Owner

Founderverse router

158 Founderverse resources, applied to CT2030 stages

Stage Topic

Define: challenge and discovery 21

Design: solution and prototype 15

Build: alpha and internal demo 22

Pilot: metrics and partner path 21

Showcase: handoff and adoption 50

General reference 29

Student team review

Sprint gate checklist

Students need supervisor, mentor, prototype, field evidence, and showcase artefact readiness.

Challenge brief names the real user, data source, and pilot pathway Student team has a faculty supervisor and an engineer mentor Prototype or model can be demonstrated without manual theatre Data, privacy, and safety risks are named for the local context Feasibility paper explains assumptions and limitations Pilot conversations are logged as evidence Showcase artefact can be understood by non-technical stakeholders

0 of 7 complete

Weekly score

Rubric cockpit

Adjust the sliders to see sprint readiness across challenge clarity, field evidence, technical work, and pilot path.

Challenge clarity 15 pts 0 Field evidence 20 pts 0 Technical artefact 20 pts 0 Faculty supervision 10 pts 0 Mentor cadence 10 pts 0 Pilot pathway 15 pts 0 Showcase readiness 10 pts 0

Total score 0 out of 100

Next decisions

Working-group asks

The app should make these deadlines visible and auditable.

Confirm the working group and focal points by 1 July 2026.
Agree criteria for selecting the first challenge areas.
Validate challenge areas by mid July 2026.
Staff each sprint team with students, one engineer mentor, and one faculty supervisor.
Close the sprint on 26 September 2026 with showcase packs ready for the October Innovation Forum.

October Innovation Forum

Presentation stage

The Forum is the selection and presentation stage after sprint close — it is not a programme gate.

October Innovation Forum: selection and presentation stage after sprint close
Sprint showcase by student and faculty teams
Curated meeting blocks for stakeholders
Forward look at pilot and incubation pathways

Student challenge cockpit

Mekong household energy-resilience model

Anchor, operator, ecosystem

90-day sprint and decision gates

2026 focus map

Challenge areas moving through gates

Student + mentor teams

Sprint brief builder

Mekong household energy-resilience model

Governance, fieldwork, and pilot evidence

158 Founderverse resources, applied to CT2030 stages

Sprint gate checklist

Rubric cockpit

Working-group asks

Presentation stage

Sign in to the Challenge OS