Aug 2, 2026

Visibility isn't the same as more meetings

Managing multiple products taught me that teams need visibility as they grow, but visibility can quickly turn into ceremony.

• #engineering-management
• #teams
• #productivity

One of the problems that shows up when you’re managing multiple products is surprisingly simple:

You don’t know what’s happening.

Not because people aren’t working.

Usually the opposite.

There is so much happening that it becomes difficult to see the important things: what’s blocked, what’s slipping, where two teams are quietly dependent on each other, what needs a decision nobody’s made yet.

At one point, while I was running delivery across two SaaS products at once, we started using pods to make ownership and delivery more visible across teams.

It helped.

But it also taught me something else.

Visibility can become ceremony

A standup is supposed to help a team coordinate.

It shouldn’t become a daily performance where everyone proves they were busy yesterday.

I’ve sat through enough of those.

“I worked on X.”

“Today I’ll continue X.”

“No blockers.”

Repeat tomorrow.

The meeting happened.

Nothing changed.

The useful questions are different

When I think about a useful team update now, I care more about:

What changed?

What’s blocked?

What decision do we need?

Who owns the next step?

That’s enough surprisingly often.

The purpose isn’t to make the manager feel informed.

The purpose is to help the team move.

Pods helped because ownership became clearer

The pod model wasn’t useful simply because it changed the org chart.

It helped because teams had clearer ownership around a product area.

That made conversations easier.

Instead of asking:

“Who’s working on this?”

you could ask:

“What does this team need to unblock this?”

That’s a subtle difference, but an important one.

The hidden cost of a meeting

Every recurring meeting has a cost.

Not just the thirty minutes on the calendar.

It’s thirty minutes multiplied by everyone attending.

Then there’s the context switch before it.

The interruption afterward.

The work that doesn’t get done because the team is waiting for the next meeting.

That’s why I don’t think the answer to poor visibility is automatically another meeting.

Some of what we needed turned out to live in dashboards instead — we started pulling PR review turnaround and cycle time into LinearB, which meant a stuck review showed up on a graph before it ever needed a standup to surface it.

Sometimes it’s a written update.

Sometimes it’s simply asking why nobody knows what’s happening.

Good visibility should help people act. The LinearB numbers only mattered because we actually changed things because of them — reviewer rotation, smaller PRs, review SLAs. A dashboard nobody acts on is just ceremony with extra steps.