The Expansive EDGE Glossary

The structured, AI-ready capture of all the decisions, processes, judgements, and tacit know-how that make a business actually work.

Every service business runs on operational intelligence. Most of it lives in people's heads. Some is half-written in old SOPs. None of it is structured, accessible, or AI-ready until it is codified. Codified Operational Intelligence is the asset we deliver, instead of selling consulting hours. It outlasts the people who built it and the consultants who helped capture it.

Trademarked by Expansive EDGE. Read more on the About page.

A central, documented source of truth for how a service business operates.

Every key process, role, standard, and decision captured in one place, a place the team actually works from every day. Typically deployed in Trainual, Whale, Notion, or Microsoft SharePoint, depending on the business size, industry, and existing tech stack. A Business Playbook is the primary output of a ControlShift engagement.

See our Business Playbooks service page for the engagement model.

A structural blueprint developed in Stage 2 (Design) of the ControlShift methodology.

The 4 Ps capture four foundational dimensions of a business:

• Profile, the essentials about the business (entity, history, market, scope)
• People, roles, responsibilities, org structure, key relationships
• Policies, workplace policies, handbooks, governance rules
• Processes, operational workflows, SOPs, decision points

The 4P Scorecard is the documented baseline that anchors the Business Playbook. Different from the 8-stage ControlShift methodology itself, the 4P Scorecard is a tool used within ControlShift, not a parallel framework. Each P becomes a working chapter of the deliverable Business Playbook.

Captured during Stage 2: Design. Expanded into the deliverable Playbook during Stage 4: Codify.

Stage 1 diagnostic of the ControlShift methodology, a structured 45-90 minute online assessment.

Scores a service business across all 8 ControlShift stages. Produces a personalized 40+ page AI-generated report and a prioritised roadmap (90-day, 6-month, 12-month). Some clients take it annually as part of their planning cadence.

Take it: ControlShift Insights Assessment.

A documented, step-by-step set of instructions for performing a specific operational task.

SOPs are the building blocks of every Business Playbook. A good SOP is repeatable (anyone trained can execute it), testable (you can tell if it was done right), and written for the person actually doing the work, not the manager describing it from memory. We typically capture SOPs through screen recordings and stakeholder interviews, then convert them into Playbook entries with AI-accelerated drafting.

SOPs come out of Stage 3: Capture.

The centralized platform where a Business Playbook lives.

A Knowledge Hub is where SOPs, policies, templates, process maps, and supporting materials are stored, navigated, and updated as the business evolves. We typically deploy on Trainual (SMB-friendly, course-style), Whale (mobile-first, trades/field-service friendly), Notion (flexible, all-in-one workspace), or Microsoft SharePoint (enterprise environments). Unlike Google Drive or OneDrive, a Knowledge Hub is purpose-built for process documentation with role-based access, search, and progress tracking.

The Knowledge Hub is stood up during Stage 4: Codify.

The decisions, processes, judgements, and tacit know-how that make a business actually work.

Most operational intelligence in service businesses lives in people's heads. Some is half-written in old SOPs nobody reads. None of it is structured, AI-ready, or transferable until it is captured and codified. When operational intelligence walks out the door with a departing employee, the business loses a piece of itself. The ControlShift methodology exists to prevent that.

See also: Codified Operational Intelligence.

A free 30-minute video call with founder Lyndon Smith.

Used to understand a prospect's current operational reality, identify where the friction is, and decide honestly whether a Business Playbook engagement, the Insights Assessment, or another Expansive EDGE service is the right next step. No script, no obligation, no hard sell, if we're not the right fit, we'll say so.

Book: Contact page.

A written, AI-generated operational diagnostic of your service business.

Surfaces the top operational opportunities, process gaps, knowledge-concentration risks, system inconsistencies, and quick wins, prioritised by impact. It is the deliverable of the ControlShift Insights Assessment (a 45-90 minute self-serve version with a full 40+ page report) and of the Insights stage of an engagement.

For a free, instant starting point, take the Owner Dependency Score.

Produced during Stage 1: Insights.

The 8 to 12 highest-value operational processes that drive most of a service business's revenue, quality, or key-person risk.

Core processes meet three tests: they drive revenue or absorb the most cost, they carry the most key-person risk, and they shape the rest of the operation downstream. Most owners can name two or three without help; the others surface through structured diagnostic conversations at the Insights stage of every engagement.

The 16-week Phase 1 engagement covers ControlShift stages 1 to 4 (Insights, Design, Capture, Codify) applied to Core Processes only. Non-core processes are addressed in follow-on engagements once the foundation is in place. See The 16-Week Roadmap for Codifying Your Core Processes for the week-by-week walkthrough.

Defined during Stage 1: Insights; codified across Stages 2–4.

A 90-minute structured-questioning methodology, AI-assisted for synthesis, that surfaces the tacit operational judgement living in senior operators' heads.

Anchored to real recent work rather than abstract reflection. Surfaces not just what a senior operator does but the patterns they're recognising and the reasoning behind the decisions they make. Replaces the multi-week consultant-led interview exercises that used to be the only way to extract tacit knowledge. Now done in an afternoon and catches more of the second-order judgement than the human version did.

Used in Stage 3: Capture. Deep dive in our methodology piece.

A structured artifact embedded in a Business Playbook that captures one operational decision, with reasoning.

Six fields: the decision, the trigger that fires it, the reasoning behind the rule, the rule itself, edge cases, and the named owner. Sits inline at the point in the procedure where the decision happens, not in a separate "decisions" folder. The decision layer is what distinguishes Codified Operational Intelligence from procedural documentation. Most playbooks document what to do; decision documents capture why and when, the part that travels poorly between operators.

Format and methodology in Documenting Decisions, Not Just Steps.

A measure of how mature a service business's operations are, scored across four dimensions.

• Knowledge, where expertise lives, in heads or in transferable systems.
• Process, whether work is repeatable without the owner in the room.
• Measurement, whether the business knows what's working, in time to act.
• Leadership, whether decisions happen across the business without the owner.

The Expansive EDGE diagnostic scores each dimension 1 to 4 across 16 questions, producing a 16-64 total mapped to four maturity stages: Founder-Dependent (16-28), Documented but Fragile (29-42), Systematised (43-54), and Codified Operational Intelligence (55-64).

Score yourself in 15 minutes with the self-diagnostic.

Operational expertise that lives undocumented in the heads of specific employees.

The most expensive form of business risk in service organisations because it walks out the door with every departure, can't be transferred to new hires efficiently, and shows up as a multiple-suppressing concentration risk in exit diligence. Tribal knowledge is what the ControlShift methodology exists to convert into Codified Operational Intelligence.

Worked example of what it costs: The Hidden Cost of Tribal Knowledge.

Continuous, AI-assisted comparison between documented processes and the actual audit trails generated by operating tools.

When documented and actual workflows diverge, the named owner gets a flag with specific deviations and decides whether to update the documentation or retrain the team. Replaces the traditional pattern of quarterly Playbook review meetings, which routinely get skipped and let documentation drift out of step with reality. Drift detection is the mechanism that turns a Playbook from a snapshot into a living asset.

Methodology in Process Maps That Don't Gather Dust. Installed during Stage 7: Refine.

A structured document defining a role in the business by purpose, outcomes owned, decisions authorised, and key relationships.

Distinct from a job description (which lists tasks) and from a RACI (which assigns Responsible/Accountable/Consulted/Informed for specific work items). Role charters are the highest-leverage of the three for designing a scalable service business because they describe what the role exists to produce rather than what the person spends time doing. The right sequence is org chart first, role charters second, RACIs and job descriptions third.

Full comparison in Job Descriptions vs Role Charters vs RACI.

A structured, opinionated answer to three questions every leadership team has to answer: how do we decide what to do, how do we get the work done, and how do we learn and adjust.

Examples: EOS (Traction), Scaling Up (Rockefeller Habits), OKRs, V2MOM, 4DX, Lean, Pinnacle. Every operating framework organises the work but none organises the operational knowledge underneath the work. Codified Operational Intelligence is the layer your chosen framework runs on top of, not a competitor to any of them.

Comparison of the major frameworks in What's an Operating Framework, and Which One Do I Need?

The collection of software tools a business uses to run its operations.

In typical service businesses, the stack accumulates through department-level decisions made over many years and reaches 30 or more tools, with significant redundancy and weak integration. The Expansive EDGE Technology Stack Assessment audits the current stack (starting with the finance manager's vendor list, then expanding through team-level inputs), maps tools to functional categories, identifies redundancy, and rationalises without disrupting team adoption.

Full method in The 30-Tool Tech Stack.