What Managers Do: Turn Problems into Action and Check the Results

A manager’s decision has little effect if nobody knows what should happen next. Choosing a new procedure, approving a project or asking a team to improve a service is only part of the work. Someone must turn the intention into a clear task, provide the means to carry it out and check what changed.

Managing an organization means connecting those steps. The challenge is not simply to stay busy with individual problems, but to make sure the work advances the organization’s purpose.

A task board photographed on 14 December 2010, showing work at different stages. Photo: Logan Ingalls, CC BY 2.0. Display size adjusted; no crop.

Define the issue before prescribing the solution

“Customer service is poor” expresses concern but does not yet identify a manageable problem. Are replies late, orders inaccurate or promised dates unrealistic? Different causes require different responses.

Consider an illustrative repair workshop receiving complaints about missed collection dates. Before adding staff or replacing its booking system, the manager could compare promised dates with actual completion dates and ask employees where work waits. The issue may involve parts, scheduling, communication or a combination of them.

The purpose of that inquiry is to make the next action specific. It also gives employees a chance to describe constraints that may not be visible in a summary report.

Set priorities without neglecting future problems

An immediate breakdown may need attention before a long-term improvement project. That does not make the improvement unimportant. Repeatedly postponing prevention can leave a team dealing with the same disruption every week.

For each issue, ask what happens if action is delayed, who is affected and what resources a response requires. Decide which matters need immediate attention, which need scheduled work and which can be handled by someone with the relevant authority and expertise.

Delegation should include an expected outcome and a way to raise obstacles. Passing a task to someone without the information, time or permission to complete it simply moves the problem.

Turn an intention into an action

In the workshop example, “communicate better” is too vague to implement consistently. A more concrete test might be to confirm parts availability before promising a collection date and notify customers when a delay becomes known.

That proposal needs an owner, a start date and a review point. It also needs answers to practical questions: who checks parts, who updates the customer and where is the status recorded? A visible task board can help people locate work in progress, but a card moving across a board is not itself evidence that the customer’s problem has been solved.

Test the change and learn from it

The American Society for Quality describes the Plan–Do–Check–Act cycle as a repeated approach to change: plan an improvement, test it on a small scale, examine the results and act on what was learned.

Applied to this example, the workshop could try the revised confirmation procedure for a defined set of bookings. Before starting, the team would decide what to observe: missed collection dates, accuracy of customer updates and any additional administrative burden.

At the review, the question is whether the change helped and what still needs attention. A successful test may justify wider use; an unsuccessful one provides a reason to reconsider the explanation or the procedure. The example illustrates the method rather than promising a particular outcome.

Measure progress with enough context

OpenStax’s account of management control connects monitoring and evaluation with corrective action. Its discussion also emphasizes accurate, timely information and the practical fit of the control system.

A workshop might reduce the number of late collections by promising much longer waits. That would improve one measure while potentially making the service less useful. Review the measure alongside the outcome it is meant to represent, rather than assuming that a better number settles the question.

People doing the work need feedback they can use. If a deadline is missed, establish what happened and which part of the arrangement should change, instead of treating every shortfall as proof of poor effort.

Connect decisions, responsibility and follow-through

For the choice between routine rules, analysis and intuition, see Ways of Decision-Making. For the distinction between governance and daily management, see Organization and Management.

A useful management review leaves the team able to explain the issue, the action being tested, who is responsible and when the result will be examined. Those connections turn a decision into work that can be carried out, questioned and improved.