The feedback was fair. That was the annoying part.
My review came back and said, in the polite way these things are always said, that I was strong on delivery and thin on cross-org influence. If I wanted the next level, I needed to show impact beyond my own team. I read it, I agreed with it, and then I sat there with no idea what to do on Monday.
Knowing your gap doesn't close your gap.
That's the part nobody tells you. The rubric is good at naming what's missing and silent on where to find it. “Drives cross-org influence” is not a ticket in my queue. It's not a project my manager hands me. And here's where I want to be honest about my own role: I treated it like something that would eventually come to me. I finished my work, I did it well, and I waited to be invited into the bigger thing.
Nobody was going to invite me. That's not how influence works, and some part of me knew it.
I wasn't losing this work to luckier people. I was losing it to people who were actually looking for it.
Because when the cross-team initiative got announced in a thread I wasn't reading, and someone two teams over put their hand up before I'd even seen it, the honest read isn't that they got lucky. It's that they were hunting and I wasn't. They treated “find the work that grows me” as part of the job. I treated it as something that would happen to me if I shipped enough. So I shipped, and the gap the rubric named stayed exactly where it was, because shipping was never going to close it.
And the gap compounds when you leave it alone. You're thin on influence, so you don't go find the influence work, so next cycle you're still thin on influence. The rubric points at the hole, and the hole gets deeper while you tell yourself you're being productive.
I assumed I was just bad at this until a friend up for staff told me how she does it. A few times a week she skims the handful of channels where this stuff gets announced. Not for her own work, for openings. A project that goes out without a clear owner, a team posting about a painful migration: she keeps a short list, and when something lines up with a gap she's trying to close, she reaches out that day instead of a week later.
That's not luck and it's not even ambition. It's a chore, and she'd taken responsibility for doing it while I'd quietly outsourced mine to hope.
The information was never hidden from me. The initiative that needed an owner was sitting in a Slack message I could have read. The stalled RFC was in a Drive I had access to. The work that would have closed my gap was scattered across the exact tools I already had open. I wasn't shut out. I just wasn't doing the daily, boring work of looking. I told myself I didn't have time, which was true and also not an excuse.
So we built that into Perfolio.
You tell it the goal, whether that's cross-team influence, visibility, mentorship, or technical depth, and the Opportunity Radar searches your connected sources for work you could actually claim against it. It's deliberately not a magic AI that dreams up opportunities. It runs a deterministic pass first, matching real signals in real messages and tickets, suppresses anything you've already done, and only then lets the model rank and explain what survived. It never invents an initiative that didn't come from a real source. When you dismiss one, it remembers why, and gets sharper about your gaps.
It doesn't do the influencing for you, and it shouldn't. You still have to raise your hand and do the hard, uncomfortable work of leading something outside your lane. All it removes is the excuse I'd been hiding behind: that I didn't have time to go looking. Now the looking is done. Whether I act on it is on me, which is exactly where it belonged the whole time.
A gap you can name is not a gap you can close. The rubric told me what was missing. It was never going to go find it for me. And for a long time, neither was I.