We design conditionsfor behavior to emerge.
We don't build a test. We build a real context where behavior can't be faked.
The institution sets the parameters
Before a team exists, someone defines the conditions under which the observation will take place.
A cohort ready to be observed in a shared context.
You don't choose your team. You work with it.
Teams:
Randomness matters: it keeps people from grouping only with those they already know or with similar profiles.
An open problem. Not a right answer.
The challenge is the simulation's starting point. It's not about solving an exercise with a single solution, but about facing a real problem that forces the team to research, decide, build and communicate together.
Sample challenges
Redesign the onboarding experience
A multidisciplinary team analyzes the current flow, proposes improvements and delivers a prototype validated with users.
Build an MVP for a healthtech
Develop a working product in 5 weeks, from research to deployment, working across different roles.
Optimize an e-commerce conversion rate
Research user behavior, identify friction points and run experiments to improve key metrics.
- →Build
- →Design
- →Analyze
- →Research
- →Develop
- →Solve
- →Launch
- →Optimize
- →Company
- →Institution
- →Startup
- →Fictionalized case
The challenge sets the playing field. How to solve it is up to the team.
Execution
Week 0 — Kick-off
Team formation and initial planning.
Weeks 1 to 4 — Execution
Coordination, decisions and deliverables throughout the whole cycle.
Demo Day and wrap-up
Peer review, final delivery and presentation of results.
The length adapts to the goal and depth of the experience — it isn't a fixed number.
Signals that record themselves
During execution, signals are recorded for:
