Better Prompts Won’t Fix a Task Nobody Has Defined

Your team does not have a prompt problem. It has a task problem.

Over the past year, many companies have sent people to prompt-writing workshops, shared lists of “perfect prompts,” and bought guides with names like “100 prompts for managers.” Then they waited for results. The results have been mixed at best.

The reason is simple, and you may already sense it. A prompt is a set of instructions. If you cannot explain a task clearly to a new colleague, you cannot explain it to a tool either.

The new hire test

Try this. Take a task you want AI to help with, such as replying to customer complaints. Write down the instructions you would give a new hire who starts on Monday. Then ask: could they do the job well using only those instructions?

Most people find they cannot. The writing is not the hard part. The answers are. What counts as a complaint worth escalating? When do we offer a refund? Who approves it? What tone do we use with a customer who has been with us for ten years?

Those are decisions about the work, not about the prompt. A better prompt cannot answer them. Only your team can.

What a defined task looks like

A task is defined when five things are written down.

1. The input. What arrives, in what form, and from whom.

2. The output. What a finished result looks like, with one real example.

3. The rules. What to do in the common cases, and in the edge cases you already know about.

4. The check. Who reviews the result, and what they look for.

5. The hand-off. Where the result goes next, and who needs to know.

When these five are clear, the prompt almost writes itself. You are copying answers into words. When they are not clear, no amount of clever wording will help, because the tool is guessing at the same gaps your new hire would.

What it looks like in numbers

Picture a team that spends 10 minutes on each first reply to a customer email, and sends 60 a week. That is 600 minutes, or 10 hours. These numbers are illustrative, so replace them with your own.

The team tries AI with a short, general prompt.

• Draft: 1 minute. Editing a weak draft: 8 minutes. Total: 60 × 9 = 540 minutes, or 9 hours

• Time saved: about 1 hour a week. Barely worth the change

Then the team spends one hour defining the task. They write down the rules, add three examples of good replies, and name who checks the results.

• Draft: 1 minute. Editing a good draft: 3 minutes. Total: 60 × 4 = 240 minutes, or 4 hours

• Time saved: 6 hours a week, or about 300 hours a year

The tool was the same in both cases. The difference was the clarity of the task.

Why the prompt myth is so popular

Prompt tips are easy to share. A good prompt fits on a slide. Defining a task means sitting with the people who do it, and often finding out that two of them do it differently.

That second part is uncomfortable. It is also where most of the value is. If two people do the same task in two ways, your company has no standard, with or without AI.

Fixing that is not a technology project. It is a conversation, and it usually pays off even if you never use a tool. New hires learn faster. Mistakes drop. Handovers get easier.

A short example of a missing rule

Imagine the AI drafts a reply to an angry customer and offers a full refund. The reply is polite and well written. It is also wrong, because your company only refunds after the item is returned.

No change of wording would have prevented that. The rule was never written down. It lived in the heads of two experienced staff members, who fixed the draft by hand every time, and never said why.

Once the rule is on the page, the tool follows it every time. And the next new hire follows it too.

Three objections you will hear

“We do not have time to write it all down.” You are already spending the time, in editing. Writing the page once costs about an hour. Editing weak drafts costs hours every week.

“Every case is different.” Some are. Most are not. Define the common cases first, and send the rest to a person. That alone covers the bulk of the work.

“Our best people just know how to do it.” That is the best reason to write it down. Knowledge kept in one head is a risk. Knowledge on a page is a shared asset.

Where prompts still matter

Prompts are not useless. Once the task is clear, a good prompt saves time and gives steadier results. Plain language works best: say what you want, give the rules, and show an example of a good result.

Keep the finished prompt in one shared place, with a name and an owner. When the task changes, update it. A prompt that lives in one person’s chat history leaves the company when that person does.

Also keep a short list of replies that needed heavy editing, and why. Those are the best clues for improving the rules. Most of the time, the fix is a missing rule, not a missing word.

How to define a task in one hour

Gather the two people who do the task most often. Ask each to complete three real examples while saying aloud why they make each choice. Write down every decision.

Then compare. Where the two differ, decide the standard together. Write one page: input, output, rules, check, hand-off.

You do not need a perfect document. You need a page that exists and that the team agrees with. You can improve it after the first month of use.

Where AI helps

AI can help you define the task, too. Give it your three examples and ask it to list the rules it sees in them. Then ask what is unclear. The questions it asks are often the same ones a new hire would ask.

Treat the answers as a first draft. Your team knows the exceptions, the customers, and the history. The tool can only work from what you show it.

One caution. Do not paste customer details or private company files into a tool until your company has a clear rule about what it may see. Use made-up examples while you are still defining the task.

Try it this month

1. Choose one task where your AI results have been disappointing.

2. Run the new hire test and mark the place where your instructions run out.

3. Fill in the five parts: input, output, rules, check, hand-off.

4. Turn the page into a prompt, and compare the editing time before and after.

Time the editing, not the drafting. The draft is always fast. The editing is where the real cost hides.

If the results are still weak after this, the page tells you where to look. That alone is worth the hour.

A better prompt starts with a clearer task.

Which task on your team would you struggle to explain to a new hire on one page?

If you want to talk through how to define a task before handing it to AI, I’d be glad to hear your thoughts.

ADDITIONAL READING

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

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

• Your First AI Project Should Be Boring. Here Is How to Pick It. — https://jordanimutan.com/2026/11/07/your-first-ai-project-should-be-boring-here-is-how-to-pick-it/ • 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/

Employee Onboarding Is a Manager’s Job: A First-30-Days Plan for New Hires

If you have new people starting in January, the first month is already being decided, mostly by whoever is organized or not. In many companies, onboarding is treated as an HR task: forms, accounts, an introduction to the team. After more than 30 years of managing people, I believe the part that decides whether a new hire succeeds belongs to their manager.

What the research says

InsightGlobal’s 2025 Employee Sentiment Report, cited by AIHR, found that 22% of workers had left a job within 90 days, and 60% of those who left within three months pointed to a lack of training or disorganized training. The same AIHR roundup cites Gallup research finding that new hires whose managers were actively involved were 3.4 times more likely to rate their onboarding experience as exceptional. The year of that Gallup figure is not stated in the article, so I treat it as a signal. It is also worth noting that, in a TalentLMS and BambooHR survey cited there, 75% of employees were satisfied with their manager’s support during onboarding, compared with 67% for HR support.

None of this means HR does not matter. It means the new person’s daily experience comes from the manager.

A simple plan: Ready. First win. Day-30 talk.

You do not need a thick program. You need three things.

Ready. Before day one, make sure the basics are in place: a desk or workspace, tools and accounts that work, a named person to sit with or ask questions, and a plan for the first week. Little frustrations in the first days, such as waiting for a password, send a message about how the company works.

First win. Agree on one clear goal the new person can reach in the first few weeks. Not a list of ten things. One small, real piece of work that matters, with a clear idea of what good looks like. It gives the person early confidence and gives you something concrete to discuss.

Day-30 talk. About a month in, set aside twenty minutes and ask three questions. What is going well? What is unclear? What would have helped you in the first week? Then act on the answers, however small.

Who to ask, and what is expected

Two things new people most want to know are who to ask and what is expected. On day one, tell them both. Name one person for everyday questions, so they are not guessing who is allowed to be bothered. And write down, in a few lines, what a good first month looks like.

What this is not

It is not a replacement for HR’s work. Forms, policies, and legal requirements still matter. This is the manager’s layer on top: making the person feel expected, supported, and clear about what to do next.

Think of your last hire. On day one, did they know who to ask and what their first win was?

If you would like to put together a simple first-30-days plan for your team, send me a message. I’m happy to compare notes, no pitch attached.

Next reads from the blog:

• Why Managers Cannot Name the Company’s Top Priorities, and How to Fix It — https://jordanimutan.com/2026/11/12/why-managers-cannot-name-the-companys-top-priorities-and-how-to-fix-it/

• Cross-Department Handoffs: Why Work Gets Stuck Between Teams and How to Fix It — https://jordanimutan.com/2026/11/05/cross-department-handoffs-why-work-gets-stuck-between-teams-and-how-to-fix-it/

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

• 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 Managers Can Hold People Accountable Without Micromanaging — https://jordanimutan.com/2026/11/04/how-managers-can-hold-people-accountable-without-micromanaging/

#Onboarding #NewHires #Leadership #PhilippineSMEs #ManagementSkills

How to Have Career Conversations With Your Team Before They Start Looking Elsewhere

Year-end is when many managers think about reviews, budgets, and next year’s plan. It is also a good time to ask each person a question that costs nothing: where do you want to be in two years? After more than 30 years of managing people, I have found that this one question is skipped far more often than it should be, and the answers are usually more useful than managers expect.

What the research suggests

A survey by Lattice and Censuswide of more than 2,000 employees at mid-to-large US companies found that 26% said they and their manager do not discuss career progression, and 29% said they lacked a clear view of career opportunities in their company. Of all respondents, 76% said they would be somewhat or very likely to leave because of dissatisfaction with career progression. The survey is from 2021 and covers US workers, so treat the numbers as a reminder and not a measure of your own team. The point is still easy to recognize: people who cannot see a future often start looking for one somewhere else.

Development does not always mean promotion

Many managers avoid this conversation because they worry they cannot offer a promotion. Most small and mid-sized companies have few senior roles, and that is fine. Development can mean a bigger piece of work, a new skill, a chance to lead a small project, or time with someone who knows the business well. Often what people want is simply to know they are growing.

A simple method: Two years. Six months. Next step.

You do not need a special form. You need about twenty minutes, once or twice a year, with each person. Ask three things.

Two years. What would you like to be doing in two years? It can be vague. Ask what they would enjoy more of, and what they would like less of.

Six months. What would you like to learn or get better at in the next six months? Ask what skill, if they had it, would make their work easier.

Next step. What is one thing that would help you take the first step, and what is one thing I can do? Agree on one action, with a date. A stretch task, an introduction to a colleague, a short course, a new responsibility.

Listen more than you talk

The goal of the conversation is not to promise anything. It is to understand. If someone’s answer surprises you, that is useful information. You may learn that a quiet person wants more responsibility, or that someone you consider ambitious would like a steadier role.

What this is not

It is not a review, and it should not replace one. Keep it separate from the performance and pay conversation, so that people can speak freely about what they want. It is also not a promise. Be clear about what you can offer, and keep the promises you make, however small.

Pick your strongest person. If they told you tomorrow what they want in two years, would you be surprised?

If you would like to think through how to start these conversations in your team, send me a message. I’m glad to compare notes, no pitch attached.

Next reads from the blog:

• How to Run a Year-End Performance Review That Helps Instead of Dreaded — https://jordanimutan.com/2026/11/10/how-to-run-a-year-end-performance-review-that-helps-instead-of-dreaded/

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

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

• Why Your Most Helpful Employee Is Also Your Biggest Time Leak — https://jordanimutan.com/2026/11/03/why-your-most-helpful-employee-is-also-your-biggest-time-leak/

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

#EmployeeDevelopment #Retention #Leadership #PhilippineSMEs #ManagementSkills

Why Approvals Sit in Inboxes for Days, and the Rules That Move Them

A purchase request has been sitting in someone’s inbox since Monday, and the person holding it is not being lazy.

They are busy. The request is not urgent to them. And nothing in the process tells them it is waiting. So it waits. The requester follows up on Wednesday. The approver replies on Thursday with a question. The answer takes another day. A ten-minute decision takes a week.

This happens in almost every company. It rarely shows up in a report, because nobody is doing the work badly. The work is simply not being done at all while it waits.

Waiting is the biggest part of the delay

Most approvals need only a few minutes of real attention. Yet they take days to finish. The gap is waiting time, and waiting time is invisible, because nobody is working on it.

Take a company that handles 40 approvals a week: purchase requests, leave forms, expense claims, and quotes. These numbers are illustrative, so replace them with your own.

• 40 approvals × 5 minutes of real review = 200 minutes, about 3 hours

• Follow-ups and “did you see my request?” messages: 40 × 10 minutes = 400 minutes, close to 7 hours

• Average waiting time of 2 days: 40 × 2 = 80 days of waiting, spread across the team

The review costs 3 hours. The chasing costs more than twice that. And the waiting costs 80 days of other people’s progress, which no timesheet will ever show.

Those 80 days matter. A salesperson waits for a discount approval while the customer cools off. A supervisor waits for a purchase approval while a machine sits idle. The cost lands on whoever is next in line.

Why approvals stall

When managers see this, they usually say people need to respond faster. It sounds reasonable, but it rarely works. Approvals stall for three reasons, and speed is not one of them.

1. Nobody knows it is waiting. A request lands in an inbox among 80 other messages. Nothing marks it as needing a decision by a certain day.

2. The approver lacks what they need. The request says “please approve” but not the amount, the reason, or the alternative. The approver replies with a question, and the clock starts again.

3. Nobody is sure who decides. The request goes to the wrong person, or to two people who each assume the other will act.

Each of these is a problem with how the process is built, not with the people in it. Telling people to be faster fixes none of them.

Four rules that move approvals

You do not need new software to fix this. Start with four rules for one type of approval.

• Name one approver and one backup. Write both down. If the approver is away, the backup decides without asking anyone.

• Set a time limit, such as two working days. State what happens when it passes: the backup decides, or low-value requests are approved automatically.

• Set a limit below which no approval is needed. Many companies approve small items out of habit, and the approval costs more than the item.

• Define what a complete request contains: the amount, the reason, the deadline, and the one alternative that was considered. Anything missing goes back the same day, not after three days.

The third rule is the most powerful. Ask how often small requests are turned down. If the answer is almost never, the approval is a toll booth, not a safeguard. Remove it, and keep control through a short monthly review of what was spent.

A small example

Picture an office where every supply purchase needs a manager’s sign-off. Most requests are for small items, and nearly all are approved. The manager spends part of every week on them, and the team waits for each one.

Now set a per-item limit, and review all purchases once a month. Most requests disappear in one move. The manager keeps control through the review. The team stops waiting.

Nothing about the people changed. The process simply stopped asking a question it did not need to ask.

Where AI helps

AI is useful at three points, and none of them replaces the approver’s judgment.

• Checking a request for completeness before it is sent, and asking the requester for whatever is missing.

• Summarizing the request in three lines for the approver: the amount, the reason, and how it differs from past requests.

• Sending a reminder when a request passes its time limit, and passing it to the backup.

The person still decides. The tool removes the sorting, the chasing, and the back-and-forth that surround the decision.

One caution. Do not let a tool approve anything on its own until you have a clear limit, a record of every decision, and a person who reviews the results each month. Start with the checking and the reminders.

When the answer is no

A fast no is a good result. The worst outcome is a request that sits for a week and then gets declined. By then the requester has lost time, and the reason for the request may have passed.

Ask approvers to give a short reason with every no, even one line. It teaches requesters what a good request looks like, so the next one arrives complete. Over a few months, fewer requests are declined, and fewer need a second look.

Also ask who is being protected by each approval step. If the answer is vague, the step may be a leftover from a problem that no longer exists.

What the numbers look like after

Using the same illustrative company, suppose the four rules and a simple completeness check bring the work down like this.

• Real review time stays about the same: 3 hours

• Follow-ups fall to about 2 minutes per approval: 40 × 2 = 80 minutes, about 1.3 hours

• Average waiting time falls from 2 days to half a day: 40 × 0.5 = 20 days

The chasing drops by about 5.7 hours a week, or around 285 hours a year. The waiting drops by 60 days of delay every week. The second figure is harder to count, and it is probably the bigger gain.

Measure the wait, not the work

Pick one approval type and record the days from request to decision for a month. Most companies have never measured this number. The first result is often a surprise, and it makes the case for the fix better than any argument.

After you change the rules, measure again. If the average wait drops from four days to one, you have given your team three days back on every request, without asking anyone to work harder.

Try it this week

1. Choose one approval your team complains about.

2. Write down the approver, the backup, and the time limit.

3. List what a complete request must contain, and share it with everyone who makes requests.

4. Ask whether anything below a set amount can be approved without asking.

Do not start with the hardest approval. Start with one that is common and low in risk. A quick win builds trust for the harder ones.

If you cannot decide which approval to pick, ask your team which one they dread. They already know.

Approvals do not stall because people are slow. They stall because the process lets requests wait without anyone noticing.

Which approval in your company has been waiting the longest, and who is paying for the wait?

If you want to talk through how to speed up approvals in your team, 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/

• Cross-Department Handoffs: Why Work Gets Stuck Between Teams and How to Fix It — https://jordanimutan.com/2026/11/05/cross-department-handoffs-why-work-gets-stuck-between-teams-and-how-to-fix-it/

• Why Comparing Three Supplier Quotes Takes Two Days, and How to Fix It — https://jordanimutan.com/2026/10/15/why-comparing-three-supplier-quotes-takes-two-days-and-how-to-fix-it/

• Why Your Most Helpful Employee Is Also Your Biggest Time Leak — https://jordanimutan.com/2026/11/03/why-your-most-helpful-employee-is-also-your-biggest-time-leak/

• How to Find and Reduce Rework in Your Company — https://jordanimutan.com/2026/11/05/how-to-find-and-reduce-rework-in-your-company/

When to Stop Coaching and Start Holding Someone Accountable

Every manager has been here. You have explained the task, shown how to do it, and given feedback. Weeks later, the same problem is back. You coach again, with a little less patience. At some point, a quiet question forms: is this still coaching, or am I avoiding a harder conversation? After more than 30 years of managing people, I believe that is one of the most useful questions a manager can ask, and one of the least asked.

Why it matters

Gallup’s data on manager behavior shows what happens when problems are ignored. In a table on active disengagement by manager focus, about 1 in 100 employees were actively disengaged under managers who focus on strengths, 22% under managers who focus on weaknesses, and 40% under managers who ignore the employee. The figures are undated and the sample is not stated, so treat them as a signal. But the message is clear. Saying nothing is not the kind option. For the person, and for the rest of the team who watch, it is often the worst one.

Gallup also reports that in 2025 only 44% of managers worldwide had ever received management training. Many managers have never been shown how to move from coaching to accountability, so they keep coaching because it is the only tool they have.

A three-question test

Before you change your approach, ask yourself three honest questions.

Is it clear? Has the person been told, in specific terms, what good looks like? If not, you have a clarity problem, and it is yours to fix.

Is the person able? Have they been shown how, and do they have the skills and tools? If not, coaching is still the right move.

Have they had time and support? Has there been enough time to improve, with real help? If not, give it more.

If the answer to all three is yes and the problem remains, the gap is no longer about skill. It is about follow-through. That is the point to move from coaching to accountability.

What the conversation looks like: Expectation. Observation. Conversation. Action.

A good accountability conversation is calm and specific. It follows four short steps.

Expectation. Say what was agreed. “We agreed that customer messages get answered within one working day.”

Observation. Say what you have seen, with dates and facts. “In the last three weeks, eight messages took more than two days.”

Conversation. Ask for their view, and listen. There may be a reason you do not know. Then say plainly what must change.

Action. Agree what will happen, by when, and when you will check. Write it down and share it, so there is no confusion later.

A word on formal steps

This is general management advice, not legal advice. In the Philippines, formal disciplinary action has required steps. Before you write anything formal, speak with your HR team or legal counsel.

What this is not

Accountability is not punishment, and it is not anger. It is a clear, respectful statement of what is expected and what happens next. Done well, many people improve after it, because they finally know where they stand.

Think of someone you have coached more than twice on the same issue. Is the gap about skill, or about follow-through?

If you would like to think through a specific situation, send me a message. I’m happy to compare notes, no pitch attached.

Next reads from the blog:

• How Managers Can Hold People Accountable Without Micromanaging — https://jordanimutan.com/2026/11/04/how-managers-can-hold-people-accountable-without-micromanaging/

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

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

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

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

#Accountability #PerformanceManagement #Leadership #PhilippineSMEs #ManagementSkills

When AI Works, People Stop Calling It an AI Project

Six months after launch, your team still calls it “the AI project.” That is not a good sign.

When a change really lands, it loses its name. Nobody talks about “the email project” or “the spreadsheet project.” Those tools are simply how work is done. An AI effort that still has a project name, a steering group, and a monthly update is usually not part of the work yet. It is a visitor.

Many companies celebrate the launch and move on. The real test comes later, and it is a quiet one: does the new way of working continue when nobody is watching?

Why projects stay projects

Most AI efforts start well. A small group tries a tool, finds a use, and shows good results. Leaders are pleased. Then attention moves elsewhere.

Without anyone watching, old habits return. Some people keep using the new method, some drift back to the old one, and some never learned it. Results become uneven, and the company concludes that the tool “did not stick.”

The tool usually did not fail. The change was never finished. Nobody decided what the new normal was, wrote it down, or removed the old route.

There is a second reason. The people who ran the pilot were the enthusiasts. They were willing to learn, to experiment, and to put up with rough edges. The rest of the team was never asked to do any of that, so the method has to work for them as well, with less patience.

What normal work looks like

A task has become normal work when four things are true.

• It has an owner. One named person is responsible for how it works and for fixing it when it does not.

• It is written down. The steps, including where AI is used and where a person checks, sit in the same place as every other procedure.

• New people learn it as the way things are done. It is part of onboarding, not an optional extra.

• The old way is retired. Two ways to do the same task means nobody is sure which one is right.

If any of these is missing, the change is still on loan. It will last only as long as the enthusiasm of the people who started it.

Notice that none of the four marks involves technology. All four are management choices. That is good news, because the fix is within reach of any team lead.

A small example

Take a team that uses AI to draft weekly customer updates, with a person checking each one. The plan: 25 updates a week, each taking about 4 minutes instead of 12. That saves 8 minutes each, or about 3.3 hours a week. These numbers are illustrative.

Three months in, the results are mixed. Two writers use the draft every time. One sometimes writes from scratch, because they do not trust it. A new hire was never shown the method and writes everything by hand.

Count it. If only 15 of the 25 updates follow the new method, the team saves 15 × 8 = 120 minutes, or 2 hours a week, not 3.3. The gap is about 1.3 hours a week, or roughly 65 hours a year. The tool did not lose those hours. Habit did.

Closing that gap needs no new technology. It needs an owner, a written procedure, a place in onboarding, and a clear end to the old method.

Five steps to make it normal

1. Name an owner. Pick one person who is responsible for the new way after the project team moves on. Make it part of their role, not a favor.

2. Write the procedure. One page in plain words: what the task is, which steps use AI, what the person checks, and what to do when the result looks wrong.

3. Put it in onboarding. New hires should learn the method in their first week, from the same document everyone uses.

4. Retire the old way. Announce the date after which the old method stops. If a task has two accepted methods, people will choose the familiar one.

5. Review once a month. Check three numbers: how many tasks follow the new method, the time per task, and how often the output needed correction.

None of this needs a big budget. The owner’s time, one page of writing, and a few minutes in each onboarding add up to very little next to the hours at stake.

Why announcing is not enough

Leaders sometimes assume that explaining the change once is enough. People hear the announcement, nod, and go back to their desks, where the old way is still easier.

Habits follow convenience. If the new method is harder to find, harder to start, or not expected by anyone, it will lose. Make the new way the easy way, and make the old way take more effort than it is worth.

This is also why the monthly review matters. It is not policing. It is interest. When a manager asks how the new method is going, people keep using it.

Listen to the people using it

Some resistance is sensible. People worry about errors, about being judged by a tool’s output, or about being replaced. Ignoring those worries creates quiet workarounds.

Ask the team what is not working, and fix the real problems. A draft that is often wrong should be improved or dropped. Trust comes from a tool that keeps its promises, not from a better announcement.

You do not need a survey. Ask three people who use the method every week: what do you skip, what do you fix by hand, and what would you change?

When to call the project finished

Set a finish line at the start. For example: the method is used for at least 90 percent of tasks, time per task has improved by the amount you planned, and the owner has run it for two months without help from the project team.

When those are true, close the project. Drop the name, end the steering meetings, and let the work be work. That is not the end of improvement. It is the moment the improvement becomes part of how the company runs.

Keep a short note of the results at close, such as hours saved per week and the number of tasks covered. It protects the work if budgets are reviewed later.

A project that never ends is not a sign of ambition. It is a sign the change has not landed.

Try it this month

1. List the AI-assisted tasks your team started in the last six months.

2. For each one, check the four marks: owner, written procedure, onboarding, and a retired old way.

3. Pick the task with the most missing marks and fix those first.

Then measure again in a month. If the time per task has improved, you have closed part of the gap. If it has not, find out which of the four marks is still missing.

Do not start new projects until the old ones have landed. Five half-finished changes cost more than two finished ones, and they make people tired of every change that follows.

An AI project succeeds the day people stop calling it one.

Which AI-assisted task on your team has quietly gone back to the old way, and would anyone notice?

If you want to talk through how to make a change stick in your team, I’d be glad to hear your thoughts.

ADDITIONAL READING

• How to Lead Change at Work: Why Announcing a New Process Is Not Enough — https://jordanimutan.com/2026/10/31/how-to-lead-change-at-work-why-announcing-a-new-process-is-not-enough/

• Stop Counting AI Users. Start Counting Hours Saved on One Task. — https://jordanimutan.com/2026/10/29/stop-counting-ai-users-start-counting-hours-saved-on-one-task/

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

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

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

Why Managers Cannot Name the Company’s Top Priorities, and How to Fix It

Ask five managers to name the company’s top three priorities. Count how many different answers you get.

If you get five different lists, the plan is not reaching the people who run the work. Many companies finish their annual plan at this time of year and then find that managers cannot say what it asks of them.

Why priorities get lost

  • Too many. When everything is a priority, managers pick their own.
  • Said once. A town hall or an email is easy to forget by the second week.
  • Not translated. Nobody told each team what the priority means for its own work.
  • Not in the weekly routine. Team meetings cover daily problems, not the priorities.
  • Different measures. A manager’s own targets may point somewhere else.

What it costs

Teams work hard on different things. Senior leaders see activity, but not progress on what matters most. And the plan sits in a document.

Five steps to fix it

  1. Limit the priorities to three. Write each as a result, for example “reduce customer complaints by a set amount this year.”
  2. Ask each department to write one sentence on how its work supports each priority and how it will measure that.
  3. Put the three priorities at the top of the weekly team meeting. Ask: what did we do this week for priority one?
  4. Have executives ask managers the same question in their regular reviews.
  5. Repeat the five-manager test every quarter. Count how many give the same answer.

The role of the executive

This works only if senior leaders keep asking. A priority that is mentioned once a year is a slogan. A priority that is asked about every week becomes a habit.

Strengthening execution across branches, sites, plants and functions is one of the priorities we build a 90-day pilot around at POC Management Execution. A pilot is a small trial with one group of managers, run before a change goes company-wide.

A priority is real when every manager can state it and knows what to do about it.

If you asked five of your managers today for the company’s top three priorities, how many would give you the same list?

If you want to try the test and talk through the result, message me and we can brainstorm it together.

Further reading on jordanimutan.com:

• Why Team Deadlines Get Missed, and How Managers Can Fix It Before the Due Date: https://jordanimutan.com/2026/11/04/why-team-deadlines-get-missed-and-how-managers-can-fix-it-before-the-due-date/

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

#StrategyExecution #LeadershipAlignment #ManagerEffectiveness #HRLeadership #BusinessPlanning

Why Sales Follow-Up Falls Through the Cracks, and What Sales Managers Can Do

A customer asks for a quote on Monday. By Friday, nobody has called back.

The salesperson was not lazy. The customer was not unreasonable. The follow-up simply had no owner and no date.

How common this is

A June 2026 Zapier survey of US sales and marketing managers reported that 92% of sales teams drop qualified leads at least once a month. A lead is a person or company that has shown interest in buying. The survey was done in the United States, so treat it as a sign of a common pattern, not a Philippine figure. Many sales managers will recognize it.

Why follow-up gets dropped

  • No written next step. The plan to call back lives in someone’s memory.
  • No date. “Follow up soon” competes with urgent work and loses.
  • Late review. The manager looks at the pipeline monthly, after deals are already lost. A pipeline is the list of sales opportunities and the stage each one has reached.
  • Awkwardness. Many salespeople dislike chasing, so they wait for the customer to respond.

Five practices for sales managers

  1. Give every open lead a next step and a date, written down where the manager can see it.
  2. Hold a 20-minute pipeline review each week. Ask one question first: which leads have no next step, or a date that has passed?
  3. Set a response time for new inquiries. For example, a reply within the same business day.
  4. Look at stalled leads together. Ask what happened. Decide to continue, hand to someone else, or close it.
  5. Track two numbers. The share of open leads with a dated next step, and the time to first reply. Write down the starting numbers first.

The manager’s role

Most follow-up problems are management routines that were never set up. The salesperson needs a clear rule, and the manager needs to ask about it every week.

Increasing sales follow-through is one of the business priorities we build a 90-day pilot around at POC Management Execution. A pilot is a small trial with one group of managers, run before a change goes company-wide.

Follow-up improves when every lead has an owner, a next step and a date.

How many of your open leads have a dated next step today?

If you do not know, message me and we can brainstorm a simple way to find out.

Further reading on jordanimutan.com:

• How Managers Can Hold People Accountable Without Micromanaging: https://jordanimutan.com/2026/11/04/how-managers-can-hold-people-accountable-without-micromanaging/

• Cross-Department Handoffs: Why Work Gets Stuck Between Teams and How to Fix It: https://jordanimutan.com/2026/11/05/cross-department-handoffs-why-work-gets-stuck-between-teams-and-how-to-fix-it/

#SalesManagement #SalesFollowUp #ManagerEffectiveness #HRLeadership #WorkplaceExecution

Why Your Team Types the Same Information Three Times

Your team typed the same customer order three times today, and none of them think it is a problem.

Here is how it usually goes. An order arrives by email. Someone types it into the order sheet. Someone else types it into the accounting system so an invoice can go out. A third person types it into the delivery schedule so the driver knows where to go. Same customer, same items, same address, three times.

Everyone is doing their job. That is exactly why nobody questions it.

What typing it three times really costs

Take a small business with 30 orders a week. These numbers are illustrative, so replace them with your own.

• 30 orders × 3 entries × 4 minutes each = 360 minutes, or 6 hours

• Fixing mismatches between the three records, such as a wrong address or a missing item: about 2 hours

That is 8 hours a week, or about 400 hours a year. Ten full working weeks spent retyping information that already existed.

The errors are the quiet part of the cost. A wrong address on the delivery sheet becomes a missed delivery. A missing item on the invoice becomes an awkward phone call. Each copy is another chance for the facts to drift apart.

Consider an address typed as “12 Mabini St.” in one place and “12 Mabini Street, Unit B” in another. Neither is wrong. Both are incomplete in different ways. The driver follows whichever one he happens to see.

The real problem is not typing

When people see this, the first reaction is to ask for a tool that copies the data automatically. That can help. It skips a more basic question, though: which of the three records is the real one?

In most companies, nobody has decided. Each system was added at a different time, by a different person, for a different need. Each one holds its own version of the order. When two versions disagree, people argue about which is right, or they call the customer to check.

Until someone decides which record is the source of truth, copying data between systems only moves the confusion around faster. It looks like a typing problem on the surface. Underneath, it is a decision nobody has made.

Four steps, in this order

1. Map it. For one process, list every place the same information is entered. Write down who enters it, how long it takes, and why.

2. Choose the source. Pick the one place where the information is entered first and checked. Everything else should read from it, not retype it.

3. Remove the extra entries. Where a second or third entry exists only out of habit, stop it. Many are left over from a time when systems could not share data, and nobody has looked at them since.

4. Automate what is left. Where information truly has to appear in more than one system, let a tool carry it across, with a person checking the result.

Notice how late the tool arrives. Three of the four steps are decisions. Only the last one needs technology.

A common example of step three is the “just in case” copy. Someone keeps a personal spreadsheet of orders because the main system was slow years ago. It is now a fourth record, quietly drifting out of date. Ask people which files they keep for themselves, and why.

Who owns the source record

Name an owner for the source record. This is the person responsible for it being complete and correct at the moment of entry.

When something is wrong, everyone knows who to ask, and the fix happens once at the source, not three times in three places. Without an owner, the source record slowly becomes one more version nobody trusts.

Where AI helps

AI is most useful at the front door, where information first enters. Orders arrive as emails, photos of forms, and messages written in every style. An AI tool can read them, pull out the customer, items, quantities, and address, and fill in the single entry form for a person to check.

The person confirms the entry once. After that, the order flows from the source to the invoice and the delivery schedule without anyone retyping it.

AI can also help with the less obvious problems, such as noticing that an order looks like a repeat of an earlier one, or that an address is missing a unit number. It flags the issue. A person decides what to do.

Two cautions apply. Check the tool’s reading every time at first, especially addresses and quantities. And do not give a tool customer details until your company has a clear rule about what it may see.

What the numbers look like after

• One entry per order, with an AI-assisted first pass and a person’s check: 30 orders × 4 minutes = 120 minutes

• Checking the automatic transfer to accounting and delivery: 30 minutes

• Fixing mismatches, now that there is only one record to correct: about 30 minutes

That is 3 hours a week instead of 8. Five hours come back each week, or about 250 hours a year.

Look at where the saving came from. Going from three entries to one accounts for most of it. The tool made the single entry faster and the transfer automatic, but the big step was deciding which record is the real one.

What to leave alone

Some duplicate records are there on purpose. Backups, audit trails, and legal copies should stay. The target is information typed in by hand more than once, not information stored in more than one place.

Why teams put this off

Duplicate entry hides because it is spread thin. Three people each spend a few minutes, so no one feels the pain, and no one owns the fix.

Fixing it also crosses department lines. The order sheet belongs to sales, the accounting system to finance, and the delivery schedule to operations. Changing one means asking the others, which is slower than living with the problem.

That is why this work usually needs someone senior to say: we are going to enter this once. A small decision from the right person unlocks the rest.

Try it on one process this month

1. Pick one process where you suspect information is typed more than once. Orders, new hires, and customer details are common places to look.

2. Follow one real item from start to finish, and write down every place its details are entered.

3. Count the entries and the minutes, and add up the time spent fixing mismatches.

4. Decide with the other teams which record is the real one, and stop the extra entries.

Talk to the people who do the typing before you talk to their managers. They know which entry is checked, which is ignored, and which one exists only because it always has.

Write the weekly total on one page. Eight hours is hard to ignore when it sits next to a process name.

You do not need software for these four steps. A notebook and a conversation are enough. Most of the savings are already waiting there.

Typing the same information three times is not a typing problem. It is an unmade decision about which record is the real one.

Which process in your company still depends on someone retyping information that already exists somewhere else?

If you’d like to talk through a process 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/

• Why Comparing Three Supplier Quotes Takes Two Days, and How to Fix It — https://jordanimutan.com/2026/10/15/why-comparing-three-supplier-quotes-takes-two-days-and-how-to-fix-it/

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

• Why Your Most Helpful Employee Is Also Your Biggest Time Leak — https://jordanimutan.com/2026/11/03/why-your-most-helpful-employee-is-also-your-biggest-time-leak/

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

How to Run a Year-End Performance Review That Helps Instead of Dreaded

November and December are review season in many Philippine companies. Managers sit down with each person and talk about the year. After more than 30 years of managing people, I can say that most of these conversations fail for one simple reason: the person hears something for the first time that happened months ago. A review should confirm what both people already know. It should never be the first time anyone says it.

What the research says

Gallup’s research on performance reviews, written by Robert Sutton and Ben Wigert, found that only 14% of employees strongly agree their performance reviews inspire them to improve. Nearly half of employees get feedback only a few times a year or less. And compared with annual feedback, weekly feedback made employees 5.2 times more likely to strongly agree they get meaningful feedback, and 2.7 times more likely to be engaged. This research is from 2019, but it speaks to a pattern that is easy to see in most workplaces.

Gallup’s more recent work adds that managers account for about 70% of the variance in team engagement. In short, the way a manager handles moments like this one matters a great deal.

Three steps: Preview. Review. Reset.

You do not need a new form or system. You need to change how you handle the conversation around the form.

Preview. About a week before the review, tell each person the two or three main points you plan to raise. One short message or a five-minute talk is enough. If you cannot bring yourself to preview a point, ask why. It is usually the point the person most needs to hear. A preview means nothing in the meeting is a surprise.

Review. Let the person speak first. Ask what they are proud of this year, what got in their way, and what they would do differently. Then share your view, using specific examples with dates, not general impressions. “The Monday report was late three times in September” can be discussed. “You are not always reliable” cannot.

Reset. End with one priority for the new year and a date for the first check-in, ideally in January. A review that only looks back leaves people with a verdict. A review that ends with one forward step leaves them with a direction.

Keep pay in a different conversation

Gallup notes that holding pay discussions and performance reviews in separate meetings gives each the right focus. When both happen in one meeting, people stop listening to feedback and start listening for the number. If you can, hold them on different days.

What this is not

It is not a reason to soften what needs to be said. A preview makes hard messages easier to hear, not easier to avoid. It is also not a replacement for talking during the year. If your review is the first time you have mentioned a problem, the work of the review begins in January with regular, short check-ins.

Think of the person on your team you most dread reviewing. What is the one thing you have not yet told them directly?

If you would like to think through a difficult review, send me a message. I’m glad to compare notes, no pitch attached.

Next reads from the blog:

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

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

• How Managers Can Hold People Accountable Without Micromanaging — https://jordanimutan.com/2026/11/04/how-managers-can-hold-people-accountable-without-micromanaging/

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

• Why Team Deadlines Get Missed, and How Managers Can Fix It Before the Due Date — https://jordanimutan.com/2026/11/04/why-team-deadlines-get-missed-and-how-managers-can-fix-it-before-the-due-date/

#PerformanceReview #Feedback #Leadership #PhilippineSMEs #ManagementSkills