As I mentioned in my blog post last week, I am posting a series of self-reflection posts where I reflect back on six different “Words of wisdom” concepts I left my former team with when I departed. In part two of my six part series, we will look at what it means to take ownership.
The other day I was waiting outside of a conference room for the previous meeting to end. There was a group of individuals near me waiting for another conference room. As much as I pretended like I wasn’t listening, I was. Don’t judge me, we were practically standing next to each other and you would have done it too. Their topic of conversation was about effectiveness and hours worked in the day. The person who initiated the topic stated that she would rather have someone on her team who worked 8 hours a day and was very effective rather than someone who worked 12 hours and was not effective. The question she posed to her colleagues was “how do you teach effectiveness?” I love this question.
The term “scope creep” is often used in business and we all know what it is, but do we really? In my experience leading various process improvement activities or new project management initiatives, I have come across at least three different problems that are often grouped together and classified as “scope creep.” I want to discuss a different concept that I call “solution creep” as a way to rethink these distinct problems and give some insight on how your can prevent your solution from creeping.