Writing · Connected products and strategy

When a company has no strategy

Strategic deficit shows up as a cluster of symptoms, and engineering often feels it before anyone names it.

I have been called into enough high-tech product companies, as a consultant and as an incoming leader, to recognise strategic deficit quickly. The tell is rarely one thing. It is a cluster. Ask senior leaders to describe the differentiation strategy and the answers differ from person to person. Look at recent major decisions and they trace back to competitor moves rather than internal intent. The roadmap is a list of incremental improvements, with nothing on it that would change the company's competitive position in three years.

The visible symptom is a business that looks directionless: reactive rather than proactive, profitable in some quarters and fragile in others. Strategic deficit is the underlying condition. In a connected-product company its cost is often higher than it first appears, because strategic drift gets built into long-lived things: product variants nobody really chose, supplier commitments made for markets that were never properly prioritised, and field-service obligations attached to products whose commercial case was already weak by the time they shipped.


What it looks like

A few patterns appear consistently across the companies I have worked with in this condition.

Decisions follow competitors. Decisions respond to whatever a competitor just did, rather than to internal strategic intent. The company is always responding, never initiating.

Leaders describe the direction differently. Direction, priorities and values change depending on who in the leadership team is speaking. That shows the strategy has never been properly shared or genuinely agreed, even if a document exists somewhere.

Cost discipline has become the strategy. Cost matters. But when cutting costs is the main mechanism for improving performance, the company is eating the future to fund the present. The capability investments that would generate the next phase of growth are the first to go.

Direction changes without clear justification. The whole organisation learns to wait for the next pivot rather than commit to the current one. Effort and morale are both diluted.

Customer feedback goes nowhere. It exists, but it does not reliably reach product development. The market is sending signals. The company is not receiving them.


What it costs

The competitive damage is cumulative and slow, which is part of what makes strategic deficit hard to address. Products stop differentiating, and customers drift towards competitors that appear more innovative. Engineering time and capital go into the wrong things while the highest-return areas stay underfunded. When the market moves, as it always does, the company cannot move with it because no strategic flexibility has been built in.

The cultural damage is often worse. Without a shared direction, departments work towards their own local objectives and the sense of common purpose erodes. The best people, who have the most options, are often the first to notice and the first to leave.


Closing the deficit

Diagnosis comes first: understand what the company is actually for, what it offers that competitors do not, and where it sits in the market. This is not a slogan-writing exercise. A vision needs to be specific enough to guide an actual decision. So does a mission.

Next, translate that into a strategy with clear priorities, measurable goals, allocated resources and a regular review cycle that adjusts to market feedback rather than ignoring it. The process needs to engage the whole leadership team, not just the people who write the document. Without genuine buy-in across the team, the plan stays on paper.

The most important leadership shift is treating strategy as the primary work, not an overhead that competes with delivery. In my experience, the companies that climb out of strategic deficit are almost always those whose leadership team made that decision consciously, at a specific point, and held to it. A high-tech business with a real strategic deficit can recover. It does require the leadership team to decide that the climb is the work, not an interruption to it.


The technical dimension

Strategic deficit has a specific technical expression worth naming separately. Without clear commercial direction, the engineering team defaults to what it knows: technically interesting problems, architectural improvements, features the team finds satisfying to build. None of these is wrong in isolation. Together, without a strategic filter, they produce a roadmap that is technically coherent and commercially directionless.

The CTO in a strategically deficient organisation is often in an uncomfortable position. They have a capable team delivering real work, and the work feels productive because it is technically sound. But the distance between what is being built and what the market actually needs is growing quietly in the background. The engineering metrics look healthy. The commercial metrics are not moving.

Diagnosing this requires the CTO to ask a question that cuts against the grain of technical culture: not "is this well built?" but "is this the right thing to build?" They are different questions with different answers, and the second needs a strategic context to answer. In a company with genuine strategic deficit, that context is either absent or contested. The CTO who names the gap between technical output and commercial direction as a strategic problem, not a prioritisation dispute, is doing work that nobody else in the organisation is positioned to do.


Four things worth taking seriously

For boards: ask senior leaders separately to describe the company's differentiation. If the answers differ, the strategy has not been agreed, whatever the document says.

For leadership teams: treat strategy as the primary work, not an overhead competing with delivery. Make that decision consciously, at a specific point, and hold to it.

For CTOs: healthy engineering metrics alongside flat commercial ones are a warning. Ask whether the team is building the right thing, not only whether it is well built.

For anyone reviewing a roadmap: look for one item that would change the company's competitive position in three years. If there is none, the roadmap is a list of improvements, not a strategy.


Which of these patterns would someone new to your organisation spot in their first month, and who in your leadership team would be first to say so?

© 2024 Catherine Ives-Yim. All rights reserved.

Catherine Ives-Yim

Catherine Ives-Yim

Chartered Engineer and independent technical adviser, with a lifetime at the bleeding edge of embedded systems, connected products, data platforms and AI-assisted engineering, who has advised clients across the UK, Europe, the Middle East, the Far East, North America and Africa. Based in Leeds.