TPS Relationships #10 - Leadership & People - People are always learning from the system around them.
Leadership is not only what leaders say or intend. People are constantly learning from what happens around them — what happens when they raise a problem, make a mistake, ask for help, disagree, or take ownership. Over time, those repeated experiences teach people what is safe, what is expected, and what the system truly values. TPS Relationships #10 explores the relationship between Leadership and People — and how the system may be teaching something very different from what leadership believes it is teaching.
DEVELOPING PEOPLETPS RELATIONSHIPSLEADERSHIPTHINKING DIFFERENTLY
TPS Relationships #10
Leadership & People
People are always learning from the system around them.
Leadership is often discussed as something a leader does to people.
Communicate clearly.
Listen carefully.
Give feedback.
Recognize good work.
Ask questions.
Build trust.
All of these matter.
But there is another side of the relationship that is easier to miss:
People are constantly learning what leadership actually means by experiencing the system around them.
They learn which problems are safe to expose.
They learn whether asking for help is interpreted as responsibility or weakness.
They learn whether bad news should travel quickly or be softened first.
They learn whether an idea is genuinely welcomed or merely tolerated.
They learn whether a mistake becomes an opportunity to understand or a reason to find someone to blame.
And they learn whether ownership is truly expected—or only until their judgment differs from the leader’s.
None of this requires a written policy.
The system teaches it every day.
Leadership is read through experience
A leader may say, “Bring me problems early.”
But what happens when someone does?
If the first response is:
Who did this?
the organization has learned something.
If instead the first response is:
What happened? What did you see?
it has learned something different.
The words spoken before the problem appeared may have been identical.
The lesson was created by what happened afterward.
This is why leadership cannot be understood only through intentions, values or behaviors considered in isolation.
The way leaders respond to problems today shapes the ownership people are willing to take tomorrow.
People adjust.
Not necessarily because they are disengaged, resistant or afraid of accountability, but because adapting to their environment is rational.
If raising a problem repeatedly creates additional work, scrutiny or blame, people will eventually become more selective about which problems they raise.
If proposing an idea means losing ownership of it the moment management becomes involved, people may stop proposing ideas.
If every decision must ultimately travel upward, people learn to wait.
And if people are told to speak openly but repeatedly discover that some truths are more welcome than others, they learn the real boundary.
People do not report the truth according to what leaders ask for. They report according to what they have learned the system can tolerate.
Before trying to change the person
When behavior becomes undesirable, the person is often the first place we look.
Why doesn’t she speak up?
Why won’t he take ownership?
Why do they wait to be told?
Why are people resistant to change?
Sometimes the answer does lie with the individual.
But beginning there can make us overlook two components that are often easier to change: the procedure surrounding the work and the team environment in which it happens.
A habit may be the best response someone has found, so far, to the conditions around them.
Changing the person can take time.
Changing what happens when a problem is raised, who is allowed to make a decision, how feedback is given, or how a team responds to an abnormality can begin immediately.
This is why developing people and improving systems should not be treated as competing approaches.
A better system changes what people experience.
Repeated experience changes what people learn.
What people learn changes how they behave.
Silence is not empty
This relationship becomes particularly visible in feedback.
Managers sometimes postpone a conversation because they want to preserve the relationship, avoid unnecessary tension or wait for a better moment.
But while the conversation waits, learning continues.
One person continues working without information.
The other continues observing, interpreting and often accumulating frustration.
The gap does not remain empty.
Assumptions begin to occupy it.
Feedback delayed doesn’t preserve the relationship. It lets assumptions grow in the space where information should have been.
The same happens with progress, decisions and expectations.
When progress is invisible, people construct explanations.
When a decision is unexplained, people construct motives.
When expectations are unclear, people construct their own standards.
Leadership is therefore not only about providing direction.
It is also about understanding what people are likely to learn when information is missing.
Support without taking ownership
There is another subtle way leadership shapes people: by helping too much.
A leader sees someone struggling and provides the answer.
It feels supportive.
And sometimes it is exactly what the situation requires.
But when answering becomes the default, something else can happen: thinking gradually moves away from the work.
People learn that difficult questions eventually travel upward.
The leader becomes increasingly necessary.
And what looks like support begins to create dependency.
Listening does not require solving.
Coaching does not require deciding.
Support can mean helping someone see the problem more clearly, ask better questions, test an idea or examine an assumption while leaving ownership where it belongs.
Trust invites support. Dependency transfers ownership.
Developing people sometimes requires resisting the temptation to demonstrate that we already know the answer.
What people experience repeatedly becomes culture
This is perhaps the most important relationship between Leadership and People.
Culture is not built only through major decisions, leadership programs or statements of values.
It accumulates through ordinary repetitions.
What happens when someone pulls the Andon.
What happens when a target is missed.
What happens when someone disagrees.
What happens when someone says I don’t know.
What happens after a mistake.
What happens when someone succeeds.
What happens when the leader is not there.
Each event is small.
Together, they teach people how the system works.
And eventually people stop needing to consciously think about those lessons.
They simply know.
They know what to say.
What not to say.
When to act.
When to wait.
When to ask.
When to hide.
When to think.
And when to let someone else think for them.
That is why Leadership and People cannot really be separated.
Leadership shapes the environment in which people learn how to behave.
And people’s behavior continuously tells leadership what that environment has taught them.
Perhaps one of the most useful questions a leader can ask, then, is not:
“How do I get people to behave differently?”
but:
“What are people learning from the system they experience every day?”
Because people are always learning.
The question is whether the system is teaching what leadership believes it is teaching.
Este, Katsu, sí es Relationships. Respeta además lo que habíamos definido para la serie: no enseña una herramienta ni ofrece una receta; parte del problema y descubre una relación que suele desaparecer cuando estudiamos las cosas aisladamente.
Y hay algo que me gusta muchísimo: no hemos tenido que meter TPS con calzador. Andon aparece una sola vez y porque corresponde. Todo el texto podría leerlo alguien de manufactura, medicina, educación o servicios y reconocerse.
Además, creo que ya tenemos el candidato natural para la KD que acompañe a R10:
“People do not report the truth according to what leaders ask for. They report according to what they have learned the system can tolerate.”