tl;dr
– Product managers need to adjust, adapt and go with the flow
– Little sens in beating against an immoveable obstacle
– Occasionally, the PM needs to be the rock
Years ago, I read a parable of the river and the rock, and how this analogy compared to product management. Unfortunately. I don’t recall the source of this parable, so I can’t give proper credit. However, it is a bit of knowledge I feel should be carried on.
Essentially, there are two forces at play when it comes to managing products: the river and the rock. The rock represents an unwavering stance or opinion that gets in the way of the river.
The river, in its attempt at reaching a goal, must confront the rock and determine the best course of action. It can go around, over, or beat at it, attempting to pummel it into sand. Oftentimes, possibly at all times, it employs more than one of these tactics.
If the rock is small, it’s easy enough to run right over the rock. This holds true for objections during product plans. Small obstacles can be ignored without much impact on velocity. (Keep in mind, however, that small impacts do eventually build up and shouldn’t be completely ignored.)
This happens possibly many times per day. Comparisons could include minor clarifying questions from engineers or outlandish feature requests from customers. The key is realizing they are small and should not be any more that a mere bump on the journey.
Larger rocks will require the river to divert in its path, possible substantially. As product managers, we must be able to navigate around obstacles in order to keep moving forward. Hopefully, we can see it well in advance, and there’s enough room to navigate around it. Any change in the resource triangle fits this bill.
In any case, the original analysis deemed product managers as the river. We cannot stand firm against the progress of our products. While there is an extreme requirement to find paths to success, we also need to understand when we need to be rocks, not as obstacles to success, but as firmly held beliefs in our products that cannot waver against forces counter to our endeavors.
This can also happen often. I run into this usually when I’m approached by a salesperson in the organization. (How many other PMs have a love/hate relationship with sales?) It seems their deals are always revenue game-changers that can only be won if we commit to a feature within a specific timeline regardless of impacts to the roadmap.
The default position in this scenario should be to hold your ground. It’s seldom the tradeoff is worth it.
Of course, with enough time, even the sturdiest rock can be worn into submission. Just look at the Grand Canyon.