Workflow in Litigation Support

I think some people have a natural eye for seeing the bigger picture.

For others, they make a decision without considering how that decision could have an effect on a future situation. I see this happen all the time.

When I am teaching litigation support to a newbie, I frequently mention “the workflow”. I was recently asked what I mean by workflow.

In litigation support, we need to work efficiently. The way my brain works, I am always thinking bigger picture.

When making a decision,

I consider the number of steps a process will take and I try to eliminate extra steps if possible.

I consider how many people need to be involved.

I consider how much time a process will take.

I often work backwards from both the deadline and the ultimate goal.

I consider if we will need to repeat the steps at a future date. I am a fan of automation.

I consider the level of probability of human error and where to minimize it.

I try to avoid accessing the same object more than once during the process. An object could be a folder, a file, a software button, or a physical item, etc.

I consider whether the end result could be repurposed in the future.

To me, a workflow is a sequence of execution events designed with the goal to be efficient, free from human error, at least partially automated, with a high quality end result that meets the deadline.

A workflow requires ongoing monitoring throughout and quality checking at the end.

A workflow may require a quick pivot if a requirement changes or a process doesn't go as expected.

A workflow requires excellent communication at the beginning, during the process and then again at the end.

A workflow that goes smoothly and that may be repeated should be documented.

Don't rush. Take the time to think about the workflow thoroughly before making a decision.