Skip to main content

Communication in cross-functional teams

Working in cross functional teams is the occupational hazard for product managers.

A typical product manager needs to work with 3 kinds of teams:
  • Engineering team - comprising of developers, testers and IT operations
  • Sales / Marketing team
  • Management team
The product manager needs to have different set of information - or rather information represented and expressed in different ways for the three different teams.

Engineering Team Focus:
  • Focus on what needs to be done.
  • Define clear milestones 
  • Clearly communicate focus of the product and end user gain
  • Help take decisions to architect the product
  • Detail the product road-map from the engineering side
Sales/Marketing Team Focus:
  • Focus on what the product positioning needs to be
  • Map the competitive landscape and find out how we are different from our competitors
  • Clearly communicate the overall marketing / sales goals - with respect to details like channels, goal for the period
  • Detail out the communication plan with the end users and involve in every engineering milestone
Management Team Focus:
  • Focus on what the product brings on the table to the organization
  • Clearly communicate what is the product road-map is and what help we need from the organization
  • Layout the risks / opportunities along with the financials
  • Ask for help in getting help from other functions
  • Get a champion from the management team for internal / external positioning.
While this is not exhaustive, It is a sanity list for a product manager - things that we should never miss.

Comments

Popular posts from this blog

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile:  http://djrusso.github.io More reading from his paper here:  https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision.  I liked the approach of principles for developing systems that are anti-fragile. It i...

Designing for Accessibility

The software world has starting being more inclusive. After serving only the geeks and the techies, a lot of the software that is produced in this world has started looking at how it can be mor euseful. One of the key constituencies of software usage is people with disability. The ADA (Americans with disability Act) has forced a lot of the software developers to look at this issue. The software world has also responded sensitively and with care making as much of the software usable by people with disability. One of the key components that we are looking at in this are people with visual impairment. Over a period of time, a lot of the software has made sure that the user experience is adjusted in such a way that is is intuitive. Google has been a front runner in this and a lot of others are also not left behind. Text The size and the font typology is very important. Choose those aspects with ADA in mind. Media like Images A lot of the media , including video and images ,...

The cost of delayed decisions in Enterprise

Large enterprises have started their IT journey in earnest. However, they are miles behind what is happening.  Some of them have been trying to learn faster by creating research programs or separate business unites to try out and learn a few exotic ideas that have not yet gained acceptance in the industry or enterprise. Enterprises have moved record collection and data to IT long back and were pioneers in that. However, since the advent of personal computers, they have been left behind. Internet and mobile have left them far behind. For example, Network security, big data, mobile apps. social applications are solved problems that the enterprise choose to ignore.