A management dashboard for small businesses: Make the next decision clearer

A management dashboard helps your business when it makes the next decision easier to recognise. Many numbers on one page do not provide that benefit by themselves. If you still have to call several people to understand what the overview means, the connection between the number, the case and the responsibility may be missing. A useful management overview makes that connection understandable and reduces unnecessary searching and coordination.

For a small business, a bounded question is often enough initially: where is work getting stuck, and what must we decide this week? That produces an overview which supports management without reproducing every piece of business information. This article explains how to select relevant measures, interpret events and use them in a short weekly discussion. All figures and people in the example are fictional. The suggested method does not claim that these reports are automatically available in Cockpit.

Start with your daily and weekly decisions

Write down the decisions that recur. You may need to decide each day who takes responsibility for an open case. Once a week, you may decide whether additional time is required for preparing quotations. Both concern the flow of work, but they require different information. Daily allocation needs the individual case and a responsible person. Weekly planning asks whether a recurring workload is building up.

Connect every question to a possible action. If a number rises, you might redistribute work, obtain missing information or change the processing order. If no useful action is conceivable, the measure does not need to appear in the first management overview. It may still be useful elsewhere. You are selecting the limited view that prepares the next discussion and directs the team’s attention, rather than deciding which data may exist anywhere in the company.

Distinguish attention from unnecessary intervention. One unusual case may need immediate clarification while a small change in a total initially calls for observation. The deciding factors are the business consequence and reliability of the information. Do not establish thresholds simply because a dashboard colour seems to require them. A signal needs a reason connected to your commitments, capacity and working practices.

Explore Cockpit as an overview of metrics and events and get started through the module page.

Select a few measures with an unambiguous meaning

A useful measure can be explained in one sentence. “Open cases on Friday after processing finishes” describes a stock at a particular moment. “New cases received from Monday to Friday” describes additions during a period. The two numbers serve different purposes. If you present them without that distinction, the team may misunderstand a development even when both values have been calculated correctly.

Record what each selected measure includes and excludes. Does a case waiting for customer information still count as open? When is a case completed? Are reopened cases tracked separately? You do not need a lengthy dictionary. A short shared definition is enough if it resolves the important distinctions. Changes to that definition must remain visible because they can affect subsequent comparisons and the meaning of a trend.

Choose a data cutoff that suits the discussion. A weekly value is difficult to interpret if part of the team has not yet updated its records. Missing or late entries should be identifiable. An empty display does not automatically mean that no cases exist. Before treating a fall as improvement, establish whether the reporting period and recording method are comparable with the previous week.

Work through a complete weekly overview

For the example, a small service business maintains its own overview of quotation preparation. Twelve cases are open at the start of the week. Eighteen arrive during the week and twenty are completed. In this artificial example there are no reopened cases, duplicate counts or other additions and removals. Ten remain at the end: twelve plus eighteen minus twenty. This is a manually assembled working overview, rather than a promised Cockpit display.

The ten open cases are examined more closely for the discussion. Four await information from prospects. Six still require internal work. Two of those six internal cases have passed a promised date for the next processing step. The two are already included in the six and must not be added to the ten again. This distinction prevents the same work from appearing several times as additional pressure on the team.

The open stock has fallen from twelve to ten. That does not yet mean everything is going well. The twenty completed cases may include older work, while two current commitments were missed. Dividing twenty completions by eighteen new cases and calling it the success rate for incoming work would also be wrong. Additions and completions do not necessarily belong to the same group. For weekly planning, the clean stock calculation and relevant open cases provide a useful starting point.

Interpret events through their business consequence

A measure draws attention to an area. An individual event often explains why attention is needed there. In the example, a missed processing date matters because a prospect is waiting for an agreed response. The decision needs more than the number two: what is missing, who can clarify it and when can a realistic next answer be prepared? That connection turns a signal into work someone can actually direct.

Avoid jumping to causes. Six internally open cases do not prove that a particular employee works too slowly. Technical information may be missing, the service scope may need a decision, or another priority may have been deliberately brought forward. Ask about the obstacle in the actual case. This keeps the discussion factual and produces an action that helps the work progress, instead of merely distributing pressure among the participants.

Finally, distinguish a recurring cause from an individual exception. If the same missing handover step appears repeatedly, a small process change may help. A one-off question may only need an answer. That distinction protects management time. Not every event justifies a new rule, and a recurring disruption should not indefinitely be treated as an accidental exception with no implication for the workflow.

A complete example of the weekly management discussion

For the fictional business, we set a twenty-minute conversation between owner Mara and team leader Jonas. This duration is a chosen working assumption, not a product promise. During the first four minutes, Jonas confirms the reporting period and data cutoff. He explains the twelve initial cases, eighteen additions and twenty completions leaving ten open. Mara asks: “Are the four waiting cases included in the ten?” Jonas confirms. They establish a shared starting point before discussing actions.

The next eight minutes focus on the two missed internal commitments. Jonas explains that one needs a decision about service scope and the other lacks a technical answer. Mara takes responsibility for the scope decision by Tuesday noon. Jonas will clarify the technical question with the relevant colleague by Wednesday afternoon. For both cases, they also establish who will communicate the next reliable update to the prospect. They do not invent a new completion date before its basis is clear.

During the following five minutes, they consider the remaining work. They do not allocate blanket extra processing time to the four cases awaiting customer information. Jonas will instead check whether the requested details and agreed response route are clear. He allocates an existing work period in the coming week to the other four internally open cases. Hiring another person or acquiring more enquiries would not be justified by these few numbers alone. The measure follows the identified bottleneck.

The final three minutes confirm the agreements. Mara repeats her scope decision and deadline; Jonas repeats the technical clarification and check of the waiting cases. They agree to begin the next weekly discussion by reviewing these commitments. The full twenty minutes are four plus eight plus five plus three. The conversation ends with named actions and owners. It does not create an additional account of every completed case, since that would not help the decisions at hand.

Record decisions so the next meeting can continue from them

A useful decision note need not be long. One entry reads: “Mara will decide the unresolved service scope in the relevant quotation by Tuesday noon; Jonas can then continue preparation.” A second records the technical clarification by Wednesday afternoon. A third says that Jonas will check the specific information request in the four waiting cases. Each entry connects an action to a person and an understandable reason.

At the next discussion, ask more than whether a box was ticked. Did the decision move the case forward? If the scope question has been answered but another prerequisite now holds up the quotation, describe that new situation precisely. This avoids treating a completed subtask as the final business result. The overview stays connected to work that should become usable for a customer or colleague.

Keep observations without actions as observations. A falling backlog does not necessarily need its own assignment. A change that is not yet adequately understood may first need investigation before anyone implements a solution. This restraint does not make the weekly conversation less accountable. It gives the few agreed actions more weight and prevents them from disappearing among tasks created merely to make the meeting look productive.

Use Cockpit for the supported overview and appropriate interpretation

According to the webRichtung cockpit module page, Cockpit brings together metrics and events from your platform use. It reads rather than intervening itself. That role fits a management routine: you gain visibility into what happened, then decide which action belongs in the responsible area of work. The overview takes over neither the owner’s responsibility nor the expert judgement needed to clarify a case.

The figures selected in this article form a methodological example. Check which particular information Cockpit actually provides for your use and which details must come from the relevant working area. Do not assume a desired metric exists in the product simply because your meeting needs it. A sound first routine needs a traceable basis, even when every question cannot yet be answered on the same screen.

Avoid duplicate maintenance without a clear purpose. Where a reliable status already exists in the relevant case, a supplementary meeting note should capture the decision. A second complete case list can drift away from the original source. Establish where the working status is maintained and which overview merely summarises it for management. That keeps clear where a change is actually made and where it should subsequently be checked.

Start small and assess the benefit of the routine

Begin with one area whose decisions regularly take your time. Establish a fixed period, a few understandable figures and a person responsible for interpretation. Ground the discussion in actual cases. You will learn which information helps and which only creates more discussion. Add further measures when they support a new relevant decision and their basis is reliable, rather than filling spare space in an overview.

After several meetings, assess whether the routine serves its purpose. Are commitments followed more clearly? Do missing responsibilities become visible earlier? Does the owner have to gather less information before deciding? These observations connect directly to the goal. If you compare time spent, include preparation and updating afterwards. A shorter meeting is not a success if it creates substantially more work elsewhere.

On the Cockpit module page, you can explore the intended overview and create your account through the existing start process. Bring your first management question: which decision would I like to make on a better basis next week? That keeps adoption connected to a concrete business need. The appropriate overview then supports the short routine in which information leads to an action somebody owns.

Get started with Cockpit and focus on the next important decision in your business.