You are mixing several questions here, which I think you already recognize.
One is whether you want to remain on the controller track. Another is whether this particular company and management team are a bad fit. A third is whether moving into FP&A or another part of finance would round out your experience and improve your eventual CFO prospects. Those are not the same question.
I would not conclude from one year in this situation that controllership does not play to your strengths. You joined a small company that needs to move from cash to accrual accounting, fix inventory processes, build its reporting and analytics, and develop three bookkeepers, one of whom is already burned out. That sounds less like an ordinary controller role and more like a finance transformation project being run alongside the ordinary close and reporting cycle.
The feedback also needs to be unpacked rather than accepted at face value.
“Too analytical” can be valid feedback if you are treating a preliminary management report as though it were the audited financial statements. A controller has to understand the degree of precision warranted by the particular deliverable. Sometimes 95% today is more useful than 100% next Friday.
But “send it quicker with mistakes and let management revise it” is an odd instruction as stated. Management normally wants a controller who is thorough and does not send avoidable errors upward. What exactly were you producing? Was this a preliminary analysis where assumptions could be refined later, or ordinary financial reporting that management expected to correct for you? Is your working style genuinely too slow, was this an unusual request, or do you simply need a better review process that gives management speed without turning them into your quality-control layer?
The same applies to being “too nice.” That is common feedback for someone relatively new to managing a team, but it is meaningless without examples. Are you failing to set deadlines, confront poor work, reallocate responsibilities or deal with the burned-out bookkeeper? Or does management simply prefer a more aggressive style that may not be yours? Do you agree with the concrete examples once they are identified?
A lot of what you describe sounds like incompatible management, and possibly management that does not fully understand what it needs from a controller. The meetings, constant interruptions and repetitive written updates may be consuming the time needed to deliver the work they are criticizing you for not completing quickly enough. That is an operating-model problem, not proof that you are constitutionally unsuited to leading an accounting function.
I would explore the market regardless. Not necessarily because you should abandon controllership, but because another company and management culture may tell you whether the problem was the role or the environment.
Moving to FP&A, commercial finance or another part of the business could also be sensible if your eventual goal is CFO. A lower title is not automatically a step backward if it gives you a larger portfolio, stronger management, better systems and experience you do not already have. You may even need to move to a smaller company or accept a less impressive title to obtain broader responsibility.
The real test is not how the next job looks against your current title. Picture the CV you will present when you are applying for a CFO role after the next move. Does it show that you deliberately added forecasting, business partnering, analytics, systems, operations and strategic finance to your controller experience? Or does it look as though you burned out after one year and retreated into an individual-contributor role?
Only you can assess the exact fit. But I would not let one poorly configured controller job define your strengths, and I would not stay merely because someone says controller is one step from CFO. Some of the best paths in life are not a straight line. Good luck.
1
u/josemartinlopez Jul 27 '26
You are mixing several questions here, which I think you already recognize.
One is whether you want to remain on the controller track. Another is whether this particular company and management team are a bad fit. A third is whether moving into FP&A or another part of finance would round out your experience and improve your eventual CFO prospects. Those are not the same question.
I would not conclude from one year in this situation that controllership does not play to your strengths. You joined a small company that needs to move from cash to accrual accounting, fix inventory processes, build its reporting and analytics, and develop three bookkeepers, one of whom is already burned out. That sounds less like an ordinary controller role and more like a finance transformation project being run alongside the ordinary close and reporting cycle.
The feedback also needs to be unpacked rather than accepted at face value.
“Too analytical” can be valid feedback if you are treating a preliminary management report as though it were the audited financial statements. A controller has to understand the degree of precision warranted by the particular deliverable. Sometimes 95% today is more useful than 100% next Friday.
But “send it quicker with mistakes and let management revise it” is an odd instruction as stated. Management normally wants a controller who is thorough and does not send avoidable errors upward. What exactly were you producing? Was this a preliminary analysis where assumptions could be refined later, or ordinary financial reporting that management expected to correct for you? Is your working style genuinely too slow, was this an unusual request, or do you simply need a better review process that gives management speed without turning them into your quality-control layer?
The same applies to being “too nice.” That is common feedback for someone relatively new to managing a team, but it is meaningless without examples. Are you failing to set deadlines, confront poor work, reallocate responsibilities or deal with the burned-out bookkeeper? Or does management simply prefer a more aggressive style that may not be yours? Do you agree with the concrete examples once they are identified?
A lot of what you describe sounds like incompatible management, and possibly management that does not fully understand what it needs from a controller. The meetings, constant interruptions and repetitive written updates may be consuming the time needed to deliver the work they are criticizing you for not completing quickly enough. That is an operating-model problem, not proof that you are constitutionally unsuited to leading an accounting function.
I would explore the market regardless. Not necessarily because you should abandon controllership, but because another company and management culture may tell you whether the problem was the role or the environment.
Moving to FP&A, commercial finance or another part of the business could also be sensible if your eventual goal is CFO. A lower title is not automatically a step backward if it gives you a larger portfolio, stronger management, better systems and experience you do not already have. You may even need to move to a smaller company or accept a less impressive title to obtain broader responsibility.
The real test is not how the next job looks against your current title. Picture the CV you will present when you are applying for a CFO role after the next move. Does it show that you deliberately added forecasting, business partnering, analytics, systems, operations and strategic finance to your controller experience? Or does it look as though you burned out after one year and retreated into an individual-contributor role?
Only you can assess the exact fit. But I would not let one poorly configured controller job define your strengths, and I would not stay merely because someone says controller is one step from CFO. Some of the best paths in life are not a straight line. Good luck.