Are we saving time or creating time debt?

I’ve been thinking a lot lately about how to help teams make the best use of their time.

There’s an undercurrent that pushes us to keep meetings focused, decisions moving forward, and reduce unnecessary friction. The intention is valid. Everyone is busy, calendars are packed, and if we can work together more effectively, that’s time people get back to focus on what matters most.

But one theme I’ve been noticing is that some of the biggest inefficiencies can come from trying to save time. More specifically, from skipping the moments that create alignment.

I’ve seen this in my own habits. Somewhere along the way, “we can take that offline” became a bit of a crutch. I worried that spending too much time on context or clarification would derail a meeting. Looking back, I underestimated the value of those conversations.

Sometimes what feels like a detour is actually the discussion that helps people align, challenge assumptions, and build a shared understanding.

Most people don’t arrive at a meeting with a clean slate. They’re coming from another call, finishing an email, responding to messages, or already thinking about what’s next. We carry assumptions, priorities, terminology, and context from one conversation into another, then assume everyone is starting from the same place.

Often, they’re not.

I’ve found that the most productive discussions usually start with a few minutes of level setting: where we are, why we’re here, what decision we’re trying to make, and what context matters.

It sounds simple, but those few minutes often save far more time than they consume.

A recent example of this came up during a working session around the word process. Everyone understood the term, but not everyone meant the same thing. One group was thinking about workflows and business processes. Another was thinking about the end-user experience within the tool.

Neither perspective was wrong, but we were getting stuck because we were having two different conversations while believing we were having one.

I’ve seen the same thing happen with terms like governance, requirements, roadmap, and MVP. Familiar terms don’t always mean shared understanding.

We skip alignment because we’re trying to be efficient, only to spend time in the future revisiting decisions, clarifying misunderstandings, repeating conversations, and reworking deliverables.

The time didn’t disappear; we just paid for it later.

Sometimes the most productive thing a team can do is slow down long enough to make sure everyone is looking at the same thing, through the same lens, with the same end goal.

Sometimes we just need a little bit more time.

---