Where code becomes creation
The Challenge
Developers at Meta's Kings
Cross campus needed
protected spaces for early-
stage code and vulnerable
creative work. Existing
solutions didn't provide the
psychological safety that
sensitive work requires.
- Full enclosure creates genuine psychological safety.
- Individual environmental controls.
- Extended comfort for deep work sessions.
- Security by design.
The Paradox of the Modern Campus
What was happening: Meta Kings Cross: open, collaborative, designed
for connection. But something was missing - the ability to disappear.
- Developers staying late to find quiet time
- Sensitive work happening in unsuitable locations
- Glass-sided booths created "goldfish bowl effect"
- No environmental control over light, sound, air, visuals
The need: A space where you could control everything - and be controlled by nothing.
Full enclosure changes everything
| Open-plan noise, constant interruption | Full acoustic enclosure — 28dB reduction |
| Average deep-work session under 45 min | 3.5 hour average session length |
| After-hours coding to avoid distraction | 40% reduction in after-hours work |
| No private space for sensitive architecture discussions | Secure, private environment by design |
The Kabin Difference
Psychological Safety - Solid walls eliminate goldfish bowl effect. Work on sensitive code without visual exposure.
Environmental Autonomy - Individual control over lighting, ventilation, sound, visuals. Modulate environment to match work mode.
Extended Comfort - 3-4 hour sessions vs. 20 minutes in competitors' stuffy pods. Proper airflow prevents claustrophobic feeling.
Security by Design - No sight lines to screens or materials. Protected space for vulnerable creative process.
The Creative Parallel - Just as a music producer needs a mixing suite where they can trust their ears- developers need environments where their instincts can be trusted.
Measured and Felt
What changed:
The Complete Story
"Before Kabin, I'd stay until 8pm just to get two hours of uninterrupted coding time. Now I can drop into a Kabin mid-afternoon and get into flow state immediately.
It's not just quiet- it's the feeling that no one can see my screen, no one's evaluating my half-finished work. That psychological safety lets me take creative risks I wouldn't take at my desk.
When I'm debugging something complex, I dim the lights. When I need energy for a sprint, I brighten them. The ventilation means I can stay in there for an entire afternoon without feeling stuffy.
My manager noticed the change before I even mentioned it. My code reviews became more thorough, my solutions more creative. When you're not expending energy on managing your environment and worrying about who's watching, you can put all that energy into the actual work."
- Senior Developer, Meta
The Expansion
Initial: 10 units → Immediate high utilization
Growth: Expanded campus-wide → Demand continued to exceed supply
Current: Essential infrastructure → Unexpected uses include pre-presentation prep, post-meeting decompression
The Reality
You've invested in open collaboration spaces.
But innovation requires both exposure AND protection.
The best ideas need time in the cocoon before they're ready to fly.
- Full enclosure = psychological safety
- Environmental control = cognitive performance
- Extended comfort = sustained deep work
- Security = protected early-stage development
Do developers feel safe working on early-stage code?
Can creative teams protect their process before it's ready for review?
Does your space offer environmental control or one-size-fits-all?
Can someone truly "cocoon" on campus, or only collaborate?
that match your aesthetic
