BradEgeland.com
  • Welcome
  • Blog
  • Expertise
  • Resume
  • Software / Service Reviews
  • Contact
  • Videos
  • Books / White Papers
  • Mentoring Contact Form
  • Awards/Recognition
  • Templates & Downloads
  • Clients
  • Professional Services
  • Past Survey Results

Skipping Shortcuts: Convincing Project Clients to Take the Better Path

8/15/2021

0 Comments

 
Picture
Your clients may not understand why you follow certain practices as a project professional. They may encourage you to take shortcuts that they believe will save time, money, and difficulty. You know better, but how can you convince them?

Doing things the right way make sense, right?

It's like learning a new piece of software. We may hesitate to watch a YouTube video about a new, unfamiliar software product due to "time constraints." Or, we may avoid the product demo for the same reason or because we don’t want to get into a long question-and-answer session with a sales representative. Or, we may avoid reading software guides because we're smart and can "just figure it out"—sort of like not wanting to stop and ask for directions when you're lost.

Does any of this sound familiar? I have been guilty of all of these things (including not stopping to ask for directions) and, often, I realized only later that they were bad ideas. What seemed to be a shortcut wasn’t really a shortcut at all. It frustrated me, took more of my time than it should have, and left me less prepared and functional than I would have been had I taken the proper amount of time to learn up front. In some cases, the "shortcut" took so much time that I abandoned the new product altogether because I no longer had the time to figure it out.

If any of these situations applies to you as a project professional, then you probably understand where your project clients are coming from if they fail to see value in certain practices you're trying to implement on the projects you’re leading for them. They may not see the value in a detailed status report. They may not understand why it's important to spend three weeks (in their eyes, three expensive weeks) hammering out good, detailed requirements when they can tell you what they want in thirty minutes.

They may not understand your urge to interview subject matter experts (SMEs) and end-users in their organization—again, all of which costs them time and money—when they’ve already come to you with the problem that they believe should tell you everything you need to know. And, the very mention of change requests may have them on the phone trying to contact another delivery organization because they think you’re out to get them. A simple weekly email can replace weekly status calls, right? Um … no.


But, how do you convince the stubborn (and potentially "cheap") project client that these are critical practices that will likely save them money, time, and heartache in the long run? You've been through this before, but maybe they haven't. What’s your approach?

Let's look at a few of these typical client push backs and discuss how to approach each in a way that will help your clients understand the importance of planning, thorough documentation, formal signoff, and frequent and thorough communication.

Thorough Requirements Definition

One of the hardest things to get the client to understand is the need for thorough, up-front—and often extensive and time-consuming—requirements analysis and documentation. Project sponsors often think they’re coming into the engagement fully equipped with detailed (or, at least detailed enough) requirements. They hand these requirements to your team, and you create a solution, right?

The problem is that, at least sometimes, you're really being handed a symptom instead of the real problem. And, you're likely being handed high- to mid-level requirements, not the detailed requirements that relate to real business process and that will truly matter as you’re developing the solution. That's why you must engage more than just the project sponsor. Future system end-users, the organization SMEs, and the business process owners must be engaged in the requirements definition phase so that the issue, problem, or project is fully understood and defined and so that requirements are detailed enough to create a useable end solution from.

How do you convince your project client of this? The best way is to explain what late-project rework can mean in terms of time and money compared to taking an extra two to three weeks now to plan out the scope and requirements of the project and to get a formal agreement on those requirements. Examples of past project issues may help your clients better understand that this is in their best interest.

Status Reporting, Status Calls, and Project-schedule Tracking

What about the clients who aren’t interested in what they consider to be “time-wasting” weekly status calls and the “busy work” of reviewing status reports and weekly project-schedule revisions. These project clients are rare, but they exist. They just don’t want to be bothered, and they may not see the need for paying a project manager to spend so much time on these items.

When this happens, I do two things:


First, I explain that it's critical on my side to perform these tasks so that my team can work efficiently—and, therefore, less expensively—on the clients’ solutions because the team will know the project status and what they’re responsible for, and they’ll assume more ownership of the tasks. Plus, it's best that clients know where things stand so they can hold my team and me accountable. Then, I slip in several tasks that the clients have to be accountable for so they remain engaged and see value in these processes.

Second, I make sure that I only include what is absolutely necessary in the status report, what we discuss on the call, and what I filter out to the clients in a project schedule update. Keeping it simple helps them to better understand what I’m giving them.

Risk Planning

Many clients want nothing to do with risk planning because they think it's a waste of time. Why spend a few sessions discussing things that haven’t happened and may not happen?

To show value to clients, I make sure they're involved in identifying and planning for risks whenever possible. I ask them a lot of questions, because many of the risks will involve business processes in their organizations that can greatly affect the outcome of the project and the functionality of the solution I deliver to them.
​

Show your clients that by fully understanding the needs and the potential issues in their organizations now, your team can avoid expensive and time-consuming rework later on.
0 Comments



Leave a Reply.

    Author:

    Picture

    Brad Egeland


    Named the "#1 Provider of Project Management Content in the World," Brad Egeland has over 25 years of professional IT experience as a developer, manager, project manager, cybersecurity enthusiast, consultant and author.  He has written more than 8,000 expert online articles, eBooks, white papers and video articles for clients worldwide.  If you want Brad to write for your site, contact him. Want your content on this blog and promoted? Contact him. Looking for advice/menoring? Contact him.

    Picture
    Picture
    Picture
    Picture
    Picture
    Picture

    RSS Feed

    Archives

    December 2022
    November 2022
    October 2022
    September 2022
    August 2022
    July 2022
    June 2022
    May 2022
    April 2022
    March 2022
    February 2022
    January 2022
    December 2021
    November 2021
    October 2021
    September 2021
    August 2021
    July 2021
    June 2021
    May 2021
    April 2021
    March 2021
    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    May 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012
    September 2012
    August 2012
    July 2012
    June 2012
    May 2012
    April 2012
    March 2012
    February 2012
    January 2012
    December 2011
    November 2011
    October 2011
    September 2011
    August 2011
    July 2011
    June 2011
    May 2011
    March 2011
    January 2011
    December 2010
    November 2010
    October 2010
    September 2010
    August 2010
    June 2010
    May 2010
    April 2010
    March 2010
    November 2009

    RSS Feed

Powered by Create your own unique website with customizable templates.