AI strategy and business architecture for the Government of Canada

Hours saved using AI is not realized value.

Astraterra helps federal and Crown executives turn AI investment into results they can report: work that has been redesigned, benefits that are measured, and value that reaches the budget.

The problem

Why the hours never reach the budget

The time AI saves is real. It rarely shows up in departmental results, and the reasons are organizational, not technical.

  1. 01

    No one planned the harvest

    AI is bought for its capability, not for an outcome. With no target measure and no plan for the capacity it frees, saved time is absorbed by email, meetings and rising demand. Below a certain gain, it stays a convenience.

    Benefits-Driven AI
  2. 02

    AI was added to the old process

    An assistant speeds up each task, but the file still waits in every queue between teams. Elapsed time barely moves, because the task was never the constraint. Return comes from redesigning the work around what AI does well.

    AI-native process redesign
  3. 03

    Strategy, maturity and governance aren't connected

    Strategy sets ambitions the organization can't yet deliver. Governance is built to approve pilots, not to scale them or hold anyone to their benefits. Each works on its own, and the value is lost in the gaps between them.

    A connected foundation

The pattern is visible in the Government of Canada's AI Register: reviewed entry by entry, few of its 400+ systems identify measurable fiscal or mission benefits.

Services

Three practice areas, one for each gap

Each practice area answers one of the reasons AI value goes missing. Most engagements draw on more than one.

01 · Plan the harvest

AI benefits and investment planning

Start every AI investment from the outcome it should move, how that will be measured, and what happens to the capacity it frees. A process typically needs about a 1.3× productivity gain before its benefits can be harvested. Below that, AI is a convenience.

  • Use-case discovery and prioritization
  • Outcome measures
  • Harvesting plans
  • Portfolio business cases
  • Benefits tracking

Built on Benefits-Driven AI

02 · Redesign the work

AI-native process redesign

Redesign the work around what AI does well, instead of speeding up the steps it already has. Start from the program's goal and its binding constraint, and keep accountability where it belongs.

  • Constraint analysis
  • Decision modelling
  • Autonomy levels and error budgets
  • Human decision rights
  • Role redesign

Built on CLAIR

03 · Connect the foundation

AI strategy, maturity and governance

Connect what the organization intends, what it is able to do, and how it decides, so pilots scale and benefits have owners. Includes the delivery lifecycle that takes solutions from proof of concept to production with the traceability the GC expects.

  • Departmental AI strategy
  • Maturity assessment and roadmap
  • Governance and sponsorship
  • Solution development lifecycle
  • Contractor oversight

Built on AI Organizational Maturity and the AI Solution Development Lifecycle

The method

One method, planned from the harvest back

The three practice areas work as one method. The harvest is planned first, the work is redesigned to deliver it, and a connected foundation lets it scale.

  1. Practice 01

    Outcome

    The departmental result the investment is meant to move.

  2. Practice 01

    Measure

    How the result will be measured, and the baseline it starts from.

  3. Practice 02

    Redesign

    The work rebuilt around what AI does well, starting from the binding constraint.

  4. Practice 01

    Harvest

    Freed capacity redeployed and the value banked, only once it shows in production.

Practice 03 · The connected foundation

AI strategy

Which outcomes matter, in what order, and who sponsors them.

Organizational maturity

What the organization must become able to do so the results last.

Governance

How AI is approved, delivered, scaled and held to its benefits.

Inside the redesign stage

CLAIR: Constraint-Led AI Redesign

CLAIR draws on the Theory of Constraints, process reengineering, Lean, Six Sigma, decision modelling and benefits realization management, and adapts them to the ways AI breaks the assumptions those methods were built on. It starts from the program's goal and its binding constraint, never from "where could we use AI?"

  1. 0Frame value
  2. Worth pursuing
  3. 1Discover reality
  4. 2Locate and forecast constraints
  5. 3Re-imagine around decisions
  6. 4Prove realizable and lawful
  7. Realizable and lawful
  8. 5Pilot on system throughput
  9. Effective in operation
  10. 6Capture value and redesign roles
  11. Value captured
  12. 7Operate and re-focus
  13. Phase 7 returns to Phase 2 whenever the constraint moves

Six of the twelve principles

  • The constraint decides where AI goes. AI placed where it is merely easy is the default failure.
  • The decision is the unit of design. Tasks are derived from decisions, not the reverse.
  • Design for verification, not just generation. An output that takes nearly as long to check as to produce has moved the work, not removed it.
  • Autonomy is capped by accountability. The impact on the affected person sets the ceiling. Capability can lower it, never raise it.
  • Prove capability on your own cases. Vendor benchmarks and demos are not evidence.
  • Bank only what has been realized. Positions, contracts and budgets change only after the effect is shown in production.

Redesign in practice

Same grant. Two processes.

Follow a mocked-up grant application through today's five-team process. Add AI to every step and each task gets faster, but the file still waits in every queue. Redesign the process around AI, with the same accountability, and the queues between teams disappear.

Today140 daysAI added to every step122 daysRedesigned around AI25 days

Play the walk-through About 5 minutes
Grant file · Today Elapsed 140 days
Handoffs 5Queues 5Rework loops 2Illustrative · click to switch

Track record

Organizations served

Government of Canada

  • Global Affairs Canada
  • Shared Services Canada
  • Public Services and Procurement Canada
  • Employment and Social Development Canada
  • Canada Revenue Agency
  • Bank of Canada

Industry

  • TD Bank
  • Lockheed Martin Canada
  • SNC-Lavalin
Terry Feltham

The principal

Terry Feltham

Astraterra is led by Terry Feltham, an engineer and business architect with 30 years of experience in redesigning how organizations work. He also brings over 13 years of experience in machine learning and artificial intelligence, having published a first article on AI commercialization in 2017. Terry served 20 years in the Royal Canadian Navy, and has held senior roles with PwC, IBM and the federal public service.

The firm rests on one view: adopting AI is mostly an organizational design problem. The technology is capable. What's usually missing is a clear strategy, redesigned work, and the discipline to measure and capture what AI delivers.

  • B.Eng, Royal Military College of Canada
  • MBA, University of Leicester
  • PMP
  • Lean Six Sigma Black Belt
  • English and French

Working together

Ways to engage Astraterra

Start with a briefing or a Scan, and decide what comes next on the evidence.

Half day

Executive briefing

For a DG, ADM or CFO leadership team: where AI value is realistically available in your organization, and what it would take to capture it.

3 to 4 weeks

Scan

One value stream: its goal, its binding constraint, the key decisions and redesign options, ending in a clear go or no-go.

6 to 9 months

Redesign

The full CLAIR lifecycle on one value stream, through a pilot to measured, captured value.

Scoped to need

Strategy and portfolio

A departmental AI strategy, benefits plan and governance model, with a prioritized investment roadmap.

Contact

Where is the AI value in your organization?

A 30-minute conversation, without a pitch deck. Bring a program, a process or a pressure.