A Candid Conversation Between a Business Strategist and a Technology Leader
The persistent disconnect between the C-suite and the server room
Co-authored by Andrew Bloo and Edward Fox
Edward and I no longer operate within the same organizational walls, yet our paths continue to intersect in the shared realization that we are having the same conversation in a dozen different rooms — a recurring dialogue that transcends industry lines and points to a fundamental, underlying tension inside the modern business environment.
What usually presents itself as a “technology issue” — a failed implementation, a budget overrun, a security lapse — is almost never actually about the technology itself. It is, instead, a profound crisis of orientation. While Edward spends his days aligning technical architecture with the shifting objectives of Tarkenton, I spend mine navigating the volatile interiors of growing organizations, translating the HITSLeadership™ framework into practical language for leaders who are already breathless from margin pressure and the relentless — and at times predatory — demand for speed.
From our respective seats, we have watched a weary pattern emerge: IT is marginalized as a necessary but burdensome cost center; executives feel perpetually throttled by technical constraints; and technology leaders quietly sense that their strategic value is being dismissed. This friction does not erupt immediately. It builds in the unseen corners of the organization — in budget meetings, in delayed approvals, in hallway workarounds — until eventually something structural gives way.
The View From The Leadership Seat
If I am being candid about the nature of leadership in the SMB space, most organizations still orient around technology as a subordinate support function—a utility to be managed rather than a frontier to be explored. We tend to operate on a reactive axis; when a system fails, we begrudgingly approve the spend, yet when the economic climate cools, IT is often the first lever we pull to control expenses. This behavior doesn’t stem from a disregard for innovation, but rather from the cold, binary math of survival.
In the executive suite, revenue is a visible, breathing entity that demands constant feeding, whereas technology risk remains a ghost—a hypothetical shadow that carries no weight until the moment it decides to haunt the balance sheet or the next launch.
From the leadership chair, every decision is filtered through the lens of immediate impact: payroll must be met, growth must be defended, and stakeholders expect a performance that translates into tangible value. Consequently, when a technology leader requests an investment that doesn’t clearly tie back to revenue acceleration, it is scrutinized not because it lacks technical merit, but because we are stewards of finite resources. This is the birthplace of the primary tension: the internal struggle between viewing IT as a draining cost center or a strategic enabler.
The View from the Server Room
From a technology leadership seat, scrutiny isn’t the problem. Misframed decisions are.
When investment is limited to maintaining current systems, organizations stay operational but rarely become resilient. Preventative security, infrastructure modernization, and automation do not generate headlines. Their success is measured in continuity, optionality, and avoided disruption.
But the threat landscape doesn’t operate on budget cycles.
Nearly half of breaches impact companies with fewer than 1,000 employees. The assumption that “we’re too small to be a target” isn’t careless. It is a natural bias toward visible revenue over invisible exposure.
The real issue isn’t growth versus protection. It’s whether risk and velocity are evaluated in the same decision framework.
Technology leadership’s role isn’t to slow momentum. It’s to design systems where momentum doesn’t introduce structural fragility. That requires translating technical exposure into business impact — not in theoretical terms, but in operational consequence: downtime, regulatory risk, client trust, recovery cost, lost leverage.
When those variables are framed clearly, the conversation shifts from “Can we afford this?” to “What are we choosing to carry?”
That’s a different posture entirely.
The Blind Spot of Momentum
There is a significant leadership blind spot here—one that I have personally inhabited more often than I care to admit. I have issued the executive mandate: “Make it secure, but don’t slow us down.” In my mind, I was asking for the preservation of momentum, but in the ears of the IT department, I was effectively telling them to absorb the organization’s risk in silence. This misalignment is subtle, yet it is powerful enough to erode the foundation of a company.
Sales demands a new tool today because a competitor gained a half-step of leverage; Marketing discovers a SaaS platform that promises a seamless “plug-and-play” miracle. Through the business lens, any delay feels like a surrender to stagnation. However, from the perspective of the technologist, this unchecked adoption is the precursor to a fractured architecture—a world of shadow systems, exposed data, and a chaotic lack of integration.
This is exactly where the HITSLeadership™ framework identifies the critical role of Structure. Speed without structure is phantom agility. It feels like momentum in the short term, but it’s recklessness disguised as progress — quietly compounding technical debt beneath the surface. On the other hand, structure without speed creates a seductive illusion of safety. Everything looks controlled… until the organization slowly suffocates under its own weight.
As leaders, we have to recognize that both extremes create damage. They just collect the debt on different timelines.
The View from the Server Room
Capacity is where theory meets reality.
Most SMB technology teams are small groups of generalists managing infrastructure, vendor relationships, security, user support, and forward-looking initiatives simultaneously. When everything is urgent, strategy becomes something you discuss — not something you execute.
From the outside, that can look like resistance. From the inside, it’s triage.
The solution isn’t simply adding headcount. It’s establishing decision discipline.
Not every initiative deserves equal urgency. Not every tool request should bypass architectural review. Mature organizations define risk tiers, adoption pathways, and capacity guardrails so that new growth initiatives don’t silently erode operational stability.
Without that structure, IT becomes reactive by default. With it, technology becomes a lever for intentional scale.
The gap isn’t effort. It’s operating design.
Where the Worldviews Diverge
| Topic | Executive Orientation | IT Orientation |
| Budget | Constrain overhead while funding growth | Invest proactively to reduce catastrophic exposure |
| Security | Protect without impeding velocity | Reduce risk before it escalates |
| New Tools | Move quickly for competitive leverage | Validate integration, compliance, sustainability |
| Downtime | Restore operations immediately | Plan maintenance to prevent larger failures |
Neither side is inherently wrong, but when each optimizes for their own siloed objectives, the organization itself absorbs the resulting tension. This is the specific intersection where HITSLeadership™ operates—not in the naive attempt to eliminate this tension, but in the sophisticated effort to manage it with intention.
Final Thought: Co-Ownership of Consequence
This persistent disconnect between the C-suite and the server room isn’t a matter of incompetence; it is a direct result of conflicting incentives. Executives are held accountable for the velocity of growth, while IT leaders are held accountable for the integrity of stability. Yet, growth without stability is a house built on sand that will eventually collapse, and stability without growth is a fortress that will eventually atrophy.
The companies pulling ahead are those that have stopped viewing speed and security as adversaries. Through the lens of the HITSLeadership™ framework, we see that these two forces are actually co-owners of the organization’s consequences. That shift doesn’t require immediate perfection, but it does require a different kind of courage—the courage to have a candid conversation and recalibrate your orientation before the next crisis arrives to do it for you.
About the Author
Andrew Bloo is a leadership consultant and the creator of the HITSLeadership™ framework. He works with founders, executives, and operators who are tired of reactive leadership and burnout-driven culture, helping them build clarity, steadiness, and trust through practical leadership systems. Andrew focuses on leadership under real pressure — when decisions are messy, people are human, and presence matters more than polish.
Edward Fox is Director of Technology at Tarkenton, with a background in software engineering and systems architecture. He leads technology strategy across infrastructure, security, and application development, translating business objectives into scalable technical platforms. Edward specializes in designing resilient architectures, governance frameworks, and operational disciplines that allow organizations to grow without sacrificing stability or control.