Leading on Busy Days

By Himanshu Khurana

For leaders of teams and organizations, busy days are often marked by packed calendars, but workdays become truly challenging when the flow of work stalls. More time is spent explaining, waiting, and switching contexts than moving something to “done.” A vendor slips a last-minute change that blocks system integration, a security review adds late risk in the build pipeline, or finance interrupts with urgent asks. None of these alone is unusual, but together they disrupt attention and slow progress.

You know you’re in one of these days when conversations start with “Quick question…” and end with “Let’s circle back,” and your to-do list looks the same at 5 p.m. as it did at 9 a.m. The calendar may be full, yet little has advanced. It’s hard to lead on such days and many of the leadership lessons we know in theory fade in the moment.

This article outlines key practices that can be employed effectively. What teams need most is steadiness, perspective, and a sense that progress is still possible. Busy days should not be a test of endurance. Treat them as an invitation to restore flow both for yourself and for everyone who depends on you.

1) Anchor the room

When the day feels fragmented, the team takes its cues from you. The most useful support you can provide is to be the anchor with a clear point of view. Without that anchor, meetings drift into status updates or arguments about scope. With it in place, people know what matters now and what must be done next.

A simple technique is to pause before you enter a meeting or open a thread and ask three questions: Why does this matter? What does good look like today? What must we do next? Say that out loud in your first minute. You’ll notice people breathe out and understand what they’re working toward. Research on motivation and engagement shows that even modest progress has an outsized impact [1]. Teams notice when a leader is present with them, not just busy around them, and that presence builds confidence that challenges can be faced together.

For example, in an engineering design review when debate heats up over architecture choices, say: “A good outcome is leaving with two agreed priorities and a clear owner for the open risk. Let’s solve for that.” The conversation will shift from defending positions to making choices. You may not solve everything, but you help drive focus on clarity and accountability.

2) Widen the “we”

A big share of busy days is spent in conversations—first with your own team, then with peers across the organization. Under pressure, cross-team sync can derail and talk shifts towards blame. An effective technique here is to hold a broad and genuine sense of “we”: your direct team, yes, but also all the other functions that complete the picture including product management shaping direction, program management coordinating dependencies, QA validating quality under pressure, finance making the numbers work, operations delivering at scale, and support keeping customers whole.

State the shared outcome in plain language, then invite each function to offer its lens. Translate across those lenses so people hear not only their own concern but how it connects to the rest. Listen for risks, surface trade-offs, and align on what each group can commit to today [2].

For example, during a cross-team sync that derails into blame over a late release, reframe: “Our shared outcome is a stable customer rollout. From each function, what concern matters most, and what are the top two priorities?” Engagement improves because perspectives align before tasks are assigned.

3) Make progress clear and verifiable

On busy days, progress slips out of reach as attention scatters across interruptions, meetings circle without decisions, and priorities shift before anything feels finished. A key practice of effective leaders is to move in clear, verifiable steps that balance speed with clarity. Notice and leverage work patterns that travel across tasks: clear problem statements, right-sized milestones, decision steps, named owners, and simple check-ins. Adapt those patterns when risks surface, deciding in advance which calls are reversible and treating new information as a signal to adjust scope or sequence rather than stall. Progress is not only a shipment or a signature. Some days it is a clarified requirement, a trimmed dependency or a decision that clears a path for others. Other times it is a short discussion that surfaces an issue, rewrites the problem in plainer terms, and agrees on a smaller, testable step that keeps the effort moving. That is still progress because it prevents drift. When the units of work are demonstrated regularly, confidence is stronger because everyone can see progress.

For example, a team aims to deliver a full feature, but an upstream dependency looks shaky. Reframe “done” for the week as API responds with mock data and passes contract tests and name the owner. When the dependency slips mid-week, the team adapts without losing momentum because the slice was small and the proof of “done” was explicit.

Leading on busy days becomes far more manageable when leaders anchor discussions, widen perspectives, and make progress visible with meaningful actions that keep complex technical work moving forward.

Digging Deeper:

[1] T. Amabile & S. Kramer, “The Power of Small Wins,” Harvard Business Review, May 2011.
[2] C. Ceurvorst et al., “Why Cross-Functional Collaboration Stalls, and How to Fix It,” Harvard Business Review, June 2024.


About the Author

Himanshu Khurana is a senior technology executive who has served as CTO and VP of Engineering at Honeywell, Fortive, and Powin. He has led product and platform innovation in building technologies, energy storage, and industrial safety, focusing on emerging technologies and delivering impact through products and services in complex industrial systems. He holds a PhD from the University of Maryland and conducted research in cybersecurity at the University of Illinois. You can reach him on LinkedIn.


TEMS – 5 Focus Areas

Moving Product/Services from Idea to Market

Identifying and Implementing Successful Projects, and Systems

Integrating Technology for Capability and Productivity

Developing from Engineer to Leader

Balancing the Norms of Society, Government, and Regulators

Attend Upcoming Conference

TEMSCON Global Montreal, Canada – August 4-7, 2026

Join IEEE TEMS