Pietas is usually translated as duty.
That does not quite carry the weight of it.
Not duty as cold obedience.
Not duty as blind loyalty.
Not duty as doing what you are told because someone above you said so.
Pietas was ordered obligation.
To family.
To country.
To the gods.
To the people depending on you.
That ancient idea maps cleanly onto management because leadership is never duty in one direction.
You owe something to the struggling employee.
You owe something to the team.
You owe something to the business.
You owe something to the customers.
You owe something to the organization that trusted you with authority.
And sometimes those duties come into conflict.
That is where management stops being theory.
That is where leadership starts to cost you something.
Duty Is Not Severity
Duty is not severity.
Duty is protection correctly ordered.
That distinction matters.
Some managers hear “accountability” and turn it into punishment. They mistake authority for force. They make hard decisions quickly because quick feels decisive, even when the situation deserves more care.
That is not duty.
That is impulse wearing a manager title.
Other managers make the opposite mistake.
They hear “compassion” and turn it into endless tolerance. They excuse behavior because someone is struggling. They delay a hard call because the person is nice, or going through something, or trying their best.
That can feel humane.
It is often cowardice with better branding.
A manager who avoids a hard decision because it feels unkind is simply transferring the pain to everyone else.
The team absorbs it.
The customers absorb it.
The business absorbs it.
The next manager inherits it.
Duty is not about being harsh.
It is about knowing what you are responsible to protect, and in what order.
The person matters.
The team matters.
The business matters.
The customers matter.
The future of the organization matters.
Pietas is not picking one and pretending the others do not exist.
Nice Is Not The Same As Safe
At a fintech SaaS company, I inherited an employee who was generally a nice guy.
Friendly.
Good natured.
Easy enough to like.
He was not a cartoon villain. He was not walking around trying to destroy the team.
But when he got frustrated, he lashed out at colleagues.
He blamed other people for his struggles.
He was not making progress on a major project.
When help was offered, he often became belligerent.
That is the hard category.
Not malicious enough to make the decision obvious from across the room.
Not productive enough to justify the damage.
Not receptive enough for help to work.
Just harmful enough that everyone around him starts paying the tax.
This is where managers lie to themselves.
They say, “He is a good guy.”
That might be true.
They say, “He is just frustrated.”
That might also be true.
They say, “He is going through a tough time.”
Maybe he is.
None of that answers the management question.
The question is not whether the person has redeeming qualities.
Most people do.
The question is whether their continued presence is helping or harming the system you are responsible to protect.
A likable person can still be harmful to the team.
That is not a contradiction.
That is management.
Help Has To Be Received
Struggling is not the problem.
Everyone struggles.
Good people hit walls. Good engineers get stuck. Good teammates go through seasons where they need more support than usual.
You help them.
You clarify expectations.
You remove blockers.
You offer pairing.
You adjust scope.
You coach.
You give direct feedback.
You create a path back to solid ground.
That is part of the job.
The problem starts when help is offered and rejected.
The problem starts when frustration turns outward.
The problem starts when the person makes their struggle everyone else’s burden.
Blaming colleagues is not struggling.
Lashing out is not struggling.
Refusing help is not struggling.
Stalling major work while making the team absorb the fallout is not struggling.
That is damage.
And when damage becomes a pattern, the manager has a duty to act.
Not because the person is worthless.
Not because the person is beyond empathy.
Not because the manager should enjoy it.
Because the duty to one person cannot erase the duty to the team.
The Team Will Tell You
Teams usually know before managers admit it.
The signal shows up in the work.
The signal shows up in the mood.
The signal shows up in who volunteers to pair, who avoids certain stories, who stops speaking in meetings, and who quietly starts looking for another job.
In this case, I tracked points per developer day as a measure of team efficiency.
It was not the whole truth.
No metric is.
But it was useful.
Every time this employee went on vacation, the number went up.
That was a signal.
The team became more efficient when one person was absent.
That does not happen by accident.
Then the strongest signal arrived.
Top performers on the team told me they would not work with him anymore.
That was the final straw.
At that point, keeping him was no longer patience.
It was choosing to spend the credibility, energy, and goodwill of the people carrying the organization.
That is not compassion.
That is misordered duty.
I let him go.
He should have been let go before I got there.
That is blunt because the lesson is blunt.
Avoided decisions do not disappear.
They become inherited damage.
Avoided Decisions Compound
One person can damage more than a sprint.
One person can damage a team.
One person can damage trust in leadership.
One person can make good people leave.
One person can teach the organization that standards are optional if someone is difficult enough to manage.
I have seen this pattern at a larger scale at a healthtech SaaS company.
A startup had been acquired by the healthtech company and turned into a division. The division owned a SaaS product, and the product manager responsible for that product had a long pattern of changing direction, giving poor requirements, yelling at developers, and making it difficult for the team to finish meaningful work.
The developers escalated.
They asked for help.
They asked for a different product manager.
The CTO’s answer was always some version of the same thing:
“They are doing their best and going through some things. Just work with them. Things will get better.”
Things did not get better.
A product owner was hired to buffer the development team from the chaos.
That product owner left.
Another product owner came in and helped stabilize the team.
That product owner eventually left too because working with the same product manager became intolerable.
The development team deteriorated.
The product struggled.
Layoffs followed.
Eventually, the division closed.
More than 50 people were affected.
The person whose behavior had caused so much damage stayed.
That is what misordered compassion can do.
It can feel kind in the moment because the immediate conflict is avoided.
No hard conversation today.
No termination meeting today.
No uncomfortable escalation today.
But the pain does not vanish.
It spreads.
It moves from the person who should be accountable to the people trying to make the organization function around them.
The team pays.
The product pays.
The customers pay.
The company pays.
Eventually, people who did nothing wrong pay with their jobs.
Compassion Needs Boundaries
Compassion matters.
If you manage people long enough, you will lead someone through grief, illness, burnout, divorce, anxiety, family crisis, financial pressure, and seasons where life outside work makes work harder.
You should care.
You should make room where you reasonably can.
You should help people recover.
You should not reduce a person to one bad quarter, one rough project, or one season of struggle.
But compassion without boundaries becomes negligence.
The kind thing for one person can become the cruel thing for everyone else.
That is the uncomfortable truth managers have to face.
You can be humane and still be firm.
You can care about someone and still remove them from a role.
You can feel the weight of the decision and still make it.
You can wish the situation were different and still act on the situation that exists.
Duty is not always gentle.
Or easy.
But a manager does not get to protect their own comfort by calling inaction compassion.
Your job is not to avoid pain.
Your job is to put protection in the right order.
Protect the person where you can.
Protect the team when you must.
Protect the business from avoidable damage.
Protect the customers depending on the work.
Protect the future employees who will inherit whatever you tolerate today.
That is duty.
Not severity.
Protection correctly ordered.