The right visualization makes data obvious. The wrong one makes it confusing. clariBI includes over 24 widget types, and choosing the right one depends on what question you are trying to answer, how much data you have, and who will be reading the dashboard. This guide covers every widget type available, explains the specific situations where each one works best, and shows you how to avoid the most common visualization mistakes.
KPI and Summary Widgets
These widgets display single values or small sets of numbers. They answer the question "what is the current state?" at a glance.
KPI Card
A single number with an optional comparison indicator (up/down arrow with percentage change). Use this for metrics that stakeholders check daily: revenue, active users, open support tickets, conversion rate.
When to use: You have one important number that needs to be visible the moment someone opens the dashboard. The audience does not need historical context on this widget—they need the current value fast.
When to avoid: When the number needs context to be meaningful. A KPI card showing "412" with no comparison or trend is just a number floating in space. If you cannot add a comparison (vs. last period, vs. target), pair the KPI card with a trend line below it.
Scorecard
A grid of multiple KPIs shown together, typically 3-6 metrics in a row. Each cell shows a metric name, current value, and trend indicator. Use this for executive summary rows at the top of a dashboard.
When to use: You need to show 3-6 related metrics in minimal space. Common pattern: revenue, expenses, profit, margin—all in one row at the top of a financial dashboard.
When to avoid: More than 8 metrics in a scorecard becomes unreadable. If you need that many KPIs, split them into logical groups with labels.
Gauge
A semicircular or circular meter showing progress toward a target. The needle or fill level indicates where you are relative to a defined goal.
When to use: Metrics with a clear target: quota attainment, budget usage, capacity utilization. The gauge immediately shows "are we on track?" without requiring the viewer to compare numbers.
When to avoid: When there is no meaningful target or upper bound. A gauge showing revenue with an arbitrary maximum is misleading. Also avoid gauges for metrics that can exceed 100%—the visual breaks down.
Trend and Time Series Widgets
These widgets show how metrics change over time. They answer the question "what is the trend?"
Line Chart
The default choice for time series data. A continuous line connects data points across a time axis. Supports multiple series for comparison.
When to use: Showing trends over time for continuous data. Revenue by month, daily active users, temperature readings. Works well with 1-5 series on the same chart.
When to avoid: More than 5-6 lines on one chart becomes a tangle. If you need to compare many series, consider small multiples (separate charts with the same scale) or a heatmap.
Area Chart
Like a line chart but with the space below the line filled in. Stacked area charts show how parts contribute to a total over time.
When to use: Showing composition over time. Revenue by product line (stacked), where you want to see both the individual trends and the total. Also good for showing volume or magnitude when a line chart feels too thin.
When to avoid: Stacked area charts with more than 4-5 categories become hard to read because the middle layers distort. Non-stacked area charts with multiple series create overlapping fills that obscure each other.
Sparkline
A tiny inline chart—typically shown inside a table cell or next to a KPI value. No axes, no labels, just the shape of the trend.
When to use: Adding trend context to a number without taking up dashboard space. A table of products with a sparkline column showing the 30-day sales trend for each row gives quick visual context.
When to avoid: When viewers need to read precise values from the chart. Sparklines are for shape and direction, not for exact numbers.
Candlestick Chart
Shows open, high, low, and close values for each time period. Originally designed for stock prices but useful for any metric with a range.
When to use: Financial data where the range within each period matters: stock prices, bid-ask spreads, daily price ranges for commodities.
When to avoid: Most business metrics do not have OHLC components. Do not force non-financial data into this format.
Comparison Widgets
These widgets compare values across categories. They answer the question "how do these things compare?"
Bar Chart (Vertical)
Rectangular bars with heights proportional to the values they represent. The most versatile comparison chart.
When to use: Comparing values across categories: revenue by region, sales by rep, tickets by priority. Works for 2-20 categories. Grouped bars compare sub-categories; stacked bars show composition.
When to avoid: Time series data where the continuous nature of time matters—use a line chart instead. Also avoid when category labels are long (use horizontal bars).
Bar Chart (Horizontal)
Bars extending from left to right. Functionally identical to vertical bars but better for certain layouts.
When to use: When category labels are long (city names, product names, employee names). Horizontal bars give labels room to breathe. Also good for ranked lists where the natural reading order (top to bottom) matches the ranking.
Grouped Bar Chart
Multiple bars per category, grouped side by side. Each sub-group uses a different color.
When to use: Comparing two or three metrics across categories. Revenue vs. cost by department, this year vs. last year by month.
When to avoid: More than 3 sub-groups per category. The bars get too thin and the comparison breaks down.
Radar Chart
Multiple axes radiating from a center point, with values plotted on each axis and connected to form a polygon. Also called a spider chart.
When to use: Comparing an entity across multiple dimensions simultaneously: a product rated on price, quality, speed, support, and features. Works well for 5-8 dimensions. Good for showing balance or imbalance across criteria.
When to avoid: When dimensions have different scales unless you normalize them first. Also poor for precise comparisons—it is hard to judge exact values on radial axes.
Bullet Chart
A bar chart variant that shows a single measure against a target and qualitative ranges (poor, acceptable, good). Compact and information-dense.
When to use: Showing progress against a goal with context about performance ranges. Sales vs. quota, budget actual vs. planned, performance vs. SLA thresholds.
Composition Widgets
These widgets show how parts make up a whole. They answer the question "what is the breakdown?"
Pie Chart
A circle divided into slices proportional to each category's share of the total.
When to use: Showing proportions when you have 2-5 categories and one category is noticeably larger or smaller. Works for the "market share" type of question where the whole is meaningful.
When to avoid: More than 5-6 slices. Humans are bad at comparing angles. If you have many categories or similar-sized slices, use a horizontal bar chart sorted by value instead. Also avoid pie charts when the parts do not add up to a meaningful whole.
Donut Chart
A pie chart with the center removed. The hollow center can display a total or key metric.
When to use: Same situations as pie charts, but when you want to show the total number in the center. Slightly easier to read than pie charts because the viewer compares arc lengths rather than angles.
Treemap
Nested rectangles where the size of each rectangle is proportional to its value. Supports hierarchical data with categories and sub-categories.
When to use: Showing composition with many categories (10-50+) where a pie chart would be illegible. Storage usage by file type and folder, revenue by product category and sub-category, budget allocation across departments and line items.
When to avoid: When exact comparisons matter. It is hard to judge whether two similar-sized rectangles are truly equal. Use a bar chart for precision.
Waterfall Chart
Shows how an initial value is affected by a series of positive and negative changes. Each bar starts where the previous one ended.
When to use: Explaining how you got from A to B. Starting revenue plus new customers minus churn equals ending revenue. Starting budget minus expenses in each category equals remaining budget. Profit and loss bridges.
Distribution and Statistical Widgets
Histogram
Bars showing the frequency distribution of a continuous variable, grouped into bins.
When to use: Understanding the shape of your data: response time distribution, order value distribution, customer age distribution. Shows whether data is normal, skewed, bimodal, or has outliers.
Box Plot
Shows the median, quartiles, and outliers for a dataset. Compare distributions across categories with side-by-side box plots.
When to use: Comparing distributions across groups: response times by day of week, deal sizes by sales rep, delivery times by carrier. Shows central tendency, spread, and outliers in one compact view.
Scatter Plot
Points plotted on two axes, showing the relationship between two variables. Optional size dimension creates a bubble chart.
When to use: Exploring correlations: ad spend vs. conversions, employee tenure vs. performance rating, store size vs. revenue. Each point is one entity (one campaign, one employee, one store).
When to avoid: When you have very few data points (under 10) or when both variables are categorical. Scatter plots need continuous or ordinal data on both axes.
Specialized Widgets
Funnel Chart
A narrowing series of bars showing stages in a process and the drop-off at each stage.
When to use: Sales pipelines, marketing funnels, conversion flows. Any process where you start with a large number and want to show where people or items drop out at each stage.
Heatmap
A grid where color intensity represents values. Two categorical axes with color encoding the metric at each intersection.
When to use: Finding patterns across two dimensions: website traffic by day of week and hour, sales by product and region, error rates by server and time period. Good for spotting clusters and anomalies in large datasets.
Geographic Map
A map with data overlaid by region (choropleth) or by point (pin map). Color or bubble size represents metric values.
When to use: Any metric with a geographic dimension: revenue by state, customers by city, support tickets by country. The spatial relationship between data points matters and adds insight you would not get from a bar chart.
Table Widget
A data table with sorting, filtering, and optional conditional formatting. The most flexible widget for detailed data.
When to use: When viewers need to look up specific values, compare across many dimensions simultaneously, or see the raw data behind a summary. Also good for ranking lists and detail views that complement summary charts.
When to avoid: As the only widget on a dashboard. Tables are reference tools, not storytelling tools. Pair them with charts that highlight the key patterns.
Pivot Table
An interactive table that lets users drag dimensions to rows and columns, changing the aggregation on the fly.
When to use: When the audience is analytical and wants to explore data themselves. Pivot tables let users slice data without editing the widget configuration. Good for finance and operations teams who need to answer ad-hoc questions.
Choosing the Right Widget: A Decision Framework
When you are unsure which widget to use, answer these questions:
- What question does this widget answer? Write it down in plain language. "How has revenue changed over the last 12 months?" leads to a line chart. "Which regions generate the most revenue?" leads to a bar chart or map.
- How many data points are there? One number = KPI card. A few categories = bar chart or pie chart. Many categories = treemap or table. Time series = line or area chart.
- Who is the audience? Executives need summary widgets (KPI cards, scorecards, gauges). Analysts need detailed widgets (tables, scatter plots, pivot tables). Operational teams need status-focused widgets (gauges, heatmaps, funnels).
- What should the viewer do with this information? If they need to take action, make the action obvious. A gauge in the red zone with a clear target tells the viewer exactly what needs to happen.
Common Visualization Mistakes
- Using pie charts with too many slices. If you have more than 5 categories, switch to a bar chart. Human perception of angles is imprecise, and small slices become indistinguishable.
- Truncating the y-axis. Starting a bar chart at a value other than zero exaggerates differences. A bar going from 98 to 102 looks dramatic on a truncated axis, but the actual variation is tiny. Line charts can start above zero; bar charts should not.
- Using 3D effects. Three-dimensional charts look flashy but distort perception. The depth adds no information and makes it harder to read values accurately.
- Overloading a single chart. If a chart needs more than 30 seconds to understand, it has too much information. Split it into multiple simpler charts.
- Ignoring color accessibility. About 8% of men have color vision deficiencies. Do not rely on red vs. green alone. Use patterns, labels, or a color-blind-friendly palette. clariBI includes accessible color palettes by default.
- Missing chart titles and labels. Every chart needs a title that states what it shows, not just the metric name. "Monthly Revenue, 2024 vs. 2023" is better than "Revenue." Axis labels and units prevent misinterpretation.
How clariBI Helps You Choose
When you add a new widget to a dashboard, clariBI's AI recommendation engine suggests the most appropriate chart types based on your data shape. If you are working with a time series, it defaults to a line chart. If you have categorical data with a numeric measure, it suggests a bar chart. You can always override the suggestion, but the recommendations are a good starting point, especially for team members who are less familiar with data visualization best practices. For more details on widget configuration, see the dashboard widgets guide in the knowledge base, or explore the template marketplace for examples of well-designed dashboards using different widget combinations.
Conclusion
Every widget type exists for a reason, and the best dashboards use a mix of types matched to the questions they answer. Start with the question, consider the data shape, think about the audience, and then pick the simplest visualization that communicates the answer clearly. When in doubt, a well-labeled bar chart or line chart beats a fancy but confusing alternative every time. The goal is not to impress with chart variety. The goal is to make the data obvious so people can make better decisions faster.