Brian lambert strategy thoughts on

Transforming
while performing

An AI platform is an operating model with a technology stack inside it,
not the other way round.


One shared engine of people and AI producing measurable business outcomes, while the business keeps running.

Six jobs, Capture, Resolve, Compute, Condition, Explain, Steer: Only Steer creates value; the rest is cost .

An answer after the decision is worth a lot less, however accurate.

Measure contributions the business accepts, not models trained, pilots launched, or tools bought.

Approach.png

Judgment is moving from people to machines, so everything right of that line needs governing


Unchanged wrap-around: data, architecture, DevOps, and cloud governance.

New: model and evaluation management, evals in CI.

Put AI where the data is. Keep it portable. Govern it once.

GCP

Main AI and analytics plane

Vertex AI · BigQuery · Cloud Run · Dataflow · Pub/Sub

Assumed from “GCP preferred”; confirm real footprint.

OCI

Where systems of record live

Autonomous Data Warehouse · OCI Data Science · OKE

Compute moves to the data.

Portability

Kubernetes · containers · Terraform · a vendor-neutral model gateway


Cloud governance defined once and inherited: identity, network, logging, cost tagging, data residency.

Exit and portability written into contracts and architecture.

Op Model.png

Classify every workload before it gets funded,
built or hosted

Classification

Workload paths

Job

Ground, Reason, Act, or Supervise; classic ML and generative AI take different paths

Timing

Batch · near-real-time · interactive

Risk tier

Drafts a person accepts · assisted decisions · autonomous agent actions

Placement rule

Data residency → latency → cost per accepted outcome → team skills

Good first workloads

Recurring, named owner, measurable baseline.

Hold off

Final legal or financial decisions.



A portfolio of models, routed by task. No single bet.

Several providers behind one gateway: Gemini on Vertex, OpenAI, Claude, and open-weight models where control or cost matters.

Use as-is

Ground with our data

Fine-tune

Build our own

Each step must beat the eval set.


Every model has a registry entry, owner, version, independent validation, and eval baseline.

Prompt and context changes go through change control like code.

Contracts cover data use, model-change notice, and exit terms.

Agree what the data means first, then index the documents

Business-definitions layer

Use what the company already owns.

RAG and vector search

Grounding is about relevance, not completeness; ranking does the real work.


Tenant isolation enforced at retrieval: permissions, entitlements, and approved sources live in the policy gate.

Reduce hallucinations with grounding, citations, evals, and abstain thresholds.

Three memory kinds

Session · episodic · semantic

Each with its own retention and consent rules.

op model.png

Agents do the work.
People own the outcome.


Every agent has an identity, a named human owner, and limited rights; no agent accepts its own work.

Action controls include authorization limits, human-in-the-loop thresholds, blast-radius limits, reversibility.

Agents prove themselves in sandboxes before promotion; multi-agent orchestration only after single-agent reliability.

Every accepted output carries a receipt

Who accepted it, against which criteria.

Preventive controls before it runs. Detective controls after. Enforcement in the middle.

Preventive

Ground, Reason

Source approval, permissions, model inventory, bias testing.

Enforcement

Policy gate

Detective

Act, Supervise

Monitoring and drift detection, incident response, audit trail and lineage, attestation.

Monitoring findings → policy: controls tighten as evidence builds.


Spine: NIST AI RMF plus sector rules (verify what currently applies).

Set once, inherited by every team: AI use policy, decision rights, a named acceptor for every output.

No big bang. The platform ships as packaged workflow releases.

Workflow release = roles + agent setup + acceptance criteria + controls + practice

Standard environments

Dev workspaces, production-like test data, agent sandboxes.

Controlled release pipeline

Piloted in one team.

Then copied

Architecture principles, pattern library, architecture reviews set once.


MLOps backbone: GitHub Actions CI/CD, evals in CI, MLflow or Kubeflow, Airflow, runtime observability and tracing.

Measures: lead time, change failure rate, time to restore, share of accepted work that was AI-assisted.

Inference and retrieval are metered, recurring costs. Manage them like a utility.

One ledger: AI cost and return, baseline signed off in the first quarter.

North star

Cost per accepted outcome

After AI spend.


Smallest model that passes evals, caching, batching, retrieval budgets, per-tenant spend limits.

Showback, then chargeback to business lines through SLAs and a transparent cost model.

Each phase funded on evidence; pilots get clear criteria to scale or stop.

One reference model, built once and reused by every operating model

Nine components

Reference model

Set once and inherited

Strategy & Governance, Technology, Environments, Performance, Partners & Suppliers

Set per operating model

Organization, People, Demand, Service Delivery

Shared AI platform service, a business within a business, organized into workstreams.

Team: platform engineering, ML and GenAI engineering, data and knowledge engineering, evaluation and assurance, forward-deployed engineers.

Leadership habits: standards, architecture reviews, mentoring, redesigned roles where AI drafts and people accept.

structure.png

Find the value, prove it, then capture it, with a decision at every gate

Months 1–4

Find

Assess seven dimensions, publish reference architecture, set cost baseline, pick 2–3 workflows.

Gate 1

Months 5–9

Prove

Pilot workflow releases, evals and governance live, value net of AI spend.

Gate 2

Months 10+

Capture

Copy proven patterns, stand up second operating model.


Scorecard: leading (readiness, eval pass rates, adoption), lagging (cost per accepted outcome, lead time, quality).

Readiness L1 AI-Assisted → L5 Collective AI; pilot areas reach L4 in year one.

Transforming Performing.png