Building Advocate Productivity Without Losing Rigor

Some of the tension between speed and rigor is genuinely unavoidable - reviewing a document carefully takes longer than skimming it, and verifying a citation takes longer than trusting it. There's no tooling that removes the actual thinking time a careful review requires, and treating verification as an obstacle to speed up is how errors get filed.

A lot of what feels like an unavoidable speed/rigor trade-off is really time lost to work that doesn't require judgment at all: reconstructing matter context because notes live in three different places, re-typing a citation because it wasn't captured the first time, or manually checking whether a case is still good law with no system tracking it.

None of that work makes an advocate's output more rigorous - it's just friction that eats into the time available for the parts that actually require legal judgment: reading the source material, forming a strategy, and reviewing the final output carefully.

The useful version of 'productivity' tooling for legal work isn't about producing more output faster - it's about removing the mechanical overhead (context reconstruction, manual citation lookup, drafting from a blank page) so more of an advocate's time goes toward the review and judgment steps that shouldn't be rushed.

That's a different goal from generic productivity software, and it's why tooling built specifically around legal workflow - matter continuity, source-grounded drafting, citation verification - tends to help more than general-purpose task or writing tools adapted after the fact.