The Founder

Structure, Sequence, and the Long View

Telstar Digital takes its name from one of the first enterprise systems I worked on.

It was a Data General MV/60000 mainframe, known internally as “Telstar.”

It was not elegant. It was not modern. It did not present itself as transformative. It simply carried operational weight without drama. Finance ran through it. Logistics ran through it. Reporting ran through it. When it failed, consequences were immediate and visible.

That experience shaped how I think about technology.

Systems are not decorative.
They are structural.
And structure determines consequence.

Birmingham Beginnings

Born into a working class family and growing up in Birmingham, I can be described as a proud ‘Brummie’ with a down to earth and pragmatic approach to most things. My state comprehensive education in a school that wouldn’t be described as academically stable helped me achieve the required qualifications to attend college and leave with a B-TEC National Diploma in Business & Finance. Something I was very proud of at the time but my time at college also made me realise that further formal education wasn’t for me as my curiosity and desire to pursue a practical application of my skills was more desirable.

That instinct to leave formal education was, I think, the right one. My curiosity and the desire to apply my skills in practice has never left.

Entering Enterprise IT

A government-funded COBOL programming course gave me a professional foothold. I became a Data General mainframe operator and later moved into IBM AIX environments, SP/2 clusters, and SAP R/3 3.0A–D implementations during the shift from centralised platforms to distributed ERP estates.

This period was formative.

It was the era when organisations were “modernising” from mainframe to client/server. The narrative was progress. The reality was complexity.

I saw firsthand what happens when systems are replaced before structure is understood. Data models drift. Processes compensate. Integration logic multiplies. Controls are bolted on later.

It was the first time I recognised a pattern that would repeat for decades.

Ambiguity does not scale.
Workarounds compound.
Technology amplifies structure — good or bad.

Engineering With Longevity in Mind

I went deep technically — IBM AIX Advanced Technical Expert, SAP Basis certified, PRINCE2, ITIL, SuSE Linux engineering — not to collect credentials, but to understand the entire stack.

In a FTSE100 organisation, I replaced incumbent proprietary routing and authentication systems with open technologies including FreeRADIUS, OpenLDAP, DRBD, BIND9 and DHCP. These were not fashionable moves at the time. They were structural ones.

Some of that engineering remains operational more than twenty years later.

That longevity matters to me.

If something you designed is still running two decades on, it suggests the architecture aligned with operational reality rather than vendor narrative.

Introducing Linux Into Government

Later, I introduced Linux as the first new operating system in twenty-five years into the UK’s largest central government authority.

This was not about open-source ideology. It was about structural flexibility.

During that work, I identified a need that was not yet widely articulated — a governed build environment capable of supporting heterogeneous estates across AIX, VMware and Linux. I described it at the time as a “Heterogeneous Build Environment.” Today it would be recognised as an early private cloud model.

I led a team of senior solution architects, each responsible for teams of engineers, to design and implement this environment across technical, operational and commercial dimensions.

The success was not the technology itself.

It was the alignment.

Capabilities, infrastructure, integration and controls were shaped deliberately together rather than layered sequentially in reaction to pressure.

That lesson stayed with me.

Sequence matters more than speed.

Enterprise Architecture at Global Scale

My move into consulting broadened perspective from engineering execution to enterprise transformation.

At EMC, later Dell Technologies, I built and led Enterprise Architecture capabilities across EMEA. I worked with global organisations including BP, Shell, GSK, AstraZeneca, Barclays, RBS and Maersk on large-scale modernisation and transformation initiatives.

This period included:

• Application modernisation strategy
• Portfolio rationalisation using early “4R” concepts (Retire, Rebuild, Replatform, Re-engineer)
• Value chain–aligned business capability modelling
• Joint go-to-market propositions with Tier-1 advisory firms including EY, Deloitte, KPMG, Accenture and Capgemini

I formalised my architectural practice through TOGAF-aligned disciplines and integrated systems thinking approaches including Wardley Mapping and Cynefin.

Alongside technical architecture, I completed executive leadership development at IMD, deepening my understanding of enterprise economics, governance structures and board-level decision environments.

The cumulative insight was clear.

Technology decisions are rarely technical.
They are organisational, economic and behavioural.

A Personal Interruption and a Sharpened Lens

During this period, I was diagnosed with a rare G.I.S.T cancer and required nine months away from work.

Time away clarifies perspective.

Speed feels impressive in the moment.
Endurance proves its value over time.

Returning to enterprise architecture after that interruption, I found myself less interested in acceleration narratives and more focused on structural coherence. I had seen enough transformation cycles to recognise the cost of mis-sequencing.

Large enterprises can absorb architectural drift for years.

Mid-sized organisations cannot.

Vendor Insight and Structural Independence

I have operated inside global vendor environments, shaping strategy and go-to-market propositions. I understand how incentive structures operate. I understand how platform gravity subtly reshapes architectural intent.

No one is acting maliciously. Vendors optimise for growth. Advisory firms optimise for billable delivery. Executives optimise for visible progress.

But incentives matter.

In more than one strategy session, I saw architecture decisions being shaped before diagnosis had occurred. Roadmaps preceded reality mapping. Tool selection preceded capability definition.

In large organisations, that risk can be amortised.

In a £40m or £75m organisation, it is felt quickly — in integration fragility, in subscription cost growth, in automation layered onto ambiguity, in fatigue across operational teams.

Telstar Digital exists outside those incentive structures.

Independence is not ideological rejection of vendors. It is structural neutrality at the beginning of the conversation.

When you are not rewarded for deployment volume, you can pause.
When you are not tied to an ecosystem, you can diagnose honestly.
When you are not defending a roadmap, you can question sequence.

That difference is material for mid-market leaders.

Why Focus on £5–100m Organisations

Mid-sized organisations operate in a constrained equilibrium.

They have:

• Complex operational footprints
• Multiple legacy systems
• Growing automation pressure
• Limited specialist architectural depth
• Tight financial tolerance for rework

In this environment, fragmentation compounds quickly.

Fragmented systems create reconciliation work.
Data ambiguity undermines reporting.
Integration fragility slows change.
Automation amplifies inconsistency.
Controls become reactive rather than embedded.
Costs rise without simplification.

These are not technical failures. They are sequencing failures.

Telstar Digital exists to introduce structural clarity before capital is committed.

The Telstar Principle

The original “Telstar” mainframe endured because it was designed around operational necessity. Dependencies were visible. Ownership was clear. Integration was deliberate. Controls were embedded because failure was unacceptable.

Modern estates are more abstract. Infrastructure is virtual. SaaS abstracts capability. Automation abstracts execution.

But the principle remains.

Every organisation operates across interconnected structural domains:

• Capabilities
• Processes
• Data
• Systems
• Integrations
• Automation
• Controls

Optimising one pillar in isolation creates tension in the others. Ignoring interdependence produces cost and fragility.

Mapping those pillars coherently before design decisions are made creates optionality.

Optionality compounds.

Dependency compounds faster.

What I Believe

Across three decades — from mainframe operator to enterprise architect to advisory leader — the pattern has been consistent.

Diagnosis precedes safe acceleration.
Architecture is economic discipline, not documentation.
Automation amplifies structure.
Integration maturity reveals organisational maturity.
Vendor independence begins with owning your structural logic.
Craft still matters in a low-code world.
Integrity in technology leadership is a commercial advantage.

These beliefs are cumulative, not theoretical.

A Long View

When I stood in front of that Data General “Telstar” system as a young operator, I did not imagine building enterprise architecture practices or advising boards on technology risk.

I was simply trying to understand how the machine worked.

The hardware was physical. Cables were visible. Dependencies were tangible. When something failed, cause and effect were traceable.

Today, abstraction hides complexity more effectively. Dashboards mask fragility. Automation obscures process weakness. Cloud elasticity disguises cost drift.

But structure still determines outcome.

You can defer it.
You can disguise it.
You cannot escape it.

Telstar Digital exists because I have seen that reality repeat across decades, industries and organisational scales.

From Birmingham to mainframes.
From open systems to private cloud.
From government transformation to global enterprise architecture.

The consistent lesson is simple.

Build for endurance.
Sequence deliberately.
Respect interdependence.
Tell the truth about structural reality before changing it.

Technology will continue to evolve. Incentives will continue to reward speed.

Organisations that endure are those that take the long view.

That is what Telstar represents.

And that is the work.