MORE TECHNOLOGY. BUT LESS DIRECTION?
Technology expands possibility. Leadership creates consequence.
Over the years, I have seen organisations invest in cloud platforms, automation, analytics, cybersecurity, IIoT and AI—often simultaneously.
Each investment may be technically justified. Each initiative may have a capable team. Each project may even deliver its intended output.
Yet, collectively, they do not always move the organisation forward.
Why?
Because more technology does not automatically create more direction.
Sometimes, it creates:
This is where technology leadership becomes fundamentally different from technology management.
Technology management asks:
“Can we implement it?”
Technology leadership asks:
“Should we implement it—and what business direction will it strengthen?”
Technology creates options. Leaders make choices.
Today, almost every business problem has multiple technology options.
A manufacturing organisation looking to improve quality may consider machine vision, advanced analytics, digital work instructions, traceability, process automation or AI-assisted root-cause analysis.
All may be valuable.
But implementing all of them at once is not a strategy.
The leadership responsibility is to determine:
The difficult part is rarely discovering another technology.
The difficult part is making a deliberate choice.
The leadership filter
Before approving a technology initiative, leaders should filter it through five practical questions.
1. What business problem are we solving?
“Implement AI” is not a business problem.
“Reduce inspection escapes,” “improve schedule adherence,” “lower unplanned downtime,” or “shorten engineering-change response time” are business problems.
Technology should enter the discussion after the operational problem and expected outcome are clear.
2. Is the foundation ready?
Many transformation initiatives begin with the visible layer—the dashboard, application, analytics model or AI interface.
But the real constraints often sit underneath:
A sophisticated solution built on an unstable foundation does not remove complexity. It hides it temporarily.
3. Can it scale beyond the pilot?
A successful pilot proves that something can work under controlled conditions.
It does not automatically prove that it can survive:
The distance between a pilot and an enterprise capability is primarily a leadership and operating-model challenge—not just a technical challenge.
4. What will we stop doing?
Every new platform introduces cost, ownership, skills, integrations and long-term support obligations.
Yet transformation discussions frequently focus only on what will be added.
Leadership must also decide:
If nothing is removed, transformation may simply become an additional layer of work.
Recommended by LinkedIn
5. Who owns the outcome?
Technology teams can deliver platforms and capabilities.
But business value is created only when operational teams use those capabilities to change decisions, behaviours and processes.
Ownership must extend beyond implementation.
Someone must be accountable for:
Without clear ownership, a technically successful project can still become an operationally irrelevant one.
Clarity. Priority. Action.
Effective technology leadership should produce three visible outcomes.
Clarity
People understand the problem, the intended value and how the initiative supports the broader business direction.
Priority
Teams know what must happen first, what can wait and what should not proceed.
Action
Decisions translate into governed execution, measurable outcomes and operational adoption.
These outcomes sound simple. In practice, they require leaders to resist technology noise, challenge fashionable assumptions and make choices that may not please every stakeholder.
That is the real work of leadership.
A manufacturing reality
In manufacturing, this discipline is particularly important.
Factories operate through interconnected systems, equipment, people, processes and constraints. A change made in one area can affect production, quality, maintenance, logistics, safety, cybersecurity and compliance.
For example, predictive maintenance is not only an analytics initiative.
It may require:
Without these elements, the organisation may produce a prediction without improving maintenance performance.
The model may work—but the operating system around it may not.
This pattern applies equally to AI inspection, digital work instructions, digital twins, connected-worker platforms and manufacturing intelligence.
Technology becomes valuable only when it changes a real operational decision.
Leadership is not anti-technology
Questioning an investment does not mean resisting innovation.
It means protecting innovation from fragmentation, weak foundations and unclear ownership.
Strong technology leaders are not those who approve the most projects or adopt every emerging platform.
They are the ones who can distinguish among:
They understand that saying “not yet” can sometimes protect a valuable idea until the organisation is ready to scale it properly.
The final perspective
Technology will continue to expand what organisations can do.
Cloud, data, automation, AI and connected operations will create possibilities faster than most organisations can absorb them.
The competitive advantage will not come from accessing these technologies. Access is becoming increasingly common.
The advantage will come from leadership judgement:
Choosing what matters. Establishing what comes first. Connecting technology to operations. Scaling what creates value. Stopping what creates only activity.
More technology is not always the answer.
Sometimes, the organisation needs something more fundamental:
Direction.
Thank you
Technology abundance makes prioritization more important, not less. A portfolio full of pilots does not create transformation if leadership cannot decide which problems deserve sustained investment.
technology without a clear vision often leads to fragmentation. in my experience, success comes from aligning initiatives with business outcomes, but that’s where most leaders falter. how do you recommend prioritizing amidst the noise?
I've seen exactly this pattern — teams with access to every tool but unclear on which direction to move. The diagram captures it well: the tools multiply the noise unless someone is making judgement calls about what actually matters. More technology without sharper direction just accelerates confusion.
Leadership can prioritize the right problem and still make the wrong technology decision when the factory reality reaching the leadership team is incomplete. A downtime number without the actual reason, production context or downstream impact can make a minor issue look strategic and a recurring loss look normal. Good technology decisions need good operational truth underneath them.