Building Effective Cross-Departmental Collaboration

As a CTO, successful collaboration with various departments is vital for the overall success of your company and your career. Each department plays a unique role, and understanding how to work effectively with them can lead to a more cohesive and efficient organization.

As stated in the chapter titled “Defining the Role of a CTO,” the duties of a CTO are closely linked to the company’s stage, but ultimately require other key skills in addition to technical abilities.

As a bridge between the company’s interests, resources, budget, and your team, your role is to produce the maximum benefit with limited resources, both budget and people. This activity is rarely just a technical issue. You will need to work with the finance department for budget conversations. The Marketing department will help acquire customers. Customer service will handle any issues that arise, and the Operations team will use your product in the field. You will also work with the Product Management team, your closest peer, to develop the product.

In this chapter, we will discuss some of the departments you will likely work with and provide some tips to create a collaborative work environment.

Collaboration between Product Management and Engineering

Product Management and Engineering teams are the two most critical departments in any technology company. The product managers, designers, and UX people are responsible for understanding customer needs, defining product vision, and creating the product roadmap. The engineering team is responsible for delivering the product, maintaining the technical infrastructure, and supporting the product in production.

The success of any technology company depends on how harmoniously these two teams collaborate. One of the most significant difficulties that arise is communication. The product managers are often focused on defining the product’s vision, and the engineering team’s focus is on delivering the product. This can create a communication gap between the teams, leading to misunderstandings, missed deadlines, and, ultimately, product failure.

Ben Horowitz, one of the founders of Andreessen Horowitz, summarizes the situation perfectly with his famous quote “Product manages what, engineers know how.” This principle can be a motto to overcome communication difficulties between product and engineering teams.

However, this motto should not prevent engineers from sharing their vision and knowledge. You need to create a healthy environment and communication channel where engineers can freely share their ideas with the product team, object to the tickets assigned to them, and suggest new features if necessary.

Often, this communication channel is created solely through your efforts. Ultimately, you are hoping to bring together people from two different disciplines and make them understand each other well. If there is a Chief Product Officer (CPO) in the company or whoever is responsible for the product team, you should discuss what these channels will be, what the feedback mechanism will be, and make a decision in a flow. It may seem like a bit of formality, but it’s not. Shaking hands on principles and guidelines while all relationships are healthy usually yields much better results than doing it when the environment is tense.

I assume that you already practice one or more agile principles. So I will not go into all the details of Scrum or Kanban but I still believe one of the most crucial but sometimes overlooked aspects of Agile, Product Refinement meetings (Grooming) still deserves a quick look.

Product Backlog Refinement meetings involve reviewing the product backlog, which is a prioritized list of features and requirements for the product. The product team and engineering team work together to refine the backlog, adding or removing items as needed, and ensuring that the backlog accurately reflects the product vision and customer needs.

During the meeting, the product team typically presents the items at the top of the backlog, providing context on why they are important and what problem they are trying to solve. The engineering team then provides feedback on the feasibility of implementing the item and estimates the effort required to do so. Together, the two teams work to ensure that the backlog is well-defined and prioritized appropriately.

Product Backlog Refinement meetings should be held regularly, usually once every two weeks. By conducting these meetings regularly, you can ensure that the backlog is up-to-date and that the product vision is aligned with customer needs. These meetings also provide an opportunity to identify and address any issues or concerns before they become problems.

In addition to refining the backlog, Product Backlog Refinement meetings also provide an opportunity for the teams to discuss any changes to the product vision or customer needs. By keeping the backlog up-to-date and ensuring that it accurately reflects the product vision and customer needs, you can maintain a clear direction for the project and avoid any miscommunications or misunderstandings.

Overall, Product Backlog Refinement meetings are an essential part of the agile development process. By working together to prioritize and refine the backlog, you can ensure that your product is aligned with customer needs and has a clear direction.

Sprint planning and retrospectives are also essential aspects of Agile. Sprint planning involves reviewing the product backlog and selecting the items that will be worked on during the sprint. The product team and engineering team work together to estimate the effort required for each item and plan the work that will be done during the sprint. Sprint retrospectives are meetings that occur at the end of each sprint to review the team’s performance and identify areas for improvement.

As a CTO, it is your responsibility to ensure that these methodologies are implemented effectively. You should also encourage your teams to provide feedback on the process and identify areas for improvement. By fostering a culture of continuous improvement, you can ensure that your teams are working together effectively and delivering high-quality products that meet customer needs.

Another important aspect of collaboration between Product Management and Engineering is the use of tools. There are many tools available that can help teams collaborate more effectively. For example, project management tools such as Jira, Trello, or Asana can be used to track progress, assign tasks, and monitor deadlines. Communication tools such as Slack or Microsoft Teams can be used to facilitate real-time communication between team members.

Product and engineering teams may have different tastes when it comes to tool selection. While this should be understood to a certain extent, it is essential to make a decision on a single product for common use. I have spent almost the last 20 years of my career using Jira. I must admit that it is far from being my favorite tool in terms of user interface and usability. However, considering its functionality and the intensity of its use in the industry, I still think it is one of the most reasonable choices. If you don’t have a specific preference, I can say go with Jira for your decision.

In Jira, the path your issues take from creation to completion is called workflow. Each workflow is composed of a set of statuses and transitions that your issue moves through during its lifecycle and typically represents work processes within your organization. Product and engineering teams should go through these workflows in Jira and start the process after making a decision on the definition of done. Of course, continuous improvement principles also apply here. The workflow is refined as needed and the process is kept simple but meets the company’s requirements.

Designers and UX people are also an essential part of the Product Management team. They are responsible for creating the product’s user experience, which is critical to the product’s success. Therefore, it is essential to ensure that they are included in all discussions and decisions related to the product. They should be encouraged to share their insights and feedback, and their contributions should be valued.

Engineering teams are often thought of as having weak profiles in design and usability as a stereotype. Throughout my career, I have witnessed hundreds of times that this bias is wrong. I have seen so many engineers who are gifted in creating user-friendly interfaces and who know their customers very well that not utilizing their contributions would be a huge waste for the company. Including design and UX teams in meetings such as product refinement and backlog planning, as I mentioned earlier, is therefore very meaningful in keeping the communication channel open.

Discussions between product and engineering teams should rely solely on relevant and trustworthy data. Statements prefaced with “in my opinion” are not statements at all, but rather opinions, which unfortunately hold little value. Anyone can have a right or wrong opinion, regardless of their title or salary. When making decisions as a team, the focus should be on the data at hand. However, what if there isn’t enough data available to develop a feature or even test if it works? In these cases, it’s best to quickly create a minimum viable product (MVP) with minimal resources. For more information, refer to the relevant chapter of the book.

Collaboration between Marketing and Engineering

Collaboration with Marketing is equally important for the success of any technology company. One of the most significant difficulties that arise when working with Marketing is a lack of alignment on goals and priorities. While the Engineering team is typically focused on technical feasibility and delivery, Marketing’s focus is on customer acquisition and retention. This can create a communication gap between the teams, leading to misunderstandings and missed opportunities.

To overcome this communication gap, it’s essential to create a shared understanding of the project’s goals and priorities. Working together to develop a shared vision for the project and aligning on key performance indicators (KPIs) can help ensure that the Engineering and Marketing teams are working towards the same objectives.

Tools such as project management software, communication platforms, and data analytics tools can help facilitate collaboration between Marketing and Engineering teams. For example, project management tools like Jira can be used to track progress and assign tasks, while communication platforms like Slack can be used to facilitate real-time communication between team members. Data analytics tools like Google Analytics or Adobe Omniture can be used to track user behavior and help inform decision-making.

When working with Marketing, it’s crucial to emphasize the importance of data-driven decision-making. Rather than relying on subjective opinions or assumptions, decisions should be based on relevant and reliable data. This requires a culture of continuous learning and improvement, where data is used to drive discussions and decision-making.

One of the key challenges when working with Marketing is tracking the effectiveness of campaigns and initiatives. To address this, it’s important to implement tracking pixels and maintain tracking codes to ensure that data is being captured accurately. Landing pages are also a critical component of digital marketing campaigns, and it’s essential to ensure that they are optimized for conversion and user experience.

Performance optimization is another area where Engineering and Marketing teams can collaborate to drive success. Slow loading times and poor performance can lead to a poor user experience and reduced engagement. By working together to optimize web pages and mobile app screens, Engineering and Marketing teams can improve user engagement and drive conversions.

To help Marketing teams utilize their ad spend effectively, Engineering teams can assist with customer acquisition and onboarding. This might involve developing features that help users get started with a product or service or integrating with third-party tools to streamline the onboarding process.

Finally, CRM teams can benefit from collaboration between Engineering and Marketing teams. By providing data and insights on user behavior, Engineering teams can help CRM teams develop more effective campaigns and initiatives.

Marketing departments are typically the biggest spenders in a company. Unfortunately, sometimes these resources are wasted due to very simple reasons. For example, the customer journey may not be set up correctly because the tracking pixel is not installed properly. People can click on an ad, but bounce before the landing page loads due to poor performance. Certain customers using specific browsers may leave a form without filling it out due to a simple JavaScript error in a form where leads need to be collected.

It’s important to remember that significant amounts of money are spent to attract traffic to these pages, and even small improvements can have positive results for the company.

Collaboration between Sales and Engineering

Collaborating with sales teams is a critical component of any CTO’s role. Sales teams provide valuable real-world feedback on your technology and are responsible for bringing in revenue to the company. Regular meetings to discuss customer needs, pain points, and success stories can help you make more informed decisions about your technology roadmap. For instance, if sales teams report that customers are struggling with a particular feature, you can prioritize improvements to address their concerns and enhance the user experience.

As usual, working together to develop a shared vision for the business and aligning on key performance indicators (KPIs) can help ensure that the Engineering and Sales teams are working towards the same objectives.

Many sales teams use CRM as a tool. They take notes of all their interactions with customers and it serves as a single point of reference when needed. If the CRM is developed in-house (except for exceptional cases, I do not recommend it), the roadmap and technology of this product are critical to the company’s revenue.

Monitoring and building reporting capabilities of the field personnel is also an essential aspect of collaborating with Sales teams. By tracking the performance and effectiveness of salespeople in the field, you can help their managers identify areas for improvement and optimize the sales process.

Prioritizing key customers and developing strategies to support them is also essential for collaborating with Sales teams. Key account management involves identifying and nurturing relationships with high-value customers to drive revenue and ensure long-term success. As the CTO, you should be aware of the key customers, how they are using your products and services, and their unique requirements and use cases. This information can be achieved through consulting the Sales personnel or even visiting the key customers personally.

Not all sales are done face-to-face, and it’s important to understand how to help Sales teams with digital sales. This might involve developing features that help users get started with a product or service or integrating with third-party tools to streamline the onboarding process. As a CTO, you can play a valuable role in important sales pitches and meetings by providing technical expertise and insights into the product. By working together with Sales teams, you can drive innovation, improve the user experience, and ensure the ongoing success of your technology strategy.

Collaboration between Finance and Engineering

Newly appointed CTOs quickly come to understand the significant role that budgeting and financial discussions play in their position. The reality of technical careers often involves a gradual shift away from day-to-day technical responsibilities as we climb the corporate ladder, and towards expanded interactions with other disciplines. Interestingly, many of us have previously undervalued the work of these other departments, and at times even viewed our own contributions as more important. The moment of reckoning arrives when we step into a CTO role and gain a true appreciation for the responsibilities and contributions of our colleagues from other disciplines.

One such department is finance. As CTOs, we are responsible for leveraging the resources at our disposal to create the best possible products and services. The company’s founders (unless we are among them) and the board of directors place their trust in us to make wise investments, whether through internal initiatives or external purchases.

Doesn’t this situation seem more like a finance problem than an engineering one? Indeed, it does. We are tackling a financial optimization problem.

The first step to becoming a successful CTO is communication. To effectively communicate with finance professionals, it is essential to have a basic understanding of their jargon. If you lack this knowledge, there are many options available to you, such as taking an accelerated course, pursuing an online MBA, or reading a book on the subject, such as “The Personal MBA” by Josh Kaufman.

If you aspire to continue progressing in your career as a CTO, you will need to discuss finances as much as technical topics. Budgets, expenses, and costs are now an indispensable part of your professional life.

Here are the most essential finance topics that a CTO must know:

• Capital Expenditures (CAPEX): Funds used to acquire, improve, and maintain long-term assets, such as buildings, equipment, and software.
• Operating Expenses (OPEX): Funds used to maintain the day-to-day operations of the company, such as salaries, utilities, and rent.
• Earnings Before Interest, Taxes, Depreciation, and Amortization (EBITDA): A measure of a company’s profitability that takes into account its revenue, expenses, and capital expenditures. It is often used as a proxy for cash flow.
• Net Income: The revenue left over after all expenses, including taxes, have been paid.
• Return on Investment (ROI): A measure of the profitability of an investment. It is calculated by dividing the return on the investment by the cost of the investment.
• Cash Flow: The amount of cash that flows in and out of a company over a period of time. It is a measure of a company’s liquidity and can be used to assess its ability to meet its financial obligations.
• Income Statement: A financial statement that shows a company’s revenue, expenses, and net income over a period of time.
• Profit and Loss (P&L) Statement: A financial statement that shows a company’s revenue, expenses, and net income over a period of time.
• Cost Accounting: The process of recording, analyzing, and allocating costs associated with producing a product or service. It helps businesses identify areas for improvement and cost savings.
• Financial Analysis: Analysis that involves analyzing financial data to evaluate a company’s performance, inform decision-making, and make projections.

When working with the Finance department, it’s essential to establish a clear communication channel and work collaboratively to identify areas where cost savings can be achieved. Reviewing the company’s contracts is one way to do this. You may be able to negotiate better rates on software licenses or identify opportunities to consolidate vendors.

As a CTO, you should be proactive in identifying areas where expenses can be reduced. Conducting a thorough review of your technology infrastructure is one way to do this. You may be able to consolidate servers or move to a cloud-based infrastructure to reduce hardware costs. Implementing automation tools can help streamline your operations and reduce labor costs.

Remember that cost-cutting should not come at the expense of innovation or quality. Your focus should be on achieving a balance between cost savings and delivering high-quality products that meet customer needs. By working collaboratively with the Finance department and other departments, you can achieve this balance and drive innovation while maintaining financial stability.

Collaboration between Procurement and Engineering

Procurement is one of the most important departments that a CTO should work with. Procurement teams are responsible for sourcing materials, products, and services necessary for the company’s operations.

One important aspect of collaboration between Engineering and Procurement is the process of selecting vendors. The Engineering team may have unique technical requirements that Procurement teams need to consider when selecting vendors. CTOs can contribute to their success by providing guidance on technical requirements, budget constraints, and industry trends.

Another area where CTOs can contribute to the success of Engineering and Procurement teams is by helping to streamline the procurement process. This might involve developing a standardized procurement process, implementing procurement software, or creating an internal procurement team to handle purchasing and vendor management.

Implementing a standardized procurement process can help ensure that all purchases are made in compliance with company policies and procedures. This can help prevent fraud, waste, and abuse and ensure that the company is getting the best value for its money.

Procurement software can help automate the procurement process, making it faster, more efficient, and less prone to errors. Procurement software can also help Procurement teams manage vendors, track orders, and monitor spending.

Creating an internal procurement team can help centralize purchasing and vendor management activities, making them more efficient and effective. Internal procurement teams can also work closely with Engineering teams to ensure that all technical requirements are met and that vendors are delivering high-quality products and services.

CTOs can also help Engineering and Procurement teams work together more effectively by promoting a culture of collaboration and open communication. CTOs can encourage Engineering teams to provide Procurement teams with feedback on vendors and products, and Procurement teams to provide Engineering teams with feedback on procurement processes and policies.

Finally, CTOs can help Engineering and Procurement teams work together more effectively by providing training and resources. This might involve providing technical training to Procurement teams, or providing Procurement teams with access to technical resources such as documentation, user manuals, and technical support.

By working together effectively, Engineering and Procurement teams can ensure that the company is getting the best value for its money and that technical requirements are being met. CTOs can contribute to their success by providing guidance, streamlining processes, promoting collaboration, and providing training and resources.

Collaboration between Human Resources and Engineering

As a CTO, it’s essential to forge a close partnership with HR to ensure that the engineering team possesses the necessary skills and resources to deliver high-quality products.

One example of how CTOs can help build a tech brand is by collaborating with HR to cultivate a positive and engaging employer brand. This entails developing a clear, compelling message that emphasizes the company’s values, culture, and mission. CTOs can also work with HR to create recruitment materials that showcase the company’s strengths and attract top-tier talent.

Another approach for CTOs to optimize the hiring pipeline is by collaborating with HR to implement an Applicant Tracking System (ATS). Whether you choose to build an ATS in-house (I wouldn’t recommend it) or purchase one, ATS platforms like Workday, Greenhouse, and Lever can streamline the recruitment process and enhance efficiency.

In many organizations, HR teams are organized into three main groups: Talent Acquisition, HR Operations, and People Partners. Each group has a distinct set of responsibilities, and CTOs can help HR teams leverage artificial intelligence (AI) to improve their performance. For instance, AI can be employed to automate resume screening, pinpoint top candidates, and provide personalized recommendations for employee training and development.

Employee self-service portals offer another area where everyone uses in their daily lives. These portals, such as Workday and its competitors, enable employees to access their personal information, benefits, and payroll data online. Implementing an employee self-service portal reduces administrative tasks and improves employee satisfaction.

Additionally, CTOs can help HR teams appreciate the significance of data and reporting. CTOs can also assist HR teams in developing custom reports and dashboards that deliver real-time insights into HR operations.

It’s crucial to remember that HR is not solely about hiring and firing employees. HR can contribute soft power, such as devising employee engagement initiatives, providing training and development opportunities, and nurturing a positive and inclusive workplace culture.

Handling terminations is one of the most challenging aspects of HR’s job. As a CTO, you can support HR teams by offering guidance on how to approach these situations with sensitivity and professionalism. This might involve creating clear policies and procedures for terminations, providing training on communicating with employees during the termination process, and supplying support and counseling services to affected employees.

In conclusion, CTOs play an invaluable role in collaborating with HR teams to build a strong and effective technology team. By fostering a positive employer brand, implementing efficient recruitment and hiring processes, leveraging AI and data, and assisting HR teams in their day-to-day operations, CTOs can help ensure that the company has the talent and resources necessary to achieve its objectives.