I’ve spent most of my career in what used to be called “IT”, today called “Digital” and is rapidly becoming “AI.” With each epoch comes not only a name change but a step towards being just “business.” The more technology does for business the more the business is technology and the technology is the business.
Each change requires new skills, brings different ways of working and different roles. The Product Manager is one of those “new” roles that came with digital. However, as I pointed out a couple of weeks ago, not all product managers are the same. I keep looking for parallels, for other roles which can inform the Product Manager role.
One of those roles comes from the world of Lean, specifically Lean Product Development. I’ve been pondering the Chief Engineer role from Lean masters Toyota for years, to my eyes it looks a lot like a Product Manager.
So when Lean Institute e-mailed with “17 Principles for Chief Engineers” I was delighted. And then I thought can I apply these to the product manager role? So here goes…
Three attitudes
Before 17 principles there are 3 attitudes: Curiosity, Empathy and Imagination.
These line up perfectly with Product Management.
Product Managers need to be curious, both about what their users/customers and the technology that can be used to address those needs and wants. Naturally it helps to have empathy with those people who will use and benefit from the product. And it helps to have empathy with the engineers who will build the solution.
But it is not enough to feel the need and to understand the technology. One needs to be able to imagine how that technology can change those users work, processes and life. More imagination is better than less and part of the Product Manager role is to invent solutions and consider how the future might be. That all requires imagination.
So, when Naoto Kitagawa suggests Chief Engineers need to cultivate these three attitudes he could equally be speaking to Product Managers.
17 Principles
1. Car planning and development is a passion; constantly envision original products, day and night.
Take away the word car and this fits for product managers.
2. Acquire the organizational skills to accomplish ambitious goals.
5. Build a broad network of people who will help in times of need.
10. Skilfully utilize experts for knowledge you lack, but never neglect your own studies.
(Kitagawa’s points as overlap so I’m bundling them together.)
Snap. It is not enough to empathise with customers, envisage a new product with new technology or imagine a better way of working. Leaders need organizational skills to bring it about. Without organizing skills a Product Manager will struggle to get realise their product.
This doesn’t mean that Product Managers or Chief Engineers need to be experts at everything. There are others: user researchers, business analysts, project and delivery managers, designers, and more who can help. Product managing requires organizational skills beyond product definition or market analysis.
When I’m new in an organization this is more difficult, but as I get to know more people – network – and I know who I can call on things get easier.
3. Possess an insatiable intellectual curiosity that surpasses everyone else’s.
Certainly I feel I posses such curiosity, after all, why do I write so much? This blog, my books, my patterns. I have a burning curiosity to understand. But, do all product managers feel this way?
In truth probably not. But then, some product managers are better than others. Maybe one can be a Product Manager without curiosity, maybe curiosity is a trait of the better managers.
4. Master the ability to clearly express your thoughts and ideas.
In my experience Product Managers who struggle to express themselves struggle to realise their products. It is not enough to imagine a new product, or empathise with customers one needs to be able to communicate that. Whether in writing, presentation or in everyday conversations.
6. Consider yourself the personnel and administrative manager of your group.
14. Diligently nurture young talent and the next generation of Chief Engineers; correct them sternly but skilfully on occasion.
Yes! Although, when your organization has other personnel managers, and when team members have different reporting lines this can be more difficult. One has to respect other people managers and not step on their toes, but at the same time Product Managers need to inspire and enrol their teams. Showing concern for the people on a team (empathy) and assisting where you can, maybe speaking to the official reporting line, helps get the best out of people.
Nurturing talent, #14 follows directly from #6 and equally applies to Product Managers.
7. Check drawings with single-minded diligence and thoroughness.
Ummm. Maybe not here. Do I forensically inspect UML diagrams? Database schema? Or user journey stories? Perhaps not.
However, there is a diligence in asking “Why?” or “Who actually wants this?” “What benefit will this bring?”
8. Diligently and thoroughly cultivate the field of cost management to achieve cost targets.
I always tell Product Managers – and anyone else who will listen! – to get onto the benefit side of the equation. To often costs are the only thing considered in product development – especially true in corporate environments were benefits can seem hard away and claimed by others.
However, as much as a Product Manager may attempt to focus on benefits, costs are never far away. So yes, like Chief Engineers, Product Managers need to cultivate an appreciation of costs.
9. Don’t leave how to sell your products solely to sales; devise your own promotional and sales strategies.
15. Be the most powerful salesperson for new market development; actively venture into new markets.
These points obviously apply to Commercial Product Managers who must make sure their product sells. Even when supported by Product Marketing specialists product managers need to stay close to sales and marketing.
Corporate Product Managers don’t need to sell to external customers but might need to sell their product internally. Knowing how and internal product helps the corporation and the products or services that are sold is essential.
So, while points #11 and #15 might not apply directly the ethos is still true.
11. Lead by example—genchi genbutsu (go to the source to see the actual situation yourself).
12. Practice interactive development with users at the earliest stage; when in doubt, observe customers.
Yes, these points are what Product Managers sometimes call “voice of the customer.” Often it is about hearing first hand from customers but it might also be about going and observing customers, processes and sales first hand.
I sometimes worry that Product Managers who are supported by the likes of Business Analysts and User Researcher are sometimes at risk of not actually hearing, and observing, customers and users often enough. One can get cut off, especially in todays work-from-home world.
13. Consider development schedule delays the greatest shame.
I can’t speak for all Product Managers but I certainly feel shame when my product ship late. Right now it further me every time I see two really small pieces of work which prevented an OKR being completed in full last quarter.
As I’ve said before: shipping dates make a difference to value and benefit. And often the way to make schedule is to flex features or functionality. Therefore, even if Product Manager can hand off delivery to a Delivery Manager they need to know their schedule and act against delays.
16. Be grateful to everyone who supports you.
Yes, whether Product Manager, Chief Engineer or any other leadership role, being grateful to those who help will get the best out of the people you work with today and those you will work with tomorrow.
17. Cultivate the physical and mental stamina to fight 24 hours a day.
Certainly I feel this at the moment! Racing up and down the pool at 7am is how I get my energy for the day ahead.
Perhaps Product Management should not be like this but it often is. It sometimes feels that the Product Manager is the one person willing thing forward!
Match?
I’m not ready to argue that Chief Engineers and Product Managers are the same role, I still want to know more about the CE role. But the more I learn about the Chief Engineer the more commonality I see.
Mentally, my image of both is that these are the roles that will a product into being. These are the roles that give the product a voice when it cannot speak itself.
However, a caveat. When I step back and look at these 17 points I find myself asking: aren’t these things any leader should be doing?
I find myself saying Yes. For anyone in a leadership role these 17 points are worth adhering too. Since both Product Managers and Chief Engineers are leading teams and teaming product development it is natural that the two roles have a lot in common.