Trying to pick a system is a bit like trying to navigate through a bunch of blind date options.
Systems can look great on paper (or profile) and say all the right things before you meet but ‘in real life’ it can be a very different story. Software vendors are not being deliberately misleading. They are putting what they believe is the best option forward when they tell you their system can do almost anything. We call it the ‘software disappointment gap’.
It’s up to you to figure out whether their offer is a good match for your business and sometimes it’s really hard to know this before you get your hands on the product and actually try it out.
We are sure there are lots of good ways to approach this but the way we like to do it is by ‘understanding the now’ first. Whether you’re expecting to take your current processes into the future or not mapping them out can really help people understand the interconnected nature of systems. Typically, we work to produce three key documents:
Current system overview diagram helps us understand existing systems and how the data flows from one system to another and how manually intensive this is.
End to end process flows help us to validate (and question) as a team how we work between departments. In these diagrams we include all the spreadsheets and ‘off system’ processes so that we’re not just looking at systems but also looking at how people interact and move information around.
Current system overview diagram helps us understand existing systems and how the data flows from one system to another and how manually intensive this is.
End to end process flows help us to validate (and question) as a team how we work between departments. In these diagrams we include all the spreadsheets and ‘off system’ processes so that we’re not just looking at systems but also looking at how people interact and move information around.
We call it a Systems Sense check. But it’s entirely the kind of thing you could DIY. If you think you would like to have a go at that you can sign up here for our templates and examples.
Every business is unique. Look, we say this with a lot of experience. We have seen a lot of things (some of them more unusual than others 😉 ) and yes, in an ideal world, it would be one easy answer. It’s rare that one business is an exact replica of another (even when those brands are owned by the same company they can be different in what they need from systems).
It would be so lovely to be able to offer people who ask a ‘here’s one I made earlier’ type of answer to the ‘which system?’ question. It really does depend on the business, on your internal capacity and capability, on what your current systems do well, and of course on your budget.
Just like any medication there are often some side effects to reviewing your processes and systems.
Here are some examples that we’ve seen:
Getting longer life out of existing systems by working on improving communication between teams.
Reducing the steps in a process by understanding the end to end needs of everyone in the business.
Using the process flow documents as onboarding /training materials to share with others how the business functions.
Gaining clarity around what does/ doesn’t serve your business and making a decision.
Moving faster through the selection process because you know what you want.
Getting longer life out of existing systems by working on improving communication between teams.
Reducing the steps in a process by understanding the end to end needs of everyone in the business.
Using the process flow documents as onboarding /training materials to share with others how the business functions.
Gaining clarity around what does/ doesn’t serve your business and making a decision.
Moving faster through the selection process because you know what you want.
Getting longer life out of existing systems by working on improving communication between teams.
Reducing the steps in a process by understanding the end to end needs of everyone in the business.
Using the process flow documents as onboarding /training materials to share with others how the business functions.
Gaining clarity around what does/ doesn’t serve your business and making a decision.
Moving faster through the selection process because you know what you want.
Typically, clients get insight on where things are working and where they’re not, what they might do (even with your current systems) to improve and finesse the situation.
In a hurry? We can go as fast as you can.
We have done this in as little as 3 weeks, but that assumes that you’ve got everyone in your business available.
Typically, it takes clients somewhere between 6-8 weeks to organise team members, book sessions and work through the review process.
Typically, clients get insight on where things are working and where they’re not, what they might do (even with your current systems) to improve and finesse the situation.
In a hurry? We can go as fast as you can.
We have done this in as little as 3 weeks, but that assumes that you’ve got everyone in your business available.
Typically, it takes clients somewhere between 6-8 weeks to organise team members, book sessions and work through the review process.
At the very least you get a set of documents that you can align on and clearly communicate with vendors. However, clients report getting a great deal more out of this process than documentation and a path forward.
The process of working together to agree on what’s needed is the first step in building your teams capability at communicating and navigating all the elements that are needed to implement a change project.
We have a long-standing client who are very technology savvy, they invest early and often. They do their homework; they’ve learnt the hard way that all is not what it seems and put lots of checks in place to ascertain if the software they’re selecting is right before they do so. Guess what? It still happens that the expectations and the reality are not aligned, it never hurts to sense check your thinking with others.