Week 01-02
VALIDATEDeconstruct the idea
Find a real problem and a reachable first user.
Must do
Interview, observe, map the existing workaround, and kill vague claims.
Proof
Problem brief, user notes, risk list, first evidence log.
The Common Labs
Stop talking about impact. Start shipping proof.
An 8-week execution lab for high-agency teenagers in Singapore. You bring the idea. We bring the pressure.
Cohort age
14-19
Sprint length
8 weeks
Minimum proof
Real users
Cohort 01 / live file
Build Lab Dashboard
Active constraint
Leave the laptop by Friday.
Week 0468%
12
Interviews
3
Proof artefacts
Strike status
CLEANVALIDATION
12 user interviews logged
Week 02 / evidence required
MVP
Prototype must leave the laptop
Week 04 / deploy or pilot
PROOF
Build history published
Demo portal / public record
Next review
Weakest assumption: students will return without reminders.
00The enemy
Most student projects are theatre.
Leadership titles. Pitch decks. Certificates. Passion projects that never touch a real user. That system rewards optics.
We reward proof.
Old model
Pitch decks
TCL model
Working MVPs
Old model
Leadership titles
TCL model
Inspectable proof
Old model
Polished retrospectives
TCL model
Public build logs
Old model
Theoretical impact
TCL model
Users in the loop
Old model
Certificates
TCL model
Evidence trails
Old model
Passive workshops
TCL model
Weekly shipping
01What TCL is
A selective accelerator for teenagers building real things.
In 8 weeks, every team must validate a real problem, build a working MVP, launch to actual users, collect evidence, and publish their build history. No vague inspiration. No slide-only projects. No fake impact narratives.
AppsPrototypesSTEM initiativesSocial enterprisesResearch projectsCommunity pilots
Week 03-04
BUILDCut to a radical MVP
Build the smallest useful thing that can be tested outside the room.
Must do
Scope brutally, prototype fast, use AI and tools openly, ship weekly.
Proof
Working demo, build log, repo/prototype/media trail.
Week 05-06
LAUNCHPut it in the wild
Get the thing in front of actual users and let reality push back.
Must do
Launch, recruit users, collect feedback, patch what breaks.
Proof
Usage evidence, interviews, screenshots, pilot records.
Week 07-08
PROOFRefine and publish
Turn messy execution into a public proof-of-work dossier.
Must do
Tighten the product, explain the learning, and demo live.
Proof
Demo Day portal, final build history, next-step plan.
02The operating system
The lab is built to make motion hard to fake.
TCL is not a content programme. It is a pressure system: logs, milestones, review, verification, strikes, and public proof.
01
Daily Ship Log
A lightweight record of what changed, what broke, and what evidence was added.
02
Weekly Milestones
Each week has a hard deliverable. Momentum is visible, not assumed.
03
Peer Review Matrix
Builders critique scope, evidence, usability, and the weakest assumption.
04
Strike System
Miss ships, dodge proof, or perform theatre twice and you are out of the public cohort.
05
Verification
Screenshots, links, interviews, usage notes, and demos are checked for substance.
06
Demo Day Portal
The final output is a public dossier people can inspect, not a closed-door pitch.
03Screening signal
If you are optimising for your portfolio, this is probably not for you.
For you if...
You independently code, research, organise, design, write, test, or tinker.
You are willing to talk to users before the idea feels polished.
You can accept sharp critique without turning it into drama.
You care more about whether the thing works than whether it sounds impressive.
Not for you if...
You want an easy certificate or a neat line for your CV.
You prefer slide decks to uncomfortable user evidence.
You need adults to keep you motivated every week.
You want a programme that protects your idea from reality.
04Mentor model
One-step-ahead mentors. Not ceremonial names on a poster.
The best mentor for a teenage builder is often close enough to remember the mess. Tactical, current, and specific beats distant prestige.
Undergraduate buildersYoung foundersJunior engineersResearchersOperators
Mentor review room
Questions mentors are allowed to ask
Q01
Who exactly used this, and what did they do next?
Q02
What assumption are you avoiding because it might kill the project?
Q03
What can be deleted so the MVP ships this week?
Q04
Which piece of proof would make a stranger believe you?
05Why different
Less inspiration. More operating pressure.
01
Pressure is structural
We do not motivate you with speeches. The system forces visible weekly output.
02
Mentors are tactical
Advice is close to the work: scope, users, prototypes, evidence, launch friction.
03
Proof beats polish
We would rather see a rough thing in a user's hand than a beautiful story about impact.
06What you leave with
A dossier that can survive inspection.
01
A working MVP, pilot, study, tool, or initiative that touched real users.
02
A public build history with decisions, evidence, failures, and iteration.
03
A sharper instinct for scope, user validation, and shipping under pressure.
04
A credible proof dossier for mentors, schools, sponsors, and future collaborators.
Cohort applications
If you build because you cannot help yourself, apply.
If you want a line on your CV, look elsewhere. If you want the pressure to turn an idea into proof, start here.
07FAQ
Read before applying.
Who is this for?+
Teenagers aged 14-19 with a Singapore connection who already show signs of agency: building, researching, coding, organising, writing, prototyping, or shipping without waiting for permission.
Do I need a team?+
No. Solo builders can apply. Teams are welcome when each person has a clear role and the project will move faster because the team exists.
What kinds of projects are accepted?+
Apps, prototypes, STEM initiatives, social enterprises, research projects, media tools, and community pilots. The common thread is that the work can reach real users and produce evidence in 8 weeks.
Is it in-person or virtual?+
The lab is designed around weekly shipping, critique, and evidence review. Some sessions can run online, but Singapore-based touchpoints and Demo Day are expected where practical.
How selective is it?+
Selective enough to protect the room. We look for initiative, obsession, coachability, and the willingness to ship rough work to real people.
What if I only have an idea?+
That can be enough if the itch is real. You will need to validate fast, cut scope, and show evidence that you can move before the cohort starts.
Is there funding?+
The first priority is execution, not grant theatre. If a project needs small operational support to test with users, we will evaluate it case by case.
How much time does it take?+
Expect a serious weekly commitment outside school. If you cannot protect build time, the strike system will make that obvious quickly.