Key takeaways
- An earlier version of this post published counts from one quarter of development plans. They cannot be reproduced from a documented cohort that excludes test and demo accounts, so they have been removed.
- Commercial business acumen is a theme we hear and see often in development conversations. We have not measured how often, and the number of real plans involved is small.
- A small count of plan objectives cannot tell you which gap is most common, or whether one stands out from the rest. Treat everything below as a hypothesis to test, not a finding.
- One plausible driver: companies are asking PMs to defend product decisions in P&L terms, not just roadmap terms.
- A development plan that names a competency without naming the specific decision it would change is not a plan, it's a label.
This post originally reported counts of which competency dimensions appeared most in one quarter of Product Assessment development plans, and concluded that commercial business acumen stood far ahead of the rest. We have removed those counts. The cohort was never documented, it was small, and we cannot show that it excluded test and demo accounts, which this site's own metrics treat as not real activity. A handful of plan objectives cannot support a claim that one gap is larger than another. What follows is the reasoning that the original numbers were used to illustrate, kept as hypotheses.
What we can and cannot say about commercial acumen
We can say commercial and business acumen is one of the 16 dimensions every full assessment scores, and that it is a common subject of development conversations. We cannot say it is the most common gap, how much more common it is than any other, or that any difference is more than chance. Counting objectives across a few plans produces numbers like 4 and 2, and differences that small say nothing reliable. Publishing real frequencies would need a documented cohort with test accounts excluded, one count per participant, and a statement of uncertainty. We do not have that yet.
Why commercial acumen, specifically
I've sat on both sides of this. At Arrivia, running a $200M P&L, the PMs who struggled weren't the ones who couldn't write a good spec. They were the ones who couldn't tell me what a feature would do to contribution margin, or why a "yes" from the customer didn't automatically mean "yes" from the business. At Caesars Sportsbook, the same pattern showed up in reverse: the PMs who got pulled into strategy conversations early were the ones who could walk into a room and talk about hold percentage, promo cost, and LTV without an analyst translating for them.
Most PMs didn't come up through finance. They came up through design, engineering-adjacent roles, or growth, where the fluency that gets rewarded is user insight and shipping velocity. Commercial acumen was rarely tested in interviews and rarely coached on the job, because for a long time it wasn't the bottleneck. That's changed. Companies are asking PMs to own outcomes, not outputs, and outcomes get measured in revenue, margin, and retention. The gap was always there. It's just now the thing standing between a PM and their next level, which may be why it comes up so often in development conversations. For a fuller breakdown of what this dimension actually covers, see commercial and business acumen.
What the second tier tells you
Execution and delivery, prioritization judgment, and commercial acumen are plausibly related. A PM who can't defend a tradeoff in commercial terms may struggle to prioritize with conviction too, because prioritization is ultimately a commercial argument: this over that, because of this expected return. When PMs get flagged on prioritization judgment, the root cause is frequently not a framework problem, it's that they don't have the commercial fluency to rank options with confidence. That is one reason these dimensions might move together, and a reason to check for a shared cause, not a measured result.
Execution and delivery is usually treated as table stakes for a PM past the associate level, so seeing it in a development plan at all is worth a second look. Possible reasons include a higher delivery bar or tighter expectations as teams make every roadmap slot count. We have no data here to say which, if any.
Why the rest are quiet
A dimension that rarely shows up in a development plan is not "solved." It may simply not be the constraint right now. A PM's development plan reflects the dimension holding them back most relative to their next milestone, not every dimension where they could improve. If commercial acumen is a person's binding constraint, the assessment surfaces that first and the others don't rise to the top of the plan, even if they're not perfect either.
This is also a reminder that competencies aren't independent. Weak stakeholder management and influence often masks itself as a commercial acumen problem, because a PM who can't frame a decision in the language their VP or CFO cares about looks like they lack business judgment, when the real gap is translation, not understanding. Worth checking which one you actually have before you build a plan around the wrong label. The full PM competency framework maps how these 16 dimensions interact, which is useful if you're trying to figure out root cause instead of symptom.
What to do with this if it's your gap too
A development plan that just says "improve commercial acumen" is a label, not a plan. It doesn't change behavior because it doesn't point at a decision. The PMs I've seen close this gap fastest do three specific things:
First, they attach a number to every roadmap item they own, even a rough one: expected revenue impact, cost to build and run, margin effect. Not because the number is precise, but because building the habit of quantifying forces the reasoning. Second, they sit in on the finance or commercial reviews they used to skip, specifically to learn the vocabulary and the questions that get asked before a decision gets approved. Third, they stop treating prioritization calls as user-value arguments only and start defending them in the same terms their leadership uses to evaluate the business, which is exactly the overlap that shows up in the product strategy dimension too.
If you're not sure whether commercial acumen is actually your binding constraint or just the trendy one to name, that's worth verifying before you spend a quarter on it. A full assessment will tell you which of the 16 dimensions is actually holding your next review back, rather than which one is easiest to name in a self-assessment.
Common questions
- Why might commercial business acumen come up so often as a PM development area?
- A likely reason, though we have not measured it, is that more PMs are being asked to own or influence P&L outcomes, not just ship features. Reviewers increasingly ask PMs to defend a roadmap decision in terms of margin, CAC, LTV, or unit economics rather than user value alone. Most PMs came up through a design or engineering-adjacent path and never built fluency in reading a P&L, pricing a feature, or modeling a business case, so it's the gap that shows up first when the bar moves.
- Does a competency appearing often in development plans mean PMs are getting worse at it?
- Not necessarily. One explanation is that the expectation moved faster than the skill did. Commercial acumen wasn't heavily weighted in PM hiring or promotion five years ago, so most PMs never built it deliberately. That would mean frequency reflects a shift in what's being measured, not a decline in what PMs know. It is an explanation worth testing, not something this post demonstrates.
- How should a PM prioritize if their development plan lists three or four competencies?
- Pick the one with the shortest path to a concrete outcome you can point to in a performance review, usually the one closest to a decision you already make repeatedly. Commercial acumen and prioritization judgment often overlap: if you can't defend a prioritization call in revenue or margin terms, closing that gap improves both dimensions at once.
Next step
See which level your evidence actually supports
An adaptive interview about your real decisions. It evaluates all 16 PM competency dimensions and maps your evidence to the level it actually supports.