Skip to main content

Concentrate on the Work

A software manager must be able to balance creative independence, strong technical opinions, staff

turnover and business continuity.  Personnel factors such as work/life balance, diversity and personal growth also add complexity to this mix.  When navigating all of this becomes tough, my advice is to get back to focusing on the work.

When I was re-reading Instructions to the Tenzo – an ancient Zen text for the monastery cooks - this paragraph seemed to be applicable to the modern day software development:

“Do not just leave washing the rice or preparing the vegetables to others but use your own hands, your own eyes, your own sincerity. Do not fragment your attention but see what each moment calls for; if you take care of just one thing then you will be careless of the other. Do not miss the opportunity of offering even a single drop into the ocean of merit or a grain atop the mountain of the roots of beneficial activity.”

These instructions that have lasted centuries contain several layers of information and seem to be too detailed, but within that specificity one can find the secret to longevity.  For instance, bringing the attention back to “washing the rice” is similar to bringing attention back to “building the product,” or “solving customers’ problems”.

- When there are problems with egos, the best way to diffuse this is to focus on solving the problem.
- When you feel like your colleague is not pulling his weight, the best way to confront this is in the context of solving the customers’ problem.
- When someone is carelessly breaking the build, the best way to handle this is to focus on actually fixing the problem, rather than passing judgment about someone’s work style.

As a manager, when focus drifts away from work, it is good to ask yourself: “Do I have the right environment that allows good people to focus?”

In his book, “Hard Thing about Hard Things,” Ben Horowitz cites a conversation he had about bad organizations:

“Let me break it down for you. In good organizations, people can focus on their work and have confidence that if they get their work done, good things will happen for both the company and them personally. It is a true pleasure to work in an organization such as this. Every person can wake up knowing that the work they do will be efficient, effective, and make a difference for the organization and themselves. These things make their jobs both motivating and fulfilling.
In a poor organization, on the other hand, people spend much of their time fighting organizational boundaries, infighting, and broken processes. They are not even clear on what their jobs are, so there is no way to know if they are getting the job done or not.”
 Horowitz, Ben (2014-03-04). The Hard Thing About Hard Things

When the conversation can’t stay focused on the work and solving customer problems, the first thing to ask is, “Do you have the right environment, vision and visibility to let people know that the work is the reason they are there in the first place?”

-mb

If you liked this blog post you might want to check out: Three Pillars of Engineering Management and Win Forever posts.

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!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…