the other day i spoke with a scheduler friend of mine by phone to see how his construction project was coming along.
from the moment i asked question “so how is the project going?” i could hear that something was up.
“good…. it’s fine. things are moving.”
“still making progress?”
“yeah, sure.” he answered.
but i could hear the frustration in his voice. i dug a bit deeper to see just how “fine” things were.
my friend, a 30-something engineer, is filling the role of project scheduler for a large multi-year rail project. he works for the general contractor. after we got into it, i found out the source of his frustration.
“schedules are useless.”
these were not his words, but it captured his sentiments as he relayed the situation on his project.
he told me that he spends all his days entirely focused on updating the schedule, incorporating the endless updates requested by the owner; a never-ending stream of small updates and added details.
being the only project controller, he had a very large schedule to maintain on his own while the owner had a team of 3 “experts” whose job it was to essentially verify and check the contract schedule he had prepared. he was feeling a bit overworked and over-scrutinized.
but here’s the rub.
although the schedule was in very good shape, it barely got a notice from his boss and management overseeing the project.
it was hardly looked at once a month in the regular meeting, but never again until the next month. the schedule was merely a formality and wasn’t being used to manage the work.
all that analysis ensuring the critical path was correct, all those detailed updates to ensure accuracy, the documentation, the weekly and monthly updates to create this model of predictability for the project. and no one was really looking at it.
maybe you can relate to this situation.
i’ve been around long enough to recognize that some projects have people who do not rely on a schedule, who prefer to go by gut feeling or experience.
right, wrong or indifferent, if you’re the scheduler in that situation, you’re probably not feeling very appreciated.
but appreciated or not, your schedule is vital to the success of the project. and it can be hard to get people to recognize that.
so to solve this dilemma, here are 5 tips to help you show the value of your schedule and get it noticed.
5 tips to show the value of your schedule & get it noticed
be proactive.
the first thing you will have do to is…
….change your way of doing things.
no one is asking to see the schedule?
no one cares about all of your hard work updating the schedule?
don’t get stuck in your expectations of what is “supposed” to happen.
we’re all “supposed” to be looking at the schedule and the dates. it’s “supposed” to be the primary source of timeline, performance and resource information.
we’re all “supposed” to be eating a lot of fiber as well, and frankly i just don’t do it. i’m just too darn busy.
actually, i will eat more fiber if:
- someone makes me do it.
- i do it myself automatically because it’s part of my routine.
the same goes here for your schedule.
you need to become the voice of the schedule.
you need to tell people to look at it – put it in their hands.
you need to get them to become dependent on it – so that they want to look at it ever week.
you can make that happen.
but you are going to have to become “proactive” about it.
yes, you’re going to have to speak up, maybe even yell and tell everyone that this schedule thing over here is valuable and important. in fact, it’s a legal document that is used to keep people accountable and is 99% effective for keeping projects on-track.
and if they don’t listen the first time, you’re going to repeat it, over and over until you get the result you’re after. and along the way, as you change the way you behave, you just might find that you and the project schedule become invaluable to have around.
if you want to hear about how proactivity leads to sucsess in project controls, shohreh and i talk about it on this webinar.
summarize it – paint a picture
a typical schedule is going to be large, dense and complex. you know it inside and out because you likely built it and are familiar with all of the parts. but your audience is not going to be as well versed with the data as you are.
so it’s your job to put in a form that is understandable, concise and that paints a picture.
you might aim to summarize your scheduling into only 1 or 2 pages. perhaps page 1 shows only the major milestones and their baseline counterparts. and page 2 shows the major disciplines by area, at only level 3.
one option to consider here is to use a visualization tool that will help you to roll everything up. here are some great visualization tools to consider using to help you out.
another approach might be to simply create a 1-pager highlighting the critical path and where the project is on it.
or perhaps you only want to show a forecast of the next 3 months at level 3 of the project schedule, to highlight the impacts of being behind.
there are many ways to take your project schedule’s data and to display just the highlights, the important bits. in fact, we teach you how to build great reports in excel as part of our primavera p6 training.
once you produce something and pass it around, if it makes an impact, your boss or your team will want to see if again next update meeting.
print it – make it visible
one of the easiest things you can do it to print your schedule and keep it handy. consult it often and show the value from the insights you are getting.
don’t just leave it on your pc. pass it around.
got a meeting coming up? print copies for everyone.
make sure you check it during the meeting to show the value it has.
many teams have been known to plot the large gantt chart of the project’s baseline and to pin it on the wall of the main meeting room. just that act alone makes a statement about the importance of the baseline schedule to the team.
share it digitally
my preference is to print the schedule and hand it around for meetings – that makes it a physical object.
but another option is to pass it around digitally. and there are lots of benefits i explain here as to why this works.
while, i’m not advocating for giving everyone a copy of your scheduling tool, there are at least 2 ways i can think up to provide the schedule to the team.
1.email a schedule report in pdf.
if you’re not sure how to get a schedule into pdf with primavera p6, here are the steps.
take the points from earlier in my post – summarize it and paint a picture. then email it out to the team.
in the subject line of the email, don’t just write “march schedule update report” – no one will read it.
rather, add some insight and at-a-glance info. like so:
subject: “march schedule report – currently 23d behind overall, 6 milestones completed late, welding on track”
now that’s an email everyone will want to open. tease them and they will open.
ensure you send your schedule out consistently, and at the same time say every week or month.
2.use a tool like primaverareader (now schedulereader) to provide access to the schedule
schedulereader or seavus project viewer is great for exactly this sort of thing – disseminating project schedules to the team.
the main advantage of using these sorts of viewer tools is that everyone can actually get a full read-only copy of the current schedule and can then dig into it.
i recommend rolling say schedulereader out to a 2-3 team members first to try this approach before you go full team.
schedulereader is very affordable, so this option is a definite consideration.
highlight what’s changed since last update
everyone loves a good comparison, and construction project managers are no exception.
why not highlight progress since last update to clearly show performance?
the schedule is one of the only datasets that can you really perform this comparison on. so pull out last month’s schedule and put it next to the current schedule to see what’s difference.
or better yet, create a report showing the changes. i’m a fan of change inspector software that does exactly this – compares two schedules and reports on the results. but of course, you could try p6’s built-in schedule comparison tool (formerly claim digger).
what you get is usually very insightful.
conclusion
we all wish projects proceeded according to the book – that schedules were primary tools, change management was easy and that the original estimate is exactly what we’re going to build.
unfortunately, the world of construction project management isn’t ideal.
but that doesn’t mean your effort is building and maintaining a project schedule is a waste of time.
i truly believe that cpm schedules are incredibly powerful tools for evaluating performance and forecasting future outcomes.
but that’s you and me.
even if it’s not in your job description, i encourage you to become the “voice of the schedule” and to share insights and issues coming from the schedule with your team, whether they asked for them or not.
don’t sit back and wait for someone to ask you.
your proactive effort might just sway the outcome of the project for the better.
