When I started in consulting, I had no idea what to expect. I thought I would be working on complex problems that required equally arcane answers: a spreadsheet that needed an entire data room, or a slide deck with enough arrows to qualify as modern art. Ten years later, I have a different view. Simplicity usually wins.
Even very large, very capable, very organized teams do not automatically come up with one clean framework for resolving problems. Markets move. Policies evolve. Systems get patched together. And when things are going well, M&A can change the reality on the ground all over again. Progress often depends on a few key leaders carrying the company forward, one decision at a time.
In strategy work, the most effective leaders are not just the people with the sharpest answer. They listen actively, summarize well, and frame a view that helps different stakeholders see how their pieces fit together. They understand that people across an organization can talk past each other even when they are all trying to solve the same problem.
That has been especially true in finance. Teams in Treasury, Accounting, FP&A, Operations, and leadership do not necessarily disagree as often as it first appears. They may be describing connected facts with different vocabulary, different time horizons, and different definitions of what “the right choice” should be.
This is where good advisors become translators. Treasury may care about cash timing and liquidity. Accounting may care about reconciliation, controls, and accuracy. Financial leadership may be trying to understand risk, performance, and which decisions are available now. All of those perspectives can be correct. The challenge is figuring out which facts materially affect the decision in front of you and which ones are concerns for another day.
A cash forecasting project made this lesson very concrete for me. The systems were messy, and getting reliable data took work, but the bigger issue was the conversation around the data. Revenue recognition mattered a lot for Accounting. Cash timing mattered a lot for Treasury. Leadership needed to know what could be decided with confidence. The breakthrough was not treating one perspective as right and the others as noise. It was creating shared language around the actual decision.
The first move for many CEOs or CFOs facing complex problems is to bring leaders together. That can work, but only if there is structure. Blending every concern into one giant list is a recipe for frustration. Everyone may be making a reasonable point, but that alone is not progress.
The most practical move I have found is to make concerns visible and shareable. A pain point, opportunity, or recommendation should fit into a few sentences at most. If you cannot explain a topic in a paragraph or less, you probably do not understand it well enough yet.
That constraint is surprisingly useful. It forces the team to separate the important objectives from the merely related facts. It also gives people language they can reuse with each other, which is often the moment the problem starts to feel less mysterious. A little light turns on once the common language is set.
Whenever I walk into a cross-functional problem now, I try not to arrive only from my own expert perspective. I definitely do not try to solve every detail on day one. Defining solution objectives, learning what each group is trying to accomplish, and then building the strategy from shared understanding works best.
You can make the recipe once you have the ingredients. Before then, you are mostly guessing what everyone wants for dinner.