Every promotion conversation eventually uses this phrase. "You need to be operating at the next level consistently." And almost nobody explains what that means concretely, which is convenient for the company and maddening for you.
Here's how I've come to interpret it, as a senior PM who's been through four promo cycles:
Operating at the next level is not about quality, it's about scope.
At every level, there are roughly two dimensions: what problems you're solving, and how much help you need to solve them. Moving up means solving bigger problems with less direction. That's it. But the detail is in the specifics per level.
PM example (but this pattern applies across functions): Mid-level PM: owns a feature or small product area, gets direction from senior PM, escalates ambiguity upward Senior PM: owns a product area, defines the direction, resolves most ambiguity without escalating, some cross-team coordination Staff PM: sets product strategy across multiple areas, defines what senior PMs are working on, manages org-level tradeoffs
If you're a mid-level PM doing mostly feature work, doing it really well doesn't move you to senior. You need to be doing the senior work: setting direction, not receiving it.
The frustrating truth is that many ICs never get the chance to do the scope of work that would justify the promo because their manager doesn't delegate it. So "operating at the next level" partly requires political/relational work: finding the right projects, getting visible work assigned to you, or proposing something big enough that you create the scope yourself.
For your packet: don't frame your evidence as "I did X well." Frame it as "here is a moment where I operated above my level because I did X without being asked, at a scale that was unexpected for my current role."