Category: Leadership

Would I Automate Meeting Minutes? Yes, After Fixing the Meeting

~ jordan ~ Leave a comment

Your meeting ended an hour ago, and nobody can say for sure what was decided.

Someone is writing the minutes. They are scrolling through notes taken in a hurry, trying to remember whether the budget was approved or only discussed. Two attendees have already sent messages asking who owns the follow-up. Nobody is sure, so nobody moves.

This is the moment many teams reach for AI. Let a tool listen, summarize, and send the minutes. It is a good idea. It also skips a more important question: did the meeting produce anything worth summarizing?

Where the time goes after the meeting

Take one weekly management meeting with eight people. These numbers are illustrative, so replace them with your own.

• Note-taker turns rough notes into clean minutes: 60 minutes

• Sending them out and fixing corrections: 20 minutes

• Eight attendees reading long minutes: 8 × 5 = 40 minutes

• Follow-up messages asking who owns what: 30 minutes

That is 150 minutes, or two and a half hours, every week. Over 50 weeks it adds up to 125 hours spent on the paperwork of one meeting.

Look at the last line. Thirty minutes of messages asking what was decided is not a writing problem. It is a sign the meeting ended without a clear answer.

The cost is also uneven. The note-taker is often a junior person or an assistant, and that hour lands on them every week. They carry a quiet tax for a problem they did not create and have little power to fix.

Would I automate this?

Meeting minutes are a good test case, because some parts of the job suit AI and some do not.

I would hand AI the mechanical parts: turning rough notes or a recording into a clean first draft, pulling out action items with names and dates, and sending a reminder two days before a deadline. These tasks repeat every week, and checking a draft is faster than writing one.

I would keep three things with a person: deciding what was actually decided, confirming who owns each action, and noting what was left open on purpose. These are judgments. A tool cannot tell the difference between “we agreed” and “we stopped arguing because it was five o’clock.”

That split is useful, and it also exposes the real problem. If a person has to decide what was decided, they should do it while everyone is still in the room.

What good minutes look like

Most minutes record the discussion. Readers need the outcome. A useful set of minutes fits on half a page and has three parts: decisions made, actions with an owner and a date, and questions still open.

The discussion itself rarely needs a record. If someone wants the reasoning behind a decision, one line is usually enough. Five paragraphs of who said what mostly give people something to disagree about later.

Shorter minutes also get read. Long ones get filed, which is a polite word for ignored.

Here is a simple test. Hand the minutes to someone who missed the meeting. If they can tell what was decided and what they must do next, the minutes work. If they need a phone call to understand them, they do not.

Fix the meeting before you fix the minutes

Here is a habit that costs five minutes and removes most of the confusion. In the last five minutes of the meeting, the chair reads back three things for each decision: what was decided, who owns it, and by when.

Say it out loud, then ask if anyone disagrees. If a decision cannot be stated in one sentence, the meeting did not make one, and it is better to find that out now than in next week’s meeting.

This is the part most teams miss. Good minutes are not written after the meeting. They are spoken at the end of it, and then written down.

When the read-back happens, an AI draft has something solid to work from. When it does not, the tool will produce a smooth, confident summary of a conversation that never reached a conclusion. That is worse than messy notes, because it looks finished.

Why the read-back feels awkward at first

People resist it. It feels like extra ceremony, and it can expose that the group never agreed on anything. That is exactly why it works.

Start by making it routine, not dramatic. Same five minutes, same three questions, every meeting. After three or four weeks, attendees expect it, and they speak more clearly during the meeting because they know a read-back is coming.

The chair carries this habit. If the chair skips it when the meeting runs late, the team learns it is optional. Protect the five minutes the way you protect the start time.

What the numbers look like after

Run the same meeting with the read-back and an AI-assisted draft.

• Read-back at the end: 5 minutes × 8 people = 40 minutes

• AI drafts the minutes from notes or a recording, and the note-taker checks it: 20 minutes

• Eight attendees reading a half-page summary: 8 × 2 = 16 minutes

• Follow-up messages: 10 minutes

The total is 86 minutes, down from 150. That is about an hour saved each week, and roughly 50 hours over a year.

Notice that the read-back adds time, and I counted it. A fair comparison includes every new step. The hours saved are modest. The larger gain is fewer lost decisions, and fewer weeks that start with “Wait, did we agree to that?”

Always check the draft

Even with a good read-back, read the draft before it goes out. Tools mishear names, mix up two people with similar names, and sometimes turn “let’s consider it” into “approved.”

Have someone who was in the meeting check every action item against their own memory. It takes a few minutes, and it prevents the kind of mistake that surfaces three weeks later in front of the boss.

Be careful what the tool hears

Some meetings should not be recorded or fed to a tool. Discussions about pay, hiring, discipline, or legal matters often carry confidentiality rules. Check your company policy, and tell attendees whenever a meeting is being recorded.

A simple rule works well. Use AI for ordinary operating meetings first. Keep sensitive conversations in the hands of a person until your policy says otherwise.

Try it for two weeks

1. Pick one recurring meeting that already has minutes.

2. Time the work around it: writing, sending, reading, and follow-up messages.

3. In week one, add the three-line read-back to the last five minutes.

4. In week two, let AI draft the minutes from your notes, and have the note-taker check every action item.

Keep the test fair. Use the same meeting, the same people, and roughly the same agenda in both weeks, so the difference you see comes from the change and not from a lighter week.

Compare the two weeks, and count the follow-up messages too. They tell you whether the meeting really ended.

If the read-back shows that your meetings often end without decisions, you have found a bigger saving than any tool can offer. Some meetings do not need better minutes. They need to be shorter, or to not happen at all.

A meeting that cannot name its decisions cannot be summarized well by anyone, human or machine.

In your last meeting, could every person in the room have stated the decision, the owner, and the date?

If you want to talk through how this could work in your team, I’d be glad to hear your thoughts.

ADDITIONAL READING

• Not Every Task Should Use AI. Here’s the Test We Use to Tell. — https://jordanimutan.com/2026/09/25/not-every-task-should-use-ai-heres-the-test-we-use-to-tell/

• The 20% of Any Job That’s Actually Worth Giving to AI — https://jordanimutan.com/2026/10/06/the-20-of-any-job-thats-actually-worth-giving-to-ai/

• Before You Automate That Weekly Report, Ask Who Reads It — https://jordanimutan.com/2026/10/13/before-you-automate-that-weekly-report-ask-who-reads-it/

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

• 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/

Escalation at Work: When Managers Should Raise a Problem, and How to Do It

~ jordan ~ Leave a comment

A supplier is late. A key customer is unhappy. A report has a mistake in it. Someone on the team knows, and a few days go by before the boss hears about it. By then, a small problem has become a costly one. This is one of the most common patterns I see in the managers I work with after more than 30 years of managing people, and it is rarely about honesty. It is about not knowing when raising a problem is the right move.

Why problems travel up so slowly

Most people do not hide problems to cause harm. They wait. They hope to fix it first. They don’t want to bother a busy boss. Or they are not sure whether it is serious enough to mention. Fear plays a part too. A 2026 survey of 2,000 UK workers by Mental Health First Aid England, as reported by Arinite, found that 45% did not feel safe raising mistakes or highlighting risks, and 15% said they had made preventable mistakes because they felt unsafe speaking up. It is a UK study, but the pattern is human, and managers in Philippine companies will recognize it.

The result is the same everywhere: the person closest to the problem knows first, and the person with the authority to fix it knows last.

Escalation is not a failure

Many managers treat escalating as admitting they cannot cope. So they carry the problem alone for too long. Good escalation is the opposite. It means sending a problem to the person who can act on it, early enough that acting still helps. Silent delay is the real failure.

Three triggers: when to raise it

Give your team a simple rule. Raise it the same day if any of these is true.

It will miss a deadline, a budget, or a promise to a customer.

Solving it needs authority or money that you do not have.

It touches another team or a customer who may be affected.

If none of the three is true, handle it and mention it in your next regular update. If any is true, do not wait to be sure. Being early and slightly wrong costs far less than being late and right.

How to raise it: What. So what. Need.

A good escalation fits in three short lines.

What happened. One or two facts, no story.

So what. What it will affect if nothing changes, and by when.

Need. What you want from the person you are telling: a decision, a resource, or simply to be aware.

The third line matters most. Without it, the boss does not know whether to act or just listen, and may react to the wrong thing.

What owners and senior managers must do

The rules above only work if the first reaction to bad news is calm. If the person who raises a problem is questioned harshly, blamed, or sighed at, they will wait longer next time. Thank them first. Ask your questions second. People learn how safe it is to speak up from how the last person was treated.

Think about the last problem that reached you later than it should have. What did that person expect would happen when they told you?

If you would like to talk through how to set escalation rules in your own team, send me a message. I’m happy to compare notes, no pitch attached.

Next reads from the blog:

• You Think People Aren’t Taking Ownership. They Think It’s Not Safe To. — https://jordanimutan.com/2026/03/21/you-think-people-arent-taking-ownership-they-think-its-not-safe-to/

• 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/

• The Feedback That Arrives Six Months Too Late — https://jordanimutan.com/2026/09/30/the-feedback-that-arrives-six-months-too-late/

• How to Set Team Priorities: Why “Everything Is Urgent” Slows Managers Down — https://jordanimutan.com/2026/10/12/how-to-set-team-priorities-why-everything-is-urgent-slows-managers-down/

• How to Help Newly Promoted Managers Perform Faster in Their First 90 Days — https://jordanimutan.com/2026/10/22/how-to-help-newly-promoted-managers-perform-faster-in-their-first-90-days/

#ManagementSkills #Leadership #Accountability #PhilippineSMEs #TeamCommunication

How to Help Newly Promoted Managers Perform Faster in Their First 90 Days

~ jordan ~ Leave a comment

Most companies promote their best performer and then wait to see what happens.

The skills that earned the promotion are rarely the skills the new job needs. A great salesperson, nurse, engineer or teller was rewarded for doing the work. A manager is judged on how well the team does it.

What changes on day one

A new manager has to do things they have never done before:

  • Hand over tasks they used to do themselves.
  • Run regular one-on-ones. A one-on-one is a private meeting between a manager and one team member.
  • Set clear expectations.
  • Give feedback, including hard feedback.
  • Hold people accountable without taking the work back.

These are new habits. A new manager cannot learn them by guessing, and a two-day course before the promotion will not make them stick.

What a slow start costs

The team is unsure what is expected. Decisions wait. Good people start looking elsewhere. The time it takes a new manager to perform well in the role, often called time to productivity, stretches from weeks to months. Most companies never measure that cost.

A 90-day plan HR can set up

Days 1 to 30: Listen and learn. Meet each team member one-on-one. Ask what work they own, where it gets stuck and what the last manager did well. Learn the one business result the manager’s own boss cares about most.

Days 31 to 60: Build habits. Start a weekly one-on-one with each team member. Write down expectations for each role on one page. Hold one feedback conversation, and practice it first with the boss or a peer.

Days 61 to 90: Own one improvement. Pick one problem in the team’s work, fix it, and show the boss the before-and-after number.

Three supports that make the plan work

  • A boss who checks. A 20-minute check-in at the same time each week. The question is simple: what did you do this week on the plan?
  • Short sessions, not one long course. Two hours every two to three weeks works better than two days upfront. New managers have little free time, and each lesson lands best when they have just met the problem it solves.
  • A peer to learn from. Pair the new manager with an experienced manager they can ask questions without feeling judged.

How to know it is working

At day 90, ask three questions. Are weekly one-on-ones happening? Are expectations written down? Did the team deliver one improvement? If the answer to all three is yes, the manager has a good start.

At POC Management Execution, we treat new-manager effectiveness as a business priority: one group of new managers, a few clear practices, a boss who reinforces them, and one number tracked.

A new manager’s first 90 days should be planned, not left to chance.

What happens in your company in the first 90 days after someone is promoted to manager?

If you would like to think through a plan for your own company, message me and we can brainstorm it together.

Further reading on jordanimutan.com:

• How to Choose One Business Priority Before You Start a Manager Development Program: https://jordanimutan.com/2026/10/16/how-to-choose-one-business-priority-before-you-start-a-manager-development-program/

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

#NewManagers #LeadershipDevelopment #ManagerOnboarding #HRStrategy #PeopleManagement

How to Keep the Results of a Leadership Program After the Program Ends

~ jordan ~ Leave a comment

A leadership program ends on a high. Six months later, many managers are back to their old habits.

That does not mean the program was weak. It is what happens when a program has an end date and the work does not.

Why the results fade

While a program runs, someone is watching. Sessions are on the calendar, a facilitator asks questions, and a report is due. When the program ends, all three disappear on the same day. Three other things usually go with them:

  • Nobody owns it. The trainer leaves, and no one inside the company takes over.
  • Supervisors stop asking. Asking “how is the new practice going?” was never part of their routine, so it stops.
  • Nobody checks the number. The business result the program was meant to move is no longer reviewed.

What the evidence says

Training Industry reported on a review of 335 samples of leadership training. Results were stronger when programs included practice, feedback and sessions spaced out over time. In plain words, programs work better when they continue past the workshop.

Four things to set up before the program ends

  1. Name an owner inside the company. One person, not a department. This person keeps the practice going and reports the result to an executive.
  2. Add one weekly question to a meeting that already happens. A one-on-one is a regular private meeting between a manager and one team member. In that meeting, the supervisor asks: “What did you do this week using the new practice?” It takes two minutes.
  3. Schedule short follow-up sessions. A one-hour session at about three months, and again at six months, lets managers share what worked and fix what did not.
  4. Keep checking the same number. If you wrote down a starting number (a baseline) before the program began, look at it every month for at least six months after the program ends.

What this looks like in practice

Here is an illustration. A program taught branch managers to call every complaining customer back within 24 hours. The head of customer service is the owner. Supervisors ask each manager about it in their Monday one-on-one. Each month, someone reports the complaint rate to the executive team.

That program stays alive without the trainer in the room.

Why this matters for your budget

If results fade, you pay for the same training again next year. If the company can keep them, one program does the job.

At POC Management Execution, we aim to leave behind stronger managers, clear routines and an owner inside your company, so you do not depend on an outside consultant.

A leadership program is finished when the company can keep the results without the trainer.

Who inside your company owns the results of your last leadership program today?

If the answer is unclear, message me and we can brainstorm how to fix that.

Further reading on jordanimutan.com:

• Why Managers at Different Branches Apply the Same Training Differently: https://jordanimutan.com/2026/10/14/why-managers-at-different-branches-apply-the-same-training-differently/

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

#LeadershipDevelopment #TrainingEffectiveness #LearningAndDevelopment #HRLeadership #ManagerEffectiveness

Strategy Execution for SMEs: How to Turn Your 2027 Plan Into Weekly Management Action

~ jordan ~ Leave a comment

I’m Jordan Imutan. I help managers and business owners in Philippine companies close the gap between what the company decided and what the team actually does. It is October, which means many owners and executives are drafting plans for 2027. This is a good moment to talk about what happens after the plan is written.

A plan is a document. Results come from what managers do each week. In between, there is a gap that most companies never look at directly.

The gap is usually about names

ClearPoint, a strategy software company, looked at more than 20,000 strategic plans from 2017 to 2024. In its data, 74% of goals had no named owner, and 57% of projects had no clear ownership. This is one vendor’s own dataset, so treat the exact figures with care. But the pattern matches what many managers will recognize: a goal everyone agrees with and nobody is responsible for.

When a goal belongs to “the team” or “operations” or “everyone,” it belongs to no one. Nobody wakes up on Monday with that goal on their mind.

Where plans quietly lose their way

Plans do not usually fail with a big announcement. They fade. The kickoff meeting goes well. The slides are shared. Then the daily work takes over, and the plan sits in a folder. By the time anyone checks, a quarter has passed.

Three things usually go missing. The plan is not turned into specific weekly actions. The goal has a team but no single owner. And no one has a regular, short moment to ask: are we on track?

A simple method: Goal. Owner. First move. Weekly check.

Take each goal in your 2027 plan and write four lines under it.

Goal. One sentence, with a result you could see or count. “Improve customer service” is a wish. “Answer every customer message within one working day” is a goal.

Owner. One name. Not a department. The person who would be asked about it if the goal slipped.

First move. The very first action, small enough to start next week. Who does what, by when.

Weekly check. A fixed ten-minute moment, same day each week, where the owner says: on track, at risk, or stuck. Nothing more.

Why the weekly check matters most

Of the four, this is the one managers drop first, because it feels like extra meetings. But a weekly check is what turns a yearly plan into a habit. It catches a problem in week three instead of month three. It also shows your managers that the plan is real, because someone is asking about it.

What this is not

It does not mean tracking every small task or building a heavy dashboard. If your plan has twelve goals, it is likely too many to run well. Many small companies do better with a handful of goals, each with a clear owner, than a long list that no one can hold in mind.

Before you finalize your 2027 plan, look at the list once more. Which goal has no name beside it?

If you’d like to think through how to assign owners and set a weekly rhythm in your company, message me. I’m happy to compare notes, no pitch attached.

Next reads from the blog:

• Why Your Leadership Program Needs an Owner, Not Just an Attendee List — https://jordanimutan.com/2026/09/29/why-your-leadership-program-needs-an-owner-not-just-an-attendee-list/

• You Delegated the Task. You Kept the Authority. That’s Why It Keeps Coming Back. — https://jordanimutan.com/2026/10/09/you-delegated-the-task-you-kept-the-authority-thats-why-it-keeps-coming-back/

• From Solo Founder to CEO — https://jordanimutan.com/2026/03/21/from-solo-founder-to-ceo/

• The Feedback That Arrives Six Months Too Late — https://jordanimutan.com/2026/09/30/the-feedback-that-arrives-six-months-too-late/

• How to Tell If Your Organization Is Actually Ready for a Leadership Program (Before You Spend the Budget) — https://jordanimutan.com/2026/10/01/how-to-tell-if-your-organization-is-actually-ready-for-a-leadership-program-before-you-spend-the-budget/

#StrategyExecution #BusinessPlanning #Leadership #PhilippineSMEs #ManagementSkills

How to Choose One Business Priority Before You Start a Manager Development Program

~ jordan ~ 1 Comment

“Better leaders” is not a business goal.

It is a common one, though. Many manager development programs start with a list of skills: communication, coaching, delegation, time management. Nobody names the business problem the skills are supposed to solve.

What goes wrong when the goal is vague

Without a clear goal, three things happen. Managers get more content than they can use. Their bosses do not know what to look for, so they ask about nothing. And when the program ends, nobody can say whether it worked.

A completion report will say that 40 managers finished. It will not say whether customers complained less or projects finished sooner.

Start with one business priority

A business priority is the one result your company most needs to improve right now. It should be something leaders already track, such as complaint rates, rework, delivery times or sales follow-up.

Then work backward. Which two or three manager practices could realistically move that number? (A manager practice is a specific action a manager takes at work.)

Here is an example. Say customer complaints are rising across your branches. Three manager practices might help:

  • Call every complaining customer back within 24 hours.
  • Review open complaint cases with the team once a week.
  • Escalate unresolved cases the same day.

That is a program managers can understand in one minute. Their bosses can check it every week. And you can see whether complaints go down.

Five steps to set it up

  1. Choose one business problem that leaders already track.
  2. Write down today’s number before any training starts. This is your baseline, meaning your starting measurement.
  3. Choose two or three manager practices that managers control themselves.
  4. Ask each manager’s boss to check on those practices every week.
  5. Look at the number again after 90 days. Say plainly what else may have affected it, such as a new system or a busy season.

Check that managers control the result

Before you commit, ask one question. Can managers actually change this number with their own actions? If the result depends on decisions made two levels above them, a manager program will not move it. Pick a different priority, or fix the decision first.

Start small, then decide

At POC Management Execution, we usually begin with a 90-day pilot. A pilot is a small trial with one group of managers, run before the program goes company-wide. It gives you real evidence before you spend on a bigger rollout.

A management program should start with a business problem and end with a measured result.

What is the one business result your next management program must improve, and what is the number today?

If you are not sure, message me and we can brainstorm it together.

Further reading on jordanimutan.com:

• How to Tell If Your Leadership Pilot Program’s Results Are Actually Valid: https://jordanimutan.com/2026/10/07/how-to-tell-if-your-leadership-pilot-programs-results-are-actually-valid/

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

#LeadershipDevelopment #ManagerDevelopment #LearningAndDevelopment #HRStrategy #BusinessPerformance

Why Comparing Three Supplier Quotes Takes Two Days, and How to Fix It

~ jordan ~ Leave a comment

Three suppliers quoted the same job. It took two days to learn which one was cheapest.

Nobody did anything wrong. The quotes simply arrived in three different shapes. One was a PDF with unit prices. One was an email with prices in the body and freight mentioned at the bottom. One was a spreadsheet with bundled items and a different unit of measure.

So a staff member opened a blank sheet and started retyping. Then the questions started. Does the second quote include installation? Is the third price before or after tax? When can the first supplier actually deliver?

Repeat that for every purchase your team handles, and you begin to see where purchasing time really goes.

Where the two days go

Here is a rough picture of one purchase. The numbers are illustrative, so use your own.

• Retyping three quotes into one comparison sheet: 1 hour

• Emails and messages to chase missing details: 1.5 hours

• Checking what each quote includes and excludes: 45 minutes

• Manager review and follow-up questions: 45 minutes

That is about 4 hours of hands-on work per purchase. If your team handles eight purchases like this a month, that is 32 hours, or four full working days, every month.

Waiting is its own cost. While the quotes sit unresolved, the purchase sits too. The branch waits for equipment, the project waits for materials, and an early-payment discount quietly expires. The four hours are visible. The two days are what the business feels.

Notice what is missing from the list. Nobody spent time on the real decision, which is which supplier to trust. Translation took the day.

The slow part is not the math. It is turning three different documents into one comparable shape.

Fix the request, not the reply

Most of the chasing happens because the original request was vague. “Please quote 20 units, delivery by the 30th” leaves every supplier to guess what you care about. Each one answers in its own style and leaves out something different.

The fix is a one-page quote request with the same fields every time: unit price, quantity, freight, installation, payment terms, delivery date, warranty, and how long the price is valid. Suppliers already know these answers. Filling in a form costs them very little.

Suppliers usually welcome this. A clear request means fewer calls back to you, a faster reply from them, and a better chance their quote is read correctly. Clarity helps both sides.

That change alone cuts the chasing. In our example, the 1.5 hours of follow-up drops to about 30 minutes, because most of the questions are already answered.

Some suppliers will ignore your form and send their usual document anyway. That is fine. You still have a standard list of what to look for in it. If a large supplier will not fill in a form, put the same eight questions in your email and ask them to reply under each one.

Where AI earns its place

Now you have a clear list of eight fields, which makes AI far more useful. Give it each quote, ask it to pull the same eight fields into one table, and have it flag anything missing or different, such as “Supplier B excludes installation.”

A person then checks the table against the original quotes. In the example, retyping falls from one hour to about 15 minutes of checking. Reviewing inclusions drops from 45 minutes to 20, because the differences are already marked. The manager’s review drops from 45 minutes to 20, because one clean table replaces three documents.

The new total is about 85 minutes per purchase, down from four hours. Across eight purchases, that is roughly 21 hours a month back, or about 250 hours a year.

The form saves about an hour of that on its own. AI handles the rest, and it works better because the questions are the same every time. A tool fed consistent input makes fewer mistakes than a tool fed a pile of surprises.

Before and after, side by side

• Before: a loose request, three formats, retyping, chasing, and about 4 hours of hands-on time per purchase.

• After: a standard request, one table, flagged differences, and a person checking the result, in about 85 minutes.

• Same decision, made by the same person, a few hours earlier.

Track one more number: the days from request to decision. Hours of work are easy to see, but days of waiting are what delay the project. A shorter chase and a ready table could bring a two-day comparison down to the same afternoon. That is an estimate, so measure it before you promise it to anyone.

And if you never use AI at all, the form still pays for itself. A standard request removes most of the chasing on its own. The tool is a bonus, not the foundation.

What stays with your team

AI can line up three quotes. It cannot know that the cheapest supplier delivered two weeks late last time, or that the second one picks up the phone when something breaks. That memory belongs to your people.

This is the right split. Let the tool handle the reading and sorting. Keep the judgment about trust, risk, and relationships with the person who owns the outcome.

Be clear about who signs off, too. When the table is wrong, the person who approved the purchase still owns the mistake. That is why the human check stays in the process, even when it starts to feel like a formality.

The same problem shows up in many places

Quotes are one example. Vendor invoices arrive in different layouts. Job applications arrive as different file types. Client onboarding forms come back with missing answers. Expense reports, insurance claims, and customer requests follow the same pattern: information arrives in different shapes, and a person spends the day translating it.

AI is a fast translator. A good form is a better one, because it makes the translation unnecessary.

Before you ask a tool to clean up the mess, ask whether you can stop the mess from arriving.

This is also why so many AI trials disappoint. The tool is asked to read whatever shows up, in whatever condition, and then gets blamed for the result. Put a little order at the front door and the same tool looks much smarter.

Try it on one purchase this month

1. Take your last purchase that needed three quotes. List every detail you had to chase or retype.

2. Turn that list into a one-page request with fixed fields.

3. Send it with your next purchase, and time each step before and after.

4. Add AI only for what is still manual, such as reading unusual documents and flagging differences.

Keep the timing simple. A notebook is enough. After two or three purchases you will have your own numbers, and they will be more convincing than any estimate in an article.

If the numbers show little time lost, good. You have confirmed that this process is fine and your attention can go somewhere else. Not every process needs fixing, and knowing which ones do is half the value.

A slow comparison is rarely a math problem. It is a format problem, and a format problem is cheaper to fix than a software problem.

What recurring task in your company still depends on turning information from one shape into another?

If you have a process like that and want to talk it through, I’d be glad to hear your thoughts.

ADDITIONAL READING

• Why Your Next AI Win Doesn’t Need a Developer — https://jordanimutan.com/2026/10/08/why-your-next-ai-win-doesnt-need-a-developer/

• 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/

• 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/

• Not Every Task Should Use AI. Here’s the Test We Use to Tell. — https://jordanimutan.com/2026/09/25/not-every-task-should-use-ai-heres-the-test-we-use-to-tell/

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

Why Managers at Different Branches Apply the Same Training Differently

~ jordan ~ 1 Comment

Two branches sent their managers to the same training. Three months later, one branch still follows the new process. The other stopped in week three.

If your company runs several branches, stores, plants or shifts, you have probably seen this. The content was the same. The results were not.

The training is the same. The conditions are not.

Most companies respond by looking at the program. Was the content good enough? Was the facilitator strong enough? Usually, the program is fine. The difference is what happens at each site after the session ends.

Four things change from one site to the next:

  • What the manager’s own boss asks about after the training.
  • How full the weekly schedule is.
  • How daily work is set up: the forms, tools and approvals managers deal with.
  • Whether anyone checks that the new practice is happening.

A new practice survives only where those four things support it. Where they do not, the old habit wins, because the old habit is faster on a busy day.

What uneven results cost you

Customers get different service depending on which branch they walk into. Leaders cannot tell which parts of the program work, so they approve another program. And the money keeps going out.

Training is no longer rare. The World Bank’s 2023 Enterprise Survey found that 62.1% of surveyed Philippine firms with 100 or more employees offered formal training. Having a program is not your edge anymore. Getting every site to use it is.

Compare your best site with your weakest site

Do not review the whole program. Pick two sites that took the same training but got different results. Then do this:

  1. Ask a manager at each site to show you one real example, from last week, of using the new practice. (A manager practice is a specific action a manager takes at work, such as a 15-minute check-in with each team member every week.)
  2. Ask each manager’s boss what they asked about after the training.
  3. Ask what gets in the way: schedule, tools, approvals or staffing.
  4. Put the answers side by side.

The gap usually shows up within an hour. Say the strong branch’s supervisor reviews the practice every Monday, and the weak branch’s supervisor never mentions it. Another workshop will not fix that. A short briefing for that supervisor, and a weekly question, will.

How this fits a wider plan

At POC Management Execution, we start with one business result the company wants to improve. We choose a few manager practices that can move it. We ask each manager’s supervisor to check on those practices. Then we compare sites to see where the practice holds and where it does not.

Consistent results come from consistent conditions, not only consistent content.

Which of your branches or sites applies your last management program best, and do you know why?

If you want to think this through for your own company, message me and we can brainstorm it together.

Further reading on jordanimutan.com:

• What It Actually Takes to Scale a Successful Leadership Pilot Program Company-Wide: https://jordanimutan.com/2026/10/08/what-it-actually-takes-to-scale-a-successful-leadership-pilot-program-company-wide/

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

#LeadershipDevelopment #ManagerEffectiveness #BranchManagement #HRLeadership #WorkplaceExecution

Before You Automate That Weekly Report, Ask Who Reads It

~ jordan ~ Leave a comment

Your weekly report costs almost seven hours a week, and nobody has asked whether anyone reads it.

You know the one. Five department heads each write a status update every Friday. A coordinator collects the five updates, merges them into one document, fixes the formatting, and sends it to the leadership team. Then someone spots a wrong number, two managers fix their sections, and the whole thing goes out again.

Nobody designed this process. It grew. A leader asked for an update once, the update became a habit, and the habit became a rule. Today it runs on its own, like a meeting that outlived its purpose.

What one report really costs

Let’s put numbers on it. These figures are illustrative, so replace them with your own.

• Five managers, 45 minutes each: 3.75 hours

• One coordinator merging and formatting: 2 hours

• Corrections and resends: 1 hour

Total: 6.75 hours every week. Over 50 weeks, that is more than 330 hours, or about eight full working weeks spent on one document.

Most companies have several reports like this. Each one looks small on its own. Together they take a real share of the week, and nobody sees it because no one has ever added it up.

There is also a cost the arithmetic misses. Managers who write a report nobody reads learn that reporting is theater. They start writing what looks safe. The report gets longer and says less.

This is not a complaint about managers. They write the update because someone asked for it, and they do it carefully, which is exactly why it takes 45 minutes.

The question to ask before you buy anything

When people see seven hours of work, the first idea is usually a tool. Let AI collect the updates, merge them, and format the document. That would help.

It would also give you a faster version of a report that may not need to exist.

Ask this first: what decision did anyone make last month because of this report?

If leaders can name one, the report has earned its place. If the answers come slowly and vaguely, you have found work that can go away. A report nobody acts on is not communication. It is a weekly ritual with a deadline.

Three steps, in this order

1. Remove. Ask who reads the report and what they do with it. If the honest answer is “no one,” stop sending it. Tell people you are pausing it for a month, then watch who complains. In many companies, nobody does.

2. Simplify. If the report survives, ask what the reader actually needs. Often it is three numbers and two risks, not five pages. Shrink the template to match. Five managers who write five lines each need ten minutes, not forty-five.

3. Automate. Only now hand the leftover mechanical work to AI: collecting the updates, putting them in one format, and drafting a short summary for a person to check before it goes out.

What a short report looks like

A useful weekly update can fit on half a page. Three headings are usually enough: what changed this week, what is at risk, and what needs a decision from the reader. Everything else is detail that belongs in a folder, not in a leader’s inbox.

Ask managers to write to those three headings and the report shortens itself, because most weeks only a few items need real attention. A quiet week produces a short report, and that is a feature. A leader who receives two lines saying nothing has changed has learned something worth knowing.

What the numbers look like after

Run the same example again. Managers now spend 10 minutes each, about 50 minutes in total. The coordinator reviews an AI-assembled draft in 30 minutes instead of building the document from scratch in two hours. Corrections drop to 15 minutes because the simpler template leaves less room for mistakes.

That is about one and a half hours a week instead of almost seven. Over a year, roughly 250 hours come back.

Look at where the savings came from. More than half of the time saved comes from the simpler template, which arrived before any AI touched the report.

A drafted summary still needs a human eye. AI can merge five updates in seconds, but it cannot tell that one manager’s “on track” has quietly meant “late” for three weeks. Keep a person on the final read. In this example that check takes 15 minutes, and it is time well spent.

Why teams skip the first two steps

Buying is exciting and removing is uncomfortable. A new tool gets a launch email and a training session. Stopping a report gets you a few awkward questions.

There is a quieter reason too. Some reports exist because a former leader asked for one, and that leader moved on years ago. The report stayed behind, like a houseplant nobody remembers buying but everybody keeps watering.

Automating that report does not solve the problem. It just makes the watering faster.

When someone defends the report

Expect the objection: “Leadership might need it someday.” Fair enough. So test it instead of arguing about it.

Pause the report for four weeks. Tell the leadership team it is available on request, and keep the template ready. Then count how many requests arrive. If the count is zero, you have your answer. If the count is two, you have learned which two readers matter, and you can send the report to them alone.

Either result is cheaper than another year of Friday afternoons.

The same test works on other recurring work

Weekly reports are only the start. Run the same questions on meeting minutes nobody opens, monthly dashboards that get a quick glance, status decks rebuilt from scratch every cycle, and spreadsheets that one employee updates by hand because the system never quite fit.

Each one has a cost in hours, a reader who may or may not exist, and a smaller version waiting to be found. Most of the time, the smallest useful version takes a fraction of the effort.

AI earns its place at the end of that process, not the beginning. By then you know what the work is for, what a good version looks like, and how to tell when a draft is wrong. A tool is far more useful to someone who knows what they want from it.

Try it on one report this week

Pick one recurring report in your department. Write down how many people touch it, how many minutes each person spends, and how often it goes out. Then multiply.

Answer three questions. Who reads it? What did they decide because of it? What is the smallest version that would still support that decision?

You do not need a consultant for this. You need a calculator and a willingness to hear the answer. Seven hours written on a page is hard to argue with, which is usually the point.

If the report passes the test, keep it and simplify it. If it fails, you have just found seven free hours a week without buying anything.

Delete what nobody uses, simplify what remains, and automate only what is left. Most teams do it in the opposite order.

Which recurring report in your company takes far longer than it should, and who would actually notice if it stopped?

If you want to compare notes on a report like that, I’d be glad to hear your thoughts.

ADDITIONAL READING

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

• 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/

• Not Every Task Should Use AI. Here’s the Test We Use to Tell. — https://jordanimutan.com/2026/09/25/not-every-task-should-use-ai-heres-the-test-we-use-to-tell/

• The 20% of Any Job That’s Actually Worth Giving to AI — https://jordanimutan.com/2026/10/06/the-20-of-any-job-thats-actually-worth-giving-to-ai/

• 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/

How to Set Team Priorities: Why “Everything Is Urgent” Slows Managers Down

~ jordan ~ Leave a comment

I’m Jordan, I help managers in Philippine companies turn what they know into what they do on a normal Monday. After managing people for more than 30 years, one problem keeps showing up in nearly every team I look at: nobody on the team can say, in one sentence, what comes first.

The manager says everything is important. The team hears that and does something sensible. They pick for themselves. Some pick the loudest request. Some pick the easiest task. Some pick whatever their manager asked about last. Nobody is being lazy. They are guessing, because guessing is the only option left.

What the numbers say

A workplace survey by Slingshot found that 62% of workers who carry too many projects lose at least one to two productive hours every day. Asked what would help most, 42% said clear priorities. Gallup has reported for years that only about half of employees strongly agree they know what is expected of them at work. These are not new problems. They are old ones that many managers still treat as a personality issue in their team, when it is usually a clarity issue in the manager’s own instructions.

Why managers avoid choosing

Choosing a top priority means saying no to something. Most managers do not like to say no to a customer, a boss, or a favorite project. So they say yes to everything and let the team sort it out. That feels kind. It is not. It moves the hardest decision from the person who has the authority to the person who has the least.

Another reason is plain fear. If I name one top priority and I’m wrong, that is on me. If I leave it vague, nobody can say I chose badly. Vague protects the manager. It costs the team.

A simple fix: One. Not now. Monday.

You do not need a new tool. You need three small habits.

One. Name the one thing that comes first this week. Not three things. One. If your team had only one hour, what would you want them to spend it on? Say that out loud.

Not now. Write a short list of things that are real but can wait. This is the part most managers skip. The list gives your team permission to stop worrying about those items. Without it, everything stays half-done and heavy.

Monday. Spend five minutes at the start of the week checking that what you said is what your team heard. Ask each person: what is your top priority this week? If their answer is not yours, the problem is not them. Your message did not land. Fix it now, not on Friday.

What this looks like in practice

Picture a team leader whose staff are handling a customer complaint, a month-end report, and a new hire’s training, all marked urgent. If the leader names the complaint as the one thing, puts the training on the not-now list until Wednesday, and tells the team the report can be sent a day late, three people know exactly where to start. Nothing was added. Something was only made clear.

What this is not

It is not a rule that only one thing ever gets done. Work is messy. Emergencies happen. The point is that when everything is urgent, your team is left to rank the work alone. A clear top priority and a not-now list put that ranking back in the hands of the person who should hold it.

Here is a question to carry into this week. Think about your team’s current list. What is one item that everyone calls important but nobody would be upset to see wait until next month?

If you want to talk through your own list, send me a message. I’m glad to think it through with you, no pitch attached.

Next reads from the blog:

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

• Coaching Is Not Rescuing: Why Solving Your Team’s Problems Keeps Them Stuck — https://jordanimutan.com/2026/10/06/coaching-is-not-rescuing-why-solving-your-teams-problems-keeps-them-stuck/

• You Think People Aren’t Taking Ownership. They Think It’s Not Safe To. — https://jordanimutan.com/2026/03/21/you-think-people-arent-taking-ownership-they-think-its-not-safe-to/

• Stop Micromanaging. Start Leading. How Systems Create Trust and Ownership — https://jordanimutan.com/2025/06/26/stop-micromanaging-start-leading-how-systems-create-trust-and-ownership/

• Why Your Leadership Program Needs an Owner, Not Just an Attendee List — https://jordanimutan.com/2026/09/29/why-your-leadership-program-needs-an-owner-not-just-an-attendee-list/

#Prioritization #ManagementSkills #Leadership #PhilippineSMEs #TeamPerformance