
"Maybe it's my OCD, or being a nerd (I know, shocking), or being a control freak (did I mention my OCD), but I am a massive proponent of reducing the types of cases you handle to a series of checklists and workflows. No matter how complex or varied your cases are, or their quantity, creating a written, step-by-step process for handling each type of case will increase efficiency, quality control, and outcomes."
"This approach - reducing your caseload to a set of processes that serve as a tool to ensure you consider all the various methods and steps in your cases - is often overlooked because it is time-consuming, non-billable, and requires regular review and updates (these checklists must be reviewed and updated periodically). Additionally, some lawyers believe their cases are too complex to be reduced to step-by-step processes. What they do is so unique, so intellectual, that it cannot possibly be reduced to checklists."
"I handle a variety of litigation-based matters. Throughout my career, I have litigated a wide range of cases, from asbestos to zoning, and everything in between. And early in my career, I looked at my cases from the vantage point of - what is every possible thing I can do in the case and what makes sense under different sets of circumstances. And I wrote out checklists."
Reducing case types to written checklists and workflows increases efficiency, quality control, and outcomes. Written step-by-step processes capture recurring tasks and ensure consistent handling across a team. Checklists require time, are non-billable, and need periodic review and updates. Many lawyers resist checklists, believing individual cases are too complex or intellectual to be reduced. Despite complexity, an estimated 50–90% of most cases can be standardized into checklist items. Mapping cases from pre-suit through trial and refining procedures with experience improves decision-making, alignment, and pursuit of client objectives. Processes serve as tools to consider all methods and steps.
Read at Above the Law
Unable to calculate read time
Collection
[
|
...
]