Skip to main content

Lessons from Donald

I am very fortunate to be surrounded by some amazing people. Some of them I learn something from. These are lessons from Donald.

#1 Help if people are asking for your help.
There is one pattern I see Donald do that continuously makes him a great resource. Donald will help you if you legitimately asks you for help.

#2 Don't correct people's mistakes before they make them.
This one goes hand in hand with #1. When Donald told me about this it was in a context of football, it went something like this: “a smart blocker doesn't take the ball away form a player because he is scared of a fumble, a smart blocker just gets ready to jump on the ball the second the fumble actually happens”

#3 Ask people for help if you can use it.
Asking people for help gets them bought into your goals. If they don't like your agenda you will hear it early, if they do then they will feel like a part of the team.

#4 People don't like surprises.
Marriage proposals and occasional flowers notwithstanding people don't like surprises. Prep people if you can prep them. It's best if they are bored in a meeting instead of defensive or scared.
Post a Comment

Popular posts from this blog

Lessons from my 9 Year Journey with DocuSign

After over 9 years at DocuSign I am taking on a new challenge.  It’s been phenomenal seeing the
company grow from from 25 to 2000 employees.  DocuSign has changed the way the people do business and I am proud of it.  The next chapter is going to be heading up software development at Tempo Automation - a 25 person startup that is changing the way people produce electronics.  While I am extremely excited about the future, this is a good time to reflect on my journey and share the things that contributed to the success and things that I will do differently next time around.
1: Focus on the Customer One of the key things that contributed to the success of DocuSign and my personal career is relentless focus on the customer success.  From the very beginning our CTO has taken meetings, listened and prioritized requests and feedback coming from customers.  People who could not be bothered by customer requests didn’t last long.  As a result over time our engineering team retained and reward…

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 …

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!