Finance Job Hunt
All articles

· 5 min read

Company Promotes Best Accountant to Controller and Is Shocked That Managing People Is a Different Skill

By T. Smith

  • satire

SATIRE — When LedgerCrest Industries needed a controller, its executive team acted with the calm precision of people who had never considered that a controller might need to manage anyone. They promoted Priya, the senior accountant who had closed every month since the company’s founding, identified an intercompany error during a fire drill, and once corrected a deferred-revenue schedule while waiting for a dentist appointment. “She is clearly our strongest accountant,” said CEO Brad Wexler, placing a ceremonial second monitor on her desk. “Therefore she will be excellent at resolving conflict between two staff accountants who both believe the other person owns prepaid expenses.”

The selection process: technically flawless, conceptually incomplete

The company’s internal controller search lasted 19 minutes. Candidates were assessed on the only criterion leadership regarded as material: whether they could explain why last February’s accrued freight balance was $43 too high. Priya gave the answer, the invoice number, the cost center, and a brief history of the vendor’s billing practices. Her competitor said he had managed a team of six through an ERP implementation, redesigned the close calendar, and retained three employees during a hiring freeze. The panel thanked him for his “leadership perspective” and asked whether he knew where the $43 went.

Priya was promoted the following Monday. Her new job description stated that she would “own the close, develop talent, partner cross-functionally, strengthen controls, provide strategic insight, and make sure nobody is surprised.” Her old job description was quietly reassigned to Priya, now wearing a different title.

A controller is issued direct reports and no operating system

Within two weeks, Priya encountered the first issue not solvable by a tie-out. A staff accountant, Evan, delivered a bank reconciliation three days late. Priya opened the file, located the missing support, fixed it in 11 minutes, and sent it back with tracked changes in red, blue, and what witnesses later described as “a concerned mauve.” Evan did not improve. Instead, he became quiet in meetings, began saying “per my last email” aloud, and updated his professional profile during lunch.

LedgerCrest’s CFO, Dana Kline, responded with the company’s standard management-development plan: asking Priya to “be more strategic.” No one could define the instruction, but it was delivered with enough confidence to enter the performance-management system. Priya asked whether strategic meant setting expectations, delegating review work, coaching Evan, prioritizing the close, or escalating a capacity issue. Dana replied that it meant “taking it up a level,” then went into a meeting titled “Talent Is Our Differentiator.”

The new controller learns that people have undocumented dependencies

Priya’s first one-on-one meetings were scheduled for 15 minutes each, immediately after flash reporting, and included an agenda with columns for owner, due date, status, blocker, and “root cause of feelings.” Her team initially found the format intimidating. Then they found it useful. Then they asked for clearer priorities, review standards, and a decision about which of the CFO’s six “urgent” requests actually mattered before day five.

This presented a problem. Priya had been rewarded for personally absorbing ambiguity until the work was complete. Now the work required her to expose ambiguity before it became a midnight problem. She had to decide who did what, explain why, review without redoing, and accept that a deliverable could be good enough before she personally had touched every tab. This was considered a radical departure from LedgerCrest’s leadership model, which had historically been based on promoting the last person still online at 11:47 p.m.

Human capital receives its first reconciliation

The breakthrough came after Evan resigned, citing a “desire to pursue an opportunity with a clearer reporting structure,” an expression that LedgerCrest’s HR team classified as a mysterious external-market event. Replacing him took four months, because the requisition requested a staff accountant with public accounting experience, industry experience, NetSuite expertise, advanced Excel, Power BI, systems implementation exposure, strong communication skills, a willingness to work onsite three days a week, and “controller potential.” The approved range was described as “competitive in spirit.”

During the vacancy, Priya rebuilt the team’s close checklist, assigned named owners and reviewers, established weekly workload reviews, and began giving feedback before annual-review season. She also told the CFO that two people could not perform the work of three people merely because the forecast did not contain a headcount line. This was escalated as a communication-style concern, then approved as a backfill after the audit partner independently noticed nobody could produce the inventory reserve support.

Leadership announces a new insight

At quarter-end, LedgerCrest’s executive team held a retrospective. The CEO praised Priya’s “growth into leadership,” explaining that the company had always believed in developing managers from within. The CFO nodded solemnly and unveiled a new Controller Readiness Framework: candidates must demonstrate technical judgment, prioritization, delegation, feedback, hiring judgment, stakeholder management, and the ability to say no when a sales leader requests a revised margin analysis at 4:58 p.m. on close day.

“We have learned that managing people is not simply accounting, but with more calendars.”
— LedgerCrest Controller Readiness Framework

The framework will be introduced after the next promotion decision, because the next promotion decision is already scheduled for Friday and the candidate has just found a $43 variance.

The joke is that companies often treat controller as a reward for being the strongest individual contributor. The job may still require deep technical judgment, but once a controller has a team, the work also becomes setting priorities, creating review capacity, making decisions visible, and helping other people do good work without personally doing all of it. That part is not soft. It is operational.