Unlocking Future Growth: Partnering with Leaders in Healthcare and Mission-Led Organizations to Drive Change, Optimize Performance and Enhance Employee & Patient Experience | Managing Director at Bee'z Consulting Sàrl

Supporting organizations in the healthcare sector through deep transformations - with structure, meaning, and commitment.

That’s my mission.

I’m Silvina Layani, consultant and facilitator in organizational transformation, with 20+ years of hands-on experience in leading organizational change.

I step in when companies need to evolve, adapt, or pivot - aligning processes, teams, and cultures around a shared vision.

🎯 My approach is built on three key pillars:

1. Co-construction: co-defining change with stakeholders to ensure engagement
2. Culture & mindset: integrating human, intercultural, and emotional dimensions into transformation efforts
3. Iteration & agility: testing, adjusting, and grounding change in day-to-day realities

My work goes beyond strategy.

I rely on a deep understanding of organizational design and governance structures, which allows me to guide transformations by addressing both structural and human dynamics.

I firmly believe that engaging employees and building their capabilities are essential to embedding lasting change.

This belief has helped me contribute to the emergence of more adaptable, collaborative, and forward-looking cultures - particularly in the pharmaceutical, medical equipment, and hospital sectors.

I'm used to working in complex, multicultural, and sometimes tense environments.

What I bring is the ability to listen, structure, rally teams, and make sure decisions don’t stay in PowerPoint decks, but come to life and are carried forward by the teams themselves.

💼 I work with:

- Executives facing strategic questions
- HR teams leading transformation initiatives
- Managers looking for concrete tools to engage their teams

Looking to evolve your organization using proven methods while involving your people every step of the way?

I’d be happy to talk, just send me a message 📩

SILVINA LAYANI

𝗣𝗲𝗼𝗽𝗹𝗲 𝘁𝗵𝗶𝗻𝗸 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗶𝘀 𝗮𝗯𝗼𝘂𝘁 𝗺𝗮𝗸𝗶𝗻𝗴 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗰𝗮𝗹𝗹𝘀.
𝗜𝘁 𝗶𝘀𝗻’𝘁.
𝗠𝗼𝘀𝘁 𝗼𝗳 𝘁𝗵𝗲 𝘁𝗶𝗺𝗲, 𝗶𝘁’𝘀 𝗮𝗯𝗼𝘂𝘁 𝗺𝗮𝗻𝗮𝗴𝗶𝗻𝗴 𝗰𝗵𝗮𝗼𝘀 𝗻𝗼𝗯𝗼𝗱𝘆 𝘁𝗮𝗹𝗸𝘀 𝗮𝗯𝗼𝘂𝘁.


I saw this during a leadership simulation.

A room full of senior executives.
A crisis scenario on the table.
A timer counting down.

The moment pressure entered the room, the conversation changed.

People leaned in.
Debates sharpened.
Hidden assumptions surfaced.

Because 𝙨𝙞𝙢𝙪𝙡𝙖𝙩𝙞𝙤𝙣𝙨 𝙧𝙚𝙫𝙚𝙖𝙡 what most boardrooms hide:

• 𝙗𝙞𝙖𝙨𝙚𝙨
• 𝙨𝙞𝙡𝙚𝙣𝙩 𝙖𝙨𝙨𝙪𝙢𝙥𝙩𝙞𝙤𝙣𝙨
• 𝙙𝙚𝙘𝙞𝙨𝙞𝙤𝙣 𝙩𝙧𝙖𝙥𝙨

They are not “games”.

𝙏𝙝𝙚𝙮 𝙖𝙧𝙚 𝙥𝙧𝙚𝙨𝙨𝙪𝙧𝙚 𝙩𝙚𝙨𝙩𝙨.

Structured conversations are useful.

But pressure shows how people actually behave.

When leaders face a simulated crisis, something shifts.

Mindsets move faster than they do through hours of slides.

Because 𝙡𝙚𝙖𝙙𝙚𝙧𝙨𝙝𝙞𝙥 𝙞𝙨 𝙣𝙤𝙩 𝙖 𝙥𝙧𝙤𝙘𝙚𝙨𝙨.
𝙄𝙩 𝙞𝙨 𝙖 𝙡𝙞𝙫𝙚 𝙚𝙣𝙫𝙞𝙧𝙤𝙣𝙢𝙚𝙣𝙩.

Trade-offs appear.
Blind spots surface.
Decisions suddenly have consequences.

And that is where real leadership work begins.

𝗣𝗿𝗲𝘀𝘀𝘂𝗿𝗲 𝗱𝗼𝗲𝘀 𝗻𝗼𝘁 𝗰𝗿𝗲𝗮𝘁𝗲 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗯𝗲𝗵𝗮𝘃𝗶𝗼𝘂𝗿.
𝗜𝘁 𝗿𝗲𝘃𝗲𝗮𝗹𝘀 𝗶𝘁.

So here is the question.

What usually happens in your organisation under pressure?
Do decisions become clearer?
Or do they climb the hierarchy?

Leaders don’t need more theory.

They need:
• trust
• faster decisions
• clarity under stress

Everything else stays at the level of talk.

Reality steps in.

And simulations?
They isolate the gaps nobody names out loud.

What’s stopping you from confronting the chaos head-on?

✨✨ 𝙄𝙛 𝙩𝙝𝙞𝙨 𝙧𝙚𝙨𝙤𝙣𝙖𝙩𝙚𝙨, 𝙛𝙚𝙚𝙡 𝙛𝙧𝙚𝙚 𝙩𝙤 𝙧𝙚𝙖𝙘𝙝 𝙤𝙪𝙩. 𝙄’𝙙 𝙗𝙚 𝙜𝙡𝙖𝙙 𝙩𝙤 𝙙𝙞𝙨𝙘𝙪𝙨𝙨 𝙝𝙤𝙬 𝙡𝙚𝙖𝙙𝙚𝙧𝙨𝙝𝙞𝙥 𝙨𝙞𝙢𝙪𝙡𝙖𝙩𝙞𝙤𝙣𝙨 𝙘𝙖𝙣 𝙝𝙚𝙡𝙥 𝙩𝙤𝙥 𝙩𝙚𝙖𝙢𝙨, 𝙢𝙞𝙙𝙙𝙡𝙚 𝙢𝙖𝙣𝙖𝙜𝙚𝙧𝙨, 𝙖𝙣𝙙 𝙡𝙚𝙖𝙙𝙚𝙧𝙨 𝙬𝙝𝙤 𝙣𝙚𝙚𝙙 𝙩𝙤 𝙨𝙝𝙞𝙛𝙩 𝙝𝙤𝙬 𝙩𝙝𝙚𝙮 𝙡𝙚𝙖𝙙 𝙩𝙝𝙧𝙤𝙪𝙜𝙝 𝙘𝙝𝙖𝙣𝙜𝙚. ✨✨

No alternative text description for this image

𝙇𝙚𝙖𝙙𝙚𝙧𝙨𝙝𝙞𝙥 𝙩𝙧𝙖𝙞𝙣𝙞𝙣𝙜 𝙞𝙣 𝙇𝙞𝙛𝙚 𝙎𝙘𝙞𝙚𝙣𝙘𝙚𝙨 𝙞𝙨 𝙨𝙚𝙧𝙞𝙤𝙪𝙨.

SOPs. Checklists. Slide decks.

Then a real problem hits.

A quality issue shows up.
A supplier fails.
A regulator asks tough questions.
A launch date is at risk.

Now let's imagine how a leadership simulation can help get ready to handle it:

Your leaders run a simulation of that day.

The scenario: a late change is needed.
Manufacturing is already full.
QA wants proof.
Regulatory wants the right wording.
Commercial wants speed.
Patients are waiting.

In the room, patterns appear fast.

- One person tries to push a decision through.
- One person goes quiet.
- One leader does something simple—but powerful.

- They lower the tension.
- They name who decides.
- They pull in the right people.
- They move forward without taking unsafe risks.

𝙏𝙝𝙖𝙩’𝙨 𝙣𝙤𝙩 𝙖 “𝙜𝙖𝙢𝙚.”
𝙄𝙩’𝙨 𝙥𝙧𝙖𝙘𝙩𝙞𝙘𝙚 𝙛𝙤𝙧 𝙧𝙚𝙖𝙡 𝙥𝙧𝙚𝙨𝙨𝙪𝙧𝙚.

𝘽𝙚𝙘𝙖𝙪𝙨𝙚 𝙬𝙝𝙚𝙣 𝙩𝙝𝙞𝙣𝙜𝙨 𝙜𝙚𝙩 𝙨𝙩𝙧𝙚𝙨𝙨𝙛𝙪𝙡, 𝙥𝙚𝙤𝙥𝙡𝙚 𝙙𝙤𝙣’𝙩 𝙛𝙤𝙡𝙡𝙤𝙬 𝙩𝙝𝙚 𝙤𝙧𝙜 𝙘𝙝𝙖𝙧𝙩.
𝙏𝙝𝙚𝙮 𝙛𝙖𝙡𝙡 𝙗𝙖𝙘𝙠 𝙤𝙣 𝙝𝙖𝙗𝙞𝙩𝙨.

Simulations show those habits early—before they hurt a project or a patient.

They help you spot:
👉 slow handoffs
👉 unclear roles
👉 “we need more data” loops
👉 teams that don’t talk to each other until it’s too late

And 𝘁𝗵𝗲 𝗯𝗲𝘀𝘁 𝗽𝗮𝗿𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗱𝗲𝗯𝗿𝗶𝗲𝗳.

People stop arguing in theory.
They talk about what actually happened.
They agree on what to do next time.

If you lead in Pharma or MedTech, here’s the question:

When was the last time your leaders practiced a high-stakes decision, from start to finish, under time pressure?

If you want, I can share a few simulation ideas that work well for QA, RA, Ops, and Commercial.
Let’s connect.

undefined undefined

Newsletter ENG

✨ Want more field stories and practical moves? Join our newsletter community.

Quick wins you probably didn’t know you needed.
👉 in French: https://links.beez-consulting.com/LkdnFR
👉 in English: https://links.beez-consulting.com/lkdn

Newsletter FR

✨ Envie de plus d’histoires de terrain et d’actions concrètes ? Rejoignez notre communauté newsletter.

Des idées simples que vous ne saviez pas encore qu’il vous fallait.

👉 En français : https://links.beez-consulting.com/LkdnFR
👉 In English : https://links.beez-consulting.com/lkdn

beezconsulting

beez-academy

hrvaud

𝗪𝗵𝗲𝗻 𝗲𝘃𝗲𝗿𝘆 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗲𝘀𝗰𝗮𝗹𝗮𝘁𝗲𝘀...
𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝘀𝗹𝗼𝘄𝘀.


Many organisations say they want more ownership.
Yet the system often encourages the opposite.

When decision rules are unclear, something predictable happens.
Teams escalate.

Not because they lack capability.
Because the risk of deciding feels unclear.

So decisions travel upward.

One level.
Then another.

Soon leaders are solving operational questions that should never reach them.

This creates two problems.

1. Executives become overloaded.
2. And teams stop developing decision confidence.

Escalation loops rarely come from talent gaps.
They come from unclear decision design.

Three things usually make the difference:

• explicit decision thresholds
• clear escalation rules
• shared priorities

When those are visible, escalation drops quickly.
Execution becomes faster and calmer.


If you look at your organisation today:

Which decisions escalate most often?

erBp1cO1n

𝗧𝘄𝗼 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝗲𝘀. 𝗦𝗮𝗺𝗲 𝘂𝗿𝗴𝗲𝗻𝗰𝘆. 𝗦𝗮𝗺𝗲 𝗺𝗲𝗲𝘁𝗶𝗻𝗴. 𝗡𝗼 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻.

A leadership team launches a new initiative.

The direction is clear.
The plan makes sense.

Then Monday morning hits.

One team pushes priority A.
Another pushes priority B.

Both are valid.
Both matter.
Both sound urgent.

𝘼𝙣𝙙 𝙩𝙝𝙖𝙩 𝙞𝙨 𝙬𝙝𝙚𝙧𝙚 𝙚𝙭𝙚𝙘𝙪𝙩𝙞𝙤𝙣 𝙨𝙩𝙖𝙧𝙩𝙨 𝙩𝙤 𝙨𝙡𝙤𝙬 𝙙𝙤𝙬𝙣.

Not because people resist.
Not because the strategy is weak.

𝘽𝙚𝙘𝙖𝙪𝙨𝙚 𝙣𝙤 𝙤𝙣𝙚 𝙝𝙖𝙨 𝙢𝙖𝙙𝙚 𝙤𝙣𝙚 𝙩𝙝𝙞𝙣𝙜 𝙘𝙡𝙚𝙖𝙧:

𝙒𝙝𝙤 𝙙𝙚𝙘𝙞𝙙𝙚𝙨 𝙬𝙝𝙚𝙣 𝙩𝙬𝙤 𝙥𝙧𝙞𝙤𝙧𝙞𝙩𝙞𝙚𝙨 𝙘𝙤𝙡𝙡𝙞𝙙𝙚?

So people do what smart teams often do when the rules are vague.

They wait.
They escalate.
They add meetings.
They try to “align.”

𝘼𝙣𝙙 𝙨𝙪𝙙𝙙𝙚𝙣𝙡𝙮, 𝙖𝙡𝙞𝙜𝙣𝙢𝙚𝙣𝙩 𝙗𝙚𝙘𝙤𝙢𝙚𝙨 𝙩𝙝𝙚 𝙬𝙤𝙧𝙠.

This is one of the most common execution gaps I see.

𝙏𝙝𝙚 𝙨𝙩𝙧𝙖𝙩𝙚𝙜𝙮 𝙞𝙨 𝙣𝙤𝙩 𝙩𝙝𝙚 𝙥𝙧𝙤𝙗𝙡𝙚𝙢.
𝙏𝙝𝙚 𝙥𝙧𝙤𝙗𝙡𝙚𝙢 𝙞𝙨 𝙩𝙝𝙚 𝙢𝙞𝙨𝙨𝙞𝙣𝙜 𝙧𝙪𝙡𝙚 𝙛𝙤𝙧 𝙖𝙧𝙗𝙞𝙩𝙧𝙖𝙩𝙞𝙤𝙣.

When two good priorities compete, high-performing teams do not improvise.

They clarify in advance:
- who decides
- on what basis
- and when escalation is really needed

That is what keeps execution moving.

𝘽𝙚𝙘𝙖𝙪𝙨𝙚 𝙖𝙜𝙧𝙚𝙚𝙞𝙣𝙜 𝙤𝙣 𝙩𝙝𝙚 𝙙𝙞𝙧𝙚𝙘𝙩𝙞𝙤𝙣 𝙞𝙨 𝙣𝙤𝙩 𝙚𝙣𝙤𝙪𝙜𝙝.
𝙔𝙤𝙪 𝙖𝙡𝙨𝙤 𝙣𝙚𝙚𝙙 𝙘𝙡𝙖𝙧𝙞𝙩𝙮 𝙤𝙣 𝙬𝙝𝙖𝙩 𝙬𝙞𝙣𝙨 𝙬𝙝𝙚𝙣 𝙥𝙧𝙞𝙤𝙧𝙞𝙩𝙞𝙚𝙨 𝙘𝙤𝙢𝙥𝙚𝙩𝙚.

Quick question.
In your organisation, when two priorities clash, is the rule clear. Or does it depend on who speaks loudest?

In one leadership review, ten escalations landed on the table.
Most should never have reached the top.

A hospital leadership team looked at them together.

Staff allocation.
Patient flow.
Priority between two urgent cases.

Operational calls.

Nothing rare.

Yet all of them climbed the hierarchy.

Not because they were too hard.

Because the decision lines were unclear.

The top team should not be the backup plan for unclear roles.

But in many organisations, that is exactly what happens.

Middle managers sit in the pressure first.

Where teams must balance:
- Speed
- Safety
- Coordination

So they escalate.

Not always because the risk is high.

Often because the boundary is not clear.

Run this test.
Review your last ten escalations.

How many were really about:

- unclear authority
- unclear risk limits
- unclear priorities

If your Executive Committee keeps solving the same tensions, the system is teaching people to escalate.

That is not a people issue.

It is a design issue.

Clearer decision lines change the flow.

- Fewer escalations.
- Faster action.
- More leadership time for real leadership work.

If this helped, repost ♻️

“𝗚𝗮𝗺𝗲𝘀? 𝗙𝗼𝗿 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝘃𝗲𝘀? 𝗬𝗼𝘂’𝗿𝗲 𝗷𝗼𝗸𝗶𝗻𝗴, 𝗿𝗶𝗴𝗵𝘁?”


That was the reaction I got the first time I introduced serious games to a group of senior leaders.

Fast-forward a few hours—and those same leaders were leaning in, laughing, challenging each other, and seeing problems in a whole new light.

𝙏𝙪𝙧𝙣𝙨 𝙤𝙪𝙩, 𝙜𝙖𝙢𝙚𝙨 𝙙𝙤 𝙨𝙤𝙢𝙚𝙩𝙝𝙞𝙣𝙜 𝙩𝙧𝙖𝙙𝙞𝙩𝙞𝙤𝙣𝙖𝙡 𝙡𝙚𝙖𝙙𝙚𝙧𝙨𝙝𝙞𝙥 𝙩𝙤𝙤𝙡𝙨 𝙘𝙖𝙣’𝙩:

𝙏𝙝𝙚𝙮 𝙗𝙮𝙥𝙖𝙨𝙨 𝙩𝙝𝙚 𝙥𝙚𝙧𝙛𝙤𝙧𝙢𝙖𝙩𝙞𝙫𝙚 𝙡𝙖𝙮𝙚𝙧 𝙖𝙣𝙙 𝙪𝙣𝙡𝙤𝙘𝙠 𝙧𝙚𝙖𝙡 𝙞𝙣𝙨𝙞𝙜𝙝𝙩, 𝙛𝙖𝙨𝙩.

I’ve used serious games in pharma, health systems, public orgs—and 🆃🅷🅴🆈 🆆🅾🆁🅺.

Not because they’re fun (though they are).

But because 𝘁𝗵𝗲𝘆 𝗰𝗿𝗲𝗮𝘁𝗲 something most boardrooms lack: 𝘀𝗮𝗳𝗲 𝗽𝗿𝗲𝘀𝘀𝘂𝗿𝗲.


🔁 Teams test strategies in real-time.

💡 They make decisions under (simulated) stress.

🤝 They surface assumptions, blind spots, and leadership styles—in minutes, not months.


𝗜𝘁’𝘀 𝗻𝗼𝘁 𝘁𝗵𝗲𝗼𝗿𝘆. 𝗜𝘁’𝘀 𝗹𝗶𝘃𝗲𝗱 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲, 𝗰𝗼𝗺𝗽𝗿𝗲𝘀𝘀𝗲𝗱.
𝗔𝗻𝗱 𝘁𝗵𝗮𝘁’𝘀 𝘄𝗵𝗮𝘁 𝗺𝗮𝗸𝗲𝘀 𝗶𝘁 𝘀𝘁𝗶𝗰𝗸.

I’ve seen skeptical leaders shift their entire mindset after one game-based session.

✔️ Communication improves
✔️ Teams start trusting again
✔️ Change stops being “rolled out” and starts being owned

𝗚𝗮𝗺𝗲𝘀 𝗱𝗼𝗻’𝘁 𝘀𝗶𝗺𝗽𝗹𝗶𝗳𝘆 𝗿𝗲𝗮𝗹𝗶𝘁𝘆.
𝗧𝗵𝗲𝘆 𝗵𝗲𝗹𝗽 𝗽𝗲𝗼𝗽𝗹𝗲 𝗲𝗻𝗴𝗮𝗴𝗲 𝘄𝗶𝘁𝗵 𝗶𝘁 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁𝗹𝘆.


So let me ask you this:
𝙒𝙝𝙖𝙩 𝙬𝙤𝙪𝙡𝙙 𝙨𝙝𝙞𝙛𝙩 𝙞𝙣 𝙮𝙤𝙪𝙧 𝙩𝙚𝙖𝙢 𝙞𝙛 𝙡𝙚𝙖𝙧𝙣𝙞𝙣𝙜 𝙛𝙚𝙡𝙩 𝙡𝙞𝙠𝙚 𝙖 𝙘𝙝𝙖𝙡𝙡𝙚𝙣𝙜𝙚 𝙬𝙤𝙧𝙩𝙝 𝙥𝙡𝙖𝙮𝙞𝙣𝙜—𝙧𝙖𝙩𝙝𝙚𝙧 𝙩𝙝𝙖𝙣 𝙖 𝙥𝙧𝙤𝙘𝙚𝙨𝙨 𝙩𝙤 𝙚𝙣𝙙𝙪𝙧𝙚?

Have you ever tried serious games in your organisation?
If so—what happened? If not—what’s holding you back?

👇 Drop your story or your skepticism.
Let’s talk about what really drives transformation.

#LeadershipDevelopment #OrganisationalChange #SeriousGames #Gamification #BeezConsultingCH #TransformThroughPlay

Trust isn't built with policies or rules. That's a myth.

Trust is built in small moments, in habits, in rituals.

It's the simple things that make people feel safe, seen, and connected.

One client, a non-profit, was stuck behind silo walls. Leadership wanted a new "collaboration guideline", a fancy rulebook.

But rules don't create relationships. Rituals do.

So we co-created a simple ritual: monthly story circles.

No slides, reports, agendas. Just teams sharing challenges, lessons, real talk.

No formal meetings, no strategy sessions. Just stories.

It shifted everything.

Walls softened. Tone changed. Trust deepened.

Trust isn't written in policies. It's woven through routines everyone participates in.

Teams aren't just groups of people. They're patterns, habits, signals.

Build those. Trust sticks.

Forget rules. Focus on rituals.

Start small. Make it routine. Watch trust grow.

What's your next ritual?

Make it...

𝗥𝗲𝗼𝗿𝗴𝗮𝗻𝗶𝘀𝗮𝘁𝗶𝗼𝗻𝘀 𝗿𝗮𝗿𝗲𝗹𝘆 𝗳𝗮𝗶𝗹 𝗼𝗻 𝗽𝗮𝗽𝗲𝗿.
𝗧𝗵𝗲𝘆 𝗳𝗮𝗶𝗹 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝘁𝗲𝗮𝗺𝘀.


A new org chart is announced.

Roles are clarified.
Reporting lines look clean.

𝗧𝗵𝗿𝗲𝗲 𝗺𝗼𝗻𝘁𝗵𝘀 𝗹𝗮𝘁𝗲𝗿, 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗳𝗲𝗲𝗹𝘀 𝘀𝗹𝗼𝘄𝗲𝗿.

- Decisions take longer.
- Projects stall.
- Priorities collide.

𝗧𝗵𝗲 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗶𝘀 𝗻𝗼𝘁 𝘁𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺.
𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗶𝘀 𝘄𝗵𝗮𝘁 𝗵𝗮𝗽𝗽𝗲𝗻𝘀 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝘁𝗵𝗲 𝗯𝗼𝘅𝗲𝘀.

Reorganisations often leave three things implicit:

• who decides when priorities conflict
• who arbitrates between teams
• what should escalate and what should not

𝗪𝗵𝗲𝗻 𝘁𝗵𝗼𝘀𝗲 𝗿𝘂𝗹𝗲𝘀 𝘀𝘁𝗮𝘆 𝘃𝗮𝗴𝘂𝗲, 𝘁𝗲𝗮𝗺𝘀 𝗶𝗺𝗽𝗿𝗼𝘃𝗶𝘀𝗲.

They add meetings.
They escalate decisions.
They avoid risk.

𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝘀𝗹𝗼𝘄𝘀.
Not because people resist the strategy.
Because the interfaces were never clarified.

𝗜𝗻 𝗺𝗮𝗻𝘆 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀, 𝗳𝗶𝘅𝗶𝗻𝗴 𝘁𝗵𝗲𝘀𝗲 𝗶𝗻𝘃𝗶𝘀𝗶𝗯𝗹𝗲 𝗶𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲𝘀 𝘂𝗻𝗹𝗼𝗰𝗸𝘀 𝗺𝗼𝗿𝗲 𝗽𝗿𝗼𝗴𝗿𝗲𝘀𝘀 𝘁𝗵𝗮𝗻 𝗿𝗲𝗱𝗲𝘀𝗶𝗴𝗻𝗶𝗻𝗴 𝘁𝗵𝗲 𝗼𝗿𝗴 𝗰𝗵𝗮𝗿𝘁 𝗮𝗴𝗮𝗶𝗻.

Sometimes the real work starts after the reorganisation.

If you have experienced a reorganisation:

Where did confusion appear first?

• roles
• decisions
• priorities
• interfaces between teams

Curious to hear your experience.

𝗧𝗿𝘆 𝘁𝗵𝗶𝘀 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗻𝗲𝘅𝘁 𝗲𝘅𝗲𝗰𝘂𝘁𝗶𝘃𝗲 𝗺𝗲𝗲𝘁𝗶𝗻𝗴.
Not as a brainstorming exercise.
As a leadership check.

𝘼𝙨𝙠 𝙤𝙣𝙚 𝙨𝙞𝙢𝙥𝙡𝙚 𝙦𝙪𝙚𝙨𝙩𝙞𝙤𝙣:
"𝘿𝙚𝙛𝙞𝙣𝙚 𝙜𝙧𝙤𝙬𝙩𝙝, 𝙬𝙞𝙩𝙝𝙤𝙪𝙩 𝙪𝙨𝙞𝙣𝙜 𝙣𝙪𝙢𝙗𝙚𝙧𝙨."

No budgets.
No volumes.
No headcount.
No new sites.

Just... growth.

𝙄𝙩'𝙨 𝙪𝙣𝙘𝙤𝙢𝙛𝙤𝙧𝙩𝙖𝙗𝙡𝙚 𝙖𝙩 𝙛𝙞𝙧𝙨𝙩.
Numbers feel safe. They're concrete.
They give the illusion of control.

But here's what many healthcare leaders are realizing:
“Bigger” doesn’t automatically mean “better.”
Sometimes, it's just the same problems on a larger scale.
More friction, more delays, more chaos.

So take the numbers away and ask again:
What improves when we grow?

If the answer isn't one of these, it's probably not growth.
It's expansion.

- Access gets easier (less waiting, fewer dead ends)
- Continuity becomes real (handovers don't reset the patient story)
- Information flows once (patients and clinicians stop repeating work)
- Trust increases (patients feel safe; teams feel supported)
- Teams recover (less overload, more capacity to improve)

This is why Europe is shifting from bigger to better.

𝙉𝙤𝙩 𝙗𝙚𝙘𝙖𝙪𝙨𝙚 “𝙗𝙞𝙜𝙜𝙚𝙧” 𝙞𝙨 𝙬𝙧𝙤𝙣𝙜.
𝘽𝙪𝙩 𝙗𝙚𝙘𝙖𝙪𝙨𝙚 𝙩𝙝𝙚 𝙣𝙚𝙭𝙩 𝙙𝙚𝙘𝙖𝙙𝙚 𝙬𝙞𝙡𝙡 𝙧𝙚𝙬𝙖𝙧𝙙 𝙨𝙮𝙨𝙩𝙚𝙢𝙨 𝙩𝙝𝙖𝙩 𝙨𝙘𝙖𝙡𝙚 𝙦𝙪𝙖𝙡𝙞𝙩𝙮, 𝙣𝙤𝙩 𝙟𝙪𝙨𝙩 𝙘𝙖𝙥𝙖𝙘𝙞𝙩𝙮.

That's the essence of "From Bigger to Better."

The real measure of growth in healthcare might be:

How reliably can your system deliver a good day, for a patient and a clinician?

Stop focusing on size. Focus on impact.

🔗 Read more here: https://lnkd.in/g365KBVP

#HealthcareLeadership #Strategy #HospitalManagement #DigitalHealth #PatientExperience #HealthSystems

They say leadership needs more ownership.


But last week, I saw the real problem.

A team says, "We need more ownership."
Ten minutes later, a decision surfaces.
Not big. Not tiny. Just uncomfortable.
Someone suddenly suggests, "Let's ask the boss. Just to be safe."

Everyone nodded.

That’s how escalation culture grows.
Quietly. Repeatedly. Reasonably.

Teams escalate because boundaries are unclear.
Managers escalate because trade-offs feel risky.
Executives step in because speed matters.

And the system learns.
Overload the top.
Stop the middle from deciding.
Slow down execution.

Here are three signs you're defaulting to escalation:
• Decisions travel upward before they move forward
• Senior forums keep revisiting the same topics
• Teams wait for approval even when the answer is obvious

This isn’t a talent issue.
It’s an operating habit.

Fix the execution gap by making one bold move:
Senior leaders decide what they will stop deciding.
Set clear owners.
Define clear thresholds.
Establish clear escalation rules.

𝙄𝙛 𝙚𝙫𝙚𝙧𝙮𝙩𝙝𝙞𝙣𝙜 𝙚𝙨𝙘𝙖𝙡𝙖𝙩𝙚𝙨, 𝙣𝙤𝙩𝙝𝙞𝙣𝙜 𝙢𝙤𝙫𝙚𝙨.

𝙎𝙩𝙖𝙧𝙩 𝙩𝙝𝙚𝙧𝙚.
𝘾𝙝𝙖𝙣𝙜𝙚 𝙩𝙝𝙖𝙩.
𝙒𝙖𝙩𝙘𝙝 𝙚𝙭𝙚𝙘𝙪𝙩𝙞𝙤𝙣 𝙨𝙥𝙚𝙚𝙙 𝙪𝙥.

𝗧𝗲𝗮𝗺𝘀 𝗿𝗮𝗿𝗲𝗹𝘆 𝗿𝗲𝘀𝗶𝘀𝘁 𝗰𝗵𝗮𝗻𝗴𝗲.
𝗧𝗵𝗲𝘆 𝗿𝗲𝘃𝗲𝗿𝘁 𝘁𝗼 𝘄𝗵𝗮𝘁 𝗳𝗲𝗲𝗹𝘀 𝘀𝗮𝗳𝗲.


A new initiative launches.

Workshops are organised.
People align.
Everyone agrees on the direction.

Three weeks later, daily work looks... familiar.

Old habits return.

Not because people rejected the change.
Because systems still reward the old behaviour.

Under pressure, teams return to what feels reliable.

That is why culture change cannot rely on agreement alone.

Execution shifts when three things change together:

• decision rules
• operational rhythms
• reinforcement signals

Otherwise the organisation quietly slides back to its previous habits.

Agreement is easy.
Reinforcement is what changes behaviour.

Where do teams in your organisation tend to fall back to old habits?

Why Change at Work Doesnt Stick

𝙔𝙤𝙪𝙧 𝙩𝙧𝙖𝙣𝙨𝙛𝙤𝙧𝙢𝙖𝙩𝙞𝙤𝙣 𝙙𝙤𝙚𝙨𝙣’𝙩 𝙡𝙞𝙫𝙚 𝙞𝙣 𝙮𝙤𝙪𝙧 𝙨𝙩𝙧𝙖𝙩𝙚𝙜𝙮.
𝙄𝙩 𝙡𝙞𝙫𝙚𝙨 (𝙤𝙧 𝙙𝙞𝙚𝙨) 𝙞𝙣 𝙢𝙞𝙙𝙙𝙡𝙚 𝙢𝙖𝙣𝙖𝙜𝙚𝙢𝙚𝙣𝙩.

Not because they “support execution.”
Because 𝘁𝗵𝗲𝘆 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝘀𝘆𝘀𝘁𝗲𝗺 𝗼𝗳 𝘁𝗵𝗲 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀.

You can have a sharp strategy, strong sponsorship, and polished communication...

and still get slow adoption, initiative fatigue, and endless “alignment” meetings.

When middle management isn’t activated, three things happen:

1. Strategy stays abstract
2. Frontline energy drops
3. Execution turns into negotiation

And most executive teams respond the same way: 
- Push harder.
- More town halls. 
- More dashboards. 
- More follow-ups.

𝙏𝙝𝙖𝙩 𝙧𝙖𝙧𝙚𝙡𝙮 𝙛𝙞𝙭𝙚𝙨 𝙞𝙩.
𝙄𝙩 𝙟𝙪𝙨𝙩 𝙘𝙤𝙣𝙨𝙪𝙢𝙚𝙨 𝙢𝙤𝙧𝙚 𝙡𝙚𝙖𝙙𝙚𝙧𝙨𝙝𝙞𝙥 𝙗𝙖𝙣𝙙𝙬𝙞𝙙𝙩𝙝.

𝗔 𝗿𝗲𝗮𝗹 𝘀𝘁𝗼𝗿𝘆
During a recent project, we were supporting a leadership team rolling out a 𝙣𝙚𝙬 𝙤𝙥𝙚𝙧𝙖𝙩𝙞𝙣𝙜 𝙢𝙤𝙙𝙚𝙡 𝙖𝙘𝙧𝙤𝙨𝙨 40 𝙨𝙞𝙩𝙚𝙨. 

The 𝙨𝙩𝙧𝙖𝙩𝙚𝙜𝙮 𝙬𝙖𝙨 𝙘𝙡𝙚𝙖𝙧. The comms kit was spotless.

Three months later, 𝙖𝙙𝙤𝙥𝙩𝙞𝙤𝙣 𝙡𝙤𝙤𝙠𝙚𝙙 𝙥𝙖𝙩𝙘𝙝𝙮.

Not because people were resisting change.
Because the plan looked perfect on slides and different on the floor.

Middle managers did what strong operators always do: they made it work.
They created 𝙬𝙤𝙧𝙠𝙖𝙧𝙤𝙪𝙣𝙙𝙨.

𝙎𝙤 𝙗𝙚𝙛𝙤𝙧𝙚 𝙩𝙝𝙚 𝙣𝙚𝙭𝙩 𝙬𝙖𝙫𝙚, 𝙬𝙚 𝙢𝙖𝙙𝙚 𝙤𝙣𝙚 𝙨𝙢𝙖𝙡𝙡 𝙨𝙝𝙞𝙛𝙩. 

We invited 12 𝙢𝙞𝙙𝙙𝙡𝙚 𝙢𝙖𝙣𝙖𝙜𝙚𝙧𝙨 into a two-hour working session — not to brief them, but to 𝙗𝙪𝙞𝙡𝙙 𝙬𝙞𝙩𝙝 𝙩𝙝𝙚𝙢.

They reshaped the rollout 𝙞𝙣𝙩𝙤 𝙨𝙤𝙢𝙚𝙩𝙝𝙞𝙣𝙜 𝙩𝙚𝙖𝙢𝙨 𝙘𝙤𝙪𝙡𝙙 𝙖𝙘𝙩𝙪𝙖𝙡𝙡𝙮 𝙧𝙪𝙣.

After that: fewer exceptions, faster adoption, and far fewer escalations landing on the executive team’s desk.

That’s the point.

𝗠𝗶𝗱𝗱𝗹𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗮 𝗹𝗮𝘆𝗲𝗿 𝘁𝗼 𝗮𝗹𝗶𝗴𝗻.
𝗧𝗵𝗲𝘆 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗹𝗮𝘆𝗲𝗿 𝘁𝗵𝗮𝘁 𝗰𝗿𝗲𝗮𝘁𝗲𝘀 𝗯𝗲𝗹𝗶𝗲𝗳, 𝘀𝗲𝘁𝘀 𝗿𝗲𝗮𝗹 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝗲𝘀, 𝗮𝗻𝗱 𝘁𝘂𝗿𝗻𝘀 𝗶𝗻𝘁𝗲𝗻𝘁 𝗶𝗻𝘁𝗼 𝗱𝗮𝗶𝗹𝘆 𝗵𝗮𝗯𝗶𝘁𝘀.

If you want faster adoption, less rework, and fewer “why isn’t this moving?” conversations, focus here:

👉 𝗕𝗿𝗶𝗻𝗴 𝘁𝗵𝗲𝗺 𝗶𝗻 𝗯𝗲𝗳𝗼𝗿𝗲 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗳𝗶𝗻𝗮𝗹
👉 𝗚𝗶𝘃𝗲 𝘁𝗵𝗲𝗺 𝗮𝘂𝘁𝗵𝗼𝗿𝗶𝘁𝘆 𝘁𝗼 𝗮𝗱𝗮𝗽𝘁 𝘁𝗵𝗲 𝗵𝗼𝘄
👉 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗿𝗲𝗰𝘂𝗿𝗿𝗶𝗻𝗴 𝗳𝗼𝗿𝘂𝗺 𝘄𝗵𝗲𝗿𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝘁𝗿𝘂𝘁𝗵 𝗿𝗲𝘀𝗵𝗮𝗽𝗲𝘀 𝗱𝗶𝗿𝗲𝗰𝘁𝗶𝗼𝗻
👉 𝗥𝗲𝘄𝗮𝗿𝗱 𝗮𝗱𝗼𝗽𝘁𝗶𝗼𝗻 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀 — 𝗻𝗼𝘁 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗰𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝗰𝗲

This isn’t delegation.
It’s decision design.

𝗪𝗵𝗶𝗰𝗵 𝗺𝗶𝗱𝗱𝗹𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀 𝘄𝗶𝗹𝗹 𝘆𝗼𝘂 𝗶𝗻𝘃𝗶𝘁𝗲 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗻𝗲𝘅𝘁 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝘀𝗲𝘀𝘀𝗶𝗼𝗻, 𝗻𝗼𝘁 𝘁𝗼 𝗯𝗿𝗶𝗲𝗳, 𝗯𝘂𝘁 𝘁𝗼 𝗰𝗼-𝗱𝗲𝘃𝗲𝗹𝗼𝗽?

They agreed on everything.
Values. Model. Pathway.


Smooth approval.

Three weeks later, reality hit.

Clinicians adjusted steps to keep care moving.
Middle managers absorbed the friction.
Escalations climbed.

No one resisted change.

They just did not trust the system enough to rely on it.

One line from that conversation stayed with me:

“We support it. We just need to see if it actually works.”

That is the gap.
Agreement is not clarity.

Here is the proof.

If one team follows the pathway and gets punished with delay, while another bypasses it and gets praised for “speed”, people learn fast.

The pathway is optional.

That’s a HABITS problem.

Not motivation.
Reinforcement.

Under pressure, teams do what feels safe.
They improvise.
They escalate.
They protect the shift.

It keeps patients safe today.
It slows the system tomorrow.

In Switzerland, where reliability is part of trust, inconsistency is expensive.

So a simple test for leaders:

When someone follows the agreed way and it creates tension, do you back them?

Values align.
Habits decide speed.

𝗠𝗼𝘀𝘁 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗲𝘀 𝗶𝗻 𝗟𝗶𝗳𝗲 𝗦𝗰𝗶𝗲𝗻𝗰𝗲𝘀 𝗱𝗼𝗻'𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗳𝗮𝗶𝗹.
𝗧𝗵𝗲𝘆 𝘀𝘁𝗮𝗹𝗹, 𝗿𝗶𝗴𝗵𝘁 𝗮𝘁 𝘁𝗵𝗲 𝘁𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻 𝗹𝗮𝘆𝗲𝗿.


Not in the boardroom. 
Not in R&D. 
But in the space that must turn global intent into local action.

That's where the real bottleneck lives.

Affiliate leaders. 
Medical affairs. 
Market access. 
Regulatory teams. 
Clinical ops. 
Brand teams.

They sit between: 

- global ambition and local constraints 
- speed and compliance 
- one operating model and many market realities 

And they absorb the collision.

Here's the truth: 

𝙒𝙝𝙚𝙣 𝙚𝙭𝙚𝙘𝙪𝙩𝙞𝙤𝙣 𝙨𝙡𝙤𝙬𝙨 𝙙𝙤𝙬𝙣, 𝙞𝙩'𝙨 𝙧𝙖𝙧𝙚𝙡𝙮 𝙖 𝙨𝙩𝙧𝙖𝙩𝙚𝙜𝙮 𝙥𝙧𝙤𝙗𝙡𝙚𝙢. 
𝙄𝙩'𝙨 𝙖 𝙙𝙚𝙘𝙞𝙨𝙞𝙤𝙣 𝙨𝙮𝙨𝙩𝙚𝙢 𝙥𝙧𝙤𝙗𝙡𝙚𝙢.

Same symptoms, every time: 

- decisions dragged from days into weeks 
- priorities stacking up, never stopping 
- governance multiplying into delays 
- accountability lost across functions 
- "alignment" becomes the work, not the outcome 

Not because people aren't capable. 

Because the system asks the middle layer to resolve contradictions without giving them the authority, capacity, or clarity to do it.

𝙒𝙖𝙣𝙩 𝙛𝙖𝙨𝙩𝙚𝙧 𝙡𝙖𝙪𝙣𝙘𝙝𝙚𝙨, 𝙗𝙚𝙩𝙩𝙚𝙧 𝙖𝙙𝙤𝙥𝙩𝙞𝙤𝙣? 
𝘿𝙤𝙣'𝙩 𝙟𝙪𝙨𝙩 𝙪𝙥𝙜𝙧𝙖𝙙𝙚 𝙮𝙤𝙪𝙧 𝙨𝙩𝙧𝙖𝙩𝙚𝙜𝙮. 
𝙐𝙥𝙜𝙧𝙖𝙙𝙚 𝙩𝙝𝙚 𝙩𝙧𝙖𝙣𝙨𝙡𝙖𝙩𝙞𝙤𝙣 𝙡𝙖𝙮𝙚𝙧. 

- Make decision rights clear. 
- Cut down competing priorities. 
- Protect execution capacity. 
- Push trade-offs upfront, not at the last minute. 
- Simplify governance that's just adding latency, not safety. 

The next decade won't go to companies running the most initiatives. 

It will go to those that can scale clarity across markets without losing compliance, trust, or momentum.

Here's the leadership test: 
Can your organization reliably translate strategy into action? 

Market by market. 
Function by function. 

Or are you still stuck translating process into delays?

Your move.

“𝙒𝙚 𝙝𝙖𝙫𝙚 𝙖 𝙘𝙡𝙚𝙖𝙧 𝙨𝙩𝙧𝙖𝙩𝙚𝙜𝙮.”
𝘼𝙣𝙙 𝙮𝙚𝙩... 𝙘𝙝𝙖𝙣𝙜𝙚 𝙨𝙡𝙤𝙬𝙨 𝙙𝙤𝙬𝙣.


New initiatives launch.
Town halls happen.
Decks circulate.

But somewhere between intent and execution, momentum fades.

It’s easy to say:
“Change gets stuck in the middle.”

More often?

We leave it there.

Middle managers in healthcare and life sciences sit at the pressure point of the system.

They translate strategy into daily decisions.
They absorb competing priorities.
They manage operational risk.
They protect their teams from overload.

And we ask them to do all of this...
while driving transformation.

If change feels slow, look at the conditions around the middle layer:

Do they have real decision rights?

Are priorities being reduced—or just added?

Is reporting multiplying faster than clarity?

Do they have protected time to lead, not just manage?

Strategy doesn’t fail because the middle resists it.

It stalls because the system overloads the people responsible for translating it.

If you want transformation to stick, don’t bypass the middle.

Back it.

That’s the core idea in our latest piece:
“Stop Blaming the Middle. Start Backing Your Managers.”

Because sustainable change doesn’t scale through pressure.

It scales through clarity, space, and leadership capacity.

🔗 Read more here: https://lnkd.in/eDn-pzAe

#HealthcareLeadership #LifeSciences #HospitalManagement #OrganizationalDesign #Transformation #Leadership

𝗖𝗵𝗮𝗻𝗴𝗲𝗿 𝗹’𝗼𝗿𝗴𝗮𝗻𝗶𝗴𝗿𝗮𝗺𝗺𝗲 𝗻𝗲 𝗰𝗵𝗮𝗻𝗴𝗲 𝗽𝗿𝗲𝘀𝗾𝘂𝗲 𝗷𝗮𝗺𝗮𝗶𝘀 𝗹’𝗼𝗿𝗴𝗮𝗻𝗶𝘀𝗮𝘁𝗶𝗼𝗻.

Les organigrammes changent.
Mais ce qui bloque est souvent ailleurs.

Voici 5 réalités que les dirigeants découvrent pendant une réorganisation.

1️⃣ 𝗖𝗵𝗮𝗻𝗴𝗲𝗿 𝗹𝗲𝘀 𝗰𝗮𝘀𝗲𝘀 𝗻𝗲 𝗰𝗵𝗮𝗻𝗴𝗲 𝗽𝗮𝘀 𝗹𝗲𝘀 𝗿é𝗳𝗹𝗲𝘅𝗲𝘀

Comme l’a très bien résumé @𝘀𝗮𝗻𝗱𝗿𝗮 𝗸𝗶𝗲𝗿𝘀 :

“𝘾𝙝𝙖𝙣𝙜𝙚𝙧 𝙡𝙚𝙨 𝙘𝙖𝙨𝙚𝙨 𝙨𝙖𝙣𝙨 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙡𝙚𝙨 𝙧é𝙛𝙡𝙚𝙭𝙚𝙨, 𝙘’𝙚𝙨𝙩 𝙙é𝙥𝙡𝙖𝙘𝙚𝙧 𝙡𝙚 𝙥𝙧𝙤𝙗𝙡è𝙢𝙚.”

Les silos se reforment vite.
Les décisions remontent.
Les habitudes reprennent le dessus.

2️⃣ 𝗔𝗽𝗹𝗮𝘁𝗶𝗿 𝗹’𝗼𝗿𝗴𝗮𝗻𝗶𝗴𝗿𝗮𝗺𝗺𝗲 𝗻𝗲 𝘀𝘂𝗳𝗳𝗶𝘁 𝗽𝗮𝘀

On parle souvent d’organisation “plate”.

𝙈𝙖𝙞𝙨 𝙨𝙞 𝙡𝙚𝙨 𝙙𝙧𝙤𝙞𝙩𝙨 𝙙𝙚 𝙙é𝙘𝙞𝙨𝙞𝙤𝙣 𝙣𝙚 𝙨𝙤𝙣𝙩 𝙥𝙖𝙨 𝙘𝙡𝙖𝙧𝙞𝙛𝙞é𝙨, 𝙩𝙤𝙪𝙩 𝙧𝙚𝙢𝙤𝙣𝙩𝙚 𝙦𝙪𝙖𝙣𝙙 𝙢ê𝙢𝙚. 𝙀𝙩 𝙡’𝙖𝙜𝙞𝙡𝙞𝙩é 𝙥𝙧𝙤𝙢𝙞𝙨𝙚 𝙙𝙞𝙨𝙥𝙖𝙧𝙖î𝙩.

3️⃣ 𝗜𝗺𝗽𝗹𝗶𝗾𝘂𝗲𝗿 𝗹𝗲𝘀 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀 𝗽𝗿𝗲𝗻𝗱 𝗱𝘂 𝘁𝗲𝗺𝗽𝘀...

C’est vrai.

Mais ne pas le faire en prend encore plus.

Car les semaines suivantes sont souvent remplies de :
• validations inutiles
• arbitrages flous
• malentendus

4️⃣ 𝗟𝗲𝘀 𝗲𝗺𝗮𝗶𝗹𝘀 𝗻’𝗮𝗹𝗶𝗴𝗻𝗲𝗻𝘁 𝗽𝗮𝘀 𝘂𝗻𝗲 𝗼𝗿𝗴𝗮𝗻𝗶𝘀𝗮𝘁𝗶𝗼𝗻

Ils informent.

Mais ils ne clarifient pas :
• les arbitrages
• les priorités
• les tensions réelles

𝘾𝙚𝙨 𝙘𝙝𝙤𝙨𝙚𝙨-𝙡à 𝙨𝙚 𝙧è𝙜𝙡𝙚𝙣𝙩 𝙙𝙖𝙣𝙨 𝙡𝙖 𝙘𝙤𝙣𝙫𝙚𝙧𝙨𝙖𝙩𝙞𝙤𝙣.

5️⃣ 𝗟𝗲𝘀 𝗵𝗮𝗯𝗶𝘁𝘂𝗱𝗲𝘀 𝘀𝗼𝗻𝘁 𝗹𝗲 𝘃𝗿𝗮𝗶 𝘀𝘆𝘀𝘁è𝗺𝗲

Un nouvel organigramme ne remplace pas un système invisible.

Ce système est fait de :
• réflexes
• circuits informels
• décisions implicites

𝙏𝙖𝙣𝙩 𝙦𝙪’𝙞𝙡 𝙣’𝙚𝙨𝙩 𝙥𝙖𝙨 𝙧𝙚𝙣𝙙𝙪 𝙫𝙞𝙨𝙞𝙗𝙡𝙚, 𝙞𝙡 𝙧𝙚𝙥𝙧𝙚𝙣𝙙 𝙩𝙤𝙪𝙟𝙤𝙪𝙧𝙨 𝙡𝙚 𝙙𝙚𝙨𝙨𝙪𝙨.


𝙇𝙖 𝙫𝙧𝙖𝙞𝙚 𝙦𝙪𝙚𝙨𝙩𝙞𝙤𝙣 𝙙𝙖𝙣𝙨 𝙪𝙣𝙚 𝙧é𝙤𝙧𝙜𝙖𝙣𝙞𝙨𝙖𝙩𝙞𝙤𝙣 n’est peut-être pas :

“Quel organigramme choisir ?”

Mais plutôt :

𝙌𝙪𝙚𝙡𝙡𝙚𝙨 𝙙é𝙘𝙞𝙨𝙞𝙤𝙣𝙨, 𝙧è𝙜𝙡𝙚𝙨 𝙚𝙩 𝙘𝙤𝙣𝙫𝙚𝙧𝙨𝙖𝙩𝙞𝙤𝙣𝙨 𝙫𝙤𝙣𝙩 𝙧é𝙚𝙡𝙡𝙚𝙢𝙚𝙣𝙩 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 ?


Si vous avez déjà vécu une réorganisation :

👉 Qu’est-ce qui a été le plus difficile à clarifier ?

Les rôles ?
Les décisions ?
Les priorités ?

Je suis curieuse de lire vos expériences.

Le vrai test d’une organisation ne se voit pas dans l’organigramme.
Il se voit entre les cases.

𝗧𝗿𝗼𝗶𝘀 𝘀𝗲𝗺𝗮𝗶𝗻𝗲𝘀 pour valider un nouvel organigramme.
𝗦𝗶𝘅 𝗺𝗼𝗶𝘀 plus tard, en réunion :

“Attendez... qui décide, au final ?”

C’est souvent là que la réorganisation montre sa limite.

Sur le papier, tout est clair.
Dans la réalité, les anciens réflexes reviennent vite.

Les équipes continuent de solliciter les mêmes personnes.
Les décisions prennent les mêmes détours.
Les priorités se contredisent.
Les silos réapparaissent.

Pourquoi ?

Parce qu’une réorganisation ne change pas, à elle seule, le vrai système.

Le vrai système, ce sont :

• les réflexes
• les circuits informels
• les arbitrages du quotidien
• les décisions implicites
• les zones grises entre équipes

Autrement dit :

changer les cases ne suffit pas.

Il faut aussi clarifier :

• qui décide quoi
• jusqu’où chacun peut aller
• quand il faut arbitrer
• ce qui doit remonter
• ce qui ne devrait plus remonter

Sinon, on redessine.
Mais on ne change pas grand-chose.

Le vrai test d’une réorganisation, ce n’est pas la slide finale.
C’est le mardi matin qui suit.
Quand deux équipes ne sont pas alignées.
Quand une priorité en contredit une autre.
Quand quelqu’un doit trancher.

Et que tout le monde regarde autour de la table.

Après une réorganisation, où voyez-vous le plus de confusion ?

• dans les rôles
• dans les décisions
• dans les priorités
• ou dans les interfaces entre équipes ?

Je suis curieuse de lire vos retours.

Et si vous êtes en plein dedans, je peux aussi partager 5 questions simples pour repérer rapidement où ça coince vraiment.

𝙌𝙪𝙖𝙣𝙙 𝙪𝙣𝙚 𝙧é𝙤𝙧𝙜𝙖𝙣𝙞𝙨𝙖𝙩𝙞𝙤𝙣 𝙗𝙡𝙤𝙦𝙪𝙚, 𝙡𝙚 𝙥𝙧𝙤𝙗𝙡è𝙢𝙚 𝙣’𝙚𝙨𝙩 𝙥𝙧𝙚𝙨𝙦𝙪𝙚 𝙟𝙖𝙢𝙖𝙞𝙨 𝙡’𝙤𝙧𝙜𝙖𝙣𝙞𝙜𝙧𝙖𝙢𝙢𝙚.
𝘾’𝙚𝙨𝙩 𝙡’𝙞𝙣𝙫𝙚𝙧𝙨𝙚.


On change les cases.
Mais pas les vrais arbitrages.

Alors, au début, tout le monde y croit.

Les rôles semblent clairs.
La direction est posée.
Le message a été envoyé.

Puis la réalité reprend la main.

Les priorités s’entrechoquent.
Les projets ralentissent.
Les décisions remontent.
Et les vieux réflexes reviennent.

Pas par résistance.

Parce que personne ne sait vraiment où s’arrête son pouvoir d’action.

Sur un projet récent, on n’a pas commencé par “mieux communiquer la stratégie”.

On a commencé ailleurs.

Avec trois questions très simples.

1️⃣ Qui décide quand deux priorités entrent en conflit ?

2️⃣ Qui tranche vraiment quand un projet bloque ?

3️⃣ Et combien de niveaux d’approbation faut-il vraiment ?

2 ?
4 ?
7 ?

C’est souvent là que le vrai sujet apparaît.

Pas dans les slides.
Pas dans les intentions.
Dans le quotidien.

Quand les managers comprennent la logique derrière les choix, quelque chose change.

Ils arrêtent d’exécuter pour rester couverts.

Ils commencent à prendre la responsabilité du comment.

Et à partir de là, la stratégie cesse d’être un discours.

Elle devient concrète.
Elle devient utile.
Elle devient visible.

Même un mardi matin.
Même sous pression.

Une réorganisation ne crée pas la clarté.

La clarté arrive quand chacun sait :
qui décide,
sur quoi,
et jusqu’où il peut avancer sans faire remonter toute la chaîne.

C’est souvent ce point qui débloque tout.

Si votre organisation tourne encore au ralenti après une réorg, il existe 5 questions simples pour voir très vite où ça coince vraiment.

Ce sont rarement les cases.
Presque toujours les arbitrages.

Partagez ce post si vous pensez qu'il peut aider votre équipe à avancer.

𝗛𝗼𝘀𝗽𝗶𝘁𝗮𝗹𝘀 𝗱𝗼 𝗻𝗼𝘁 𝗹𝗮𝗰𝗸 𝗲𝗳𝗳𝗼𝗿𝘁.
𝗧𝗵𝗲𝘆 𝗹𝗮𝗰𝗸 𝘂𝘀𝗮𝗯𝗹𝗲 𝘁𝗶𝗺𝗲.

Pressure builds fast.
Flow breaks quietly.
Care pays the price.

More work will not fix it.
More reporting will not fix it.
Friction is the real leak.

Time shortages are now normal.
Workflow drives outcomes.
So does staff energy. 

Mastering healthcare efficiency

Thrive creates capacity inside the system.
Cut inefficiencies.
Streamline work.
Use resources better. 

Mastering healthcare efficiency

Start with bottlenecks.
Remove repeat time drains.
Make handovers reliable.
Clarify who decides what. 

Mastering healthcare efficiency

Close workflow gaps.
Improve day to day communication.
Support swift, informed decisions. 

Mastering healthcare efficiency

This is how capacity comes back.
Not by pushing harder.
By fixing how work moves.


𝗧𝗵𝗶𝘀 𝗶𝘀 𝗵𝗼𝘄 𝗰𝗮𝗽𝗮𝗰𝗶𝘁𝘆 𝗰𝗼𝗺𝗲𝘀 𝗯𝗮𝗰𝗸. 

𝗡𝗼𝘁 𝗯𝘆 𝗽𝘂𝘀𝗵𝗶𝗻𝗴 𝗵𝗮𝗿𝗱𝗲𝗿. 
𝗕𝘆 𝗳𝗶𝘅𝗶𝗻𝗴 𝗵𝗼𝘄 𝘄𝗼𝗿𝗸 𝗺𝗼𝘃𝗲𝘀. 

𝙊𝙣𝙚 𝙨𝙞𝙢𝙥𝙡𝙚 𝙘𝙝𝙚𝙘𝙠: 𝙒𝙝𝙚𝙧𝙚 𝙙𝙤𝙚𝙨 𝙬𝙤𝙧𝙠 𝙨𝙡𝙤𝙬 𝙙𝙤𝙬𝙣 𝙢𝙤𝙨𝙩 𝙞𝙣 𝙮𝙤𝙪𝙧 𝙤𝙧𝙜𝙖𝙣𝙞𝙨𝙖𝙩𝙞𝙤𝙣?

Mastering Healthcare Efficiency

𝗟𝗮 𝘀𝘁𝗿𝗮𝘁é𝗴𝗶𝗲, 𝗰’𝗲𝘀𝘁 𝘂𝗻𝗲 𝗹𝗮𝗻𝗴𝘂𝗲.
𝗘𝘁 𝗱𝗮𝗻𝘀 𝗯𝗲𝗮𝘂𝗰𝗼𝘂𝗽 𝗱’𝗼𝗿𝗴𝗮𝗻𝗶𝘀𝗮𝘁𝗶𝗼𝗻𝘀 𝘀𝗮𝗻𝘁é / 𝗹𝗶𝗳𝗲 𝘀𝗰𝗶𝗲𝗻𝗰𝗲𝘀, 𝗼𝗻 𝗼𝘂𝗯𝗹𝗶𝗲 𝘂𝗻 𝗱é𝘁𝗮𝗶𝗹 :
𝗲𝗹𝗹𝗲 𝗻𝗲 𝘀𝗲 𝗽𝗮𝗿𝗹𝗲 𝗽𝗮𝘀 𝘁𝗼𝘂𝘁𝗲 𝘀𝗲𝘂𝗹𝗲.


𝙀𝙣𝙩𝙧𝙚 𝙡𝙚 𝘾𝙊𝘿𝙄𝙍 𝙚𝙩 𝙡𝙚 𝙩𝙚𝙧𝙧𝙖𝙞𝙣, 𝙞𝙡 𝙮 𝙖 𝙙𝙚𝙨 𝙩𝙧𝙖𝙙𝙪𝙘𝙩𝙚𝙪𝙧𝙨.

Vos 𝙘𝙖𝙙𝙧𝙚𝙨 𝙞𝙣𝙩𝙚𝙧𝙢é𝙙𝙞𝙖𝙞𝙧𝙚𝙨.

Ils prennent :
- “Améliorer l’expérience patient.”
- “Réduire les délais.”
- “Renforcer la conformité.”

... et ils doivent le traduire en :

✅ 𝙦𝙪𝙞 𝙛𝙖𝙞𝙩 𝙦𝙪𝙤𝙞, dès lundi
✅ quels 𝙖𝙧𝙗𝙞𝙩𝙧𝙖𝙜𝙚𝙨 on accepte
✅ 𝙘𝙚 𝙦𝙪’𝙤𝙣 𝙖𝙧𝙧ê𝙩𝙚 pour libérer du temps 
✅ comment on gère le 𝙧𝙞𝙨𝙦𝙪𝙚 𝙤𝙥é𝙧𝙖𝙩𝙞𝙤𝙣𝙣𝙚𝙡
✅ comment on 𝙜𝙖𝙧𝙙𝙚 𝙡’é𝙦𝙪𝙞𝙥𝙚 𝙙𝙚𝙗𝙤𝙪𝙩


Et si la transformation “ralentit”, ce n’est pas parce que “le middle résiste”.

C’est souvent parce qu’𝗼𝗻 𝗮 𝘀𝗼𝘂𝘀-é𝗾𝘂𝗶𝗽é 𝗹𝗮 𝗳𝗼𝗻𝗰𝘁𝗶𝗼𝗻 𝗱𝗲 𝘁𝗿𝗮𝗱𝘂𝗰𝘁𝗶𝗼𝗻.

👉 𝗣𝗮𝘀 𝗱𝗲 𝘃𝗿𝗮𝗶𝘀 droits de décision = traduction floue.
👉 𝗧𝗿𝗼𝗽 𝗱𝗲 priorités = messages contradictoires.
👉 𝗧𝗿𝗼𝗽 𝗱𝗲 reporting = temps volé à l’exécution.
👉 𝗭é𝗿𝗼 𝗲𝘀𝗽𝗮𝗰𝗲 𝗽𝗼𝘂𝗿 leader = pilotage automatique.

Résultat :
La stratégie arrive sur le terrain... comme un mauvais sous-titrage.
On croit qu’on s’est compris.
On ne s’est pas compris.

Si vous voulez que ça accélère, ne demandez pas aux traducteurs de “faire un effort”.

𝗗𝗼𝗻𝗻𝗲𝘇-𝗹𝗲𝘂𝗿 : 𝗰𝗹𝗮𝗿𝘁é, 𝗺𝗮𝗿𝗴𝗲 𝗱𝗲 𝗺𝗮𝗻œ𝘂𝘃𝗿𝗲, 𝘁𝗲𝗺𝗽𝘀 𝗽𝗿𝗼𝘁é𝗴é, 𝗽𝗿𝗶𝗼𝗿𝗶𝘁é𝘀 𝘁𝗿𝗮𝗻𝗰𝗵é𝗲𝘀.

Bref : donnez-leur les moyens.

C’est exactement ce qu’on développe ici :
“𝗔𝗿𝗿ê𝘁𝗲𝘇 𝗱𝗲 𝗯𝗹â𝗺𝗲𝗿 𝗹𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗶𝗻𝘁𝗲𝗿𝗺é𝗱𝗶𝗮𝗶𝗿𝗲. 𝗗𝗼𝗻𝗻𝗲𝘇 𝗹𝗲𝘀 𝗺𝗼𝘆𝗲𝗻𝘀 à 𝘃𝗼𝘀 𝗺𝗮𝗻𝗮𝗴𝗲𝗿𝘀.”

🔗 Lire l’article : https://lnkd.in/eHTwbbRu


#LeadershipSanté #LifeSciences #ManagementHospitalier #Transformation #Organisation #Leadership

taplio