July 16, 2025

Demystifying MDLs with Alex Parkinson of Kellogg Hansen

Subscribe to Our Newsletter

Newsletter


Kevin Skrzysowski

|

July 16, 2025

In the 34th episode of Alternative Litigation Strategies, Kevin Skrzysowski speaks with Alex Parkinson, a partner at Kellogg Hansen and the author of Practising Law Institute ‘s (PLI) newest treatise on multidistrict litigation. Alex dives into how MDLs have shaped federal litigation, what inspired him to compile a comprehensive review of JPML decisions, and how attorneys can proactively prepare for complex, high-stakes cases.

Whether you’re a seasoned litigator or just starting to navigate MDLs, this episode offers actionable insights and a behind-the-scenes look at one of the most important areas in procedural law.

This transcript has been lightly edited for grammar and clarity.

Host: Kevin Skrzysowski

Guest: Alex A. Parkinson, Partner at Kellogg Hansen and Author of Practising Law Institute’s (PLI) Comprehensive Treatise on Multidistrict Litigation

Kevin Skrzysowski:
Welcome to the latest episode of Certum Group’s podcast Alternative Litigation Strategies , where I interview esteemed members of the bar on the latest litigation trends and strategies. I’m your host, Kevin Skrzysowski, a director at the litigation consulting firm Certum Group, which provides a suite of litigation finance and insurance solutions to help companies and their counsel mitigate, cap, and transfer outcome risk.

Today, I’m very pleased to be joined by Alex Parkinson, a partner at the litigation boutique Kellogg Hansen, located in Washington, D.C. Alex is also the author of PLI’s most recent comprehensive treatise on multidistrict litigation and the judicial panel that oversees them, which is the topic of our conversation today. Alex, welcome to the program.

Alex Parkinson:
Thank you for having me, Kevin. I appreciate it.

Kevin:
Certainly. I’d like to start by diving right in. How did you become involved in the area of multidistrict litigation, and how has the field evolved since you started?

Alex:
Great question, and again, thank you for having me. This goes back to when I was in law school, probably a rising 2L. I was at a lunch talk and overheard a practicing attorney say, in reference to a high-profile data breach, maybe Equifax, that there would be a lot of litigation and that the courts would probably “park it in an MDL.” That language stuck with me.

I started reading about MDLs. They’re fascinating and everywhere. They dictate a lot of the federal civil docket, but there isn’t much written about them procedurally, nor are they usually taught in law school. That started my interest.

Then I began practicing at a firm like Kellogg Hansen, which regularly handles cases that are either part of MDLs or affected by them. We represent both plaintiffs and defendants, so MDLs became a recurring part of my practice.

In terms of how the field is evolving, MDLs evolve with society. They reflect the world around us. If there’s a major event, like a plane crash, a data breach, a mass torts issue, or an antitrust dispute. It’s likely you’ll see it processed through the MDL framework. They follow the trends of our time.

Kevin:
You raise great points. MDLs are certainly dominating the federal docket. I work on class action risk products, and a huge portion of those are MDLs. Like you said, it’s not something most people learn in law school.

So what inspired you to write this treatise now?

Alex:
It really stemmed from wanting to read more about the topic. When I got to Kellogg Hansen and started working on MDLs, I wanted to go deep. I read David Herr’s Multidistrict Litigation Manual , which is excellent, but beyond that, there wasn’t much out there.

After reading everything available, I still had questions, and I couldn’t find recent or comprehensive answers in the market. That’s what drove me to start this project.

Kevin:
Interesting. Your firm handles high-stakes litigation across sectors. How did that shape the book?

Alex:
It helped a lot. Because we litigate on both sides, plaintiff and defense. We see MDLs from all angles. That balanced experience informed how I approached the treatise. Our firm philosophy is that working both sides sharpens your overall strategy. That definitely applied to this writing project.

Kevin:
Same here. At Certum, we work on both sides, and it really informs strategy. So, as you researched and wrote this book, what surprised you the most?

Alex:
Two things: First, that so little has been written about MDLs given how influential they are. They shape the lives of consumers across the country and drive so much of the federal docket.

Second, I realized this is a manageable area of law. If I tried to write a comprehensive treatise on antitrust or patent law, I’d be overwhelmed. But with MDLs, I found it was actually possible to read every decision issued by the Judicial Panel on Multidistrict Litigation (JPML) since its inception in the 1960s. That became my baseline.

Kevin:
Did you include those cases in the book?

Alex:
Yes. There are two appendices. One catalogs every JPML decision since 1968 by subject matter: antitrust, patent, labor, etc., and by whether centralization was granted or denied. The second appendix sorts MDL cases by the factors the JPML used to select the transferee district. The goal was to be truly comprehensive.

Kevin:
So anyone reading this has a complete bird’s eye view of MDL law?

Alex:
Exactly. If you’re facing a potential MDL – say from a data breach – you can go to the appendix, find all relevant precedent, and strategize accordingly. Whether you’re trying to create or resist centralization, the book gives you the history and outcomes to build your case.

Kevin:
Who is this book for, corporate counsel, law firm lawyers, policymakers, judges?

Alex:
It’s geared toward practicing attorneys, both in-house and outside counsel. Future editions might touch on reform or policy ideas, but this edition is meant to be a practical resource.

Kevin:
Fair enough. What’s your main advice for lawyers working in this space?

Alex:
Get familiar with MDLs before you’re facing one. Once there’s a motion to centralize before the JPML, things move fast. Ideally, you’d consult this book early, when there’s only one or two suits filed, and you sense more may follow. That’s the time to plan.

Kevin:
What are the key takeaways for less experienced vs. more seasoned attorneys?

Alex:
For less experienced attorneys: this book is a great way to learn MDL procedure, which is distinct from substantive law. For more experienced attorneys: there’s no universal playbook for MDLs. This resource gives you the tools to shape a strategy tailored to your client’s goals, whether you’re for or against centralization.

Kevin:
You mentioned future editions might explore public policy. What kind of impact do you hope this edition has?

Alex:
My goals are modest. If practitioners cite this work in briefing before the JPML, I’ll consider that a win. It would mean they’re using the content, and that it’s helpful.

Kevin:
Let’s talk about PLI. How did that partnership begin, and what was it like?

Alex:
I clerked for Judge Sack on the Second Circuit, who authored the leading treatise on defamation, published by PLI. He connected me with them, and that led to the partnership. Working with PLI has been fantastic. They were patient, helpful, and generous throughout. My editor, Jacob Metric, was a great collaborator.

Kevin:
How long did it take to complete?

Alex:
Several years. I worked on it in pockets of time – early mornings, late nights, weekends. I treated it like a hobby. I even have a photo of me holding my then three-month-old son while writing. He’s six now, so that gives you an idea.

Kevin:
Did writing it change how you think about the law?

Alex:
It gave me a greater appreciation for the problem-solving built into our system. MDLs were created to manage mass litigation more efficiently, and judges have done remarkable work making that process fair and effective.

Kevin:
What advice would you give to someone considering writing a treatise with PLI?

Alex:
Do it. Even if you’re starting from scratch, it’s a rewarding experience. Just know it’s a time commitment. Talk to your firm. My firm was supportive. Kellogg Hansen has a long history of scholarship, and I had mentors who encouraged me to go for it. But yes, there were vacations where I stayed inside writing while the rest of the family went to the beach.

Kevin:
Thanks, Alex. This has been a terrific conversation. If listeners want to reach you, what’s the best way?

Alex:
My email is on our firm’s website, www.kellogghansen.com. You can reach me at aparkinson@kellogghansen.com.

Kevin:
And for listeners, the treatise is available at www.pli.edu/mdl. This episode will also be available at www.certumgroup.com, as well as on Apple, Spotify, and Stitcher.

Thanks again for listening. Until next time!

Certum Group Can Help

Get in touch to start discussing options.

Recent Content

By Patrick Dempsey September 1, 2026
This is the first post in Certum Group's seven-part series bringing our Trade Secret Litigation Playbook to the blog. It draws on Part I of the Playbook, Why Trade Secret Claims Matter Now. Read or download the full Playbook here . In 2025, federal trade secret filings reached an all-time high — roughly 1,551 new cases in U.S. district courts, up from 1,203 just two years earlier. 1 That is not a blip, and it is not a quirk of the docket. It is the visible edge of a structural shift in how companies create value and how easily that value now walks out the door. Trade secrets used to be the quiet cousin of the intellectual property family — patents got the valuation multiples, trademarks got the brand meetings. That era is over. For a lot of growth-stage companies, the trade secret portfolio can be worth more than the patents, copyrights, and trademarks combined. It rarely shows up on the balance sheet, and it is almost never insured against the risk it actually faces — which is not that someone will design around it, but that someone will take it. So it is worth understanding why the numbers are climbing, because each driver points to a specific exposure that a business owner can do something about. Employees move more, and faster The single largest source of trade secret disputes is not corporate espionage. It is ordinary talent mobility. Roughly 60% of misappropriation cases involve a departing employee, typically heading to a direct competitor. Tenure has shortened, remote work has normalized discreet cross-company job searches, and the volume of departures that touch sensitive information has grown accordingly. The prototypical case a decade ago was a sales rep leaving with a customer list. Today it is a design lead, a data scientist, or a process engineer carrying the company's hardest-won know-how — sometimes in a file, more often in their head. The cost of taking information has collapsed A USB drive, a personal cloud folder, an auto-forwarded email rule, a screenshot script — what once required filing cabinets and a truck now takes a few minutes. The technical friction that used to deter casual misappropriation is largely gone. That has two consequences. It makes the taking easier, and it makes the forensic trail richer: badge records, git commit histories, egress logs, and download timestamps now tell a story that is often more persuasive to a judge than any witness. The evidence exists. The question is whether the claim holder preserves it before it rolls off a ninety-day retention setting. AI has raised the stakes Machine-learning models are trained on data, code, and process knowledge that is frequently proprietary. Competitors racing to ship an equivalent product have a powerful incentive to shortcut the long, expensive path of independent development — and in software, life sciences, financial services, and advanced manufacturing, a six-to-twelve-month head start can be worth hundreds of millions of dollars. When the crown jewels are unpatented know-how, misappropriation is not a nuisance. It is an existential competitive event. Apple's 2026 trade secret suit against OpenAI — built around aggressive hiring from Apple's hardware teams — is only the most visible example of a pattern now playing out across the economy. A single, credible venue Finally, the law itself has changed the calculus. Since 2016, the federal Defend Trade Secrets Act has given claim holders a nationwide cause of action, federal discovery tools, and remedies strong enough to matter — including an extraordinary ex parte seizure procedure. 2 Enforcement is more predictable than it was under a patchwork of state statutes, and predictability attracts plaintiffs. It also attracts capital, which is where a firm like ours enters the picture. What it means for you From the underwriter's chair, the trend line is unambiguous: more valuable secrets, more mobile employees, cheaper theft, and a legal framework that rewards claim holders who move deliberately. The companies that fare worst are the ones that treated their secrecy program as a compliance checkbox and discover, only in a complaint, that it was the strategy all along. The companies that fare best have thought about identification, preservation, and enforcement economics before they ever need them. If your business runs on information other people would love to have, the record filing numbers are not abstract. They are a forecast. Go deeper with the Playbook. This post covers one piece of a much larger picture. For the full framework — what the law requires, what a strong pre-filing case looks like, how damages experts value these matters, how counsel fee structures change your economics, and how litigation finance fits in — read Certum Group's Trade Secret Litigation Playbook , our field guide for business owners and the counsel who advise them: certumgroup.com/the-trade-secret-playbook . And if you are evaluating a live dispute — or simply want to pressure-test what a matter is worth and how it might be funded — get in touch. A confidential conversation with Certum is free and carries no obligation, whether or not you ultimately seek funding. Reach us at certumgroup.com/contact-us . Sources 1. Lex Machina, Trade Secret Litigation Report (2026), reporting an all-time high in federal trade secret case filings in 2025; see also Lex Machina, Trade Secret Litigation Report (2024) (1,203 federal filings in 2023). 2. Defend Trade Secrets Act of 2016, Pub. L. No. 114-153, 18 U.S.C. Section 1836 et seq.
By Certum Group Team August 31, 2026
Certum’s William Marra was recently quoted in an article by MLex, a LexisNexis publication, on the widening debate over third-party litigation funding disclosure. “Litigation finance is the capital markets come to law,” Marra told the publication, emphasizing that funders are one of the few sources of capital available to an individual or small business facing a far larger opponent.  Responding to claims that litigation funding is a vehicle for foreign influence, Marra observed that “there’s just no evidence [of foreign influence] in the third-party funding space,” emphasizing that any real threat should be addressed through regulation covering foreign influence in litigation “in all of its forms.” The article also referenced Marra’s forthcoming New York University Law Review article on the third-party funding disclosure debate, which argues that any court-made disclosure rule should apply evenhandedly to all outside financing, and should not target only one form of third-party finance. “If you want to genuinely have a third-party litigation funding disclosure rule, then disclose all forms of third-party funding. Don’t just disclose the type of non-recourse litigation funding seeking money damages that is disproportionately used by poor individuals and small businesses.” The full article, Patent Litigation Drawn into Broader Third-Party Funding Disclosure Debate, is available here .
By Patrick Dempsey August 18, 2026
On July 10, 2026, the most valuable company in the world accused the most talked-about company in the world of theft. Apple sued OpenAI in the U.S. District Court for the Northern District of California, alleging that OpenAI built its hardware ambitions on a foundation of Apple’s misappropriated trade secrets.¹ Few disputes touch as much of Certum’s Trade Secret Litigation Playbook at once: reasonable measures to guard a secret, identifying with particularity what was taken, and the human-centered points — recruiting and employee departures — where secrets actually walk out the door. Nearly every core theme in Certum Group’s Trade Secret Guide is in this case. And the lesson beneath it is worth sitting with: for the companies with the most to protect, trade secret litigation is not a last resort. It’s a front-line instrument of competitive strategy. Background The dispute sits at the intersection of two of the most closely watched storylines in technology. In 2025, OpenAI acquired io, the hardware venture founded by former Apple design chief Jony Ive and a group of other Apple alumni, for a reported $6.5 billion, and set out to build its first consumer hardware device, widely expected to compete directly with the iPhone.² To staff that effort, OpenAI hired aggressively from Apple. According to the complaint, more than 400 former Apple employees now work at OpenAI.³ Two of those hires anchor Apple’s allegations. Tang Yew Tan spent roughly 24 years at Apple, where he served as a vice president of product design responsible for the iPhone and Apple Watch, before becoming OpenAI’s chief hardware officer. Chang Liu spent about eight years at Apple as a senior systems electrical engineer before departing for OpenAI in 2026.⁴ Apple’s theory is not that a single rogue employee walked out the door with a file. It is that the movement of talent was accompanied by a coordinated effort, one Apple describes as operating “at every level," to extract and exploit the confidential information those employees carried in their heads and on their devices.⁵ The Allegations The complaint reads less like a garden-variety departure dispute and more like a catalog of the exact conduct the Trade Secret Guide warns companies to watch for. Among Apple’s central allegations: Apple claims OpenAI’s hardware leadership directed recruiters to use Apple’s confidential project code names during the hiring process, and instructed job candidates to bring “actual parts” and “CAD/design artifacts” to their interviews.⁶ It alleges that OpenAI circulated internal Apple documents marked “Need to Know” that coached departing employees on how to evade Apple’s exit-security procedures, including the “dreaded walkout,” and to alert OpenAI before signing their exit agreements.⁷ The specifics attributed to individual employees are what give the complaint its texture. Apple alleges that Chang Liu exploited an authentication bug to reach internal network storage after his access should have been cut off, messaging a colleague, “LOL, I found out I can access the [network storage], so funny,” and noting within hours of his departure that he “still ha[d] another computer.”⁸ And Apple alleges that io “exploited and used Apple’s secret, proprietary industrial design techniques,” misleading one of Apple’s own manufacturing partners about whether it was authorized to use a confidential metal-finishing technique.⁹ The trade secrets Apple says are at risk span the full arc of its product-development process: technical specifications for unreleased technologies, engineering presentations and prototype data, component and vendor selection processes, and the proprietary manufacturing techniques that turn a design into a shippable product.¹⁰ Notably, Apple’s opening ask is not a damages windfall. It is protection. Apple seeks to bar OpenAI from using or disclosing the information at issue, to compel the return of its confidential materials, and to preserve the evidence.¹¹ In other words, Apple is using the courthouse to do what its NDAs and exit interviews were supposed to do: keep its edge inside the building. OpenAI’s Response OpenAI has pushed back hard, and its answer is a preview of the fault lines any trade secret plaintiff should expect to fight over. On August 6, 2026, OpenAI moved to dismiss, characterizing the alleged conduct as “benign, lawful conduct” that Apple has mischaracterized, and arguing that its hardware executives simply followed standard industry recruiting practices.¹² As to Chang Liu, OpenAI contends he was “trying to help Apple” by assisting former colleagues who asked him to locate work information, not stealing anything.¹³ More pointed, and more instructive, is OpenAI’s argument that Apple’s own conduct undermines its case. OpenAI asserts that Apple allowed employees to use personal iCloud accounts for work and failed to properly revoke access when they left — noting that an Apple manager remained logged into Chang Liu’s personal iCloud account after his departure in order to transfer files.¹⁴ From that, OpenAI argues that Apple’s offboarding lapses created “confusion and unwanted access issues that Apple now characterizes as theft.” OpenAI also contends that Apple has not identified its trade secrets with adequate specificity, pointing instead to “generic categories of the product-development process.”¹⁵ OpenAI must file its full response by August 17, 2026, with oral argument on the motion set for October 1, 2026.¹⁶ Whatever the merits, OpenAI’s playbook is worth studying precisely because it is so conventional. Reasonable secrecy measures and identification of the trade secret with particularity are two of the elements every misappropriation claim rises or falls on, and they are exactly where a well-resourced defendant will apply pressure first. What This Means It is easy to read a case like this as celebrity litigation between two of the most valuable enterprises on earth. The more useful reading is that trade secret law has become core infrastructure for how modern companies protect competitive advantage. Apple did not respond to a $6.5 billion competitive threat with a press release or a patent portfolio. It responded with a trade secret complaint, because in a business where the crown jewels are unpatented know-how — manufacturing techniques, vendor relationships, unreleased designs — the Defend Trade Secrets Act and its state-law counterparts are the sharpest tools available. The case also throws the Trade Secret Guide’s central lessons into relief. The value of a trade secret program is only as good as the “reasonable measures” behind it; OpenAI’s opening move is to argue that Apple’s own iCloud and offboarding practices were not reasonable at all. The ability to describe what was taken, with specificity, is not a formality. It is frequently the whole ballgame at the pleading stage. And the human element — recruiting, exit procedures, the “dreaded walkout” — is where secrets actually leak, long before anyone reaches a courtroom. Companies that treat these as compliance checkboxes learn the hard way, in a complaint, that they were the strategy all along. For those of us who evaluate disputes for a living, Apple v. OpenAI is also a reminder of why high-stakes trade secret matters are among the most compelling on the plaintiff’s side. The conduct is often concrete and documentable, the competitive stakes are enormous, and, as the Federal Circuit’s recent decision in Versata Software v. Ford underscored, the damages framework can reach the full value of what the misappropriation delivered to the wrongdoer, not merely a discounted license fee. That combination is exactly what makes these cases worth pursuing, and worth backing. Apple’s complaint will be tested, as it should be, and the allegations remain just that — allegations. But the strategic signal is already unmistakable. When the most valuable company in the world wants to defend its future, it reaches for trade secret law. Certum Group’s Trade Secret Guide is built to help plaintiffs and their counsel do the same, whatever their size, and this case is a live illustration of why that playbook matters now more than ever. Certum Group can help. If you are evaluating a trade secret dispute or want to talk through options for funding or de-risking one, get in touch . Footnotes ¹ Complaint, Apple Inc. v. OpenAI, Inc. , No. 5:26-cv-07078 (N.D. Cal. filed July 10, 2026); see Apple sues OpenAI over alleged trade secret theft , TechCrunch (July 10, 2026). ² The wildest allegations in Apple's trade secrets lawsuit against OpenAI , TechCrunch (July 13, 2026). ³ Id. ⁴ Apple sues OpenAI over alleged trade secret theft , TechCrunch (July 10, 2026). ⁵ Apple sues OpenAI alleging trade secret theft, says scheme was "at every level," CNBC (July 10, 2026). ⁶ The wildest allegations in Apple's trade secrets lawsuit against OpenAI , TechCrunch (July 13, 2026). ⁷ Id. ⁸ Id. ⁹ Id. ¹⁰ Apple sues OpenAI over alleged trade secret theft , TechCrunch (July 10, 2026). ¹¹ Id. ¹² OpenAI Asks Judge to Toss Apple's Trade Secrets Lawsuit , Claims Journal (Aug. 7, 2026). ¹³ Id. ¹⁴ OpenAI says Apple's own security practices undermine its trade secrets case , TechCrunch (Aug. 6, 2026). ¹⁵ Id. ¹⁶ OpenAI Asks Judge to Toss Apple's Trade Secrets Lawsuit , Claims Journal (Aug. 7, 2026).