Last week was interesting in terms of both doing a lot of automation work, while also discussing potential approaches to new projects with prospective customers.

When scoping out a new project, I usually try and understand the bigger picture and where all the opportunities for improvement are.

This is because even if the project is delivered in smaller phases and there are off-ramps to stop work if things aren't turning out as expected, it is useful to know where the ultimate endpoint is likely to be and where most of the opportunities to create value are. Sometimes, just a little more effort will create a lot more immediate value.

What I often find, though, is that while it's easier for me as someone who lives and breathes this stuff every day to see the potential endpoint and where extra benefits could come, it's much harder for someone who hasn't done it before to picture it. A Statement of Work can only paint a partial picture at best.

When a project starts to feel too big and uncertain, it can delay decision-making, and sometimes, the project doesn't get started or is significantly delayed. Conversations with prospective Government customers, in particular, often end in a feeling that it could be years before anything happens, while in the meantime, there are many things that could be improved within days.

The most recent project I started for a law firm customer has so much potential that I can't help but be excited about it.  However, for the law firm involved to take advantage of the opportunities, they would need to adopt some business models that they aren't used to and run before they walk.

Where we landed was that it was more important to get started, so they could see how it would work and get some runs on the board. We agreed on a fairly small budget on the basis that we would do as much automation as we could within that budget, and would then reassess.

In this video, hear how Foodstuffs overcame their initial barriers to get their automation projects going

One week in, I've already automated a number of their Priority 1 documents, leveraging automation on similar projects that we've already delivered. I've been able to do a lot more than I originally expected. Everything has been designed to enable a bigger solution when things are right, but at the same time, we've avoided the complexity and delay of trying to plan and budget for a bigger project before everyone is ready for it.

If you're thinking about your own automation project and getting stuck, I recommend this approach: Start small, but at least start. Set a budget you can work with—maybe as little as $5,000 - $10,000. Enough that will make a difference, but not so much that it worries you. Gather quick wins. Learn and adapt as you go.

Organisations like Victoria University of Wellington and New Zealand Green Investment Finance have had a lot of success in their legal automation projects by taking this approach. They started small and have subsequently done a lot of additional automation that has delivered great results. You can see more details here https://www.lawhawk.nz/automation-services/case-studies/victoria-university-of-wellington-obtains-phd-in-legal-automation-solutions and here https://www.lawhawk.nz/automation-services/case-studies/powering-green-finance-with-legal-automation. 

At the end of the day, done beats perfect, and you can always improve further once you have made a start.