I want people to think before they escalate an issue. I also want to hear about serious risks while there is still time to act.

Those expectations need to work together. If staff believe they must arrive with a complete solution before speaking up, an escalation rule can delay information a manager needs. This is the format I would use for routine issues, with a separate route for urgent concerns.

When should you escalate an issue?

Escalate when the decision falls outside your authority. You may know what you would recommend but still need permission to change a customer commitment or use another team’s resources. State the boundary you cannot cross, so the manager understands why their decision is needed.

A different trigger is an unresolved dependency that has passed its agreed limit. Record the commitment and the follow-up already made. An information update tells the manager what is happening; a decision request states what you need them to resolve. Label the message accordingly.

I would not require someone to exhaust every imaginable option. Missing expertise or access may prevent a reliable recommendation. Asking for help can be a responsible next step, provided the employee explains what they need to establish.

Clarify decision ownership before setting the reporting rule.

Copy this employee escalation template.

It is acceptable to write, “I do not yet have a reliable option because…” and identify the missing information or expertise. The decision you need may be permission to investigate. A short, honest request is more useful than a confident recommendation built on guesses.

A worked example of a routine escalation.

Illustrative example: a required internal review is pending before a client presentation. “The review is pending. Please advise.” leaves the manager to reconstruct the situation. I would prefer a note like this, using the organisation’s actual names and decision deadlines.

The employee has made the decision easier to assess without assuming the manager’s authority. The note also preserves uncertainty: a possible backup is not a confirmed reviewer. If neither option is feasible, the manager needs to set a different route rather than treating the recommendation as an instruction already issued.

The manager needs a response template too.

Acknowledging a message does not resolve its decision. If you need more information, identify what is missing and who will obtain it. If you cannot decide, name the person who can and confirm when they will take ownership. Otherwise the employee may read “noted” as permission to proceed.

I would resolve the immediate issue before coaching the quality of a routine escalation. A manager can challenge weak reasoning without humiliating the person who raised it. Ask what evidence supports the recommendation and what would change it. Keep that discussion separate from whether reporting the concern was welcome.

AHRQ’s healthcare guidance emphasises acknowledging raised concerns. Its mutual-support material also treats asking for assistance as compatible with responsibility. Those are useful principles to consider, not evidence validating this business template. Speaking up and acknowledgement; Mutual support in healthcare.

Agree what happens when nobody responds.

Agree response expectations for your organisation rather than copying universal deadlines. Keep the unresolved decision visible until responsibility is accepted. If the risk increases or the agreed response time passes, use the designated backup route. Do not let an unanswered message become an unspoken transfer of responsibility.

Where AI can help.

AI may organise authorised notes or flag a missing decision request. Use an approved tool with information you are permitted to share. I would use a bounded prompt like this:

The employee verifies the final message against the source notes. The authorised manager retains the decision. AI does not replace urgent reporting, and a polished paragraph does not establish that its explanation is correct.

Read more about human accountability in AI workflows.

Introduce the standard without creating more paperwork.

I would trial the format with a small team using a recent anonymised issue. Ask the employee to prepare the note and the manager to answer it. Look for information that changed the decision, and remove fields that add effort without helping that review. Keep the urgent route visible throughout.

Review decision turnaround and unresolved items past their agreed deadlines. Also check whether urgent reporting has become slower. These are proposed measures, not promised improvements. Preparation should improve routine decisions while preserving early reporting of important concerns.

The business context

Lunox Malaysia is a self-funded consumer health and sleep wellness brand. My role was to help shape its business model and operating structure as it grew.

My advisory work

Business model & positioning

I helped connect the brand's commercial positioning with how the business would operate.

Operating structure & performance rhythms

The work connected commercial positioning with the management rhythms needed to support growth.

The operating lesson

My takeaway from this engagement: commercial direction needs a clear path into everyday execution. The value of an operating structure is whether it helps people act on the business model.

When an SME is growing, leaders often focus on targets, systems and customer delivery. Motivation can feel less concrete. Yet the way work is designed and managed determines whether people bring judgment, energy and ownership to those targets.

The ten behaviours below are quiet because each one can look small in isolation. Repeated over time, they teach people that contribution is risky, effort is not recognised, and standards depend on who is involved.

10. Taking credit for other people's work

Recognition tells a team what the organisation values. When a manager presents someone else's idea or result as their own, the person loses more than public credit. They lose confidence that contribution will be treated fairly.

What strong leaders do instead

Name the people who shaped the result. Explain their contribution specifically. Shared credit does not weaken leadership authority. It shows that the leader can build capable people and recognise them honestly.

9. Ignoring ideas and input

Employees closest to customers, workflows and recurring problems often see risks before leaders do. If their input disappears without explanation, they learn that speaking up creates effort without impact.

What strong leaders do instead

Close the loop. If an idea is not being used, explain why. A clear answer preserves trust even when the answer is no. When the suggestion is useful, show what changed because someone raised it.

8. Micromanaging every small detail

Micromanagement often begins as quality control. It becomes destructive when every decision returns to the manager. People stop using judgment because the safest option is to wait for approval.

What strong leaders do instead

Define the outcome, constraints, decision rights and review point. Then allow the person to choose the method. Control the conditions that matter without controlling every movement.

7. Giving feedback only when something goes wrong

If feedback only arrives with criticism, people associate leadership attention with danger. They become more cautious, hide uncertainty and avoid experiments that could improve the work.

What strong leaders do instead

Make feedback frequent, specific and balanced. Reinforce the behaviour that should continue. Address gaps early enough for the employee to change course before the final result is judged.

6. Changing priorities without explanation

Priorities sometimes need to change. The motivational damage comes from unexplained change. People invest in an outcome, watch it get replaced, and receive no context for what changed or what should stop.

What strong leaders do instead

State the new priority, the reason, the trade off and the work that is no longer required. Teams can adapt quickly when they understand the decision. They become cynical when every direction feels temporary.

5. Failing to follow through on promises

Small commitments create a pattern. A promised decision, resource or conversation that never happens tells people that leadership words are provisional. Trust then becomes expensive to rebuild.

What strong leaders do instead

Track leadership commitments with the same discipline used for employee actions. If circumstances change, communicate before the deadline. A renegotiated promise is usually better than silence.

4. Playing favourites

People notice who receives information, opportunity, flexibility and forgiveness. When access depends on personal preference rather than contribution and need, performance standards lose credibility.

What strong leaders do instead

Make the logic behind important decisions visible. Use consistent performance criteria. Fairness does not require identical treatment, but different treatment should have a clear and defensible reason.

Fair rewards across different cultures

A regional reward policy can produce different reactions even when the written rule is identical. Expectations around individual recognition, team contribution, transparency and manager discretion vary across markets.

The answer is not a separate performance standard for every country. Keep the outcome standards consistent. Then explain how contribution is evaluated in the local context, including why an exception exists and who approved it.

Fairness travels better than sameness. Employees do not need every decision to be identical. They need the logic to be understandable, defensible and applied without favouritism.

3. Setting unclear expectations, then blaming people

When the standard remains in the manager's head, employees can only discover it after the work is reviewed. They begin to ask for approval on every step because independent judgment feels unsafe.

What strong leaders do instead

Define the outcome, constraints, decision rights and what good looks like before the work begins. Clarity is not micromanagement. It gives people a fair chance to succeed. Read the deeper guide to setting clear expectations without controlling every detail.

2. Letting poor performance become everyone else's problem

Work does not disappear when a leader avoids consistent underperformance. It moves to the people who are already reliable. Over time, dependability starts to feel like a penalty.

This is the high performer tax. The strongest employee becomes the answer to every weak handoff, urgent recovery and unfinished task. Leaders may call it trust, while the employee experiences the cost of being reliable.

What strong leaders do instead

Address the gap early. Confirm the standard, provide support, agree on a review period and act when performance does not improve. Accountability protects the team when it is fair and timely.

Audit the destination of unfinished work. If the answer is repeatedly the same person, repair ownership at the original handoff before adding another task to the dependable employee.

1. Punishing honesty

Teams learn what is safe to say. If bad news creates anger, questions are treated as resistance, or disagreement becomes disloyalty, people stop speaking before they stop caring.

What strong leaders do instead

Separate the message from the messenger. Thank people for surfacing risks early. Psychological safety does not mean lower standards. It means the truth appears early enough for the team to solve the problem.

A practical motivation audit for SME leaders

Ask these questions during your next leadership review:

1. Can every team member explain their most important outcome and what good looks like?
2. Are reliable employees repeatedly absorbing work created by weak performance elsewhere?
3. Do priority changes include a reason, a trade off and a clear stop decision?
4. Can people raise bad news without being blamed for the news?
5. Do recognition, opportunity and consequences follow visible standards?

Do not try to repair all ten issues at once. Identify the behaviour causing the greatest loss of trust. Change the operating rule behind it. Then repeat the audit after the team has experienced the new pattern consistently.

A common management pattern begins with a short instruction. The employee starts work using the information available. At review, the manager reveals a standard that was never explained. The employee is then criticised for missing it.

The manager may see a performance problem. The employee experiences a moving target.

After this happens repeatedly, people stop trusting their judgment. They ask for approval on small choices. They copy the manager on every decision. They spend energy protecting themselves instead of solving the problem.

Clarity is part of accountability

Accountability requires a credible agreement about what should happen. If the outcome, standard or authority remains unclear, the manager is evaluating an expectation that existed only in their own head.

This does not mean every task needs a long document. The level of clarity should match the risk, complexity and experience of the person doing the work.

A routine task may need one sentence. A cross functional initiative may need a written brief, decision map and review cadence.

The six part expectation framework

1. Outcome

Describe the result that must exist when the work is complete. Focus on the business outcome rather than the activity.

Weak: Prepare a report on customer complaints.

Clearer: Identify the three complaint patterns causing the most refunds and recommend one action for each by Friday.

2. Context

Explain why the work matters now. Context helps an employee make sensible trade offs when new information appears.

For example, a complaints report intended for product redesign will be structured differently from one intended for a customer service training session.

3. Constraints

State the boundaries that cannot be crossed. These may include budget, legal requirements, brand standards, customer commitments or dependencies on another team.

Constraints should protect the business without becoming a list of personal preferences.

4. Decision rights

Clarify what the employee can decide, what requires consultation and what requires approval. Ownership cannot grow when authority remains invisible.

A useful statement is: You can make the decision within this budget. Consult Finance if the payment terms change. Return to me only if the customer commitment is affected.

5. Quality standard

Explain what good looks like. Use an example, a measurable standard or a short checklist. Avoid asking people to match an unstated preference.

If a previous piece of work represents the standard, show it and explain which aspects matter. Do not assume the example can speak for itself.

6. Review point

Set the next useful check in. Review early when the work is new, risky or difficult to reverse. Review later when the employee has experience and the decisions are easy to adjust.

A review point is not permission to inspect every step. Its purpose is to surface learning and risk at the right moment.

How to clarify without micromanaging

Clarity defines the destination and the important boundaries. Micromanagement controls the route even when the employee is capable of choosing it.

Before stepping into the work, ask:

• Is the agreed outcome at risk?
• Has an important constraint changed?
• Does the person lack information or capability they could not reasonably have?
• Are you correcting a business risk or expressing a personal preference?

If the outcome and constraints remain protected, allow room for a different method. That space is where judgment and confidence develop.

Resetting accountability after a vague brief

If the original expectation was unclear, do not pretend the problem belongs only to the employee. Reset the agreement.

1. Acknowledge what was missing from the original direction.
2. Clarify the outcome and standard now.
3. Confirm the support or information the employee needs.
4. Agree on a new review point.
5. Evaluate performance against the reset expectation.

This does not remove accountability. It makes accountability fair.

Clarity matters even more during AI transformation

AI can produce work quickly. It can also accelerate confusion when teams do not know the outcome, decision owner or acceptable risk.

Before introducing an AI workflow, leaders should clarify who verifies the result, which data can be used, what quality threshold applies and when a human decision is mandatory. Technology does not remove the need for clear expectations. It increases it.

This principle connects to a wider pattern. Explore the full guide to ten leadership behaviours that quietly kill team motivation, or read why AI transformation fails when the operating system stays broken.

Technology is rarely the first constraint

When an organisation feels pressure to “do something with AI,” the natural response is to buy a platform, launch training or assemble a list of use cases. Activity rises quickly. Results often do not.

The deeper constraint is usually operational. The process has too many handoffs. Nobody owns the final decision. The data is inconsistent. Teams are measured on activity instead of outcomes. Put AI on top of that environment and the organisation gets faster output, but not necessarily better performance.

This is why AI can create transformation fatigue. Employees experience another tool, another workflow and another set of expectations without relief from the old system. Leaders see adoption dashboards while the original bottleneck remains.

Start with friction, not features

A useful AI initiative begins with a sentence that names the business constraint. For example: “Commercial leaders wait five days for a reliable pipeline view,” or “Customer exceptions move through four teams without a clear owner.” That is specific enough to redesign.

Before selecting technology, map four things:

1. The outcome: What measurable result should change?
2. The workflow: Where do decisions, delays and rework occur?
3. The owner: Who remains accountable when AI contributes?
4. The evidence: What baseline will prove the new approach is better?

This diagnostic work is not a delay to transformation. It is the work that prevents an expensive pilot from becoming another disconnected layer.

Use an SME AI adoption scorecard

AI readiness should be measured at workflow level, not by counting licences, prompts or training attendance. Score each item from one to five before scaling a use case:

1. Business outcome: Is the result specific and measurable?
2. Workflow fit: Does the tool support how the work really happens?
3. Accountability: Is one person responsible for the outcome?
4. Team usability: Can the team use it without relying on the project team?
5. Data reliability: Is the input accurate enough for the decision?
6. Review cadence: Is there a fixed rhythm for checking quality and impact?

The lowest score is the next constraint to fix. A strong average can hide one failure point that makes the whole workflow unreliable.

Automate or redesign? Use a five question gate

Automation makes sense only when the underlying process deserves to run faster. Before automating, ask:

• Is the intended outcome clear?
• Is the workflow stable enough to repeat?
• Are common exceptions understood?
• Is ownership defined at every consequential step?
• Would the process still make sense without the current tool?

If several answers are weak, redesign the process first. That prevents AI from scaling avoidable handoffs, rework and unclear accountability.

Place AI quietly inside the work

The best operational AI is often less visible than a new transformation programme. It summarises a recurring management report, flags an exception before a deadline is missed, prepares decision context or removes repetitive coordination between teams.

Used this way, AI supports the operating rhythm instead of competing with it. Teams do not need to remember to visit another dashboard. Leaders receive a clearer signal at the moment a decision is required.

Good candidates are repetitive, information-heavy steps with a definable quality standard. Poor candidates are ambiguous decisions where context, trust or accountability cannot be delegated safely.

Govern outcomes, not just access

AI governance should extend beyond who can use which model. Operational governance asks who approves consequential outputs, how exceptions are escalated, what evidence is retained and how performance is reviewed.

A practical pilot can be small: one workflow, one accountable owner, one metric and one review cycle. If it produces a genuine improvement, expand carefully. If it creates more review work than it removes, redesign it.

The leadership question

AI can accelerate execution, but it also makes leadership gaps more visible. When information moves faster, unclear priorities and weak ownership surface sooner. The answer is not tighter control. It is clearer intent, better questions and stronger accountability.

The goal is not an “AI-powered company” as a label. The goal is an organisation that makes better decisions, responds earlier and gives people more capacity for high-value work.

AI changes the speed of work, but not the need for leadership

Teams can now research, draft, analyse and automate faster than before. That does not remove the need for leaders. It changes where leadership creates value.

If priorities are vague, AI helps teams produce more work in different directions. If decision rights are unclear, AI creates more recommendations without resolving who chooses. If accountability is weak, automation makes the gap visible sooner.

The organisations that benefit most will not simply have the most tools. They will have leaders who evolve at the same pace as the operating environment.

Shift one: from control to clarity

In a slower organisation, leaders can compensate for ambiguity through frequent approvals and direct supervision. In an AI-enabled environment, that control becomes a bottleneck.

Clarity scales better. Teams need to understand the outcome, boundaries, trade-offs and standard of evidence. With those elements in place, people can use AI to move quickly without waiting for constant permission.

A practical test is simple: can a team member explain what success looks like, what they may decide independently and when they must escalate? If not, the organisation does not have an AI problem. It has an operating clarity problem.

Shift two: from answers to better questions

AI can produce plausible answers instantly. The scarce capability is increasingly the judgment to frame the right problem.

Leaders create leverage by asking: What decision are we actually making? Which assumption matters most? What evidence would change our direction? What happens if the recommendation is wrong?

These questions turn AI from an answer machine into a decision-support system. They also prevent teams from mistaking polished output for a useful conclusion.

Shift three: from tasks to ownership

As routine steps become easier to automate, managing activity becomes less valuable. Ownership becomes more important.

Ownership means a person is accountable for an outcome, understands the customer or stakeholder impact, monitors the right signal and acts when the system produces an exception. AI may complete part of the workflow; it cannot absorb organisational accountability.

Performance systems should evolve accordingly. Rewarding volume while asking for judgment sends conflicting signals. Measures need to reflect quality, outcome and responsible decision-making.

What leaders should do next

1. Choose one important workflow where AI is already changing how the team operates.
2. Write down the outcome, boundaries, decision owner and escalation conditions.
3. Review whether current KPIs reward the behaviour the new workflow requires.
4. Ask the team what became easier, what became riskier and what remains unclear.

This is how an organisation develops AI maturity: not through a one-off training event, but through repeated cycles of clearer intent, better decisions and stronger ownership.

Continue the conversation on LinkedIn ↗

For a practical review of the warning signs and the first operating changes, read the founder dependency guide for Malaysian SMEs.

The founder bottleneck is usually a design problem

Founders often become the organisation’s fastest problem-solver. Early on, that is an advantage. They hold the customer context, product intuition and commercial history. As the company grows, the same strength can become a constraint.

Decisions queue for approval. Managers escalate issues they could solve. Priorities change through conversations that not everyone hears. The founder works harder while the team waits for certainty.

This is not fixed by telling people to “take more ownership.” Ownership needs an operating environment that makes good decisions possible.

Do not promote the best problem solver without testing management readiness

The person who solves problems fastest often looks like the obvious management choice. Yet the strengths that make someone a strong individual contributor can create a new dependency when the role changes.

A manager adds scale by improving the judgment of the team. If they keep taking over difficult work, colleagues learn to wait for rescue. The founder has simply moved the bottleneck one level down.

Before promoting a high performer into management, test four behaviours:

• Under pressure, do they coach or take over?
• Can they define a decision boundary without controlling every step?
• Do colleagues leave conversations with more capability?
• Can performance continue when they are unavailable?

Technical credibility matters. Management readiness depends on whether that credibility becomes shared capability.

Make priorities observable

A leadership team may agree on strategy while departments experience a different reality. Sales is chasing this quarter. Operations is protecting service levels. Product is building for next year. Every objective can appear reasonable in isolation.

The first step is to reduce the number of priorities and express each one as an outcome. A useful priority has a clear owner, measure, deadline and explanation of why it matters now.

Visibility matters because teams cannot align around priorities they only hear about in private meetings. A shared operating review turns strategy into a repeated signal.

Delegate decisions, not just tasks

Task delegation gives someone work while the founder retains the judgment. Decision delegation transfers defined authority.

For every recurring decision, clarify:

• Who recommends and who decides?
• What information is required?
• What financial, customer or reputational limits apply?
• Which exceptions must return to leadership?

This creates speed without abandoning control. The founder stops approving routine choices and focuses on the decisions where their perspective is still uniquely valuable.

Four signs role ambiguity is slowing the company

Role ambiguity becomes expensive before it becomes obvious. Look for duplicated work, recurring decisions that keep escalating upward, arguments about who owns a handoff and outcomes that fall between teams.

The practical fix is to give each recurring outcome one accountable owner, then define which decisions they can make without further approval. A job title alone does not create clarity. People need to know the result they own, the boundary of their authority and the exceptions that require escalation.

For a deeper framework, read how to set clear expectations without micromanaging.

Install a performance rhythm people can trust

More meetings do not create more accountability. A useful operating rhythm brings the same outcomes, owners and exceptions into view at a consistent cadence.

A weekly review should answer three questions: What moved? What is blocked? What decision is needed? A monthly review should go deeper into trends, resource allocation and whether the priorities still deserve attention.

The rhythm becomes credible when leaders use it consistently. If decisions keep happening through side channels, the formal system loses authority and founder dependency returns.

Align rewards with the operating model

Teams notice what gets recognised. If leaders ask for collaboration but rewards remain purely individual, the organisation receives two different instructions. If people are measured on activity, they will protect activity even when outcomes are weak.

Performance measures should connect the company outcome to functional ownership and individual contribution. The purpose is not more metrics. It is a clearer line between effort, decision and result.

Use AI after the rhythm is clear

Once the operating system is visible, AI can reduce reporting effort, summarise risks, identify recurring blockers and prepare decision context. It becomes a multiplier for a functioning system instead of a substitute for one.

Before automating a workflow, use the AI operational transformation scorecard to test whether the outcome, ownership and review rhythm are ready.

The sign of progress is not that the founder becomes irrelevant. It is that the organisation can make more good decisions without requiring the founder to carry every one of them.