Podcast

Close Ups Episode 4: Chris Potter

‍‍‍This interview is part of the Litify Close Ups series, where we get behind the title and into the mindset of the legal community’s boldest leaders. Hosted by Litify’s CEO, Curtis Brewer, each episode features a leading voice in the legal operations community and covers career journeys, technology, trends, and how leaders are adapting their teams and operations to stay ahead. Subscribe to this series on Apple Podcasts or Spotify to be the first to know about future releases.

Recently, Curtis sat down with Chris Potter, Legal Operations Executive, to discuss building global legal operations from the ground up, driving technology adoption and ROI, and the future of AI in legal.

Can you tell us about your recent experience and the scope of your role within legal, the responsibilities you've carried, and the teams you've overseen?

I’ve worked in legal for 25 years, and most recently, I had a team of 11 direct reports. Two of those direct reports were located in EMEA, and the rest of the team was centralized in the US, where our world headquarters and the core of the law department are based.

Broadly, I also had indirect reporting lines from Latin America and Asia Pacific, as those regions were scaling up in anticipation of adopting more homogeneous, universal ways of working globally. Within that whole context, I was also working with and understanding our regional teams and the roles our business partners play in procurement, finance, and HR. It took a lot of coordination across many different global nodes to tie everything together, make sense of it, and ensure everyone was operating within expectations. You have your anticipated vision of where you're headed, but there's also the reality of where you are now, and the challenge is meeting people where they are while pulling them along toward that unified vision.

Can you tell us about the arc of your career and how you navigated your way into this kind of role?

When I started, I worked for a consulting firm and had some experience assisting with insurance defense matters under the guidance of outside counsel. That was really my only tie to the legal field, per se. However, I was looking for a change because consulting and constant travel were becoming a bit old, especially with my growing family.

I also have an MBA, so the combination of relevant experience and background capability made me a strong fit when the position was described, and I was fortunate to be hired. At the time, the title was something like "Vendor and Outside Counsel Specialist" — a long, rambling name because the term "legal operations" didn't even exist yet. 

There wasn't a broader context of shared systems, standardized ways of working, or a guiding light for how the department should support the business. At the time, the prevailing mindset was that attorneys already knew how to do their jobs because they were attorneys. That wasn't untrue, of course, but it completely ignored infrastructure, efficiency, and operational workflows. It was a bit of the Wild West back then.

What was the seed in those early days that has now grown into a more holistic view of how legal can best support the business?

This may or may not be a telling data point, but my first year in the role was the first year we exceeded $100 million in litigation spending. I don't know if that can be attributed to me or if I just stepped in at the right time — and I think I was the only one who really paid attention to it. Coming from litigation alone gave me a lot to work with, and I forged a path by treating that focus as an incubator of sorts.

We were doing a lot of innovative thinking and facing plenty of challenges. The team had just installed a new matter management system, and within my first 12 months, I brought in an eBilling system. At the time, most of our firms were asking, "What is this? What is eBilling?" There were only a few players on the market. To add to the complexity, our new matter management system didn't have its own eBilling module, and I couldn't just throw away the system they had just implemented. I had to find an eBilling platform that would play nicely with it.

Back in 2003, things like APIs were scarce, if they existed at all, so handling those integrations was a heavy lift. I didn't know the technical details, I just told IT, "Do whatever you need to do, just help me make this work," because the conversation was really about how this could enable the business. We built up from there: once we had eBilling running for litigation, we asked why we shouldn't expand it to the general law department, and then IP wanted to get on board. Because of the siloed structure, I had to prove we could make it work, make it look and feel good, and then expand it out from there.

How have you continued to use that incubator approach throughout your tenure to gain buy-in, adoption, and budget for new tools?

For me, that became a very organic way of operating. One of the hardest things to do is ask everyone to adopt something when nobody has any experience with it. How do you demonstrate knowledge and expertise in what you're talking about, or point toward results you haven't experienced yet? It really has to be a "try before you buy" approach.

I was given a lot of latitude to build out these systems because, as external legal spend grew, our business partners — particularly in corporate finance — wanted strong controls in place. Cost containment was the primary emphasis, so our focus was developing systems that were both useful and usable to drive toward that goal. Whether it was direct, like implementing eBilling rules, or indirect, like building systems that produced data and intelligence we could leverage for other initiatives, everything collectively drove toward the same objective: achieving cost containment through better decision-making and giving people the insights they needed to make informed choices.

Have you found a common thread of what helps make the technology you implement truly drive ROI? What tends to work and what tends to not work?

I think of two guiding principles. The first is that you can't build something that only works for you without thinking about the broader audience. You might have a solution that works in theory and assume you just need everyone else to get on board. You can roll out a tool and call it change management — forcing users onto the system under the threat of noncompliance — but that doesn't create a good client experience or meaningful adoption. Force isn't a way to engender creative or forward-thinking behavior.

The second principle is that whenever you implement something, it is critical to have someone who can speak to both sides of the fence — the business and technology sides. When people are siloed in one camp or the other, you end up with massive gaps that slow execution or result in a final product that looks and functions completely differently from what was expected. It also creates huge hurdles for communication and change management.

While I'm less of a technology-centric person, I've always stayed open to learning the terms of art and technical concepts. For me, the biggest priority was ensuring the people executing the technology truly understood the business requirements. It's not enough to just say, "We handle matters," and let the tech team assume a matter is basically like a purchase order. You have to explain that there are claims, third-party subpoenas, litigation, and all kinds of unique dimensions. Once you get into that nuance, the heavier lift happens: the tech team has to ingest and appreciate those details so they can stand up a system that actually meets business expectations.

What have you seen around how expectations of legal have changed within the business?

Setting AI aside — because that could easily fill 10 more podcasts — the trajectory and role of the law department within a company has definitely grown and expanded. There is this concept of the "T-shaped attorney," which means having a broad set of skills alongside deep subject-matter expertise. For example, a regulatory attorney supporting medical devices knows the ins and outs of the FDA, disclosures, and privacy, but they are also expected to manage their own budget and think proactively about what will benefit the business.

One of the biggest challenges and migrations of thought with the law department and the way that the attorneys service the business is this idea that you can't just be the House of No. You can't walk into a room and say something is a bad idea without offering solutions and alternatives.

It's one thing to give guidance and share your recommended approach, but that's only half of the equation. If you are truly focused on business enablement, the answer isn't "no" — it's "here is a different way you could approach that." You really need to be more invested in the solutioning side rather than just reacting to the solutions that are provided to you.

That shifts how attorneys show up: it's not enough to just list dos and don'ts, because those recommendations impact marketing, budgets, strategy, and a whole collective universe of business decisions. Today, there is a much broader expectation for the attorney to act as a true business partner rather than just a legal sounding board.

How has the relationship with outside counsel and outside legal spend evolved between the internal and external teams?

When I started, outside counsel was essentially sacrosanct. In-house attorneys chose the firms they worked with, no questions asked — they got results, the company was protected, and whatever it cost was simply accepted as the cost of doing business. At the time, that made sense because we didn't have the systems or processes to support a more nuanced understanding of requirements and expectations. Technology is what really enabled us to think differently and execute strategies like preferred panels and alternative fee arrangements (AFAs).

Within that context, however, I've always been an advocate that relationships with outside counsel still matter. My definition of a strong relationship isn't "that's the person I went to law school with." A true relationship is with someone who understands our business, is attuned to our needs, and already grasps our context and values when we bring them a problem. That foundation informs legal advice and strategy that best accommodates the business.

We have to recognize that legal work falls into different tiers — roughly three levels: high-stakes "bet-the-company" matters, important middle-ground work, and routinized lower-tier work that can go to alternative legal service providers. You have to be thoughtful from both a business and cost-containment perspective about how you categorize and assign that work. Still, particularly in those top two tiers, you can never lose sight of investing in strong partnerships. These are bright, motivated people, and you want them viewing you as a client they genuinely want to help—not just a paycheck or a box to check. You want outside counsel going to bed thinking about your business because they care about getting good results for you. That kind of partnership absolutely matters.

Are there specific places in legal or use cases that you get really excited about transforming with AI?

There are so many, and predictive analytics is one of the biggest areas I think about. It's actually something we experimented with a long time ago. Back around 2006, we brought in a consultant who built a database tool that would take historical matter management and spend data and filter by variables like matter type, whether we were the plaintiff or defendant, and which state the case was in to spot commonalities. It might tell you that you had 47 similar cases, or one, or none, helping you associate patterns and anticipate what good looked like.

Fast-forward to today, with AI and predictive analytics, and we can take that concept much further, provided we get the fundamentals right. You can never lose sight of the fact that you need clean, well-structured data and consistent nomenclature in your systems to execute on that future state.

When you have that foundation, predictive analytics becomes hugely beneficial. Right now, I view it as a valuable second opinion rather than something dictating your exact moves — relying on it blindly introduces too much risk. Instead, it acts like an enhanced early case assessment (ECA). Combined with automation that improves how you collaborate with outside counsel, AI can deliver a stream of filtered, categorized, and nuanced information that meets you where you are, helping you make much better decisions about where to go next.

Are there any places where you think the vision should be full automation without a human in the loop?

I actually think we should view all of it through the lens of full automation — not by throwing common sense out the window, but by using it as our North Star. The goal is to build robust, reliable systems that enable rapid, balanced decision-making, whether that drives efficiency, effectiveness, or simply frees up time to focus on higher-order priorities.

The key is treating the machine as a collaborator. You want AI to take on the heavy lifting, but in a collaborative way where it comes back and says, "Here is what I'm seeing, and here is my rationale." That's no different than how you work with human colleagues. Once you understand how a colleague thinks and operates, their perspective carries weight and credibility.

It's the same with AI. If a system demonstrates repeated consistency and nuance — for instance, auditing invoices against outside counsel guidelines and recognizing that the exact same time entry carries a different context in a product liability matter versus a government investigation — that's when you start building real trust. Trust comes over time by proving the system can do things the right way repeatedly. To me, keeping a "human in the loop" isn't about arbitrary checkpoints; it means that once the system proves itself, you simply check in less often. That said, you should always verify. Even the most robust, proven systems still require periodic checks. It's the classic "trust, but verify" approach.

When it comes to adopting AI tools, are you seeing anything different around what it takes to create true adoption and trust?

The challenge always comes back to user experience. When you mandate a clunky tool purely for compliance, it becomes a hurdle people have to jump over just to get back to their real jobs. Mandates don't motivate forward-looking thinking. If you want true adoption — especially when your goal is enabling attorneys to be better business partners — the best systems are the ones that lean into how people actually want to work.

To support that future vision, the technology also needs to be able to grow and expand, which comes down to interoperability. No single system is going to do everything, nor should you expect it to, because an all-in-one platform can quickly become an all-in-one failure point. What you want are strong points of convergence and a single point of entry to move smoothly from challenge A to decision Z.

I look at it like an ecosystem — for example, having Litify built on Salesforce. A good corollary is Microsoft in the 1980s, when they opened up their platform so other developers could build compatible products on top of it. Knowing that Salesforce invests heavily in its architecture and has a massive developer network, combined with our own in-house expertise, changes the equation. When you adopt a platform like Litify that plays nicely with other tools, you aren't forced into compromises. If a system doesn't handle one specific niche, you can easily integrate something that does, allowing you to achieve your business goals without roadblocks.

Are there any hype cycle areas of AI that you don't believe in or think are a flash in the pan?

The reality is that different personas use AI in different ways to fit their workflows, which is the best possible use of technology. At the same time, there is a heavily hyped ecosystem where every vendor claims to do everything with AI. Just putting "AI" on a product doesn't mean it is good, reliable, or actually helpful. You have to look closely at your specific use case, the AI's actual capability, the underlying infrastructure, and your confidence level in its reliability. From a corporate governance standpoint, companies also have to be hyper-aware of data security, asking whether a vendor's AI is contained, where the data is going, and how outside counsel is using AI.

Ultimately, you have to separate vague, general applications from high-value, specific ones. Using a general chatbot to ask how long a flight might take is fine, whereas using AI to refine the tone of an email for a specific audience is a concrete efficiency win — you see the result immediately, so you don't even need a "trust, but verify" step. Because attorneys live in language, those use cases are easy wins. When you move into areas like predictive analytics, the potential ROI is much higher, but the stakes and risks rise right alongside it. There always has to be a thoughtful balance between the two.

When you think about the long arc of your career, how would you like to be remembered and what legacy would you like to leave behind?

For me, it has always been about the people. I loved my team, and I grew that team in a very thoughtful way. Even though I'm no longer there with them, I know they are held in high regard by everyone they interact with, and they continue to support and drive vision for the enterprise.

Relationships with colleagues have always been at the center of my career, which is why the hardest part of COVID was seeing everyone scatter to the wind. What I loved most was that sense of connectivity and building things for others that genuinely made their lives easier. Being able to stand up a new system and tell someone, "You don't have to manually review those bills anymore," or "Just push this button to get the report you need," and seeing their relief — that sense of accomplishment, being an enabler, and building a team that carries that mission forward is my favorite thing.

Ready to turn your legal operations into a platform of action? Learn more about how Litify ELM can help unleash your team’s full potential.