PROJECT PANTHEON·THE OPERATING MODELAs of September 2026

Speed with Control

This page is the reference for how Pantheon works: the principles the plan enforces, the arrangement between Product, Innovation, and Technology, the six-stage lifecycle every feature passes through, and who decides what along the way.

THE PRINCIPLES WE BUILD TO

Each principle in the product strategy has one mechanism in Pantheon that enforces it

  1. {{ p.n }}
    {{ p.title }}

    {{ p.how }}

    2.

“We are not missing capability. We are missing connection.”

Jim Hansen, Chief Product Officer

The Release Approval gate in Pillar II publishes the enablement note that Pillar I consumes, so nothing is taught that has not shipped.

HOW CONVEY BUILDS CONVEYIQ

Three peer organizations, each owning its functions exactly once

Product curates the destination: it groups legacy deployments into migration cohorts and negotiates scope with the ELT and stakeholders.
Innovation sole-sources the ConveyIQ OS core, runs the module teams to one standard, and architects the infrastructure that Technology then operates. Technology supplies the engineers who move into the platform and develops the enterprise services that the platform exposes.

EXHIBIT 1

Innovation builds the platform; Product decides what it delivers; Technology supplies the capacity and runs the enterprise.

Source: Convey Innovation, operating model · As of September 2026
Convey ProductCurates the destination.Convey InnovationSole-sources the platform.Builds the core. Runs the module teams. Architects the infrastructure.Convey TechnologySupplies capacity. Runs the enterprise.Legacy customerdeploymentsMigrationcohort 1Migrationcohort 2Migrationcohort 3Scope negotiationCuratedroadmap andfeature listELTInnovationCustomersDeliveryConveyIQ OScore · one teamModule teamQualityReliabilityTimelineModule teamQualityReliabilityTimelineModule teamQualityReliabilityTimelineModule teamQualityReliabilityTimelineModule teamQualityReliabilityTimeline+nStandards and gates — one Definition of DoneInfrastructure architectureand reference implementationTalentreservoirEnterprise Services LayerEONS HTPDevelopedand testedto theexposurestandard.PaymentsDevelopedand testedto theexposurestandard.PreferencesDevelopedand testedto theexposurestandard.…Developedand testedto theexposurestandard.Infrastructure operationsRuns the platforminfrastructure —throughput, uptime,resilienceScoped features,sequenced by cohort.Estimates, capacity,delivery dates.Services exposed through the OSto the exposure standard.Service readiness informs cohort sequencing.Engineers move into module teams,trained in the framework.Reference implementationhands off to operations.the platform corecapacity and infrastructure hand-offswhere scope is negotiated
Capacity moves. Decision rights move. Growth does not pause.
TodayConvey ProductConvey InnovationConvey TechnologylegacyroadmapTransitionConvey ProductConvey InnovationConvey TechnologyTargetConvey ProductConvey InnovationConvey Technology

One platform. Three organizations. Each function owned once.

EXHIBIT 2

Every function has one owner and every hand-off has a named receiver.

Source: Convey Innovation, operating model · As of September 2026
RESPONSIBILITY PRODUCT INNOVATION TECHNOLOGY
{{ r.name }}
Owns Hands off or receives No role

The two places the old structure strained, the moment a platform capability becomes Technology's to run and Product's authority over engineers it does not manage, are resolved here as explicit hand-offs rather than shared ownership.

EXHIBIT 3

Every feature passes six gates, and each gate has one approver

Source: Pillar II, Development Lifecycle Blueprint · As of September 2026 · Approvers and SLAs OWNER TO REPLACE
1 · Intake
2 · Design Review
3 · Estimation
4 · Build
5 · Quality Gate
6 · Release Approval
Product
Submits and prioritizes
Confirms outcome
Accepts scope
Confirms sellable
Innovation
Triages fit to OS
Approves design
Estimates effort
Builds to standard
Verifies against DoD
Delivery
Reviews operability
Commits capacity
Load and tenancy tests
Releases
GATE
Prioritization Owner
Innovation
Delivery
Module lead
One Definition of Done
Executive Sponsor
Darker cells mark the lane that holds the gate.
EXHIBIT 4

Six decision types, one accountable role each

Source: Pillar II, decision-rights charter · As of September 2026 · Assignments OWNER TO REPLACE
DECISIONPRIORITIZATION OWNERPRODUCTINNOVATIONDELIVERYELT
{{ r.name }} {{ r.c1 }} {{ r.c2 }} {{ r.c3 }} {{ r.c4 }} {{ r.c5 }}
R responsible · A accountable · C consulted · I informed

Features and enterprise services pass the same Quality Gate

There is one Definition of Done. A feature built by a module team and an enterprise service developed by Technology are verified against the same five groups: Functional, Security and Multi-Tenancy, Performance, Documentation, Enablement. The standard is held in Pillar II and applied without variation in Pillar V, so that anything ConveyIQ exposes to a client has cleared the same bar regardless of who built it.

Convey InnovationPublished by Convey InnovationEdition · September 2026