Tag: Small Business Analytics

  • How Many Charts Should a Dashboard Have?

    There is no fixed number. The practical limit is the screen: a dashboard should fit on one laptop screen without scrolling and tell someone within a few seconds whether the business is on track. That usually means a row of number cards for your core metrics across the top, a few charts beneath them showing the trends behind those numbers, and a small breakdown or two at the bottom. Anything that doesn’t fit belongs on a second page.

    The better question is what each chart is for. A chart earns its place when someone looks at it regularly to make a decision and needs the shape of the data, not just the number. Start from those questions and the count takes care of itself.


    Why Does a Dashboard Need a Limit at All?

    A dashboard exists to be read quickly. Stephen Few, whose Information Dashboard Design is widely cited on the subject, defines a dashboard as the most important information needed to meet one or more objectives, arranged on a single screen so it can be monitored at a glance. Both parts of that definition limit the chart count: “most important” and “at a glance.”

    Every chart you add competes with the others for the reader’s attention. With three charts, a line that turns sharply down stands out. With fifteen, it looks like one more shape among many, and the reader has to search for it. The screen also runs out of room. Charts shrunk to fit lose their labels and axes, and a chart nobody can read hasn’t been included in any useful sense.

    Scrolling is the clearest warning sign. Once the dashboard runs below the fold, the reader can no longer see the headline numbers and the charts behind them at the same time. Anything below the fold is easy to miss.


    How Do You Decide How Many Charts You Need?

    Count Cards and Charts Separately

    A card shows one number: this month’s revenue, cash on hand, jobs completed. Add the target and last period’s value beside it, and a card answers “are we on track?” in a single glance.

    A chart shows a shape: how a number moved over time, or how it splits across categories. It answers “since when?” or “where is it concentrated?” A chart can show when a change started and which part of the business it sits in. Working out why it happened still takes someone who knows the business.

    Most of the confusion about chart count comes from treating these as the same thing. The cards carry your core metrics. My rule of thumb, depending on the business, is four to seven metrics, and no vanity metrics; each one has to move the needle. How Many KPIs Should a Small Business Track? covers how to choose them. Charts are a separate decision, and there should usually be fewer of them than cards.

    Give Each Chart a Question

    For every chart you’re considering, write the question it answers and who asks it. For example:

    • Is revenue running ahead of or behind last year, month by month?
    • Is weekly capacity keeping up with booked work?
    • Which customers owe us money, and how overdue is it?
    • Where are deals stalling in the pipeline?

    If you can’t write the question, the chart probably doesn’t belong on the main screen. If two charts answer the same question, keep the clearer one. If the answer is fully captured by a single number, use a card instead.

    Let the Screen Set the Ceiling

    Once you have a list of charts with real questions behind them, lay them out on the actual screen your team uses. On a typical laptop, a row of cards plus two rows of two or three charts at a readable size is often about as much as fits. Treat that as a starting estimate, not a rule. The real capacity depends on the viewport and browser zoom, how much room filters and labels take, and how complex each chart is. A simple line chart needs less room than a labeled breakdown. A larger monitor in a shared office fits more; a phone fits much less. Check on the screen your team actually uses.

    If the charts don’t fit, don’t shrink them. Move the lower-priority ones to a second page.


    What Should Go Where on the Screen?

    A simple three-part layout works for most business dashboards. Put the most important information at the top, where it is visible the moment the page opens.

    Top: The Headline Numbers

    A single row of cards across the top of the screen. Each card shows the current value, the target, and the change from the last period. This row should answer the main question, whether the business is on track, before the reader looks at anything else.

    Keep the cards in a consistent order, such as money first, then operations, then customers. If a card is out of range, color can flag it, but keep the rest of the screen in neutral tones so the color means something.

    Middle: The Trends

    The largest area goes to the charts that show how the headline numbers have moved over time. A typical small-business set might include:

    • A line chart of revenue or cash over the last twelve months, against target or last year.
    • A bar chart of weekly throughput: jobs completed, hours billed, or orders shipped.

    Each trend chart should connect to a card above it. If a trend chart doesn’t relate to any headline number, ask whether it belongs on this page.

    Bottom: The Breakdowns

    The bottom holds charts that split a number into parts, so the reader can see which part of the business a change sits in. Examples include receivables by age, sales by product line, or deals by pipeline stage. These are usually the first candidates for a second page if space runs short.


    Which Chart Types Work Best?

    A small set of chart types handles most everyday business questions. Using the same few types across the dashboard also makes it faster to read, because nobody has to work out how each chart works.

    Line Charts for Change Over Time

    Use a line chart when the question is about direction: up, down, flat, seasonal. Months or weeks run left to right. Two lines, such as this year and last year, are easy to compare. Each line you add after that makes the chart harder to read.

    Column Charts for Comparing Periods or Groups

    Vertical bars work well for comparing a small number of periods or categories, such as sales by month or jobs by team. Start the value axis at zero, because bar length is what the reader compares.

    Horizontal Bar Charts for Rankings

    When the categories have long names, or you want them ranked, turn the bars sideways. Top customers by revenue, overdue invoices by client, and product lines by margin all read well this way. Sort from largest to smallest.

    Sparklines Inside Cards

    A sparkline is a small, word-sized line chart without axes, a term introduced by Edward Tufte. Placed inside a card, it shows the recent direction of a number without taking up a chart’s worth of space. Sparklines are one of the easiest ways to show more trend information without adding charts.

    Tables, Sparingly

    A short table works for a specific list someone needs to act on, such as the five most overdue invoices. A long table of raw data belongs elsewhere. 7 Dashboard Mistakes Small Businesses Make covers raw tables on the main screen along with other common layout problems.


    Which Charts Should You Avoid?

    Some chart types take up a lot of space or make comparisons harder than they need to be.

    • Gauges and speedometer dials. A dial uses a large area to show one value. A card with the value, target, and prior period shows more in less room.
    • Pie charts with many slices. Comparing angles is harder than comparing lengths. A pie with two or three slices can work; beyond that, a sorted horizontal bar chart is easier to read.
    • 3D effects. Perspective distorts the size of bars and slices, so the chart misrepresents the numbers it shows.
    • Decoration. Heavy gridlines, background images, shadows, and gradient fills add nothing to the data. Tufte called this kind of non-data ink “chartjunk.” Remove it, and the numbers get easier to see.
    • Novel chart types for their own sake. Radar charts, bubble charts, and other less familiar types have legitimate uses, but on a dashboard for a general business audience, they usually take longer to read than a bar or line chart showing the same thing.

    A chart doesn’t need to look impressive. It needs to be understood quickly by the person who uses it.


    When Should a Dashboard Have More Than One Page?

    When the charts that pass the question test don’t fit on one screen, split the dashboard by audience or purpose instead of cramming everything in.

    A common structure for a small business:

    1. Overview. The headline cards and the few trend charts the owner or leadership team reviews. This page answers “are we on track?”
    2. Operations. Capacity, throughput, scheduling, and quality detail for the people running daily work.
    3. Finance. Receivables, cash timing, margin by product or service line, and the detail behind the money cards.

    Each page follows the same layout: cards at the top, trends in the middle, breakdowns at the bottom. Link the overview cards to the page with their detail, if your tool supports it. Looker Studio, Power BI, and Tableau all let you build more than one page or dashboard, and a spreadsheet can use separate tabs.

    The overview should stay stable. When someone asks for a new chart, the default home is a detail page. It moves to the overview only if it answers a question leadership asks regularly, and then something else should come off.


    How Do You Cut a Cluttered Dashboard Down?

    If you’re starting with a screen that already has fifteen charts:

    1. List every chart and card. Write the question each one answers and who uses it.
    2. Mark each one. Keep on the overview, move to a detail page, or delete. Duplicates and charts with no clear question are the first to go.
    3. Turn single numbers into cards. A chart whose only purpose is showing the current value can become a card, often with a sparkline.
    4. Rebuild the overview using the three-part layout, and check that it fits without scrolling on the screen your team actually uses.
    5. Ask the people who use it. Show the new version to two or three regular readers and ask what they’d look for first. If they can’t find it quickly, adjust.

    For a full renovation process that also covers data accuracy and ownership, see How to Improve a Business Dashboard You Already Have.


    Dashboard Chart Checklist

    • The overview fits on one screen without scrolling.
    • The top row holds four to seven cards, each with a target and prior-period comparison.
    • Every chart answers a written question that someone asks regularly.
    • No two charts answer the same question.
    • Trend charts relate to headline numbers.
    • Lines, columns, horizontal bars, sparklines, and short tables do most of the work; any other chart type is there for a reason.
    • No gauges, 3D effects, or decoration.
    • Anything that doesn’t fit lives on a clearly labeled detail page.

    Frequently Asked Questions

    Is there a standard maximum number of charts?
    No. Any fixed number would ignore the screen size, the audience, and how often the dashboard is used. The one-screen test and the question test are more reliable than a count.

    Should a spreadsheet scorecard have charts?
    Not necessarily. A monthly scorecard in rows and columns, with a status color for each metric, can do the job without any charts. How to Build a Monthly KPI Scorecard shows how to build one. Add a trend chart only if the team keeps asking how a number has moved.

    What about mobile?
    A phone screen fits far less, so don’t just shrink the desktop layout. If people will check the dashboard on their phones, build a mobile layout: the cards first, stacked vertically, then the one or two charts that matter most. On a phone, scrolling down is expected. Order the view so the most important items come first. Power BI and Tableau both let you design a separate phone layout.

    Does the tool matter?
    Less than the layout. Google Sheets, Excel, Looker Studio, Power BI, and Tableau can all produce a clean one-screen dashboard. A cluttered dashboard stays cluttered in any tool.

  • Why Your Business Numbers Don’t Match Across Systems

    Your payment processor, your bank, and your accounting software each record a different moment in the life of a sale. The processor records the charge when the customer pays. The bank records a deposit days later, after fees and refunds come out and several sales are batched together. Your accounting software records revenue according to your accounting method, which may be when the revenue is earned rather than when the cash arrives. In most cases, three different numbers mean three different measurements, and a short monthly reconciliation shows how they connect.

    I’ve seen this plenty in operating businesses. An owner compares last month’s sales across two or three systems, gets different totals, and starts wondering whether the bookkeeper made a mistake or whether money is missing. Usually the numbers are fine. Nobody has written down how they relate to each other.


    Why Does Each System Show a Different Number?

    Each system sits at a different step of the same transaction. Follow one sale through all of them, and the differences stop looking mysterious.

    A Sample Scenario: A client pays a $1,000 invoice by card on a Friday.

    1. Accounting software. The invoice was entered when the work was billed, perhaps the previous month. Entering the invoice is not what created the revenue. Under accrual accounting, the $1,000 counted as revenue when it was earned, typically when the work was completed, under the business’s accounting policy. That can fall in a different month from both the invoice and the payment.
    2. Payment processor. The charge is approved on Friday and shows $1,000 in gross sales.
    3. Processor balance. The processor takes its fee. At Stripe’s standard US price for domestic cards, 2.9% plus 30 cents per successful charge, that is $29.30, leaving $970.70 in the processor balance.
    4. Bank account. The money is not available the moment the card is approved. On Stripe’s standard two-business-day timing for US accounts, Friday’s sale becomes available for payout the following Tuesday. When it actually lands in the bank is a separate question, set by your payout schedule and your bank’s own processing, and it arrives batched with other sales in a single payout.
    5. Back in accounting. Someone matches that combined deposit to the invoices it paid and records the $29.30 as a processing expense.

    The same $1,000 now appears as revenue in one month, a $1,000 charge on a Friday, and part of a larger bank deposit some days later. All three are correct.

    The Business Data You Already Have describes what each of these records can tell you on its own. This article covers how to connect them.


    What Are the Four Reasons the Numbers Disagree?

    1. Timing

    Cash lags sales. Funds are not available for payout until the processor’s settlement timing has run; payouts then follow whatever schedule the account is on, and weekend or holiday payouts move to the next business day. Stripe says a new account’s first payout typically takes 7 to 14 days, and later payouts follow a schedule the business can set to daily, weekly, or monthly.

    The lag matters most at month end. Sales on the last two days of March may be in the processor’s March report but in the bank’s April statement. Sales from the end of February land in March deposits. The two months never contain exactly the same transactions.

    2. Fees, Refunds, and Disputes

    Processors usually pay out the net amount. Fees, refunds, and chargebacks come out of the balance before the money moves, so the deposit is smaller than the sales that produced it.

    The problem gets worse when the books record only the deposit. If $970.70 is booked as revenue, sales look lower than they were and the $29.30 processing cost disappears from the expense lines. The usual setup is to record the full sale and the fee separately. Confirm how your bookkeeper handles it.

    3. Cash Versus Accrual

    Under cash accounting, income counts when it is actually or constructively received. Under accrual accounting, it generally counts when it is earned, typically when the work is done or the goods are delivered, regardless of when the customer pays. A business on accrual accounting can show strong March revenue with little March cash, because the invoices are still open.

    Multi-month contracts, deposits, retainers, and milestone billing make this more complicated. Revenue recognition rules for those arrangements are a question for your CPA. Confirm your policy with them before you decide which revenue number a dashboard should show.

    4. Different Definitions

    The same word can mean different things to different teams. Take a signed two-year service contract. Sales may report the whole contract value as a win. Finance may record most of it as deferred revenue, to be recognized month by month. Operations may call the remaining work backlog. Each number is legitimate. They answer different questions, and a report that uses one without saying which will contradict a report that uses another.


    What Does a Monthly Reconciliation Look Like?

    A service business reviews March and finds three totals:

    SystemMarch totalWhat it measures
    Accounting software$52,700.00Revenue recognized in March: $48,200 paid by card plus $4,500 invoiced and still unpaid
    Payment processor$48,200.00Gross card charges in March
    Bank account$45,441.80Processor payouts that reached the bank in March

    The gap between accounting and the processor is the $4,500 in open invoices. It will turn into cash when those clients pay.

    The gap between the processor and the bank takes a few more lines:

    Bridge lineAmount
    Gross card charges$48,200.00
    Less refunds−$600.00
    Less processing fees−$1,697.80
    Net processor activity$45,902.20
    Plus balance not yet paid out on March 1 (late-February sales)+$2,950.00
    Less balance not yet paid out on March 31 (late-March sales)−$3,410.40
    Other balance activity (disputes, reserves, adjustments)$0.00
    Expected bank deposits$45,441.80

    The expected figure matches the bank total, so the month ties out. If the bank had shown $44,900, the unexplained $541.80 would be the thing to investigate.

    The bridge works because it follows the processor’s balance: what was waiting to be paid out at the start, plus the month’s net activity, less what was still waiting at the end, equals what was paid out. This example is deliberately simplified, which is why the “other balance activity” line is zero. A real month can also carry disputes and dispute fees, reserves or holds on the balance, failed or reversed payouts, taxes withheld, and account adjustments, and any of those changes what reaches the bank. Processors such as Stripe provide balance and payout reports that show these items, and each one earns its own line in the bridge.


    How Do You Stop Arguing About Which Number Is Right?

    Decide in advance which system answers which question, and write it down.

    QuestionSystem of record
    How much cash do we have?Bank
    How much revenue did we earn?Accounting software, under the policy your CPA confirmed
    How much did customers pay us, and how?Payment processor or POS
    How much work have we sold?CRM, booking system, or sales tracker

    Once each metric has a home, a dashboard can label the source beside every number: “Revenue (accounting, accrual)” or “Cash (bank, as of the 5th).” People stop comparing numbers that were never meant to match.

    This matters beyond the finance office. When two managers bring different revenue figures to the same meeting, the meeting turns into an argument about the data. After a few of those, people stop trusting the dashboard and go back to their own spreadsheets. Why Nobody Looks at Your Dashboard covers that problem in more detail.


    How Do You Reconcile the Systems Each Month?

    Step 1: Assign a System of Record to Each Metric

    Use the table above as a starting point. Keep the list short and share it with anyone who builds or reads reports.

    Step 2: Record Sales and Fees Separately

    Ask your bookkeeper whether card sales are recorded at the gross amount with fees, refunds, and chargebacks in their own accounts. If the books record only net deposits, you cannot see what processing costs you, and revenue is unlikely to tie to the processor’s report.

    Step 3: Reconcile on a Fixed Schedule

    Pick a day each month, after the books close, to match processor payouts to bank deposits. Use the processor’s payout report, which lists which transactions went into each deposit. Reconcile the same way every month so differences are easy to spot.

    Step 4: Keep a Simple Bridge

    Build the bridge from the March example in a spreadsheet: gross sales, refunds, fees, any other balance activity, the unpaid balance at the start and end of the month, and the bank deposits. Anything left over after those lines is what needs investigating. Once the monthly numbers tie out, they can feed a scorecard; How to Build a Monthly KPI Scorecard shows how to set one up.


    Is It a Timing Difference or a Real Problem?

    Work through these checks before assuming anything is wrong:

    • Does the gap match the balance waiting to be paid out? Compare it with the processor’s pending or in-transit amount at month-end.
    • Does the gap match fees? Divide last month’s total fees by gross charges to get your own fee rate, then see whether the difference is close to that share of sales.
    • Are refunds or disputes involved? Check the processor for refunds, chargebacks, and any reserve or hold on your balance.
    • Are both reports covering the same dates? Confirm the start and end dates, and whether each system uses the same time zone for its cutoff.
    • Is anything counted in one report and not the other? Look for open invoices, cash or check payments, sales tax, tips, or deposits for future work.

    If a difference remains after these checks, it deserves a closer look. Duplicate entries, a payout that never arrived, a sale recorded in the wrong period, and a missing connection between systems are all possible causes. Bring the bridge to your bookkeeper or accountant. It shows exactly how much is unexplained, which makes the conversation much shorter.


    Frequently Asked Questions

    Why doesn’t my Stripe total match my bank deposit?
    Stripe pays out your balance after fees and refunds come out, and it groups transactions into payouts on a schedule. A single deposit usually covers several days of sales, and the amount is net of costs.

    Should my systems match every day?
    No. Daily totals will almost always differ because of settlement timing. Monthly totals should tie out once you account for fees, refunds, and the balance still waiting to be paid out.

    Do I need an accountant to do this?
    You can build and review the bridge yourself. Questions about how revenue should be recognized, especially for contracts, deposits, or milestone billing, belong with your CPA.

    Can software do the reconciliation for me?
    Accounting tools such as QuickBooks and Xero can import bank transactions and suggest matches. Someone still needs to review exceptions and decide which system answers which question.


    Where to Start

    List every system that records money coming in, who has access, and what each one exports. The Small Business Data Audit Checklist walks through that inventory. With the list in hand, pick last month, pull the three totals, and build the bridge once. After the first month, the process gets much faster.

  • How to Build a Monthly KPI Scorecard

    Build it in the spreadsheet you already use. Put four to seven metrics on a Scorecard tab that shows, for the current month, the target, the actual, the variance, and a green, yellow, or red status. Keep the twelve-month history on a Trend tab, calculations on a Data tab, and each raw export on its own import tab. Start targets from your own recent history, and update the sheet the same way every month after the books close.

    That is the whole design. Most of the work is in the decisions behind each cell: which metrics earn a row, what counts as on target, and how the numbers get in without someone retyping them.


    What a Monthly Scorecard Is For

    A scorecard answers one question each month: is the business on track, and if not, where? It is not your accounting system and it is not a report. It is a single view that someone can read in a minute and act on.

    That purpose sets the rules:

    • Four to seven metrics. My rule of thumb, depending on the business, is four to seven, and no vanity metrics. Each one has to move the needle: when it changes, someone makes a decision. How Many KPIs Should a Small Business Track? covers how to choose them.
    • One screen. The Scorecard tab fits on a laptop screen without scrolling sideways. If it doesn’t, you have too many metrics or too many columns. The full history lives on another tab.
    • Metrics in rows, in the same order on every tab. Row 6 is the same metric on the Scorecard and the Trend tab, which keeps formulas simple to copy.
    • Every number has a comparison. A figure with no target beside it doesn’t tell anyone whether to act.

    Use Google Sheets if your business runs on Google Workspace, and Excel if it runs on Microsoft 365. My view is that a small business should stay with the tools it already pays for as long as they do the job, and a monthly scorecard is well within what either can do.


    Step 1: Choose the Rows

    Group the metrics so the sheet reads in a consistent order. A practical split for most small businesses:

    • Money (two or three rows): revenue, gross margin, operating cash flow.
    • Operations or capacity (one to three rows): billable utilization for a service firm, first-pass yield for a shop, jobs completed for a trade business.
    • Customers and pipeline (one or two rows): qualified pipeline value, on-time delivery, customer retention.

    Pick from these, don’t take all of them. If you already track seven metrics and want an eighth, one of the seven should go. For service-business examples with formulas, see KPIs for a Small Professional Services Firm.

    For each metric, write down four things before you build anything:

    • Definition, including where the number comes from.
    • Unit: dollars, percent, days, or count.
    • Direction: whether higher or lower is better. Revenue is better high. Days sales outstanding is better low. The sheet needs to know the difference, or it will color a collections problem green.
    • Type: a flow, a ratio, or a point-in-time figure. This decides how year-to-date is calculated in Step 3.

    Step 2: Lay Out the Tabs

    Build the workbook in layers, so the tab people read never touches raw data.

    Scorecard tab. This is what people read. A header block at the top holds the company name, the reporting month, the date last updated, and who updated it. Put the reporting month in its own cell (say, B2), because the formulas will use it. Below that, each metric gets one row:

    ColumnContents
    AMetric name
    BOwner
    CUnit ($, %, days, count)
    DDirection (higher or lower is better)
    EThis month’s target
    FThis month’s actual
    GVariance
    HStatus (green, yellow, red)
    IYear-to-date actual
    JYear-to-date target

    Ten columns fit on one screen. If a comparison with the same month last year matters in your business, add it after F, as long as the tab still fits.

    Trend tab. The same metric rows, with January through December in columns C through N and the month names in row 5. This is where people look when they want to know whether this month is a blip or a trend. Below the metric rows, keep the components that ratios need, such as monthly gross profit and revenue, or billable and available hours.

    Data tab. Calculations only. Each metric’s monthly value is calculated here from the import tabs, in a labeled block. Nobody pastes anything onto this tab.

    Import tabs. One tab per source: accounting, CRM, time tracking. Each month, the owner clears the tab and pastes that source’s standard export into cell A1. Nothing is typed or calculated on an import tab, so a longer or shorter export can’t overwrite a formula. On the Data tab, refer to whole columns or use lookups by label, so the calculations still work when the export has more rows than last month.


    Step 3: Add the Formulas

    These formulas behave the same way in Google Sheets and Excel. The examples use row 6.

    Pull this month’s actual. Rather than retyping, have column F on the Scorecard look up the month named in B2 from the Trend tab. The month in B2 has to be spelled exactly as it is in the Trend headers. With the month names in C5:N5:

    =INDEX(Trend!C6:N6, 1, MATCH($B$2, Trend!$C$5:$N$5, 0))

    The 1 tells INDEX to stay in the first (and only) row of the range, and MATCH supplies the column. Change B2 next month and every row updates.

    Calculate the variance. For dollars and counts, use the percentage difference from target:

    =(F6-E6)/E6

    For metrics that are already percentages, such as gross margin or utilization, use the difference in points instead:

    =F6-E6

    The two give different impressions. A margin target of 42% against an actual of 38.5% is 3.5 points below target, which is also 8.3% below it. “3.5 points” is the figure most people understand when they read a margin. Pick one convention per metric, label it, and keep it.

    Flip the sign for lower-is-better metrics. If D6 says “lower,” multiply the variance by −1 so that a negative number always means worse:

    =IF(D6="lower", -1, 1) * (F6-E6)/E6

    Handle zero targets. A percentage variance divides by the target, so a target of zero, such as zero overdue invoices or zero safety incidents, returns an error. Track those metrics in units instead: the variance is simply the count. Give that row its own status rule, for example =IF(F6="", "No data", IF(F6>0, "Red", "Green")), in place of the band formula in Step 5. Give “No data” a neutral style so a missing actual is never shown as Green.

    Calculate year-to-date by metric type. Averaging twelve monthly figures is right for almost nothing. Use the type you wrote down in Step 1:

    • For flows such as revenue, jobs completed, or operating cash flow, sum the months.
    • For ratios such as gross margin, utilization, or on-time delivery, recompute them from the summed components. Year-to-date margin is total gross profit divided by total revenue; year-to-date utilization is total billable hours divided by total available hours.
    • Point-in-time figures such as pipeline value, days sales outstanding, or cash balance: use the latest month-end value, or another method you define and write down.

    Retention depends on how you define it, so write the year-to-date rule into its definition. The year-to-date target follows the same rule as the actual.

    The ratio difference is real. Suppose January brings in $50,000 at a 40% margin ($20,000 gross profit) and February brings in $100,000 at 30% ($30,000). The average of the two percentages is 35%. The actual year-to-date margin is $50,000 ÷ $150,000, or 33.3%, because February’s larger month counts for more.


    Step 4: Set Targets, Starting From Your Own History

    A target picked because it sounds good gets ignored after the first miss. Start from what the business has actually done, then decide what it should do.

    1. Find a baseline. The trailing three-month average is a reasonable starting point, because recent months reflect your current staff, prices, and customers. If your business is seasonal, look at the same month last year as well.
    2. Turn the baseline into a target. Check it against your budget, your capacity, commitments you’ve already made, the season, and any improvement you’re planning. A baseline built from weak months will simply repeat them if you adopt it unchanged.
    3. Write down the reason for any difference between baseline and target, so the target can be explained later.
    4. Round to a number people can remember.

    Here is an example, not a client case. A business had revenue of $78,400 in June, $81,200 in July, and $76,900 in August. The three-month baseline is about $78,800. September is usually similar to the summer months; nothing unusual is planned, and the budget agrees, so the target is set at $79,000. September comes in at $72,600, which is $6,400 short, or 8.1% below target.

    Whether 8.1% is a problem depends on the band you set.


    Step 5: Set Tolerance Bands

    A tolerance band says how far a metric can move before anyone needs to act. Without one, every small dip gets discussed, and the meetings lose their point.

    I set bands from the business’s own history. I look at how much each metric actually moved over the last six to twelve months. Movement inside that normal range I treat as noise. Movement outside it means something changed. One caution: several months drifting the same way inside the band is still a trend, which is why the Trend tab matters.

    I also set them metric by metric, because metrics don’t behave the same way. A 5% miss on gross margin can be serious, while a 5% dip in inquiries may be an ordinary month.

    If you don’t have enough history yet, you still need a placeholder. There is no standard band. As a rough starting point, not a hard rule, some businesses could begin with something like:

    • Green: within 5% of target, or better.
    • Yellow: 5% to 15% worse than target.
    • Red: more than 15% worse than target.

    Replace it with bands from your own data once you have a few months. On that sample starting point, the September revenue example above (8.1% below) is yellow. A days sales outstanding target of 45 days against an actual of 52 is 15.6% worse, so it’s red.

    To fill the Status column, add a formula that returns a word:

    =IF(G6>=-0.05, "Green", IF(G6>=-0.15, "Yellow", "Red"))

    Then add three conditional formatting rules to column H: text is exactly “Green,” “Yellow,” or “Red.” Use the word as well as the color so the status still reads correctly in a printout or for anyone who has trouble telling the colors apart. Keep the rest of the sheet in neutral tones so the color means something when it appears.

    For percentage metrics tracked in points, the formula compares against point thresholds instead, for example −1 and −3 points. Record the band for each metric in a note on the Data tab so nobody has to guess later why margin turned red at a smaller miss than revenue did.

    A red status should trigger a short note from the metric’s owner: what happened, what it means, what we’ll do, and who does it by when. How to Get Your Team to Actually Use Your Reports covers that note and the meeting around it.


    Step 6: Update It the Same Way Every Month

    A scorecard that takes an afternoon to update gets skipped within a few months. If the update drags, the problem is usually how the data gets in, not the scorecard.

    Here is an example routine for a business that finishes its month-end bookkeeping within the first few business days. Adjust the days to your own close.

    1. Books closed. Wait until the month’s transactions are reconciled. Numbers pulled earlier will change, and the scorecard will disagree with your accounting.
    2. Exports in. Each metric owner clears their import tab and pastes the same standard export into cell A1. Save each export with the same filters and date range every month, and write those settings down.
    3. Record the month. Copy the Data tab’s results into that month’s column on the Trend tab using paste values, so next month’s imports don’t change them.
    4. Review. Change the reporting month in B2. Check the status column, then check that two or three headline figures match your accounting system before anyone else reads the sheet.
    5. Lock the month. Protect the finished month’s column on the Trend tab so nobody edits it by accident. In Google Sheets, use Protect sheets and ranges. In Excel, lock the cells and turn on Protect Sheet.

    When numbers do disagree, don’t adjust the scorecard to make them match. Find the cause. Revenue that differs between your payment processor, your bank, and your books usually has an ordinary explanation: payout timing, processor fees, or a different cutoff date. The Business Data You Already Have explains why those sources rarely line up.


    Monthly Scorecard Checklist

    • Four to seven metrics, each with a written definition, unit, direction, and type.
    • One owner per metric.
    • A Scorecard tab that fits on one screen, with a Trend tab, a Data tab, and one import tab per source behind it.
    • This month’s target, actual, variance, and status in adjacent columns.
    • Year-to-date figures calculated by type: flows summed, ratios recomputed from components, point-in-time figures taken at month end.
    • Targets that start from a baseline and account for budget, capacity, and season, with adjustments written down.
    • A tolerance band for each metric, and a separate rule for any metric with a zero target.
    • A written monthly routine, with each finished month recorded as values and locked.

    Frequently Asked Questions

    Should the scorecard be weekly or monthly?
    Both can exist. Weekly suits operating numbers people can act on quickly. Monthly suits numbers that only settle after the books close, such as margin and cash flow. Build the monthly scorecard first if your accounting only closes monthly.

    Can I download a template instead?
    Yes, if it’s close to what you need. Check that it lets you set your own four to seven metrics, keeps raw data away from the results, and uses formulas you can follow. If you’d have to delete most of it, building the tabs yourself may be simpler. Either way, make sure you understand every formula before something breaks.

    When should the scorecard move out of a spreadsheet?
    When the spreadsheet becomes the hard part: refreshing the data takes more time than acting on it, different people need different access, you need a record of who changed what, the data volume slows the file down, or keeping it working has become a job of its own. Until then, a spreadsheet is easier to change as you learn which metrics matter.

  • How Much Does a Small Business Dashboard Cost?

    There is no responsible single price for a small business dashboard, because "dashboard" covers everything from a spreadsheet scorecard to a multi-system software project. What you can judge is the work behind a quote. Four things drive it, and none of them is how the charts look: how clean your data already is, how many systems have to feed it, whether the numbers update on their own, and how many metrics you ask for. One tidy source in a spreadsheet is the cheapest build. Several automated feeds cost more. A build that needs a database or custom integration costs the most. Software licenses and upkeep are separate and ongoing.

    That is also why two honest quotes for "a dashboard" can differ widely. They are pricing different amounts of work, and most of that work happens before anything appears on a screen.


    What Actually Drives the Price

    How clean your data is. This is usually the biggest single factor. If the same customer appears three ways in your invoicing system, if products were never mapped to consistent codes, or if someone types entries by hand each week, that all gets sorted out before any chart is accurate. Clean, consistent records make a build straightforward. Messy ones turn it into a data project with a dashboard at the end.

    How many systems feed it. Each additional source adds more than a connection. It adds a definition to agree on and a reconciliation to maintain. Your accounting software, your payment processor, and your bank will each report a different number for what looks like the same month, for legitimate reasons, and someone has to decide which one the dashboard shows. The Business Data You Already Have covers why those three rarely agree.

    Whether it updates by itself. A dashboard you refresh by pasting an export is cheap to build and costs you time every week. An automated refresh costs more up front and less afterward, as long as someone maintains the connection when a source changes its format.

    How many metrics you ask for. This is the one you control most directly. My rule of thumb is four to seven metrics on the main view, and the question I ask about each one is whether it makes a difference: does it help bring in revenue, make the business more efficient, or cut costs? A request for twenty-five charts does not just add twenty-five drawings. Each metric needs its data found, cleaned, defined, and tested. Cutting the list is the cheapest change you can make to a quote. How Many KPIs Should a Small Business Track? covers how to choose them.


    Three Scope Tiers, Lowest to Highest

    One or two clean sources in a spreadsheet. Google Sheets or Excel, fed by exports you download from your accounting or payment system and paste in, with formulas doing the rest. This suits a business that wants a reliable monthly scorecard and can live with updating it by hand.

    Automated feeds in a reporting tool. Looker Studio or Power BI pulling from two to four systems on a schedule, with metric definitions agreed and built in. This is the common choice for a business that reviews numbers weekly and does not want anyone handling files.

    A multi-system pipeline. Five or more sources, a proprietary POS or ERP in the mix, data landing in a cloud database before it reaches the dashboard, and user permissions controlling who sees what. This is a software project, priced accordingly, and worth it mainly when the alternative is several people reconciling by hand.


    What a Comparable Quote Contains

    Quotes vary more because of scope than because of rates. Before comparing two numbers, make sure both describe the same work. A quote you can compare states, in writing:

    • Which systems get connected, and who provides the access.
    • Which metrics get built, and the agreed definition of each one.
    • How the data refreshes, and how often.
    • What happens when a source changes its export format.
    • Who owns the file or workspace when the project ends.
    • How ongoing maintenance is requested and billed.

    Hourly billing suits small changes and work where the scope is still unclear. A fixed price caps your cost for the work written into the scope, so ask how the quote handles changes you request later. A short paid scoping step before a fixed quote can reduce that risk, because it forces the definitions conversation early, when changing your mind costs the least.


    The Costs That Don't Stop

    Software licensing is separate from the build. Looker Studio is free for authoring and sharing reports. Power BI Pro is a paid per-user license, listed at $14.00 per user per month billed annually at the time of writing. If a system you use has no native connector, a third-party connector service may add its own monthly subscription.

    Maintenance is the easiest part to leave out of a budget. Upstream software changes column headers, an API updates, a new service line needs a new definition. Some businesses pay a fixed retainer; others handle changes as they arise, billed hourly or under a service agreement. What matters is agreeing in advance who does it, not how many hours it takes.


    Building It Yourself Isn't Free

    The tools can be free. Your time isn't. Estimate the hours you expect to spend building it, add the hours to keep it running every month, and multiply by what an hour of your own time is worth to the business. Use your own figures rather than a published average.

    Compare that against a quote before deciding. The common failure is not a bad decision either way. It is the half-built file that gets abandoned three weeks in, after the hours are already spent.


    Frequently Asked Questions

    Why won't anyone publish a price?
    Because "a dashboard" can mean a single spreadsheet tab or a multi-system software project. Most of the difference is in your data, which nobody can see until they look at it.

    Can I start small and add to it later?
    Yes, and it's usually the better path. Start with one source and the few metrics that pass the revenue, efficiency, or cost test. Adding a second source later is easier than removing four you never used.

    Should I fix what I have instead?
    Often, yes. If your numbers are accurate and the dashboard is just cluttered, renovation is often the smaller job. Have someone inspect how the current one is built before you decide. How to Improve a Business Dashboard You Already Have walks through that.


    Before You Spend Anything

    Check whether you already have what you need. Pull two or three headline numbers from your existing systems and see whether they hold up. If they do and the problem is presentation, renovate. If you're not sure whether you need outside help at all, When Should a Small Business Hire a Data Analyst? covers that decision.

  • KPIs for a Small Professional Services Firm

    A small professional services firm can run on five KPIs: billable utilization, realization, project gross margin, days sales outstanding (DSO), and qualified pipeline. Together, they answer the questions that decide whether a firm that sells time makes money. Are people spending their hours on billable work? Is that work getting billed and paid at the rates you set? Are projects finishing on budget? Is cash arriving on time? Is next quarter’s work lined up?

    What those numbers should be in your firm is a separate question, and it is where generic advice is weakest.


    Why Generic Benchmarks Don’t Fit Your Firm

    You’ll find plenty of published targets for utilization and margin. I wouldn’t lean on them. Setting a utilization target without looking at what a firm does and how it does the work is like generalizing about a family’s culture from the outside. A five-person engineering firm where the owner writes every proposal is a different business from a ten-person agency with a dedicated salesperson, even though both sell hours.

    Margin works the same way. What a healthy project margin looks like depends on the industry and the market you serve.

    So use the formulas below as written, but set your normal ranges from your own history: the last six to twelve months of time, invoice, and payment records, with seasonal periods compared like for like. The point is to notice when a number moves away from your normal and to know what to do about it. For why five metrics is enough, see How Many KPIs Should a Small Business Track?


    1. Billable Utilization

    Formula: billable hours ÷ available working hours × 100

    A consultant who records 30 billable hours in a 40-hour working week is at 75 percent. Define available working hours consistently by excluding company holidays and approved leave. Whether 75 percent is right depends on the role. Someone whose job is mostly client delivery will run higher than a senior lead who also reviews work and trains staff. An owner who writes proposals and runs the firm will run lower still. If an owner’s billable hours climb while the pipeline shrinks, check whether client delivery is crowding out business development.

    Set a normal range for each role based on what that role is actually expected to do, rather than one number for the whole firm.

    Watch for: utilization rising while realization falls. People are busy on work the firm isn’t getting paid for.


    2. Realization

    Realization shows how much of the work you record turns into revenue. Track it in two parts.

    Billed realization: fees invoiced ÷ (billable hours × standard rate) × 100

    If a team records 120 billable hours at a $150 standard rate, that work is worth $18,000 at standard rates. If the invoices total $15,300, billed realization is 85 percent. The missing $2,700 went to write-downs, discounts, or scope that never got billed.

    Collected realization: cash collected against a group of invoices ÷ the value of those invoices × 100

    Measure the same invoice group in the numerator and denominator, or use a rolling window long enough to absorb ordinary payment lag. Otherwise, this month’s collections divided by this month’s invoices can compare unrelated work. The measure catches disputes, deductions, and invoices that never get paid.

    On fixed-fee work, the same idea appears as an effective hourly rate: fees collected on the project ÷ all hours worked on it, including rework. A $10,000 fixed-fee project that took 100 hours earned $100 an hour. At a $175 standard rate, the same 100 hours have a standard-rate value of $17,500, leaving a $7,500 gap to investigate. That gap is not automatically lost profit; it may reflect deliberate pricing, scope growth, or delivery inefficiency.

    Watch for: billed realization dropping on the same clients or project types. The fix is usually tighter scope and change orders, not more hours.


    3. Project Gross Margin

    Formula: (project revenue − direct labor cost − direct project expenses) ÷ project revenue × 100

    Use burdened direct labor cost: wages plus employer payroll taxes and employee benefits for the hours spent on the project. Keep overhead separate unless your project-costing method allocates it consistently.

    Because margin expectations vary so much by industry and market, compare each project with its own budget. A project priced for a 55 percent margin that finishes at 38 percent tells you something went wrong in the estimate, the scope, or the delivery. Find out which before you quote similar work.

    Watch for: the same type of project repeatedly finishing below its budgeted margin.


    4. Days Sales Outstanding (DSO)

    Simple formula: ending accounts receivable ÷ credit sales for the period × days in the period

    With $90,000 in ending receivables and $270,000 in credit sales over the last 90 days, DSO is 30 days. If receivables swing sharply during the period, use average receivables instead of the ending balance and label the method so comparisons stay consistent.

    DSO estimates how long clients take to pay, but it lags. By the time it jumps, the late invoices are already late. I prefer to set up receivables so someone sends reminders and talks with clients around the due date. That way, the firm can identify payments that may lag and address issues before invoices drift past 60 days.

    Watch for: individual invoices getting close to 60 days, not just a rising average.


    5. Qualified Pipeline

    Definition: total value of qualified proposals and opportunities expected to close in the next 90 days

    Some firms weight each opportunity by its chance of closing. A simple total works too, as long as you count the same way every week.

    The first four KPIs describe the work you already have. Pipeline tells you whether there will be work next quarter, and it’s the number that suffers first when senior people are too busy billing to sell. Client retention matters as well, but it changes slowly; review it quarterly rather than weekly.

    Watch for: pipeline shrinking while utilization is high. That’s a firm that is busy now and will be short of work later.


    A Simple Scorecard Layout

    KPISource recordsReviewExample ownerWhen it moves outside your range
    Billable utilization, by roleTime trackingWeeklyOperations leadRebalance assignments; check who is overloaded
    Billed and collected realizationTime tracking and invoicingMonthlyManaging partnerLook for write-downs by client or project type; tighten scope
    Project gross marginTime, payroll, and project expensesAt milestones and closeProject leadCompare with the estimate; adjust pricing for similar work
    DSO and open invoicesAccounting receivables agingWeeklyOffice or finance managerFollow up on invoices near their due date
    Qualified pipelineCRM or proposal listWeeklyOwner or sales leadProtect time for business development

    Most of this data already lives in your time-tracking, invoicing, and accounting software. Start with a simple spreadsheet if you need to bring the sources together.

    If pulling these numbers together each week takes longer than acting on them, it may be time for outside help. When Should a Small Business Hire a Data Analyst? covers how to tell.

  • How to Get Your Team to Actually Use Your Reports

    Reports get used when they feed a routine that ends in decisions. Keep the report to one page with four to seven core numbers. Have each manager prepare a short note on any number that’s off track. Then run a short weekly meeting built around three questions: What do the numbers mean? Who will act on them? By when? Open the next meeting by checking whether those actions happened.

    To me, a useful conversation about the numbers is an action-oriented one: what the numbers mean, who will act on them, and by when. Most reporting routines stop at the first part. Without a name and a date, a team can discuss the same bad number every week and nothing changes.


    Why Doesn’t Your Team Read the Reports You Send?

    Often because reading them is not connected to a decision or a follow-up. A report emailed on Monday competes with customer calls, staffing problems, and everything else on a manager’s list. If no meeting depends on it and nobody will ask about it, reading it is optional, and optional work gets pushed to later.

    Two other problems make it worse:

    • The report makes the reader do the analysis. A ten-tab spreadsheet or a 15-page PDF asks each manager to find what changed and decide whether it matters. Most probably won’t.
    • The report describes the past without asking for anything. If a report never leads to a decision, people reasonably conclude it isn’t meant for them.

    If the problem runs deeper, and people don’t trust the numbers or can’t connect the metrics to their work, start with Why Nobody Looks at Your Dashboard. The routine below works best once people believe the numbers.


    What Should the Report Look Like Before the Meeting?

    One page. If it doesn’t fit on one page, each reader has to do the sorting the report should have done for them.

    A one-page weekly summary needs four parts:

    1. The scorecard. Four to seven core metrics, each with its current value, target range, prior period, and a simple on-track or off-track status. Four to seven is my rule of thumb for most small businesses; How Many KPIs Should a Small Business Track? covers how to choose them.
    2. What’s off track. The metrics outside their range this week, called out at the top so nobody has to hunt for them in a table.
    3. What went well. One to three things that improved, and why. This keeps the meeting from turning into a list of problems and tells people what to keep doing.
    4. Decisions needed. Anything that needs an approval, a trade-off, or resources from the owner this week.

    Everything else goes in an appendix or a linked file: full financial statements, transaction detail, breakdowns by customer or crew. People open it when they need to investigate. A monthly version can add that detail without crowding the weekly operating view.


    How Should Managers Prepare for the Meeting?

    They should read the one-page summary beforehand and write a short note for any metric they own that is off track. Meeting time is for deciding, and reading numbers aloud wastes it.

    Send the summary early enough to read: Friday afternoon for a Monday meeting, or first thing in the morning for a late-morning meeting. Put the notes in one shared document so everyone can see them before the meeting starts.

    The Off-Track Note

    Each note answers four questions in a few sentences:

    1. What happened? The number, its target, and how far off it is.
    2. What does it mean? The effect on cash, customers, delivery, or cost.
    3. What will we do? The specific action.
    4. Who, and by when? One name and one date.

    Here is a hypothetical example, not a client case:

    What happened: First-pass yield fell to 88% this week against a target of 95%.

    What it means: About 12 hours of rework, roughly $2,500 in scrapped material, and one order at risk of shipping late.

    What we’ll do: Recalibrate the tooling on the cutting station and review the new tolerances with the operators.

    Who and by when: Shop lead. Tooling done by Tuesday; operator review Wednesday morning.

    A short note like this changes where the conversation starts: with a proposed fix instead of an argument about what went wrong.

    One rule matters more than the format. Don’t penalize people for reporting a red number. Ask them to bring either a proposed next step or a clear request for help. If off-track numbers get people criticized in front of the team, expect to see numbers explained away instead of fixed.


    How Do You Run the Meeting?

    Keep it short, run it the same way every week, and end with names and dates. The agenda below is a 15-minute starting point for a small team; add time when several metrics need real decisions.

    Here is a starting agenda for a 15-minute meeting. Stretch the off-track section if you need a longer one.

    MinutesTopicWhat happens
    0–3Last week’s actionsEach owner says done, in progress, or missed; a missed action gets a new date
    3–5ScorecardWalk through the metrics and confirm which are off track
    5–12Off-track metricsEach owner gives their note in about a minute; the group agrees on the action, owner, and date
    12–15Decisions and blockersThe owner approves resources or settles conflicts between departments

    A few rules keep it on track:

    • Show the report itself. Put the one-page summary or the dashboard on the screen. A separate slide deck is one more document to maintain and one more place for numbers to disagree.
    • Skip what’s on track. If a number is in range, move on.
    • Take long problems out of the meeting. If something needs more than a few minutes, assign someone to work on it and set a date to report back.
    • Record every action before anyone leaves, with its owner and due date.

    How Do You Make Sure Actions Actually Happen?

    Keep a running action log and open every meeting with it. This step is easy to skip, but it is the one that shows people the routine matters.

    The log can be a simple table in the same shared document. The entries below are samples:

    RaisedMetricActionOwnerDueStatus
    Sept. 8Days sales outstandingCall the five largest overdue accountsOffice managerSept. 12Done
    Sept. 8Labor cost as % of salesAdjust Tuesday and Wednesday schedulesOperations leadSept. 15In progress
    Sept. 15First-pass yieldRecalibrate cutting station toolingShop leadSept. 16Open

    When you review the log each week:

    • Done: Check whether the metric responded. If it didn’t, the action didn’t address the cause, and the owner needs a new plan. Or, decide if the action did address the cause and the response needs more time to become indicative.
    • In progress: Confirm the date still holds.
    • Missed: Ask for a new date and what got in the way. If the same action slips twice, investigate whether the constraint is time, authority, resources, or an unclear assignment instead of sending another reminder.

    Over a few months, the log also shows which problems keep coming back. That pattern can be more useful than any single week’s report.


    What About Monthly Reviews and One-on-Ones?

    Use the same pattern at a different pace.

    A monthly review covers the numbers that only change meaningfully after the books close, such as gross margin, and looks at trends across several weeks. It uses the same off-track notes and the same action log, with additional financial and operating detail where needed.

    A one-on-one is where you help a manager with their own numbers. Start with the metrics they own, look at the trend, and ask what they need to bring an off-track number back into range: time, budget, help from another department, or a decision from you. Asked that way, the conversation becomes about solving the problem together rather than checking up on them.


    How Do You Keep Reports From Piling Up Again?

    Review every recurring report once a quarter and stop the ones nobody would miss. Reports accumulate: someone asks a one-time question, the answer becomes a weekly report, and nobody ever turns it off.

    For each scheduled report, ask the people who receive it: “If this report stopped tomorrow, what decision would you be unable to make?” If nobody can name one, stop sending it. If someone misses it later, you can bring it back.

    Apply the same test to the metrics on the weekly summary. If your dashboard has grown well past what the meeting can use, How to Improve a Business Dashboard You Already Have walks through cutting it down.


    Your First Four Weeks

    • Week 1: Cut the report to one page with four to seven metrics, and assign an owner to each.
    • Week 2: Send the summary before the meeting and ask owners of off-track metrics for their notes. Some notes will be missing; ask for them anyway.
    • Week 3: Open the meeting with the action log from week 2.
    • Week 4: Look back at the log. Which actions got done, which slipped, and did the numbers respond? Adjust the metrics, the timing, or the meeting length based on what you find.

    Expect the routine to feel mechanical at first. It starts to stick once people see that a number raised in one meeting leads to an action, and that the action gets checked in the next one.

  • Why Nobody Looks at Your Dashboard (and How to Fix It)

    People stop looking at a dashboard for a few predictable reasons: they don’t trust the numbers, the metrics don’t connect to their work, nobody has shown them what to do when a number changes, the screen is a hassle to use, or the person in charge ignores it too. Training alone will not fix those causes. What works is rebuilding trust in the numbers, cutting the dashboard down to metrics people can act on, and tying each one to a decision.

    I have seen reports get ignored for several of these reasons. A recurring one was that people didn’t understand what difference the numbers could make, or how to act on them. Once, the reason was simpler: the person in charge was sure they already knew the business better than any report could tell them.

    The good news is that each cause leaves a recognizable trail, so you can figure out which one you are dealing with before you change anything.


    How Does a Dashboard Go From Launch to Ignored?

    Usually gradually, and for reasons that started weeks before anyone noticed the drop in use. Abandoned dashboards tend to follow the same pattern.

    1. Launch. The dashboard is introduced in a meeting. People open it out of curiosity, click around, and say it looks useful.
    2. The first doubt. Someone notices a number that doesn’t match what they know: a sales total that looks low, a job count that seems off. Nobody explains the difference.
    3. The quiet return. Instead of reporting the problem, that person goes back to their own spreadsheet. Others follow for their own reasons: the dashboard is slow, or it doesn’t show what they need.
    4. Neglect. With fewer people looking, nobody notices when a data connection fails, or a metric goes stale. The out-of-date numbers confirm everyone’s decision to stop using it.

    The clearest sign you have reached step 3 or 4 is that managers arrive at meetings with their own spreadsheets. A dashboard that has lost to private spreadsheets has usually lost on trust, relevance, or both.


    Why Do People Stop Trusting the Numbers?

    At some point, a dashboard number disagreed with something they knew was true, and nobody could explain why, or worse, could figure out why. That single discrepancy erodes confidence entirely.

    Take a sales manager who knows the team closed about $55,000 in new work last month. The dashboard says $42,000. There may be a perfectly good reason. The dashboard might count invoiced revenue, while the manager counts signed contracts. It might use a different month-end cutoff, or leave out a job still waiting on an invoice. Without an explanation, though, the manager concludes the dashboard is wrong and stops trusting the other numbers on the screen, too.

    Numbers drift apart for a handful of common reasons:

    • Different definitions. “Sales” can mean booked, invoiced, or collected. Each is legitimate, and each produces a different total.
    • Timing. Cash and accrual accounting put the same transaction in different periods. Payment processors deposit money days after the sale.
    • Unmapped categories. A new product, service code, or customer type gets added to the source system but never mapped into the dashboard, so its revenue disappears from the totals.
    • Silent failures. A data refresh fails, or a formula breaks, and the dashboard keeps showing old numbers without any warning.

    Most of these aren’t errors in the usual sense. They are definitions and rules that were never written down where the people using the dashboard could see them. Tracing a mismatch starts with documenting which system, definition, date range, and cutoff produced each number.


    Why Don’t the Metrics Feel Relevant to the Team?

    Because the dashboard shows what the owner wants to know rather than what the people using it can influence.

    A shop supervisor can’t do much with quarterly net profit. They can act on the number of jobs waiting for inspection or the parts that failed first inspection this week. A service coordinator can’t move company-wide revenue directly, but they can act on unbilled hours or open slots in next week’s schedule.

    When the main view shows only company-level results, frontline managers reasonably decide the dashboard isn’t for them. They aren’t resisting data. They are ignoring numbers they can’t do anything about.

    Each person should see the few metrics they can move, alongside the company results those metrics feed. For choosing those metrics, and keeping the list short enough to act on, see How Many KPIs Should a Small Business Track?


    What If People Don’t Know What to Do With the Numbers?

    Then the numbers are trivia, and people stop checking trivia. In my experience, this is a recurring reason reports get ignored: nobody understood what difference the number could make or how to act on it.

    Suppose a dashboard shows that days sales outstanding rose from 38 to 47 over two months. To an owner who watches cash closely, that is an obvious warning: customers are paying more slowly, cash will be tighter, and someone should start calling the largest overdue accounts. To a manager who has never had that explained, it is just a number that went up.

    A practical fix is to write one line for every metric on the main view that answers three questions: what it means when the number moves, what usually happens next, and who does it. Put those lines on a notes tab or beside each card.

    Here is what that looks like for a few metrics. The metrics, triggers, and owners are illustrative; set your own.

    MetricWhen it moves the wrong wayWhat usually happens nextWho
    Days sales outstandingRises two weeks in a rowCall the five largest overdue accounts; review payment terms on new workOffice manager
    Gross margin by jobA job finishes below targetCompare actual hours and materials with the estimate; adjust the next quoteOperations lead
    Qualified inquiriesFalls below the monthly rangeCheck whether the source changed (referrals, website, repeat customers) before spending more on marketingOwner
    Booked hours next weekBelow available capacityContact customers with pending work; move maintenance tasks into the open timeScheduler

    Writing these lines also tests the metric. If nobody can say what action would follow a change, the metric probably doesn’t belong on the main view.


    Is the Dashboard Too Much Trouble to Use?

    It may be. Every extra login, filter, click, and scroll makes it easier to just ask someone for the number.

    Watch for these signs:

    • People email or message you asking for figures that are already on the dashboard.
    • Getting to the dashboard requires a login people forget, or a link buried in an old email.
    • Each visit starts with setting date ranges and filters before anything useful appears.
    • It loads slowly, or the important numbers are below the fold.

    Most of these have simple fixes: save a default view with the right filters already applied, share one bookmarked link, and fit the main metrics on one screen. For the design problems that make dashboards hard to read, see 7 Dashboard Mistakes Small Businesses Make.


    What If the Person in Charge Doesn’t Use It?

    Other people are unlikely to use it for long too. One of the reports I have seen ignored went unused for exactly this reason: the boss believed they already knew better and didn’t need it.

    People take their cues from what the person in charge pays attention to. If the owner makes decisions from instinct and never mentions the dashboard, managers learn that keeping the numbers current is wasted effort, and they stop.

    This doesn’t mean experience and instinct should be ignored. An experienced owner often does know things a report can’t show. But when instinct and the dashboard disagree, that disagreement is worth resolving. The data may be wrong, the instinct may rely on context the dashboard does not capture, or an old assumption may need another look.

    If you are the person in charge, three habits change the signal you send:

    1. Ask about the numbers first. Start conversations with managers by looking at their metrics together.
    2. Say which number informed a decision. “We’re holding off on the new hire because booked hours dropped for three weeks” teaches more than a memo about being data-driven.
    3. Treat disagreement as a question. When a number surprises you, ask why before dismissing it.

    How Do You Get People Looking at the Dashboard Again?

    Fix trust first, then relevance, then habit. Redesigning the layout before people trust the numbers produces a better-looking dashboard that people still ignore.

    Step 1: Reconcile the Numbers in the Open

    Sit down with the managers who use the dashboard. Pick the headline numbers and compare each one with its source: bank deposits, accounting reports, payroll, or the scheduling system. For every gap, either fix it or explain it. Then write each metric’s definition in plain language where everyone can see it, such as “Revenue = invoiced amounts by invoice date, excluding sales tax.”

    Step 2: Let Managers Challenge Their Metrics

    If a manager says a metric doesn’t reflect their work, take it seriously. Either the definition needs to change or the metric needs to be replaced. Separate two kinds of objections, though: “this is measured wrong” gets fixed, while “I don’t like what this shows” doesn’t.

    Step 3: Cut the Main View Down

    Keep four to seven metrics on the main screen, which is my rule of thumb for most small businesses. Move the rest to a detail tab. How to Improve a Business Dashboard You Already Have walks through the cleanup step by step.

    Step 4: Attach an Action and an Owner to Every Metric

    Write the one-line action notes described above, and put one person’s name on each metric.

    Step 5: Put the Dashboard on a Meeting Agenda

    A dashboard that people are only invited to check will keep sliding back toward neglect. Make it the first thing a regular meeting opens, and ask each owner to speak to their number: what changed, what it means, who will act, and by when.


    Which Problem Do You Have?

    Match what you see to the likely cause and the place to start:

    What you noticeLikely causeStart with
    Managers bring their own spreadsheets to meetingsThe numbers aren’t trustedStep 1: reconcile in the open
    “That’s not really my number”Metrics don’t fit their workStep 2: let managers challenge metrics
    People look at the numbers, but nothing changesNo action attachedStep 4: write action notes
    People ask for figures that are already on the dashboardToo much trouble to useDefault views, one link, one screen
    Decisions get made without mentioning the numbersLeadership doesn’t use itAsk about the numbers first
    Nobody opens it between meetings, or there are no meetingsNo routineStep 5: put it on the agenda

    Most ignored dashboards have more than one of these problems. Start with trust. Nothing else sticks until people believe the numbers.

  • 7 Dashboard Mistakes Small Businesses Make

    The most common dashboard mistakes are showing too many metrics, featuring vanity metrics that don't lead to decisions, displaying numbers without targets or comparisons, pasting raw tables onto the main screen, paying for real-time updates nobody acts on, leaving metrics without an owner, and mixing headline results with detail. Each one makes the dashboard harder to read quickly, and reading quickly is the whole point of a dashboard.

    Most of these mistakes start the same way: the dashboard gets built around what the software can show instead of the decisions the business needs to make. Use the seven below as a checklist against your own screen.


    1. Too Many Metrics on One Screen

    What it looks like: Twenty or thirty charts, cards, and gauges, and you have to scroll to see them all.

    Why it hurts: When everything competes for attention, the number signaling a real problem looks the same as the twenty that don't. People skim, then stop opening it.

    What to do instead: Keep four to seven core metrics on the main view. That's my rule of thumb for most small businesses, and the reasoning is in How Many KPIs Should a Small Business Track?

    2. Vanity Metrics in the Top Row

    What it looks like: Page views, social followers, total sign-ups, or revenue booked sit in the most prominent spots.

    Why it hurts: These numbers can climb while margins shrink or cash gets tight. They feel like progress and give you nothing to act on.

    What to do instead: Ask whether each metric makes a difference. Does it help bring in revenue, make the business more efficient, or cut costs? Then ask who would do what if it dropped 20 percent next week. A metric that fails both questions doesn't belong at the top.

    3. Numbers With No Context

    What it looks like: A card that says "Revenue: $45,000" or "DSO: 48 days" and nothing else.

    Why it hurts: The reader has to remember last month, recall the budget, and do the math. Is $45,000 a good month? The card can't say.

    What to do instead: Show each number beside a target and the prior period: "$45,000 against a $50,000 target, up from $41,500 last month."

    4. Raw Tables on the Main Screen

    What it looks like: A 50-row export of invoices or transactions embedded on the dashboard.

    Why it hurts: A large raw table usually has to be read line by line, which makes trends and outliers harder to spot at a glance.

    What to do instead: Summarize on the main view with a number card or a small trend line. Keep the table on a separate detail tab for when you need to investigate.

    5. Real-Time Updates for Weekly Decisions

    What it looks like: Live feeds refreshing every few minutes for sales, pipeline, or margin that the team reviews once a week.

    Why it hurts: Real-time connections can add cost or maintenance complexity, and they can invite overreaction to swings that even out by the end of the week.

    What to do instead: Refresh as often as you act. A scheduler may need daily capacity data, while a closed-month margin calculation only needs to update after the accounting period ends.

    6. Metrics Nobody Owns

    What it looks like: Everyone can see the dashboard, but when a number turns red, nobody is sure whose job it is to explain it.

    Why it hurts: Problems get noticed and discussed but not fixed. After a few weeks of that, people stop taking red numbers seriously.

    What to do instead: Put one person's name on each metric. That person explains the number when it moves and says what they'll do about it. Build that ownership into a regular meeting and follow-up routine.

    7. Headline Results Mixed With Detail

    What it looks like: Gross margin and cash runway sit beside ad cost per click and scrap at a single workstation, all the same size.

    Why it hurts: This can happen even on a dashboard with only a handful of metrics. When detail gets the same weight as headline results, reviews drift into the detail and nobody steps back to ask whether the business is on track.

    What to do instead: Use two tiers. The main view holds the headline metrics. Detail lives on a separate tab you open when a headline number moves. The two-tier setup is explained in How Many KPIs Should a Small Business Track?


    A Quick Dashboard Check

    Open your dashboard and answer yes or no:

    1. Does the main view show seven metrics or fewer, without scrolling?
    2. Does every metric on it help bring in revenue, improve efficiency, or cut costs?
    3. Does every number show a target and a prior period?
    4. Are detailed tables kept off the main view?
    5. Does the refresh schedule match how often you act on the numbers?
    6. Does every metric have one named owner?
    7. Is detail kept on a separate tab from headline results?

    Each "no" points to the matching mistake above.


    Next Step: Fix What You Found

    Once you know which mistakes your dashboard has, How to Improve a Business Dashboard You Already Have walks through repairing them in order, starting with whether the numbers can be trusted. If the dashboard is in good shape and people still ignore it, investigate trust and routine rather than redesigning it again.

  • How to Improve a Business Dashboard You Already Have

    Edit your dashboard before you replace it. Confirm the numbers match your source systems, cut the main view to four to seven metrics, lay out what remains on one screen with a target beside each number, fix the manual data steps that keep breaking, and put one person's name on each metric. Most cluttered dashboards can be repaired in the tool you already have.

    A rebuild feels cleaner, but it tends to recreate the same problem in new software. Dashboards get cluttered because requests keep getting added and nothing gets removed. A new tool doesn't change that habit.


    Should You Fix Your Dashboard or Rebuild It?

    Fix it if the underlying numbers are right and the business still works the way it did when the dashboard was built. Rebuild only when the data feeding it can't be repaired, or the business has changed so much that the old metrics no longer describe it.

    Answer three questions before changing anything:

    1. Do the numbers match the source? Pick two or three headline figures, such as last month's revenue or current receivables, and compare them with your accounting system, bank, or POS for the same period. If they match, or the gaps have a known cause like payout timing, the foundation is usable. If nobody can explain the gaps, fix the data first. Redesigning a screen full of wrong numbers wastes the afternoon.
    2. Does the dashboard still describe the business? If you've added a service line, closed a location, or changed how you price, some metrics may describe a business you no longer run.
    3. Is the tool really the problem? Google Sheets, Excel, Looker Studio, and Power BI can all display a clean, focused set of KPIs. Switching tools rarely fixes a layout problem.

    If the answers point to renovation, work through the four steps below in order.


    The Four-Step Dashboard Renovation

    Step 1: Cut the Main View to Four to Seven Metrics

    The fastest improvement is removal. List every chart, card, and table on the dashboard, then mark each one: keep on the main view, move to a diagnostic tab, or delete.

    Which metrics survive depends on the business, but the question I ask is the same: does this metric make a difference? Does it help bring in more revenue, make the company more efficient, or cut costs? If it does none of those, it's a candidate for deletion.

    My rule of thumb is four to seven core metrics, and each one has to move the needle: when it changes, someone makes a specific decision. The full test for sorting metrics is in How Many KPIs Should a Small Business Track?

    Expect pushback on deletions. Instead of arguing, move disputed metrics to a tab labeled "Diagnostic." If nobody opens that tab in two months, delete them.

    Step 2: Make It Readable at a Glance

    Arrange what's left so someone can tell whether the business is on track within a few seconds, on one laptop screen, without scrolling.

    • Replace gauges and dials with number cards. A speedometer graphic uses a lot of space to show one value. A card showing the current value, the target, and last period's value shows more in less room.
    • Take large tables off the main view. A 50-row table is a report. Summarize it in a card or a small trend line and move the detail to the diagnostic tab.
    • Give every number a comparison. "$74,200" alone doesn't tell you much. "$74,200 against an $80,000 target, up from $69,800 last month" tells you where you stand and which way you're heading.
    • Save color for exceptions. Use gray and neutral tones for the layout. Reserve red, yellow, and green for metrics outside their target range, so color means something when it appears.

    If the main view still doesn't fit on one screen, go back to Step 1. The next useful check is to look for repeated design errors such as missing comparisons, raw tables, and detail mixed with headline results.

    Step 3: Fix the Data Steps That Break

    Find every place where someone copies, pastes, or retypes data to update the dashboard. Manual steps are where errors creep in, and where updates stop when that person is on vacation.

    • Connect instead of paste where your tools allow it: a built-in data connector in Looker Studio or Power BI, or the IMPORTRANGE function to pull from another Google Sheet.
    • Document what can't be connected. Write down which report is exported, with which filters and date range, by whom, and when.
    • Match the refresh schedule to your decisions. A metric you review weekly needs a dependable daily or weekly refresh, not necessarily a live feed. Real-time connections can add cost or maintenance complexity, and faster data can invite reactions to swings that even out by the end of the week.

    Step 4: Put a Name on Every Metric

    Assign one person to each metric on the main view and show their name or initials on the card. That person explains the number when it moves outside its range and says what they're doing about it.

    When a metric belongs to everyone, nobody follows up. A named owner means a red number gets an explanation and a next step. Ownership works best when the dashboard is reviewed at a regular meeting with a consistent follow-up routine.


    Dashboard Renovation Checklist

    1. Compare two or three headline numbers with your accounting, bank, or POS records.
    2. List every item on the dashboard and mark it keep, diagnostic, or delete.
    3. Move diagnostic items to a separate tab and delete the rest.
    4. Fit the remaining four to seven metrics on one screen.
    5. Replace space-heavy gauges with cards showing actual, target, and prior period.
    6. List every manual data step, then connect or document each one.
    7. Add an owner's name to every metric.

    Frequently Asked Questions

    How long does it take to fix a cluttered dashboard?

    The cuts and layout changes are usually the quickest part. Data problems take longer, especially if nobody documented how the dashboard was built.

    Should a small business dashboard update in real time?

    Rarely. Match the refresh to how often you act on the number. A scheduler may need daily capacity data, while a closed-month margin calculation only needs to update after the accounting period ends.

    When is it worth paying for a rebuild?

    When the source data can't be reconciled, the business has changed enough that the metrics need to be redesigned, or nobody on staff can maintain the data connections.


    Start With the Numbers

    Begin with the first check: pull two headline figures and compare them with your source systems. If they hold up, the rest of the renovation is editing. If your team still ignores the dashboard after it's cleaned up, investigate trust and routine rather than redesigning it again.

  • How Many KPIs Should a Small Business Track?

    Most small businesses should track four to seven KPIs on their main scorecard. Where you land in that range depends on the business, but the rule for what earns a place does not change: every metric has to move the needle. A change in the number should lead someone to make a specific decision about cash, capacity, or customers. You can still measure everything else. It just belongs in a second layer you open when a core number goes off track.

    Four to seven is an operating guideline, not a scientifically fixed limit. It is deliberately shorter than most “essential KPI” lists. Those lists are written to cover every possible business. Your scorecard only has to cover yours, and it has to be short enough that you and your team will read it every week.


    Why Four to Seven KPIs?

    Four to seven metrics can cover the questions that keep a small business healthy: Do we have cash? Are we making money on the work? Can we deliver? Is new work coming in? That is enough coverage without turning the weekly review into a research project.

    Below four, something important usually goes unwatched. An owner who tracks only the bank balance sees problems weeks after they start: a slow-paying customer, a job that ran over budget, a quiet month in the pipeline. The balance tells you where you are. It says little about what is coming.

    Above seven, three things tend to happen.

    The review takes too long. A short scorecard can fit into a brief weekly review. A 25-metric dashboard is more likely to turn that review into a status recital, so the meeting gets skipped, or the important change gets buried.

    Nobody can tell which change matters. In any given week, some of 25 numbers will rise, and some will fall for ordinary reasons. When everything moves, the one signaling a real problem is easy to miss.

    Ownership blurs. Each of the seven metrics can have a named person responsible for explaining it. With twenty-five metrics, ownership is harder to keep clear, and follow-up becomes less consistent.

    Treat the range as a guideline. A business with several distinct departments may need a short scorecard for each one. The principle holds at every level: the list any one person reviews should be short enough to act on.


    What Makes a Metric a Needle-Mover Instead of a Vanity Metric?

    A needle-mover leads to a specific decision when it changes. A vanity metric can look impressive and still tell you nothing about what to do next.

    Analytics expert Avinash Kaushik calls this the “Three Layers of So What” test. Keep asking “so what?” until the metric leads to a recommended action. If it cannot, it does not belong on the main scorecard.

    Run every metric you currently track through three questions:

    1. The Monday test. If this number dropped 20 percent by Monday morning, who on the team would do what? If the honest answer is “nobody” or “we’d keep an eye on it,” the metric is not a KPI.
    2. The anchor test. Does the metric connect directly to cash, margin, delivery capacity, or keeping customers? If the connection takes three steps of reasoning to explain, it is a supporting metric at best.
    3. The response test. Can your team make a useful decision when this number changes? You may not control the weather, the economy, or a vendor’s pricing, but you can still change staffing, purchasing, pricing, or cash plans in response. If the team cannot influence the number or respond to it, keep it off the main scorecard.

    A metric has to pass all three to earn a place on the main scorecard.

    Here is how some common vanity metrics compare with metrics that answer a similar question in a form you can act on:

    Looks usefulMoves the needleWhy
    Website page viewsQualified inquiries, and the share that become quotesTraffic can rise while the phone stays quiet
    Social media followersCost to acquire a paying customerFollowers don’t pay invoices
    Revenue bookedGross margin and cash collectedRevenue earned at a loss still costs you money
    Total labor or machine hours loggedShare of work done right the first timeBusy hours can hide rework
    Number of proposals sentProposal win rate and pipeline valueVolume without wins is activity, not progress

    The metrics in the left column still have uses. Page views can help explain why inquiries fell. They just don’t belong in the weekly review.


    What Do You Do With All the Other Metrics?

    Keep them, but take them off the main scorecard. Move them into a diagnostic layer that you open only when a core KPI goes outside its normal range.

    Think of it as two tiers.

    Tier 1: the scorecard. Four to seven KPIs, reviewed on a fixed schedule, usually weekly. (Some, such as gross margin, only update meaningfully once the month closes.) Each has a normal range, a named owner, and a place on one page or one screen without scrolling.

    Tier 2: diagnostics. The supporting detail: revenue by customer, overtime by crew, cost by vendor, scrap by workstation, website traffic by source. These live in a separate tab, a saved report, or an export from software you already use. You don’t review them every week. You open them to find out why a Tier 1 number moved.

    Here is how the two tiers work together. Say gross margin is one of your scorecard KPIs and normally runs between 45 and 50 percent. One month it comes in at 39 percent. That is a clear signal, so you open the diagnostics: material costs by vendor, overtime hours, rework on specific jobs. The scorecard tells you that something is wrong. The diagnostic layer tells you where.

    Most Tier 2 data already exists in your accounting, payment, scheduling, and operations systems. The Business Data You Already Have covers where to find it and how to test an export in a spreadsheet.


    Which Four to Seven KPIs Fit Your Business?

    The right KPIs depend on what limits your business: billable time in a service firm, flow through the shop in a manufacturer, food and labor costs in a restaurant. The three scorecards below are starting points. Replace any metric that fails the three-question test in your business.

    Each list includes a cash measure in a form that fits the business model. Whatever you change, keep one.

    Professional Services Firm

    Consulting, accounting, design, engineering, and agency firms sell expert time.

    1. Billable utilization: billable hours as a share of available hours, tracked by role
    2. Project gross margin: project revenue minus direct labor and project expenses, as a share of project revenue
    3. Days sales outstanding (DSO): how long, on average, clients take to pay
    4. Qualified pipeline: value of opportunities likely to close in the next 90 days
    5. Client retention: share of last year’s clients that still buy from you this year

    Job Shop or Light Manufacturer

    Output is limited by the slowest step in the process, so this scorecard watches flow, quality, and delivery.

    1. Queue time: how long work in progress waits between operations, such as between machining and assembly
    2. First-pass yield: share of parts or jobs completed without rework or scrap
    3. On-time, in-full delivery: share of orders shipped complete by the promised date
    4. Quote-to-order rate: share of quotes that become orders
    5. Cash runway: weeks of operating expenses covered by available cash

    Queue time is the one most shops overlook. A part can spend two hours on a machine and several days waiting for the next operation. Adding machine capacity won’t shorten that wait if the delay is downstream.

    Restaurant or Hospitality Business

    Food and labor are the highest costs you can control week to week, and they move quickly.

    1. Prime cost: cost of goods sold plus total labor, as a share of sales
    2. Labor cost as a share of sales, by shift or day of the week
    3. Average check, or spend per guest
    4. Table turns during peak periods
    5. Weekly cash in compared with fixed costs going out

    Prime cost and labor overlap on purpose. Prime cost tells you whether the combined total is under control. Labor by shift tells you where to change the schedule.

    Each list stops at five. That leaves room for one or two metrics specific to your situation, such as a major customer’s order volume or a seasonal inventory position, without going past seven.


    How Do You Cut an Existing Metric List Down?

    Use four steps: list what you track now, sort each metric with the three-question test, set a normal range for the survivors, and move everything else to the diagnostic tier.

    Step 1: List Everything You Currently Track

    Include dashboard widgets, spreadsheet tabs, numbers in your accountant’s monthly packet, and figures you check inside software on your own. Most owners find more than they expected.

    Step 2: Sort Each Metric Into Three Groups

    Apply the Monday, anchor, and response tests, then mark each metric:

    • Scorecard: passes all three tests
    • Diagnostic: helps explain a scorecard metric but fails the Monday test on its own
    • Drop: fails the anchor test and doesn’t help explain anything on the scorecard

    If more than seven metrics pass, rank them by how much cash or capacity is at stake and keep the top seven. Several of the ones that fall off will make good diagnostics.

    Step 3: Set a Normal Range and a Trigger

    For each scorecard KPI, write down its normal range and the point that requires action. Base the range on your own last 12 months rather than an industry average you found online. For example: “Gross margin normally runs 45 to 50 percent. Below 44 percent, the operations manager reviews job costs within a week.”

    Assign each KPI to one person, who explains it when it moves.

    Step 4: Move the Rest to the Diagnostic Tier

    Put diagnostic metrics in a separate tab or saved report, and remove dropped metrics from the weekly view. If someone objects to losing a metric, move it to diagnostics and check whether anyone opens it over the next two months.

    Example: 16 Metrics Down to 5

    This is an illustrative example, not a client case. An eight-person commercial cleaning company tracks 16 metrics in a spreadsheet. After the three-question test, they sort like this:

    ResultMetrics
    Scorecard (5)Weeks of cash on hand · Gross margin by contract · Invoice dollars more than 45 days past due · Labor hours versus bid hours by site · Contracts at risk or cancelled
    Diagnostic (7)Revenue by client · Supply cost by site · Overtime by crew · Re-cleans and complaints by site · Quote win rate · Average contract value · Days from signed quote to first service
    Drop (4)Website visits · Social media followers · Total square feet cleaned · Prospecting emails sent

    Labor hours versus bid hours made the scorecard because a site that consistently takes longer than bid is losing money, and the site supervisor can act on it that week. Overtime by crew stayed in diagnostics: it helps explain a labor problem but doesn’t need weekly attention on its own. Total square feet cleaned was dropped. It grows as the company grows but says nothing about whether the work is profitable.


    Next Step: Put Your KPIs on a Scorecard

    Once you have your four to seven, lay them out so they are quick to review: current value, normal range, prior period, and owner, all on one page. Start in a spreadsheet if that is the tool your team already uses. The important part is the decision and follow-up attached to each number.