009 When the Plan Breaks: Trust, Pivots, and Real Leadership

🎧 Listen to this episode on Apple Podcasts, Spotify, or your favorite platform.

The hardest part of product and design work is rarely the deliverable.

I wish a shiny PRD or impressive prototype were enough, but it’s not that simple. Sometimes the organization is not ready. The timing is wrong. The culture resists change. The team is tired. The stakeholder conversation goes sideways. The thing that made so much sense in my head suddenly has to survive inside a very human system.

Our daily reality is at the center of our conversation with Kirsten Rourke, founder of Rourke Training. Kirsten’s work blends e-learning, technical training, public speaking, presentation strategy, and stagecraft. She describes her focus as helping people reach their audience “in the way you actually mean to, rather than the way you think you mean to.”

For product managers, UX designers, product owners, consultants, and digital leaders, so much of the work is not simply what we make. The work is how clearly we communicate, how honestly we show up, and how well we understand the system we are working inside.

Authenticity is Not the Opposite of Professionalism

One of the strongest threads in this conversation is the difference between being polished and being trusted.

Kirsten talks about the frustration of watching people with powerful messages get coached into becoming slicker, smoother, or more “professional.”

We often prepare for stakeholder meetings, customer conversations, roadmap reviews, design critiques, and executive updates as though the goal is to remove every rough edge.

Unfortunately, trust does not come from sounding flawless. Trust comes from sounding real.

“I want them to become the most genuine version of themselves because that’s what actually creates connection.” – Kirsten Rourke

Authenticity means communicating clearly without hiding behind jargon. It means naming tradeoffs honestly.

Authenticity means being willing to say, “Here is what we know, here is what we do not know yet, and here is where we need to learn more.”

Before your next presentation or product discussion, ask:

• Am I trying to sound impressive, or am I trying to be understood?
• Where am I over-polishing instead of clarifying?
• What would make this conversation feel more human and more honest?

Cross-disciplinary Thinking Creates Insight and Friction

Kirsten shares a story about trying to bridge gaps between e-learning products and Creative Cloud products. She could see the connection. She had experience across the spaces, and she understood why integration would matter.

Yet seeing the connection and convincing an organization to change are not the same skill. Luckily, many people in the product and design space are great at pattern recognition.

“When you have broad knowledge, you start seeing opportunities and patterns that other people may not see. But organizations are often structured around silos.” – Metsy Rose

Silos are one of the challenges of cross-functional product work.

Product managers often sit between business goals, user needs, engineering constraints, analytics, customer feedback, and executive expectations. UX professionals often move between research, design systems, accessibility, customer psychology, and visual execution.

Thankfully, the broader our view becomes, the more connections we see.

Organizations do not always reward connective thinking. Sometimes they protect existing structures. Sometimes even when the idea is right, the ecosystem is not ready for it… yet.

When you see a valuable cross-functional opportunity, do not only ask, “Is this a good idea?” Also ask:

• What incentives currently reinforce the old behavior?
• Who is likely to feel threatened, ignored, or overloaded?
• What smaller proof point could help the idea land?

Emotional Intelligence is a Product Skill

“Sometimes the challenge isn’t whether an idea is correct. It’s whether the timing, environment, and culture are prepared to receive it.” – J Schuh

We can have the right research insight, the right roadmap recommendation, the right UX improvement, the right customer experience strategy, but if we ignore the emotional and organizational context, the idea may still fail.

Emotional intelligence (EQ) in product and design means understanding the room around the idea.

EQ means noticing when people are defensive because they feel blamed. It means recognizing when a team has change fatigue. It means knowing when to push, when to pause, and when to translate the idea differently.

This is not just “soft skill” work. It is the connective tissue of successful execution.

Before advocating for a pivot, redesign, roadmap change, or strategy shift, consider:

• What work does this create for others?
• What fear might be underneath the resistance?
• What does the organization need to believe before it can act?

Rejection is Not Always about the Quality of the Idea

Kirsten reflects on becoming emotionally attached to an idea and believing she was right while others were wrong. Oof, we’ve all been there.

Many of us have had the experience of seeing a better path and feeling frustrated when the organization does not move toward it. In product and UX work, this can feel deeply personal because our ideas are often tied to our judgment, craft, care for users, and professional identity.

“When an idea gets rejected, it can feel personal.” – Kirsten Rourke

She reminds us about an important truth: rejection is not always about the quality of the idea. Sometimes it is organizational reality.

We have to separate the fear of “this idea has no value” from the possibility that “this system is not prepared to act on it yet.”

Questions for Reflection

• Where are we currently treating organizational resistance as a communication problem, when it may actually be a readiness problem?
• What idea are we emotionally attached to, and what would happen if we stepped back from needing to be right?
• How can we make our product, design, or leadership conversations more human without making them less rigorous?

Key Takeaways

• Real leadership is not just having the right idea. It is understanding whether the organization is ready to receive it.
• Authentic communication builds trust faster than performative professionalism.
• Cross-disciplinary thinkers often see patterns early, but influencing change requires empathy, timing, and patience.
• Product managers and UX professionals need emotional intelligence because our work depends on people, not just processes.
• Rejection is not always proof that an idea is wrong. Sometimes it reveals the limits of the current system.

When the plan breaks, the hidden work begins.

Not the Jira-ticket work. Not the slide-deck work.

The human work begins: trust, timing, communication, empathy, and understanding the system well enough to move through it with care.

If you work in product management, UX/UI design, customer experience, consulting, or digital leadership, this conversation offers a grounded look at what it really takes to guide work through complexity.

– Metsy
Co-host, Pixels & Priorities

Stay Connected

🎧 Listen to new episodes every Tuesday on Apple Podcasts, Spotify, or your favorite podcast platform. Please leave us a rating, submit a review, and share with a friend. It helps more people find the show and join the conversation.

Connect on LinkedIn: Metsy Rose | J Schuh | Pixels & Priorities