6 Comments

  1. Michael Cruse

    You make some excellent points regarding the importance of communication. People love information and can quickly feel ignored if the flow of information is sparse.

    There is nothing wrong with sending updates every couple week that only says our heads are down working on this or that. People know that the project is alive and moving forward. Furthermore, I love the suggestion about industry information or best-practice sharing. This is an excellent value add communication and builds authenticity.

    Report

  2. Y J Shah

    Hey Jeff,
    Nice one!

    I have written an article about how communication skills can help grow your freelancing business. Please have a read to this post. You could get couple more live cases to help readers understand practically.

    Best Regards,
    Y J Shah

    Report

  3. Peter Cralen

    Agree. Cool post Jeff.
    If I choose a plugin/service, I always check how the developer is active. Checking changelog, last update, blog, twitter …
    Even if a plugin/service looks cool but not any noise from a developer/company for two-three months, I hold back.

    What I also like is if I know what I can expect from the plugin in near future, not many developers has something like a roadmap or at least some thoughts about a direction where he try to move.
    Usually, I don’t build a business or website for one month, so know something more about tools/services what I use is always appreciated. I also enjoy contact with a developer (comment, twitter, forum …) as I prefer some kind of relationship instead of just filling a credit card data to a form.

    Report

  4. Andreas Nurbo

    Its interesting too look at the WP project itself in this regard. It(they?) have improved greatly over the years. Before things were hidden away att hallway discussions in WordCamps, or barbeque parties, some things probably still is, but overall things are much more transparent and inclusive nowadays. Now with the make blogs, slack and being easily able to link to discussions etc things are only going to get better. Given the long time period things are decided and separate projects being made such as the REST API and Fields API etc there is risk of things getting too spread out again but so far everything is relatively easy to trace. One improvement would be if there was a log of all the meetings with a link back to slack. That would be a great addition I think.

    Report

  5. Jupiter Jim

    Yes, I love how iThemes owned up to the problem and went to work to fix it immediately and kept the public up to date. It’s analogous to having a boss who screws up and does NOT admit it. Everyone knows the boss screwed up. So pretending it didn’t happen solves nothing and causes people to instantly lose respect that is extremely difficult to get back that respect. Same thing with plugin and theme developers whose product develops a problem dealing with security or functionality. By having blog posts, email lists, twitter followers, etc., the proper and necessary communication can get out to clients and user as quickly as possible. Companies who delete unpleasant tweets instead of responding to legitimate concerns, is another poor way of dealing with your paying public! Thanks for sharing.

    Report

Comments are closed.

%d bloggers like this: