01
The Mandate
“Everyone should use AI.”
A town hall, a Slack channel, then nothing changes.
Why it fails
you change habits without changing the environment. A gym membership bought in January.
Owned AI · Jikken Method
Let's welcome your new AI colleague.
Your teams already use AI — quietly, each on their own. The Jikken method turns those uses into a real operating system for your work: personal, then team, then company-wide. Co-built with you, lived as colleagues, and yours to keep.
The three traps
You're not behind. You bought the licences, ran the workshops, maybe built a few automations. And yet AI is still a side project. Because most teams fall into one of three traps.
01
“Everyone should use AI.”
A town hall, a Slack channel, then nothing changes.
Why it fails
you change habits without changing the environment. A gym membership bought in January.
02
“Let’s add AI to our existing process.”
Inserted into a human-designed flow; output is generic, trust erodes.
Why it fails
a new engine in a car built for a different drivetrain.
03
“We trained everyone on the tools.”
Individuals get faster, the organisation doesn't change.
Why it fails
ten slightly faster people is multiplication. New capability is addition. A different equation.
What they share? AI is deployed onto your teams, not owned by them. The problem isn't AI. It's how you bring it in.
The Jikken method
You don't deploy an operating system. You grow it, through experimentation, loop after loop. The same loop, from the workstation to the C-suite.
The loop, five steps
1
start from the real work and the uses already there (the gemba).
2
build a testable use fast, not a three-year plan.
3
real effect: time saved, quality, mental load.
4
anchor it in team rituals, hand it over.
5
lock what works into a living playbook, then start again one level up.
leadership sets direction, value is born at the workstation, managers are the belt. Value is created from the bottom — but we work with leadership and managers, not around them.
we start by building their personal OS; they live it in their own week before imposing it on anyone.
“We don't deploy onto your teams what you haven't lived yourself.”
With AI, productivity is just the start. The real edge is collective.
It can't be decreed — it emerges when individual pairs coordinate.
Each person builds their pair — a second brain that acts, not just stores: domain tasks, knowledge, routines.
Deliverable
your personal OS — configured pair, playbook, measured gains.
Pairs coordinate; we redesign and tool the team's workflows.
Deliverable
your team OS — redesigned flows, rituals, shared metrics.
Agents per department or business unit talking to each other, up to the C-suite.
Deliverable
your company OS — cross-unit orchestration, governance, transferred bench.
No lock-in
Same goal at every scale: you own your system, you don't rent it. You keep your AI colleagues, your playbooks, your data. We don't rent you intelligence; we teach you to run your own.
Our principle
No surveillance, no telemetry, no reading your teams' conversations. We start from what people choose to share. Analysis happens at team level; individual data belongs to the individual alone. A colleague you welcome, not an eye you impose.
About
Christophe Routhieau
Founder
Co-founder of Emakina and BlueKiwi Software, contributor to Anaplan's growth. After 20 years shaping the future of work, I've learned one thing: human adoption is what separates a tool from a lever for change. Today I help impact-driven organisations build AI they master. Jikken — “experimentation” in Japanese — names my belief: neither technology alone nor humans alone; it's the right combination of both, grown through experiment, that creates impact.
Let's welcome your new AI colleague.
A 30-minute call to map your real uses and see where to start. No slides.
Book a call →