Some days being a SaaS CFO feels like air traffic control — but every plane is on fire.

There are days in Finance when the calendar looks less like a schedule and more like evidence.

Board prep. Forecast review. A system issue. Three business-partner questions. A meeting about the meeting that will decide when the next meeting happens.

Then 5:30 arrives and the one piece of work that actually required judgment is still sitting untouched.

I do not think this is mainly a productivity-app problem.

I think it is an operating-model problem.

Finance has unusually expensive context switching

Moving from a vendor question to a revenue forecast to a board narrative is not the same as moving between three similar tasks.

Each requires a different mental model.

The cost is not only the minutes spent switching.

It is the depth we never reach because another notification arrives before the thinking becomes useful.

FP&A is supposed to connect information across the business.

That becomes difficult when the analyst’s attention is being allocated in 11-minute increments.

Urgent and consequential are different

A Slack message can feel urgent because another person is waiting.

A downside scenario for next week’s executive meeting may be far more consequential and completely silent.

I like separating requests by consequence, deadline and reversibility.

What decision is waiting? What happens if this is answered tomorrow? Can someone else handle it? Does the answer require me specifically?

Those questions are more useful than sorting the inbox by whoever typed “quick question.”

I protect thinking time before the calendar fills

If I wait for two empty hours to appear naturally, I may see them around Thanksgiving.

I prefer blocking time for work that needs concentration before routine meetings consume the week.

Forecast architecture. Scenario analysis. Writing. Reviewing a complicated model. Anything where the value comes from connecting ideas rather than processing transactions.

The block does not need to be sacred in a religious sense.

Real emergencies exist.

It should be expensive enough to interrupt that routine requests do not win automatically.

A sterile cockpit is a useful idea—with limits

Aviation uses the concept of limiting nonessential activity during critical phases of flight.

I like the analogy for Finance.

There are moments when fragmented attention creates disproportionate risk: finalizing a board forecast, reviewing a liquidity scenario, validating a model before distribution.

During those windows, I want fewer inputs.

No unnecessary meetings. Notifications off. One task.

I do not need to pretend the office is an airplane.

I just appreciate that pilots figured out a long time ago that concentration is a control.

Recurring meetings should earn their place

A meeting that made sense two years ago can survive long after the decision it supported disappeared.

Finance calendars accumulate these things.

Weekly status meetings. Pre-close meetings. Forecast check-ins. Reporting reviews.

I like asking what decision or coordination problem the meeting solves.

If the answer is “we have always done it,” I become interested.

Removing one recurring hour can return more annual capacity than automating a small monthly report.

Office hours can reduce random interruption

Business partnering requires accessibility.

I do not want Finance hiding behind focus time while operators wait days for answers.

One practical compromise is predictable availability.

Office hours, recurring business-partner blocks or known response windows can give people access without turning every question into an immediate interruption.

The exact mechanism depends on the culture.

The principle is to make responsiveness intentional instead of continuous.

Slack is not a work queue unless we design it that way

Chat tools are excellent for conversation.

They are less excellent as the permanent system for prioritizing finance work.

A request arrives in a channel, another in a DM, one by email, two verbally after a meeting.

Now the finance person is carrying the queue in their head.

For material requests, I like some visible intake mechanism.

It can be simple.

What is the question, who needs it, by when, and what decision does it support?

That alone makes prioritization much less political.

Not every fire drill is unavoidable

Some genuinely come from the business.

A customer issue. A financing question. A sudden operating problem.

Others are recurring processes that we have chosen to experience as emergencies.

The board deck is due on roughly the same schedule every quarter. Close happens every month with suspicious regularity.

If those events repeatedly require last-minute heroics, I look at the process before I praise the hero.

Predictable urgency is usually a design opportunity.

I batch low-judgment work where I can

Approvals, routine responses, small data pulls, administrative updates.

These tasks still matter.

They just do not all need to interrupt deeper work at the moment they arrive.

Batching reduces the number of times the brain has to reload the finance equivalent of a different operating system.

I would rather process six small approvals together than allow each one to take a bite out of six separate hours.

The CFO has to model the behavior too

If the finance leader sends nonurgent messages at all hours, attends every meeting and responds to every question instantly, the team learns what “good” looks like.

Then leadership wonders why nobody has time for strategic work.

Culture is often a calendar with explanations added afterward.

If we want analysts and managers to think, we have to make thinking an acceptable use of visible work time.

Delegation is not just workload management

Senior finance people can become bottlenecks because they are good at answering questions.

Everything routes to them.

That feels efficient until the organization cannot move without their response.

I like pushing recurring decisions toward the lowest level with enough context and authority to handle them safely.

That develops people and protects senior attention.

The objective is not to make the CFO unreachable.

It is to stop using the CFO as a human API.

Documentation reduces interruption

If people repeatedly ask where a metric comes from, how a process works or which file to use, answering faster is not the only option.

Document it.

A short model guide, metric definition or process note can remove dozens of future interruptions.

I am not advocating a corporate encyclopedia.

I am advocating writing down the things the organization keeps asking humans to remember.

Close and forecast calendars should protect each other

Finance creates some of its own context switching by overlapping major cycles badly.

If FP&A starts forecast meetings while Accounting is still changing actuals, everyone pays.

If the board process begins before forecast assumptions are stable, everyone pays again.

I like designing the operating calendar as a system: close, analysis, forecast, management review, board preparation.

Dates should reflect dependencies rather than historical habit.

I leave capacity for the unexpected

A calendar scheduled to 100% assumes nothing unusual will happen.

That is an optimistic assumption for Finance.

I would rather preserve some capacity than run the team at theoretical maximum utilization.

The open space is not waste.

It is where an unexpected analysis, customer issue or executive question can land without destroying the rest of the week.

Airlines learned that a schedule with no slack looks efficient right up until weather exists.

The measure is not how busy the calendar looks

I care about whether the important work happened.

Did Finance identify the risk? Did management get the analysis before the decision? Did the forecast improve? Did the team fix a recurring process instead of surviving it again?

A full calendar can coexist with very little progress.

So can an empty-looking two-hour block with some of the highest-value work of the week.

Clarity scales better than constant availability

I do not think the answer is disappearing for half the day and telling everyone to respect my boundaries.

The answer is clearer priorities, predictable access, better processes, stronger delegation and protected concentration when the work requires it.

Finance will always get interrupted.

It should. We are part of the business.

But if every incoming request gets equal access to attention, the calendar will make the strategic decisions for us.

I would rather decide deliberately.

Some work needs a fast response.

Some work needs a quiet room.

Knowing the difference is part of the job.

Meeting preparation should be part of the meeting cost

A one-hour meeting can consume four hours of Finance capacity if three people each spend an hour preparing for it.

I like looking at the full cost.

Does the meeting need a custom deck? Could the same dashboard support the discussion? Are we rebuilding information that already exists because the meeting format expects slides?

Preparation is sometimes necessary.

It should still be counted.

A recurring meeting with expensive preparation deserves a particularly clear purpose.

I distinguish production time from interpretation time

Finance calendars can look analytical while most of the hours are actually production.

Pull data. Refresh model. Format deck. Reconcile report. Update commentary.

Those tasks enable analysis, but they are not the same thing.

I like measuring where the team’s time goes.

If 80% of a forecast cycle is spent assembling the forecast and 20% understanding it, automation has a very obvious target.

The goal is not automation for its own sake.

It is changing that ratio.

Decision deadlines should drive analytical deadlines

Sometimes Finance produces work earlier than anyone needs it because the calendar was inherited.

Sometimes it produces work too late because nobody worked backward from the actual decision.

I like starting with the management event.

When does the CFO need the answer? When does leadership decide? How much review time is necessary? What inputs have to be available before Finance begins?

Then build the schedule backward.

Deadlines make more sense when they are attached to decisions instead of dates.

There should be a cost to changing priorities

Not a punishment.

A tradeoff.

If an urgent analysis moves to the front, something else may move back.

I like making that visible.

Otherwise every new request simply gets added to the existing workload and the team absorbs the difference through longer hours or lower quality.

Capacity is finite even when the spreadsheet has another row.

Leaders should be able to reprioritize.

They should also see what the reprioritization displaced.

I watch for people becoming permanent routers

Sometimes a finance manager spends the day forwarding questions, checking statuses and connecting people who could eventually connect directly.

That coordination may be necessary during growth.

It should not automatically become the permanent job.

If the same handoff happens repeatedly, I look for clearer ownership, shared data or a direct workflow.

Removing a human routing step can free more strategic capacity than another personal-productivity trick.

Remote work did not invent interruption

It changed the delivery mechanism.

Before Slack, people walked over to a desk.

Before that, I assume they found some other way to ask for a number five minutes before lunch.

The underlying issue is organizational: how does work enter Finance, how is it prioritized, and which questions require synchronous conversation?

Tools can amplify bad norms or support good ones.

They do not decide the norms for us.

Deep work should produce something decision-relevant

I am not interested in protecting focus time because concentration is morally superior.

I protect it because certain finance outputs require it.

A coherent scenario model. A thoughtful forecast challenge. A written recommendation. A system design.

If the block produces no meaningful output, the calendar label did not create value.

The discipline goes both ways.

Protect the time, then use it for work worthy of protection.

A healthier finance calendar feels less heroic

The month has a rhythm. People know when inputs are due. Business partners know when Finance is available. Senior people are not the only path to an answer. Reporting production is increasingly automated. There is enough slack for something unexpected.

None of this eliminates busy periods.

Budget season will still be budget season.

Board weeks will still have gravity.

The difference is that chaos becomes episodic instead of the operating model.

That is what I am after.

Not a perfectly empty calendar.

A finance function with enough control over its attention to use judgment before the deadline uses it for us.

That is enough.