An annual ambition
Name the outcomes that matter, the commitments you must keep, and the capabilities your people need to grow.
Rethink the work, the capabilities, and the plan together. Build an approach around your industry, your organization, and the people who will carry the change.
Start a conversationAgree what should get better, how to measure it, and which work could change.
Revisit the assumptions behind the plan.
Bring leaders, HR, operations, IT, and people doing the work together. Decide what work to redesign or retire, how responsibilities will change, and which capabilities and investments the change needs.
A prioritized workflow portfolio, baseline measures, supervision responsibilities, protected learning needs, and a review cadence fitted to your context.
Build skills around a real problem.
Develop technical talent through Microsoft or Google pathways, and business leaders through the 120-hour Business-to-FDE Leadership Lab with Microsoft 365, Codex, GitHub Enterprise, and Azure.
Practical skills demonstrated through a project, feedback, and a clear review rubric.
Give useful experiments a way forward.
Pair business experts and technical learners with an engineering reviewer around a bounded use case.
A prototype, evaluation evidence, and the documentation needed for the organization’s delivery process.
A plan built around yesterday’s workflows and roles can miss tomorrow’s opportunities. Connect strategy, workforce development, and AI investment in a plan that can respond to evidence.
Name the outcomes that matter, the commitments you must keep, and the capabilities your people need to grow.
Choose a workflow, establish a baseline, assign an owner, and agree an investment and learning goal. A 90-day cycle is one option.
Review quality, adoption, full costs, and effects on people. Decide whether to scale, revise, hold, or stop—and update the plan.
We call this Frontier Activation: connecting business outcomes, human capability, intelligent execution, and organizational readiness. An initiative should improve the work as a whole. Include review effort, exceptions, and employee workload in the decision to expand it.
Read our latest thinking on work redesignWe begin with the actual work, available data, existing systems, workforce needs, and consequences of error. Explore how those conditions can change the learning and the project.
Use agents to gather approved material and prepare a draft, while professionals own interpretation and client commitments.
Examples for discussion, not ready-made implementations. Company size, systems, workforce needs, and local requirements change the design.
The workflow and intended outcome. The roles and capabilities involved. The approved environment and review responsibilities. The evidence needed for an investment decision. The pace and format of learning.
Agree on the environment, data, tools, review criteria, and ownership before the first prototype. The people closest to the work stay involved through testing and adoption.
Your engineering team decides whether to accept, revise, or rebuild the implementation. Production release follows your established process.
Explore each step of the journey
Map the workflow and its exceptions. Agree on who should benefit, what success looks like, and where human judgment must stay involved.
Build something small enough to test. Use approved data and tools, and record the permissions, prompts, integrations, and assumptions behind it.
Try realistic cases and failure paths with users. Document limitations and human approvals so engineering and security can make an informed decision.
Your engineering team accepts, revises, or rebuilds the solution through its normal release process. Track quality, adoption, cost, and the impact on people.
Measure accepted outcomes, quality, adoption, review and rework effort, and full operating costs. Examine the skills people demonstrate, the opportunities they gain, and how their workload changes.
Time saved is an opportunity to create value; it is not automatically a cash saving. Begin with a bounded project and an accountable sponsor. Learn from the results before expanding, and make the next decision visible to the people affected.
Model your workforce scenario