Requiring a uniformity of process caps the highest potential of your teams.
Process protects us from making mistakes, and can lift every team to a good level. Forcing this is what stops us finding the truly great performances.
We sometime fall to uniformity when we find it hard to measure the outcomes that teams are driving. Measuring adherence to a process is often easy. It’s easy to count the number of widgets that are being created, and it’s easy to see if we’re all doing it in the right way. It’s not always easy to determine if we’re doing the smart things that actually achieve the outsize results.
A classic example of a mistake is to enforce Scrum, or any other particular flavour of agile. The more tightly it’s enforced, the less likely you’ll get a 10/10 team performance.
Instead, go back to the Agile Principles. The best architectures, requirements and designs emerge from self-organising teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
An overly rigid process hinders this adjustment. It doesn’t recognise the unique context of the team, and that’s where the potential is capped.
By all means, if your org needs certain things reported, or activities that must be done for legal reasons then you can require that of the teams. Beyond those must do things, you should instead encourage your teams to experiment and find out what works best for them.
The goals of leadership in this model is to share the things that are working, and also the things that aren’t. Giving access to the tools that can support, and taking away the noise that breaks focus.
It’s imperative that you don’t just allow each team to meander through the path to excellence!
So forcing a process can take you up to good, coaching teams and sharing the best outcomes widely will help you achieve greatness.