The concept of 'Shift Left' has its roots in software testing, where it refers to the relative cost to fix an error, based on the time of detection. You can see in the graph below that errors which make it through to the final stage of Production/Post-Release stage cost 30 times more to fix than those detected at the initial Requirements/Architecture phase. So the software industry does whatever it can to 'shift left' those errors, and detect them as early as possible.
I'm going to explain to you how the shift left approach works with a problem many of you will encounter all the time, I'm sure - incorrect artwork being sent in by the customer.
Our main goal is to move the problem away from Prepress and shift it left to the CSRs, so that any artwork discrepancies are detected before they reach Prepress. In this example, we would do this using technology to implement job structure pre-flighting, specifically an integration between your MIS and Enfocus Switch.
I'm sure you'll have realized you could move this even further left by implementing content submission portals for your clients, which automatically check the artwork without involving the CSRs (unless a re-quote is required).
The Shift Left concept is an easy one to understand, but a hard one to implement. You need to have the right people in your business that will recognize the need to do this, as well as have the desire and the skills to do it.
If you're interested in finding out what kind of people you need and how exactly you can go about implementing a Shift Left culture, you can read more of our advice in our Automation Culture eBook.