How to master the skill of legal data storytelling

Ask a general counsel what their team achieved last quarter and you'll usually get a list: contracts reviewed, matters closed, policies updated.

Ask them to prove it moved the business forward, and the list stops working. Bullet points don't show trend, don't show risk, and don't answer the question every stakeholder is actually asking, which is: so what?

That gap — between having data and being able to tell a story with it — is what legal ops leaders increasingly call legal data storytelling. It isn't a reporting exercise. It's a communication skill, and like most communication skills, nobody teaches it in law school.

As one legal ops panel on the topic put it plainly: legal education doesn't prepare lawyers to capture, analyze or present data, even as businesses expect every function — including legal — to justify itself in numbers.

This article pulls together the practical playbook: why the skill matters now, where to start if you have nothing, how to structure intake so the data is usable later, and the traps that turn good data into a story nobody believes.

What "legal data storytelling" actually means

Legal data storytelling is the practice of turning legal ops data — contract volumes, contract cycle times, deviation rates — into a narrative that drives a specific business decision, rather than a report that simply describes activity.

It's increasingly treated as a core legal ops skill because in-house teams are now expected to justify headcount, process change and tooling spend with evidence, not adjectives.

Legal data storytelling vs dashboards

It's easy to conflate storytelling with dashboards, but they're not the same thing, and conflating them is one of the most common gaps in how legal teams approach this.

• A dashboard shows what happened.
• A story explains why it happened, what it means for the business, and what should happen next.

A chart showing "40% of requests came in with no deadline" is a dashboard. Turning that into "Team A treats every request as equally urgent, which means we can't prioritise properly... here's the education we need to run, and here's the process change that would fix it" is a story.

{{quote1}}

The most effective in-house teams frame this deliberately as a user story before they build anything — starting from "as a legal team, we want to understand X, so that we can Y" — because it forces you to define the audience and the outcome before you touch a spreadsheet. Skipping that step is why so many legal dashboards get built, glanced at once, and never opened again.

The underlying shift is really about legal moving from reactive documentation ("here's what we did") to proactive narrative ("here's what's happening, here's what it means, here's what we need from you"). That second version is what gets budget approved and headcount signed off.

Why does this skill matter so much for in-house legal?

Legal has historically been treated as a cost centre — a support function that exists to reduce risk, not to demonstrate value. But we know from speaking to our customers that the value delivered by legal is far greater than that, and often underreported.

Legal teams that want a seat at the table, next to revenue, product and marketing, need to speak that language too, not because storytelling is fashionable but because it's how modern businesses make decisions.

{{quote2}}

The anatomy of a legal data story

Every legal data story that actually changes a decision follows a version of the same shape:

1. Context. What did the audience already believe, or what did they ask? This is where you meet them, not where you educate them.
2. Complication. What does the data reveal that contradicts, sharpens, or complicates that belief? This is the moment of tension, the reason anyone should keep listening.
3. So what. What does this mean in terms the audience already cares about (revenue, risk, headcount, time)? Not "here's a chart," but "here's what this costs you if nothing changes."
4. Ask. What decision, specifically, should this change? A story with no ask is an anecdote.

Skip step 1 and you sound like you're reporting into a void. Skip step 3 and your audience sees a chart but not a reason to care. Skip step 4 and you've told a good story that nobody acts on, which, for this purpose, is the same as telling no story at all.

Want to see the skill gap fast? Watch how two people open with the exact same data.

The novice:

• Opens with the chart. "Here's request volume by category, last quarter."
• Shows everything they tracked. Tracking it felt like work worth showing.
• Ends with a summary. Not a decision.
• Treats every number as equally important. Ranking them feels presumptuous.

The expert:

• Opens with the stakes. "You asked why legal feels slow. Here's what's actually going on."
• Picks one number. The one that resolves the tension in the room. Cuts the rest.
• Ends with a named decision. "So the ask is X."
• Cuts anything that doesn't serve the point, even the stuff that took real effort to collect.

How to actually practise the skill of legal data storytelling

Treat it like any other craft you'd want to get better at: draft it, test it on a real audience, and revise based on what happened, not on whether you liked writing it.

1. Draft the story before you touch the data

‍Write the sentence you want your audience to say back to you after seeing your report. If you can't write that sentence in one line, you don't have a story yet, you have a topic. Only once that sentence exists should you go looking for the number that proves it.

2. Choose the smallest amount of data that supports the sentence

‍Most first drafts include everything, because leaving data out feels like waste. It isn't. A story buried under six charts is not six times more convincing than a story built on one. Cut until only the number doing the actual persuading is left.

3. Test it on one real stakeholder, not a template

‍Send the draft to the actual person whose decision you're trying to change, or better, say it to them out loud, before it goes in a deck. Watch where they lean in and where they check their phone. That reaction is your feedback loop, and it's far more useful than any dashboard best-practice guide.

4. Revise based on what didn't land, not on what you'd add

‍The instinct after a flat reaction is almost always to add more context or more charts. Resist it. The far more common fix is to cut earlier and get to the complication faster, because most legal data stories die from throat-clearing, not from missing information.

5. Reuse the shape, not the content

‍Once a story structure works (context, complication, so what, ask) on one audience, the same shape will work on the next quarter's numbers, or a different stakeholder entirely. What changes each time is which single number you choose to carry the story, and the implications on that particular audience.

Where the data work fits in

None of this replaces the practical groundwork of clean legal ops data, structured intake forms, honest metrics that resist gaming, deviation rates and turnaround brackets tracked consistently over time. That groundwork still matters. But it's the material you sculpt with, not the sculpture itself.

A team with immaculate contract dashboards and no narrative instinct will still lose the argument to a team with messier data and a sharper story, because decision-makers respond to stakes and resolution, not to spreadsheets.

On a legal ops panel discussion where Claudia and Stephanie compared notes on exactly this, both described starting small and unglamorous rather than starting with a story.

Claudia's team began not with a dashboard but with a single number: how often signed contracts deviated from the standard template, tracked against a threshold that triggered escalation when crossed.

Stephanie's team started even rougher, repurposing a basic IT ticketing tool never designed for legal, and building three simple intake forms just to prove how much work was actually coming in. Neither started with a story.

Both started with one honest number, tracked consistently, until there was enough of it to say something.