top of page

๐Ÿ‘“Managing Scope is Dope!

Updated: Sep 19, 2021

As I have started to pour through my project management study materials I am left with several realizations.

  1. Please gain knowledge because others have made pitfalls. This is a value I have adopted a few years ago. However, this studying has made me realize that I need to do it more for the things that go poorly. I am learning SO MUCH!

  2. Lessons Learned are not just a business thing. They are a way to process what you have learned through a rollout. More than that, they are a way to adjust future elements. Practice them (Even if your business does not ๐Ÿ˜‰)

  3. A plan is only as good as its control / process management (Scope Document)

Plans needs to be controlled to produce the desired outcomes

If you don't have rules or guidelines of engagement in your plan then the plan will change. Defining SCOPE of a project and outlining clear expectations is key.

So how do you manage customer expectations? This is not an easy easier, so seek knowledge from others who have learned. What I have learned is true for most areas of business:

  1. Open and honest conversations about business decisions that impact the rollout

  2. Direct and transparent conversations. They might suck, but they need to happen

The "A-Hole" Rule

When delivery my first child with my wife we had a Nurse come in during the final hours of the delivery. She told me, "Hi my name is Chris and I am an A-Hole". I was taken back to be honest ๐Ÿ™€. She explained that if she told people, then when she was an a-hole she would not surprise people.

Later that day, she proved her statement true ๐Ÿ˜… but I was not surprised or honestly really upset about it, because I had already processed the truth she told me. That idea ๐ŸŒฑ grew on me until I realized that all people really want to know about something is the truth. That way if it happens they are not surprised by it.

So if a project is going to be delayed, don't hide it until last minute, get in front of the problem and let them know what's up (The a-hole rule). The client might be surprised, but at least they will be prepared and in the long run will appreciate it.

Lets take a highly complex emoji diagram of both situations ๐Ÿ˜†

Limited or Poor Communication:

Start --------------------------------------------------๐Ÿ™‚

Project is take a while -------------------------๐Ÿค”

Communication is limited or not honest ๐Ÿ˜

Project is delayed -------------------------------๐Ÿ˜ฒ (This is NEVER what you want a reaction to be)

Client is repeatedly treated like this -----๐Ÿ˜ก

Open and Honest Communication:

Start ------------------------------------------------- ๐Ÿ™‚

Project is take a while -------------------------๐Ÿคจ

Communication is Honest -------------------๐Ÿค”

Expected outcome -----------------------------๐Ÿ˜

Client is then delivered promise ----------๐Ÿ™‚

Moral of the story is to control SCOPE and Expectations because the client needs to know the truth of what is happening.

Scope Management:

  1. Create a Scope Management Document

  2. Be Specific, talk details

  3. Who is in charge of what?

  4. What if Scope Changes? What does it impact?

  5. Don't say yes without consider the Project Management Triangle (See Below)

  6. Everything does have an equal and opposite reaction.

I am excited to continue my knowledge gain with Project Management. Continue to do your own reading and learning! Comment below some articles you find so others can benefit from the Internet!

As always, my Zoom Room is always open. Reach out if you want to connect!

Awesome cover photo created by Moose Photos and I got it from Pexels!

Photo by Moose Photos from Pexels

Also feel free to come with me on my Journey to getting my PMP! The Day One Episode has gone live! ๐Ÿ˜„


Recent Posts

See All
bottom of page