As a company grows, so does the way it operates. Most of this is natural and harmless. For example, career ladders are created and promotions are formalized. However, with more measurement comes more opportunity to create bad incentives. Enter the "Good PM in Disguise".

First, let's look at a few ways a "Good PM" might be measured:

1. launches on time
2. protects their roadmap
3. works through others

None of these are inherently bad. But there are nefarious side effects to each that can go unnoticed, or worse, used as feedback to guide someone towards a promotion. Let's review that list again and expose some of the side effects.

1. Launches on time

There are 2 ways to launch on time: cut scope, reduce quality. It is easy to cut scope. It is easy to reduce quality. It is hard to do both. A "Good PM in Disguise" will sacrifice cust exp so they have an example of launching on time in their promo packet.

2. Protects their roadmap

PMs are responsible for the roadmap — both the creation and iteration. This can go wrong in a few ways. The "Good PM in Disguise" ignores new info that invalidates a roadmap item or increases the priority of something else, to show "conviction".

3. Works through others

Product management is primarily an influencing role. But it must be done with a selfless mentality. A "Good PM in Disguise" will find every chance for other teams to do their work. You should only ask when it benefits both teams (or the customer).

Don't launch on time if it hurts the customer experience.

Don't protect your roadmap if new information invalidates it.

Don't ask other teams for help just because they can.

Don't be a "Good PM in Disguise".

Put the customer before yourself.