Preparation: The Key to Legal Tech Success
Why, in my opinion, so many legal tech projects fail before a single line of code is written.
I’m a former litigation lawyer now working on the product and technology side of legal innovation. Over the years, I’ve worn multiple ‘techie’ hats—developer, UX designer, product owner, and delivery lead—but at its core, my work is about problem-solving. Whether I’m writing code or shaping product strategy, I focus on making things clearer, faster, and genuinely usable.
I’ve seen legal tech projects from both sides: legal teams frustrated by clunky tools, and tech teams struggling to deliver against vague, shifting briefs. I work in the gap between those worlds—helping turn good ideas into software that actually gets used.
The most valuable lesson I’ve learned is simple.
Without proper preparation, legal tech projects invariably fail to deliver.
Over the next few months, I’ll be publishing an 8-part series to help lawyers and legal ops professionals avoid that fate. Each article will walk through the kind of preparation that’s essential before a build begins — the part too many legal tech projects skip, often at great cost.
Article 1: Want Legal Tech That Works? Start With the Requirements
- Why unclear requirements are the root cause of scope creep, budget overrun, and failed pilots
- What usable requirements actually look like
- How to bridge the gap between legal insight and tech execution — without needing to “speak dev”
Follow along for the full series, and share with your team if you’re planning a legal tech build of your own.
Get the Free Article
Download “Want Legal Tech That Works? Start With the Requirements”
Got thoughts or questions? Get in touch.