Technology Insights
Total Applications publishes technology insights for technology leaders who need clarity, not consultancy jargon. Every article is written from a practitioner perspective, drawing on direct experience across technology ROI, AI governance, enterprise architecture, AEM, cybersecurity, data strategy, legacy modernisation, operating model design, transformation assurance, and business case development.
The technology insights library covers the decisions that matter most: how to build a technology ROI measurement plan that survives go-live, how to govern AI adoption across the enterprise, when to build versus buy, how to structure an API governance framework, and how to write a technology business case that a board will actually approve.
Use the category filters below to find technology insights relevant to your current challenge. New articles are added regularly across all topic areas.
Featured
Architecture Without Bureaucracy: How to Set Technology Standards That Teams Will Actually Follow
Architecture governance fails in two opposite ways. There can be too much of it, or too little. Too much governance creates friction. Teams prepare presentations for review boards,...
All articles
From Projects to Platforms: The Operating Model That Makes Technology Investments Compound
The project model of technology investment has a structural weakness: it is designed around completion. A project has a start...
The Cloud Cost Illusion: Why Moving to the Cloud Does Not Automatically Save Money
The Cloud Cost Illusion: Why Moving to the Cloud Does Not Automatically Save MoneyThe business case said that moving to...
The Technology Portfolio Trap: Why More Systems Create Less Business Value
The Technology Portfolio Trap: Why More Systems Create Less Business ValueOPENING (Hook + Problem Statement) Most technology leaders believe more...
How to write a technology business case the board will actually approve
A technology business case that fails board approval usually fails for one of three reasons: it speaks technology rather than...
The platform team model is not right for every organisation
Team Topologies popularised the platform team model as a solution to the coordination problems that emerge in large technology organisations....
Why programme boards receive the wrong information about delivery risk
The escalation problem in large technology programmes is well documented. Boards discover that a programme is in serious difficulty months...
Strangler fig is a sequencing principle, not a migration strategy
The strangler fig pattern describes a way of incrementally replacing a legacy system by routing functionality to a new system...
AEM headless delivery: when GraphQL is the right answer and when it is not
AEM headless delivery via GraphQL has become the default recommendation for many new AEM implementations. It offers genuine advantages: channel...
Content Fragments in AEM: separating content from presentation properly
Content Fragments are one of the most important architectural decisions in a modern AEM implementation. They determine how content is...
AEM as a Cloud Service migration: what changes and what to plan for
AEM as a Cloud Service is not simply AEM 6.5 hosted in the cloud. It is a different architecture, a...
How technical debt creates security exposure your CISO cannot see
Security assessments look at the current state of a system: its configuration, its access controls, its patch level, its dependencies....
Zero trust architecture is not a product you can buy
Zero trust has been absorbed by the security vendor market so thoroughly that it is now possible to buy a...
No articles in this category yet.