Activity
Mon
Wed
Fri
Sun
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
What is this?
Less
More

Memberships

Product Management Circle

86 members • Free

3 contributions to Product Management Circle
Leadership lessons learned
🪞 As I reflect on the past year, this story comes to mind. Not as a failure but as a step toward increasing strategic maturity. ☸️ Last year I stepped into a temporary program role at a large tech company. On paper, I was asked to “take the wheel” for a critical product initiative. In reality, I inherited ownership with zero authority. When I asked the product team when they last spoke with customers, the answer was, “We talk to UX Research weekly.” 🙅 Translation: they weren’t hearing from real users, and I wasn’t supposed to question it. I pushed the issue to a senior product leader. They agreed the gap was real—but the organization wasn’t ready to act. My takeaway: boundaries matter more than titles. Empowerment beats job description. What are some strategic leadership lessons you have learned?
1 like • Dec '25
Oof this feels relatable! I feel like I'm definitely trying to learn how to cultivate receptivity in order to more effectively communicate and ultimately move forward with strategy.
How to Influence Stakeholders
The shift from order-taker to influencer I see most senior PMs miss is this: 🤔 They think influence means convincing. It actually means alignment through their language, not yours. 🏎️ Here's a quick pattern I encourage: The 3-Question Stakeholder Map Before any strategic conversation, answer these for each key stakeholder: 1. What do they optimize for? (their success metric, not yours) 📈 2. What evidence convinces them? (data, user stories, peer validation, etc.) 🔎 3. What's their skepticism rooted in? (risk, resource constraints, past failures) 🤨 Quick example: 🤨 Skeptical Engineer archetype: - Optimizes for: Technical elegance + avoiding rework - Convinced by: Technical approach that reduces future debt - Skepticism: "PM doesn't understand the technical complexity" Your reframe: Instead of "We need to ship feature X" → "I'm thinking we tackle X now because it sets up the architecture for Y and Z later. Want to sketch out an approach that doesn't create debt?" 😃 You just turned a skeptic into a collaborator. 🪄 The trick isn't having all the answers. It's knowing how to surface the right questions that get each archetype leaning in. Curious if this lands? Happy to riff more on the specific stakeholders you're navigating.
1 like • Oct '25
Just used this insight as the springboard for an email I sent a client--fingers crossed!
Introduction
Hello folks! I'm a project manager for a U.S.-based software development agency that produces a variety of digital products. I'm looking to learn how to better guide our clients with effective technical strategy.
1-3 of 3
Malinda Gosvig
1
1point to level up
@malinda-gosvig-6298
Project manager at Stratosphere Digital

Active 2d ago
Joined Oct 24, 2025