BOLT¶
BOLT: Business-Owned Low-Code Technology Enablement
TL;DR
BOLT defines how business and IT collaborate on low-code delivery. Four principles (Business Ownership, On-Demand Agility, Low-Code Platforms, Trusted Enablement), four delivery tiers based on complexity, six accountable roles. Business teams own and build within guardrails that IT has pre-approved.
BOLT is the enterprise operating model that defines how business and IT collaborate to build, own, and scale digital solutions on low-code platforms — enabling rapid delivery of applications, automation, and AI-driven agents, with built-in security, guardrails, and governance.
What BOLT Is¶
Most enterprise IT challenges are not technology problems. They are delivery problems. Business teams have real needs that are straightforward to meet with modern low-code tooling — but the traditional path runs through IT backlogs, investment cycles, and security review queues that can take months. By the time the solution is approved, the business context has changed.
BOLT solves this by defining a structured, tiered delivery model where business teams are empowered to own and deliver solutions directly — within a governed, pre-approved platform that IT has already secured and enabled. The result is faster delivery, reduced IT backlog, clear accountability, and no shadow IT.
BOLT is not a future plan. It is an operating model that works today. The platform is accredited. Security pre-approvals are in place. Connectors are approved. Ownership is defined. Solutions are being delivered. BOLT formalises this into a repeatable, scalable model ready to grow with the organisation.
The BOLT Principles¶
Four principles define the framework — two owned by the business, two owned by IT, all interdependent:
| Pillar | Owner | What It Means |
|---|---|---|
| B — Business Ownership | Business | Business teams define requirements and lead solution delivery aligned with operational needs |
| O — On-Demand Agility | Business | Subject matter experts build and iterate solutions rapidly without traditional IT queues |
| L — Low-Code Platforms | IT | Enterprise platforms that enable rapid development of apps, automation, and AI-driven agents |
| T — Trusted Enablement | IT | IT provides secure platforms, guardrails, and oversight to ensure scalable and compliant delivery |
The B and O pillars give business teams the speed and ownership they need. The L and T pillars give IT the control and governance they require. Neither works without the other — BOLT is the contract between them.
Why BOLT Now?¶
The conditions that make BOLT viable are already in place in most enterprise Power Platform deployments:
- The platform is accredited — organisations have invested in getting Power Platform through enterprise security review. That investment should be leveraged, not repeated for every solution.
- The demand is real and growing — business teams want to build. The question is whether that building happens inside a governed model or outside it.
- The alternative is worse — without BOLT, citizen development happens anyway. Ungoverned, untracked, and invisible to IT until something breaks or an audit finds it.
- Traditional delivery models have structural gaps — RAD teams, agile squads, and outsourced development are not the right tool for the volume and variety of low-to-medium complexity solutions that business teams genuinely need.
BOLT does not replace IT-led delivery for complex, strategic solutions. It creates a parallel track for the large class of solutions that business teams can and should own — freeing IT capacity for the work that genuinely requires it.
BOLT and the Other Frameworks¶
BOLT is one of four complementary frameworks on powerplatform.wiki:
| Framework | Core Question | Primary Audience |
|---|---|---|
| BOLT | How do business and IT build together? | Business Leadership · CIO · CTO · CFO · Business Leaders |
| SCALE-OPS | How do we govern and operate the platform at scale? | Admin · CoE Lead · Platform Lead |
| DIALOGE | What are the building blocks of a solution? | Solution Maker · Solution Engineer |
| SHIELD | How do we protect the solution and platform? | CISO · Security Org |
BOLT and DIALOGE work together at the solution level — BOLT defines who owns the solution and how it flows through the delivery tiers; DIALOGE defines what the solution is made of and how to build it well.
BOLT and SCALE-OPS work together at the platform level — BOLT defines how business teams engage with the platform; SCALE-OPS defines how the platform is operated and governed for them.
BOLT and SHIELD work together at the security level — BOLT's Trusted Enablement pillar (T) defines the security governance model for citizen development; SHIELD defines the detailed security controls that Trusted Enablement is built on.
BOLT asks: Who owns this, and how does it get delivered? SCALE-OPS asks: How do we run the platform it runs on? DIALOGE asks: How do we build it well? SHIELD asks: How do we keep it secure?
The Four Delivery Tiers¶
The heart of BOLT is a four-tier delivery model where complexity determines the tier — not the technology, the team, or the tool. Each tier defines who owns the solution, what IT's role is, and what oversight applies.
| Tier | Name | Complexity | Owner | IT Role |
|---|---|---|---|---|
| 01 | Personal Productivity | Very Low | Citizen Developer | Support on request |
| 02 | Business Solutions | Low | Business Team | Onboarding and guidance |
| 03 | Fusion Team Solutions | Medium | Business + IT collaborative | Co-development and architecture |
| 04 | Enterprise & Strategic | High | Line of Business IT | Full SDLC ownership |
Increasing complexity → Increasing IT involvement → Increasing oversight
For the full tier definitions, ownership model, escalation triggers, and decision guidance — see BOLT Delivery Tiers →
The Six Roles¶
BOLT defines clear accountability across six roles — eliminating the ownership ambiguity that creates shadow IT, duplicated effort, and governance gaps.
| Role | Primary Tier | Core Responsibility |
|---|---|---|
| Citizen Developer | Tier 1 | Personal productivity solutions within approved boundaries |
| Business Team / Solution Owner | Tier 2–3 | Business-led solution ownership and delivery |
| Platform Team | All | Platform standards, guardrails, enablement, connector library |
| Tech Solution Team | Tier 1 | First-line support for citizen developers |
| Line of Business IT | Tier 3–4 | Architecture, complex delivery, enterprise integration |
| Security / Compliance Function | All | Pre-approval, periodic review, mandatory sign-off for Tier 3–4 |
For the full role definitions, RACI breakdown, and interaction model — see BOLT Roles & Accountability →
What Makes BOLT Work — The Foundation¶
BOLT is not aspirational. The foundation that makes it operational is already in place:
- Platform accredited — enterprise security approval obtained. No new reviews to begin building.
- Security pre-approved — solutions up to defined classification levels are pre-approved. The biggest bottleneck is removed.
- Connector library approved — 30+ enterprise connectors approved and published. Teams can integrate without starting a new review cycle.
- Terms of use defined — acceptable use policies, data handling guidelines, and developer terms documented.
- Ownership model defined — clear delineation of who owns what across all four tiers.
- Solutions delivered — real solutions live in production across multiple business teams.
For the full foundation detail and Power Platform capability status — see BOLT Foundation →
BOLT Maturity Model¶
| Level | What it means |
|---|---|
| Establishing | BOLT operating model defined. Platform accredited. Tier 1 and Tier 2 delivery active. Connector library published. Ownership model communicated. |
| Scaling | All four tiers operational. Fusion team delivery (Tier 3) active. Security / Compliance Function engagement model embedded. Enablement programme running. CoE providing platform visibility. |
| Optimising | BOLT continuously improved based on delivery experience. New platform capabilities assessed and onboarded. Demand pipeline managed. Metrics tracked and reported. Platform extends to new use cases and potentially new low-code platforms. |
How to Use This Framework¶
If you are a business leader or executive: Start with the BOLT principles and the four delivery tiers. Understand what your teams can own and deliver directly — and what engages IT. BOLT is the answer to "how do we move faster without losing control?"
If you are a Platform Team lead or CoE Lead: Read the full framework — particularly the tiers, roles, and guardrails. BOLT is your operating model for managing citizen development at scale. The Trusted Enablement pillar is your mandate.
If you are a business analyst or power user building solutions: Start with the delivery tiers to understand which tier your solution belongs to. Then read the guardrails to understand what you can build, how, and when to escalate.
If you are a Line of Business IT architect: Read the roles and the Tier 3/4 delivery model. BOLT defines when and how IT engages — not as a gatekeeper, but as a collaborative delivery partner for complex solutions.
If you are in a security or compliance role: Read the guardrails and the security / compliance function role. BOLT's pre-approval model defines what is already cleared and what requires your involvement.
Reference Files¶
| File | Contents |
|---|---|
| bolt-principles.md | B, O, L, T — the four principles explained in depth |
| bolt-tiers.md | The four delivery tiers — scope, ownership, escalation, decision guide |
| bolt-roles.md | Six roles — RACI, responsibilities, interaction model |
| bolt-guardrails.md | Trusted Enablement in practice — connector library, data classification, workspace strategy, security pre-approval |
| bolt-foundation.md | What's already built — accreditation, capabilities, and the path to scale |
Part of the powerplatform.wiki framework library Last updated: March 2026 Last reviewed: March 2026 Status: Complete — all pillar files documented