Leadership advice sounds simple when the situation is simple.
Delegate. Listen. Empower people. Hold them accountable. Be decisive. Show empathy. Trust your team.
The difficulty comes when two good ideas pull you in different directions.
An employee brings you a customer problem that they should probably learn to solve. You want to empower them, but the customer is waiting and you can fix the problem faster yourself.
A team member misses an important commitment. You want accountability, but you also know that something difficult is happening in their life.
Someone tells you about a mistake before it becomes serious. You need to address what went wrong, but you also want people to keep bringing bad news to you instead of hiding it.
What do you rely on when there is no script?
This is where leadership principles become useful.
A principle does not give you an automatic answer. It gives your judgment somewhere to stand while you decide.
Leadership principles do not remove judgment. They help you use it.
Characteristics, Principles, and Plays Are Different
We often describe good leaders through characteristics: integrity, courage, humility, empathy, decisiveness, accountability, resilience. These qualities matter. I discuss them more fully in 20 Characteristics of Good Leaders.
But a characteristic does not always tell you what to do next.
Suppose an employee says, “Ma’am, the customer wants a replacement. What should I do?”
You want to be empowering. You also want to be accountable. You care about the employee and the customer. You want to be decisive.
All good qualities.
The decision is still yours to make.
A principle helps guide that judgment. One principle might be:
Keep decisions as close to the work as responsibly possible.
That principle could lead to a practical response:
“What do you recommend?”
That response is a play—something you can call when a recurring moment appears.
The distinction is useful:
Characteristics describe what you want to embody. Principles guide your judgment. Plays help you act in recurring moments.
A good leadership principle therefore has to do more than sound wise. It should help you choose when two reasonable responses compete.
Let What Matters Lead
Leadership principles themselves can sometimes pull in different directions.
Empower the employee—but protect the customer.
Move quickly—but avoid an irreversible mistake.
Support the person—but do not quietly take their work back.
So there must be something above the principle.
For me, the starting question is:
What matters here?
What result, person, customer, commitment, relationship, or strategic priority must be protected or moved?
I learned this in my own company through an employee I call Rose.
Rose had two degrees from a respected Philippine university and was capable of doing many things. I could have kept filling her days with whatever needed attention—training preparation, writing, routine office work, photocopying, errands, and administrative tasks.
Instead, I looked at the business problem.
At that time, we offered a large number of training programs. Prospective customers would inquire and then disappear. The problem was not that our catalog was too small. We did not understand customers deeply enough, and we were not sustaining relationships with them well enough.
So I stopped asking, “What else can Rose do?” and started asking where the business needed her most.
Her work shifted toward understanding customers, representing their concerns inside our company, and continuing the relationship whether the customer bought immediately or not. Customers became more willing to meet me because Rose had already shown that we had taken the time to understand their world.
The lesson was not simply about delegation.
It was about leadership attention.
Capable people can always be given more work. Leadership requires deciding which work deserves their capability.
Move what matters, not merely more work.
This is one of the ideas behind Build Leaders Who Move Work. Leadership should eventually help something important become clearer, move faster, gain ownership, or produce visible progress.
When you are unsure which principle to apply, return first to what matters.
Your Response Teaches People What Is Safe
At one resort where I worked, the day began with a 7:30 a.m. briefing.
It should have prepared people for the work ahead. Instead, employees learned to fear it.
The general manager was direct. When someone made a mistake, he named it in front of the group. Small failures could become public examples, sometimes repeated long after the lesson had been understood.
Eventually, people discovered something: reporting a problem could make you the problem.
They became quieter. They patched issues on their own. They delayed bad news. They hoped the general manager would not notice.
The manager was not imagining everything. Some employees really were hesitant to act, and some mistakes really did need correction. But his response to those mistakes was teaching another lesson at the same time.
I asked him:
“What do you want people to do after these sessions—hide or help?”
That question reveals another leadership principle:
Your response teaches people what is safe to repeat.
A manager may tell people, “Use your judgment,” then reverse their decisions whenever they choose differently.
A supervisor may say, “Tell me early when something is going wrong,” then become visibly angry whenever someone brings bad news.
A leader may ask for ideas and spend the next ten minutes explaining why every suggestion will fail.
People do not learn only from what leaders say.
They learn from what happens after they act.
If you want people to surface problems earlier, look closely at what happens to the person who brings you one.
If you want initiative, notice what happens when someone tries something without your permission.
If you want truth, make sure telling the truth does not repeatedly become the most dangerous move in the room.
Go First When You Want the Team to Shift
Leaders sometimes wait for people to change before changing their own response.
The team needs to be more accountable.
People need to speak up.
Employees should become more proactive.
Perhaps.
But what are they learning from you?
In Team First, I tell the story of a leader I call Nina. She inherited a team that was professional but disengaged. People completed their jobs, but few volunteered ideas or openly admitted where they were stuck. Her Monday huddles were mostly status updates and uncomfortable silence.
Nina did not launch a culture campaign.
She changed what she repeatedly did in the meeting.
She recognized something the team had done well. Then she named something she could have done better and stated what she would do differently that week. Only after doing that did she ask people what they were focusing on and what support they needed.
Over time, people began mirroring her. They surfaced problems more readily, took greater responsibility, and spoke more honestly about what they needed.
You could describe Nina as humble or accountable. Those characteristics matter.
But the principle was visible in what she did:
Model the response you want repeated.
If you want people to admit mistakes, show them what responsible admission looks like.
If you want better follow-through, make your own commitments visible.
If you want people to listen, let them experience being heard.
Leadership can begin before anyone agrees to follow you.
Sometimes somebody simply has to go first.
Keep Judgment Close to the Work
One of the most common ways leaders accidentally create dependence is by answering questions too quickly.
An employee comes with a problem.
The manager knows the answer.
Giving it takes ten seconds.
That feels efficient.
But if the employee has enough information, capability, and responsibility to make the decision, those ten seconds may teach the wrong lesson.
The employee learns that uncertainty means asking the boss. The manager gets more practice deciding while the employee gets more practice escalating.
Soon both sides have evidence that the manager is necessary.
A better principle is:
Keep judgment as close to the work as responsibly possible.
The phrase responsibly possible matters. Some decisions involve legal, financial, safety, strategic, or reputational risks that genuinely require higher authority.
But when another person can responsibly carry the decision, your job is not necessarily to demonstrate that you know the answer.
You may instead ask:
“What do you recommend?”
Listen to the reasoning. Clarify a boundary if necessary. Coach the judgment. Then leave the decision where it belongs.
If you delegate only the hands and keep all the thinking, you have not created ownership.
You have created another pair of hands.
Support Without Quietly Taking the Work Back
This principle becomes difficult when someone struggles.
You delegate an important assignment. The person makes progress, then encounters a problem. You know exactly what to do, and stepping in would be faster.
Sometimes you should intervene. Serious risk may justify it.
But sometimes the real problem is that watching someone else think is slower than thinking for them.
If a manager repeatedly takes work back whenever difficulty appears, employees learn that ownership lasts only until the task becomes uncomfortable.
Support should make another person more capable of carrying the work.
That may mean asking what they have already tried. It may mean narrowing a risk, clarifying a boundary, providing information, or agreeing on a checkback point.
The principle is not “Never rescue.”
It is:
Support people in carrying the work before assuming you must carry it for them.
The distinction matters because leadership development often happens precisely in that uncomfortable space between abandonment and rescue.
Look at the Work Before You Diagnose the Person
When behavior disappoints us, our attention naturally moves toward the individual.
“They are not motivated.”
“They lack accountability.”
“They are not proactive.”
“They need more confidence.”
Any of those explanations may eventually prove useful. But they are poor places to stop.
Ask what the behavior is responding to.
In another organization, a BPO team had missed three campaigns in four months. They thought they needed a better task-management system and were considering tools such as ClickUp or Notion.
When I observed the planning meeting, a different problem became visible. Deadlines were not confirmed aloud. Actions were not clearly assigned. The leader would end discussions with something like, “OK na? Sige, good luck.”
They thought they had a software problem.
The work showed that ownership was not becoming visible in the meeting.
A new tool might have made the confusion more organized without removing it.
This does not mean systems never matter. They do.
The principle is:
Before blaming the person—or buying the solution—look at what the current work makes easy, difficult, safe, or costly.
Authority matters. Information matters. Handoffs matter. Measures matter. Routines matter. Manager behavior matters.
Personal responsibility does not disappear when we inspect the system.
We simply diagnose more intelligently.
Follow Proof, Not Leadership Theater
A leadership conversation can feel excellent.
The employee nods.
The team agrees.
The workshop receives high ratings.
The manager feels that something important happened.
Maybe it did.
But what happened next?
Years ago, I entered an elevator with several managers who were about to attend a time-management seminar I was facilitating. Someone mentioned that they had previously attended a program led by a famous Filipino speaker. The organization had reportedly paid around ₱350,000 for it.
The HR manager asked whether the program had helped.
The managers praised the speaker. He had been excellent, entertaining, impressive.
Then she asked what had changed.
“Same, same,” they said. “We are still busy.”
That conversation stayed with me.
The earlier program may have been well designed. Participants may genuinely have learned something. The speaker may have delivered everything promised.
But the organization had measured the event more easily than it had measured the movement.
Leadership can fall into the same trap.
If you clarified direction, watch whether people make better decisions.
If you transferred ownership, watch whether the work stays with the person when difficulty appears.
If you made truth safer, watch whether bad news starts arriving earlier.
If you coached someone, watch what happens when the same moment returns.
Leadership should eventually leave evidence in the work.
The meeting is not the proof.
The conversation is not the proof.
The workshop is not the proof.
Look at what people can now do differently.
Principles Matter When Good Things Compete
You do not need a principle when the answer is already obvious.
Principles earn their place when good things compete.
Listen—but eventually decide.
Empower—but protect serious risk.
Support—but do not rescue.
Move quickly—but slow down when the consequences are difficult to reverse.
Care about the person—but do not make commitments meaningless.
Tell the truth—but do it in a way that helps people face reality rather than hide from you.
There is no formula that removes judgment from leadership.
Nor should there be.
That is why I do not think of leadership principles as laws. I think of them as ideas worth returning to because they improve the questions we ask when circumstances become uncertain.
Let what matters lead.
Move what matters rather than merely more work.
Model what you want repeated.
Keep judgment close to the work.
Support ownership without taking it back.
Look at the conditions around behavior.
Follow the proof.
The situation will still require you to think.
That is the point.
Use the No-Script Test
The next time you face a leadership decision where two reasonable responses compete, try four questions:
- What matters most here? What result, person, customer, commitment, relationship, or risk must be protected or moved?
- Which principle should guide my judgment? What idea will help me choose rather than merely react?
- What play will put that principle into action? What will I actually say or do?
- What will I watch afterward? What evidence would tell me that the response helped?
The resort manager did not need another slogan about accountability. He needed to see that the way he pursued accountability was teaching people to hide.
The question hide or help? allowed him to examine what mattered and what his leadership was producing.
Your next moment will look different.
A customer will need an answer. Someone will disappoint you. An employee will make a decision you would not have made. Two priorities will collide. A policy will not quite fit the situation.
There may be no script.
You will still have to judge.
That is when a leadership principle earns its place—not because it sounds wise on a slide, but because when the answer is unclear, it helps you make a better next move.