Otto Bohon on Making Better Decisions When Business Gets Complicated

Success is supposed to make running a business easier. In practice, growth often creates a new collection of problems. A founder who once made five meaningful decisions a week may suddenly face five before lunch. More employees create more opinions. More customers create competing priorities. More data creates additional questions. Leaders who built their companies by personally solving problems can eventually become the very bottleneck slowing those companies down.

Otto Bohon has experienced business from several sides of the table. He started working in his family's Tucson restaurant business at nine years old and was learning payroll by twelve. He later earned a bachelor's degree in Psychology and an MBA with concentrations in Finance and Marketing. His career has included banking, entrepreneurship, financial services, executive operations, and consulting.

Those experiences shaped an approach to decision-making that is less about having perfect answers and more about knowing what deserves attention.

"The older I've gotten, the less impressed I am by someone who can make a fast decision," Bohon says. "I'm more interested in whether they identified the right problem before making it."

More information does not always produce better decisions

Modern executives have access to an extraordinary amount of information. Dashboards can track sales, customer activity, employee performance, marketing results, and dozens of other measures.

Bohon does not believe more information automatically produces better judgment.

"You can stare at 40 metrics and still miss the one thing that's actually causing the problem," he says. "I've been in situations where everyone wanted another report, and the useful answer came from talking to the person doing the job every day."

His psychology background has influenced that approach. Numbers can show what happened, but understanding why it happened often requires talking to people.

When entering an unfamiliar operation, Bohon likes to compare what leadership believes happens with what employees say actually happens. The gap can reveal problems that reports miss.

"If three executives tell me a process works one way and the person actually doing it shows me six workarounds they use every morning, I'm paying attention to the workarounds," he says.

Knowing when a problem is actually a pattern

One bad week does not necessarily require a new strategy.

Bohon believes leaders sometimes react too quickly because visible action feels productive. A customer complaint triggers a new policy. One missed target creates another meeting. A temporary slowdown leads to a new layer of oversight.

Soon the company has accumulated solutions to problems that no longer exist.

"I've seen businesses build an entire process around one unusual event," he says. "Six months later, employees are still completing extra steps because nobody went back and asked whether the original problem was even happening anymore."

His preferred approach is to look for repetition.

If the same breakdown happens across employees, departments, or customers, the problem is more likely structural. If it happens once under unusual circumstances, changing the entire system may create more trouble than it solves.

That distinction becomes increasingly important as organizations grow.

Leaders can become their own biggest bottleneck

Founders often build businesses by becoming exceptionally good at solving problems. That ability can become a liability when the organization reaches a certain size.

Employees learn that asking the founder is faster than making a decision themselves. Managers begin escalating routine issues. Eventually, the founder spends the day approving work others should own.

Bohon believes the warning sign is simple.

"If you're answering the same question for the fifth time, answering it a sixth time isn't leadership," he says. "Something needs to be documented, delegated, or trained."

Delegation, however, requires more than handing someone a task. People need to understand the boundaries of their authority.

A manager might be allowed to resolve customer problems below a certain threshold without executive approval. A department head might control hiring within an approved budget. Teams might receive clear rules about which decisions require escalation.

The goal is not to remove leadership from decisions. It is to reserve leadership attention for decisions that actually require it.

Pressure reveals whether a system works

Some of Bohon's earliest lessons about pressure came from restaurants.

A restaurant during a rush provides immediate feedback. Orders arrive whether the team is ready or not. Customers expect consistent service. One weak handoff can affect the kitchen, servers, and guests within minutes.

"You learn quickly that the middle of a dinner rush is a terrible time to invent your process," he says. "The preparation either happened beforehand or everybody feels it."

Competitive sports and martial arts reinforced a similar lesson. Preparation creates options when circumstances change.

Business leaders cannot predict every problem, but they can establish clear responsibilities and communication before pressure arrives.

When something unexpected happens, Bohon's first instinct is to simplify rather than add complexity.

"What is the actual problem? Who owns it? What decision has to happen next? Those three questions can clear a surprising amount of noise," he says.

Disagreement is useful when the rules are clear

Experienced executives will not always agree.

Bohon sees disagreement as useful when everyone understands how the final decision will be made. Problems begin when organizations confuse collaboration with unanimous consent.

A leader should hear competing arguments, identify the assumptions behind them, and decide who ultimately owns the call.

"I want someone in the room who disagrees with me," he says. "What I don't want is a decision getting reopened every three days because somebody didn't like the answer."

That requires a culture where challenging an idea is different from challenging someone's authority.

Leaders also need enough self-awareness to recognize when ego has entered the conversation.

Bohon uses a simple test: would he make the same decision if someone else had originally suggested it?

"If the answer changes because my name isn't attached to the idea, that's a problem," he says.

Good leaders know when to leave things alone

Consultants are often expected to arrive and immediately change things. Bohon takes a different view.

When entering an established organization, he first wants to understand why existing processes developed.

Some procedures may look inefficient but exist for a valid reason. Experienced employees may know constraints that are invisible from the executive level.

"I never want to walk in on Monday and start mo ving furniture because I was hired to improve something," he says. "First I want to know why the furniture is where it is."

That patience does not mean avoiding change. It means understanding the cost and purpose of change before introducing it.

The same principle applies to technology. New software can improve a strong process, but it cannot rescue a process nobody understands.

A bad outcome does not always mean a bad decision

One of the harder lessons in leadership is separating decision quality from outcome quality.

A thoughtful decision can produce a poor result because circumstances change. A reckless decision can occasionally produce a great result through luck.

Bohon believes leaders should review what they knew when they made the decision rather than judging themselves entirely with hindsight.

"Ask whether you used the information available, challenged your assumptions, and understood the downside," he says. "If you did those things and the result still went against you, learn from it. Don't rewrite history and pretend you should have known something nobody knew."

That mindset makes it easier to admit mistakes without fearing the next decision.

The three questions leaders should ask

For executives facing an important decision, Bohon returns to three questions.

First, what problem are we actually solving?

Second, who should own the decision?

Third, what happens if we are wrong?

The questions are simple because the job is not to make decision-making look sophisticated. The job is to make good decisions repeatable.

That may be the larger lesson from Bohon's path through restaurants, banking, entrepreneurship, and operations. Experience does not give leaders perfect instincts. It gives them a better process for questioning those instincts.

"Confidence isn't believing you're always right," he says. "For me, it's knowing I can make the best decision with what I have, own the result, and change course when the facts tell me I should."

As companies become larger, that distinction matters. The leader who insists on having every answer eventually limits the organization to what one person can know.

The leader who builds good judgment throughout the company creates something far more scalable: a team that knows how to think when the answer is not obvious.