Credo

Design leadership isn't an executive role. It's infrastructure work. Creating the conditions for others to think, decide, learn. Not positioning yourself as the person who has the answers.

Success isn't measured by the list of signed deliverables. It's measured by the autonomy teams have gained. A healthy design organization could run without its Head of Design for two months without falling apart. Not because it doesn't need her: because everything that was indispensable has been documented, passed on, made reusable.

The four beliefs that follow are the pillars of this infrastructure. They have held through 10 years of practice across very different contexts. They are not fixed. They are tested.

The opposite reflex is expensive. A team that executes without context produces what it's asked for, but can't recognize what should have been asked for instead. It can't step away from a vague instruction, because it has nothing to judge with. Control tightens, autonomy erodes, and the work gradually gets more expensive for a less accurate result.

In practice, that means the 'why' gets documented everywhere. In a research brief, in a trade-off note, in a commit message, in a design system review. The extra effort at writing time saves hours of clarification six months later. It's the only way we have to make a decision outlive its author.

The cost is visible: we talk longer, we document more, we start slower. The bet is always the same. Save on context today, pay double for it in six months.

The test is simple: if the person who produced the deliverable disappears tomorrow, can what they delivered still be used? If the answer is no, the deliverable isn't finished. It exists as a promise, not as an object.

That changes how every work artifact is designed. A design system isn't a component library, it's a documented governance infrastructure. A Research Repository isn't a tidy Drive folder, it's a shared taxonomy and consumable dashboards. A discovery brief isn't a framing document, it's an object that guides a team for 6 weeks without going back to its author.

This discipline also changes the posture. Earlier in the practice, you protect your work like a personal signature. Later, you understand that the strongest signature is the people who pick up your work and make it evolve without you.

Curiosity is practiced. Testing, getting it wrong, starting again, without delegating to others what could be learned by doing. It's the most demanding belief of the four, because it means accepting to be regularly out of your comfort zone, including at a point in your career where you're supposed to 'know'.

Right now, that zone is AI in design. Not AI as a conference topic, AI as a daily working tool. Building prototypes code-first with an LLM rather than in Figma. Structuring briefs for agents rather than for humans. Rethinking how a team of 3 does the work of 6, not by going faster but by changing what we delegate and what we keep. It's uncomfortable. It's also the only way not to go stale.

This posture applies to tools, but also to the subjects handled alongside the core craft: business model, pricing, content strategy, legal. And to the relational skills you discover while handling situations beyond what previous experience prepared you for. Learning in public is also leadership. Above all, leadership.

Someone under stress doesn't really think. The gesture takes thirty seconds. A simple question, attentive listening, an adjustment of pace if the person in front of you needs to breathe. Whatever work follows depends on that quality of presence.

This discipline carries an invisible cumulative effect. A team that knows it is cared for individually develops a trust that later shows in the quality of the collective work. Cause and effect are separated by several weeks, sometimes several months. You can't draw a straight line between attention given on a Thursday and a brief that passes review on the first try the following Friday. But the relational ecosystem produces the quality ecosystem.

It's also the belief that resists rushed contexts the most. When a quarter is tight, when a reorganization is coming, when pressure builds from above, the natural reflex is to cut things short. That is precisely the moment to hold. The quality of presence is the infrastructure that makes everything else possible.

This credo isn't fixed. Several subjects remain open, and it would be dishonest to gloss over them to look tidy.

AI in design is fast-moving ground. The practices that work today will probably be outdated in eighteen months. What's being built right now is a methodological posture to absorb those changes, not a lasting truth. Having integrated AI as a belief and as a practice doesn't mean the right integration has been found.

Scaling internationally is another open subject. Working in French and Spanish within English-speaking environments imposes an asymmetry in thinking. What comes out clearly in one language sometimes takes extra effort in another. That asymmetry can be worked on, but it's real.

The boundary between coaching and management remains an active exploration. The designers we support sometimes expect peer thinking, sometimes a clear decision, sometimes a frame, sometimes blunt feedback. Years of complex management situations have built the reading needed to navigate that. What stays open is that people change, contexts move, and the right answer to a situation is never exactly the same twice. That's what keeps the subject alive.