company, you've probably run into change control. Change control is the means whereby a company limits the changes that are made to the network (or anything, for that matter) until they are understood and scheduled. If you want to upgrade a router with change control active, you need to submit a request. The request then needs to be approved, at which point the change might be scheduled. In some companies, a single person approves or denies change requests. In other companies, committees review every request. I've seen companies where the change-control committee meets only on, say, Tuesdays. If your change is denied, you have to wait until the next Tuesday for an alternative change to be considered. Scheduling changes is one of those things that seems to make engineers a bit nutty. Why should you have to wait for a team of people who don't understand what you're doing to tell you it's OK to do it? Why waste time if you know you can fix a problem with a single command that won't hurt anything? To engineers, change control can seem like a waste of time and energy that does nothing but interfere with their ability to get work done. Over the years, I've held many positions, ranging from junior engineer to director of a large consulting company to head of my own business. During those years, I've learned a few things about how businesses operate and how engineers think. Running a busi- ness while also being an engineer has given me a unique insight into both worlds. Change control is important for any company for the simple reason that failures cost money. Take a large ecommerce website, for example. If an engineer makes a change Why Change Control Is Your Friend that causes the site to become unavailable, the company loses income until it's fixed. What's more, the company's reputation may be affected when users try to make pur- chases online only to find the site unavailable. Most users probably won't wait more than 10 seconds for a page to load if they can get the same information or products elsewhere. Imagine the