017 When Everything Is Priority One

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

Burnout Is Not Always a Personal Performance Problem

You have finished a demanding workday with the uncomfortable feeling that you were constantly moving but never quite getting ahead. We all have.

We attend the meetings. Answer the messages. Reprioritize the roadmap. Update the story. Review the design. Respond to the urgent request that appeared halfway through the sprint.

Somehow, the important work still feels unfinished.

When that pattern keeps happening, we tend to turn the problem inward. We wonder whether we need a better productivity system, stronger boundaries, greater resilience, or one more AI tool to help us keep up.

During my conversation with J, I kept returning to a different possibility:

“It’s not about you needing to be better, but this is an environment that we are all operating in.” – Metsy Rose

Burnout is not always an individual weakness. It can be a signal that the system surrounding the individual is generating more cognitive and emotional demand than people can sustainably carry.

For product managers and UX professionals, three conditions are especially important: clarity, alignment, and timing.

Clarity Is Invisible Infrastructure

Product and design teams rarely begin with perfect information.

We often receive a problem with fuzzy edges, incomplete research, competing stakeholder interpretations, or an urgent deadline already attached. Product managers are expected to build clarity while moving the work forward.

That creates a difficult balancing act.

Spend too long defining the problem, and we may be accused of slowing delivery. Move too quickly, and we risk sending designers and developers into a maze built from assumptions.

The cost of insufficient clarity does not appear only in documentation. It appears later as:

• Design churn
• Rewritten user stories
• Conflicting stakeholder feedback
• Unexpected dependencies
• Delayed development
• Frustration between teammates

Clarity is therefore not administrative polish. It is infrastructure for collaboration.

One useful practice is to hold a brief directional check before work becomes expensive. A sketch, rough wireframe, or five-minute conversation can reveal whether product and design are solving the same problem before anyone invests two days creating a polished answer to the wrong question.

I used to think I needed to create a perfect work item covering every eventuality and user consideration unfurled across the fields in Jira, but I cannot do that on my own. That is not the goal. That is too slow for today's world.

Refinement sessions now look more like a link to a Jira story posted to the chat, an introduction of a problem and unrealized business value, the direction I would like to head, and then a discussion with my devs and QA to fill in the blanks... or identify the holes that still need to be filled before work can begin.

Alignment Includes Emotional Labor

Alignment is often described as though it is a tidy business activity. Gather the right people, review the goals, make a decision, and move forward.

The reality is much more human.

Alignment involves telling someone that their work has been deprioritized. It means reconciling groups that are measured by different outcomes. It requires asking difficult questions when everyone is already under pressure.

It also means remembering that the person challenging a decision may be protecting a customer, a team, or a responsibility we cannot see.

J described a situation many of us will recognize:

“They’re all number one. Everything on here is number one.” – J Schuh

When everything is priority one, prioritization has effectively disappeared. The team is left to absorb the contradiction through longer hours, fragmented attention, or quiet tradeoffs in quality.

Healthy alignment requires leaders to make those tradeoffs visible. Instead of declaring six priorities equal, teams need explicit guidance about sequence, capacity, and what will not happen yet.

That clarity can feel uncomfortable, but hidden prioritization does not remove the discomfort. It merely transfers it to the people doing the work.

Timing Can Turn Ambiguity Into Urgency

A small change in product work can create a long chain of consequences.

A deadline moves. A leader introduces an urgent request. A dependency appears. A team already at capacity is asked to absorb additional work.

Everyone shifts into reaction mode.

The problem is not only that the team has more work. It causes people to stop thinking about one complex problem, reconstruct the context of another, and later rebuild the context they abandoned.

“The more you context switch, actually it degrades your effectiveness. It reduces your ability to get things done and produce quality work.” – J Schuh

Context switching creates the appearance of motion while quietly consuming the attention required for meaningful problem-solving.

Product and design leaders can reduce this pressure by asking:

• What truly changed?
• Which existing commitment moves because of this request?
• Who needs to be realigned?
• What information is still missing?
• What level of quality is realistic within the new timeframe?

Urgency should create a decision about tradeoffs, not an expectation that people will somehow expand their capacity.

AI May Accelerate the Expectation, Not the Work

AI is frequently presented as the escape hatch from workload pressure.

Some tools genuinely save time. I use AI in parts of my own product work, and I am hopeful about what it can help us do.

The more complicated reality is that AI does some things well and quickly. It does not do everything well or quickly.

Learning a new tool takes time. Building a reliable workflow takes experimentation. Reviewing outputs takes judgment and a fresh mind. A poor result still requires revision, regardless of how quickly it appeared.

There is also a larger organizational risk. Once a task can be completed faster, that speed can become the new minimum expectation. The promised free time becomes additional capacity for more work.

J captured the emotional result:

“There is a sense that you always have to be 'on'.” – J Schuh

AI cannot compensate for an unclear problem, conflicting goals, or unrealistic capacity. In those situations, it may simply help us produce the wrong answer more rapidly.

Creative Work Requires Space to Think

Creative and strategic work cannot always be summoned on demand.

Designers need time to explore possibilities. Product managers need time to synthesize information, consider tradeoffs, and understand the implications of a decision.

“Creatives are humans. We can’t always just be highly creative at the drop of a dime.” – J Schuh

When teams remove thinking time in pursuit of speed, they often receive more familiar and less remarkable solutions. People default to the first viable answer because there is no room to investigate a better one.

Space to think is not wasted time. It is where judgment, creativity, and product strategy actually happen.

Practical Ways to Reduce the Pressure

We may not control the entire organization, but we can create small pockets of clarity and humanity within our teams.

• Confirm direction early. Review rough thinking before producing polished deliverables.
• Name the tradeoff. When new work enters, explicitly identify what moves out or moves later.
• Separate urgency from anxiety. Ask what must happen now and what merely feels uncomfortable.
• Protect focused work. Reduce unnecessary context switching and meeting fragmentation.
• Investigate intention before assigning blame. Misalignment often contains information the other person did not have.
• Discuss capacity honestly. A full sprint does not become larger because a new priority appears.

These practices will not eliminate every source of burnout. They can prevent teams from turning structural pressure into interpersonal damage.

Questions for Reflection

1. Where is missing clarity currently creating hidden work for your team?
2. When a new priority appears, what process determines which existing commitment changes?
3. Does your team have enough space to think, or only enough time to react?

Key Takeaways

• Burnout can be a signal of system conditions, not individual inadequacy.
• Clarity prevents ambiguity from becoming expensive rework.
• Alignment requires emotional intelligence as well as meetings.
• Context switching reduces both quality and effectiveness.
• AI can amplify unhealthy expectations when leaders ignore capacity and tradeoffs.

Final Thoughts

Toward the end of our conversation, I summarized the tension this way:

“Ultimately, if you don’t have clarity, alignment, and timing, the speed of our current world is going to amplify the problem and add pressure.” – Metsy Rose

Product and design professionals are being asked to navigate rapid change, expanding expectations, economic uncertainty, and evolving AI tools while continuing to create thoughtful experiences for other humans.

We should expect excellent work. We should also build environments where excellent work remains humanly possible.

Where are clarity, alignment, or timing creating the most pressure for your team? Join the conversation and share what you are seeing in your own product or design organization.

– 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