AI Strategy and Transformation
Which parts of the work should change, and how far? FAR places every AI opportunity at one of three levels of ambition: Fix what is broken, Accelerate what works, or Reimagine how the outcome is produced.
The work in context
Automating a task can leave the workflow around it untouched. Teams finish their part faster while queues, handoffs and exceptions still set the pace. Or they use AI to speed up a process whose assumptions stopped holding years ago. Work redesign starts from the outcome: which work changes, where people keep their judgment, and how responsibility moves.
FAR is how we frame that choice. We place every opportunity at one of three levels, Fix, Accelerate or Reimagine, and the level sets the ambition, the investment and the evidence the decision needs. Work redesign runs as a focused engagement or inside AI Solution Blueprinting. It shapes the business process and its roles. The Engineering Operating Model shapes how the software behind it is built and released.
A view of the work
Working together
Remove the specific source of friction that holds the work back, and keep the workflow as it is. Typical targets are intake, information quality and handoffs. We confirm the defect matters before deciding whether AI is the right repair.
Raise the speed or capacity of work whose purpose still holds. We measure the full downstream effort, including review and exceptions, because faster drafting only helps when the work can move through the rest of the process.
Design a different way to reach the outcome, with a new task sequence, new roles and new decision points. Reimagine carries the largest value and the largest change, so we test feasibility, adoption and accountability before it becomes the plan.
Weigh each option against business evidence, constraints and the outcome you want. Define the future workflow and its success measures, then connect the choice to Blueprinting or Engineering where it needs building. Assumptions and client decisions go on the record.
Outputs and decisions
Example
Take a quotation process. Fix closes the gaps in request information before anyone starts work. Accelerate helps experts prepare the quote faster, with their review intact. Reimagine changes how requests are qualified, how configuration options come together and when expert judgment enters. The right level depends on the evidence: where errors occur, where time is lost, and what the risk allows.
Example scenario, used to explain the framework.
Scope and responsibility
Work redesign defines the change. Building the system and changing roles follow as their own decisions. We agree up front which roles, processes and organizational questions are in scope, and policy decisions and role changes stay with the client. FAR sits inside the Target, Build and Scale flywheel as the way we frame the redesign choice. It does not add another sequence.
Practical questions
No. They are levels of ambition, and each is a valid end point. One workflow can hold more than one: fix the intake, accelerate the drafting, reimagine the approval path. The client journey stays Target, Build and Scale.
Work redesign concerns the business process and its roles. Engineering Operating Model concerns requirements, evaluation, release and ongoing engineering responsibility. The two should connect when the redesigned work requires software.
Yes. The design should consider process, information and responsibility changes alongside technology. A platform decision is justified by the chosen workflow and its requirements, rather than assumed at the start.
Next step
Bring the workflow. We’ll compare the changes worth testing and the decisions the design must resolve.
Discuss this work