Michael Martino Show

AI has the potential to fundamentally reshape how government delivers services. But technology alone won’t get you there. The real enabler—the real differentiator—is your operating model. The question isn’t “Are we investing in AI?”, It's “Are we structured to actually benefit from it?” 

What is Government 2030? Government 2030 is often framed as: Digital-first services  AI-enabled decision-making  Seamless citizen experiences  Data-driven policy   All of that is true — but it’s incomplete. Government 2030 is not a technology vision, it is an operating model transformation.  It’s a shift from program-centric, siloed delivery, and reactive service models to citizen-centric, integrated ecosystems proactive, and predictive services   This is not modernization but a re-architecture.  That distinction matters — because modernization can be layered on top of legacy thinking -- re-architecture cannot. 

Technology enables transformation. Process defines it. People determine whether it actually happens.  If you treat People Readiness as a secondary concern, you’re gambling the outcome of your entire program. If you elevate it—if you invest in it, integrate it, and lead it from the front—you dramatically increase your chances of success.  

Cloud platforms are foundational.  To deliver value you need to manage the experience end-to-end and that means making customer journey management a core capability, not a side activity.  Your customers don’t experience your systems they experience your journeys. 

Cloud transformation is not a technology problem, it’s a delivery system problem.  The design of your team is one of the most critical variables in that system. If your team is too big, too fragmented, or too part-time,  you’re going to feel it: slower progress  lower quality  constant sense of friction.   If you invest in a small, dedicated core team: aligned accountable empowered, you create something much more powerful -- momentum.  In transformation, momentum is everything. 

Transformation is not about what you implement -- it’s about what you achieve.  Benefits realization is the mechanism that ensures you actually get there. If you’re leading a transformation — or about to start one — ask yourself: Do we have clearly defined, measurable benefits? Does every benefit have a real owner? Are we actively tracking and managing value delivery?  If the answer to any of those is no — that’s your starting point

Process excellence is customer experience. Not a contributor to it. Not something that supports it in the background. It is the experience.  In government, we often talk about customer experience as if it lives in the front office—websites, call centers, service counters, digital channels. There are investments in better UX, chatbots are deployed, and forms are redesigned.  Yet citizens are still frustrated.  Why?  Because the experience doesn’t break in the interface it breaks in the process.  The citizen perspective A citizen will: submit an application call for an update get transferred  be told their case is “in progress.”  Weeks go by and there is no movement -- that’s not a channel or UX problem.   That’s a process failure.  What is process excellence? Process excellence is not just documenting workflows or creating standard operating procedures. It’s about designing processes that are: Predictable – outcomes are consistent  Efficient – minimal waste, minimal delay  Transparent – visible to both staff and customers  Outcome-driven – focused on resolution, not activity   The key is if your processes are broken, no amount of front-end investment will fix the experience. 

Cloud platforms are powerful and accelerate transformation, improve customer experience, and modernize your organization.  They, however, are not a silver bullet.  Without a modern operating model, they will reflect your existing dysfunctions—just faster and more expensively.  Before you sign that contract do the hard work of defining how your organization will operate because technology doesn’t transform organizations operating models do. 

AI should not be deployed where it is most visible, it should be deployed where it removes the most friction from the system.  In most government organizations, that friction lives deep in the back office.  If you fix that, the front office will take care of itself. Ignore it and no amount of AI in the front will save you. 

Delivering large cloud platforms in iterations is not easy.  It requires: discipline in architecture maturity in governance a fundamental shift in how organizations think about delivery  When done right you stop treating delivery as a single high-risk event and start treating it as a controlled, continuous system and that’s ultimately what large-scale transformation needs to become.   Not a project but a machine that reliably delivers value over time. 

When transparency is done right, trust increases, not because everything is going well—but because everyone understands what’s actually happening.   Decision-making becomes faster and more grounded. Issues get resolved earlier and the program becomes resilient, because it can adapt in real time.  

A system integrator is not just a vendor and they’re not just a builder.  They are the execution engine of your transformation and that engine only works if it's: properly integrated into your operating model  governed with clarity and discipline  it’s aligned to outcomes—not just deliverables   If you get the SI model right, you accelerate delivery, reduce risk, and actually achieve transformation.  If you get it wrong, you end up with: delays  cost overruns  a system that doesn’t serve your citizens   In government—that’s not just a project failure it's a service failure. 

What are we comparing At a high level, Waterfall and Agile are not just delivery methods—they represent fundamentally different beliefs about how work gets done.  Waterfall assumes: Requirements can be known upfront Change is a risk to be controlled Delivery should be sequential and gated  Agile assumes: Requirements evolve Change is expected and valuable Delivery should be iterative and incremental 

Should AI shape your operating model?  Eventually, it has to.  You can start by adding AI tools to existing processes but the real opportunity comes when you step back and ask, "If AI could do a large portion of our operational work how would we design this organization from scratch?"  The organizations that ask that question early will be the ones that build the next generation of service delivery. For governments especially, that could mean something incredibly powerful: faster services consistent decisions better outcomes for citizens.  

Today we’re going to talk about something that is quickly becoming one of the most important topics in public-sector leadership: how artificial intelligence can transform government service.  For decades, government modernization has mostly meant digitization.  Governments took paper forms and turned them into online forms. They took in-person transactions and moved them to websites. Portals, contact centers, and mobile apps.  These things helped but the underlying system stayed the same.  Citizens still had to figure out government. They had to navigate programs. They had to understand eligibility rules. They had to know which department to contact. They had to repeat their story multiple times across multiple channels.  Artificial intelligence introduces something fundamentally different. For the first time, governments have the ability to build systems that understand, guide, and resolve citizen needs in real time. When implemented properly, AI doesn't just make services faster. It changes the entire service model. 

Delivering an out-of-the-box implementation is not about resisting change -- it is about choosing the right kind of change. Rather than bending the platform to match the past, the organization adapts its processes to match the future.  That takes discipline and leadership.  It also takes a clear understanding that the value of modern platforms comes not from how much you change them—but from how much you allow them to change you, and when organizations get that balance right, they don’t just implement software -- they modernize how they operate. 

Today we’re going to talk about a decision that quietly determines whether your transformation succeeds or becomes a multi-year recovery effort.  When should you get out of the box and bend the system to your business and when should you let the platform redefine your business processes?  This is not a technology debate – it's an operating model decision.  If you’re in government, or running a large enterprise platform program — ERP, CRM, case management, core modernization — this question is the fulcrum. 

Start with outcomes  There’s a famous line from How Big Things Get Done by Bent Flyvbjerg: Big projects don’t fail because they’re ambitious. They fail because they’re poorly governed and poorly scoped.  In government, transformation often starts with a solution: “We need a new case management system.” “We need AI.” “We need to modernize.”  That’s activity language. Successful programs start with outcome language: Reduce claim processing time by 40%. Increase first contact resolution to 75%. Cut regulatory backlog in half. Improve public trust scores by 15%.  Transformation must be tied to measurable public value.  If the outcome is vague, the program will drift. If the outcome is precise, the system can self-correct. Outcome clarity is not a communications exercise. It is governance architecture.  Governance is design, not oversight Most governments treat governance as reporting: Steering committees Status decks Traffic-light dashboards  That’s oversight, but governance in transformational programs must be design authority.  High-performing jurisdictions embed decision rights clearly: Who owns scope? Who owns funding trade-offs? Who can kill features? Who can redefine policy constraints?  If no one can say no, scope will explode. If everyone can say no, nothing will move. Successful programs establish: A single accountable executive Clear escalation pathways Explicit decision cadences Integrated policy, operations, and technology leadership.  Governance must reduce friction, not create it.  Decompose the transformation Big transformations fail when treated as a single monolithic build. The better pattern is modular decomposition. Instead of replace the entire operating model. You break it into: Service journeys Capability clusters Technology components Regulatory enablers Data architecture layers  This is where program architecture matters.  Successful transformation programs operate like portfolios, not projects.  Each component: Has a defined value hypothesis Has an accountable owner Has delivery milestones Feeds into enterprise outcomes  This mirrors principles found in scaled agile and portfolio governance models, but applied with public-sector rigor.  The key question becomes -- what can we deliver in 6–12 months that moves the outcome metric? Transformation is not an event.  It’s a sequence of value releases.  Align CX with Operations This is where many governments stumble. They redesign experience in isolation from operational process, but experience is an emergent property of process design. If you want faster service you redesign: intake logic decision authority automation triggers escalation thresholds  Not just the front-end portal.  Successful government transformations engineer process-driven experience architecture.  Institutionalize risk management One of the biggest myths in government transformation is that risk can be eliminated before launch.  It cannot.  What matters is risk visibility and structured mitigation. In government: Costs are underestimated. Benefits are overstated. Timelines are compressed for political cycles.  Successful programs do the opposite: Independent cost validation Reference-class forecasting Stage-gate funding tied to evidence Transparent reporting to Treasury and Cabinet.  Transformation requires professional program controls: Integrated master schedules Dependency mapping Benefits realization tracking Risk heatmaps updated monthly.  This is not bureaucracy. This is operational hygiene.  Build internal capability  Another consistent failure pattern -- outsourcing transformation thinking.  Vendors can implement. They cannot own accountability for public value. Successful governments: Retain architectural authority Build internal product management capability Embed business process designers Develop enterprise data governance.  

Governments are very good at approving transformation but they are much less disciplined at benefiting from it.  If you’re leading a large-scale modernization — digital platform replacement, service transformation, AI implementation, operating model redesign — you need a benefit realization framework that is operational, measurable, and governed.  Start with business outcomes Most benefit frameworks fail at the starting line. They define benefits like this: implement new CRM launch new portal reduce manual processing automate intake.  Those are outputs.  A benefit realization framework starts with outcomes. For example: reduced average case processing time increased first contact resolution reduced cost per transaction increased compliance rate improved client satisfaction index  When Treasury Board of Canada Secretariat evaluates transformation proposals, they are not funding “technology.” They are funding performance improvement. Your framework must reflect that discipline in that every initiative must tie to a measurable business outcome.  If it cannot — it is a project, not a transformation.  Define benefit types  A mature framework categorizes benefits into four major types: 1. Financial Benefits cost avoidance cost reduction revenue recovery productivity gains  2. Service benefits reduced wait times increased accessibility improved service standards  3. Risk and compliance benefits reduced audit findings improved regulatory adherence reduced fraud exposure  4. Strategic benefits increased policy agility improved public trust cross-ministry integration  Large programs often over vector on financial benefits because they are easier to quantify, but in public sector transformation, risk and service benefits often carry more long-term value. A good framework balances them.  Assign a benefit owner — not a project owner Here’s where most governments collapse. Benefits are assigned to the project team. That’s a mistake as project teams deliver outputs while operations delivers benefits.  For every benefit in your framework, you need a: named executive owner (usually Director or ADM level) baseline metric target state measurement frequency reporting mechanism.  If no operational executive is accountable for realizing the benefit, it will not materialize.  Establish a baseline  You cannot measure improvement if you don’t know where you started and yet, in many large public programs, baseline measurement is skipped because: data is fragmented metrics are inconsistent reporting systems are immature.  Without a baseline: cost savings are estimated productivity gains are assumed service improvements are anecdotal.  A credible benefit realization framework requires a current: cost per transaction FTE effort processing time satisfaction score error rate.  If you don’t have this data, the first workstream in your program should be performance instrumentation. This is where many transformation offices underestimate the importance of analytics maturity.  Separate “Hard” vs “Soft” benefits  Hard benefits: direct cost savings headcount reduction contract elimination.  Soft benefits: employee engagement client trust reduced complaints improved brand perception.  Hard benefits satisfy finance. Soft benefits drive long-term legitimacy. The key is not dismissing soft benefits — but operationalizing them. For example, instead of “improved trust,” measure: complaint rate reduction net satisfaction movement public sentiment index.  Framework discipline turns soft benefits into observable metrics.  Build a benefit realization register Every large transformation should maintain a living Benefit Register. This is not a slide deck. It’s a structured artifact that includes: Benefit ID Description Category Baseline Target Measurement formula Owner Dependencies Realization date Status. 

Start with the business outcome   Before you build anything, define the operational objective. Are you trying to: Increase first-contact resolution? Reduce case backlog? Improve eligibility accuracy? Shorten processing time? Lower cost per transaction?  This is not about “using AI.” This is about improving a measurable public-sector performance indicator. If you can’t tie your AI agent to: a reduction in processing time a decrease in call volume a increase in compliance accuracy a measurable client outcome.  You are not building an agent -- you are running an experiment. AI agents must be outcome-anchored.  Select the right journey Not every service is ready for an AI agent. Start with a journey that is: high volume rules-based process-heavy data-rich currently constrained by human throughput  Think about: benefits eligibility screening license renewals status inquiries simple case triage document validation.  Do not start with complex discretionary casework -- start where process discipline already exists. AI agents amplify process maturity.  They do not compensate for process chaos.  Decompose the work This is where most agencies get it wrong. They try to build an “AI agent for intake.”  Instead, break the work into micro-decisions: validate identity confirm eligibility criteria cross-reference records flag missing documentation route exceptions draft correspondence.  Formalize the decision logic Before any model is trained or configured, you must extract the institutional logic. That means: policy rules eligibility thresholds exception handling criteria escalation triggers risk thresholds compliance constraints.  Most of this already exists — but it lives in: policy binders tribal knowledge training manuals legacy documentation.  Build the human-in-the-loop control model Government agencies cannot deploy autonomous agents without layered oversight. This is where many agencies should look at how regulated sectors like healthcare and financial services design controls.  Your AI agent must have: confidence thresholds automatic escalation rules audit logging version control explainability outputs override authority  In public service, “black box” is unacceptable, every decision must be defensible.  Human-in-the-loop is not optional, it is a design principle.  Engineer the data layer AI agents are only as good as the data environment they operate in. That means: clean client records structured fields real-time system access API integrations secure identity management.  If your agency still relies on PDF uploads and manual data re-entry, your agent will struggle.  Before scaling AI agents, agencies often need to modernize: case management systems document management systems identity verification layers.  This is why AI is often the forcing function for digital modernization. You cannot layer intelligence on top of fragmentation.  Pilot in a contained environment Do not launch enterprise-wide.  Select one: service line regional office transaction type.  Define: baseline performance metrics clear success criteria controlled workload a rollback plan.  Measure: cycle time error rate escalation frequency client satisfaction staff productivity.  The pilot should run long enough to observe edge cases. Agents fail in the edges — not the happy path.  Redesign the workforce model This is the step leaders underestimate.  If an AI agent performs: intake validation basic eligibility checks standard correspondence drafting.  Then what happens to your employees? They don’t disappear.  They shift to: complex exceptions vulnerable client cases appeals fraud detection quality assurance.  AI agents increase cognitive leverage, but only if the agency intentionally redesigns roles, KPIs, and performance models. If you don’t redesign the workforce, the agent creates friction instead of capacity.    

Let’s start with a common pattern. An organization says, “We need to improve CX.”   They launch: a CX initiative build journey maps identify pain point  redesign touchpoints.  All this and nothing changes.  Why?  The underlying workflow — the intake process, the routing logic, the approval hierarchy, the eligibility rules, the system architecture — stays the same, and that’s where experience actually lives.  Experience is not what you intend--it's what your process produces.  A real life example - UNIQLO Let’s take a private sector example. Walk into a UNIQLO store it  feels calm is organized is efficient is predictable.  The fitting rooms flow. Checkout is fast. Inventory is tightly managed.  That isn’t “good vibes.” That is process discipline.  Their merchandising process, supply chain integration, inventory management, and staff task orchestration are engineered to eliminate friction.  The experience you feel is the byproduct of structured operational design.  If the: replenishment model was chaotic store associates didn’t have clearly defined operating standards handoffs between warehouse and retail were inconsistent, the experience would collapse.  Not because the brand promise changed — but because the process would produce a different outcome.  A government example Now let’s bring this into a government context.  Picture a public benefits agency.  A citizen applies for a benefit online.  Here’s what actually determines their experience: how many systems the application must pass through whether eligibility rules are automated or manually adjudicated whether documentation requirements are sequential or parallel whether case assignment is pooled or individual whether decision letters are generated dynamically or manually edited whether policy exceptions require escalation.  The citizen doesn’t see any of that -- but they feel it.  They feel it as: “This is confusing.” “Why do I have to submit this again?” “Why does it take 30 days?” “Why did I get transferred three times?”  Those outcomes are not communication failures.  They are structural outputs.  The operating model is the experience Your: operating model is your customer experience architecture queue logic is an experience decision case routing rules are an experience decision data architecture is an experience decision funding model is an experience decision.  If: intake is fragmented across channels, customers will experience fragmentation approvals require four layers of hierarchy, customers will experience delay your CRM doesn’t expose case history to front-line staff, customers will experience repetition.  You don’t fix that with empathy training -- you fix that with process engineering.  The Maturity Shift Early-stage CX organizations focus on perception.  Mid-stage organizations focus on touchpoints.  Mature organizations focus on process.  Elite organizations integrate journey governance directly into operational design authority.  In elite organizations: journey leaders sit in operating committees policy design considers downstream workflow impact digital teams and process engineers co-design performance metrics tie customer outcomes to operational KPIs.  That’s when experience stops being cosmetic, it becomes systemic.  The strategic reframe Instead of asking, “How do we improve CX?”, you should be asking, “What in our operating model is structurally producing friction?”  That question changes everything. It: moves the conversation from branding to engineering switches empathy workshops to process redesign goes from journey maps to workflow diagrams.  This is where transformation actually happens.  If you want better experience, engineer better flow, because the customer is always downstream of your operations and downstream effects are never solved upstream with messaging. They’re solved at the source. 

 First Contact Resolution isn’t a contact center metric -- it’s a journey outcome. If you try to “train your way” to FCR without fixing the journey, you’ll fail every single time.  Why first contact resolution is misunderstood Let’s start with the misconception. Most organizations treat First Contact Resolution as a: frontline performance issue coaching issue script compliance problem.  So what do companies do? Add more knowledge articles Run refresher training Tighten QA scorecards  Then they’re shocked when FCR barely moves. That’s because FCR is not about agent capability alone. FCR breaks when: customers contact you too early in the journey information is fragmented across systems policies force handoffs agents lack authority upstream processes are fundamentally broken.  If a customer has to call you, explain their story, get transferred, wait for a back office action, and then call again—that’s not an agent failure. That’s a journey design failure.  Shifting from contact handling to resolution journeys To deliver First Contact Resolution consistently, you need to stop asking, “How do we resolve this contact faster?” and start asking, “Why is this customer contacting us—and what has to happen so they never have to contact us again?”  That’s a journey mindset. A resolution journey includes, what: happened before the contact information the customer already has systems the agent needs access to decisions can be made in the moment what follow-up actions are triggered automatically  When FCR fails, it’s usually because: the journey crosses too many organizational silos ownership is unclear  resolution authority is split across teams  First Contact Resolution only works when one moment in the journey owns the outcome.  Designing the FCR journey How do you design for FCR journey:  Identify high-volume, high-friction reasons for contact Not all contacts are equal. Start with: repeat callers status-check calls “I already submitted this” calls “I was told to call back” calls  These are journey failures disguised as demand. Map these issues end-to-end—not just from the moment the call starts, but from the customer’s original intent.  Define what resolved means Organizations define resolution as: “We answered the question” “We logged the request” “We handed it off”  Customers define resolution as: “My issue is done” “I don’t have to follow up” “Nothing else is required from me”  If your FCR definition doesn’t include customer confirmation of completion, you’re measuring activity—not outcomes.  Collapse handoffs Every handoff is an FCR killer. To design for FCR: bring policy, process, and authority as close to the first contact as possible eliminate unnecessary approvals pre-authorize common exceptions.  The question to ask is: “What prevents this agent from fully resolving this today?” Then remove that constraint—systematically.  Design agent enablement into the journey This is not just about training. It’s about: unified customer context real-time decision support clear escalation paths permission to act  FCR doesn’t happen because agents are heroic. It happens because the journey is engineered for success.  What leaders get wrong Leaders kill First Contact Resolution when they: obsess over handle time penalize agents for taking ownership measure productivity instead of outcomes separate “front office” and “back office” accountability  You cannot demand FCR while designing a system that rewards deflection, speed, and handoffs. If you want First Contact Resolution: fund journey redesign, not just tools hold journey owners accountable—not just contact center leaders  accept that some calls will take longer so future calls don’t happen at all.  That’s how mature organizations think.  

One of the biggest misconceptions is this belief that AI maturity equals removing humans from decisions.  The narrative goes something like this: “AI will eliminate manual work.”  “AI will replace decision-making.”  “AI will automate the frontline.”  AI reduces repetitive effort but mature AI strategies don’t remove humans. They reposition humans because AI doesn’t replace judgment — it changes where judgment sits.  In service environments, especially government or customer operations, you’re not just optimizing for efficiency. You’re optimizing for: trust fairness compliance transparency experience outcomes.  These aren’t purely technical problems -- they’re human problems. Human-in-the-loop isn’t a safety net added later -- it’s an architectural principle.  What human-in-the-loop means Human-in-the-loop doesn’t mean someone clicking “approve” on every AI output. That’s not strategy — that’s bottleneck engineering. A strong human-in-the-loop model defines where human expertise adds value across the lifecycle.  There are three primary layers: 1. Design-time humans These are your service designers, policy owners, product managers, and domain experts. They define: what the AI is allowed to do what outcomes it should optimize for where escalation happens  If humans aren’t embedded at design time, your AI will scale the wrong behaviors faster.  2. Run-time humans These are frontline staff, supervisors, and operational reviewers. They intervene when: confidence thresholds drop policy ambiguity appears edge cases emerge  This is where AI becomes an augmentation tool — not a replacement.  3. Oversight humans This is governance. Risk leaders. Ethics committees. Service excellence teams. They analyze: model drift bias signals complaint patterns experience impacts.  Human-in-the-loop isn’t one role. It’s a layered system.  Why this matters more in government  In commercial tech, a bad AI decision might cost revenue. In public service, a bad AI decision can cost trust and trust is harder to rebuild than any operational metric.  Think about AI in contexts like: eligibility decisions benefits processing contact centre automation case management digital service navigation.  These environments carry: policy complexity legal obligations vulnerable populations high emotional stakes.  When organizations rush into full automation, they often discover something quickly efficiency goes up as well as escalations and complaints.  Why?  AI handles the predictable middle of the bell curve extremely well, but the edges — the messy, human scenarios — still require interpretation.  A human-in-the-loop strategy protects the system from brittle automation. It acknowledges that service isn’t just about speed. It’s about judgment.  The strategic benefits leaders miss Most conversations about human-in-the-loop focus on risk mitigation but there’s a strategic upside that many leaders underestimate:  If humans don’t have authority or context, they’re not in the loop -- they’re in the queue.  Treating humans as error catchers. Humans shouldn’t only exist to fix AI mistakes -- they should shape strategy, define guardrails, and continuously improve outcomes.  To wrap If you’re building or refining your AI strategy -- human-in-the-loop isn’t a compliance checkbox. It’s a competitive advantage, creates resilience, and  accelerates learning.  Most importantly — it preserves the human trust that every modern service depends on.  As AI becomes more capable, the organizations that win won’t be the ones that remove people fastest. They’ll be the ones that design the smartest partnership between humans and intelligent systems. That’s where real transformation happens. 

AI is already operating inside your organization. Your staff are using generative AI tools to draft emails, summarize policy documents, analyze data, and prep briefing notes.  All of this is happening without a coherent, enterprise-level strategy.  Which means decisions about AI are being made: individually inconsistently invisibly  That’s not innovation. That’s unmanaged risk.  An AI strategy is not about “starting AI.”   Without a strategy, AI amplifies the wrong things  Government systems are very good at one thing--scaling whatever already exists.  If your processes are slow, AI can make them faster—but still slow in the wrong places.   If your data is biased, AI can make those biases more efficient.   If your policies are unclear, AI will apply that ambiguity at machine speed.  This is why an AI strategy has to start before technology.  A real AI strategy answers questions like: what problems are we trying to solve for citizens? where is human judgment essential—and where is it not? what decisions should never be automated? what level of explainability do we require for public trust? how do we ensure AI improves equity instead of undermining it?  Without those answers, AI doesn’t transform government. It industrializes its flaws.  AI strategy is a trust stragtegy In government, trust is the currency.  And AI—used poorly—can burn through trust faster than almost any other technology we’ve seen.  Citizens don’t care whether a decision was made by a: legacy system human caseworker AI model They care whether it was: fair transparent timely accountable  An AI strategy establishes: clear accountability for AI-supported decisions standards for explainability and auditability guardrails around surveillance, consent, and data use.  A strong AI strategy starts with mission outcomes: reducing wait times improving eligibility accuracy increasing compliance through better guidance supporting frontline staff under pressure making services more accessible to vulnerable populations  Your strategy should clearly articulate where: AI creates material public value it does not  where simpler solutions are better  This clarity is what prevents wasted investment—and public embarrassment.  AI changes the operating model, not just the toolset  This is the part most agencies underestimate.  AI is not just another system you plug in.  It changes how work is done decisions are made roles evolve accountability flows.  An AI strategy must address operating model questions: how do humans and AI collaborate in service delivery? what new skills do managers and frontline staff need? how do we redesign processes around AI, not bolt it on? who owns model performance over time?  If you don’t answer these questions deliberately, they get answered accidentally and accidental operating models are never good operating models.  Strategy enables speed There’s a false choice often presented in government--move fast and be reckless or move slow and be safe.  A well-designed AI strategy enables responsible speed.  It allows agencies to: move faster on low-risk, high-value use cases apply stronger controls to high-impact decisions reuse patterns, standards, and governance instead of reinventing them  Strategy reduces friction because people know: what’s allowed what’s not how to proceed That’s how you scale innovation without chaos.  What a government AI strategy should include Let’s get concrete.  A credible government AI strategy typically includes: A clear vision tied to public value and mission outcomes principles for responsible and ethical use A prioritization framework for AI use cases data readiness and quality standards governance and accountability models workforce and capability development vendor and procurement considerations metrics for success beyond cost savings  

Many organizations are building initiatives around activities, projects, and deliverables—instead of anchoring them in clear business outcomes.  If you’ve ever sat in a steering committee where someone says, “We delivered everything we promised… but the metrics didn’t change,”  this episode is for you.  Activity is not impact Most organizations don’t actually have a strategy execution problem.   They have an outcomes discipline problem.  They fund initiatives like: launch a new platform redesign a process implement a tool stand up a new team.  All these things don’t clearly answer one basic question:  What business outcome will be materially different if this succeeds?  Not, what will be: built delivered Launched.  Instead, what will improve reduce grow?  When initiatives aren’t explicitly tied to outcomes, success becomes subjective—and accountability disappears.  What “basing initiatives on business outcomes” means Basing initiatives on business outcomes does not mean adding a KPI slide at the end of a deck.  It means flipping how initiatives are conceived from the start.  Instead of asking. "What should we do next?”  You ask, “What outcome must change for the business to succeed?”  Real business outcomes are reduce cost-to-serve by 15% increase first-contact resolution by 10 points shorten cycle time by 20% improve regulatory compliance confidence increase customer retention in a specific segment.  Only after the outcome is clear do you ask, “What initiatives are most likely to drive that change?”  This sounds obvious, but it is rare.  Three failure modes  When initiatives aren’t anchored in outcomes, three predictable things happen.  Success becomes theater Teams celebrate go-lives, launches, and milestones—but no one can prove impact. The organization gets better at delivery, not results.  Prioritization breaks When everything sounds important, leaders prioritize based on politics, volume, or urgency—not value. Outcome-based initiatives create a common currency for trade-offs.  Continuous improvement dies If you don’t define the outcome, you can’t measure progress, learn, or adjust. Initiatives become “one and done” instead of continuously optimized.  Outcomes create strategic alignment  Business outcomes are the bridge between: strategy and execution leadership intent and frontline action investment and accountability.  When outcomes are explicit: executives know why they’re funding something teams know what success actually means managers can align trade-offs metrics stop being performative and start being operational.  This is especially critical in large, complex organizations—where initiatives cut across silos and no single team owns the full value chain.  Outcomes create shared ownership.  The outcome clarity check  Take any major initiative and ask three questions: What business metric will change if this succeeds? By how much must it change to justify the investment? Who is accountable for realizing that change—not just delivering the work?  If those answers aren’t clear, you don’t have an outcome-based initiative.  You have a well-funded experiment.   Why this matters now  In today’s environment—tight budgets, rising expectations, and increasing complexity—organizations cannot afford activity without impact.  AI, digital transformation, service design, journey management—all of these are powerful.  But none of them are strategies. They are means. Business outcomes are the end.  The organizations that win aren’t the ones doing the most work. They’re the ones that can clearly answer, “What changed because we did this?”  To wrap If you want better results, stop starting with initiatives.  Start with outcomes.   Fund outcomes.   Govern outcomes.   Hold leaders accountable for outcomes. 

Most government operating models are built around: programs policies channels functional silos.  Government is organized by what it does and  not by what the customer experiences. As a result, the customer journey is fragmented.  A citizen starts a service in one channel, gets handed off to another team, repeats their story, hits a policy boundary, and eventually gives up—or escalates.  No one owns that journey end to end.  Everyone owns a piece of the process.   No one owns the experience.  A journey-enabled operating model flips that logic.  Instead of asking, “How do we optimize our functions?”   It asks, “How do we design the organization around the journeys that matter most?”  What does journey enabled mean? A journey-enabled operating model does three critical things, it: treats customer journeys as managed assets, not artifacts embeds journey accountability into governance and decision-making aligns teams, funding, metrics, and technology around outcomes—not outputs.  This is not about replacing functional structures. It’s about overlaying a journey lens on top of them. Think of journeys as the connective tissue across policy, operations, technology, and service delivery.   Assign journey ownership Here’s where most organizations hesitate.  A journey-enabled operating model requires explicit journey ownership.  Not symbolic ownership. Not advisory ownership. Real accountability. A Journey owner is responsible for: end-to-end experience performance identifying friction and failure points prioritizing improvements across silos advocating for the customer in governance forums.  They do not replace operational leaders, instead, they act as horizontal leaders—cutting across vertical structures.  In mature models, journey owners have: decision rights dedicated capacity a formal role in investment and prioritization.  Without this, journeys revert to PowerPoint slides that collect digital dust.  Build journey-aligned teams A journey-enabled organization does not rely solely on centralized CX teams.  Instead, it creates journey-aligned, cross-functional squads—either permanent or federated—bringing together: operations policy technology data and analytics design and research.  These teams work on continuous improvement, not one-off projects.  They are measured on outcomes like: time to resolution first-contact completion effort reduction trust and confidence.  This is where the operating model shifts from episodic change to ongoing journey management.  Embed journeys into governance This is the hardest—and most important—part.  A journey-enabled operating model changes how decisions get made.  Journeys must be embedded into: portfolio planning investment governance performance reviews executive reporting.  Instead of asking, “Which project should we fund?” Leaders should be asking, “Which journey outcome are we improving?”  Instead of channel-based KPIs, organizations track: journey health drop-off points rework and escalation cross-channel failure demand.  This makes the customer visible in rooms where the customer has historically been absent.  Enable with data and technology Journeys cannot be managed without insight.  A journey-enabled operating model relies on: integrated data across channels journey analytics and flow analysis voice-of-customer and operational signals case and workflow visibility.  This is not about perfect data. It’s about directionally accurate insight that allows teams to see, where: customers get stuck effort spikes policies create friction  Technology becomes an enabler of learning—not just automation.  What does this look like? In organizations that do this well, you see real shifts: fewer handoffs faster service recovery reduced repeat contacts better alignment between policy intent and lived experience.  

The Illusion of AI readiness Many governments believe they are AI-ready because they’ve:  published an AI strategy piloted a chatbot created an ethics framework stood up a data or innovation office  All of that is important -- none of it, on its own, equals readiness.  True AI readiness is not about technology adoption--it’s about organizational transformation. AI doesn’t simply automate tasks—it reshapes decision-making, accountability, service models, workforce roles, and citizen expectations.  This is where many governments run into trouble. Governments try to layer AI onto legacy systems, legacy processes, and—most critically—legacy ways of working. That approach creates isolated wins, but systemic failure.  What is AI readiness?  A government is AI-ready when it can: deploy AI safely and ethically at scale integrate AI into core service delivery—not just pilots govern AI decisions with clarity and confidence equip its workforce to work with AI continuously adapt as AI capabilities evolve  What is not on the list? Tools. Vendors. Hype.  AI readiness sits at the intersection of data, governance, operating models, and culture. If any one of those is weak, AI maturity stalls.  The readiness gaps  1. Data readiness AI runs on data—but many governments still struggle with: fragmented data ownership poor data quality limited interoperability across ministries or agencies unclear rules on data sharing.  Without trusted, accessible, and well-governed data, AI systems produce unreliable or biased outputs. AI does not fix bad data.  It amplifies it.  2. Governance and accountability Too often AI governance becomes either so restrictive that nothing can move forward, or so vague that accountability disappears.  Key questions often go unanswered: who is accountable for AI decisions? who approves model use? who monitors bias and drift? who owns outcomes when AI is embedded in services?  AI readiness requires decision clarity, not just ethical principles.  3. Operating model misalignment This is the biggest gap—and the least discussed.  Most government operating models were designed for: linear processes human-only decision making static policies and rules. 4. Workforce confidence AI readiness is not just about skills—it’s about confidence and trust.  Public servants need to know: when to rely on AI when to override it how to explain AI-supported decisions to the public how AI changes—not replaces—their professional judgment  Without deliberate workforce enablement--AI becomes something that happens to employees, not with them.   The goal is not speed-- the goal is trust at scale.  Trust is built when AI is: explainable governed embedded in human-centered service design.  Are governments AI-ready? Some are becoming ready. Most are not yet ready at scale.  Governments are: experimenting responsibly learning what works and what doesn’t building foundational capabilities.  But readiness is uneven and the risk is not that governments move too fast--it's that they are move too cautiously in the wrong areas—focusing on pilots instead of platforms, tools instead of transformation.  What governments should do next 1. Shift from AI Projects to AI Capabilities Stop thinking in terms of pilots and start building reusable AI capabilities—data platforms, governance models, shared services.  2. Redesign the operating model Explicitly design how humans and AI work together. Define roles, escalation paths, and accountability.  3. Invest in data as critical infrastructure Treat data like roads, bridges, and utilities.  4. Build workforce fluency, not just skills Focus on judgment, ethics, and decision-making—not just prompts and tools.  5. Anchor everything in service outcomes AI is not the strategy. Better, faster, fairer services are. 

Before we talk about plans, we need to ground the conversation.  An AI agent is not just a chatbot that answers FAQs.  An AI agent is a system that can: interpret intent take action across systems follow defined rules and policies escalate appropriately learn within controlled boundaries.  In a government context, that could mean an agent that: guides a citizen through eligibility, application, and next steps  supports case workers by summarizing files, flagging risks, or drafting correspondence  proactively notifies citizens of obligations, deadlines, or benefits.   Start outcomes, not technology The biggest mistake I see government organizations make is starting with the tool.  They ask: what AI platform should we buy? should we build or buy? can we pilot something quickly?  Those are the wrong first questions The plan must start with service outcomes.  Instead ask, where do citizens experience the most friction? are staff overwhelmed by repetitive, rules-based work? do delays create risk, cost, or loss of trust?  High-value use cases for AI agents in government usually share three characteristics: high volume high repetition clear policy or decision frameworks  Eligibility checks. Status updates. Intake and triage. Case summarization. Guided self-service.  Your plan should prioritize two or three services, not twenty.   Define guardrails before building This is where government differs fundamentally from the private sector—and where planning really matters.  Before deploying AI agents, your plan must clearly define guardrails in four areas:  Authority What decisions can an AI agent make? What decisions must remain human-led? What decisions require dual control?  If you can’t answer that clearly, you’re not ready to deploy.  Accountability Every AI-enabled service must have a: named service owner business accountable for outcomes clear escalation and remediation model.  AI does not remove accountability. It concentrates it.  Privacy and data use Your plan must explicitly define: what data the agent can access what data it cannot access how data is logged, audited, and retained.  If privacy teams are brought in after the pilot, you’ve already failed.    Design AI Agents as part of the service journey Here’s an important mindset shift--you don’t “add” an AI agent to a service.  You design the service around the agent and the human together.  That means mapping the end-to-end journey and asking where does the agent: lead? assist? step back?  Build the operating model around the agent One of the most overlooked parts of AI planning in government is the operating model.  AI agents require: ongoing training and tuning policy updates content governance performance monitoring.  Your plan must answer who: owns the agent? updates rules and prompts? reviews decisions and outcomes? responds when something goes wrong?  Leading organizations have: product-style ownership for AI agents multidisciplinary teams—policy, service design, legal, technology clear metrics tied to service outcomes, not usage statistics  Measure  Let’s talk about metrics.  Too many AI pilots measure: number of interactions containment rates cost deflection  Those are operational metrics not public value metrics.  A strong AI agent plan measures: reduction in time to resolution increase in first-time-right applications improved staff capacity and satisfaction decrease in repeat contact improved equity of access  Scale intentionally Once the first use cases are live and stable, the plan should shift from experimentation to platform thinking.  That means: reusable components shared governance models consistent citizen experience across services.  The goal is not dozens of disconnected agents. The goal is a coherent AI-enabled service ecosystem. Scaling without a plan creates fragmentation. Scaling with a plan creates momentum.  

Trust in government services isn’t a “nice to have.”  It’s not a branding exercise.  It’s not a communications problem.  Trust is an operational outcome.  Trust matters  Most people don’t want to interact with government. They interact because they need: benefits healthcare licenses permits.  Trust determines whether they: comply willingly or reluctantly believe the information they’re given come back to the same channel next time—or avoid it entirely  When trust is low: call volumes spike complaints increase escalations become the norm frontline staff burn out  When trust is high: digital adoption rises self-service works conversations become shorter, calmer, and more productive  What trust means in government Here’s where governments often get it wrong.  They treat trust as a communications challenge: “Let’s explain better.” “Let’s update the website.” “Let’s issue a statement.”  Trust is not built by what you say. It’s built by what people experience repeatedly.  In government services, trust has four core dimensions:  Reliability Do you do what you say you’ll do—every time?  If you promise a response in five days, is it five days or fifteen?  Competence Do staff know the rules, the process, and the next steps or does the citizen hear, “I’m not sure,” too often?  Transparency Do people understand where they are in the process or does their application disappear into a black hole?  Fairness Do similar cases get similar outcomes or does it feel arbitrary, inconsistent, or dependent on who you talk to?  Trust is the accumulation of these experiences over time.  Trust is created at the journey level If you want to build trust, stop thinking in channels and start thinking in journeys.  Citizens don’t experience the: website customer service area payment area.  A person experiences: trying to get help waiting for a decision fixing a mistake following up when nothing happens.  Trust is most often broken in three moments: Handoffs When a citizen moves from digital to phone, or phone to caseworker, and has to repeat their story.  Waiting Silence kills trust.  If people don’t know what’s happening, they assume the worst.  Exceptions Life doesn’t fit into policy.  When the process can’t handle edge cases, trust collapses fast.  High-trust organizations design journeys that: minimize handoffs make status visible empower staff to resolve, not deflect  Role of employees  Citizens judge the entire government by the last person they spoke to.  That means trust is delivered—or destroyed—by frontline employees.  Trust cannot exist externally if it doesn’t exist internally.   Digital trust  Digital services don’t build trust by being flashy. They build trust by being predictable. Citizens trust digital services when: forms are clear and don’t ask unnecessary questions errors are explained in plain language progress is visible outcomes are consistent with offline channels.  Nothing destroys trust faster than a website that says one thing, a live agent says something else and a letter says something else entirely different.  To wrap Trust is not owned by the: communications team digital team customer service.  Trust is owned by the operating model.  Government agencies that build trust ask where: do citizens get stuck most often? do we force people to call us? does policy override common sense? do employees feel powerless?  If you want to measure trust, don’t start with surveys--start with friction.  Every unnecessary step, delay, and handoff is a withdrawal from the trust account.  Every clear answer, timely update, and fair outcome is a deposit.  Trust in government services is built quietly--journey by journey.  It’s not about perfection but consistency, transparency, and respect for the citizen’s time and reality.  Once trust is earned, everything else—digital adoption, efficiency, compliance—gets easier. 

AI is not a single thing. It’s not one system. It's also not a magic button you bolt onto a broken process.  When most people say “AI,” they’re lumping together: machine learning predictive analytics natural language processing Generative AI intelligent automation  Each of these has very different implications for government.  The mistake many agencies make is jumping straight to the technology conversation without asking the more important questions: What decisions are we trying to improve? What work is repetitive, rules-based, or data-heavy? Where are citizens experiencing friction or delay?  AI does not replace strategy. It amplifies whatever strategy you already have—good or bad. If your processes are fragmented, AI will scale fragmentation. If your data is unreliable, AI will industrialize bad decisions.  This is why AI in government is not primarily a technology transformation. It is an operating model transformation.   Operations, not chatbots Public attention tends to focus on visible AI use cases:  Chatbots virtual assistants  automated responses.  Those matter—but the biggest impact of AI in government will happen behind the scenes.  Consider operational realities most agencies face: large backlogs manual case processing inconsistent decisioning limited visibility into demand and workload workforce shortages  AI is already changing this in three major ways. First: Intelligent triage and prioritization  AI can assess incoming applications, claims, or requests and: route them to the right team flag high-risk or high-impact cases identify missing information early  This alone can reduce cycle times dramatically—without changing legislation or service promises.  Second: Decision support, not decision replacement In government, AI should rarely make final decisions.   It can: surface patterns humans can’t see provide probability scores highlight anomalies or potential errors  This leads to more consistent, defensible, and auditable outcomes.  Third: Predictive operations Instead of reacting to spikes in demand, AI enables agencies to: forecast volumes anticipate capacity gaps adjust staffing and channels proactively  That is a fundamental shift—from reactive service delivery to managed demand.   The citizen experience  The biggest change AI brings to the citizen experience is not “faster answers.”   Historically, government has been structured around programs, not people.   Citizens are forced to: navigate complex eligibility rules re-enter the same information interact through channels the agency prefers.  AI starts to change that dynamic. With the right data foundations, AI can enable: personalized guidance instead of generic instructions proactive outreach instead of reactive enforcement seamless handoffs across channels and departments.  Imagine a government experience where: citizens are guided to the right service the first time life events trigger coordinated responses repetition and redundancy are designed out.  That is not science fiction but it requires agencies to think in terms of journeys, not transactions.  AI accelerates this shift—but only if the organization has done the journey design work first.  The agencies that struggle with AI adoption won’t fail because of technology—they will fail because they didn’t redesign work.  Governments need to be transparent about: where AI is used what decisions it supports where humans remain accountable  AI done poorly erodes trust quickly. AI done well can actually strengthen legitimacy by making decisions more consistent and fair.   To wrap AI will not make government smaller. It will make government different.  It will make government more predictive and consistent.   The agencies that succeed won’t be the ones with the most advanced algorithms, they’ll be the ones that align technology, operating models, and public values.  

Most government operating models were not designed for the environment we are operating in today.  They were designed for stability.   They were designed for predictability.  They were designed for policy-driven, siloed execution.  Today’s environment demands something very different: citizens expect seamless digital services policy changes are faster and more frequent funding pressures are constant technology—especially AI—is changing how work gets done almost monthly. What Is a dynamic operating model? A dynamic operating model is the way an organization continuously aligns: strategy policy customer needs processes technology people  In real time—or as close to real time as government can reasonably get.  The key word here is dynamic.  This model is designed to change without chaos.  It allows an agency to: respond to new policy direction shift resources to priority outcomes introduce new channels or technologies improve services based on lived customer experience  All without breaking delivery.   Why government needs this now Government agencies are facing a perfect storm.  First, citizen expectations are shaped by the private sector. People compare government services to banks, retailers, and digital platforms—even if that comparison is not always fair.  Second, policy volatility has increased. Programs are launched, amended, or paused faster than ever.  Third, legacy operating models are holding agencies back: siloed program ownership channel-centric delivery rigid funding and workforce models technology that dictates process instead of enabling it  The result is predictable: slow change inconsistent service experiences burnout in frontline staff  frustrated citizens.  A dynamic operating model gives government a way to modernize how it operates, not just what it delivers.   The dynamic operating model  A dynamic operating model as having six integrated components.  1. Clear Outcome-Based Strategy Everything starts with outcomes—not outputs: not “process more applications” not “launch a new portal”  But outcomes like: faster access to benefits reduced administrative burden improved trust in government services  These outcomes guide decisions across policy, operations, and technology.  2. Customer-led service design In a dynamic model, journeys—not programs—are the organizing principle.  That means: mapping end-to-end citizen journeys understanding pain points across channels designing services around life events, not internal structures  Journey management becomes a core capability, not a side project.  3. Agile governance and decision-making Traditional governance is built for control.   Dynamic governance is built for speed with accountability.  This includes: clear decision rights delegated authority where appropriate shorter approval cycles data-driven prioritization  Governance should enable movement—not block it.  4. Modular processes and technology Dynamic models rely on modularity.  Processes are designed in components that can be adjusted without redesigning everything.  Technology is: API-enabled Cloud-based Configurable rather than custom-built  This is what allows agencies to evolve incrementally instead of through massive transformation programs.  5. Workforce Enablement A dynamic model requires a workforce that is: multi-skilled empowered to solve problems supported by automation and AI roles shift from task execution to judgment, exception handling, and service recovery change management is not a phase—it is continuous.  6. Performance management and feedback loops Dynamic operating models are measured and adjusted constantly.  This includes: operational KPIs customer experience metrics employee feedback policy and compliance indicators  The model improves itself over time.  

What omnichannel really means  Let’s start by getting clear: Omnichannel isn’t just offering multiple ways to get help.  It’s about offering connected ways.  When someone starts a process on a website, then moves to a chatbot for clarification, gets a follow-up call from an agent, and ends up submitting documents through a mobile app.  The experience should feel like one single conversation, not four disconnected ones.  Citizens shouldn’t have to repeat information.  Agents shouldn’t have to guess what’s already happened.  And nobody should feel like they’re starting from scratch every time they reach out.  This isn’t a “nice-to-have” anymore.  People interact with banks, airlines, and retailers every day — and these industries have raised expectations. Government has to catch up.    Why government needs omnichannel  Government services are often complex: regulations, eligibility, documentation, and identity verification.   People don’t reach out because they want to. They reach out because they have to.  The burden is on government to simplify.  Think about these real-world scenarios:  Someone starts a benefits application online, but gets stuck on a confusing question.  A person calls a service center to clarify something, then receives a letter in the mail asking for the same information they already submitted.  Or my favorite, the “print this PDF, sign it, scan it, and email it back” request. In 2026...  An omnichannel experience ensures every interaction is informed by the previous one — regardless of channel. That makes service delivery more efficient, more accessible, and more human.  The four pillars of government omnichannel  There are four building blocks I always look for when designing an omnichannel ecosystem for public services:  Unified Identity One login. One profile. Whether you’re online, in person, or calling in — the system knows who you are. This eliminates duplication, errors, and delays.  Shared Context Agents can see your history — what forms you’ve started, what documents you submitted, what chatbot interactions happened earlier that day. This reduces frustration and improves trust.  Seamless Channel Transition Citizens should be able to pick up right where they left off: Start online → continue on live chat Visit in person → get digital follow-up Start by phone → complete on mobile  No resets. No “please explain that again.”  Consistent Policies and Messaging Every channel needs to deliver the same rules, the same answers, the same deadlines.   Conflicting information destroys confidence faster than anything.    One experience. Citizen-focused.  Making it real  Omnichannel transformation doesn’t happen overnight. Here’s how government teams can build momentum:  Start with ONE high-volume journey. Maybe it’s benefits, licensing, permitting, or payments. Don’t boil the ocean — focus where there’s impact.  Map the end-to-end journey. Find the drop-offs, the confusion points, the hand-offs that break the experience.  Integrate data first — channels second. The technology that shares context is more important than the interfaces people see.  Design for accessibility and inclusion. Omnichannel is equal-opportunity service — not digital-only.  Empower employees.   Front-line staff are the glue. Give them tools that show the whole picture.  Measure continually.   What gets measured gets improved.  What is success?  When omnichannel is working, you’ll see: Shorter resolution times Less call volume driven by confusion Higher adoption of digital services Better public trust and satisfaction Lower operational cost 

What Do We Mean by a “Dynamic” Operating Model? A dynamic operating model has three defining characteristics. It: separates what must be stable from what must be adaptable enables rapid reconfiguration of work—not people is managed as a product, not a one-time design  This means: Strategy can shift without rewriting job descriptions New services can be launched without new org charts Capacity can move without months of approval cycles  The key point for today’s episode is you do not design a dynamic operating model -- you plan for its continuous development.  Step One: Anchor the Model in Outcomes, Not Structure  The first mistake organizations make is starting with structure.  Who reports where.   Which division owns what.   Where digital or CX should “sit.”  A dynamic operating model starts somewhere else entirely: outcomes.  Your plan must begin by answering three questions: What outcomes matter most to the people we serve? What outcomes matter most to the organization? Where are those outcomes currently constrained?  In government, this might be: Time to decision Ease of compliance Quality of service recovery  In enterprise, it might be: Speed to market Cost to serve Retention and loyalty  Your operating model exists to reliably produce outcomes under changing conditions.   If the outcomes are unclear, the model will always be sketchy.   Step Two: Identify the “Fixed Spine” of the Organization Every dynamic operating model has a stable foundation.  This includes: Core governance Financial controls Risk management Legislative or regulatory obligations Enterprise platforms and data foundations  Your plan must explicitly document: What cannot change frequently What should not change frequently  This is not a limitation—it’s an enabler. When people know what is fixed, they are far more comfortable adapting everything else. Dynamic organizations are not chaotic.  They are clear about their non-negotiables.  Step Three: Design for Flow, Not Functions  The third element of your plan is shifting how work is organized.  Traditional operating models organize around: functions programs channels  Dynamic operating models organize around value flows.  That means: End-to-end journeys Products and services Capabilities that cut across silos  Your plan should define: The major value streams that deliver outcomes The capabilities required to support those streams How those capabilities are shared, not duplicated  This is where agility actually comes from—not from agile ceremonies, but from reducing handoffs and ownership ambiguity.   Step Four: Build an Evolution Roadmap, Not a Target State  This is the most important shift.  Static operating models aim for a “future state.”  Dynamic operating models plan for perpetual evolution.  Your plan should include: A 12–18 month evolution roadmap Clear hypotheses about what changes will unlock value Lightweight governance for testing and adjusting  Think in terms of: “If we change this capability…” “If we move ownership here…” “If we standardize this platform…”  Then measure, learn, and adapt.  A dynamic operating model is never finished.   To wrap Developing a dynamic operating model is not a design exercise—it’s a leadership commitment.  It requires leaders to: Let go of false certainty Reward learning, not just compliance Invest in capability, not just capacity  

This isn’t just about technology. It’s about how residents, businesses, service providers, and employees interact with government across every channel—phone, web, email, chat, mobile apps, in-person, kiosks, partner portals—everything.  So, how do you align all those channels into a consistent, intentional experience? That’s where a Channel Experience Roadmap comes in.  Why Channel Planning Matters in Government Government clients don’t wake up thinking, “Which channel am I going to use today?” They think: “I need to renew my license.” “I want to file a claim.” “I need help with my payment.”  The channel should never be the focus—it’s simply the path.  The reality is most governments did not design their channels.   They inherited them.  Phone lines existed.   Websites were added.   Portals popped up.   Mobile apps came later.  Suddenly, there was a fragmented system of disconnected experiences.  No wonder residents repeat themselves, employees scramble to find information, and service providers feel frustrated.  The Channel Experience Roadmap is your strategy to bring consistency, clarity, and intentional design into your multi-channel world.  The Five Principles of a Good Channel Experience Before we build the roadmap, let’s agree on what a good channel experience looks like.   It should be: - Consistent – No matter where I start, the information, branding, and process feel the same. Seamless – citizens can move from web to phone without losing context. Directed – channels have clear purposes--governments don’t rely on ‘trial and error.’ Equitable – digital-first does not mean digital-only--accessibility remains core. Measurable – governments can track performance and citizen satisfaction for each touchpoint.  The Four Stages of Building a Channel Experience Roadmap Stage 1: Discovery — Understand Today’s Channel Landscape Start by mapping what you have today. Not just the technology—but what role it plays.  Stage 2: Use data—call volumes, web analytics, customer feedback—but also run workshops with frontline employees, call agents, digital teams, policy staff.  You’re not just mapping channels.   You’re mapping behaviours, expectations, and frustrations.  Define Channel Purpose — Give Each Channel a Job Think of your channels like a team: The website might be for self-service—forms, FAQs, calculators, applications. The contact center might provide guided support for more complex issues. Live chat could be your triage—quick questions before escalating to a specialist. In-person offices might exist for legal processes, accessibility, or trust-building. AI chatbots handle routine transactions and information requests.  By clarifying the role and boundaries of each channel, you help citizens choose the right one—without guessing.   Stage 3: Design the Future State Channel Mix Now, create a blueprint.   Ask: Where should automation live? Where should humans stay central? How do channels support one another? How do we integrate CRM, case management, and knowledge bases for continuity?  For example: A resident starts on the web. The system detects complexity, offers live chat. Chat agent escalates to phone. The agent already sees the full digital history. No repetition. No frustration.  Build the Roadmap — Prioritize, Phase, Align This is where channels meet strategy.  Categorize your roadmap into:  Now (0–12 months): Fix high-friction issues, improve digital content, introduce chatbot pilots, reduce call volume through better web design.  Next (1–3 years): Integrate CRM systems, improve automation, align processes, redesign call center workflows, unify authentication.  Later (3–5 years): Implement AI-driven personalization, omnichannel case tracking, proactive notifications, digital identity integration.  Each milestone should tie back to customer outcomes, not just technology upgrades.    

The current landscape  If you’ve ever worked with a worker’s compensation system — whether you’re a case manager, an employer, or a healthcare provider — you know it can be complex.  Paperwork. Phone calls. Forms that look like they haven’t been redesigned since the 1990s. And long waits for updates or approvals.  Over the past decade, many worker’s compensation boards have made large strides to modernize.  The reality is we’re still in the early stages of digital transformation. Much of the system is still reactive — waiting for an injury, waiting for paperwork, waiting for decisions.  The next wave — powered by artificial intelligence — is going to flip that model.   The AI opportunity Instead of an injured worker waiting days for updates, they receive instant status notifications through a digital assistant — one that speaks their language, understands their claim, and guides them step-by-step through recovery.  AI could review medical notes and match them to prior claims to recommend next steps or identify potential barriers to return-to-work — not to replace case managers, but to augment their judgment.  It’s the difference between a reactive system and a proactive one.  AI can also help identify patterns across industries — spotting emerging workplace risks or predicting where safety interventions will have the most impact before injuries even happen.  Think about that for a second: a worker’s compensation system that prevents injuries, not just responds to them.  The digital worker’s journey  Let’s walk through what a future claim might look like in this AI-powered world.  A worker is injured at work. Instead of filling out forms by hand, their employer logs the incident digitally — or even automatically through connected safety systems.  Within seconds, the worker receives a message on their phone: “We’re here to help. Let’s get started.”  An AI assistant collects basic details — location, injury type, symptoms — and starts a preliminary claim file. It schedules a medical assessment, connects the worker with a nurse advisor, and provides personalized information about expected recovery timelines.  Behind the scenes, AI reviews the report for completeness, cross-checks eligibility, and identifies potential red flags that need a human case manager’s review.  Within hours, not weeks, the claim is in motion.  As the worker recovers, AI tools track progress, identify when return-to-work plans might need adjusting, and alert case managers when human support is most needed.  It’s not just faster — it’s smarter, fairer, and more human.  Data, ethics, and trust This journey hinges on something critical--trust.  We’re talking about sensitive personal information — medical records, income details, workplace data. AI systems must handle this responsibly, securely, and ethically.  Transparency is key. Workers need to understand how their information is being used. Case managers need to see how AI reached its recommendations.  We can’t let “black box” decision-making creep into something as sensitive as worker recovery.  The best systems will build AI with people, not for them — using co-design, testing, and strong privacy safeguards.  The road ahead What does the next decade of worker’s compensation look like?  There will be fewer forms and more conversations.   Fewer delays and more real-time updates.   Fewer silos — and more integrated data across healthcare, employers, and compensation boards.  AI will quietly power the background — predicting, connecting, and simplifying — while humans focus on empathy, fairness, and recovery.  In that future, worker’s compensation won’t just be a safety net. It’ll be a human-centered system — faster, more transparent, and ultimately more caring. 

For most of the last century, healthcare was built around hospitals, clinics, and specialists. You got sick, you went somewhere, and someone took care of you.  But the future? It’s distributed. It’s digital. It’s everywhere.  We’re seeing the rise of virtual care, where patients can consult with doctors from home — and not just for colds or prescriptions. Mental health support, chronic disease management, post-operative follow-ups — all happening online.  In Ontario, for example, telehealth visits skyrocketed during the pandemic and have now stabilized at levels far higher than before. That’s not just a shift in technology — it’s a shift in expectations.  People now expect the same kind of seamless, personalized experiences they get from their bank, their airline, or even their fitness tracker — in their healthcare too.  Then there’s the data side. We’ve entered an era where digital health records, AI, and wearables are merging into something incredibly powerful — a real-time picture of a person’s health journey.  Imagine a future where your smartwatch doesn’t just count steps, but predicts stress patterns--where your electronic health record automatically alerts your care team to subtle warning signs before a crisis.   Think about where AI can personalize your treatment plan based on your genetics, lifestyle, and environment.  That’s the promise of predictive health — care that doesn’t wait for you to get sick.  That promise also brings new challenges such as privacy, interoperability, and trust.  We can’t build digital health on technology alone. We have to build it on relationships — between patients, clinicians, and systems that speak the same language.   Let’s talk about the patient experience — because this is where design really matters.  Often, healthcare feels like a maze. You’re passed from one system to another, one login to another, one referral to another. Digital health gives us a chance to fix that — to make care feel more coordinated, more human.  Imagine logging into one secure platform and seeing your appointments, prescriptions, referrals, and lab results — all in one place. Add in real-time messaging with your care team, personalized health education, and proactive reminders.  That’s not science fiction — it’s happening in places like Estonia, Denmark, and even some Canadian provinces that are piloting integrated digital health portals. When done right, these systems don’t just save time — they save lives. They give patients control.  Of course, technology alone doesn’t guarantee better care. We’ve all seen examples of flashy digital tools that fail to gain traction because they weren’t designed with clinicians in mind, or they didn’t fit into existing workflows.  That’s why the future of digital health depends on co-design — bringing doctors, nurses, patients, and technologists to the same table.  There’s another big shift underway — from treatment to prevention. Digital health enables us to spot trends early — changes in sleep, diet, movement, even tone of voice — that may indicate something deeper.  There are real barriers: Outdated systems that don’t talk to each other. Privacy laws that weren’t built for the age of AI. Clinician burnout and digital fatigue. Technology moving faster than policy.  Governments will have to lead with vision — setting standards, protecting citizens’ data, and ensuring equitable access. Because a digital health revolution that leaves behind rural communities, seniors, or low-income populations isn’t progress — it’s a new kind of divide.  The future of digital health must be inclusive, ethical, and human-centered.   So where does that leave us? We’re at a crossroads — between the healthcare system we’ve always known, and the one we can now imagine.  Digital health has the power to make care more connected, more compassionate, and more effective than ever before.  

Today we are going to talk about how governments deliver services, and what the future holds for those delivery channels.  We hear plenty about “digital government,” “online portals,” or “e-services,” but that only tells part of the story. Behind that is a complex ecosystem of channels—web, mobile, call centers, kiosks, in-person offices, even physical mail—and the big question is--how will that ecosystem evolve over the next 5 to 10 years to meet citizen expectations, build trust, and operate efficiently?  The current state  Before we look forward, it’s helpful to understand where many governments are today—and what’s holding progress back.  Channel fragmentation and legacy systems Many government agencies developed their channels—web portal, phone center, physical offices, mail, etc.—in silos, often tied to legacy IT systems or department boundaries. That leads to fragmentation. Citizens may start an application on a website, get stuck, and have to go to a physical office or call a hotline. That handoff is often awkward and disconnected.  Channel shift and self-service pressures Governments often aim to “shift” users from assisted or in-person channels to digital self-service channels. That is sometimes measured via a “channel shift KPI”—the share of interactions handled online (or “self-service”) versus via in-person or call channels.   The appeal is clear: digital channels scale better, cost less per interaction, and can be available 24/7. But there’s always a base of users who need—or prefer—high-touch support--because of complexity, accessibility, language, or trust issues.  Rising citizen expectations, trust, and adoption gap Citizens expect experiences analogous to private-sector digital services, but adoption is uneven.   In addition, satisfaction with online government services often lags the private sector by more than 20%.   Internal process, culture, and change constraints Even when the vision is there, the execution hits resistance: legacy processes, staff unfamiliar with new channels, budget siloes, legal/regulatory constraints, risk aversion, and procurement issues. Transforming channels isn’t just technology—it’s changing workflows, roles, incentives, and culture.    Emerging trends and the future of channels  Let's look ahead--what are the forces and innovations shaping how governments will deliver services in the coming decade?  AI, automation and conversational agents Artificial intelligence and automation are a central lever. Routine, high-volume inquiries or tasks—“What’s the status of my permit?” or “How do I renew?”—can increasingly be handled by chatbots or voice agents. Deloitte calls this an “AI-amplified future of work,” freeing human staff for more complex or discretionary cases.  Behind the scenes, workflow automation can route, validate, and even auto-resolve cases. This reduces human error and accelerates response times.   Predictive analytics can also anticipate bottlenecks—if filings surge in a region, the system could proactively allocate more resources or roll out an “express lane” channel.  Channel orchestration  Rather than independent silos, future channel delivery will be orchestrated--the citizen can start in one channel and continue in another with full continuity (e.g. start on mobile, pick up with an agent, finish in a physical office).  Designing for channel continuity requires shared session context, identity/authentication, stateful case tracking, and standardized APIs across systems.  To wrap The future of government channel delivery is not about choosing digital over in-person, but about orchestrating a rich, secure, inclusive, and seamless ecosystem of channels—powered by AI, embedded in everyday life, and designed around citizen needs. 

What we mean by “Digital Government 2.0” “Digital government 2.0” isn’t just tech procurement. It’s a shift in how government works: Citizen-centric design — services built around life events: birth, starting school, moving, starting a business, retirement Shared platforms — identity, payments, notifications, document exchange that any department can plug into Data as infrastructure — high-quality, governed data with clear ownership and audit trails Secure-by-default — zero-trust architectures, privacy engineering, and verifiable logs Delivery culture — multidisciplinary teams shipping small, learning fast, scaling what works  Digital is no longer a channel--it’s the method.  Five predictions for 2030  Let’s time-travel to the near future.  Prediction 1: Government AI copilots become mundane—and that’s good Clerks and analysts will use AI copilots for drafting letters, summarizing case files, and routing inquiries—always with human accountability. The win isn’t sci-fi; it’s cycle-time: decisions in days, not months.  Prediction 2: Digital identity goes mainstream, with privacy controls citizens can see Think secure sign-in that travels across services, plus consent dashboards showing who accessed your data and why. Expect strong authentication (passkeys), granular consent, and “data receipts.”  Prediction 3: Services become “event-triggered” Instead of applying for everything, citizens will get proactive offers when the system knows they’re eligible—like childcare benefits after a birth is registered—opt-in, transparent, revocable.  Prediction 4: Interoperability beats modernization We won’t replace every legacy system; we’ll wrap and route. Lightweight APIs, data catalogs, and canonical schemas will let old and new systems talk without million-dollar rewrites.  Prediction 5: Trust becomes the KPI. Yes, we’ll still measure cost and speed. But the north star will be trust—privacy incidents down, resolution times down, satisfaction up. Publish the metrics. Earn the confidence.   Myth vs. Reality  Myth: “AI will replace frontline staff.” Reality: It will augment them—freeing time for judgment calls and complex cases. The value is quality + equity, not headcount reduction.  Myth: “We need a big bang system replacement.” Reality: Modernization via thin slices wins: wrap legacy, expose APIs, migrate workloads incrementally.  Myth: “Privacy and innovation are a trade-off.” Reality: Privacy engineering—differential privacy, role-based access, encryption at rest and in transit—enables innovation by making it safe to connect data.  The risks As always I will give you both sides of the story.  The risks are real: Algorithmic bias — require bias assessments, publish model cards, enable human overrides. Vendor lock-in — insist on open standards, data export, and exit plans. Security debt — patch cadence, red-team exercises, and tabletop incident drills. Digital divide — blend online, phone, mail, and in-person options; fund community intermediaries.  The future of digital government isn’t a shiny app. It’s an operating system for the public interest—compassion baked into code, accountability baked into data, and services that work the first time, every time. That’s the bar. 

Why cross-functional teams matter Let’s start with the “why.”  AI projects in government aren’t like rolling out a new app in Silicon Valley. A model that predicts traffic congestion, or flags fraudulent tax claims, or helps prioritize emergency services—these are high-stakes solutions.  If you only put data scientists in a room, you’ll get technically sound models, sure—but they may not align with policy, may not respect privacy laws, or may simply confuse end-users.  Cross-functional teams bring all the key perspectives together. It’s about ensuring technology serves the mission and the citizen, not the other way around.  Who should be on the team Think of it like building a bridge—engineers alone can’t do it. You need city planners, safety inspectors, and yes, the people who will walk across that bridge every day.  For government AI, here are the core roles: Product Manager – They create the product vision and make all the product decisions Policy Experts and Legal Advisors: They make sure the solution complies with laws, ethical standards, and public mandates. Data Scientists and Engineers: They design and train the models. IT and Cybersecurity Staff: They ensure infrastructure is secure, resilient, and scalable. Frontline Workers or Service Staff: These are the people who actually interact with citizens—whether it’s call-center staff, social workers, or inspectors. They help ground the solution in real-world workflows. Change Management Specialists: Because let’s face it—AI adoption is as much about people as it is about code. Citizen Voice: Whether through advisory panels, user testing, or surveys, the public perspective must be heard.  That combination of expertise is what turns an AI project into a real public service.  Overcoming roadblocks Government projects often stall because of silos, risk aversion, and unclear accountability.  Some ways to overcome this are: Shared Goals and Metrics. Instead of each department measuring success differently, define one mission metric. For example, “reduce wait times for benefits by 30%” rather than just “deploy an AI chatbot.” Agile, Not Just Waterfall. Cross-functional teams thrive when they can test, learn, and adjust. Pilot projects with limited scope are less risky and build confidence. Transparent Communication. Regular stand-ups and open documentation keep everyone aligned. It’s amazing how many issues disappear when legal, IT, and data teams actually talk every week.  To wrap Start small. Don’t aim to “AI-ify” an entire department. Begin with one process, one workflow, one citizen experience. Form a core team. Pick one policy lead, one technologist, and one frontline worker. Expand as you go. Invest in trust. Create spaces where people can challenge assumptions without fear. Government culture can be hierarchical, but innovation requires openness. Celebrate wins. When a small pilot reduces paperwork time by 15%, shout it from the rooftops. Momentum matters.   AI isn’t about replacing public servants—it’s about empowering them. When governments build cross-functional teams, they don’t just deliver technology.   They deliver trust, transparency, and better outcomes for citizens. 

In this episode, we’re going to explore: Why citizen experience is now the north star for government transformation, How AI is being used to improve accessibility, responsiveness, and trust, and What agencies can do right now to start their AI journey responsibly.  The new expectation  Citizens today expect their government to be as responsive as their favorite app.   They want fast, accurate answers — anytime, anywhere.  The problem?   Government systems weren’t built for that. Many are decades old, scattered across silos, and full of friction.  Here is where AI steps in. AI can help government deliver what I like to call “service at the speed of life.” That means anticipating citizen needs, responding instantly, and simplifying complex processes.  For example, when a citizen applies for a permit, pays a tax, or asks a question — they don’t care about which department owns what. They just want a clear answer and an easy experience.  AI gives governments the tools to provide that — by connecting data, automating routine tasks, and delivering personalized, human-like interactions 24/7.  How AI is transforming the citizen experience Intelligent Virtual Agents. These are more than just chatbots. They use natural language understanding to handle thousands of different questions — from “What’s my application status?” to “How do I renew my license?”  In Canada, for example, several departments are using AI agents to reduce wait times and free up human staff for more complex cases. In some cases, citizens get answers in seconds instead of waiting hours on hold.  Predictive and proactive services Imagine a world where the government not only responds to citizens, but anticipates their needs. AI can analyze patterns to identify when someone might need help — like reminding a senior about a benefit renewal, or notifying a driver that their license is about to expire.  This is where AI can make government feel truly human — not by replacing empathy, but by enabling it at scale.  Accessibility AI-powered translation, voice recognition, and text simplification tools are making government services more inclusive than ever before. Whether someone speaks a different language, has low vision, or struggles with complex forms — AI can bridge that gap.  When governments use AI this way, they’re not just improving efficiency — they’re building equity into the system.  Building trust and transparency Governments can’t simply roll out AI and hope for the best. Citizen trust is everything. And if AI is seen as secretive or unfair, that trust can erode fast.  That’s why transparency is key. Citizens should know when they’re interacting with AI and understand how their data is used.  Explainable AI — systems that can describe how they make decisions — will be crucial for maintaining accountability.  Data privacy must be non-negotiable. Governments need strong governance frameworks that clearly define what data is collected, how it’s protected, and how it’s used to improve services — not to profile or exclude anyone.  AI should never be about replacing human judgment, but about enhancing it — giving public servants better tools to serve people with speed, empathy, and fairness.  Getting Started — A Playbook for Governments Step 1 — Start with the citizen journey. Don’t start with the tech. Start with the problem. Identify the biggest pain points for citizens — maybe it’s long call wait times, confusing forms, or inconsistent information. Then ask: how can AI help solve this problem?  Step 2 — Build small, scale fast. Pilot AI in one service area. For example, an AI assistant for unemployment benefits or driver’s license renewals. Measure the results, get feedback, and scale from there.  Step 3 — Train and empower employees. AI works best when public servants understand how to use it. Investing in digital literacy and AI training helps staff become partners in innovation, not victims of it. 

The Changing Role of Contact Centre Agents If we rewind 10 or 15 years, the job of a contact centre agent was often about following a script. You answered the call, read from the knowledge base, and handled routine requests.  Today, automation and AI have taken over those routine, repetitive interactions. Customers reset their passwords online. They get status updates through a bot. They pay bills with an app.  That means the calls that do reach a live agent? They’re harder. They’re higher stakes. And they almost always require judgment, empathy, and critical thinking. So the role of the agent has shifted from “transaction processor” to “problem solver, advocate, and brand ambassador.”   Skill #1: Empathy and Emotional Intelligence The number one skill that matters right now is empathy. When a customer reaches a live agent, chances are they’re already frustrated. They may have tried self-service, the website, or a chatbot, and now they’re here—looking for help from a real human being.  Agents who can listen actively, acknowledge emotions, and validate concerns make the biggest impact. Customers don’t just want the problem solved—they want to feel heard.  That’s where emotional intelligence comes in: reading tone, sensing frustration or confusion, and adjusting your communication style to match the customer’s state of mind.  In a world full of automation, empathy has become the ultimate differentiator.   Skill #2: Critical Thinking and Problem Solving The second critical skill is problem solving. Because the easy questions—the “what’s my balance” type of queries—never make it to an agent anymore. What’s left are the complex issues that require judgment, creativity, and decision-making.  That means contact centre professionals need to be comfortable navigating ambiguity. They need to know how to look beyond the script, connect the dots, and sometimes even challenge the process to do what’s right for the customer.  It’s not just about answering questions—it’s about owning the customer’s problem until it’s solved.   Skill #3: Digital Fluency The third skill set is digital fluency. Customers are omnichannel. They may start on chat, move to email, then pick up the phone. Agents need to be comfortable switching between platforms, handling multiple systems, and even working alongside AI assistants.  Digital fluency doesn’t just mean using tools—it also means understanding how customers use digital. Agents who can guide a customer through a process online, explain how to use self-service features, or troubleshoot an app issue provide enormous value.  The contact centre of today isn’t just about phones—it’s about navigating a digital ecosystem.   Skill #4: Adaptability and Continuous Learning The fourth essential skill is adaptability. Let’s be honest—technology in contact centres is changing fast. New AI tools, new CRM platforms, new workflows. The half-life of skills is shrinking.  The best agents today are those who can learn, unlearn, and relearn quickly. They’re curious. They don’t just resist change—they lean into it. And adaptability isn’t just about technology. It’s also about adapting to new customer expectations, new policies, even unexpected situations like service outages or crises.  Leaders should be building a culture where learning is continuous and adaptability is celebrated.   Skill #5: Communication Mastery Whether it’s voice, chat, or email, clear communication is the foundation of great customer experience.  It’s about choosing words that build trust, explaining complex things simply, and avoiding jargon. And in digital channels like chat, it’s about striking the right balance between speed, accuracy, and tone.  Agents who can communicate with clarity and warmth stand out—and customers notice.   

For decades, it’s been human agents answering phones, handling emails, and more recently, chat messages. Over time, automation has played a bigger role—IVRs, chatbots, even self-service portals.  With generative AI and agentic AI, we’re seeing something much bigger. These systems aren’t just automating routine tasks—they’re becoming intelligent partners that can support agents in real time, anticipate customer needs, and even orchestrate workflows across multiple systems.  The question now is -- How do we design a future where AI enhances the human role rather than diminishes it?  From tools to teammates Traditionally, AI was a tool -- you used it to search a knowledge base or triage an email. Today, AI is moving into the role of a teammate. Imagine an AI that sits alongside an agent during a call as it: listens to the conversation in real time retrieves a customer’s history in real time suggests the next best action flags compliance risks.  After all this, when the call ends, it: writes the summary updates the CRM sends a follow-up email—all automatically.  What does that mean for the human agent?  It means less time clicking between multiple screens and more time focusing on the customer’s tone, empathy, and the relationship.  This is the future of partnership: AI handling the heavy lifting of process, humans handling the heavy lifting of connection.  Evolving the agent role This shift changes what it means to be an agent. If AI is taking care of the repetitive work -- the agent’s role becomes more specialized, more consultative.  Instead of being judged on call volume, agents will be valued for: Problem-solving--tackling the nuanced issues AI can’t resolve. Emotional intelligence:--knowing when a customer is frustrated, anxious, or vulnerable—and responding with empathy. Trust-building--customers want to feel heard by a real person, especially in moments that matter.  Agents are evolving to become experience managers, brand ambassadors, and problem solvers at a higher level.  It also means we need to invest in new training, new performance metrics, and new career paths. Without this agents will feel like they’re competing with AI instead of collaborating with it.  Building trust Customers need to trust that when they interact with AI, it’s accurate, transparent, and respectful of their data.  Agents need to trust that AI isn’t a threat to their jobs but a partner that makes their work more meaningful.  Leaders need to trust that the AI systems they deploy are explainable, compliant, and reliable.  Partnership only works if all three levels of trust are in place. Without it, you risk resistance, from: customers who don’t want to talk to “a bot,”  agents who fear obsolescence,  regulators who question your transparency.  Where are we headed? Proactive AI--not just responding, but predicting customer needs before they reach out. Real-time coaching--AI whispering in the agent’s ear with suggestions, compliance checks, and empathy prompts. Seamless multimodality--AI enabling a customer to move from chat to voice to video with zero friction—and the agent having full context every step of the way. Shared accountability--service outcomes measured not as “agent success” or “AI success,” but as team success. To wrap AI is an enabler, not a replacement. It frees humans from repetitive work so they can focus on empathy and problem-solving. The agent role is evolving. We need new training, new metrics, and new career paths that reflect the shift from transaction handling to relationship building. Trust is everything. Customers, agents, and leaders must all believe in the partnership for it to succeed. The contact centre of the future isn’t about humans versus machines. It’s about designing a partnership where each does what it does best—AI with speed, scale, and precision; humans with empathy, judgment, and connection. 

Why an AI strategy matters in government Citizens don’t wake up saying, “Today I’m going to experience government.”  They wake up needing something: renewing a driver’s license, applying for benefits, paying taxes, asking questions about permits. These aren’t just transactions—they’re moments that shape how people trust government.  The problem citizens have is many agencies have legacy systems, siloed data, and outdated processes. Citizens get stuck bouncing between websites, waiting on hold, or mailing paper forms. That’s not just inefficient—it erodes trust.  This is where AI comes in. With the right strategy, AI can: Automate routine interactions so staff can focus on complex cases. Provide 24/7 support through intelligent chat or voice assistants. Analyze patterns in service requests to predict citizen needs. Translate services into multiple languages instantly. Improve accessibility for citizens with disabilities.  That is only with the right strategy. Without one, you risk pilot projects that fizzle, tools nobody uses, or worse—AI systems that feel cold, biased, or untrustworthy. That’s why agencies need a clear, thoughtful roadmap for AI in customer experience.  Principles of an AI strategy Citizen-Centric Design – Start with citizen journeys, not technology. What are the pain points? Where is the friction? What would make someone’s experience feel simple, transparent, and respectful? Trust and Transparency – Citizens need to know when they’re interacting with AI, how their data is used, and that privacy is protected. Trust is non-negotiable in government. Equity and Accessibility – AI must serve everyone, including people with disabilities, limited digital literacy, or those in rural areas. This isn’t just good practice—it’s essential for public service. Human + AI Partnership – The goal isn’t to replace government workers. It’s to free them from repetitive tasks so they can handle the complex, human-centered work where empathy matters most. Governance and Accountability – Clear rules for data, model training, monitoring bias, and auditing outcomes. AI in government has to be held to a higher standard.  Building an AI Strategy Step 1: Define the vision and goals. Is the aim to reduce call center wait times? Increase self-service adoption? Improve accessibility? Don’t start with “we want AI.” Start with the outcomes that matter to citizens.  Step 2: Map the customer journey. Look at where people struggle most—form complexity, long response times, lack of status updates. These are prime candidates for AI solutions.  Step 3: Build a data foundation. AI is only as good as the data behind it. Agencies need to clean, standardize, and integrate their data across silos. Think of it as plumbing—you can’t deliver water if the pipes are rusty and leaking.  Step 4: Start small, then scale. Pilot AI in a high-volume, low-risk area—like answering FAQs through a virtual assistant. Measure the impact, learn, and iterate. Then expand to more complex use cases.  Step 5: Train and support staff. Change management is crucial. Employees need to understand how AI supports their work, not threatens it. Upskilling teams builds confidence and reduces resistance.  Step 6: Establish governance. Who oversees AI projects? How are algorithms tested for bias? How do you audit decisions? Governance must be part of the strategy from day one.  To wrap Start with citizens, not technology. Build trust through transparency and accountability. Ensure equity and accessibility for all. Position AI as a partner, not a replacement, for staff. Lay a strong data foundation and scale thoughtfully.  Government agencies have a unique responsibility—not just to deliver services efficiently, but to do so in a way that strengthens trust in public institutions. AI, guided by a smart strategy, can help rebuild that trust by making interactions faster, fairer, and more human. 

Customer Experience Platforms A CX platform is a technology foundation that allows organizations to manage, analyze, and optimize every interaction they have with their customers across multiple channels.  Think of it like a control tower for the customer journey. It doesn’t just answer a phone call or manage a chat session—it connects everything: email, voice, social media, mobile apps, websites, and even in-person service.  The key is integration. Without it, you’re left with silos—contact centers doing one thing, marketing doing another, service teams flying blind. A customer experience platform pulls all that together into one consistent view, so customers feel like they’re dealing with one organization, not six different departments.   Why They Matter  Customer expectations have changed. People expect personalization, speed, and seamless transitions from one channel to another. Your customers don't care how complex your organization is behind the scenes—they just want their problem solved or their need met.  CX platforms are how organizations keep up with these rising stakes. They provide real-time data, they use AI to predict customer needs, and they allow you to proactively address issues before they turn into complaints.  The CX Platform There are a few core components: Omnichannel Communication – The ability to handle phone, chat, email, social, and messaging apps all in one place. Customer Data Management – Centralized profiles so you know who you’re talking to and what their history is. Analytics and Insights – Real-time dashboards that track sentiment, wait times, and resolution rates. Automation and AI – Chatbots, intelligent routing, agent assist, and predictive analytics. Integration Capabilities – APIs and connectors that tie into your CRM, ERP, or other back-end systems.  Put all of this together, and you’ve got a platform that allows you to orchestrate the entire customer journey, rather than just react to it.  Pitfalls and Misconceptions Buying the platform but not fixing the process. Technology won’t solve broken workflows. If your teams don’t collaborate, a CX platform just makes the dysfunction more visible. Over-customizing. Many organizations buy these powerful platforms and then spend millions customizing them, only to end up with a system they can’t upgrade. Ignoring the human side. Even with AI and automation, your frontline employees need training, empowerment, and tools that actually make their jobs easier.   A CX platform is only as good as the strategy behind it.  Getting Started Define the customer journey. Map out where your pain points are today. Don’t start with the tech—start with the customer. Align across departments. Marketing, sales, and service all need to be in the same room. Start small, scale smart. Maybe launch with chat and self-service, then expand to voice or proactive outreach. Measure success. Look at metrics like customer effort score, first contact resolution, and retention. Not just cost savings.  Remember, CX platforms aren’t about chasing shiny tools. They’re about delivering outcomes that matter—loyalty, trust, and long-term relationships.  To Wrap  A customer experience platform is not just another piece of enterprise software—it’s the foundation for how your organization connects with the people it serves.   Done correctly, it creates seamless experiences, empowers employees, and delivers real business value. Done wrong, it becomes just another expensive system that nobody uses.  Start with the customer, not the technology. The platform should enable your strategy, not define it. 

Agentic AI is the next evolution—it’s not just about automation, it’s about intelligence, adaptability, and agency. It’s about creating government services that feel less like bureaucracy and more like a helpful guide, walking you through what you need, when you need it.  What do we mean by Agentic AI? Traditional AI in government might look like a chatbot on a website that answers simple questions: “What hours is city hall open?” or “Where do I get a passport application?” Useful, but super limited.  Agentic AI takes this much further. It doesn’t just answer questions—it acts. It understands context, holds goals in mind, and can take steps on behalf of the citizen. Think of it like a digital case worker who knows the rules, can fill out forms, can connect systems, and can anticipate next steps.  This is the big leap: from static responses to dynamic problem-solving.   Why do Government need it? Governments, more than any other organizations, deal with complexity. Citizens have to navigate countless forms, eligibility requirements, and departments that don’t always talk to each other.  This creates friction—long lines, confusing websites, and frustrating phone calls. But citizens aren’t customers who can just “go somewhere else.” They rely on government, whether it’s renewing a driver’s license, applying for benefits, or paying taxes.  Agentic AI offers a path to reduce friction, increase trust, and deliver services faster.   What makes Agentic AI different? There are three big shifts that agentic AI brings to government: Goal-oriented service. Instead of citizens figuring out which department to go to, AI agents focus on the outcome: “I need to register a business” or “I need healthcare coverage.” The agent handles the routing Autonomy. These agents can complete tasks on their own—filling out forms, checking eligibility, scheduling appointments Proactive engagement. Instead of waiting for citizens to come to them, governments can use AI to send reminders: “It looks like your child is turning six—here’s how to register for school.” Or “Your permit is about to expire—let’s renew it now.”  That’s a big change. Government moves from being reactive to being anticipatory.  Challenges to consider To be clear, there are challenges.  Data silos. Government systems are often fragmented. For AI to be effective, it needs access to connected data. Trust and transparency. Citizens need to know when they’re interacting with AI, how their data is being used, and that privacy is protected. Equity. We must ensure agentic AI works for everyone, including those without digital literacy or access to technology.  If not managed carefully, AI could reinforce bureaucracy instead of removing it.  That’s why governance, oversight, and ethical design matter so much.   The road ahead Governments don’t need to wait ten years for this future. We’re already seeing pilot programs—digital assistants in tax agencies, AI-driven case management in social services, and even agentic AI prototypes for public health.  The real work now is scaling these tools responsibly. That means building a foundation of data interoperability, clear AI governance policies, and human oversight.  It also means rethinking the role of public servants. With AI handling repetitive tasks, employees can spend more time on empathy, complex problem-solving, and policy innovation.  To wrap Agentic AI can transform the citizen experience by making government: Simpler – guiding people through complexity. Faster – automating forms and workflows. Smarter – anticipating needs before they become problems. 

What do we mean by a frictionless? Frictionless doesn’t mean invisible. It doesn’t mean people never interact with government. It means interactions are smooth, intuitive, and require as little effort as possible from the customer.  Think about ordering a ride through an app: one click, and everything else happens behind the scenes. Imagine if renewing your driver’s license felt that easy.  The goal isn’t just speed—it’s reducing frustration, minimizing repetitive steps, and making sure the citizen feels confident and cared for during the interaction.  Why governments struggle with customer experience? Complex regulations – Services are bound by laws and policies that aren’t always designed with the end user in mind Legacy systems – Outdated IT infrastructure makes integration hard Siloed departments – Citizens don’t care about which ministry or agency owns a service. They just want one simple interaction. But inside government, services are fragmented High demand and limited resources – Millions of people need help, but staff numbers are finite  All of this creates friction: long wait times, confusing forms, and repeat calls or visits just to get something done.  Enter AI Agents This is where AI agents come in.  An AI agent is more than just a chatbot—it’s an intelligent, context-aware assistant that can understand natural language, pull information across systems, and guide the user to resolution in real time.  For example: Instead of waiting on hold, a resident could ask an AI agent, “Do I qualify for this housing program?” and instantly get a personalized answer based on eligibility criteria.  If citizens need to upload documents, the AI can walk them through step by step—no PDF instructions, no guessing.  If the case is too complex, the AI seamlessly escalates to a human agent with all the context already summarized, so the person doesn’t need to repeat themselves.  That’s frictionless.  Use cases in government Let’s look at a few high-impact areas where governments are already experimenting with AI agents:  Licensing and Permits – From business registrations to fishing licenses, AI can make application and renewal processes self-service and error-free Social Services – Eligibility checks, appointment scheduling, and benefit status updates can be handled 24/7 by AI, reducing pressure on caseworkers Immigration and Travel – AI can answer real-time questions about application status, required documents, or processing times, reducing uncertainty Tax Services – Instead of waiting on the phone during tax season, citizens can get accurate guidance instantly  Each of these saves time for the resident and frees up human workers to focus on complex or sensitive cases.  Making it work Of course, it’s not enough to just plug in AI and hope for the best. Governments need to design with intention.  The five keys to success are: Human-centered design – Start with the citizen journey. Map the pain points, then design the AI experience to remove them Data integration – AI is only as good as the data it can access. Breaking down silos between departments is critical Transparency – People need to know when they’re interacting with AI and trust the answers they’re receiving Accessibility – AI agents must work across languages, channels, and devices—so no one is left out Human backup – AI should empower people, not replace them. The best experiences are hybrid—AI handles the simple, humans handle the complex.  The payoff Faster service – Wait times drop from weeks to minutes Greater trust – Citizens feel seen and valued when government “just works” Operational efficiency – Agencies reduce costs and staff burnout by automating routine tasks Equity – AI can help level the playing field by giving consistent, accurate information to everyone.  A frictionless experience strengthens the social contract. When government is easier to work with, people engage more, comply more, and trust more.  

What Is Customer Experience Management?  Customer experience management is the discipline of understanding, designing, and optimizing every interaction a customer has with your brand—across channels, over time.  It’s not just about having a call center or a website—it’s about orchestrating a journey that’s seamless, personalized, and responsive to the customer’s needs. CXM includes three big components: Journey mapping – identifying key customer touchpoints Listening and measuring – collecting feedback, analytics, and sentiment Acting on insights – using data to improve and personalize service  Great CXM is proactive, not reactive. It’s about anticipating needs before the customer has to ask.  Why CXM Often Falls Short Most organizations still struggle with CXM because they confuse it with customer service. CXM is not just about solving problems—it’s about preventing them.  Here are a few common pitfalls: Siloed departments that don’t share customer data Inconsistent experiences across channels Metrics that focus on internal efficiency, not customer satisfaction Not listening to the customer voice at scale  The New Rules of Engagement  Let’s talk about what good CXM looks like in 2025. The expectations have changed: Omnichannel is a must – Your customers expect to move from web to chat to phone without repeating themselves Speed + empathy = satisfaction – Fast service matters, but so does making the customer feel heard Personalization isn’t creepy—it’s expected – Use data to show you understand your customer’s history and needs AI is the co-pilot, not the replacement – Use automation to make agents faster and more effective, not to eliminate human touch Forward-thinking organizations are using customer journey analytics, real-time feedback loops, and AI-driven insights to constantly iterate and improve  Building a CXM Strategy  What can you do today to get better at customer experience management?  Map your customer journeys—know where the friction is Break down data silos—connect your systems Implement real-time feedback channels—voice of the customer tools Use AI to surface insights—but always validate with humans Empower frontline staff—because great CX is delivered by people, not systems  CXM isn’t a one-time project. It’s a mindset. A way of working. A commitment to being better every single day. 

People don’t care about channels. They care about outcomes. They just want quick, accurate help—whether it’s on the phone, online, chat, AI self-service, or in person.  That’s where AI-powered omnichannel experiences come in.  What Does Omnichannel Actually Mean? Omnichannel isn’t just about being available on lots of channels. It’s about seamlessly connecting those channels so the experience feels continuous and  consistent.  For governments, this might mean a citizen starts a chat on the website, gets an update later via SMS, and then finishes the process over the phone—with no need to repeat themselves or restart the interaction.  This is where AI becomes a game-changer—because it can integrate, automate, and personalize across all those channels at scale.  The Challenge Governments Face Governments aren’t like startups. They’ve got: Legacy systems Siloed departments Compliance and privacy rules Tight budgets High expectations from the public  Delivering a smooth omnichannel experience across all that? It’s not easy. Governments can't rip everything out and start over. With the right AI tools and strategy, they can layer intelligence onto existing infrastructure to drive better service.  How AI Enables Omnichannel for the Public Sector 1. Unified Virtual Agents AI-powered virtual assistants can operate across web chat, SMS, email, and voice. With proper integration, they can access case data, answer questions, and complete simple transactions—24/7. When the AI hands off to a human, the full context is preserved. 2. Natural Language Understanding (NLU) Citizens don’t always know the right “terms” to use. AI can interpret plain language across channels, whether someone says, “I lost my health card”, “I need a replacement,” or “I can't find my ID.” 3. Predictive Routing and Sentiment Analysis AI can detect frustration in voice or text and escalate to live help. It can also route inquiries to the right department before a human even picks up. 4. Personalized Outreach Through machine learning and analytics, AI can segment citizens and send reminders or nudges through their preferred channel—whether it’s email, app notifications, or even automated calls. For example: “It’s time to renew your vehicle registration.” 5. Analytics and Feedback Loops Governments can use AI to analyze interactions across all channels, spot trends, and identify areas for improvement—fast.  For Leaders 1. Start with the citizen journey Map out common use cases and pain points. Look for where people drop off, get confused, or need to switch channels. 2. Start small Begin with one service or department and expand. Omnichannel isn’t built overnight—it evolves iteratively. 3. Break down silos Create cross-functional teams that include IT, service delivery, policy, and communications. AI only works if the data and processes behind the scenes are aligned. 4. Choose tools that integrate Look for AI platforms that can connect across existing CRM, contact center, and web systems—not just one shiny point solution. 5. Be transparent Let users know when they’re interacting with AI—and why. When done right, this builds trust.  To Wrap The future of public service is not just digital—it’s connected.  By using AI to create a seamless experience across web, phone, chat, and in-person interactions, governments can: Reduce frustration Improve access Free up staff time Deliver better outcomes for the people they serve  AI won’t fix everything—but when used thoughtfully, it can help governments meet people where they are—and carry the conversation across every channel. 

We’ve come a long way from static IVRs and robotic scripts. Now we’re staring down a future where AI doesn’t just respond—it anticipates, emotes, adapts, and collaborates.  What’s Next in AI: Proactive, Emotional, and Agentic Let’s start with what’s coming around the corner.  We’re moving from reactive AI—responding to questions and routing calls—to proactive AI. Imagine a contact center that knows a customer is likely to churn before they even say a word. AI systems will use behavioral signals, sentiment trends, and historical data to predict issues and offer personalized solutions before customers reach out.  Next is emotional intelligence. Generative AI is can understand tone, intent, and even empathy in real-time. Voice analysis, sentiment detection, and dynamic response generation will allow bots to sound more human—and more importantly—be more human in their interactions.   That means recognizing frustration, expressing understanding, and escalating at just the right moment.  Finally, we’re entering the era of agentic workflows. These are AI agents that don’t just answer a question—they act. They navigate systems, update records, draft follow-ups, trigger refunds, and even collaborate with other agents—human or machine—to solve complex problems. This is where generative AI meets automation in a powerful, orchestrated way.  The Role of Generative AI and Multimodal Interactions Let’s talk about the engine driving this evolution—Generative AI.  It’s not just about chatbots anymore. GenAI is enabling systems that can: draft personalized emails based on a conversation. summarize long service interactions instantly. translate customer intent into backend tasks. generate knowledge base articles or training scripts on demand.  Even more transformative is the shift to multimodal AI. These are models that don’t just understand text—they process voice, images, documents, and even video.  Imagine a customer sending a picture of a broken product. AI: analyzes it confirms warranty status, and initiates a replacement—without human intervention.   Imagine a voice call where the AI: picks up on frustration adjusts its tone, and  flags the interaction to a supervisor in real time.  We’re heading toward seamless, channel-agnostic experiences powered by AI that understands in every dimension.  How Leaders Can Prepare Here’s the part that’s easy to overlook: how do we prepare?  It starts with governance. Leaders need to define guardrails around data privacy, model usage, escalation paths, and ethical considerations. Without structure, it’s chaos.  Next, skills and training. This future isn’t about replacing agents—it’s about augmenting them. Invest in training your workforce to work with AI: interpreting insights, validating responses, and using AI as a co-pilot, not a crutch.  Then there’s infrastructure. Many contact centers are still running on legacy systems that can’t integrate with modern AI tools. Think modular, API-driven, cloud-first architecture. It’s not sexy, but it’s essential.  Finally—partnerships and pilots. Don’t wait for perfection. Start small, iterate fast, and learn in the real world. That’s where true transformation happens.  Strategy Over Shiny Tools AI is not the strategy It’s a tool. Don’t chase the trend—define the outcome you want, then use AI to help get you there.  Don’t over-automate AI should elevate the human experience, not eliminate it. Use it to remove friction, not empathy.  Balance innovation with intention The best contact centers of the future will be those that marry cutting-edge tech with rock-solid fundamentals—governance, empathy, and a relentless focus on the customer.  The future isn’t five years away—it’s here Your competitors are piloting proactive AI, deploying GenAI assistants, and rethinking workflows. If you're still evaluating, you’re already behind.  

Today, we’re breaking down: common mistakes organizations make when implementing AI why so many AI pilots fail to scale how to build a strong AI foundation from the start what we can learn from those who’ve already stumbled.  Implementation mistakes 1. Bad Data: AI is only as good as the data you feed it. If your data is outdated, incomplete, or inconsistent across systems, your AI is going to reflect that. I’ve seen bots go live with training data that didn’t reflect the actual questions customers ask. Result? Frustrated users, high abandonment, and no ROI.  2. No Change Management: You can’t just plug in AI and expect magic. If your teams aren’t trained, if there’s fear, confusion, or resistance — adoption will stall. Frontline agents need to know how the AI helps them, not replaces them. Leaders need to communicate clearly. Change management isn’t optional — it’s essential.  3. Overhyping AI: Some vendors and internal champions oversell AI as the silver bullet. But AI isn’t going to fix a broken process — it’s going to expose it. You need to set realistic expectations. Start small, prove value, then scale.  Why AI pilots fail to scale You launch a chatbot in one department. It goes okay. Then when you try to scale everything breaks.   Why?  Lack of strategic alignment The pilot solved a local problem — but didn’t fit into a broader enterprise strategy. It was a siloed win with no path to broader adoption.  No operational readiness Many organizations forget to build the support systems around the AI. Who updates the bot content? Who retrains the model? Who measures success? AI at scale needs ownership, process, and infrastructure.  Culture and leadership If leaders don’t champion the value, if users don’t trust it, the pilot stays stuck in in pilot mode. To scale AI, people need to believe in it — and see the benefit.  Building the right foundation So how do you avoid these pitfalls? It starts with building the right foundation.  1. Governance You need clear roles and responsibilities: Who owns the AI strategy?  Who signs off on changes?  How do you ensure ethical use, compliance, and privacy?  Governance isn’t bureaucracy — it’s how you scale responsibly.  2. Training Train your teams. Not just the tech teams, but your agents, managers, and executives. Everyone needs a base level of AI literacy. If your employees don’t understand the AI, they won’t use it. Worse — they’ll work around it.  3. Iteration AI is not a “set it and forget it” solution. You need a feedback loop. Look at performance. Talk to users. Iterate often. The most successful AI deployments I’ve seen have one thing in common: a culture of continuous improvement.   Learn from other companies You don’t have to learn everything the hard way. There are case studies, post-mortems, and war stories out there. Learn from them.  A major telco launched a voice bot without involving the contact center. It worked in the lab, but in production? Callers hated it. Agents weren’t trained to take over from the bot. NPS dropped like a rock. Lesson? Bring frontline teams in early and often.  A government agency tried to automate benefit eligibility using a model trained on old data. What happened? The AI reinforced biases. Applications from vulnerable groups were flagged more often for review. Public trust eroded. Lesson? AI needs oversight, diverse data, and ethical review.  These aren’t tech failures — they’re leadership failures and they’re preventable.  To wrap AI has enormous potential, but it’s not plug-and-play. Avoiding the pitfalls starts with: treating data like an asset investing in change management being realistic about what AI can — and can’t — do building a foundation rooted in governance, training, and iteration. remembering, you’re not alone. Learn from others. Share your wins and your stumbles.