Nightingale Rose Chart: What It Is and When to Use It

Cyclical data hides in tables. The Nightingale rose chart pulls it into the open, wrapping seasonal patterns around a circle where they become impossible to ignore. This guide covers what the chart actually is, when it earns its spot on a dashboard, how to sidestep the interpretation errors that trip up even experienced analysts, and how to build one in Excel or a dedicated BI tool.

Key takeaways for Nightingale rose charts

Here are the key points to confirm before you choose a Nightingale rose chart.

• Use this chart when: Your data has a natural cycle like months, hours, or compass directions, and you want to spot patterns rather than extract exact numbers.
• Avoid this chart when: Stakeholders need precise values, you have more than 12 categories, or your data has no inherent periodicity.
• Primary decision supported: Identifying which time periods or directional segments deserve deeper investigation based on relative size.
• Biggest interpretation risk: Viewers read radius instead of area, which makes large wedges look even more dominant than they actually are.
• Best alternative: A grouped bar chart handles precise comparisons better.

What is a Nightingale rose chart

Each wedge shares the same angle but varies in radius to show different values. The wedge's area represents the data point. Not the radius. This distinction matters more than most people realize.

Here's why: when every wedge uses the same angle, the wedge area grows with the radius squared. If you want accurate visual encoding, the radius needs to scale as the square root of your value. Because so many people skip over this, they end up with charts that exaggerate differences, sometimes by factors that would make a statistician wince.

You'll hear a few names for this chart depending on who you talk to.

• Coxcomb chart: The name Florence Nightingale used in her 1858 mortality analysis.
• Polar area diagram: The technical term in visualization literature.
• Rose diagram: Common in meteorology and geology for directional data.

Some people call it a Florence Nightingale pie chart. That's technically wrong since pie charts vary by angle rather than radius.

Most BI tools label this chart inconsistently. Plotly calls it a polar bar. Excel requires a doughnut chart workaround. Domo BI includes the Nightingale rose chart (polar area diagram) in its visualization library for interactive dashboards, so you can build it where the rest of your reporting already lives.

When to use a Nightingale rose chart

Your data loops back on itself. That's the first condition. Months wrap from December to January. Compass directions wrap from 359 degrees to zero. Hours wrap from 11:59 pm to 12:00 am.

No natural endpoint that connects to its start? Stick with a linear bar chart.

The conditions that make this chart shine:

• Cyclical categories: Six to 12 categories work best. Months, hours, and cardinal directions fit naturally.
• Pattern recognition goals: You want to spot which segments dominate across a cycle, not read exact values.
• Familiar audiences: Scientific, operations, or executive contexts where people have seen polar layouts before.
• Periodicity as a finding: You want to highlight that seasonal spikes exist, not just what the numbers are.

And the situations where it falls apart:

• Too many categories: With more than 12 categories, wedges get too narrow. Viewers start treating adjacent segments as equivalent when they're not.
• Precision requirements: Area perception is weaker than length perception. People can overestimate or underestimate by 20 to 30 percent (a margin that matters when budgets or staffing decisions hang on the numbers).
• Negative values: Radial encoding can't represent negatives. What would an inward wedge even mean?
• No natural cycle: Forcing noncyclical data into a circle implies a relationship between the first and last category that doesn't exist.

If you use it anyway, expect viewers to rank wedges by radius rather than area. They will also assume adjacent wedges are related even when your categories are nominal.

This is also a stakeholder-fit chart. BI analysts often pick it because it makes patterns hard to ignore in an executive review, especially when a table or standard bar chart buries the seasonality. The flip side? You may need to pair it with a bar chart (or add data labels) when someone asks, "Okay, but what was March exactly?"

Data requirements for a Nightingale rose chart

Shape the data correctly before you think about design. This is where BI teams save themselves from last-minute dashboard edits and those "can you resend that chart?" follow-ups that eat into actual analysis time.

At minimum, your dataset needs:

1. One categorical field that represents a cycle (month, hour, direction, department-by-month).
2. One positive numeric metric per category (counts, sessions, admissions, revenue).
3. A single, consistent grain, so each wedge represents the same unit of time or the same bin size.

If the metric is defined differently across teams, the chart turns into a confidence-killer. Governed metric definitions matter, especially in large enterprises where finance, sales, and operations dashboards can drift apart over time. In platforms that support a semantic layer and reusable metrics (like Domo BI), the same definition can feed every Nightingale rose chart, so "monthly sales" means the same thing everywhere.

For data engineers, the prep work is usually straightforward but easy to mess up under pressure: aggregate to the intended level, normalize category labels (no "Sept" vs "September"), and make sure the pipeline refreshes on schedule.

How to read a Nightingale rose chart

Your eye lands on the largest wedge first. Then you scan clockwise comparing adjacent wedges. Most people estimate magnitude by radius rather than area, which is where misreads begin.

Follow this sequence for accurate interpretation:

1. Check the center label or legend to understand what each wedge represents.
2. Look for scale markers. If the outermost ring isn't labeled, you can only make relative comparisons.
3. Compare wedge areas, not radii. A wedge that looks twice as tall is actually four times the value if the chart is built correctly.
4. Note the start position (usually 12 o'clock for months) and direction (clockwise is standard for time).
5. Look for clusters of large or small wedges to identify seasonal patterns.

Several perceptual biases distort how people read these charts:

• Outer-ring bias: Large wedges grab attention disproportionately because they occupy more peripheral space.
• Radius-as-value error: Without coaching, most viewers read radius as the metric.
• Adjacent-wedge conflation: People assume wedges next to each other are related even when categories are nominal.
• Missing baseline: Unlike bar charts, there's no horizontal axis to anchor zero.

Label the outermost ring value. Add callouts for peak wedges. For audiences unfamiliar with polar layouts, consider including a small inset bar chart. In an interactive dashboard, tooltips do a lot of the work here.

Nightingale rose chart examples

Florence Nightingale's original mortality diagram

The original Florence Nightingale graph showed deaths by cause (disease, wounds, other) across months during the Crimean War. Preventable disease deaths dominated every month. They peaked in winter. The circular layout made the repeating pattern undeniable.

A grouped bar chart would have shown the same numbers but without the cyclical framing that drove sanitation reform. Those reforms reduced mortality from 42.7 percent to 2 percent. That 40-point drop illustrates why the chart's persuasive power mattered: It wasn't just visualization, it was an argument for saving lives.

Monthly website traffic by channel

An e-commerce team plots sessions by acquisition channel across 12 months. The rose chart reveals that paid traffic dominates November and December while organic traffic spreads more evenly. A stacked bar chart would show the same totals but wouldn't emphasize the seasonal concentration as starkly.

Wind direction frequency

Meteorologists use rose diagrams to show how often wind blows from each compass direction. The circular layout matches the data's inherent structure. A bar chart with 16 directional bins would lose the spatial intuition that northwest winds dominate.

Patient admissions by department by month

A healthcare analyst tracks patient admission volumes across departments by month. A Nightingale rose chart makes the seasonal surges obvious, which is useful when operations leaders are trying to staff ahead of predictable peaks. This is also a nice fit for a live BI dashboard where leaders can filter by department and still keep the cyclical shape.

How to create a Nightingale rose chart in Excel

Excel doesn't have a native Nightingale rose chart. The workaround uses a doughnut chart, which encodes value as arc length rather than area. For quick presentations, this approximation works. For accurate area encoding, you need a helper column with square-root-transformed values.

If you're building this chart repeatedly for dashboards, a BI platform with a Nightingale rose chart option (like Domo BI) can save time and reduce manual formatting.

Step 1: Prepare the data

Create a table with Category (like months) and Value columns. Add a third column with the formula =SQRT(Value). This transformed column becomes your chart's data series.

Step 2: Insert the chart

Select the Category and transformed Value columns. Go to Insert, then Charts, then Pie, and select Doughnut.

Step 3: Configure the appearance

Right-click the chart and select Format Data Series. Set the doughnut hole size to zero percent. Adjust the angle of the first slice to position your start category. For January at 12 o'clock, set the angle to 270 degrees.

Step 4: Add labels

Add data labels showing the original values so viewers see actual metrics rather than square roots. Remove the legend if categories are labeled directly on wedges.

Step 5: Validate

Compare the largest and smallest wedges visually. If the largest value is four times the smallest, the largest wedge's area should appear roughly four times as large. If the ratio looks off, confirm you applied the SQRT transformation.

Using raw values without transformation creates a chart that encodes value as angle. That's technically a pie chart in polar form.

Doughnut charts don't support radial gridlines or axis labels. For dashboards that need frequent updates, a BI tool with native polar area support reduces manual formatting. If you need this chart embedded inside a customer portal or product experience, Domo Embed can render the same visualization with programmatic filtering and row-level security, so each account sees only its own data.

Alternatives to a Nightingale rose chart

Both rose charts and pie charts use area, but rose charts preserve category order around the circle while pie charts emphasize part-to-whole composition. Use a pie chart when the total matters. Use a rose chart when the sequence matters.

Radar charts connect points with lines, emphasizing shape and balance. Rose charts keep wedges discrete.

Best practices for Nightingale rose charts

These practices help the chart stay readable and reduce misinterpretation.

• Apply square-root scaling: Without it, area grows quadratically and exaggerates differences. A value of 100 vs 25 should look like a four-to-one area ratio, not 16-to-one.
• Limit categories to 12: With more than 12 categories, wedges get too narrow for reliable comparison.
• Start at a meaningful position: Place January at 12 o'clock for monthly data. Arbitrary start positions force viewers to hunt for orientation.
• Label the outermost ring: Without a scale reference, viewers can't anchor their estimates.
• Avoid stacking multiple series: Stacked rose charts make inner rings nearly invisible. Use small multiples instead.

If the chart is headed to an executive audience, do yourself a favor and add interaction or supporting detail. Tooltips, filters, and a companion bar chart can prevent the "radius-as-value" misread without turning the dashboard into a textbook. You'll notice that the best dashboards pair the visual punch of the rose chart with the precision of a simple table or bar chart sitting right next to it.

Limitations of Nightingale rose charts

Area perception is less accurate than length perception. People estimate bar lengths more precisely than areas. This isn't a flaw to fix. It's inherent to the chart type.

As covered earlier, this chart only works with positive values. If people will ask for the exact number for March, use a table or bar chart.

The chart also assumes equal-angle categories. If your categories have unequal importance or duration (months with different numbers of days), the equal-angle assumption can mislead. Consider normalizing values to a per-day basis when comparing months of different lengths.

In large organizations, there's also a trust issue that has nothing to do with geometry. If two teams build the same Nightingale rose chart with different metric definitions, you get two different stories. Central governance, access controls, and row-level permissions help prevent that, especially when the chart includes sensitive breakdowns like financial performance by region. It's happended many a time, and it's almost always a metric definition problem masquerading as a visualization disagreement.

Final thoughts

The Nightingale rose chart earns its place when data has a natural cycle and the goal is pattern recognition rather than precision. It makes seasonal spikes visually immediate in a way linear charts simply can't match.

Before choosing it, confirm three things: the data loops back on itself, the audience doesn't need exact values, and you have time to add proper scaling and labels. If any of those conditions fail, a grouped bar chart or small multiples will communicate more reliably.

And if you're a BI analyst who's tired of answering the same ad hoc "can you slice this by month again?" request, this chart can be a nice change of pace. Put it in a governed dashboard with consistent metrics, let people explore, and spend your time on the investigation the chart is pointing you toward. Then swap notes, templates, and dashboard do's and don'ts with peers when you join the Domo community.