Iworkincycles,adaptedtotheambiguity,misalignment,andriskinvolved.
Iworkincycles,adaptedtotheambiguity,misalignment,andriskinvolved.
Iworkincycles,adaptedtotheambiguity,misalignment,andriskinvolved.

My role is to help teams understand the system they’re operating in, make informed decisions, and move forward with confidence.

CLARIFY • LEARN • DECIDE • ADJUST •

Leadership principles

Fast clarify before execution

Do not rush when the problem is still blurry

I surface uncertainty, name the real problem, and create the context teams need before committing to execution. This is why research, mapping, workshops, IA work, and decision frameworks are central to how I lead.

Fast clarify before execution

Do not rush when the problem is still blurry

I surface uncertainty, name the real problem, and create the context teams need before committing to execution. This is why research, mapping, workshops, IA work, and decision frameworks are central to how I lead.

Simplify without shallowness

Push for simple solutions and language

Simplicity today holds real complexity underneath. I am not interested in fake simplicity or polished slides that avoid the hard questions.

Simplify without shallowness

Push for simple solutions and language

Simplicity today holds real complexity underneath. I am not interested in fake simplicity or polished slides that avoid the hard questions.

Alignment is not agreement

Not everyone has to like the same idea.

I need people to understand the same problem, the same constraints, and the same direction. Alignment means shared understanding, not forced consensus..

Alignment is not agreement

Not everyone has to like the same idea.

I need people to understand the same problem, the same constraints, and the same direction. Alignment means shared understanding, not forced consensus..

Challenge with respect

Push back, especially when moving without clarity.

The goal is not to win. The goal is to protect the quality of the decision. This keeps leadership sharp without making it ego-driven.

Challenge with respect

Push back, especially when moving without clarity.

The goal is not to win. The goal is to protect the quality of the decision. This keeps leadership sharp without making it ego-driven.

Think in systems, not tickets

Design beyond the immediate feature.

I ask how one decision affects the product architecture, the user mental model, the team model, and future scalability. Will today’s work still make sense in one or two years?

Think in systems, not tickets

Design beyond the immediate feature.

I ask how one decision affects the product architecture, the user mental model, the team model, and future scalability. Will today’s work still make sense in one or two years?

Way of Working

Framing the problem
Framing the problem
Understanding the system
Understanding the system
Using research
Using research
Making design decisions
Making design decisions
Scaling beyond A design
Scaling beyond A design
Framing the problem

If people can’t explain the problem the same way, design work will fragment later. I start by aligning on the decision we need to make, not the solution to build.

I focus on identifying:

  • The right problem we are trying to solve

  • Who this decision serves (users, business, system)

  • What success and failure look like

  • What we explicitly choose not to solve right now

Check how reframing the problem at Jedo unlocked growth

Understanding the system

My favorite step! It prevents local optimisation and repeated redesign. Before exploring solutions, I map the system around the problem.

This includes:

  • User workflows and edge cases

  • Operational dependencies and ownership gaps

  • Technical, legal, or other constraints

  • Existing patterns that should be reused or avoided

Targeted research

If research doesn’t change a decision, it’s noise. I use research to answer specific uncertainties without generating noisy volume.

Insights come from context-based methods, and are translated into:

  • Implications

  • Tradeoffs

  • Assumptions to validate

See how Research became a strategic asset at Doctolib

Making design decisions

I structure decisions around clarity, not consensus, to keep teams aligned as complexity increases.

Every design direction is shaped by:

  • Principles: what good outcomes look like

  • Constraints: what we must respect

  • Variations to validate: usually 2–3 realistic paths

Designing for scale

I believe that design impact is not in just shipping. I design structures teams can build on.

This means:

  • Shared language and mental models

  • Reusable patterns and guardrails

  • Clear boundaries between flexibility and consistency

Check how Design for scale unlocked new business verticals at Temper

Christian Almurr
Christian Almurr