
Imposter Syndrome Is a Feature, Not a Bug — Here’s What to Do
Author: Waqar B. Hashim is a veteran product development leader with over 30 years of experience bringing complex hardware-software integrated products to market, generating more than $5 billion in sales worldwide.
Ever feel like your job isn’t real? You’re not broken. The system is.
To be perfectly clear, product management is one of the most misunderstood roles in tech. You’re not quite a project manager. You’re not really the designer. You don’t code, but you’re supposed to lead engineers. You don’t own revenue, but you’re asked to drive growth.
No wonder so many PMs quietly wonder: "What exactly do I do here?"
If you’ve ever felt like an imposter in your role, you’re not alone. And more importantly, you’re not wrong to feel that way. The problem isn’t you. It’s the ambiguity of the role and the lack of shared understanding across teams.
I have come across this phenomenon quite frequently when talking to PMs, particularly during one on one conversations. Of course it depends on the size of the organization, style of management and many other factors but lets's explore the fundamentals of why PMs often wrestle with role confusion and lack of recognition, and how you can reclaim clarity, confidence, and impact—without waiting for someone else to define it for you.
Why the Product Manager Role Is So Confusing
There’s no universal job description for PMs. Some are deeply technical. Others are customer-facing. Some drive vision and roadmap. Others write stories and QA features.
The result?
-
One company’s PM is another’s product owner
-
Expectations change from team to team
-
Success metrics are often fuzzy or inherited
Worse, many organizations lump several jobs into the PM title:
-
Strategy and vision
-
Project management
-
User research
-
Backlog grooming
-
Stakeholder wrangling
-
GTM alignment
-
Feature validation
You’re doing a lot. But it doesn’t always feel like it adds up.
Imposter Syndrome: The Default Setting
When your role is vaguely defined and inconsistently rewarded, imposter syndrome becomes the baseline.
Here’s what that sounds like:
-
"Am I doing enough?"
-
"Why does this still feel messy?"
-
"Do people even know what I do?"
-
"What if I’m the only one who doesn’t get it?"
It doesn’t help that PMs often don’t "produce" anything tangible. Engineers ship code. Designers create mockups. PMs connect dots—and that work is hard to point to.
That’s not a bug. That’s the job.
Your job is to:
-
Make sense of ambiguity
-
Create shared understanding
-
Set direction when there isn’t one
-
Prevent problems before they happen
You’re not broken. You’re doing invisible work.
You’re Not a Project Manager or a Product Owner (But You May Play One)
Let’s clarify the distinctions, because this is where many PMs get pulled in too many directions.
Project Manager
Focuses on execution, timelines, dependencies, and delivery.
-
Owns "when and how"
-
Makes sure things ship on time
-
Optimizes for efficiency
Product Owner
(Usually within Agile/Scrum)
-
Owns the backlog
-
Writes user stories
-
Works closely with dev teams to prioritize sprint work
Product Manager
Focuses on vision, strategy, and user value.
-
Owns the "why"
-
Defines problems to solve
-
Balances user needs and business goals
In reality, many PMs are expected to be all three. The key is knowing what mode you’re in—and communicating that clearly.
Redefine Your Role Before Others Do
If you wait for your org to define your role, you may end up stuck in execution mode forever.
Instead, take time to define your own impact narrative. Whether you have moved into this role from within the company or you were hired as a new PM employee in an organization the ideal time to do this is during a 3 month or 6 month review once you understand what is actually happening on the job. Don't wait till the end of the first year!
Ask Yourself:
-
What parts of my job energize me the most?
-
Where do I create the most value for the team?
-
What do I want to be known for?
-
What metrics or feedback show that I’m making a difference?
This isn’t fluff. It’s how you begin shaping how others see your contributions.
Then Share It:
-
In 1:1s with your manager
-
During performance reviews
-
In sprint recaps or team updates
-
In onboarding docs for new teammates
When you frame your work around outcomes, not just outputs, your role starts to gain clarity.
Write a Monthly "Impact Brief"
This is a game-changer, especially when imposter syndrome is whispering in your ear.
Once a month, write a short internal memo for yourself (and optionally your team):
Sections to Include:
-
Key outcomes delivered this month (e.g., features shipped, bugs reduced, user behavior changed)
-
Cross-functional wins (e.g., smoother handoffs, faster alignment, stakeholder clarity)
-
Customer insights surfaced (e.g., discovery findings, support patterns, feedback themes)
-
Risks flagged or decisions unblocked
Keep it to one page. Do it for yourself, not just for execs.
Over time, this becomes a record of your impact. A confidence booster. A promo packet. A reminder that yes, you do drive real results.
Normalize the Confusion
You are not the only PM who feels this way.
You’re not the only one who feels unsure about your place. You’re not the only one whose calendar is full of meetings but who wonders if you got anything "done."
Here’s what to do:
-
Talk to other PMs. You’ll be shocked how similar your struggles are.
-
Ask your manager for role clarity and autonomy. They’re not mutually exclusive.
-
Push for team-wide discussions about what success looks like for PMs
-
Support junior PMs by naming these patterns early so they don’t carry the weight alone
The more we talk about this, the more we make room for realistic expectations—and healthy growth.
A Real Example: Defining the Role Out Loud
Jared joined a growth-stage startup as the second PM. In his first month, he found himself writing QA test cases, reviewing wireframes, attending investor pitch meetings, and running sprint planning.
He felt scattered and unsure if he was succeeding.
Instead of waiting for feedback, he created a one-page summary of his role, responsibilities, and goals. He shared it with his manager and cross-functional leads.
The result? Clarity. Respect. Better delegation.
He wasn’t trying to brag. He was building a shared understanding of what he owned—and what he didn’t.
Now, he updates that document quarterly and uses it to check alignment with leadership.
What Makes a PM Great (Even If It’s Invisible)
Great PMs do a lot that never shows up in Jira.
-
You asked the hard question no one else did
-
You saw a risk no one wanted to name
-
You got two directors to finally align on priorities
-
You killed a feature that would’ve wasted a sprint
-
You made a decision that helped your team sleep better
These things matter. Even if they don’t fit neatly into OKRs.
Learn to recognize them. And teach others to recognize them too.
Actionable Tip: Start Your Impact Brief Today
Before this month ends, block 30 minutes.
Open a doc titled: [Your Name] - Monthly Impact Brief
Fill in 3-5 bullet points for:
-
What changed because of your work?
-
Who was helped?
-
What insights did you surface?
No fluff. Just facts. It’s for you first.
Then decide if you want to share it with your manager, your team, or your future self in a job interview.
You’ll be surprised how good it feels to see it all written down.
Final Thoughts: You Belong Here
If you feel like an imposter, congratulations. That means you’re thinking critically. You care. You’re self-aware.
But don’t let role confusion erase your confidence.
Define your role. Track your impact. Talk about the work that matters.
And when someone asks, "What do you actually do?"
Smile. And say:
"I connect people, ideas, and insights to build the right things. I help teams make better decisions. I make the invisible work, visible."
Because that’s not fluff. That’s leadership.
So tell me... what’s your real title, and what do you actually do?
Let’s rewrite the job description together.
Smartware Advisors is your partner in product success. Book a strategy call to find out how.
#ProductManagement #PMLeadership #ImposterSyndrome #ImpactDriven #CareerGrowth #TechCareers #DefineSuccess #RoleClarity
Leave a comment
This site is protected by hCaptcha and the hCaptcha Privacy Policy and Terms of Service apply.