Tax Season Is When Your Firm Learns the Most — And Remembers the Least

A few weeks ago, I sat down with a managing partner at a mid-size CPA firm. Smart person. Experienced. Running a practice that has survived every kind of regulatory change the last two decades have thrown at public accounting.

I asked how the firm handles knowledge capture during tax season and audits — what systems they use to track what's working, what isn't, where the bottlenecks are forming.

He looked at me the way you look at someone who has just asked a mildly absurd question.

"During tax season," he said, "we don't have time to collect anything. We're putting out fires from January through April. We do our improvements after. When it's over."

I asked what "after" looked like.

He paused. "Honestly? By the time it's over, people just want to move on."

If you've run a tax practice through a busy season, you've either said this or heard it.

---

That exchange has stayed with me — because the pattern it describes is not unique to accounting. I've spent years managing software delivery programs: fast-moving, high-pressure, deadline-driven. And I've watched the same failure mode play out in every environment where the work is too intense to stop and reflect. In every high-pressure environment I've worked in, the busiest seasons generate the most valuable learning — and almost none of it gets captured.

The result is expensive. Not in a way that shows up cleanly on a P&L, but in a way that compounds quietly across years. The same problems resurface every cycle. The same client situations catch teams off-guard. The same bottlenecks form in the same places. Senior people leave and take years of hard-won judgment with them. And every April, the firm survives another season without knowing quite how — or why some of it was harder than it needed to be.

This is not an accounting industry problem. It is a knowledge capture problem. And for the first time, there are tools purpose-built to solve it.

---

The fires that didn't have to happen

Here is the part most managing partners don't want to sit with too long: some of the fires you fight every season are partly the result of knowledge you didn't capture in a previous one.

Not all of them. Some complexity is irreducible — a new regulation, a client's situation, timing you couldn't control. But a meaningful portion of what feels like external chaos has internal roots. Take the client whose particular requirements surface every February and catch the team flat-footed every February. Not because the situation is new — because no one captured how they handled it last time. The insight existed. It just evaporated with the season.

In software, we have a name for this pattern: technical debt. You take shortcuts under pressure, you ship, and the shortcuts cost you more next sprint than they would have cost to fix in the moment. The debt compounds. Teams that never pay it down spend an increasing fraction of every cycle just servicing what they left behind.

CPA firms carry their own version. Call it operational debt. Every season that ends without capturing what worked and what didn't adds another layer. Left uncaptured, that debt compounds — you're not just repeating mistakes, you're repeating them with less experienced staff, while the partners who knew how to handle them have moved on to bigger books or retired. The firm gets better at surviving. It gets no better at thriving.

The cruelest part is that the information needed to break this cycle already exists. It surfaces during the season, not after it. It lives in the conversations partners have with frustrated clients. In the moments junior staff escalate things that shouldn't need escalating. In the bottlenecks that form around the same partner's review queue every single year. By the time April ends, most of that information has evaporated — replaced by the collective amnesia of a team that just wants a break.

---

Three things managing partners say here — and why they don't hold up

If you've been in practice long enough, you have objections ready. I've heard all three.

"We already do debriefs after the season."

Some firms do. Most don't do them rigorously. And the ones that do are fighting a fundamental timing problem: the debrief happens weeks after the events it's meant to examine. Memory has degraded. The specifics are gone. What remains is a general impression — "staffing was tight," "client X was difficult" — too vague to act on and too blunt to produce a meaningful change.

A debrief conducted in May about what happened in February is like a flight data recorder that only activates after you've landed safely. You learn that you made it. You don't learn much about the moments that mattered.

Capturing knowledge during the season — while the situation is live, while the friction is still fresh — is categorically different from reconstructing it afterward. The detail, the nuance, the specific moment that should have led to a process change: that lives in the moment. Not in the recap.

"Our senior people carry that knowledge."

They do. That's exactly the problem.

Institutional knowledge that lives in the heads of your most experienced people is not an asset — it's a concentration risk. When those people retire, take on a larger book of business, or leave for another firm, the knowledge leaves with them. The junior staff they never had time to properly develop are left to rediscover lessons the firm already learned, at the same cost it took to learn them the first time.

This is not a hypothetical. It is the succession crisis already playing out across professional services: an aging senior population, a generation of less-experienced staff who were rarely developed at the pace needed to absorb what the senior generation knew, and firms realizing too late that their "knowledge" was never an organizational asset. It was a personal one, locked inside a handful of people.

The answer is not to expect senior partners to document everything. They won't — and they shouldn't have to. The answer is to build lightweight capture into the work itself, so that what they know starts to transfer structurally, not just through proximity and osmosis.

"We don't have time to add one more thing during our busiest months."

This is the objection that sounds most reasonable and is actually the least examined.

The implicit assumption is that knowledge capture is a separate activity — something you do in addition to the work. A form to fill out. A meeting to schedule. Something that competes with billable hours for time and attention.

That assumption was true when capture meant stopping what you were doing and writing a report. It is not true anymore.

Modern knowledge capture tools are built around structured conversations that take minutes, not hours. A partner finishes a difficult client call and answers four focused questions while the details are fresh. A staff member completes a complex return and records what confused them and how they resolved it. A manager notices a recurring bottleneck and captures the observation in real time — not in a retrospective six weeks later.

The return — fewer repeated mistakes, faster staff development, better institutional memory — compounds in a way that "we'll handle it after the season" never does.

---

What changes when you start capturing

Here's what that looks like in practice. A new manager at your firm is fielding a complex multi-state manufacturing client in February. Instead of calling around to find out if anyone has handled this before, they search the firm's knowledge base: "How have we handled clients in manufacturing with multi-state filing requirements?" The answer comes back — grounded in prior engagements, with the specific complexities that came up and how they were resolved.

That's what structured knowledge capture makes possible. The firm's accumulated judgment stops living in individual heads and starts behaving like a shared asset.

Firm leaders build short, focused sessions — a handful of questions tied to specific moments in the engagement cycle: after a difficult client call, after a complex return is filed, after a bottleneck clears. Staff and partners complete them in minutes while the details are still fresh. The system generates summaries, surfaces patterns across respondents, and builds a searchable record that grows with every completed season.

For a CPA firm, this translates to four things that don't happen otherwise:

During engagements: Issues get captured in real time — not reconstructed from memory three months later when the detail that mattered is gone.

Across staff: Junior staff struggles surface before they become errors. Experienced partners transfer judgment through structured capture rather than proximity and osmosis.

Across clients: Each client accumulates a record of their patterns, preferences, and recurring complexities. The team that picks up a file in February isn't starting from scratch.

Across seasons: Post-season planning stops being impressionistic. You're working from data about what actually happened — not from what people remember feeling in May.

---

The habit that separates them

No one is suggesting you redesign your practice during tax season. That would be absurd — and anyone who tells you otherwise has never run a high-pressure delivery organization.

But there is a difference between redesigning the practice and starting to capture the information that would let you improve it.

The first is too much to ask during the busiest months. The second takes minutes.

In software, we learned this the hard way: teams that wait until the project is over to think about how to do it better are always behind. The market doesn't pause while you catch up. Neither does your competition, your talent market, or your clients' expectations.

The firms that will look different in ten years are not the ones that work harder during tax season. They are the ones that build the habit of learning during it — so that every season makes the next one slightly less brutal, and the knowledge generated by your best people actually outlasts their tenure.

---

The managing partner I spoke with told me his firm couldn't afford the luxury of improving while fighting fires. I understand why it feels that way. But the math runs in the other direction: not capturing costs you next season, and the season after that, compounding until the improvement you kept deferring costs more than doing it right ever would have. Every season that ends without capturing what it generated is a season you paid for twice — and a down payment on a third.

The way your firm has always survived tax season is not the same as the best way to run it. And for the first time, you have a tool that makes the alternative possible.

If you want to see what this looks like for a practice your size, Mayetik is worth thirty minutes.