Business-focused custom software

Go Back

Project success tip: Provide a single point of contact

Whenever I’ve heard people talk about the importance of a single point of contact for communication between the developer and the “customer”, I’ve thought this was primarily to protect team members from unnecessary emails and meetings. But what I’ve come to realize is how important this is to project health generally, for a couple of reasons:

Consistent message

If only one person is giving the programmer feedback, they are less likely to get conflicting messages about how things should work.

Less communication about the communication

As a programmer on the outside of an organization, I often can’t tell who will have the answers to my questions. This means that when I have a question I have a few options:

  • Send an email to everyone on the project, and hope that the right someone responds.
  • Send an email to who I think is the right someone, and hope that they respond if they are the right someone, and that they redirect me if I’m not.

Unfortunately, my hopes are not always realized.

I have found that what works best is for there to be a project manager or other person within the organization who coordinates communication with me. That way, I’m not sending email to 5 people, and hoping one of them will respond to my questions. It also works best if this person is a decision maker, because that can mean faster answers than if they have to run it by someone else.

  • Facebook
  • Twitter
  • Digg It!
  • StumbleUpon
  • Technorati
  • Reddit

Comments  2

  1. Mark W. Schumann 05 Mar

    What Avonelle said.

    One of my worst Client Hell stories ever was when the CEO was traveling on business in China for much of the year, spanning most of the duration of the software project. His proxies didn't quite understand his priorities and intentions for the project, and tended to substitute their own opinions.

    This appeared to work reasonably well until the CEO got back. Much dissatisfaction ensued.

    You need the client to have a <em>single point of contact</em> but also--echoing my recent rant!--you need them to sign for it. Otherwise you're reduced to guessing at what they want, and that's never good.
  2. Avonelle Lovhaug 05 Mar

    It is sad but true - guessing at what they want rarely works!
Post a comment!

Formatting options

Wanna Subscribe?
Here's the RSS Feed

What the critics are saying...

As someone with over 20 years of software development experience and currently a small business owner, it has been a pleasure working with Avonelle. In addition to being a talented developer, Avonelle also has database expertise and system design skills. Avonelle is open minded and willing to discuss various methodologies for achieving a project goal. She is also not afraid to ask questions which is vital in a software development project. Her up-front project cost (not estimate) is very helpful in budgeting for a project.

--Dwayne Wolterstorff, Owner @ Fair