What determines whether technology creates measurable business value?
It is rarely the technology alone. Most organisations have access to similar cloud platforms, applications, data tools, automation capabilities, and artificial intelligence. The real difference is the organisation’s ability to turn those possibilities into business capability, adoption, operational performance and continuous renewal.
This is why business technology has become a leadership capability. Technology is no longer only a support function, delivery organisation, or cost centre. It is embedded in products, services, customer journeys, business processes, data flows, decisions, operations and ecosystems. The question for leaders is no longer whether technology matters. The question is whether the organisation has the capabilities to use technology deliberately, repeatedly and responsibly to create value.
The Business Technology Standard, (BT Standard or BTS in short), provides an integrated operating model for this challenge. It helps business and technology work as one value creation system. BTS connects the five business technology disciplines (demand, strategy and governance, service governance, development, service delivery, data and AI) and the related capabilities into a shared way of working.
BT Standard is not intended to replace specialist practices. Agile development, service management, architecture, security, sourcing, data governance, and portfolio management all remain important. BTS provides the common frame that makes these practices work together towards business outcomes.
The central idea is simple: value creation must be managed end-to-end. Value does not begin when development starts. It begins with the enterprise mission, vision and business strategy. It ends with the operational delivery of value to meet the strategy. It never stands still, as review of service performance, the environment and unmet strategic needs lead into continuous improvement and change.
Leadership reflection:
In your organisation, is technology success mainly measured by delivery activity, or by realised business outcomes?
The Business Technology Standard (BT Standard) is based on a business technology mindset. In this mindset, business and technology are not two separate domains connected by requests and handovers. They are two perspectives of the same value creation system.
In the traditional model, business defines needs and technology delivers solutions. This model can work when change is slow, solutions are well understood, and dependencies are limited. It becomes much weaker when business models, platforms, data, ecosystems and AI-enabled capabilities evolve continuously. In that environment, business and technology must shape each other from the beginning.
BT Standard provides an operating model for this collaboration. It connects business design, demand planning, development, service lifecycle management, service delivery, and business value realisation. It also provides the governance, roles, capabilities, and management structures needed to keep this collaboration coherent.
The purpose of BTS is not only to deliver faster. Speed matters, but speed without direction creates waste. Control matters, but control without flow creates delay. BTS aims to combine time-to-value, minimum viable governance, end-to-end accountability and continuous value realisation.
This balance is especially important in the AI era. AI can accelerate planning, development, analysis, service operations and support. It can also increase complexity, blur accountability, and create new forms of operational and data risk. Organisations need an operating model that enables fast learning and automation while keeping ownership, governance, trust and operational readiness clear.
BTS provides that shared operating model. It helps leaders ask better questions: What value are we trying to create? Which capabilities must change? Who owns the outcome? How do we prioritise work? How do we ensure adoption? How do we operate the service reliably? How do data and AI strengthen value without weakening accountability?
This BT Standard Capability Book explains what an organisation must be able to do consistently to create value with business technology.
A capability is more than a process. It combines practices, roles, decision rights, information, tools, competences and governance into an organisational ability. When a capability is strong, the organisation can perform an important activity repeatedly and reliably, even as people, technologies, and business priorities change.
This book presents the BTS capability view through six disciplines: demand, strategy and governance, service governance, development, service delivery and data and AI. These disciplines describe how business technology is directed, planned, governed, developed, operated, improved and renewed.
The disciplines should not be read as separate management silos. Together, they form one connected operating model. Demand shapes what the organisation needs to change. Strategy and governance provide direction and control. Service governance manages services and ecosystems across their lifecycle. Development turns business intent into working capability. Service delivery makes value dependable in daily use. Data and AI ensure that information and intelligent capabilities are governed as business assets.
This book is intended for leaders and practitioners who need a shared language for business technology. It supports executive discussions, operating model design, capability assessments, role clarification, governance development and improvement planning. It is relevant for business leaders, technology leaders, service owners, data and AI leaders, portfolio leaders, development leaders and governance roles.
Rather than describing every implementation detail, the book aims to make the capability landscape visible, understandable and actionable.
Leadership reflection:
Which capability most limits your organisation’s time-to-value today: shaping demand, making decisions, developing solutions, adopting change, operating services, or using data and AI responsibly?
The Value Creation Model explains how value moves from business need to realised outcome.
The Role Identity Model shows how people, roles and professional identities bring the operating model to life.
The Operations Canvas shows the operational backbone that is often hidden behind value creation and governance views, yet is essential for dependable value delivery.
Together, these pictures give four complementary views of the same operating model: the capability view, the flow view, the people view, and the operational reality view.
The Business Technology Capability Model is the central picture of this capability book. It is the master map for understanding the BTS capability landscape.
The model shows the six disciplines and the capabilities that make business technology value creation repeatable. It should not be read as an organisation chart. The coloured rows are not departments. They are connected capability areas that must work together across the organisation.
The model helps leaders see whether business technology is managed as a coherent whole or as a collection of separate activities. Many organisations already have demand management, architecture, development, service operations, sourcing, data governance and security capabilities. The challenge is often how these capabilities work together. The capability model makes these connections visible.
Demand creates the front end of value creation. It ensures that business capability development and technology solution development shape each other from the beginning. Business needs must be understood in the context of architecture, services, data, AI, continuity, portfolio capacity and operational reality. Technology possibilities must be evaluated through business value, operating model impact and service use. Demand planning determines what needs to change and why, while demand management organises approved demand into executable development work without losing business intent.
Strategy and governance give direction and control to business technology. This discipline ensures that business technology is managed as one capability rather than as separate initiatives, technologies or control activities. The discipline translates business ambition into governance, architecture, operating model practices, risk management, security and data protection. Its role is to enable speed and flow while reducing fragmentation, duplicated investment and unnecessary risk.
Service governance manages the lifecycle of services and ecosystems. Modern organisations increasingly depend on suppliers, cloud platforms, digital services, data ecosystems and AI-enabled capabilities. Service governance keeps services, sourcing, contracts, finances, resources and lifecycle decisions aligned with business objectives and operational needs. This enables services to remain valuable, sustainable and able to evolve over time.
Development transforms business intent into operational business capability and measurable business value. Development is a business capability as much as a delivery capability. It brings together business ownership, operational understanding, technology capability, data, partners and governance to create solutions that work in real business environments. It covers the flow from requirements and feasibility to prioritisation, design, development, validation, rollout, training and business value realisation.
Service delivery turns service commitments into operational reality. It focuses on reliable operations, service integration, operational readiness, automation, support and continual improvement. Its purpose extends beyond keeping services running. It ensures that services deliver value in daily operations and continue to adapt as business and operational needs change.
Data and AI ensure that information and intelligent capabilities are managed as business assets. Data becomes valuable when ownership, structure, quality and use are actively managed. AI increases both the opportunities and the need for governance because AI-enabled capabilities increasingly influence decisions, operations, services and customer interactions.
The capability model is therefore neither an organisation chart nor a process map. It describes the organisational capabilities required to create business value through technology. Each chapter explains one part of the model, but the greatest value comes from understanding how the capabilities work together.
Leadership reflection:
What must our organisation be able to do consistently to create value with business technology?
The Business Technology Value Creation Model shows the capability model in motion.
While the capability model explains what the organisation must be able to do, the value creation model explains how value flows. It connects business design, demand, development, release, rollout, service delivery and business value realisation into one end-to-end view.
The model highlights an important principle: value creation starts before formal development begins. Business needs must be first recognised, shaped and prioritised before they become development requests or backlog items. When this early work is weak, development teams are often forced to clarify business intent too late and with too little context.
The model also shows that value creation continues after development. A technically complete solution has not yet created business value. Value is realised when people adopt the solution, services operate reliably and business outcomes improve.
This is why BTS connects plan, build and run. Traditional operating models often separate planning, development and operations into different organisational areas. These separations create handovers, delays and fragmented accountability. BTS treats them as connected parts of one value creation flow.
The model also recognises different types of demand. Capability planning, ideas and concepts, increments and improvements, service changes and service requests do not require the same level of planning, governance, or delivery preparation. Larger and more uncertain needs require broader business design and portfolio steering while smaller changes can move more quickly through backlog-based or service-based flows.
This supports enterprise agility. Applying one governance model to every type of work often leads either to excessive control or insufficient planning. BTS allows different types of demand to follow different paths while maintaining visibility, ownership and accountability.
The value creation model also introduces Minimum Viable Governance. Governance is embedded in the flow through a limited number of decision points. These decision points ensure that the right work is started, development capacity is committed at the right time, solutions are ready for release, and outcomes are followed through. The purpose is not to increase bureaucracy, but to make value, risk and accountability visible where decisions matter most.
The surrounding frame of the model is also important. BTS aims to create value, improve efficiency, ensure continuity, and support business design. These objectives reinforce one another. The organisation creates value by developing the right capabilities Efficiency comes from connecting activities across the lifecycle. It ensures continuity by making services dependable. It supports business design by bringing business and technology expertise together from the outset.
The value creation model therefore provides the dynamic view of BTS t shows how the capabilities described throughout this book work together to create business value from initial ambition to measurable operational outcomes.
Leadership reflection:
Where does value most often slow down in your organisation: before development starts, during delivery, at release, in adoption, or in daily operations?
Operating models do not work because they are documented. They work when people understand their roles, accountabilities, decision rights, and contribution to value creation.
The Business Technology Roles and Identities Model provides the people view of BTS. It gives a common language for the roles needed to plan, govern, develop, operate and improve business technology.
BTS groups roles into four professional identities: business excellence, development excellence, service excellence and smart governance. Together, these identities reflect the end-to-end value creation flow and help people understand how they contribute to business outcomes.
Business excellence focuses on creating competitive advantage through integrated business and technology development. People in this identity shape business needs, design capabilities, challenge existing ways of working, identify opportunities and ensure that business outcomes are defined and realised.
Development excellence focuses on turning business intent into working solutions. People in this identity manage development flows, solve implementation challenges, coordinate dependencies, and ensure that solutions are designed, validated and delivered effectively.
Service Excellence focuses on reliable and continuously improving services. People in this identity manage service ecosystems, operational quality, support, resilience, service integration and user experience.
Smart Governance focuses on direction, clarity, decision-making, and trust. People in this identity ensure that governance, roles, risks, tools, architecture, finances and operating model practices enable value creation rather than slow it down.
The role identity model is important because roles are not the same as job titles. One person may perform several BTS roles. One role may be shared between several people. The right arrangement depends on the size, structure, and maturity of the organisation. What matters is that the responsibilities are clear and that accountability does not disappear between organisational units.
In practice, BTS roles follow three broad contribution patterns. Owners are accountable for value, direction, funding, priorities or lifecycle outcomes. Orchestrators make the flow work across teams, services, portfolios and governance structures. Practitioners and implementers perform the development, operational, analytical, support and improvement work that creates outcomes in practice.
This distinction helps leaders avoid two common problems. The first is assuming that a role exists because a job title exists. The second is assuming that collaboration will succeed without clear ownership. BTS makes the required responsibilities visible so that organisations can decide how to assign them in their own context.
The role model becomes even more important in the AI era. AI-enabled capabilities may support analysis, documentation, workflow execution, monitoring, user support, and decision preparation. This does not remove the need for clear roles. Instead, it increases the need to define human accountability, supervision, decision rights and quality expectations.
People remain accountable for judgement, outcomes, governance, exception handling and continuous improvement. AI-enabled capabilities assist, automate and scale defined work. The clearer the roles, the more safely and effectively AI can contribute to value creation.
Leadership reflection:
Are your business technology accountabilities clear enough that collaboration happens naturally, or does progress still depend on personal networks and escalation?
The Operations Canvas complements the value creation model.
Like the value creation model, it follows the flow from demand and development through release, service delivery and service consumption. Its purpose is different, however. While the value creation model explains how value flows, the operations canvas makes visible the operational backbone that is often hidden behind value creation and governance yet is essential for dependable value delivery.
These elements are the operational backbone of value delivery.
Many organisations can describe how an idea becomes a project, how an agile team manages a backlog, or how a release decision is made. Fewer can clearly describe the operational structures that make services reliable, supportable, recoverable, secure, consumable and continuously improving.
The operations canvas addresses this gap. It shows the practical operational layers that support value delivery: service management, service desk, service integration, service release, application maintenance, data and AI operations, service operations, security operations, provider coordination and service consumption.
This matters because business value is not realised when a solution is technically complete. Value is realised when the solution works reliably in the operational environment. Users need to access it easily, receive effective support and trust that it will perform as expected. Services need to be monitored, maintained and recovered when necessary. Providers need to work together, operational risks need to be managed and operational insight needs to drive continual improvement.
The operations canvas also reminds leaders that operations are not simply the final stage of the lifecycle. Operational requirements influence demand, development and release decisions from the beginning. A solution that cannot be supported, monitored, recovered or integrated into the service landscape is not yet ready to deliver sustainable value.
This is especially important in modern service ecosystems. Services now depend on internal teams, suppliers, cloud platforms, external providers, data flows, automation, AI-enabled capabilities, and global operations. Operational failures often arise across these dependencies rather than within a single system. The operational backbone therefore needs to be visible, coordinated and governed.
The operations canvas makes visible the work that often sits behind the scenes. It shows how service management, service integration, release, support, operations, security and service consumption together sustain value after development. Without these capabilities, development may deliver solutions, but the organisation will struggle to operate, support, improve and eventually retire them.
The canvas also connects service governance and service delivery. Service governance defines service lifecycle direction, sourcing, financial control, supplier relationships, and resource structures. Service delivery turns service commitments into operational reality through release readiness, operations, support, service integration and continual improvement. The operations canvas shows how these disciplines meet in practice.
In this capability book, the operations canvas provides the operational perspective of BTS . It explains what must be in place for value to be delivered beyond development: operational capabilities, service structures, support mechanisms, service management practices and consumption channels that make business technology dependable in daily use.
Leadership reflection:
The operations canvas shows what keeps value alive after delivery: the operational structures, services, support mechanisms, and management practices that make business technology dependable in daily use.
This capability book can be read from beginning to end as an introduction to the six BTS disciplines. It can also be used as a reference when improving a specific part of the operating model.
Leaders designing or renewing an operating model should start with the capability model. It helps identify which capabilities are strong, which are fragmented and which are missing.
Leaders improving value flow should use the value creation model. It helps reveal where value slows down, where handovers create friction and where governance is either too heavy or too weak.
Leaders clarifying accountability should use the roles and identity model. It helps define ownership, orchestration and practitioner responsibilities across business and technology.
Leaders strengthening operational performance should use the operations canvas. It helps reveal whether the operational backbone is visible, managed and connected to business value.
Each chapter of this book explains one discipline, but the disciplines should always be read as parts of one system. Improving one capability in isolation may strengthen specific areas. Improving the connections between capabilities creates enterprise value.
The book begins with demand discipline because value creation starts before development. Demand is where business ambition, capability needs, service needs, data needs and AI opportunities are shaped into a form that can be prioritised, governed, developed and delivered.
A strong demand discipline helps the organisation avoid a common trap: treating business technology as a request-handling mechanism. BTS starts from a different premise. Business technology is a shared capability for creating business value. It begins with understanding what the organisation needs to become better at, and it continues until that improvement is visible in daily operations and measurable outcomes.
Final leadership reflection:
If your organisation improved only one thing in its business technology operating model this year, which capability would create the greatest business impact?
