Back to resources

Effective Cross-Functional Collaboration Between Technical and Product Leaders

Product
Leadership
Collaboration
Ownership
Coaching / Training / Mentorship
Cross-Functional Collaboration

4 January, 2022

Manu Gurudatha
Manu Gurudatha

Senior Director, Software Engineering at PagerDuty

Manu Gurudatha, Senior Director, Software Engineering at PagerDuty, shares how he established a trust-based relationship between product and engineering, which led to many successful product deliveries.

Getting into Uncharted Territories

We had to pivot our product into a new area for growth and relevance in the market. In this case, our product owners did not precisely know what to build to enter the new product area, while keeping the existing flywheel spinning. Fortunately, I had a principal engineer on my team with strong business acumen and was very collaborative with the product owners. Although we had well-defined roles for various levels of product owners, engineers, engineering managers, etc., it was still a grey area on how a principal engineer and product leadership would collaborate successfully. We needed to create that template.

Define a repeatable M.O.

I worked with the principal engineer and the product leadership to first collectively define “what needs to be built”, if we did not have time or capacity constraints. Since neither of us knew what the full scope of the new initiative was, the principal engineer blocked off their time for a couple of days and got to researching and defining the problem space.

This research and dedication gave the product owners an in-depth knowledge and understanding of full scope, how to approach it from an MVP perspective, helped them to overlay with a customer perspective, gave a few options to play with, and also have an idea on future iterations. New initiatives typically take months to get off the ground with huge amounts of uncertainty, and this engineer’s holistic research gave us a condensed view from both product and technical perspective in a short time. Knowing the risks, feasibility and viability ahead of time helped me to structure our teams accordingly, and options on how to roll out the product to our customers. This essentially became our modus operandi on how to productize and operationalize new ideas to market, which we successfully applied to several other new features thereafter.

Using this relationship between the engineer and the product team, I also created a Venn diagram to help my team understand the difference between a good and a great engineer. The diagram had three simple circles: Product, Technology, and Mentorship.

A good engineer is excellent with technical depth and breadth. When given a problem, they can develop a solid engineering solution, and mentor others on the team as well. The third dimension that makes them great engineers is their understanding of the product, business and operations side as well - essentially their ability to define the problem holistically. An engineer who can assess things from a technical, product and business perspective can influence a much wider surface area of the product, than just technology.

Define “the What” before “How”, “When” or “Who”

  • Always have your senior-most engineers pair effectively with Product leadership so that you can define the problem effectively before attempting to solve it. This way, the feasibility and viability of new initiatives are addressed upfront, risks are minimized, you have more options with trade-offs, and the probability of success increases.
  • Building a “We win together, we lose together” mindset across both Engineering and Product organizations will help set the stage for effective collaboration, and let the best ideas and approaches shine, irrespective of where they come from.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

The Growth Mindset in Modern Product Engineering

28 November

The impact you can have with a Growth Mindset' and the factors involved in driving orchestrated change.

Ownership
Vikash Chhaganlal

Vikash Chhaganlal

Head of Engineering at Xero

How to improve engagement and retention in remote engineering teams?

25 October

Mrunal Kapade, an Engineering leader, based in Silicon Valley, shares tips that helped reduce attrition in the remote engineering teams while leading multiple teams from startups to Fortune 500 companies.

Remote
Company Culture
Collaboration
Motivation
Team Processes
Mrunal Kapade

Mrunal Kapade

Director of Engineering at Inspire Energy

High Performance Team in Action

13 October

A high performance team refers to “ a group of goal-focused individuals with specialized expertise and complementary skills who collaborate, innovate and produce consistently superior results.”

Managing Expectations
Building A Team
Company Culture
Feedback
Coaching / Training / Mentorship
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

Developing an Early Career Program in Technology Organizations

12 October

Why companies should invest in early career programs ?

Building A Team
Hiring
Coaching / Training / Mentorship
Juniors
Career Path
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

Strategies for Hiring

12 October

Recruiting right people is the single most important decision for the company. Building a great platform, product and company is hard. Getting the right people into the company is twice hard.

Building A Team
Company Culture
Ownership
Hiring
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan