When stakeholders complain that they are not getting what they need, the obvious diagnosis is often a difficult stakeholder, poor communication, or unrealistic expectations.

But repeated frustration usually has more behind it.

In this episode of Is That Really the Problem?, Navicet's Peter Moon and Lauren Broomall unpack what sits underneath stakeholder dissatisfaction: limited visibility into work and priorities, unclear service models, mismatched expectations, capacity constraints, defensive commitments, and the difference between delivering what someone asked for and solving the problem they actually have.

They explore how shared-services teams can get caught in a reinforcing cycle of frustration. Stakeholders become accustomed to disappointment. Delivery teams become cautious about overcommitting. Estimates get padded, processes become more rigid, and both sides develop ways of protecting themselves from the other.

The conversation also looks at what changes when teams move beyond order taking and begin working as strategic collaborators: making work visible, sharing unfinished thinking, testing assumptions early, understanding the underlying need, and designing services around both organizational constraints and the people who depend on them.

The problem may not be that stakeholders complain. The complaint may be evidence that the relationship, process, or service model is making effective collaboration harder than it needs to be.

When dependencies show up late, the obvious diagnosis is often poor planning. Someone should have identified the need earlier, communicated it sooner, or put it on the roadmap.

But in complex organizations, some dependencies only become visible as the work itself becomes clearer.

In this episode of Is That Really the Problem?, Peter Moon and Lauren Broomall from Navicet unpack why dependencies surface late, including changing priorities, evolving requirements, shifting organizational structures, incomplete information, and the simple fact that teams often depend on expertise they do not themselves possess.

They explore the role of dependency workshops, roadmaps, planning tools, assumptions, and progressive levels of detail in making those dependencies easier to anticipate and manage. They also look at the limits of trying to map everything in advance, especially when plans are still changing and the organization around them is changing too.

The conversation offers a more practical way to think about dependency management: not as an attempt to eliminate surprises, but as a way to surface the important ones early enough, create useful placeholders for what is not yet known, and make the collaboration between teams much less disruptive when the details finally emerge.

When people say “roles and responsibilities are unclear,” the obvious response is usually to create more clarity: better role definitions, a RACI, a team charter, or more detailed documentation.

But what if the roles are already clearly defined?

In this episode of Is That Really the Problem?, we unpack the different problems that can hide underneath role confusion, including unclear decision rights, overlapping team boundaries, shared-service models, differences in team composition, and the limits of trying to define ambiguity away.

They also explore when RACIs are useful, why process maps can sometimes reveal more than role descriptions, and why teams may need stronger ways of working through ambiguity rather than simply adding another layer of documentation.

The conversation offers a practical way to think beyond the role description itself and focus on the specific points of friction that may be making collaboration harder than it needs to be.

If your team relies on heroics to get the work done, telling people to “just say no” probably won’t fix it.

When heroics become the norm, the issue is bigger than individual boundaries. It can be about how work comes in, how priorities get set, who has authority to make tradeoffs, and whether anyone can accurately see the relationship between demand and capacity.

In this week’s Is That Really the Problem?, we unpack what may be underneath a team’s reliance on heroics and why the better question might be: what about the way we manage the work keeps making heroics necessary?

“Our tools aren’t working for us.” Sometimes the tool really is a poor fit. But in plenty of cases, the tool is where a deeper problem becomes visible.

In this episode, we explore what may be hiding behind a frustrating tool experience, including inconsistent work structures, unclear terminology, competing processes, decision rights, organizational readiness, and the gap between meeting technical requirements and supporting the people who will use the tool every day.

We also discuss why flexible tools still carry an echo of their original purpose, how moving disorganized information into a new platform can recreate the same problems, and why a small prototype can reveal more about tool fit than a long requirements scorecard.

If your team is considering a new tool, struggling with an existing one, or building workarounds around a system that never quite seems to fit, this conversation will help you ask a better question: Is the tool really the problem?

“My boss is a micromanager.” It’s a familiar workplace frustration, but what’s actually driving the behavior?

In this episode of Is That Really the Problem?, we unpack what might be happening beneath micromanagement, from pressure and poor visibility into the work to the difficult transition from being a great practitioner to becoming a great manager. We also explore why the right amount of support isn’t always obvious, and how managers and direct reports can get more explicit about what kind of help is actually useful.

If you’ve ever felt micromanaged, wondered whether you might be micromanaging someone else, or struggled to find the right balance between autonomy and support, this conversation offers some new questions to consider and practical things to try.

Everything is a Priority — So why are we delivering more than we planned — and burning out anyway?

The annual plan is locked. The stack rank is done. The line is drawn. And somehow, by year's end, we've delivered far more than we committed to — and everyone's exhausted. If deprioritized work gets done anyway, what was the prioritization for?

In this episode, we pull apart what's actually underneath "everything is a priority": planning cadences that can't keep up with the pace of the work, teams that grow because they can't say no, a culture that rewards heroics, governance structures with as much hierarchy as the org chart, dependencies nobody can see, and the quiet arms race where every request gets rated top priority — because anything less never gets done.

We've watched teams navigate this in some of the largest, fastest-growing companies around, and we share what we've seen work: not stack-ranking behind closed doors, and not throwing the decision back at stakeholders either, but a harder, more interesting middle path. We also each offer one small thing worth trying this week.

If this conversation helps you think about a problem differently, share it with someone who's trying to improve the way work gets done.

And until next time — keep asking: is that really the problem?

We Have Too Many Meetings — So why does cutting them never seem to work?

Every organization has tried the obvious fixes: 30-minute limits, no-meeting Fridays, "this could have been an email." Calendars stay full anyway. Constrain the meeting count in one place and it bulges out somewhere else, which suggests that maybe the meetings count isn't the problem. It's a symptom of something else.

In this episode, we go looking for what that something is. It turns out "too many meetings" can mean at least five or six different things, and almost none of them get fixed by having fewer meetings. One of us also admits, on the record, to actually liking meetings.

We leave you with one question worth asking about your own calendar this week — one that doesn't require restructuring anything, or anyone's permission.

If this conversation helps you think about a problem differently, share it with someone who's trying to improve the way work gets done.

And until next time — keep asking: is that really the problem?

Too many meetings, roles unclear, priorities keep changing. This is a podcast about the kinds of problems big companies have.

We're Lauren Broomall and Peter Moon. In 2014, we started Navicet, a human-centered management consultancy, where we've spent years helping organizations untangle complex challenges and improve how work gets done.

Come join us. It will be fun.