Jeff Kramer

This weekend, I had my first clarity session as part of the ProductDive Product Manager Mentorship Program. It was introductory, but powerful in a different way. Before diving into frameworks or execution, we focused on something more foundational: Understanding where we are. Identifying pain points. Clarifying growth goals. Sometimes we are so busy building that we don’t pause to articulate what we actually need to improve. That session gave me space to reflect on: – The kind of Product Manager I am becoming – The gaps I want to close – And the direction I am intentionally growing toward I am grateful to be learning in a space that encourages self-awareness before strategy. And thankful to my mentor, Calista Ohama, PSPO II™, MBA, for guiding that first conversation so thoughtfully.   This is just the beginning, but clarity always comes before elevation. #ProductManagement #PMJourney #Growth

7

2 Comments

Ever felt like your teams are working hard, but the organization still isn’t moving forward together? I recently facilitated a workshop with the Agile3M community in Atlassian's Gdansk office, and one conversation hit me hard: We’re often so focused on doing the work that we forget to check if we’re working on the right things together. And we do something bottom-up, but how do we connect it with top-down initiatives and leadership support? We explored the idea of Systems Thinking and the System of Work. I call it a connected enterprise, where every department, every role, and every initiative supports a shared goal. Not just in words. In how we work and in how we think about the work. Systems Thinking helps us ask: “𝘞𝘩𝘢𝘵 𝘩𝘢𝘱𝘱𝘦𝘯𝘴 𝘵𝘰 𝘵𝘩𝘦 𝘸𝘩𝘰𝘭𝘦 𝘪𝘧 𝘐 𝘤𝘩𝘢𝘯𝘨𝘦 𝘵𝘩𝘪𝘴 𝘰𝘯𝘦 𝘱𝘢𝘳𝘵?” A System of Work ensures teams collaborate with shared practices, tools, and expectations. In the workshop, we explored three tools that help make this visible and actionable: 💡𝗩𝗮𝗹𝘂𝗲 𝗦𝘁𝗿𝗲𝗮𝗺 𝗠𝗮𝗽𝗽𝗶𝗻𝗴 – to see how value flows (or gets stuck) across the org. 💡𝗖𝘂𝗿𝗿𝗲𝗻𝘁 𝗥𝗲𝗮𝗹𝗶𝘁𝘆 𝗧𝗿𝗲𝗲 – to uncover root causes behind recurring problems. 💡𝟱𝗦 – to organize and standardize the way we work for consistency and focus. What stood out? Many organizations don’t connect the what (strategy, vision, goals) with the how (daily execution, collaboration, tools). That gap creates delays, frustration, and misalignment—especially in complex environments where speed and adaptability matter. When you connect them, though— -> Decisions improve. -> Teams become aligned. -> Change becomes sustainable. The biggest takeaway? You don’t scale a business by adding more tools or teams. You scale by designing a system that connects thinking with doing, people with purpose, and strategy with execution. How connected is your system at the moment? #systemsthinking #systemofwork #connectedenterprise #agilecoach #process #processoptimization #valuestreammap #theoryofcontraints #sustainablebusiness

14

2 Comments

As a PM, do you document all of your decisions? I may be biased coming from a technical writing background, but strong decision documentation has saved many a project in my experience. Here are 5 reasons to document your decisions (including the options, considerations, and final choice):

10

One thing product management has taught me: If people don’t understand what you’re building, it doesn’t matter how good it is. Clarity isn’t a “nice to have.” It’s the foundation of trust.

5

You Don’t Need More Jira Boards, You Need More Conversations You’re not stuck because the board is messy. You’re stuck because people aren’t talking. You can color-code every card, refine your backlog to perfection, track every velocity point with precision… …but if your team is avoiding conflict, if decisions are being made in side chats, if folks are burned out and no one’s asking why No amount of process will fix that. Stop trying to manage everything through tools. Start getting curious. Start getting human. Because most of what’s blocking your team isn’t technical. It’s emotional. It’s relational. It’s real life. And that can’t be automated.

12

5 Comments

💼 Servant Leadership: Elevating Both the Team and the Customer The longer I lead, the more I realize that true leadership—especially as a Scrum Master—is rooted in service, not control. Being a servant leader means showing up for your internal team with the same commitment and care that you bring to the customer. It means understanding that both groups rely on you to create clarity, remove obstacles, and build trust. And it also means navigating the uncomfortable moments—not just conflict, but the demands that come from customers who expect excellence and teams who are working hard to deliver it. I’ll be honest: I don’t always keep my calm with the customer. Sometimes the pressure, the urgency, or the assumptions become too much. And as a servant leader, I’ve learned that staying calm doesn’t mean being passive. It means knowing when to step in, set expectations, and draw a line to protect the team and the integrity of the work. Here’s what that looks like in practice: 🔹 Advocating for the team so they feel supported, protected, and empowered. 🔹 Championing the customer’s goals so they feel heard, valued, and understood. 🔹 Balancing demands on both sides—turning tension into alignment rather than allowing it to become friction. 🔹 Being transparent and direct, even when it feels uncomfortable. 🔹 Modeling composure when possible, but also standing firm when boundaries must be set. When we lead through service, something powerful happens: teams thrive, customers trust us more, and outcomes improve for everyone. Servant leadership isn’t always easy—and it’s not always calm. But it is always worth it. In a world that moves fast and demands more, choosing to lead with empathy, clarity, courage, and healthy boundaries is how we create sustainable success. #Leadership #ServantLeadership #ScrumMaster #Agile #TeamCulture #ConflictResolution #Boundaries #LeadByExample

6

1 Comment