Automate, integrate or build? A simple way to choose

When something is slow, it is tempting to jump straight to a solution. A better first move is to work out what kind of problem you have.

Question 1: Do you know what is slowing the work down?

If not, start by mapping the workflow. Automating a process you do not fully understand tends to automate the confusion too.

Question 2: Do your tools work, but people move information between them?

That points to automation or integration: connecting systems you already use so that reminders, handoffs and updates happen without copying and chasing.

Question 3: Can the tools you have support how your team needs to work?

If you keep bending the process to fit the software and the workarounds keep growing, custom software may be worth considering. Because it usually costs more upfront, it should come after the first two questions.

A rule of thumb

• You do not know what is slow: map the workflow first.
• Your tools work, but people link them: automate or integrate.
• Your tools cannot support the process: consider custom software.

Many situations are a mix. That is fine: start with the smallest step that teaches you something.