A leadership pilot program — a small test run of a training initiative with one group of managers before it goes company-wide — can prove the idea works. It doesn’t prove the company can run it at ten times the size.

Enterprise scale should be earned through proof, not assumed in the proposal — and that’s true even after the proof shows up.

Why a proven pilot program still isn’t a scaling plan

A pilot program with 20 managers and a rollout to 400 managers aren’t the same program at a different size. They’re two different delivery problems wearing the same curriculum. The pilot ran with one skilled facilitator who knew the material cold, one sponsor paying close attention, and a group small enough that quality control happened naturally. None of that survives multiplying the program by ten without deliberate design.

Three things that quietly break at scale

Facilitator consistency. The pilot facilitator — the person who actually delivers the training — was excellent, maybe the best in the building. At scale, you need five or ten facilitators delivering the same standard, and “find more people exactly like the first one” isn’t a plan.

Measurement discipline. Tracking adoption and evidence for one group of 20 managers is manageable by hand. Tracking it across ten groups of 40 requires a system, an owner, and a rhythm — or the dashboard quietly turns back into a simple attendance report.

Sponsor attention. One executive sponsor could realistically pay attention to one pilot program. Spread across ten sites or functions, that same attention gets diluted fast, and the thing that made the pilot program work — someone who actually cared about the result — gets lost in the handoff.

What earning the right to scale actually requires

Scaling well isn’t bigger budget and more sessions. It requires:

• Facilitator enablement — a way to train and calibrate multiple facilitators against the same standard, not just hand them the same slides.
• Group-by-group ownership — a named person accountable for each new group added, with clear authority to make changes mid-rollout.
• A reporting rhythm that survives size — a dashboard and review schedule built to handle ten groups as cleanly as it handled one, not a spreadsheet someone updates when they remember.

Skip these, and the thing that made your pilot program credible — real evidence, real adoption, a sponsor who cared — quietly erodes with every group you add, until the company-wide version looks a lot like the attendance-driven programs you were trying to avoid in the first place.

The question worth asking before you scale up

If you multiplied your pilot program’s delivery model by ten tomorrow, would the same quality, the same measurement discipline, and the same sponsor attention survive — or would you be scaling the slides and quietly losing everything that made the pilot program work?

If the honest answer is “we’d lose something,” that’s worth designing for now, not discovering after the sixth group has already started. Message Jordan if you’d like to think through what your proven pilot program actually needs to scale without losing what made it work.

Further reading on jordanimutan.com:

• Turn Capability Into Consistent Execution — https://jordanimutan.com/turn-capability-into-consistent-execution/

• Group Coaching Beats One-on-One Advice: Why Managers Learn Faster Together — https://jordanimutan.com/2026/08/27/group-coaching-beats-one-on-one-advice-why-managers-learn-faster-together/

#LeadershipDevelopment #ScalingPrograms #TrainingROI #HRLeadership #OrganizationalExecution

A leadership pilot program — a small, time-limited test of a training initiative with one group of managers before rolling it out company-wide — can succeed on paper and still tell you nothing. That’s not a contradiction. It’s the most common mistake in program evaluation.

Stop or redesign a pilot program when the conditions it ran under make the result impossible to trust.

Why a “successful” pilot program can still be worthless

Picture this: a 90-day pilot program wraps up, the business indicator moved in the right direction, and everyone’s ready to recommend rolling it out to the whole company. Except the group of managers who took part — the cohort — was hand-picked by supervisors who chose their strongest performers. Or half the cohort missed more than a third of the sessions, and nobody tracked who actually participated versus who showed up once. Or a new system rolled out in the same quarter, and nobody can say how much of the movement came from that instead.

None of these pilot programs failed in the usual sense. They “worked.” The problem is nobody can actually say why — and a result you can’t explain is not evidence you can build a company-wide investment on.

Three conditions that quietly poison a pilot program’s results

Before trusting any pilot program’s result, check for these:

• Selection bias. Were participants chosen because they were likely to succeed anyway, rather than representing the real population this program needs to work for?
• Inconsistent participation. Did everyone actually complete the assignments and reviews, or did completion vary so widely that the cohort isn’t really one group?
• Uncontrolled change. Did something else happen at the same time — a new system, a leadership change, a seasonal swing — big enough to explain the result on its own?

If any of these are true and nobody accounted for them, the honest conclusion isn’t “it worked.” It’s “we don’t actually know.”

The harder, more credible move

It takes real discipline to look at a pilot program with a positive-looking number and say, “this doesn’t prove what we hoped it would prove.” It’s uncomfortable in a room full of people who want a win to report upward. It’s also the only position that protects you six months later, when the company-wide version doesn’t deliver the same result and someone asks why.

A redesigned pilot program — same business priority, cleaner conditions, a real baseline measurement, participants chosen by criteria instead of convenience — costs less than a company-wide rollout built on a number nobody can defend.

Three questions before you recommend scaling up

Before taking any pilot program’s result to leadership as proof, ask:

1. Were the participants representative of the population this needs to work for, or were they the easiest group to succeed with?
2. Can we actually account for who did and didn’t engage with the practice, not just who was invited?
3. Is there anything else happening in the business during this window that could explain the result on its own?

If you can’t answer these with confidence, the pilot program isn’t finished. It’s inconclusive.

A question worth sitting with

If someone challenged your last pilot program’s result and asked you to defend exactly who participated and how consistently — could you?

If the honest answer is “not really,” that’s worth fixing before the next recommendation goes to your board. Message Jordan if you’d like a second opinion on whether your next pilot program’s design will actually hold up to scrutiny.

Further reading on jordanimutan.com:

• How to Improve Manager Performance in 90 Days — https://jordanimutan.com/2026/08/21/how-to-improve-manager-performance-in-90-days-stop-training-for-attendance-and-start-training-for-behavior/

• Why Your Leadership Training Isn’t Working (And What To Do Instead) — https://jordanimutan.com/why-your-leadership-training-is-not-working/

#LeadershipDevelopment #PilotProgram #TrainingROI #HRLeadership #EvidenceBasedLD

You don’t need AI to do your job. You need it to do the part of your job you’ve stopped noticing you hate.

That’s the mistake behind most AI rollouts that quietly go nowhere. Someone pictures AI taking over a whole role — the thinking, the judgment calls, the relationships that come with the title — and when that doesn’t happen cleanly, the whole effort gets written off as “not ready yet” and shelved.

But a role was never the right unit to automate. A task is.

Every job is really two jobs stacked together

Look closely at almost any role, and you’ll find it’s made of two very different kinds of work. One part is judgment: reading a room, deciding what matters, weighing a trade-off nobody wrote down the rules for. The other part is repetition: pulling the same numbers, writing the same kind of update, reformatting the same report, answering the same three questions in a slightly different order every time.

The judgment part is what the person was actually hired for. The repetition part is what quietly eats their week.

Most companies try to hand AI the whole job at once. A smaller number hand it nothing at all, worried about losing the judgment part entirely. Almost nobody stops first to separate the two.

A finance manager, not a finance job

I worked with a finance manager recently whose week revolved around a Friday report. The report itself required real judgment: flagging which numbers mattered, deciding what to escalate, framing a recommendation for leadership. That part was the job. Nobody wanted AI anywhere near it.

But building the report took her close to four hours every week — pulling data from three different systems, formatting the same tables the same way, writing the same three boilerplate paragraphs that opened each section. None of that required her judgment. It required her patience.

So we didn’t ask AI to write her recommendation. We asked it to assemble the raw report: pull the numbers, format the tables, draft the boilerplate. That freed her four hours to spend on the one hour of actual thinking the report had always needed from her.

That’s the twenty percent. Not twenty percent of her time — twenty percent of the task. The mechanical slice sitting underneath the judgment slice. The part that was never really her job to begin with, just the toll she paid to get to it.

The same pattern shows up almost everywhere

Once you start looking for it, the pattern repeats across every department.

An HR coordinator screening résumés isn’t really being paid to read five hundred of them. She’s being paid to recognize the dozen worth a second look. The first pass — checking for basic requirements, sorting by years of experience, flagging obvious mismatches — is the mechanical slice. The judgment happens after that, in the dozen she actually reads closely.

A sales manager isn’t paid to type up call notes. He’s paid to notice which deal is quietly slipping and decide what to do about it. The notes are the toll. The read on the deal is the job.

In every case, the twenty percent looks different, but the shape is the same: a mechanical task that has to happen before the real thinking can start, consuming hours that were never buying anyone anything.

Why the whole-job approach keeps failing

When companies try to automate the entire role instead of the mechanical slice, three things tend to happen.

The judgment part gets automated badly, because AI doesn’t actually have the relationship history, the political context, or the accountability a person carries into that decision. The team notices the output feels shallow, and trust collapses — not just in that one task, but in AI generally, for everything that follows. And the real time-waster, the repetitive mechanical slice, never actually gets touched, because everyone was too busy arguing over whether AI should be allowed anywhere near the judgment call in the first place.

Meanwhile the twenty percent just sits there, quietly costing four hours a week, untouched the whole time.

How to find your own twenty percent

You don’t need a consultant in the room to spot this. Pick any task on your plate that regularly eats more time than it should, and ask one question: which parts of this would look identical no matter who did them, and which parts would look different depending on who’s in the chair?

The parts that would look identical no matter who’s doing them — the formatting, the pulling, the first draft of a paragraph everyone writes the same way — are your twenty percent. The parts that would look different depending on the person are not. Those stay exactly as they are.

Try it on one task this week. Write down the steps, start to finish. Circle the ones that only exist because of who you are — your judgment, your relationships, your accountability. Everything left uncircled is worth a second look.

What this actually buys you

The finance manager didn’t get her whole week back. She got four hours back, every week, that used to disappear into formatting and assembly. She still owns the report. She still makes the call. She just stopped paying a four-hour toll to get there.

Multiply that across a team, and the math gets interesting fast — not because AI did anything dramatic, but because somebody finally separated the boring twenty percent from the job that actually mattered.

There’s a second benefit that’s easy to miss. When a team sees AI take over the four hours nobody wanted and leave the one hour that mattered untouched, trust builds fast. Nobody has to defend the judgment call, because AI was never anywhere near it. That’s often what makes the next task worth looking at — not a bigger rollout, just one more twenty percent, proven the same simple way.

The instinct to protect judgment work from AI is the right instinct. The mistake is assuming that protecting it also means leaving the mechanical slice untouched. They are not the same thing, and treating them as one is why so many AI efforts quietly stall before they start.

Useful advice. Zero behavior change, until someone sits down with one real task and actually draws the line between the two.

Which twenty percent of your own week is mechanical enough that it shouldn’t need you — and how long has it been sitting there anyway?

If this made you think of a task worth pulling apart, I’d be glad to hear your thoughts on it.

ADDITIONAL READING

• The Real Reason Most AI Projects Stall Before They Start — https://jordanimutan.com/2026/09/11/the-real-reason-most-ai-projects-stall-before-they-start/

• You Trained Your Team on AI. Their Output Didn’t Change. — https://jordanimutan.com/2026/09/15/you-trained-your-team-on-ai-their-output-didnt-change/

• AI Was Supposed to Save Your Managers Time. It Didn’t. — https://jordanimutan.com/2026/09/03/ai-was-supposed-to-save-your-managers-time-it-didnt/

• Your AI Rollout Won’t Fix What’s Actually Slowing Your Managers Down. — https://jordanimutan.com/2026/09/16/your-ai-rollout-wont-fix-whats-actually-slowing-your-managers-down/

• Your Company Isn’t Slow — Your Decisions Are Trapped in Manual Processes — https://jordanimutan.com/2025/12/19/your-company-isnt-slow/

Some organizations aren’t ready for a leadership program. They’re ready for an inspirational afternoon, and that’s a different purchase.

There’s nothing wrong with wanting a good speaker and a motivating day. The problem is buying that experience and expecting it to behave like a program that changes how managers work. The two rarely disappoint for the same reasons, but they disappoint for entirely predictable ones.

The readiness check most companies skip

Before committing to a leadership program, a handful of honest questions will tell you more than any vendor’s proposal:

• Is there a business priority — cycle time, complaints, rework, sales follow-through — that this program is actually meant to move? Or is the goal just “better leaders,” with no number attached?
• Is there an executive sponsor willing to require participation and make the result their own, not just approve the invoice?
• Will managers actually get access to baseline data and time to apply what they learn, or is everyone already stretched thin with no room for anything new?
• Is the desired change something managers can actually control, or does it depend on decisions made two levels above them?

If most of these come back “no” or “not really,” the honest answer isn’t “don’t invest in your people.” It’s “this isn’t the right investment yet.”

What an unready organization usually looks like

A few patterns show up again and again in organizations that aren’t ready, even when the intent is genuinely good:

The desired result is vague and politically unsafe to measure — everyone agrees “we need stronger leaders,” but nobody can name the specific number that would prove it worked, because naming it would mean someone has to be accountable for it.

The only thing everyone can agree on is the inspirational event. There’s real enthusiasm for a keynote speaker and a workshop day, and real resistance the moment anyone suggests homework, follow-up, or measurement.

Nobody with real authority is willing to require participation. The program becomes optional in practice, even if it’s mandatory on paper — and optional development gets deprioritized the first time a deadline collides with it.

None of these are reasons to give up on developing your people. They’re reasons to fix the conditions first, so the investment actually has a chance to work.

What to do if you’re not ready yet

If your organization is short on one or two of these conditions, that’s fixable, usually faster than you’d expect: name the one number this initiative should move, even roughly. Find the one executive willing to own that number publicly. Agree, before you spend a peso, on how you’ll know if it worked.

That’s a shorter conversation than most companies expect — and it’s far cheaper than discovering the gap after the program has already launched.

A quick honest check before you spend the budget

Before your next leadership program is approved, ask the room: if we ran this exact program today, would anyone be able to tell us, in plain numbers, whether it actually worked?

If the honest answer is no, that’s the conversation worth having first — not a reason to cancel the idea, just a reason to fix the foundation underneath it. Message Jordan if you’d like a second opinion on whether your organization is ready for this investment, or what needs to be true first.

Further reading on jordanimutan.com:

• Why Your Leadership Training Isn’t Working (And What To Do Instead) — https://jordanimutan.com/why-your-leadership-training-is-not-working/

• How to Improve Manager Performance in 90 Days — https://jordanimutan.com/2026/08/21/how-to-improve-manager-performance-in-90-days-stop-training-for-attendance-and-start-training-for-behavior/

#LeadershipDevelopment #OrganizationalReadiness #HRLeadership #TrainingROI #ExecutiveSponsorship

I’ve trained managers across dozens of Philippine companies over the years, and one pattern shows up almost everywhere I go: the feedback that could have fixed a small problem gets saved for the annual review, by which point it isn’t small anymore.

An employee misses a deadline in February. The manager notices, feels a flicker of frustration, and decides to bring it up “when we do the formal review.” By November, that flicker has become a pattern nobody named out loud for nine months, and the employee is genuinely surprised to hear about it.

This isn’t a rare mistake. It’s the default setting in most companies, and it’s expensive.

Why Managers Save Feedback For Later

Giving feedback in the moment feels confrontational. Saving it for a scheduled review feels safer, more organized, even more fair — you’re not “picking on” someone in the middle of a busy week.

The problem is that the moment passes. The behavior repeats, quietly becomes habit, and by the time the formal review arrives, the manager isn’t addressing one missed deadline anymore. They’re addressing a pattern, and the employee has had months to believe the pattern was fine, because nobody said otherwise.

The Real Cost Of Waiting

Delayed feedback doesn’t just fail to fix the problem. It actively makes the eventual conversation harder. A single missed deadline is easy to raise and easy to hear. Nine months of unaddressed misses feels, to the employee, like an ambush.

Deloitte has estimated that large companies spend millions of hours a year on formal review cycles that, on their own, produce almost no measurable change in performance. The reviews happen. The behavior doesn’t move. The gap between the two is almost always timing.

A Simple Way To Fix The Timing

The fix isn’t a new form or a longer review. It’s a habit small enough to use in real time: Notice, Name, Now.

• Notice the specific moment — not a vague sense that “something’s off,” but one observable thing: a missed deadline, a skipped step, a report that arrived without the numbers it needed.

• Name it plainly, without saving it for later: “The report came in Tuesday without the Q3 numbers. That pushed the whole review back a day.”

• Do it now, not at the next scheduled one-on-one, and never at the annual review. The closer the feedback sits to the actual moment, the more useful it is and the less it feels like an attack.

This isn’t about becoming harsher. It’s about becoming faster. A manager who raises a small thing this week rarely needs a hard conversation in six months, because the small thing never had time to become a pattern.

What This Requires From The Manager

The uncomfortable part is that Notice, Name, Now takes more courage in the moment than saving it for later does. It’s genuinely easier to let a Tuesday slide and deal with it “eventually.” The cost of that ease just doesn’t show up until much later, wearing a different, bigger problem’s clothes.

Managers who get good at this stop dreading review season, because there’s nothing left to save up. Everything that mattered already got said, in the week it happened.

What’s one piece of feedback you’ve been holding onto since last month, waiting for a “better time” to bring it up?

If you’re trying to build this habit into how your managers operate day to day, feel free to reach out — I’m happy to compare notes.

Next reads on jordanimutan.com:

• Your Managers Keep Avoiding Difficult Conversations—And It’s Quietly Killing Performance — https://jordanimutan.com/2026/05/05/your-managers-keep-avoiding-difficult-conversations-and-its-quietly-killing-performance/

• Your Managers Keep Talking About Accountability—But No One Feels It — https://jordanimutan.com/2026/04/30/your-managers-keep-talking-about-accountability-but-no-one-feels-it/

• Clarity Is Uncomfortable. That’s Why It’s Rare. — https://jordanimutan.com/2026/02/28/clarity-is-uncomfortable-thats-why-its-rare/

• The One Person Who Decides If Your Training Actually Sticks (And It’s Not the Trainee) — https://jordanimutan.com/2026/09/18/the-one-person-who-decides-if-your-training-actually-sticks-and-its-not-the-trainee/

• Before You Book Another Workshop, Ask If Training Is Even the Right Fix — https://jordanimutan.com/2026/09/24/before-you-book-another-workshop-ask-if-training-is-even-the-right-fix/

#FeedbackCulture #PerformanceManagement #ManagerDevelopment #PhilippineBusiness #ManagementExecution

Every name on your training roster has a manager. Almost none of those programs have an owner.

There’s a difference, and it’s the one thing that predicts whether your next leadership investment survives contact with a busy quarter.

An attendee list tells you who showed up. An owner is the executive who is accountable for the business result the program was supposed to move — and who will still be asking about it in month four, after the launch excitement has worn off.

Why “who’s attending” is the wrong first question

Most program planning starts with logistics: who’s invited, what dates work, which venue, how many cohorts. All reasonable questions. None of them touch the one that actually determines whether the program does anything.

If no executive or business sponsor will own the result, application becomes optional the moment anyone gets busy — and everyone gets busy.

An owner does three things a training coordinator can’t:

• Names the one business result the program is actually meant to move, in numbers the rest of the business already tracks.
• Removes the excuses that stop managers from applying what they learned — a scheduling conflict, a competing priority, a “we’ll get to it later.”
• Sits in the room when the results come back, good or bad, and decides what happens next.

Without that person, a program is a well-attended event with no one accountable for what happens after it ends.

What good sponsorship actually looks like

A real sponsor isn’t the person who gives the opening remarks and leaves. It’s the person who:

1. Picks the business priority the program serves before a single session is designed.
2. Tells their own direct reports that this matters — not through a memo, through actually asking about it.
3. Reviews the results at the end and makes the call: scale it, fix it, or stop it.

None of this requires a large time commitment. It requires one executive who treats the program as their accountability, not HR’s.

The disqualifying question worth asking before you sign

Before committing budget to your next leadership program, ask one question inside the room: who, specifically, will still be asking about this in four months?

If the honest answer is “nobody” or “whoever’s free,” that’s worth fixing before the kickoff date, not after the results disappoint.

This is also worth asking of yourself if you’re the one buying the program. A vendor who never asks you this question is planning to deliver an event. A vendor who insists on it is planning to deliver a result.

One question for your next program

If your organization rolled out a leadership program tomorrow with no named executive sponsor, who would actually notice if it quietly failed?

If that’s a hard name to produce, that’s the real gap to close before the next investment — not the curriculum. Message Jordan if you’d like to think through who should own your next program’s result, and what that ownership should actually look like.

Further reading on jordanimutan.com:

• Turn Capability Into Consistent Execution — https://jordanimutan.com/turn-capability-into-consistent-execution/

• Half Your New Hires Won’t Last. Here’s the Real Reason Why. — https://jordanimutan.com/2026/09/02/half-your-new-hires-wont-last-heres-the-real-reason-why/

#LeadershipDevelopment #ExecutiveSponsorship #HRLeadership #TrainingROI #ManagerExecution

Not every task on your list should get an AI fix. Some of them will just break in a new, more expensive way.

The real question isn’t “can AI do this.” It’s whether the task is even the right shape for AI to help with in the first place.

Here’s the test we run before recommending any tool. Five yes-or-no questions. Is the task mostly about processing, summarizing, or drafting text or documents? Does it follow a repeatable pattern most of the time, instead of a new judgment call every time? Is the knowledge needed to do it already written down somewhere — templates, past examples, docs? Does it avoid needing real-time access to sensitive or regulated data? And would a human still review the output before it’s final?

Four or five yeses, and you’ve got a strong candidate. Two or fewer, and the task isn’t ready for AI yet — no matter how much it’s annoying someone.

We ran this test with a client last month who wanted AI handling their vendor negotiation emails. It failed the test almost immediately. Every email depended on relationship history, unwritten context, and a judgment call about how hard to push. That’s not a repeatable pattern. That’s a skill living in one person’s head, and no checklist changes that.

The same team also wanted help with their weekly ops summary — pulling numbers from three systems into one readable report. That one passed everything. Repeatable, already templated, no sensitive live data, and someone was going to review it before it went out anyway. That’s the one we started with.

This is the part most companies skip. They see a task that’s slow and annoying, and slow-and-annoying gets treated as reason enough to hand it to AI. But slow-and-annoying and judgment-heavy is not the same as slow-and-annoying and repeatable. The first one needs a person. The second one is your quick win.

Useful advice. Zero behavior change — until someone actually runs the test on the task in front of them.

Which task on your list is actually a judgment call wearing an “admin work” disguise?

If you’re not sure which of your tasks would pass, send a message. Let’s discuss how the AI Quick-Win Audit works and screens for exactly this.

Additional Reading

• Your AI Rollout Won’t Fix What’s Actually Slowing Your Managers Down.

• You Trained Your Team on AI. Their Output Didn’t Change.

• AI Was Supposed to Save Your Managers Time. It Didn’t.

• The Real Reason Most AI Projects Stall Before They Start

• Your Company Isn’t Slow — Your Decisions Are Trapped in Manual Processes

The manager who used to challenge every bad decision in the room has gone quiet. Not resigned. Not underperforming. Just quiet.

That is quiet cracking, and it is the workplace trend HR researchers are most worried about heading into 2026. Unlike quiet quitting, which is a deliberate choice to do less, quiet cracking is not a decision at all. It is a slow erosion of morale and energy that the person experiencing it may not even notice happening to them.

The dangerous part is that it does not show up on a scorecard until it already has. The work still gets done. The meetings still get attended. What disappears first is the things no dashboard measures: the pushback, the extra idea, the willingness to go first.

Why It Hides So Well

Quiet cracking hides because it looks like nothing. There is no resignation letter, no complaint, no obvious drop in output. What changes is smaller and easier to miss: a manager who used to volunteer for the hard project stops raising their hand. Someone who used to flag a problem early starts waiting to be asked.

By the time it shows up in a performance number, it has usually been building for months.

The Signs Worth Watching For

A few patterns tend to show up before the numbers do.

• A manager who used to speak first in meetings now speaks last, or not at all.

• Someone who used to flag risks early starts only mentioning them after something has already gone wrong.

• A person who used to volunteer for stretch assignments starts doing exactly what is asked, no more.

• Small decisions that used to get made on the spot now get escalated, even when they clearly do not need to be.

None of these on their own means much. Together, over a few weeks, they are worth a direct conversation.

Why The Usual Fixes Miss

Most companies respond to disengagement with wellness gestures. A mental health email. A team lunch. These are not wrong, exactly. They are just aimed at the wrong layer of the problem.

Quiet cracking is rarely caused by a lack of resilience. It is caused by a manager carrying weight nobody ever gave them the skill or the authority to put down. Wellness perks do not fix an unclear decision boundary or an unsustainable workload. Only the structure underneath does.

What Actually Helps

A short, honest check-in beats a survey every time. Ask directly: what is one thing on your plate right now that feels heavier than it should, and what would make it lighter?

Then act on the answer visibly. Quiet cracking often continues because the last time someone spoke up, nothing changed. The fastest way to reverse it is proof that speaking up still works.

Quiet cracking rarely announces itself. It just gets a little quieter, week by week, until the person who used to fight for their team stops fighting altogether.

Which of your managers has gone a little quieter lately, and when did you last ask them why?

If you want to talk through what you’re seeing, message me.

Next reads on jordanimutan.com:

• Why Micromanagement Is Almost Never a Personality Problem — https://jordanimutan.com/2026/09/18/why-micromanagement-is-almost-never-a-personality-problem/

• Managing Yourself Before You Can Manage Anyone Else — https://jordanimutan.com/2026/08/25/managing-yourself-before-you-can-manage-anyone-else/

• Your Managers Keep Avoiding Difficult Conversations—And It’s Quietly Killing Performance — https://jordanimutan.com/2026/05/05/your-managers-keep-avoiding-difficult-conversations-and-its-quietly-killing-performance/

• Every Company Tracks Time-to-Hire. Almost None Tracks Time-to-Productive. — https://jordanimutan.com/2026/09/09/every-company-tracks-time-to-hire-almost-none-tracks-time-to-productive/

• Half Your New Hires Won’t Last. Here’s the Real Reason Why. — https://jordanimutan.com/2026/09/02/half-your-new-hires-wont-last-heres-the-real-reason-why/

#QuietCracking #EmployeeEngagement #ManagerBurnout #PhilippineBusiness #ManagementExecution