<p>More meetings, more committees, more reviews isn't going to deliver more reliable network changes. While a formalized process and policies for network changes is important, you hit a point of very diminishing returns: Doubling your meetings or committees or reviews isn't going to halve your error rate. It just adds friction to the process. </p>

More meetings, more committees, more reviews isn't going to deliver more reliable network changes. While a formalized process and policies for network changes is important, you hit a point of very diminishing returns: Doubling your meetings or committees or reviews isn't going to halve your error rate. It just adds friction to the process.

Don't Add Meetings/Committees To Your Change Control Process, Add Autotmation

This is a (probably) limited series where Tony Bourke, a networking instructor (Arista, Cisco, etc.) talks in a vendor-neutral way about the process of network automation, the basic concepts, and where everything falls into place.

Share Don't Add Meetings/Committees To Your Change Control Process, Add Autotmation

Sign up to save your podcasts

Don't Add Meetings/Committees To Your Change Control Process, Add Autotmation

Don't Add Meetings/Committees To Your Change Control Process, Add Autotmation