
In 1908, the British Olympic cycling team won seven gold medals. Best in the world, no contest. Then they won nothing for the next 72 years.
By 2003, someone finally asked what changed. Turns out, nothing dramatic; no genius hire, no miracle strategy. They just started obsessing over the small, boring stuff. Hand-washing time went from 10 seconds to 2 minutes, and team illness dropped from 80 sick-days a year to 4. They swapped mattress springs for cotton so athletes slept better. That's it. That's the whole unlock.
By 2012, they were setting world records and winning the Tour de France for the first time ever.
We opened the recent SpotDraft x Law Ninjas webinar with this story, because it's basically the plot of every in-house legal team that's ever tried to scale. You don't get a high-performing team by working harder or turning contracts around faster. You get one by fixing the unglamorous, structural stuff nobody wants to spend a sprint on.
We got three GCs in a room; Preseedha Premnath, (General Counsel, Stellaris Venture Partners), Swati Soni, (Senior Legal Counsel, myZoi - Financial Inclusion Technologies), and Pooja Bedi, (Chief Counsel – India, Mondelez International) moderated by Shailesh, Regional Sales Head at SpotDraft); to talk about what actually separates a legal team that's performing from one that's just busy. Here's what came out of it.
Turnaround time was never the metric. It just felt like one.
Every legal team gets measured on speed at some point. How fast contracts move, how quickly you reply, how many you close in a quarter. All three panelists said the same thing, more or less: that's an input, not an outcome. It tells you nothing about whether the work was any good.
Swati put it simply; a missed regulatory nuance costs her fintech far more than a contract sitting an extra day for review. If the business only felt the speed of legal, that was actually a red flag, not a win.
Pooja's line was the sharpest one of the session: if your team is only getting complimented on how fast they turn things around, you're still in the build phase. If people are celebrating the impact instead, you've made it sustainable.
That distinction matters even more when you start measuring contracting efficiency, because the point of tracking speed isn't to glorify turnaround time; it's to expose bottlenecks, prove business impact, and improve the system behind the work.
Build mode and sustain mode need completely different playbooks
This was the real spine of the conversation. Everyone's chasing "high performance," but almost nobody separates the two very different jobs of getting there and staying there.
You're still in build mode if:
- Only 2-3 people actually know how anything gets done
- The team runs on tribal knowledge instead of documented process
- People go to the same one or two seniors for everything, regardless of team size
You're in sustain mode when:
- People across the whole team are empowered to make calls independently — not escalating everything up
- Nobody is a single point of failure (Swati's team documented literally everything specifically so a two-week mandatory leave wouldn't stall the business)
- Impact gets celebrated, not speed
Pooja said it best: if you've got 15 people on your team but everyone still funnels through the same three, you haven't built a high-performing team. You've built a bottleneck with headcount.
This is also why leaders trying to scale legal teams need more than extra hires. Without clear ownership, coaching, and systems, growth just creates a larger version of the same chaos.
The five things that actually hold a sustainable legal team together
Prasidha broke it down into five pillars, and the other two panelists kept independently landing on the same ones from different angles:
- People: invest in the right hires, then make it everyone's job to build the people around them, not just the leader's.
- Process: templates, checklists, repositories, automation. Boring. Non-negotiable. This is also where templates, checklists, repositories, automation. Boring. Non-negotiable. This is also where AI tooling is doing real work now; Prasidha's team built an internal term sheet generator with Claude in about 10 minutes, something that used to need a dedicated legal-tech vendor. A strong contract playbook can turn tribal knowledge into repeatable judgment, while contract automation helps teams operationalize that structure at scale.
- Proactiveness: catching the regulatory or legal issue before the founder or business team even knows to ask. Reactive legal teams are always playing defense.
- Prioritization: and specifically, learning to say no. Swati's rule: when someone says something's urgent, she shows them everything else on her plate and asks which one they want bumped. That's not friction, it's clarity.
- Empowerment: giving people real ownership, not just tasks. Career growth in-house doesn't look like a law firm promotion ladder, so leaders have to create other ways for people to feel like they're moving forward.
Legal doesn't need to earn a seat at the table anymore. It needs a new pitch.
One thing all three agreed on, unprompted: the old positioning; "look, we're business enablers, give us a seat at the table"; is done. That fight's over. Legal already has the seat.
The new job is different. It's aligning your incentives with the business's actual commercial goals, the same number the sales head or the CEO is chasing, instead of measuring yourself on contracts closed or average turnaround. And it's translating legal risk into language the business actually feels: not "this indemnity clause is uncapped," but "this is what it costs us if it goes wrong."
Prasidha's advice for pushing back effectively: you can only say no with conviction once you can explain the actual cost of saying yes. Pooja added the flip side, be a little less risk-averse, take measured risks alongside your business teams, and you won't need to sell yourself at all. You'll just be the first call when someone has an idea.
The takeaway
None of this is about working harder or moving faster. It's marginal gains, legal-team edition: fix the process, document the knowledge, decide what you're going to stop doing, and let the outcomes, not the turnaround times, do the talking.
If you're building a legal team right now and everything still runs through you personally, that's not a performance problem. That's a design problem. And it's fixable a lot faster than seven decades.

