Understand, design and use dashboards without overcomplicating them.
A dashboard is a screen that brings important information together so you can quickly understand what is happening.
Think of a car dashboard:
Speed Fuel Temperature Warning
↓ ↓ ↓ ↓
You don't need every detail.
You need the information that helps you drive.
A business dashboard works the same way.
1. What Is a Dashboard?
A dashboard turns data into information you can understand quickly.
Instead of looking at:
1,248 sales records
3,582 customers
9,421 transactions
you might see:
Sales Customers Orders
MWK 8.2M 3,582 1,248
The goal is:
See → Understand → Act
2. What Should a Dashboard Show?
Only information that helps someone make a decision.
Common examples:
Sales
Today's Sales
Monthly Sales
Orders
Average Order Value
Customers
New Customers
Active Customers
Returning Customers
Operations
Completed
Pending
Overdue
Finance
Revenue
Expenses
Profit
Outstanding Payments
3. Start With the Questions
Don't start by asking:
"What charts should I put on my dashboard?"
Start with:
"What do I need to know?"
For example:
Business owner:
Are sales increasing?
Operations manager:
Which orders are still pending?
Finance manager:
Who hasn't paid?
School administrator:
How many students are enrolled?
The questions determine the dashboard.
4. KPIs
A KPI (Key Performance Indicator) is an important measurement used to understand performance.
Examples:
Revenue
Profit
Sales
Customers
Orders
Attendance
Response Time
A dashboard might show:
REVENUE
MWK 8.2M
↑ 12% this month
Don't fill a dashboard with dozens of KPIs.
A few useful numbers are better than a wall of numbers.
5. Numbers vs Charts
Use a number when you need a quick answer:
TOTAL SALES
MWK 8.2M
Use a chart when you need to see a pattern:
Sales over the last 12 months
Use a table when people need details:
Customer | Order | Amount | Status
Use a chart + number when both the value and trend matter.
6. Common Charts
Bar Chart
Good for comparing things.
Sales by Product
A ██████████
B ██████
C ████
Line Chart
Good for trends over time.
Sales
│ ╱──╲
│ ╱─╯
│──╯
└────────────
Time
Pie / Donut Chart
Useful for simple proportions.
Don't use one when there are dozens of categories.
Table
Best when people need exact values or individual records.
7. Dashboard Layout
A simple dashboard often works well like this:
┌──────────────────────────────────────────┐
│ DASHBOARD │
├──────────┬──────────┬──────────┬────────┤
│ Revenue │ Orders │ Customers│ Profit │
├──────────┴──────────┴──────────┴────────┤
│ │
│ Sales Trend │
│ │
├──────────────────────┬───────────────────┤
│ Sales by Product │ Recent Orders │
│ │ │
└──────────────────────┴───────────────────┘
Put the most important information first.
8. Filters
Filters allow users to change what they are looking at.
Common filters:
Date
Branch
Product
Region
Department
Customer
For example:
Date: [September 2026]
Branch: [Blantyre]
The dashboard then updates to show only that information.
9. Keep It Simple
A beginner dashboard does not need:
20 charts ❌
50 KPIs ❌
Animations ❌
Fancy graphics ❌
Every piece of available data ❌
Instead:
3–6 important KPIs
1–3 useful charts
1 useful table
A few useful filters
Clarity beats decoration.
10. Data Behind the Dashboard
A dashboard is only as good as the data behind it.
The basic flow is:
DATA
↓
CLEAN
↓
CALCULATE
↓
DISPLAY
↓
DECISION
For example:
Sales Records
↓
Calculate Total Sales
↓
Show Sales KPI
↓
Owner sees sales are falling
↓
Investigate
A beautiful dashboard with bad data is still a bad dashboard.
11. Dashboard vs Report
They're related, but not exactly the same.
Dashboard
What's happening right now?
Designed for quick monitoring and decisions.
Report
What happened, and what are the details?
Usually contains more explanation and detail.
Think:
Dashboard → Quick understanding
Report → Detailed analysis
12. Choose the Right Tool
You don't always need custom software.
You can create dashboards with tools such as:
Excel
Google Sheets
Power BI
Looker Studio
Tableau
Custom Web Applications
Start with the simplest tool that can do the job.
13. Dashboard Design Checklist
Before publishing a dashboard, ask:
□ Who is going to use it?
□ What decisions will they make?
□ Are the most important numbers easy to see?
□ Are the numbers accurate?
□ Are the charts easy to understand?
□ Can users filter the information they need?
□ Is there unnecessary information?
□ Does it work on the intended screen/device?
The Golden Rule
A dashboard is not a collection of charts.
It is a tool for helping someone understand something and decide what to do next.
Remember:
QUESTION
↓
DATA
↓
INFORMATION
↓
INSIGHT
↓
ACTION
Build the dashboard around the decision—not around the data.
