How Top Engineering Leaders Build High-Performance Teams

Krishna Mohan
BeautifulCode Talks
6 min readJul 22, 2019
VP Engineering/CTO building a high performance team

VPs of Engineering and CTOs have one overarching goal: to build and retain a high-performance team that can deliver quality products on time.

To create teams of talented people that work together effectively, a leader must maintain a strong focus on finding and hiring the best engineers and managers, as well as building a positive company culture. In this article, we’ll take a look at how some of the top engineering leaders in the business approach this task.

Building the Right Team Starts with Hiring the Right People

Okta’s CEO, Todd McKinnon, says his team flourishes because they’ve made hiring as easy as possible. Unlike some companies, which require unanimous approval of every hire, Okta allows hiring managers to sign on new employees right away. McKinnnon says that some of the best engineers on his team would not have been brought on if the hiring process had required unanimous approval.

Of course, hiring the right people means creating an environment where talented people want to work. HubSpot co-founder Dharmesh Shah, when describing how he attracts what he calls “exceptional” people to work for him, said that he creates a company culture that’s rooted in growing the individual market value of each employee. Unlike some tech companies, which offer perks like flex-time, games, and company parties, HubSpot focuses on advancing individual value. That way, Shah says, he knows he can attract people who like to learn, grow, and advance.

HubSpot offers its engineers perks like its unlimited meal program, which encourages staff to invite mentors to lunch in order to learn from them. Employees can expense these meals with no approval required. HubSpot also offers employees access to its impressive alumni group, which meets every quarter and brings together some of the best engineers in the business.

Create a Cultural Manifesto to Build Strong Teams

Most top leaders agree that a “cultural manifesto” is the key to building strong engineering teams. A cultural manifesto — also called a culture code, or a culture handbook — is a document that lays out a company’s values, goals, and working methods.

It’s a repository of the company’s shared experience. A cultural manifesto isn’t just a feel-good declaration, motto, or set of directives — it’s the backbone of a strong company. It holds the company’s teams together, making them greater than the sum of their parts. Cultural manifestos have been shown to have a positive impact on company success, boosting revenues by as much as 400%.

MIT scholar Edward Schein defines culture as a “pattern of basic assumptions” which are invented, discovered, or developed by a group as it works through its problems. Those basic assumptions, values, and problem-solving techniques become part of the organization’s “culture” as soon as they are codified into something that can be taught to new employees.

That’s why having a cultural manifesto is so crucial when it comes to scaling teams. A manifesto makes it easy to communicate shared values and methods when onboarding new staff.

It’s no wonder that Kevin Scott, LinkedIn’s VP of engineering, called a cultural manifesto “the single most valuable management tool while you’re scaling your engineering team.” HubSpot is also renowned for its strong cultural manifesto, which co-founder Dharmesh Shah spent 200 hours crafting. Shah says it’s paid off by creating a strong, cohesive team that’s flexible enough to adapt to new challenges. HubSpot has put together a free guide for creating your own cultural manifesto.

The 12-Month Roadmap

Just as a cultural manifesto is important for setting your team’s big-picture goals, a roadmap can point your team in the right direction on small and mid-size projects.

A roadmap is more than just a to-do list or a step-by-step plan for delivering your product — it’s an overview of the product plan. It should be clear, adaptable guide created with input from your team.

Okta CEO Todd McKinnon recommends using 12-month roadmaps for product areas and for infrastructure. The roadmap itself is simple. It is, in his words, a “high-level list of what you need to accomplish in your product and underlying technology.”

He recommends writing this roadmap down and sharing it with the company at large to get everyone on the same page. McKinnon also recommends crafting a 12-month roadmap for software architecture.

That’s where collaboration really comes into play, since McKinnon also recommends creating a virtual team with members of all the groups in the engineering organization to own and manage software architecture projects.

Management

In the tech world, most VPs and CTOs start out as engineers. While that provides them with a good bottom-up understanding of the company, it can have an unexpected drawback; all too often, VPs focus on the process of coding rather than on managing their teams.

In fact, managing and developing are hugely different positions, and VPs need to focus on the human aspect more. They also need to be aware that cultural problems within an organization, especially a large company or one that’s in the process of scaling, aren’t always as easy to remedy as coding problems.

Part of being a great manager is keeping your team members both happy and challenged. You want your engineers to feel a sense of ownership and investment in the projects they work on. You also want to clearly define each employee’s role. There are different ways of going about this; some managers like to move employees around from project to project, while others like to encourage people to specialize in one area.

McKinnon recommends a more permanent model, which allows people to build expertise and a stronger sense of ownership. He also urges managers to conduct frequent evaluations of employees. Not only will this tip off managers to any issues in the team’s functioning, it will give engineers a sense of their worth and value within the company; high-performing employees will appreciate the reassurance, and any poor performers will benefit from clear, focused feedback.

Collaboration

Effective collaboration and communication are vital for any team aiming to deliver high-quality products on schedule. But collaboration doesn’t happen automatically; simply hiring a group of talented engineers and putting them in a room together won’t guarantee you an effective team.

More often than not, there will be some inherent tension between the different members of an engineering team. Employees from different departments will inevitably have different priorities, which will sometimes clash. It takes patience, open communication, and a clear understanding of everyone’s roles to get all the members of a team working together toward a common goal.

Final Thoughts

Ironically, sometimes one of the best ways to improve teamwork and create a cohesive culture is to increase autonomy among your employees. Werner Vogels, Amazon’s CTO, spoke about this back in 2006. Vogels credited Amazon’s small teams with creating a sense of responsibility among its staff and nurturing a can-do attitude. He said, “the services model has been a key enabler in creating teams that can innovate quickly with a strong customer focus. Each service has a team associated with it, and that team is completely responsible for the service — from scoping out the functionality, to architecting it, building it, and operating it.”

Vogel added that empowering developers and charging them with overseeing their product through all of the stages of operation made for a strong sense of ownership and responsibility.

In the end, it all boils down to a few fairly simple ideas:

  • Hire the right people, and give them the tools they need to do their jobs
  • Encourage collaboration between team members
  • Establish a strong organizational culture and write a clear cultural manifesto
  • Create project roadmaps and share them with the entire company
  • Define employee roles, encourage growth, and give regular feedback
  • Encourage a sense of ownership through employee autonomy

If you’re a VP or CTO, these will almost certainly be issues you’ve had to wrestle with before and that you’ll encounter again in the future. Forming a great team isn’t easy, but it’s crucial if you want to create a company that stands above the competition.

--

--