Skip to content
Resilient Systems

The best process is one that doesn't depend on any single person to remember it.

Published · Updated

When I joined the IKEA Home Services team, there was no shared working system. Files existed everywhere. The hierarchy of work, what belonged in Figma, what in Confluence, what in Jira, was unclear and inconsistently applied. The process that existed depended on specific individuals to hold it in memory and transmit it informally. When those individuals weren't available, the system collapsed.

My approach was to start with principles rather than tools. I mapped the actual work the team was doing: the types of tasks, their interdependencies, the decisions that kept getting lost. From that, I derived a set of structural rules, what goes where, when, and why, that could be documented, taught, and modified without requiring me to be present.

Adoption was messy, honestly, but the underlying structure held up regardless. That's what I was aiming for: a process solid enough to keep working when people don't follow it to the letter. It's already outlived changes in the team, a round of new hires, and the stretches where nobody had time to babysit it. That's the real test, and it passed.

A good system keeps working when people don't follow it perfectly.
Available

Thinking about
the same questions?

I’m always glad to compare notes on AI in design teams, behavioural science and how teams work. Open to senior product design roles and selective consulting engagements, in English or Spanish.