Understand Your Numbers

Managers must understand their numbers.

This is basic.

A manager who does not know the numbers is managing from impression,
memory, hope and anecdote. They may be busy. They may be sincere. They
may even be experienced. But without numbers, they do not have enough
contact with the reality of the business.

Numbers tell us something important.

Sales. Costs. Margin. Cash flow. Conversion. Capacity. Utilisation.
Quality. Complaints. Productivity. Waste. Absenteeism. Stock movement.
Turnaround time. Customer retention. Project progress. Error rates.

These numbers matter.

They should be close enough that a manager can speak about them
without needing a long search. They should be familiar enough that
movement is noticed. They should be understood well enough that a
manager can explain what changed and why it matters.

But understanding your numbers is not enough.

The deeper management skill is understanding the physical processes
that create those numbers.

A Number Is an Outcome

A number is not magic.

It is an outcome.

It is the result of work, behaviour, process, timing, resourcing,
system design, customer action, supplier performance, decisions and
constraints.

Revenue is not only a number.

It is customers found, conversations held, proposals made, trust
built, orders received, products delivered and invoices paid.

Cost is not only a number.

It is people, time, materials, waste, rework, systems, contracts,
choices, habits and inefficiencies.

Quality is not only a score.

It is design, training, supervision, tools, standards, attention,
handovers and the conditions under which people work.

When managers treat numbers as isolated outcomes, they try to manage
the number directly.

They say:

Increase sales.

Reduce cost.

Improve margin.

Cut complaints.

Raise productivity.

Speed up delivery.

These instructions may be clear, but they are incomplete.

To change a number, something physical must change in the work.

Bigger Goals Are Not a Plan

One of the common mistakes in management is to believe that a bigger
target is the same as a better plan.

The team achieved ten.

Next month the target is fifteen.

The business grew by five percent.

Next year the target is fifteen percent.

Customer satisfaction is at seventy.

The goal is ninety.

There is nothing wrong with ambition.

But ambition without changed operating conditions becomes pressure
disguised as strategy.

If the number must change, the work must change.

More sales may require better leads, clearer positioning, stronger
sales capability, a shorter proposal cycle, more follow-up discipline,
better pricing, improved product quality or additional capacity.

Lower cost may require different procurement, reduced waste, better
scheduling, improved process design, automation, supplier renegotiation
or fewer errors.

Faster delivery may require more people, better planning, fewer
handovers, clearer priorities, improved tooling or removal of
bottlenecks.

Improved quality may require training, supervision, standards, better
inputs, more time at critical points or redesign of the work itself.

Planning to change a number means planning to change the reality that
produces the number.

If that reality remains the same, the target is only a wish.

Know the Levers

Managers must know their levers.

A lever is something that can be changed in the system to influence
the outcome.

Some levers are obvious.

Price. Headcount. Budget. Stock. Hours. Marketing spend.

Others are less visible.

Skill. Sequence. Handover quality. Decision speed. Queue length.
Error correction. Customer effort. Manager availability. Tool
reliability. Supplier responsiveness. Information quality. Workload
balance.

The best managers do not only know the dashboard.

They know what moves the dashboard.

They can say:

If we want to improve this number, these are the three things that
must change.

If we change this lever, this is the likely consequence.

If we push this too hard, this other measure will suffer.

If this measure is declining, these are the first places to look.

This is the difference between reporting and managing.

Reporting explains what happened.

Managing changes what happens next.

Numbers Without Process
Create Blame

When managers do not understand the process behind the number, they
often blame people too quickly.

Sales are down, so the sales team is not trying hard enough.

Costs are up, so managers are careless.

Customer complaints are increasing, so service agents are poor.

Projects are late, so teams are lazy.

Sometimes people are part of the problem.

But people work inside systems.

A sales team may be working with weak leads, unclear positioning,
poor product reliability or a pricing model that no longer fits the
market.

A service team may be receiving calls caused by product defects,
confusing communication or systems that do not give them the authority
to solve the problem.

A project team may be late because dependencies were unrealistic,
approvals were slow, priorities changed, or resources were shared across
too many initiatives.

If the manager sees only the number, the manager may punish the
person nearest to the number.

If the manager understands the process, the manager can ask better
questions.

Where is the constraint?

Where is the work failing?

Where is rework created?

Where are people waiting?

Where is the customer confused?

Where are we asking effort to compensate for poor design?

Numbers without process create blame.

Numbers with process create diagnosis.

Weekly Reports and Monthly
Reports

The old management discipline of weekly and monthly reporting still
matters.

But a report is useful only if it creates better management
conversation.

A weekly report should help managers see movement while there is
still time to act. It should show what is changing, where attention is
needed, what decisions are blocked and whether the work is on track.

A monthly report should show deeper patterns. It should connect
performance to causes, decisions, resources, risks and future
action.

Neither report should be a ritual of data collection.

The purpose is not to produce a document.

The purpose is to understand the business.

Good reports answer practical questions:

What changed?

Why did it change?

What is the pattern?

What action is required?

Who owns the action?

What support is needed?

What decision must be made?

What will we look for next week or next month?

If a report does not lead to better action, it is probably not a
management report.

It is an archive.

Meet Regularly with Managers

Managers should meet regularly with the managers who own the
numbers.

Not only to check whether targets were reached.

To understand what is happening in the work.

The best management conversations move between numbers and
reality.

Show me the number.

Show me the process.

Show me where the work happens.

Show me the constraint.

Show me what the team is doing differently.

Show me what support is missing.

Show me what will change before the next report.

This kind of conversation is not micromanagement if it is done
properly.

It is management.

It respects the fact that numbers come from work, and that work needs
attention, support and judgement.

Managers should not be allowed to hide behind a spreadsheet.

They should also not be judged by numbers without being heard on the
conditions that produce them.

The conversation must hold both.

Resourcing Must Follow
Ambition

If goals become larger, resourcing must be examined.

This does not always mean adding people.

Sometimes the answer is better tools, clearer priorities, fewer
meetings, better training, improved workflow, different suppliers,
stronger supervision, faster decisions, automation or removal of
low-value work.

But something must change.

An organisation cannot keep adding targets without asking what
capacity exists to deliver them.

This is where many plans become dishonest.

The plan shows higher revenue, faster delivery, better quality, lower
cost and improved customer experience. But the same people, same
systems, same processes and same constraints remain in place.

The numbers are expected to improve because the plan says they
must.

That is not management.

That is arithmetic without operations.

Responsible planning connects targets to resources and support
processes.

If the organisation wants more output, it must understand what
creates output.

If it wants better quality, it must understand what creates
quality.

If it wants lower cost, it must understand what creates cost.

If it wants growth, it must understand what growth will demand from
the system.

The Physical Process Matters

Managers should spend time where the work happens.

This may be a factory floor, a service desk, a classroom, a clinic, a
warehouse, a sales call, a software workflow, a finance process, a
customer journey or a project meeting.

The point is not tourism.

The point is understanding.

Numbers become clearer when the manager sees the physical
process.

They see where people wait. They see where information is missing.
They see which system screens slow the work down. They see where
customers become frustrated. They see where quality depends on memory
rather than design. They see where a report hides variation. They see
where one strong person is holding a weak process together.

Physical observation protects the manager from abstract
management.

It prevents the mistake of believing that a number has changed
because the number itself was instructed to change.

The number changed because the work changed.

Or it did not change because the work did not change.

Beware of Isolated Metrics

Metrics can mislead when they are isolated.

If productivity increases, quality may decline.

If costs are cut, service may weaken.

If call times are reduced, customer effort may increase.

If sales grow, margin may fall.

If stock is reduced, availability may suffer.

If utilisation rises too high, people may burn out and errors may
increase.

This is why managers must understand the relationship between
numbers.

Every number sits inside a system.

A good manager does not ask only whether one number improved.

They ask what happened to the surrounding numbers, and what happened
in the work.

Improvement in one place can create damage somewhere else.

The goal is not to move a metric in isolation.

The goal is to improve the system.

Numbers on Your Fingertips

Managers should have their important numbers on their fingertips.

This does not mean memorising every detail.

It means knowing the few numbers that reveal the health of the
area.

What are we trying to achieve?

What tells us whether we are moving?

What tells us whether the customer is better served?

What tells us whether the work is sustainable?

What tells us whether quality is improving?

What tells us whether cost is under control?

What tells us whether risk is increasing?

These numbers should be familiar.

But the deeper knowledge is not the number itself.

The deeper knowledge is knowing what levers change it.

The manager who can recite the number but cannot explain the lever is
still dependent on luck, pressure or someone else’s understanding.

From Review to Action

A review meeting should not end with a vague instruction to
improve.

It should end with a change in action.

What will be done differently?

Who will do it?

What resource is needed?

What support process must change?

What decision is required?

What will be measured next?

When will we know whether it worked?

This is where numbers become management.

The number identifies the issue.

The manager diagnoses the process.

The team changes the work.

The next report shows whether the change had an effect.

Then the cycle repeats.

Without this cycle, reporting becomes theatre.

With this cycle, reporting becomes learning.

Conclusion

Managers must understand their numbers.

They must know them, review them, question them and keep them
close.

But numbers are not enough.

Every number is created by a physical process, a set of decisions, a
flow of work, a pattern of behaviour and a level of resourcing.

To plan a change in a number is to plan a change in what people
physically do.

If goals become larger, capacity, tools, skills, priorities and
support processes must be examined. If a metric is weak, the manager
must understand the lever that moves it. If a report shows a trend, the
manager must connect that trend to reality.

Numbers should be on your fingertips.

But the levers should be in your hands.

That is the difference between knowing the score and managing the
game.