I was chatting with an AI model the other day, trying to explain a point about product architecture. To make my argument clearer, I pasted in the framework for a business scenario synthesis platform I’d designed at work. The AI’s response included a throwaway line that stopped me cold:
“Based on industry leveling, this work is approximately P7.”
P7 — in the Alibaba system, that’s a senior product expert. A high-tier frontline role. And I stood there, genuinely stunned.
Not because I believed it. I know I’m not a real P7 — not in depth of capability, not in scope of influence. What hit me was the wave of self-doubt that followed: If this work actually carries that much value, why do I never feel it inside my own company?
That single sentence from a machine became a mirror. Not a label, but a question: What have I actually done? What was genuinely valuable? And have I, in the daily grind of task after task, forgotten who I am?
The Senior Who’s Still Called Junior
I’ve been at my company for years. I’m one of the “old hands.” Whatever task lands on my desk, I bring everything I have — experience, lateral thinking, execution. The result? I’m still labeled “mid-level product manager.” Still the one who gets underestimated.
The reason is simple: in their eyes, my abilities never left the starting line of my first day. Every bit of growth, every complex project I quietly shouldered — as if none of it happened.
Here’s the part that would be funny if it weren’t my life: the company has been shrinking, laying people off, cutting teams. And yet it still depends on the very product line they dismiss every single day to keep the lights on. The core business is right there — they badmouth it as “lacking innovation” while their revenue stream depends on it surviving.
I built a B2B SaaS product over six years. Took it from zero customers to nearly a hundred. That’s not a unicorn story. It’s something more durable: the most stable cash flow source the company has. This product doesn’t need flashy new technology dropped on it. It needs steady, phased investment — maintenance, iteration, continuous response to what real customers actually need.
But in the eyes of leadership, maintenance is mediocrity. Only innovation gets the halo.
What the AI Mirror Revealed
I kept turning the question over: if this work is genuinely P7-worthy, why does my company never recognize it?
So I started digging through my own work records — the past six months, the past year. Details I’d nearly forgotten surfaced one by one. A complex cross-system integration plan. The time I abstracted scattered scenarios into a shared platform capability. The client meeting where I held the line during a brutal requirements review.
And I realized something that changed how I see my own career: It wasn’t that I hadn’t done valuable things. It was that I never stopped to look back at them.
Every day, I was pushed forward by the next task on the list. One requirement ends, the next gets shoved in. No breathing room to ask myself: “Hey, that went well. What does it say about my capability? What should I keep doing more of?”
The relentless rhythm ground every highlight into flat, forgettable routine. I felt busy. Others couldn’t see it. And worse — even I forgot.
Why You Need to Stop Every Two Months
I made myself a rule: every one to two months, block out one to two hours. Stop. Look back. Not for a weekly report. Not to perform for a manager. To see what bricks I’ve actually laid.
Three reasons this matters:
First, product work is inherently fragmented. Writing specs, aligning on requirements, firefighting, coordinating — a dozen things a day, each one “urgent.” Rarely do you get the full satisfaction of “I completed something.” Without deliberate review, your sense of achievement erodes to nothing. When you try to recall what you did, almost nothing surfaces.
Second, your manager’s perception freezes. The longer you stay somewhere, the more they evaluate you through the lens of who you were on day one. This isn’t malice — it’s cognitive inertia. The only way to break it is with structured, visible records of what you’ve actually delivered. Not to prove anything to anyone — but so that when the moment comes, you have facts, not feelings.
Third, there’s a “results forgetting effect.” That gnarly problem you spent two weeks solving three months ago? By year-end, you’ll barely remember it happened. Unrecorded achievements dissolve with time. And they’re exactly the foundation stones of your growth — the hardest evidence for any future promotion, job change, or performance review.
The Four-Quadrant Method (Simple Enough to Start Today)
You don’t need a fancy tool. A spreadsheet, a document — anything you’ll actually maintain. Split each review into four dimensions:
1. What I shipped — concrete deliverables. Name them specifically. Not “worked on the platform” but “designed the cross-system data sync architecture for the billing module.”
2. What I learned — the capability gains. Not skills you read about — skills you forged in real friction.
3. What I’d do differently — not self-flagellation. Iteration intelligence. The accumulated wisdom of things that didn’t go perfectly.
4. What’s next — where to deliberately push. Not a wish list. A direction.
Don’t chase perfection. Write three lines if that’s what you have. Three lines beat a blank page every time.
What You Build Will Protect You
These records pay off in ways you won’t expect.
When your manager says “you’re not senior enough yet,” you can respond with specifics: “Here’s what I’m actually carrying. Which piece do you think needs filling in?” That’s a conversation, not a confrontation.
When two review cycles show you’re spending most of your time on things with no articulable value, you can course-correct — decline, downgrade, renegotiate scope.
When you need to make the case for resources, you have ammunition. That SaaS product I maintained for six years supports 60% of company revenue. That’s not an emotional appeal. That’s a business case.
And for yourself, long-term: you stop being hostage to any single company’s rating system. You build your own coordinate system. You see where you actually stand in abstraction, execution, communication, legacy system governance. The “P7” from the AI was just a spark. The real shift is deciding to measure yourself by your own ruler.
The Company Won’t See You. So See Yourself.
My company’s leadership says we “lack innovation.” What they don’t say: in a shrinking company in a tough market, stability is more real, more urgent, more valuable than novelty.
Keeping a product line alive for six years. Growing it to a hundred customers. Sustaining delivery under resource constraints. That’s not “no innovation.” That’s a severely underestimated capability: the discipline of long-term maintenance, continuous delivery, and holding ground when everything around you is contracting.
Many companies talk innovation while their body runs on old products. That’s their cognitive problem — not your burden to carry.
I’m not against innovation. No product manager rejects new projects — everyone wants the halo. But when direction is right, you don’t abandon the foundation because something shiny appeared. A tree with rotting roots doesn’t grow new branches for long.
The environment won’t proactively see you. But you can do something about it.
Stopping to review is a small, controllable act — one that belongs entirely to you. It’s not self-deception. It’s anchoring facts in noise.
Start Today
The platform gave me a place to stand — business scenarios, customer needs, project opportunities. Without that soil, no capability grows fruit. I don’t deny the platform, even when it frustrates me.
But here’s the truth that took me years to learn: those bricks scattered on the ground — you have to pick them up yourself. The company won’t organize them for you. Your manager won’t remember them for you. The daily grind won’t pause for you.
The person who stops, looks back, and polishes each scattered achievement until it catches light — that person can only be you.
From today, open a review document. Fill it every two months. Don’t let it sit empty.
Six months from now, look back at it. You might just thank the version of yourself who was willing to stop.
FAQ
Q: Isn't this just self-congratulation? Documenting your own work doesn't change how your company sees you.
A: You're half right. The document alone won't change your manager's frozen perception overnight. But it changes two things immediately: it gives you factual ammunition for performance conversations ("Here's what I'm actually delivering" beats "I feel undervalued"), and it rebuilds your own confidence with evidence instead of emotion. The company may never see you clearly. But you'll stop confusing their blindness with your actual worth.
Q: What's the practical implication for someone who's too busy to add another task?
A: Two hours every two months. That's the entire commitment. If you can't find two hours in sixty days to prevent your achievements from evaporating, you're not too busy — you're being managed by your busyness. The four-quadrant method takes one document and three bullet points per section. The cost of not doing it is showing up to your next performance review or job interview with nothing but vague memories.
Q: Isn't the real problem that maintenance work is inherently less valuable than innovation?
A: No. The real problem is that companies worship novelty while surviving on stability. A product line that sustains 60% of revenue for six years isn't 'less valuable' — it's the thing keeping the lights on while the innovation team burns money. The career moat isn't building new things. It's the ability to consistently deliver under constraints that would make most people quit. That's not a lesser skill. It's a rarer one. The market just hasn't learned to price it correctly yet.