Category: Transformation

Your Managers Keep Talking About Accountability—But No One Feels It

~ jordan ~ Leave a comment

It shows up in small ways.

Deadlines are missed—but explained away.
Commitments are made—but quietly adjusted.
Issues are raised—but not owned.

No one is openly refusing responsibility.

But no one is fully owning it either.

And if you’re honest—you can feel it.

Work gets done.

But not with urgency.
Not with ownership.
Not with consistency.

So the question becomes:

Why does accountability sound strong in conversations… but feel weak in reality?

Here’s the truth most organizations avoid:

Accountability is not built through words.
It is built through systems.

Because talking about accountability is easy.

Enforcing it consistently?

That’s where most leaders struggle.

Let’s break this down.

Managers often say:

“We need more accountability.”
“People should take ownership.”
“The team needs to step up.”

All valid.

All true.

All ineffective—on their own.

Because accountability is not a mindset issue.

It’s a clarity issue.

When expectations are unclear—accountability disappears.

When ownership is shared—accountability fades.

When follow-through is inconsistent—accountability becomes optional.

And once accountability becomes optional…

Performance becomes unpredictable.

Let’s make this real.

A manager assigns a task:

“Let’s get this done by next week.”

Sounds clear.

But look closer.

Who owns it?

What exactly is “done”?

What happens if it’s delayed?

No clarity.

No accountability.

Now compare that to this:

“John owns this. Final output is the completed proposal. Due Friday at 3 PM. We’ll review progress Wednesday.”

Now it’s clear.

Now it’s visible.

Now it’s accountable.

That’s the difference.

Accountability is not about pressure.

It’s about precision.

Let’s go deeper.

Why do managers struggle with this?

First—they avoid discomfort.

Holding people accountable can feel confrontational.

So managers soften expectations.

Or avoid follow-ups.

Second—they assume understanding.

They believe the team “gets it.”

But assumption is not clarity.

Third—they lack follow-through systems.

They assign work.

Then move on.

And without follow-through—

Accountability disappears.

Now here’s the shift.

Stop thinking of accountability as a conversation.

Start thinking of it as a structure.

Let’s simplify what that structure looks like.

Every task needs three things:

  1. Clear owner
  2. Defined outcome
  3. Specific timeline

If any of these are missing—

Accountability weakens.

Now add one more layer.

Follow-through.

Not random.

Not reactive.

Consistent.

Checkpoints.

Reviews.

Visibility.

Because accountability is not enforced at the start.

It’s reinforced along the way.

Now here’s where most training fails again.

They teach accountability as a concept.

They explain ownership.

They discuss responsibility.

But they don’t build the behavior.

Because accountability is not learned once.

It is practiced daily.

This is where microlearning becomes powerful.

Because it focuses on small, repeated actions.

Here’s how it can look.

Day 1:

Review a task you assigned.

Was ownership clear?

Day 2:

Rewrite it with a single owner.

Day 3:

Define the outcome precisely.

Day 4:

Set a clear timeline and checkpoint.

Day 5:

Follow up.

Did it happen?

That’s one cycle.

Now repeat that across weeks.

Managers start assigning work differently.

They start following up consistently.

They start holding standards.

And something changes.

Accountability becomes visible.

Not forced.

Not pushed.

But expected.

Now imagine this across your organization.

Managers don’t chase work.

Work gets delivered.

Teams don’t guess expectations.

They know them.

Delays don’t get ignored.

They get addressed.

That’s when accountability becomes real.

Not in meetings.

Not in speeches.

In daily behavior.

Let’s be direct.

Most organizations don’t lack talent.

They lack consistent accountability.

And accountability is not built through motivation.

It is built through clarity and follow-through.

So before your next leadership program rollout, take a step back.

Look at how work is assigned.

Look at how follow-ups are done.

Look at how delays are handled.

And ask yourself:

Are your managers talking about accountability… or actually building it into how work gets done every day?

Here are five related articles from jordanimutan.com that break down how to move accountability from a buzzword into a functioning team operating system:

1. The Accountability Ladder: A Tool for Measuring Ownership

This is the most critical resource for this topic. It introduces the Accountability Ladder, a visual framework that helps managers diagnose exactly where their team members are getting stuck (e.g., “Wait and Hope,” “Blaming Others,” or “I’ll do it”). It helps managers identify if they are coaching for activity or ownership.

2. Accountability vs. Blame: Why You Are Creating a Culture of Fear

Often, managers think accountability means “finding out who is at fault when things go wrong.” This article flips the script, explaining that if your team associates accountability with punishment, they will hide their mistakes rather than owning them. It provides strategies to shift the focus from “Who did this?” to “How do we ensure this doesn’t happen again?”

3. The Clarity Gap: Why Ambiguity Kills Accountability

You cannot hold someone accountable for an expectation you never clearly defined. This article teaches the use of RACI (Responsible, Accountable, Consulted, Informed) matrices. It demonstrates how to clarify exactly who owns the final decision and the outcomes, eliminating the “I thought someone else was doing it” excuse.

4. Closing the Loop: Why Accountability Requires Consequences

Accountability fails when “nothing happens” regardless of whether the goal was met or missed. This article discusses the necessity of consistency. It provides a framework for “Positive Reinforcement of Standards”—teaching managers how to reward those who take ownership and address those who don’t, ensuring that accountability isn’t just a threat, but a standard.

5. The STRIDES™ Framework: Building an Ownership-First Culture

If accountability is missing, it’s usually because the system doesn’t support it. This article focuses on the “S—Systematize” and “D—Direct” pillars of the STRIDES™ methodology. It helps leaders build rituals (like weekly debriefs) that naturally demand accountability in a way that feels supportive and structured, rather than forced.

Your Managers Are Always “Busy”—But Your Business Isn’t Moving

~ jordan ~ Leave a comment

It doesn’t look like failure.

No one is slacking.
No one is obviously underperforming.
Everyone looks… busy.

Calendars are full.
Messages are constant.
Work is happening all day.

And yet—progress feels slow.

Projects drag.
Decisions take longer.
Results don’t match the effort.

If you’ve ever looked at your team and thought, “We’re working hard, but why aren’t we moving faster?”—this is for you.

Because the issue is not effort.

It’s direction.

Let’s be clear.

Being busy is easy.

It’s natural to respond to what’s in front of you.

Emails.
Requests.
Meetings.
Urgent tasks.

They pull your attention instantly.

And when managers spend their day reacting to these things, they feel productive.

But here’s the problem:

Reaction does not create progress.

It only creates activity.

Now think about your managers.

What does their typical day look like?

They start with a plan.

Then something comes in.

Then another.

Then a meeting.

Then a “quick question.”

Then another request.

And suddenly, the day is gone.

The plan?

Still there.

But untouched.

This is one of the most common leadership issues today:

Managers are reacting instead of directing.

And here’s why that matters.

Because in any organization, progress doesn’t come from doing more.

It comes from doing what matters most—consistently.

Let’s simplify this.

There are two types of work:

  1. Work that keeps things running
  2. Work that moves things forward

Most managers spend their time on the first.

Fixing issues.
Answering questions.
Handling daily operations.

Important?

Yes.

But not enough.

Because growth happens in the second.

Planning.
Improving processes.
Driving key initiatives.

And this is where most managers struggle.

Not because they don’t understand it.

But because they don’t protect time for it.

So the day gets filled with what’s urgent.

And what’s important gets delayed.

Again and again.

Now here’s the uncomfortable truth:

If managers don’t control their time—everything else will.

So how do you fix this?

Not by telling managers to “work harder.”

Not by adding more tools.

But by changing how they decide what to focus on.

Let’s start with clarity.

Every manager needs to answer one question at the start of the day:

“What is the one thing that must move forward today?”

Not five things.

Not everything.

Just one.

Because focus creates progress.

Once that’s clear—the next step is protection.

That one priority needs time.

Real time.

Not leftover time.

So it gets scheduled.

Blocked.

Protected.

Because if it’s not protected—it will get replaced.

Now let’s talk about interruptions.

Because they will happen.

Requests will come in.

Questions will be asked.

Issues will appear.

So managers need a simple filter:

“Does this need my attention now—or can it wait?”

If it doesn’t move the priority forward—

It can wait.

This is where discipline comes in.

Not saying yes to everything.

Not responding immediately to everything.

But choosing where attention goes.

Now here’s where most training misses this.

They teach time management.

They teach productivity tools.

But they don’t build the behavior.

Because behavior is built daily.

This is where microlearning becomes powerful.

Because it focuses on small, repeatable actions.

Here’s what that looks like.

Day 1:

Identify your top priority.

Day 2:

Block time for it.

Day 3:

Track how much time actually went to it.

Day 4:

Notice what pulled you away.

Day 5:

Adjust.

That’s one cycle.

Simple.

But real.

Now repeat that weekly.

Managers become more aware.

More intentional.

More focused.

And slowly—something changes.

They stop reacting.

And start directing.

Now let’s talk about the impact.

When managers focus on what matters:

Work moves faster.

Decisions happen earlier.

Teams become clearer.

Because direction replaces confusion.

And progress becomes visible.

Not because people are working more.

But because they are working on the right things.

Now imagine this across your organization.

Managers are not just busy.

They are effective.

Teams are not just active.

They are productive.

Work is not just happening.

It’s moving.

That’s the difference.

Let’s be direct.

Most organizations don’t lack effort.

They lack focus.

And focus is a leadership skill.

One that needs to be built.

Practiced.

Reinforced.

So before your next training program, pause.

Look at your managers’ days.

Look at how time is spent.

Look at what actually moves forward.

And ask yourself:

Are your managers truly leading their time… or just reacting to it?

Here are five related articles from jordanimutan.com that provide the frameworks needed to break this cycle and shift from “being busy” to “moving the needle”:

1. The Eisenhower Matrix: Separating Urgent Noise from Strategic Impact

This article is the foundational tool for any manager trapped in the “busy” cycle. It teaches leaders to categorize their tasks into four quadrants, helping them ruthlessly eliminate or delegate tasks that are “urgent” but not “important,” freeing up time for the high-impact work that actually moves the business forward.

2. Outcome-Based Leadership: Why Metrics Matter More Than Hours

Managers often equate “being busy” with “working hard.” This piece challenges that assumption by introducing an outcome-based model. It helps leaders redefine success not by how many hours they log or meetings they attend, but by the tangible business results they achieve. It provides a rubric for auditing your own calendar to see which tasks actually correlate to revenue or growth.

3. The STRIDES™ Framework: Systematizing for Growth

If a manager’s day is chaotic, it is usually a sign of a “Systematize” (the ‘S’ in STRIDES) failure. This article shows how to build organizational rhythms—like recurring strategic deep-dive sessions and automated status reporting—that replace ad-hoc busy-work with a predictable, high-output operating rhythm.

4. Saying No to Good Ideas: The Art of Strategic Focus

Often, business isn’t moving because managers are doing too many good things. This article explores the concept of “Essentialism” for leadership. It provides a toolkit for evaluating new projects and initiatives, ensuring that the team’s energy is concentrated on the few tasks that have the highest leverage rather than being scattered across many low-impact activities.

5. Deep Work for Leaders: Reclaiming Time in a Reactive World

Managers stay busy because they are constantly in reactive mode (email, Slack, meetings). This article teaches the “Time-Blocking” technique specifically for leaders. It provides a roadmap for securing “focus blocks” in a busy calendar, allowing managers to tackle complex, high-value strategy work that is impossible to do when you are constantly interrupted.

Your Managers Keep Solving Problems—But the Same Problems Keep Coming Back

~ jordan ~ Leave a comment

It looks like leadership.

A problem shows up.
The manager steps in.
They fix it quickly.

Crisis avoided.

Team relieved.

Manager feels effective.

From the outside, it looks like strong leadership.

Decisive. Hands-on. Reliable.

But look closer.

The same problems keep coming back.

Different week. Same issue.

Different person. Same pattern.

And now the question becomes uncomfortable:

Are your managers actually solving problems… or just repeatedly fixing them?

This is one of the most common leadership gaps across organizations.

Managers are trained—formally or informally—to respond.

To act quickly.

To fix issues as they arise.

And that’s valuable.

Until it becomes the only thing they do.

Because when managers focus only on solving problems in the moment…

They miss the bigger opportunity.

Preventing the problem from happening again.

Let’s make this real.

A customer complaint comes in.

Manager handles it well.

Issue resolved.

But the root cause? Untouched.

A team member misses a deadline.

Manager adjusts the plan.

Work gets completed.

But the reason behind the delay? Ignored.

A process breaks.

Manager steps in.

Gets things moving again.

But the system flaw? Still there.

So the organization keeps moving.

But with friction.

Repeated friction.

And over time, that friction becomes costly.

Not in one big moment.

But in small, repeated inefficiencies.

Now here’s the challenge.

Managers don’t ignore root causes on purpose.

They are just too busy reacting.

Because the system rewards speed.

Quick fixes.

Immediate action.

Not long-term thinking.

And here’s the irony.

The better your managers are at solving problems…

The more problems they get.

Because people start relying on them.

“Just ask the manager. They’ll fix it.”

So managers become the solution.

Instead of building solutions.

This creates a cycle.

Problem appears → Manager fixes → Problem returns → Manager fixes again

Over and over.

And slowly, something happens.

Managers become firefighters.

Always busy.

Always reacting.

But rarely preventing.

This is where most leadership training misses the mark.

They focus on problem-solving skills.

Decision-making.

Critical thinking.

All important.

But they rarely emphasize this:

The goal is not to solve more problems.
The goal is to reduce the number of problems that need solving.

That requires a different mindset.

From reactive…

To proactive.

From fixing…

To preventing.

So how do you build that shift?

Let’s break it down.

First—pause the instinct to fix immediately.

This is hard.

Because speed feels productive.

But the moment a manager jumps straight to a solution…

They skip understanding the real issue.

So the first step is simple:

Ask before acting.

What exactly happened?
When does this usually occur?
Who is involved?
What’s the pattern?

Now the problem becomes clearer.

Second—identify the root cause.

Not the surface issue.

The underlying one.

This is where many managers stop too early.

They fix what they see.

Not what’s causing it.

Here’s a simple way to go deeper:

Ask “why” multiple times.

Deadline missed. Why?
Because the task started late. Why?
Because priorities were unclear. Why?
Because instructions were not specific.

Now you’re getting somewhere.

Now the issue is not “missed deadline.”

It’s “lack of clarity in task assignment.”

That’s a different problem.

And it requires a different solution.

Third—fix the system, not just the situation.

This is the shift.

Instead of asking:

“How do I solve this now?”

Ask:

“What needs to change so this doesn’t happen again?”

Maybe it’s clearer instructions.

Maybe it’s better tracking.

Maybe it’s a simple checklist.

Small adjustments.

But repeated impact.

Fourth—build awareness in the team.

Because prevention is not just the manager’s job.

The team needs to understand patterns too.

So when a problem is solved—

Don’t just move on.

Share the learning.

“What caused this?”
“What will we do differently next time?”

Now the team grows.

Not just the manager.

Now here’s where most organizations struggle.

They know this makes sense.

But they don’t apply it consistently.

Because in the moment—

Fixing feels easier than analyzing.

That’s why this needs to be built into daily behavior.

Not taught once.

Practiced regularly.

This is where microlearning becomes powerful again.

Because instead of a one-time session on problem-solving—

You create a habit of reflection and prevention.

Here’s what that can look like.

Day 1:

Identify a problem you solved today.

Day 2:

Write what actually caused it.

Not the symptom—the cause.

Day 3:

Ask what change could prevent it.

Day 4:

Apply that change.

Even a small one.

Day 5:

Observe.

Did it improve?

Did the problem repeat?

That’s one cycle.

Simple.

But powerful.

Now imagine this across teams.

Managers don’t just react.

They reflect.

They adjust.

They improve systems.

And slowly—

Problems decrease.

Not disappear.

But reduce.

That’s when leadership shifts.

From busy…

To effective.

Now let’s talk about the impact.

Because this is where it becomes real.

When managers prevent problems:

Teams become more stable.

Work becomes smoother.

Fewer disruptions.

Less stress.

Better performance.

And most importantly—

Managers get their time back.

Because they are no longer solving the same issue again and again.

This is how organizations scale.

Not by solving more problems.

But by creating fewer.

And this is where HR can drive real change.

Because this is not about adding more training.

It’s about changing focus.

From:

“How do we improve problem-solving skills?”

To:

“How do we reduce recurring problems?”

Because that’s where efficiency lives.

That’s where growth happens.

So before your next leadership program rollout, take a moment.

Look at the issues your teams are facing.

How many of them are new?

And how many are just… repeating?

Because that tells you everything.

And then ask yourself:

Are your managers trained to fix problems… or to make sure those problems never come back?

The articles below from jordanimutan.com help leaders move from treating symptoms to curing the underlying organizational diseases.

1. Root Cause Analysis: Why “Five Whys” is a Manager’s Best Friend

This article is the perfect diagnostic companion. It explains that when problems recur, it’s because the manager solved the event but ignored the pattern. It teaches the “Five Whys” technique to help managers dig past the surface-level excuse and find the systemic failure.

2. The STRIDES™ Framework: Systematizing Excellence

If the same problems keep coming back, your “S—Systematize” pillar is likely broken. This piece explains how to turn a one-time fix into a permanent process. It focuses on creating “Standard Operating Procedures” (SOPs) that ensure once a problem is solved, the solution is baked into the company’s DNA.

3. Double-Loop Learning: How to Change the Thinking, Not Just the Action

This deep dive explains the difference between “Single-Loop” (fixing the error) and “Double-Loop” (fixing the mental model that allowed the error). It is essential reading for managers who feel like they are stuck in a “Groundhog Day” loop of repetitive mistakes.

4. Stop Being the Chief Problem Solver: Coaching Teams to Own the Solution

Often, problems return because the manager is the only one who knows how to fix them. This article discusses the “hero manager” syndrome and provides a roadmap for shifting problem-ownership to the team. It emphasizes that a manager’s job isn’t to have all the answers, but to ask the questions that lead the team to find them.

5. The Accountability Ladder: Shifting from “What Happened” to “How Do We Fix It Forever”

This piece explores the levels of accountability within a team. It helps managers identify if their team is stuck in “Wait and Hope” or “Tell me what to do” modes. By moving the team up the ladder, the manager ensures that the people closest to the problem are the ones empowered to kill it for good.

You Keep Checking Everything—And That’s Exactly Why Your Team Isn’t Growing

~ jordan ~ Leave a comment

You said you trust your team.

You’ve told them that more than once.

In meetings. In one-on-ones. Even casually, just to reassure them.

But your actions tell a different story.

You still review every output.
You still double-check decisions.
You still ask for updates… even when nothing has changed.

And when something goes wrong—you step in immediately.

Fix it.

Correct it.

Redo it.

Because it’s faster.

Because it’s safer.

Because it’s easier than dealing with the consequences of letting it slide.

And just like that, without meaning to…

You’ve become the bottleneck.

This is one of the most common leadership issues in growing organizations.

Not lack of talent.

Not lack of effort.

But lack of delegation.

Or more specifically—ineffective delegation.

Because let’s be honest.

Most managers think they are delegating.

But what they are really doing is this:

Assigning tasks… while keeping ownership.

And that changes everything.

Because when ownership stays with the manager—so does the responsibility to check, correct, and follow up.

Which means the workload never actually leaves their plate.

It just… multiplies.

If you’re leading HR or observing this across teams, you’ve likely seen the signs:

Managers complain about being overwhelmed—but refuse to let go.

Team members wait for approval—even for small decisions.

Work gets done—but only after multiple revisions.

And growth stalls—not because people can’t perform, but because they’re not allowed to.

Now here’s the uncomfortable truth.

This is not a team problem.

It’s a leadership behavior.

And it usually comes from a good place.

Managers want quality.

They want consistency.

They want to avoid mistakes.

So they stay involved.

Too involved.

But what they don’t realize is this:

Over-involvement kills capability.

Because when managers hold on to control—teams stop thinking.

They stop taking initiative.

They stop owning outcomes.

And over time, they become dependent.

Not because they lack skill.

But because they were never given the space to use it.

Let’s break down where delegation usually fails.

There are three common mistakes:

  1. Unclear expectations
  2. Lack of ownership transfer
  3. No follow-through system

Let’s go through each one.

First—unclear expectations.

Managers say things like:

“Can you handle this?”
“Please take care of it.”
“Make sure this gets done.”

Sounds simple.

But it’s vague.

What does “handle” mean?
What does “done” look like?
When is it expected?

Without clarity—people guess.

And when people guess—managers step in to correct.

And the cycle continues.

The fix is simple.

Be specific.

Not “handle the report.”
But “complete the report by Friday, including the summary and recommendations.”

Now the expectation is clear.

Now there’s a standard.

Second—lack of ownership transfer.

This is the silent killer.

Managers assign the task.

But they don’t fully release control.

They check in too often.

They adjust too early.

They step in at the first sign of struggle.

So the team member never truly owns the work.

And if they don’t own it—they won’t grow.

Real delegation means this:

You give the task—and the responsibility for the outcome.

Not just the activity.

The result.

That’s the shift.

Now does that mean no involvement at all?

No.

It means structured involvement.

Which brings us to the third issue.

No follow-through system.

Most managers fall into two extremes:

They either micromanage…

Or disappear completely.

Neither works.

Because delegation needs visibility—not control.

So instead of constant checking—set clear checkpoints.

Not random follow-ups.

Planned ones.

For example:

“Let’s review progress on Wednesday.”
“Send me your draft before finalizing.”
“We’ll align once before submission.”

Now there’s structure.

Now there’s accountability.

Without hovering.

This is where most traditional training misses the mark.

They teach delegation as a concept.

Explain the importance.

Give frameworks.

Then move on.

But delegation is not learned in one session.

It’s built through repetition.

Daily.

In real work.

This is where microlearning becomes powerful.

Because instead of a one-time discussion—you create a daily practice.

Here’s what that can look like.

Day 1:

Identify one task you should delegate—but haven’t.

Day 2:

Define the outcome clearly.

What does success look like?

Day 3:

Assign the task with full clarity.

Outcome. Deadline. Expectations.

Day 4:

Set a checkpoint.

Not to control—but to guide.

Day 5:

Review the result.

What worked? What didn’t?

What would you do differently next time?

That’s one cycle.

Simple.

Practical.

Applied.

Now repeat that over several weeks.

Managers start letting go.

Slowly at first.

Then more confidently.

Teams start stepping up.

Mistakes happen—but learning happens faster.

And something shifts.

Managers are no longer overwhelmed.

Teams are no longer dependent.

Work starts moving without constant supervision.

Now let’s address the fear.

Because this is where most managers hesitate.

“What if they mess it up?”

They will.

At some point.

But here’s the real question:

What’s the cost of not letting them try?

Because if managers keep holding on—

They stay stuck.

Their teams stay stuck.

And the organization stays dependent on a few people.

That’s not sustainable.

And it’s not scalable.

So the goal is not perfect delegation.

It’s progressive delegation.

Better each time.

Clearer each time.

More ownership each time.

Now imagine this across your organization.

Managers trust their teams—with structure.

Teams take ownership—without fear.

Work flows—without constant checking.

And leaders finally have space.

Space to think.

To plan.

To lead.

This is what effective delegation unlocks.

Not just efficiency.

But growth.

And this is where HR can drive real change.

Not by adding more training days.

But by changing how leadership skills are built.

Because the goal is not to teach delegation.

The goal is to make it a habit.

A daily behavior.

Something managers practice—not just understand.

So before your next leadership program rollout, take a step back.

Look at how work actually moves in your organization.

Look at how often managers step in.

Look at how much ownership teams really have.

And ask yourself:

Are your managers truly delegating… or just assigning work they still control?

The articles below from jordanimutan.com explore the “trust gap” and provide the tools needed to let go without losing control.

1. The Micromanagement Trap: Why High-Performers Struggle to Lead

This article explains the “competence bias”—the internal drive that makes leaders think, “I can just do it faster myself.” It breaks down how this mindset creates a ceiling for the team’s growth and offers a psychological shift for leaders to move from “Doer-in-Chief” to “Enabler-in-Chief.”

2. 7 Levels of Delegation: How to Trust Without Abandoning

The fear of “checking everything” usually stems from a lack of clear boundaries. This piece provides a tactical framework to decide how much freedom an employee should have based on their skill level. It helps you stop checking every email and start focusing on high-level outcomes.

3. The STRIDES™ Framework: Empowering Teams Through Systems

If you feel you must check everything, it’s often because there are no reliable systems in place. This article focuses on the “E—Empower” and “S—Systematize” pillars of the STRIDES™ methodology. It shows how to build “guardrails” so that the team can operate safely and correctly without your constant intervention.

4. Outcome-Based Leadership: Measuring Results, Not Activities

Managers who “check everything” are usually obsessed with the process. This article teaches you how to shift your focus to the result. By defining what “done” looks like at the beginning, you can step back from the “how” and only step in if the “what” is off track.

5. The LEAD Coaching™ Framework: Developing Independent Problem-Solvers

The more you check, the more your team depends on you. This piece introduces the LEAD (Listen, Explore, Align, Drive) framework as an alternative to “fixing” things. It teaches managers how to ask the right questions so that the employee learns to check their own work, effectively working the manager out of a job.

Your Managers Keep Avoiding Tough Conversations—And It’s Quietly Killing Your Team

~ jordan ~ Leave a comment

The meeting ended the way it always does.

Everyone nodded.

Everyone agreed.

Everyone walked out… knowing the real issue was never discussed.

You’ve seen this before.

A team member underperforming—but no one addresses it directly. A conflict between two employees—but it gets “managed” instead of resolved. A deadline missed—but the conversation focuses on effort, not accountability.

On paper, everything looks fine.

In reality, problems are stacking up.

And as an HR leader, you can feel it.

Not in reports. Not in dashboards.

In tension.

In silence.

In the things people don’t say.

Because one of the most common—and damaging—leadership gaps today is this:

Managers avoid difficult conversations.

And the longer they avoid them, the bigger the problem becomes.

Let’s be clear.

This is not a personality issue.

It’s not because your managers are “too soft” or “not assertive enough.”

It’s because they were never trained to handle difficult conversations properly.

So they do what most people do.

They delay.

They soften the message.

They hope the issue fixes itself.

Or worse—they escalate it to someone else.

And that’s where performance starts to break.

Think about the cost of avoided conversations.

Underperformance continues longer than it should.

High performers get frustrated because standards are unclear.

Small issues turn into bigger conflicts.

Leaders lose credibility—quietly.

And over time, a culture forms.

A culture where people talk around problems… instead of solving them.

Now here’s the tricky part.

Most managers know they should address issues directly.

They just don’t know how to do it without making things worse.

So instead of risking a bad conversation… they choose no conversation.

And that feels safer.

In the moment.

But more expensive in the long run.

This is where traditional training tries to help—and often falls short.

Managers attend a workshop on “Crucial Conversations” or “Effective Feedback.”

They learn frameworks.

They practice role plays.

They leave with confidence.

Then real life happens.

The situation is more emotional than the role play.

The person involved reacts differently.

The stakes feel higher.

And suddenly, the framework disappears.

Old habits return.

Avoidance wins.

So the problem is not awareness.

It’s not even skill.

It’s application under pressure.

And that’s where most leadership training breaks down.

Because it prepares managers for ideal situations—not real ones.

Let’s simplify this.

A difficult conversation has three basic parts:

  1. Clarity of the issue
  2. Courage to address it
  3. Skill to handle the response

Most managers struggle with all three.

They are not fully clear on what the real issue is.
They hesitate to bring it up.
And when they do—they don’t know how to navigate the reaction.

So instead, they choose silence.

Let’s fix that—step by step.

Start with clarity.

One reason managers avoid conversations is because they are not sure what they are addressing.

They say things like:

“Performance needs improvement.”
“Communication should be better.”
“Let’s be more proactive.”

These are vague.

And vague conversations don’t lead to change.

So the first shift is this:

Make the issue specific and observable.

Not “you lack initiative.”
But “the last three reports were submitted past the agreed deadline.”

Not “you have a bad attitude.”
But “in the last meeting, you interrupted two teammates and dismissed their ideas.”

Now the conversation has ground.

Now it’s real.

Next is courage.

And here’s the truth most leaders won’t say out loud:

Courage is not built in training rooms.

It’s built through repetition.

Small, consistent acts of speaking up.

Which is why one-time workshops don’t work.

Because courage fades when it’s not used.

So instead of expecting managers to suddenly become confident—you train them to take small steps.

Start with lower-risk conversations.

Build the habit.

Increase the stakes gradually.

That’s how confidence is actually formed.

Then comes skill.

And this is where most managers overcomplicate things.

They think they need the perfect words.

The perfect tone.

The perfect timing.

So they wait.

But effective conversations are not about perfection.

They are about structure.

Here’s a simple one:

State the observation → Explain the impact → Ask for response

Example:

“I noticed the last three reports were late. This delays the team’s planning and affects deadlines. What’s happening on your end?”

That’s it.

Clear. Direct. Open.

Not aggressive.

Not vague.

Just structured.

Now let’s talk about what usually happens next.

The response.

And this is where managers panic.

Because they expect resistance.

Defensiveness.

Excuses.

And sometimes—they get it.

But that’s part of the process.

A difficult conversation is not difficult because of what you say.

It’s difficult because of how people react.

So the goal is not to control the reaction.

It’s to handle it.

Stay calm.

Listen.

Clarify.

Bring the conversation back to the issue.

And most importantly—don’t back off too early.

Because the moment you soften too much—the message gets lost.

Now here’s where this becomes a leadership system—not just a skill.

Because knowing this is not enough.

Managers need to practice this.

Frequently.

In real situations.

With follow-through.

And this is where microlearning becomes powerful.

Instead of a one-day training on difficult conversations—you create a daily practice.

Short lesson.

One concept.

Immediate application.

For example:

Day 1: Identify one conversation you’ve been avoiding.
Day 2: Write the specific issue clearly.
Day 3: Plan how to open the conversation.
Day 4: Have the conversation.
Day 5: Reflect on what happened.

That’s one week.

One real issue addressed.

Now multiply that over several weeks.

Now managers are not just learning.

They are doing.

And that changes everything.

Because the skill becomes natural.

Not theoretical.

Managers start addressing issues earlier.

Conversations become clearer.

Problems get solved faster.

And the team feels it.

Not because of a training certificate—but because of daily behavior.

Now let’s address a common concern.

“What if managers make mistakes during these conversations?”

They will.

And that’s part of the process.

Because the alternative is worse.

Avoidance.

And avoidance doesn’t fix anything.

It just delays the problem.

So instead of aiming for perfect conversations—aim for consistent ones.

That’s what builds capability.

Now imagine the impact across your organization.

Managers don’t wait for HR to step in.

They handle issues early.

They communicate clearly.

They set expectations.

They address gaps.

And slowly, something shifts.

Accountability becomes normal.

Not forced.

Not escalated.

Just expected.

This is how culture changes.

Not through values written on walls.

But through conversations happening daily.

Or not happening.

And if you’re leading HR, this is where your influence is critical.

Because you are not just designing training.

You are shaping behavior.

So the question is not:

“Did we run a program on communication?”

The question is:

“Are managers actually having the conversations they used to avoid?”

That’s the real metric.

So if you’re looking at your current leadership development efforts—pause for a moment.

Look beyond attendance.

Look beyond feedback scores.

Look at behavior.

Are difficult conversations happening more often?

Are issues being addressed earlier?

Are managers stepping up—or stepping back?

Because that tells you everything.

Now here’s the shift.

Stop treating communication as a soft skill.

It’s not.

It’s a performance driver.

Because teams don’t fail because of lack of intelligence.

They fail because of lack of clarity.

And clarity comes from conversations.

The ones most managers avoid.

So instead of designing another broad leadership program—start here.

Teach managers how to handle difficult conversations.

But more importantly—build a system where they actually practice it.

Daily.

With real issues.

With real stakes.

Because that’s where growth happens.

And when managers start doing this consistently—you’ll see it.

Faster decisions.

Stronger accountability.

Better team alignment.

And fewer surprises.

Because problems are no longer hidden.

They are handled.

That’s when leadership starts to work.

Not in theory.

But in practice.

So before your next training rollout, ask yourself:

Are your managers trained to communicate… or trained to avoid?

For similar articles, you can click on any of the topics below.

1. The High Cost of Conflict Avoidance in Leadership

This piece serves as the “Part 2” to your topic. It quantifies the “invisible tax” companies pay when leaders stay silent. It explores how avoiding friction leads to “Artificial Harmony,” where teams seem to get along but fail to innovate or solve underlying performance issues.

2. Radical Candor: Balancing Personal Care with Direct Challenge

One of the biggest reasons managers avoid tough talks is the fear of being “mean.” This article introduces Kim Scott’s framework, teaching managers how to avoid “Ruinous Empathy”—the state of being so nice that you ultimately hurt the person’s career by withholding the truth.

3. Building Psychological Safety: The Foundation of Feedback

Tough conversations backfire if the team doesn’t feel safe. This article explains how to lay the groundwork for a culture where high-stakes feedback is seen as a gift rather than a threat. It emphasizes that accountability and safety must grow at the same rate.

4. The LEAD Coaching™ Framework: A Guide for Manager 1-on-1s

If a manager is struggling with how to start a difficult conversation, this article provides the script. Using the LEAD (Listen, Explore, Align, Drive) framework, it shows how to pivot a conversation from a problem to a solution without making the employee feel attacked.

5. From Micromanagement to Empowerment: Changing the Feedback Loop

Often, managers avoid tough talks because they don’t want to be perceived as micromanagers. This article clarifies the distinction: holding someone accountable to a standard isn’t micromanaging—it’s empowering them to succeed. It provides a roadmap for shifting the manager’s role from “policeman” to “coach.”

Your Training Works on Slides—But Not at Work. Here’s How to Finally Fix It.

~ jordan ~ Leave a comment

You approved the training.

You sat through the proposal. It sounded sharp. Structured. Proven. The facilitator had energy. The slides were clean. The feedback forms at the end? Strong. People even said things like “very insightful” and “great learning experience.”

Then Monday came.

And nothing changed.

The same managers escalated simple decisions. The same communication issues showed up in meetings. The same execution gaps quietly slowed down projects. It was as if the training never happened—except now you also had a line item in your budget reminding you that it did.

If you’re an HR executive, this is not new. It’s just frustrating.

Because the problem isn’t that your company doesn’t invest in training. The problem is… the training doesn’t stick.

And here’s the uncomfortable truth:
Most leadership training fails not because of the content—but because of the lack of application.

Let’s talk about how to fix that.

You don’t have a knowledge problem.

You have an application problem.

Think about your managers today.

They already know what good leadership looks like. They’ve heard it multiple times. Communicate clearly. Delegate effectively. Take ownership. Give feedback. Execute well.

They’ve attended workshops. Read books. Sat through seminars. Some of them can even repeat leadership frameworks word for word.

And yet—when they go back to work—they default to old habits.

They wait for instructions. They avoid difficult conversations. They escalate decisions instead of owning them.

Why?

Because knowing is not doing.

And traditional training is designed for knowing—not doing.

That’s where the disconnect begins.

Let’s break the pattern most trainings follow.

Day 1: Inspiration
People feel energized. They write notes. They say, “This makes sense.”

Day 2: Reality
They go back to work. Emails pile up. Deadlines hit. Urgency takes over.

Day 3: Regression
They revert to what’s familiar. Not because they don’t care—but because there’s no system forcing them to apply what they learned.

And that’s the key issue.

There is no bridge between learning and real work.

No structure. No reinforcement. No daily pressure to apply.

So even the best training fades.

If you’re leading HR, this is where the pressure sits.

You are expected to build leaders.

But the tools available to you often stop at awareness.

And awareness doesn’t move performance.

Application does.

So the question becomes:

How do you design a leadership development approach that actually changes behavior—not just mindset?

Start by focusing on one problem.

Not ten.

Not even five.

One.

Because one of the biggest mistakes in training design is trying to fix everything at once.

Communication. Delegation. Execution. Coaching. Emotional intelligence. Decision-making.

All important.

All relevant.

All too much.

When everything is taught, nothing is applied.

So let’s narrow it down.

One of the most common—and costly—issues across organizations is this:

Managers are not trained to execute consistently.

They start strong. Then lose momentum.

They understand the goal. But struggle to follow through.

They rely on motivation. Instead of systems.

And when execution breaks—everything breaks.

Deadlines slip. Teams get confused. Leaders step in to fix things. Bottlenecks form.

So instead of solving ten problems, start here.

Fix execution.

Now here’s where most training still gets it wrong.

They teach execution as a concept.

But execution is not a concept.

It’s a daily behavior.

Which means it needs daily reinforcement.

And this is where microlearning changes the game.

Microlearning is not about shorter content.

That’s the common misunderstanding.

It’s about continuous application.

Instead of pulling managers out for a full day or two…
You integrate learning into their actual workdays.

Short lessons. Daily.

Clear focus. One behavior at a time.

Immediate application. Same day.

And most importantly—follow-through.

Because the goal is not to “finish training.”

The goal is to change how managers behave at work.

Let’s walk through how this works in practice.

Day 1: A focused lesson.

Not a long lecture. Not a heavy framework.

Just one clear idea.

For example:
“Execution fails when tasks are not clearly defined.”

Simple.

Easy to understand.

Immediately relevant.

Then comes the critical part—application.

Managers are given a simple assignment:

Take one task you are currently handling.
Rewrite it using clear outcomes, deadlines, and ownership.

That’s it.

Not theoretical.

Not abstract.

Real work.

Day 2: Follow-up.

Managers reflect:

Did clarity improve?
Did the team respond better?
Was there less back-and-forth?

Now learning becomes visible.

Not because someone explained it better—but because they experienced it.

Then the next lesson builds on it.

Another small shift.

Another real-world application.

And over time—something changes.

Not in theory.

In behavior.

This is what traditional training misses.

It assumes change happens in a room.

But real change happens at work.

In emails. In meetings. In decisions. In daily execution.

So training needs to live there.

Now let’s address the concern most HR leaders have:

“Will managers take this seriously if it’s short?”

The answer is yes—if it’s relevant and required.

Because here’s what managers don’t have:

Time for long sessions.

But here’s what they do have:

Work.

So when learning is tied directly to their work—it becomes useful.

And when it’s measured—it becomes real.

This is another critical piece.

Measurement.

Not attendance.

Not satisfaction scores.

Actual application.

Did they apply the lesson?
What changed?
What improved?

Because if you don’t measure application—you’re still guessing.

And HR has done enough guessing.

Now imagine this shift across your organization.

Managers are not waiting for quarterly training.

They are improving weekly.

Small adjustments. Continuous.

Communication becomes clearer.

Delegation becomes sharper.

Execution becomes consistent.

Not overnight.

But steadily.

And that’s the point.

Leadership development is not an event.

It’s a process.

Let’s make this practical.

If you were to redesign your leadership training today, focusing on execution, here’s what it would look like:

  1. One Core Focus
    Start with execution. Not everything else.
  2. Daily Micro Lessons (5–10 minutes)
    Clear. Simple. Actionable.
  3. Same-Day Application
    Every lesson is applied immediately to real work.
  4. Next-Day Reflection
    Capture what happened. What worked. What didn’t.
  5. Weekly Summary
    Managers review how their behavior changed over the week.
  6. Visible Tracking
    HR sees progress—not just participation.

This is not complicated.

But it is different.

And that difference is what creates results.

Now here’s where customization matters.

Because while execution is a common problem—the context varies.

A startup might struggle with structure.

A large organization might struggle with speed.

An operations team might struggle with consistency.

So the examples, scenarios, and assignments need to match their reality.

That’s how relevance is built.

And relevance is what drives engagement.

Let’s address another reality.

Some managers will resist.

Not openly.

But quietly.

They will say they are busy.

They will delay assignments.

They will participate halfway.

This is normal.

Because behavior change is uncomfortable.

So the system needs to account for that.

Short lessons remove time excuses.

Daily tracking creates accountability.

And leadership support reinforces importance.

Without these—training becomes optional.

And optional training doesn’t work.

Here’s the shift HR leaders need to make.

Stop asking:

“Did they learn something?”

Start asking:

“Did they do something differently?”

Because that’s where impact lives.

Not in notes.

Not in feedback forms.

In changed behavior.

And once that shift happens—everything else follows.

Managers start thinking independently.

Decisions move faster.

Teams become more aligned.

And leaders stop being bottlenecks.

Not because they were replaced.

But because they were finally supported properly.

This is where microlearning becomes more than a format.

It becomes a system.

A way to continuously build leadership capability—without pulling people away from work.

And more importantly—without wasting time on training that doesn’t translate.

Let’s be direct.

The cost of ineffective training is not just budget.

It’s performance.

It’s delays.

It’s missed opportunities.

It’s leaders stepping in when they shouldn’t have to.

And over time—it compounds.

So fixing this is not optional.

It’s necessary.

But here’s the good news.

You don’t need to overhaul everything.

You don’t need to redesign your entire L&D strategy overnight.

You just need to start differently.

Start with one problem.

Execution.

Build a system around daily application.

Measure behavior—not attendance.

And adjust based on what actually works.

Because at the end of the day, the goal is simple.

Not better training.

Better managers.

Managers who can think.

Decide.

Execute.

And lead without constant supervision.

That’s the real outcome.

And once you see that shift—even in a small group—it becomes clear.

This is how leadership is built.

Not in one big moment.

But in small, consistent actions.

Done daily.

So before you approve your next training program, pause.

Ask yourself this:

Are you investing in learning… or in behavior change?

Because only one of those actually shows up at work.

Related Articles

1. How to Use the LEAD Coaching™ Framework in a 1-on-1

While your initial article discusses why training fails, this piece provides a practical tool to ensure it succeeds. It breaks down the LEAD (Listen, Explore, Align, Drive) framework, showing managers exactly how to move from “giving instructions” to “growing responsibility” during daily interactions.

2. Sustain the Momentum: Making Success Last After the Workshop

Part of the STRIDES™ methodology, this article focuses on the “Transfer of Knowledge.” it addresses the specific challenge of what happens when the consultant or trainer leaves, offering toolkits like “Internal Champion Toolkits” and “Continuity Plans” to keep execution alive.

3. Training and Development: Equipping Middle Managers for Change

This article explores why middle managers often resist new training and how to turn that skepticism into support. It emphasizes that training should not just be about new technologies but about building “support systems” and “peer groups” to navigate the transition from classroom to office.

4. Measure and Evaluate Training Effectiveness: Moving Beyond Satisfaction Scores

A key reason training “stays on the slides” is that companies measure the wrong things (like how much people liked the trainer). This article discusses setting specific, measurable goals such as improved team performance and KPIs, ensuring that the training’s impact is visible in the business results.

5. Social Learning: Unleashing the Wisdom of the Crowd

Learning transfer often fails because it happens in isolation. This article argues that for training to work at work, it must be social. It discusses using peer-to-peer mentoring and collaborative platforms to ensure that what is learned in a workshop is reinforced through daily social exchange and “democratized coaching.”

The Decision Gap: Why Your Startup Managers Aren’t Slow—They’re Just Waiting for You

~ jordan ~ Leave a comment

The office clock in your Makati headquarters strikes 6:00 PM. You are hunched over your desk, reviewing a stack of “urgent” requests. Your Marketing Manager is waiting for you to approve a single Facebook ad headline. Your Operations Lead is waiting for you to sign off on a small equipment repair. Your Sales Head is waiting for your “final look” at a standard client proposal.

You feel like a hero. You are the engine that keeps this company running. But as you look at your team, you feel a quiet frustration: Why is everyone so slow? Why can’t they just get things done?

If you’ve been searching for leadership training for startup founders or looking into how to build a corporate structure for a small business, you likely think your problem is “efficiency.” You think you need faster people.

The truth is much harder to swallow: Your managers aren’t slow. They are perfectly capable. They just don’t decide. And the reason they don’t decide is because you have unintentionally built a culture where “the founder’s word” is the only thing that matters.

To scale, you must move from being a centralized bottleneck to a leader who delegates accountability.

The Story of Paulo and the “Approval Trap”

Paulo founded a successful logistics startup. He was a brilliant problem solver. In the early days, his speed was his competitive advantage. If a courier was lost, Paulo found them. If a client was angry, Paulo called them.

As the company grew to forty employees, Paulo hired experienced managers. But something strange happened. These high-level hires—people with impressive resumes—seemed to lose their edge the moment they started working for him. They became “order takers.”

Paulo’s search for business operations consulting for founders led him to a realization: He was suffering from the Approval Trap. Because Paulo had a habit of “tweaking” every decision his managers made, his managers stopped making them. They realized that making a choice was a waste of energy because Paulo would eventually change it anyway.

They weren’t slow; they were waiting. They were waiting for Paulo to give them the answer so they wouldn’t have to risk being “wrong.”

Lesson 1: Clarity of Direction (The “Success Criteria” Shift)

Managers don’t decide because they don’t know what “right” looks like in your eyes. Most founders provide vague goals and specific instructions. To scale, you must do the opposite: Provide specific goals and vague instructions.

  • The Bottleneck Way: “Make the new website look premium.” (Subjective. They will wait for you to “feel” if it’s premium).
  • The CEO Way: “The new website is successful if it reduces our bounce rate by 10% and follows the minimalist brand guidelines in our handbook.” (Objective. They can decide based on data).

When you provide Clarity of Direction, you give your team a yardstick. They no longer need to ask for your opinion because the goal is the judge, not you.

Lesson 2: Radical Delegation (Handing Over the “Baton”)

Delegation is not a task; it is a transfer of authority. If you tell a manager to “run a project” but then jump into their Slack threads to correct minor details, you haven’t delegated. You’ve just hired a very expensive personal assistant.

To move to a corporate structure, you must give the “baton” and stay on the sidelines. This means accepting the 80% Rule: If a manager can do a task 80% as well as you can, let them do it. The 20% “loss” in quality is the price you pay for the 100% gain in your own time.

Lesson 3: Not Being a Bottleneck Owner (The “Wait and See” Strategy)

The fastest way to train your managers to decide is to stop being so helpful. Paulo implemented a “No-Answer Monday.” When a manager came to him with a problem, he wasn’t allowed to solve it. He could only ask:

  1. “What does the data say?”
  2. “What is your recommendation?”
  3. “What is the risk of doing nothing?”

By refusing to be the “Answer Man,” Paulo forced his managers to exercise their decision-making muscles. He stopped being the owner of every problem and became the Architect of Accountability.

Lesson 4: Designing Systems, Not Solving Fires

If you are constantly putting out fires, you are a firefighter. Firefighters don’t have time to build skyscrapers. To scale your startup, you must move from “firefighting” to System Design.

Every time a manager asks you for a decision, ask yourself: “What system is missing that would have allowed them to decide this without me?”

  • Is it a lack of a clear budget?
  • Is it a missing SOP (Standard Operating Procedure)?
  • Is it a fear of failure?

Fix the system, not the fire. When you build a system of accountability, you aren’t just offloading work; you are building a company that can thrive while you sleep.

The Goal: The “30-Day Test”

How do you know if you have successfully stopped being a bottleneck? Take the 30-Day Test. If you were to leave your office for 30 days, would your managers keep the company on course, or would they sit in the lobby waiting for your return?

A company that can’t decide without its founder isn’t a business; it’s a very stressful hobby. True scaling happens when your team stops asking, “What does the boss want?” and starts asking, “What does the goal require?”

If you stopped answering “quick questions” for the next 48 hours, which of your managers would step up to lead, and which would wait in silence?

Relevant Articles from JordanImutan.com

The “Invisible” CEO: Building a Startup Structure That Doesn’t Break When You Step Away

~ jordan ~ Leave a comment

It’s 3:00 PM on a Friday in your office overlooking the Makati skyline. You’ve just finished your eighth meeting of the day. Your throat is dry, your head is spinning, and you realize you haven’t actually “worked” on your business strategy in weeks. You’ve spent the entire day giving permissions, answering “quick questions,” and proofreading emails that your managers should have handled themselves.

You started this company to build something bigger than yourself. But right now, the company is you. If you don’t show up, the gears stop turning.

If you’ve been searching for how to move from founder-led to a professional management structure or leadership training for startup CEOs, you are likely facing the same wall every successful founder hits: the centralization ceiling.

The problem isn’t that your team is incompetent. The problem is that you are too helpful. By being the “Hero” who saves every project, you have become the ultimate bottleneck. To scale, you must move from being the owner of every task to being the architect of a system.

Here is how to stop being the “everything” person and start being the CEO your company needs.

The Story of Clara and the “Magic” Vacation

Clara founded a thriving logistics tech startup. She was brilliant, energetic, and possessed a “founder’s eye” for detail. She personally interviewed every hire, signed off on every social media post, and was the only one who could handle a direct call from their biggest client.

Clara felt essential. But she was also exhausted. She felt like she was carrying the weight of thirty people on her shoulders. She started looking for a business scaling consultant for founders because she thought she needed better “time management.”

Then, Clara was forced to take a sudden, ten-day leave for a family matter. She went “dark”—no Slack, no email, no calls.

She expected to return to a smoldering ruin. Instead, she returned to a team that was… fine. In fact, they were better than fine. In her absence, the Operations Manager had finally overhauled the delivery tracking system—a project Clara had been “meaning to get to” for months. The Marketing Lead had launched a new campaign that was outperforming their previous ones.

Clara realized a painful truth: Her constant presence wasn’t helping the team; it was hovering over them. She was the bottleneck because she hadn’t given them the Accountability to lead.

Lesson 1: Clarity of Direction (The Compass, Not the Steering Wheel)

The first reason founders become bottlenecks is a lack of clear direction. When the destination is fuzzy, the team will constantly ask you which way to turn.

Most founders give instructions. A CEO gives Clarity of Direction.

  • The Instructions (Bottleneck): “I want you to call these five clients today and offer them a 10% discount if they renew their contract by Friday.”
  • The Direction (Scalable): “Our goal for this month is a 95% retention rate. You have the authority to offer up to a 15% discount for early renewals. I trust your judgment on which clients need it most.”

When you provide the “What” and the “Why,” you empower your team to figure out the “How.” If you are still explaining the “How,” you haven’t defined the “What” clearly enough.

Lesson 2: Radical Delegation (Giving Up the “Legos”)

In the early days, you did everything. You owned all the “Legos.” But as you grow, you have to give those Legos away.

Delegation is not “assigning a task.” It is transferring ownership.

Many founders “delegate” but then jump into the Slack thread or the Google Doc to make “minor suggestions.” This is a trap. Every time you “tweak” a team member’s work, you take back the ownership. You signal to them that their work isn’t final until you’ve touched it.

To move to a corporate structure, you must give the baton and let the other person run. Even if they run a slightly different route than you would. Even if they stumble. Accountability only exists when the person feels the full weight of the responsibility.

Lesson 3: System Design Over Problem Solving

When a team member comes to you with a problem, your founder instinct is to solve it. You’ve been solving problems since day one. It’s your superpower.

But as a CEO, solving a problem is a failure of leadership. Wait—read that again. If you solve the problem, you’ve helped one person one time. If you design a system to solve the problem, you’ve helped the company forever.

  • The Problem Solver: Fixes a bug in a client’s account.
  • The System Designer: Asks the Engineering Lead, “What part of our QA process allowed this bug to reach the client, and how do we change the code-review system to prevent it from happening again?”

To stop being a bottleneck, your primary job is to build the “machine” that solves the problems, not to be a gear inside the machine.

Lesson 4: The Accountability Map

If you are looking for leadership coaching for tech founders, the most practical tool you can build is an Accountability Map.

This isn’t a traditional organizational chart. An organizational chart shows who reports to whom. An Accountability Map shows who is “on the hook” for specific outcomes.

  • Who owns the “Customer Acquisition Cost”? (If it’s you, you’re the bottleneck).
  • Who owns the “Employee Retention Rate”? (If it’s you, you’re the bottleneck).
  • Who owns “Product Uptime”? (If it’s you, you’re the bottleneck).

Every major metric in your business should have one name next to it. And as much as possible, that name should not be yours. Your name should only be next to the “North Star” metrics: Vision, Culture, and Capital.

The Goal: The “30-Day Test”

How do you know if you’ve successfully moved from a centralized owner to a CEO? Take the 30-Day Test.

If you were to step away from your business for 30 days, would the company grow, stay the same, or shrink?

A company that shrinks without its founder is a job. A company that grows without its founder is an asset.

To build an asset, you must be willing to be “less important” in the day-to-day. You must find your value not in being the smartest person in the room, but in being the person who built the room and filled it with people smarter than yourself.

Are you building a business that is fueled by your exhaustion, or one that is powered by your team’s autonomy?

Relevant Articles from JordanImutan.com

The “Founder’s Speed” Fallacy: Why Your Quick Thinking is Slowing Down Your Startup

~ jordan ~ Leave a comment

The office is quiet, but your mind is racing. You’ve just spent the last four hours “helping.” You helped the design team pick a font. You helped the sales lead draft an email to a Tier-1 prospect. You helped the office manager decide on the new health insurance provider.

To you, this feels like high-octane leadership. You are fast, you are decisive, and you are keeping the wheels turning. But if you look closely at your team, you’ll see a different story. They aren’t moving faster; they are standing still, waiting for your next “input.”

If you are searching for leadership training for startup founders or how to scale a business without the founder, you have likely hit the “Founder’s Speed” wall. You think your involvement accelerates the company, but in reality, you have become a human stoplight.

The problem is centralization. When every path leads back to your desk, you aren’t a leader—you are a bottleneck owner. To scale, you must trade your speed for your team’s accountability.

The Story of David and the “Decision Debt”

David founded a fintech startup in Manila that was growing at 20% month-over-month. David was a “fixer.” He prided himself on his 30-second response time on Slack. He thought that by being available 24/7, he was empowering his team.

But David’s team was suffering from “Decision Debt.” Because David made all the hard choices, his managers never developed their own “judgment muscles.” Whenever a complex problem arose, they simply tossed it to David.

David’s search for business operations consulting for founders led him to a startling realization: his team wasn’t lazy; they were logically adapted to his behavior. Why take a risk on a decision when David will just override it or do it himself in half the time?

David had to learn the hardest lesson in scaling: Your job is no longer to make the right decision; it’s to ensure the right decision gets made without you.

Step 1: Clarity of Direction (The “Success Criteria” Shift)

The main reason founders jump into the “How” is because they haven’t clearly defined the “What.” If your team doesn’t know exactly what a win looks like, they will naturally ask you to check their work.

To break the cycle, you must provide Clarity of Direction.

  • The Bottleneck Way: “Make the landing page look more professional.” (This is subjective; they need you to “approve” what “professional” means).
  • The CEO Way: “The goal of this landing page is a 15% conversion rate for users aged 25–35. It must load in under two seconds and align with our brand’s ‘minimalist’ style guide.”

When you define the Success Criteria, you give your team a yardstick. They don’t need to ask if you like it; they can look at the data and the style guide and know for themselves.

Step 2: Radical Delegation (Handing Over the Keys)

Delegation is not a chore you offload; it’s an investment in capacity. Most founders delegate “tasks” but keep the “authority.”

  • Task Delegation: “Research three CRM systems and show me the options.” (You are still the decision-maker).
  • Authority Delegation: “You are the owner of our Sales Tech Stack. Your goal is to implement a CRM that reduces lead response time by 50% within a ₱100,000 budget. You have the final sign-off.”

When you hand over the authority, you are moving from an owner-led model to a corporate structure. You must be prepared for them to choose a CRM you might not have picked. As long as it hits the goal, you must stay silent.

Step 3: Not Being a Bottleneck Owner (The “Wait and See” Rule)

To stop being a bottleneck, you have to embrace the silence. David implemented a “24-Hour Hold” on all non-emergency questions. When a manager asked, “What should we do about X?”, David would wait.

Often, within four hours, the manager would message again: “Actually, I figured it out. We’re going with option B because it saves us time on implementation.”

By refusing to be the “Answer Man,” David forced his team to become “Solution Owners.” He moved from being the center of the web to being the architect of the system.

Step 4: Systematizing Accountability

Accountability isn’t a lecture; it’s a structure. To scale, you need a way to track results that doesn’t involve you hovering.

  1. The Scoreboard: Does every department have one number they are responsible for?
  2. The Cadence: Do you have a regular, brief meeting where they report on that number?
  3. The System: If the number is off-track, do they have a process to diagnose why before they come to you?

When you build these systems, you are no longer managing people; you are managing the process. This is how you move from a frantic startup to a professional organization.

The Goal: Becoming the “Invisible” CEO

The ultimate sign of a successful founder-to-CEO transition is when your team handles a crisis and you only hear about it after it’s solved. This isn’t a sign that you are unnecessary; it’s a sign that you have built a masterpiece.

When you stop being the bottleneck, you gain the one thing every founder craves: Time. Time to look at the horizon, time to build the next big thing, and time to lead the company where only you can take it.

If you disappeared from your business for two weeks, would your team grow in your absence, or would they simply wait for you to return?

Relevant Articles from JordanImutan.com

7-Point transformational tips

~ jordan ~ Leave a comment

suzanne-d-williams-VMKBFR6r_jg-unsplash.jpg

Photo by Suzanne D. Williams on Unsplash

There is no silver bullet for all transformational needs. Every company has its own culture, needs, peculiarities, uniqueness, management maturity, leadership competencies that affect what approach will be successful.

Even though we often hear about how a big percentage of transformations fail, we should also look at the positive side. How did the smaller percentage of companies that have successfully transformed do it? What was their secret recipe? There is something in common about the way successful companies executed their transformation programs.

Here are my thoughts.

Tips to a successful transformation

  1. Clear and well communicated Vision. Answer the question “Why do we need to transform?”

What will the company look and feel like at the end of the transformation program? If the leadership cannot or does not paint a clearly articulated picture of it then how will the company know if it has reached its transformational journey? Too often companies jump into the transformational bandwagon without taking the time to paint this picture. Successful companies do not transform for the sake of transformation. IBM CEO Lou Gerstner clearly painted a picture of IBM moving from a computer selling company to an IT Service Provider. They transformed from selling boxes of computers (which they were losing money) to selling services. This clear transformation saved IBM from bankruptcy.

The organization must also understand the ‘why’ behind the transformation. If this is not clear, at least two negative things may happen. Employees will think that this is just the next ‘flavor of the month’ program of the executives. They do not see the burning platform behind the need to change. The other outcome for not explaining the ‘why’; employees will speculate why the company is transforming. Things like ‘we are going bankrupt, we are being merged with a bigger company, we are down-sizing’ and other negative rumors will start spreading across the organization.

  1. Core cross-functional process improved. Creating change teams. Core process to be re-built around company values.

Products and services are delivered through 3-5 Cross-functional Core processes. Companies that starts losing marketing share or incur high customer attrition is usually partially caused by faulty cross-functional core processes. These core processes may have been efficient when the company was starting or was smaller than it is today. However, the growth and direction of the company may no longer be reflected in its core processes.

One of GE’s strength under the leadership of Jack Welch was its ability to improve its core process. Six Sigma was implemented across the different GE affiliates. The initiative was sponsored and fully supported by the group CEO. In the earlier days of Jack Welch, executives were expected to understand and run Six Sigma programs. The program was so effective that is was merged with Toyotas LEAN program. The result is the popular Lean Six Sigma. In a nutshell, Lean Six Sigma is about reduction of a core processes errors and cycle time. Let’s take a simple example; customer service. A customer is better serviced if the company has minimal mistakes in its service and the delivery of service takes little time. This can apply to products as well. Delivering products with less or no defect at the shortest possible time is an advantage to any company.

  1. Bottom-up problem solving

Problem definition is best done from the field and not the boardroom. Too many times, I have witnessed decision making being done by people removed from actual customer touch-point. They are done through personal views and opinions. To make things worse, decisions and problem definition is being done in the absence of data.

In transformation programs, we often forget that problems will be surfaced and needs resolution. Two things to remember in problem-solving. One, we need to involve people closest to the problems. They feel the problem and often know the root cause. We just need to have the humility to ask them. Two, we need to equip them. There are several problem solving and decision-making tools. We need to equip employees with these techniques. It’s similar to asking employees to build a birdcage and yet not provide them the training and tools to carry out the job. A client of mine did a similar tact years ago. This huge retail company was in the middle of a massive change. They engaged us in customized change management & psdm (problem-solving and decision making) programs. They ran these in dozens of batches for company managers.

  1. Alignment of Structure/Systems and Staff

Transformation will always cause realignments. We need to take this into careful consideration. Organizational structures need to be reviewed in light of the transformation. Systems and processes need to be updated in light of the transformation. Staff and job profiles need to be reviewed and updated in light of the transformation. Transformation programs need to be implemented with sustainability in mind. Transformation needs to be designed for the long term and not short-lived.

For sustainability, we need to take these three things into careful consideration. Most transformations fail or are short-lived because these three things were neglected or not taken seriously.

  1. Inside-out approach

In order to transform your company, you first need to transform your people. We don’t mean compliant transformation. Compliant transformation means that people ‘transform’ for the sake of compliance. It’s temporary and superficial.

Transformation must make the drop from the head to the heart. It starts with logic but makes its way to our emotions. If the transformation program does not make that drop then it’s simply compliant and not sustainable. It will be just another fad that executives are trying to implement.

Transformation workshops need to be designed to transform lives. Transformed lives sustain transformed organizations. This is what we (Vanguard Center for Leadership) are good at.

  1. Top-down.

This is the classic ‘walk-the-talk’. We cannot have our leadership talk about transformation and yet do not embody it. Transformation workshops need to start from the top. I had luxury supermarket client before that reached out to me for guidance on an interesting topic. The French CEO said that his company was good at creating strategies and plans. However, execution was another thing. They were terrible at it. Plans would get delayed, project managers would get lost in the handover, project costs would sky-rocket. The CEO needed a simple Project Management/Change Management and PSDM (Problem Solving and Decision Making) program. We provided them a template driven and simple Effective Execution program we used in a large Middle East Bank I used to work for.

As a good leader, the CEO got himself and his first level executives trained in the program. This is clearly ‘walking the talk’. He then set-up a Projects Office (as per our guidance) to make sure that all projects followed the process and their progress is reviewed on a regular basis. All his store management team where then trained on the same program he attended. This way, they talk the same language. Two years later and with another CEO sitting at the helm, the company is still using the methodology and the governance is still in place.

  1. Culture integration

You cannot have your transformation program going in one direction and yet sustaining a culture moving in another direction. Transformation programs must be designed to change culture. I remember a great British Manager saying ‘culture is what you allow to grow.’ It is people that defined the culture of a company. To be more specific, it’s the leaders and how they behave that molds a company’s culture. This is the very reason why we need to have a top-down approach. This is the reason we need an inside-out approach.

There are other things to consider in a successful transformation. For instance, we did not tackle the need to reflect the transformational goals in the performance management system of a company. Aligning transformational goals from top-to-bottom is essential. We also did not tackle the identification of the vital few measures to help us keep track of progress. What measures matter and how should we quantify them. For instance, improving customer complaints by 70% does not really make much sense. It would be better to say ‘reducing the average monthly customer complaint from an average of 700 to less than 20.’

Each transformation journey will be unique. Let’s begin it with the 7 tips and you will be off to a better start with your transformation program. Transformation is never easy; however, we hope that the tips will make it an easier journey for you.

Feel free to reach out if there is any topic in transformation you want us to cover.

Click here for the podcast version.