When people hear the word “operations,” they often think about production schedules, logistics, or the processes that keep a business moving behind the scenes. Those things are certainly part of it, but I’ve come to believe that operational thinking is much broader than that.
To me, operational thinking is a way of approaching decisions. It means looking beyond the immediate problem and asking what happens next. It means understanding how one decision affects another department, another team, or another customer. Most importantly, it means recognizing that a good decision isn’t always the one that produces the fastest result. Sometimes it’s the one that creates the fewest problems six months from now.
I’ve spent my career working in pipeline operations, manufacturing, international sourcing, and sales. Those experiences have given me a front-row seat to how businesses actually function when plans meet reality. They’ve also changed the way I think about decision-making. Today, I rarely look at an issue in isolation because I’ve seen too many situations where solving one problem simply created another somewhere else.
Every Decision Has a Ripple Effect
One of the biggest lessons operations taught me is that almost nothing happens in isolation.
A sourcing decision affects manufacturing. Manufacturing affects delivery schedules. Delivery schedules influence customer relationships. Sales teams are often left explaining delays that started weeks earlier in an entirely different department.
Early in my career, I don’t think I fully appreciated how connected everything was. Like most people, I focused on the task directly in front of me. If my part of the project was moving forward, I assumed everything else would fall into place.
It didn’t take long to realize that businesses don’t work that way.
I’ve found that the strongest decisions come from stepping back and asking a simple question before moving forward: Who else will this affect? Sometimes the answer changes the decision entirely. Other times, it confirms we’re on the right path. Either way, it’s a question worth asking.
Solving Today’s Problem Isn’t Always Enough
There have been plenty of situations where the quickest solution looked like the obvious one.
A supplier issue needed immediate attention. A deadline was approaching. Customers were waiting. The pressure to act was real.
Those moments taught me that urgency can sometimes cloud judgment. It’s easy to solve the immediate issue without considering what happens after that.
I’ve learned to pause long enough to ask whether we’re fixing the problem or simply postponing it. That isn’t always easy when people want quick answers, and I certainly haven’t gotten it right every time. Still, I’ve found that taking a little more time upfront often prevents much larger problems later.
Operational thinking doesn’t ignore short-term needs. It simply tries to balance them with long-term consequences.
The Best Decisions Usually Involve Listening
One observation that has stayed with me throughout my career is that the people closest to the work often see problems long before leadership does.
I’ve learned a great deal from conversations with operators, warehouse teams, suppliers, production staff, and colleagues who deal with processes every day. They often notice inefficiencies that don’t appear in reports or performance metrics because they’re experiencing them firsthand.
Early on, I probably relied too heavily on data alone. Data is important, but it rarely tells the complete story.
I’ve become much more interested in asking people what they’re seeing, what keeps slowing them down, and what they would change if they could. Those conversations have led to improvements that no spreadsheet would have identified on its own.
Experience has taught me that good decisions are often built from good conversations.
Every Improvement Comes With a Cost
One thing I appreciate about operations is that it forces you to think about tradeoffs.
Every improvement requires something. It may require more time, additional resources, or changes to established routines. Sometimes improving one process creates extra work somewhere else.
That doesn’t mean improvements shouldn’t happen. It simply means they deserve careful thought.
I’ve become cautious whenever someone describes a solution as a “win-win” with no downside. In my experience, every meaningful decision involves compromise. The real question is whether the long-term benefits justify the short-term cost.
I think businesses make better decisions when they’re honest about those tradeoffs instead of pretending they don’t exist.
Experience Changes the Questions You Ask
One thing I’ve noticed over the years is that experience doesn’t necessarily give you faster answers. Instead, it gives you better questions.
Earlier in my career, I wanted to know whether something could be done.
Now I’m more likely to ask whether it should be done.
Will this make the process more reliable?
Will it improve communication?
Will it help people work together more effectively?
Will it still make sense a year from now?
Those questions don’t eliminate uncertainty, but they usually lead to better discussions.
I’ve also become more comfortable admitting when I don’t know the answer. That probably would have bothered me years ago. Today, I see it differently. If a decision affects multiple parts of the business, I would rather gather different perspectives than assume I already have the complete picture.
Relationships Are Part of the Process
Operations often gets described as systems, workflows, and procedures. Those elements matter, but I’ve found that relationships matter just as much.
Processes don’t solve problems by themselves. People do.
I’ve seen strong supplier relationships keep projects on track during difficult circumstances. I’ve watched internal teams overcome unexpected setbacks because they trusted each other enough to communicate openly instead of assigning blame.
The opposite is true as well. Even well-designed processes struggle when communication breaks down.
That has reinforced something I’ve come to believe over the years. Operational excellence isn’t just about efficiency. It’s also about building relationships that allow people to solve problems together.
Looking Beyond the Immediate Result
If there’s one thing operational thinking has changed for me, it’s the time horizon I use when evaluating decisions.
It’s easy to celebrate a quick success. It’s harder to ask whether that decision will still look like the right one six months from now.
I’ve learned that sustainable progress usually comes from making thoughtful decisions consistently rather than chasing quick wins. That approach may not always be the fastest, but it tends to create fewer surprises and stronger outcomes over time.
Looking back across the industries I’ve worked in, I don’t think the best organizations were defined by having perfect systems or flawless execution. They stood out because they developed a habit of thinking beyond the immediate task. They understood how decisions connected across departments, they listened to the people doing the work, and they were willing to improve processes instead of simply reacting to problems.
That’s what operational thinking means to me now. It isn’t confined to one department or one role. It’s a way of approaching business with a broader perspective, knowing that today’s decisions shape tomorrow’s results.