Operational, tactical and strategic dashboards: matching purpose to audience

One Storm, Three Questions. It's two in the morning and a winter storm has just split three water mains across the city. The dispatcher needs to know which crew is closest to the break on Elm Street, right now. The operations supervisor wants to see whether this week is worse than last week. And tomorrow morning, the city manager will ask whether the aging pipe replacement program is actually working. It's the same data and the same breaks, but these are three very different questions. If you hand all three people the same screen, at least two of them will struggle to find their answer. This lesson is about avoiding that.

What You Will Learn. By the end of this lesson, you'll be able to do three things. First, tell the three main types of dashboard apart: operational, tactical and strategic. Second, match each type to the people who use it and to the time horizon they care about. Time horizon just means how far ahead or back someone looks when they make a decision, like minutes, days or years. Third, take a single layer of water main breaks and sketch the right view for each person. Everything here comes before you open ArcGIS Dashboards, so you build the right thing the first time.

Three Families of Dashboards. Dashboards fall into three broad families, and the easiest way to tell them apart is by who's watching. Operational dashboards serve dispatchers and crew leads, people who act within minutes. Tactical dashboards serve supervisors and analysts, people who adjust staffing, schedules and priorities over days or weeks. Strategic dashboards serve executives and elected officials, people who set budgets and policy over months and years. Think of a hospital. The emergency room nurse, the ward manager and the hospital board all care about patients, but each one needs a very different view to do their job well.

Operational: What Is Happening Now?. An operational dashboard answers one question: what is happening right now, and what do I do next? The data is live, often refreshing every minute or so. The map is usually the biggest element on the screen, because location drives action. You'll see lists of active incidents and indicators. An indicator is simply a single big number, like the count of open breaks, and it can turn red when it crosses a threshold. During a storm, the emergency operations center watches power outages and road closures this way. For our water utility, the dispatcher sees every open break, its status, and which crew is assigned.

Tactical: How Are We Doing This Week?. A tactical dashboard steps back a little. It asks: how are we doing, and where should we shift effort? The time window is days or weeks, and refreshing hourly or even daily is usually enough. Charts take up more room here, because comparison matters more than location alone. A supervisor might look at service requests closed per crew, or average repair time by district. Is the North zone getting more breaks than usual? That kind of pattern is invisible on a live map, but it jumps out on a bar chart comparing this week with last week.

Strategic: Are We Meeting Our Goals?. A strategic dashboard looks at the long game. Its users are executives, council members and boards, and they check it monthly or quarterly, not every hour. The data behind it usually refreshes monthly or even less often. It shows a handful of key performance indicators, often called KPIs. A KPI is simply one number that tells you whether you're hitting a goal, like a fitness tracker showing your steps against your daily goal. For the water utility, that might be total breaks per year, the percentage of pipes replaced, and average customer outage hours. The map, if there is one, usually summarizes by district rather than showing single breaks.

Worked Example: One Layer, Three Views. Let's sketch all three views from one small layer. It holds eight water main breaks, and each break has a zone, a status and a date. Today is September twenty-eighth, 2026. For the dispatcher, we count the breaks whose status is open. There are three: one in South and two in East. So the operational sketch is an indicator showing three open, next to a list of those three breaks with their crews. For the supervisor, we keep only the breaks from the last seven days and count them per zone. East has two and South has two, so the tactical sketch is a bar chart with one bar per zone. For the city manager, we count the breaks per year. There were three in 2025 and five so far in 2026, so the strategic sketch is a serial chart with one point per year. Same layer, three very different views, and each one answers its own person's question.

Three Questions to Pick the Type. Before you build anything, ask three questions. First, who will look at it? Write down an actual job title, not "everyone." Second, how quickly must they act on what they see? If the answer is minutes, you're building an operational dashboard. If it's days or weeks, you're building a tactical one. If it's months or longer, you're building a strategic one. Third, what decision does this screen support? If you can't name a decision, pause and talk to the user again. A dashboard that doesn't support a decision quickly turns into wallpaper that nobody reads.

Elements That Fit Each Type. ArcGIS Dashboards gives you the same building blocks for every type, but each type leans on different ones. Operational dashboards lean on the map, a list of active features, and indicators whose color changes past a threshold. Tactical dashboards lean on serial charts, which are bar or line charts over categories or time. They also use pie charts to show each zone's share of the total, plus selectors so a supervisor can filter by zone or crew. Strategic dashboards lean on large indicators, gauges and serial charts that show long trends over years. Refresh settings follow the type too. Choosing the type first means half your layout decisions are already made for you.

Common Mistake: One Dashboard for Everyone. The most common mistake is trying to build one dashboard that pleases everyone. It starts innocently: a live map for dispatch, then someone asks for weekly charts, then the director wants yearly KPIs. Soon you have twelve panels on one screen. The dispatcher has to hunt for the map, and the executive is buried in individual breaks they don't care about. The fix is simple. Build one dashboard per audience, and let them all read from the same hosted feature layer underneath. A hosted feature layer is a single copy of your data stored in ArcGIS Online that many maps and dashboards can read. You maintain the data once, and each person gets a screen built around their own decisions.

Recap. Let's recap. Operational dashboards help people act in minutes, tactical dashboards help them adjust over days and weeks, and strategic dashboards help them steer over months and years. Always start from the audience and the decision they make, not from the widgets you'd like to try. And remember that one well-prepared data layer can feed a separate dashboard for each audience. That's exactly why the next lessons focus on hosted feature layers, clean data and web maps. They're the shared foundation underneath every one of these views.

Your Exercise. Now it's your turn. Pick one scenario you know well, such as utility outages, 311 service requests, or traffic incidents. Write down one real person for each dashboard type, using a job title. For each person, write the one question they ask most often, how often the data needs to refresh, and the three dashboard elements that would answer it best. Keep it to a single page. Bring it to the next lesson, because we'll look at the ArcGIS Online content that would sit behind all three of those dashboards.