
## I don't lose talent to the “market”: I lose it to friction
There is a moment that repeats in many SMEs: a key person leaves, and suddenly everything feels more fragile than it seemed.
-
- decisions slow down
-
- doubts multiply
-
- “silly” errors appear
-
- and the company enters a reactive mode that consumes energy.
The usual discourse is “we can't compete with salaries” or “people don't want to commit anymore.”
My experience is different: people don't run away only from money; they run away from constant friction and uncertainty.
When an SME becomes an environment where everything depends on memory, urgencies, and corrections, talent wears out even if it is well paid.
## The real cost of turnover is not the departure: it's what it breaks around it
I separate the cost into four layers. The departure itself is only the first.
### 1) Visible substitution cost
-
- search
-
- interviews
-
- integration
-
- learning curve.
That is seen and accepted.
### 2) Hidden operational cost
-
- extra coordination
-
- tasks “that nobody does,”
-
- postponed decisions
-
- and more interruptions for the profiles that stay.
Here is where the real hole starts.
### 3) Internal promise cost
When someone leaves, the team learns an implicit message:
-
- “here the load is not sustainable,”
-
- “here you don't grow,”
-
- “here you survive.”
That increases future turnover even if the position is covered quickly.
### 4) Margin cost
The margin is lost through small and repeated things:
-
- rework
-
- poorly captured changes
-
- duplicate verifications
-
- urgencies that disrupt the week
-
- and failures that end in discounts or concessions.
Turnover doesn't “increase costs” in a generic way: it degrades the ability to fulfill the promise.

## Why people leave (even if they don't tell you)
Most people don't leave shouting. They leave by disconnecting.
I usually see these causes, in this order:
### 1) Lack of useful clarity

Not “pretty” clarity in org charts. Useful clarity:
-
- what is expected of me
-
- what “well done” means
-
- what decisions I can make without asking permission
-
- and what I do when something goes off-script.
Without that, the person lives in alert-mode: every day is about interpretation.
### 2) Unpredictable load (and guilt for not arriving)
It's not “working a lot.” It's not being able to plan:
-
- spikes without explanation
-
- urgencies as the norm
-
- priorities that change through loose messages
-
- and a sense of permanent debt.
People endure high loads if there is meaning and a framework. What burns people is randomness.
### 3) Attacked professional pride
In project-based environments, pride is key: delivering something solid.
When the system causes:
-
- repeated errors
-
- uncontrolled changes
-
- impossible promises
-
- and re-processes that seem avoidable…
the person feels that they are working “to put out fires” and not to build.
### 4) Stagnant learning
If work is reduced to executing urgencies, there is no real growth.
People don't demand “courses.” They demand to feel progress: mastering something more, deciding better, contributing more.
### 5) Recognition confused with urgency
In tense companies, recognition becomes:
-
- “thanks for staying late,”
-
- “good thing you fixed it.”
That rewards heroism, not the system. And heroism exhausts.
## The most frequent management error: trying to retain with incentives what is lost by system
I have seen companies design:
-
- bonuses
-
- “benefits,”
-
- improvised flexibility
-
- one-off gifts…
while keeping intact what drives people away:
-
- daily friction
-
- decisions without a framework
-
- erratic load
-
- and conflicts over internal expectations.
I say it bluntly: if the day-to-day hurts, the incentive only buys time.
## Attraction and retention in an SME is won with three internal promises
For me, talent stays when it perceives three promises fulfilled internally:
### 1) “Here I know what winning is”
Winning is a clear standard: quality, deadline, margin, and client experience.
It's not perfection. It's coherence.
### 2) “Here my energy is used well”
That the work is not an infinite cycle of correction, urgencies, and rework.
### 3) “Here I advance”
I advance in mastery, autonomy, and judgment. Not just in accumulated hours.
If these three promises exist, attracting becomes easier because the reputation travels.
## Early warning signs of exit that I take very seriously
Before a departure, patterns appear. If you detect them, there is still room for maneuver.
- Fewer proposals, more defensive questions (“Are you sure I should do it this way?”).
- Less future vision (“We'll see”).
- More isolation (avoids coordination).
- More focus on limits (“This isn't my job,” even when previously collaborating).
- Mood changes around urgencies (irritation, cynicism).
- Quality drop in small deliverables.
7) Disinterest in learning something new “here.”
I don't read it as a lack of attitude. I read it as system fatigue.


## Onboarding: where it's decided if the SME retains or expels
Onboarding is the first real psychological contract.
When onboarding is:
-
- informal
-
- based on “ask X,”
-
- and without a standard…
the person learns that knowledge lives in people, not in the system.
That kills two things:
-
- autonomy
-
- and confidence in the future.
I'm not talking about “infinite manuals.” I'm talking about there being a visible path:
-
- what I must master first
-
- what risks are critical
-
- what tools I use
-
- where the truth is
-
- and how my progress is measured.
When that exists, the person feels progress. And progress retains.
## Joseph's Key Question: do you want strong profiles or obedient profiles?
This question hurts, but it's useful.
A chaotic system retains obedience: people who endure and execute without asking.
A clear system retains talent: people who think, propose, and improve.
If you want to retain talent, you have to accept one condition:
the system must allow deciding without asking permission for everything.
That demands limits, not constant supervision.
## Versatility and specialization: the balance that prevents exhaustion
In SMEs, versatility is necessary. But poorly designed, it becomes:
-
- “you do everything,”
-
- “here we all put out fires,”
-
- “when someone is missing, you cover.”
That isn't versatility: it's overload.

The versatility that retains feels different:
-
- there is a visible matrix of coverage
-
- there are levels (not everyone covers everything)
-
- and there is a criterion to decide what is prioritized when capacity is missing.
Without that framework, versatility becomes a trap.

## How I diagnose if the problem is “talent” or “system” in 30 minutes (without implementing anything)
I don't need to deploy anything to see the pattern. It's enough to observe:
### 1) Where the decision gets stuck
Are most blocks resolved with judgment or with personal escalation?
### 2) What percentage of the work is rework
Not the official rework. The rework that is lived as “adjustments,” “reviews,” and “corrections.”
### 3) How predictable the week is
Is the week planned or is it rewritten every day?
### 4) How clear the standard is
Are there agreements on what “finished” means or is everything decided by last-minute review?
### 5) Where the truth lives
In a system or in conversations?
If the truth lives in conversations, talent gets tired sooner.
## Decision criteria I use to prioritize without “doing an HR project”
I don't recommend starting with “policies.” I start with criteria.
When an SME wants to attract and retain, it needs to decide:
-
- which roles are critical by impact and by scarcity
-
- which frictions expel faster
-
- what part of the load is avoidable (by system) and what is inherent
-
- and what signals indicate that the balance is broken.
That is decided with evidence, not with intuition.
And the evidence doesn't need months: it needs focus.
## Closing: I don't retain talent with promises, I retain it with design
Rotation is rarely a “people problem.” It's usually an environment problem:
-
- insufficient clarity
-
- unpredictable load
-
- weak learning
-
- and eroded professional pride.
I don't compete for talent with speeches. I compete with a system that makes the day-to-day defensible.
If you want, let's look at it in 15 minutes: I'll identify with you which frictions are expelling energy, which roles are at real risk, and what criteria to use so that the company stops depending on heroism.








