It’s about the business, not the tech
To set the scene let’s define the term director to mean a manager of managers. In addition, a director isn’t an executive (a person reporting to the CEO) in companies above a certain size (100?).
So you start your career in software engineering in some entry role. At some point you transition to a managerial role. Usually the first managerial role is a Team Lead, which is essentially a line manager: responsible for day-to-day operations, making sure the team does what it needs to do. To use a trench as a metaphor: as a line manager you are mostly inside the trench, unable to peek outside. Sometimes you might climb a ladder and have a short peek. But you’re mostly confined to the world which is your team and its responsibilities. All of your past experience has granted you a lot of technical know-how which is one of your most powerful tools as a leader - it’s the basis of the trust and confidence you gain from your team members.
At some point you step into the role of a director. You’re mostly able to climb the ladder and observe outside, even step out of the trench. There’s now an organization that you’re in charge of. Naturally, you keep doing what made you successful before.
The worst mistake you can make at this level is failing to understand that however unique, specialized, hard-earned or valuable all of your technical knowledge is, it is not as valuable anymore. Why is that? Because you’re no longer in charge of a team’s daily operations. Instead, you are (mostly) free to set your own schedule and priorities to make sure that a tangible business goal is being achieved. Business goals can be stated simply but are complex and require a lot of work to be achieved - that work is too big for any one person, so it’s spread across teams, and your job is to steer those teams, not run them.
I’ll state this simply:
A director must be able to connect a line from every decision they make to clear business outcomes. In the purest form, the business impact is measured as an increase in revenue or decrease in spending. Every decision that cannot have a stated path that leads to business impact should be questioned.
Example (made up): “We are going to invest 3 engineering person-months in the org to optimize the most expensive service we have running in production in order to reduce at least 5% of our annual cloud spending.”
(You might have a good reason to believe that 5% is achievable or you have purposefully set a high bar; the 5% figure should also be commensurate to 3 months’ salary so afterwards there are recurring savings and the engineers are free to do something else)
(Also: this is probably irrelevant to small start-ups where a small team will race and do whatever it takes to make something happen)
Just to clarify the argument, “tech” in this post’s headline is taken to mean some team-level decision: if a code change is approved and/or deployed; adoption of a new tool, framework or technology; how to monitor the system, etc. These are usually detached from clear business outcomes.
If the job is about the business, it means that you have to focus your attention on what will make you succeed in it (otherwise, I have no idea why you’re doing this job). I boil it down to 3 clear themes:
- Relationships
- Communication
- Engagement
The last two points will be expanded on in future posts, so here I’ll focus on the first theme - relationships. The reason I want to emphasize this theme is that I’ve seen what happens when people fail to understand it. The result is never pretty.
You have to understand that when you are in charge of delivering a business goal, it means your responsibility exceeds your authority. There are some things that must happen for the goal to be achieved, but you can’t perform them in your org with the people you manage directly and indirectly. Some examples:
- You need to expand and hire new people but can’t approve the additional headcount. For that you need the right people in the org to approve the headcount as it incurs additional budget commitment.
- You need legal advice on how to comply with updated regulation. For that you’ll probably need your company’s legal department.
- You need to purchase software, licenses, hardware or other things. For that you need to go through the procurement process.
So yes, on the face of it all of these other people that perform diverse functions should do their jobs and help you with achieving your goals, but the reality is that they have their own set of goals and incoming requests from other people that need to be prioritized. If you establish good relationships with other functions in the company then you remove one barrier (of being unknown to them or even worse, being considered as a “don’t want to hear them” kind of person) from the path of reaching your goals. It’s not a guarantee you will reach them, it just improves your odds. This might sound cold, and it is cold to some degree. But if all of the managers in a company have their goals, and they all try to deliver them, isn’t it easier when you’re just kind to one another and help each other out?
It’s important to remember that a relationship is bi-directional. You can’t expect to receive without giving back. Other functions in the company will need you to meet their goals. Sure, you can always snub them with the excuse that you can’t help because you have your own priorities, but that approach guarantees you’ll make enemies instead of friends and be on the short path to failure. Essentially this means that your higher role entails added risk - that of relying on your colleagues for your own success.
The risk manifests in two ways:
- Your colleagues might be absent for a number of reasons, or be incompetent. You still have to meet your goals, no one cares if your colleagues aren’t there, literally or figuratively.
- Despite your best intent and effort you might not receive a welcoming hand from the other side. You still have to meet your goals, no one cares if your colleagues don’t like you.
The added risk likely translates to better financial compensation, just like in economic theory (added risk entails greater return on investment).
In addition, you likely don’t have the full picture of a particular issue. Your colleagues have skills, information and knowledge that can help you understand how to solve a problem you face. They might even help you realize the problem isn’t really a problem and you can move on and invest your time somewhere else. In other words, you and your colleagues can make a whole that is greater than the sum of its parts - the definition of synergy.
Another fine point to touch upon is that in this position you are responsible for translating technical lingo to non-tech figures in the company, and vice versa: translating non-technical requirements into technical ones for your org to implement. I’ll touch on this when I expand theme 2 (Communication).
Tip: leverage your colleagues. This by no means is intended to mean exploiting your colleagues. Your colleagues are a resource that the organization grants you to succeed in your role. Work with them, building on their expertise, so they could contribute, thrive and actually be valuable. Don’t rob them of this opportunity! If you do, how can you expect them to never rob you of your own opportunities? Ask them to step in. Listen to what they have to say. You don’t have to accept their advice, but you do have to listen to it.
Remember: as a director, you have to keep your eyes on the business. The tech is just a tool the business uses.