The Forge

The canvas is the artifact each project carries. The Forge is the institutional venue where canvases live. Without it, the canvas is just a document. With it, the canvas becomes the working surface for a recurring conversation that gives the project layer its shape.

This chapter introduces The Forge: what it is, what it does, who is in it, and how it adapts across organizations of different sizes. The Forge is not optional in this framework. It is the body that holds the project layer together. Without it, projects run in isolation, patterns surface invisibly, and the connection between the project layer and the layers above and below it never gets made.

What The Forge is

The Forge is a cross-functional body that meets on a regular cadence to do three things: gate new project candidates, review the canvases of active projects, and surface patterns that should move toward the policy layer. The same body holds all three functions, because the three are connected — the gate produces canvases, the review reveals what is working, and the pattern work feeds the policy layer. Splitting the functions into separate bodies would lose the conversation that connects them.

Membership is functional, not titular. The AI Enablement Lead chairs. The executive sponsor attends when needed, particularly for promotion decisions or escalations to the strategic loop. The L&D partner attends because capability projects come through The Forge alongside operational ones. Function leads from data, IT, legal or risk, and other relevant areas rotate in based on what is currently on the canvas — someone from the data team is in the room when a data-heavy project is being reviewed; legal is in the room when a consent question is up. Project sponsors of active canvases are members; project leads attend when their canvas is being reviewed. The configuration shifts as the project portfolio shifts.

The Forge is a working body, not an audience. People in the room are expected to engage with the canvases, ask questions, name patterns, and contribute judgment. The Forge does not work as a status meeting where teams report and the room nods.

Three functions

The gate. When a candidate project — strategic or emergent — wants to enter the canvas, it comes to The Forge first. The candidate is described briefly, with a working answer to the strategic-alignment question: which priority in the Strategic Loop does this serve, and how will we know if it does? The Forge tests the answer. Candidates that clear the test enter the canvas with a sketched plan. Candidates that cannot answer the question stay outside the formal Project Layer — which does not mean they go away. Team-level experimentation continues without consuming institutional resources, and a candidate may come back later with a sharper case for strategic relevance.

The gate is simple. It is also the most important decision The Forge makes. A weak gate produces a project portfolio that drifts away from the strategy. A strict gate suffocates the curiosity and emergence the framework wants to keep alive. The discipline is to ask the alignment question honestly without using it as a club.

The review venue. Active project canvases come to The Forge on a recurring basis. The review is brief — what has hardened, what has changed, what is approaching graduation, what new evidence has come in. The point is not to relitigate the project. It is to make the project legible to the rest of the body, and to make the broader portfolio legible to the project. Canvases get sharper because they are reviewed, and the people in the room learn the actual texture of what AI is doing in the organization.

This review is also where the project hands evidence up to the strategic loop and across to the policy layer. When something a project has surfaced changes what leadership should believe about the business, that flows up. When something a project has surfaced is the kind of issue that keeps appearing across projects, that flows toward policy. The Forge is the connective tissue.

The pattern surfacer. Across multiple canvases, the same readiness gap shows up. Or the same risk question. Or the same governance bottleneck. The Forge holds the standing question: is this familiar? When the answer is yes, the recurrence gets named — written down on the candidate-pattern list maintained by the AI Enablement Lead — and tracked across subsequent reviews. When the recurrence keeps holding, the pattern qualifies for promotion, and the conditions in Chapter 16 govern what happens next.

This is the function Chapter 15 said could not be left to chance. Patterns do not surface on their own. The Forge is the venue where someone is making them visible.

The role of the AI Enablement Lead

The Lead chairs The Forge, but the chair is more orchestrator than decision-maker. The body decides; the chair makes the deciding possible. The Lead prepares the agenda, holds the candidate-pattern list across reviews, tracks what has been escalated to the strategic loop and what has been promoted to the policy layer, and keeps the conversation tied to the canvases rather than to politics or anecdote. Most of the time, the chair’s job is to ask sharp questions and get out of the way.

The Lead also holds the institutional memory between reviews. The Forge meets on a cadence; the Lead works between meetings — surfacing new candidates for the next gate, preparing canvas updates with project leads, watching for patterns that might surface at the next review. The chair role is not the same as the Lead’s larger role, but it is one of the central activities the Lead performs.

How The Forge adapts to organization size

The Forge takes different forms in different organizations. The function is constant; the structure adapts.

In a small organization — a few hundred employees, perhaps one or two AI projects in flight — The Forge may be a single recurring meeting with three or four people: the AI Enablement Lead, the executive sponsor, the L&D partner, and one or two function leads relevant to current work. It may not even be called The Forge formally. It may just be “the AI working group.” That is fine. Calling it something else does not change what it is doing.

In a mid-sized organization with more projects in flight, The Forge becomes a more formal body with rotating membership. Function leads attend based on what canvases are active. Project sponsors are standing members. The Lead’s coordination work between meetings increases proportionally.

In a large organization with dozens of projects across business units, The Forge may become a hierarchy — a central Forge that handles cross-cutting work and pattern surfacing for the policy layer, with business-unit-level Forges feeding into it. The patterns that surface at the unit level eventually flow to the central body, where the cross-organizational view is held.

The principle to hold across all three: The Forge is a working body, not a bureaucratic structure. As the organization grows, the temptation to build more formal procedures grows with it. Resist. The Forge works because the people in the room engage with the actual canvases. Anything that gets in the way of that engagement is a feature to remove, not a feature to add.

What The Forge is not

The Forge is not a governance committee that pre-approves projects in detail. It applies the strategic-alignment test, not a project-design review. The actual project work — scoping, staffing, running — stays with project teams.

The Forge is not a status meeting. Reports flow into the body through the canvas, not through slide decks. A canvas that has been kept current is enough for a Forge review; a project that has not updated its canvas has nothing useful to report.

The Forge is not a body that makes design decisions for projects. Project leads make project-level calls. The Forge makes calls that span multiple projects: what crosses the gate, what gets escalated up, what gets promoted to policy.

The next chapter begins the deep dive into the canvas’s first section: project readiness.