Someone else proposed this use case but, to my eye anyway, bars would be considerably quicker and easier to read:

Really excellent. Nice work, @shrikhalpada.dev .

While I (thank god) haven't had to do a lot of hands-on work w Power BI, I've seen enough to know that it would be soul-destroying for anyone who cares about making effective charts.
I'm sometimes asked to adapt my courses to Power BI's limitations; my answer: www.linkedin.com/pulse/why-wo...

So, all dashboards should be ignored?

Nice. I have yet to find a good use case for radar graphs, apart from some highly specialized applications in which the audience thinks of the data as "circular," e.g., wind roses.

Agreed. I cover this situation in my "Practical Charts" course and book:

The dumbbell version would address the "steep slopes" perception issue, but it adds visual busy-ness and I'm not sure it makes the deviations between both series any more salient. The line chart also communicates that one series was always lower than the other at a glance...

Love this.
(...though the minimalism-fascism connection feels like a bit of stretch, IMHO.)

@duvekot.bsky.social I see your point but, again, pros and cons. If you only show deviation vals, the scale of the "lag" is lost. In a chart like that, it could be that, e.g., in the grand scheme of things, Boeing is only lagging Airbus by a tiny amount relative to total sales, or it could be huge.

@duvekot.bsky.social Also a viable option, yes. No color associations needed, but the trade-off is that the chart is visually busier with each category name listed four times (and yet busier with all 20 quantitative values labeled instead of a quant scale with 4 or 5 value labels). Pros and cons...

@mjskay.com @frank.computer
🤣 Here's my version: