Scope creep is a major destroyer of ITSM process improvement. We’ve come to view it as the productivity killer that lurks in the shadows, ready to pounce. However, scope creep can take many shapes, and we often don’t recognize its most common form: a boldly raised hand. Ryan Ogilvie says that scope creep most often stems from questions that start with “What about…?”
What about this? What about that? What about enhancing the knowledge management while we work on problem management? These questions usually have good intentions, but they can pose serious problems if they aren’t handled correctly. You don’t want to get sidetracked from the task at hand, so explain that you are tabling that activity for the time being, or that you will introduce it during the next phase of improvements.
Don’t be dismissive, but stand your ground on why your current improvement is the one to be considered first and foremost. There will always be time to go back and discuss other changes later, but you may never get any improvements finished if you are constantly attacked by scope creep.