Are you creating a monster? Repeatability & Scalability in Process

I'm working with a team at the moment who has a product that they sell to clients. As part of the ongoing managed service to this client they have 9 key services that they provide. Basic stuff really - service requests.

Think about this:

• They have 9 process maps for each service request type

• They have procedures for each service request type

• They are all "client specific"

So what happens when they bring on a new client? Yes, they create a new set of processes and procedures for that client.

And what happens if a change is required to a process - yes they have to change the process across all the clients!

Just think about the administrative overhead of all that and the potential confusion caused by 9 processes times X number of clients. Essentially what they have done is to create a process monster. We're now going through the process (ahem) of stripping back the client specific information to create 1 process and set of procedures that can be used across all clients. This reduces the admin overhead, reduces the margin for error and allows us to go to market quickly and implement rapidly if a potential client comes along.

So the message is, when you create or modify process remember:

• Repeatability - make it easily repeatable, don't re-invent the wheel each time
• Scalability - make it adaptable to growth

Don't create a monster.

TPN