Skip to main content

Why I hate meetings, emails and phone calls




I hate meetings, emails and phone calls.  Does that mean I am a complete introvert that doesn’t like talking to people?  Not at all!  I just hate telling the same story or giving people the same answer over and over again.

In defense of meetings – I actually love the richness of communication that face-to-face communication offers.   However, what I find is a lot of folks actually do not take full advantage of this communication and are sort of half there.  Often times I look at a meeting and everyone but a couple of people are on their computers checking e-mail.  What’s the point of being in the same room if that’s what you are going to do?

Meetings, e-mails and phone calls miss a key component that new means of communication offer.  That key component is broadcasting.  A lot of information that people need is actually relevant for a lot of people.  When I created DocuSign DevCenter I specifically tried to push most of the communication to the forum.  At first people were really upset.  Salespeople came over to my desk wondering: “it’s a customer who needs help, just pick up the phone and talk to them!”  The strategy ended up paying off: thousands of developers shared questions and answers and now we have days when some posts are viewed 60,000+ times!

Of course a lot of communication is not meant for broadcasting, with the proliferation of social media I would argue that some folks actually dialed their broadcasting a little too far.  In the corporate world deal negotiations, performance reviews and trade secrets should all be disclosed in private.  Make those phone calls, attend those meetings and stay focused on the people you are in the room with.

For work related questions I always encourage folks to start with DocuSign DevCenter (www.docusign.com/devcenter) and for personal inquiries I am always reachable via Twitter: @mikebz, G+: https://plus.google.com/112023503898972747539 and FB: http://fb.me/mikebz

Happy Broadcasting!

Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …