I *never* like to talk about a client project until it’s complete, the client has signed off and final payment is received.
Well as much fun as it may be for some to add a “me too” to a conversation online about a pending project they may be part of – it is NOT good practice to discuss the when’s and what ifs while a project is still in development phase. . . because too much could change.
Now some of you may argue that building buzz is a good thing. And yes, in certain cases it could be. . . but when it comes to forcing talk about a launch date online about a ‘new widget x’ that no one yet knows about – well, that can do more harm than good.
Here are a few reasons why you and other contractors who may be helping (or hurting) the project should not discuss it until it has final approval from the client and the paycheck has cleared the bank.
1. The scope of the project could change. Enough said. >>
2. Making the promise of a launch date too soon, only to miss it because of scope creep (or natural disaster, family death etc), only makes you and/or your team look bad.
3. It’s better to promote the final completed ‘new widget x’ than what the project MAY be. (see #1) >>
4. NEVER promote or announce a newly designed anything until said newly designed something is READY for launch. (If you are an independent contractor you should know not to divulge your client’s ‘new widget X’ info just to get yourself a little attention online) >>
5. Be respectful of not putting your client on the spot. By publicly divulging info on ‘new widget x’ you may be putting unnecessary pressure on your client to rush to launch. This is not a good thing. If your client isn’t ready for ‘new widget x’ to launch yet and feels pressured to do so because of your online antics . . . it WILL show. . . and not in a good way. >>
My best advice? Be patient. . . and be quiet online until the client is ready to shout the news of ‘new widget x’ from the roof tops.