Close and Go BackBack to Viget

Push it Real Good

Stephanie Hay
Nov 06 2007
1 Comment
Stephanie Hay - Project Manager :

Trying to navigate the sensitive communication involved in keeping a project within scope in the early stages of your relationship with a client can be tricky.  When a client begins to ask for bells and whistles beyond the original discussions, but doesn’t want to compromise on budget or timeline, it’s essential that project managers be comfortable pushing back.

Being honest early in the relationship that some seemingly “simple” changes can dramatically affect the bottom line or the launch date will set the stage to promote effective communication. Just as we—a dynamic, full-service web consulting company (and a fabulous one, at that)—are accountable for the quality and deliverables of our work, the client must be responsible for making informed choices.  She can’t do that if, instead of openly mentioning the impact of those decisions, we quietly scramble to try and accommodate her requests.  Keeping mum until the critical final stages can lead to the client *understandably* wondering why the project is late and over budget.

On the flipside, allowing for some flexibility whenever possible shows the client that her wishes are being weighed realistically.  Committing to five small changes might push the limits of the budget, but their effect on the overall relationship with the client could be priceless—particularly if that flexibility and nimble reaction leads to future work.

Learning to balance this desire to please with the realistic constraints of money and time is a challenge project managers wrestle with each day. But our long-term relationships with clients—and their ongoing commitment to our company—is dependent upon us demonstrating the utmost integrity and honesty during a site build, especially when we have to say “no.”

Patrick Reagan - Director, Application Development said on 11/08 at 10:47 AM

Steph - good points.

I think that frequent communication within the project team is essential - the client is most definitely a part of this team.  Knowing when something that seems “simple” is actually going to take a lot longer than anticipated is important and should be communicated immediately to the team.  This helps the customer to make an informed decision when prioritizing that work as it relates to their business objectives.  For example, a feature that takes 2 hours to implement may be worth doing for the current release, but if it instead takes 2 days it might make sense to push it to the next iteration or even to a future release.

This is where Agile processes help the entire team - with a focus on constant communication and flexibility through iterative development, together we can make small course corrections that optimize the effectiveness of the team.  Clients will sometimes have the misconception that if they don’t state everything they want up front, they will never get it when it comes time to launch the final product.  Instead of a process that relies on big design up front (BDUF), we are able to work with clients to prioritize functionality based on impact, level of effort, and how each feature aligns with their business objectives.
-----

Name:

Email:

URL:

Not a robot? Prove it by entering the word below.


Remember my personal information

Notify me of follow-up comments?

Discuss Web Strategy With Viget Labs