A process-led field guide for internal forward deployed engineers. Map the operation, investigate the causes of lost value, size the opportunity and inspect how the work could change.
By the Forward Deployed Team · Updated 24 October 2026 · Illustrative scenarios; not customer results.
Start with the operating outcome. Follow the end-to-end process, identify a specific cause of lost value, then test the intervention. Eight process families below contain 24 working hypotheses; the visual investigations that follow illustrate selected mechanisms.
Demand, specification, purchasing, process effort and loss. Distinguish spend removed from capacity released.
03 / Capital resilience
Improve capital decisions
Asset use, investment discipline, liquidity and resilience. Preserve service and essential controls.
Evaluate every opportunity through: people and responsibilities · process and standard work · data and information · controls and decision rights · technology and adoption. AI is one possible enabler.
These are starting hypotheses, not diagnoses. Establish the baseline and the burden of proof before selecting a tool. All process families stay open as you scroll.
IT / 01
Technology strategy and demand
01Business need
02demand
03portfolio
04funding
05roadmap
01.01
Duplicate requests may fund overlapping capabilities
01.02
Poor demand qualification may initiate low-value work
01.03
Unclear ownership may allow obsolete services to persist
Proof or rejection: what evidence is needed?
Map business capabilities, demand evidence, service owners and total lifecycle cost. Reject consolidation where separation serves a real requirement.
Where AI could contribute
Cluster demand and link business evidence to portfolio scenarios; owners set priorities.
Example sizing model / Avoided duplicate delivery cost
Confirm business capability equivalence, commitments, cancellation and migration cost. Do not count a deferred project as expenditure removed or add this to the same project benefit twice.
Estimate released processing capacity from your own workload. This is an effort model, not a prediction of AI savings. Use the separate formulas above for cash, capital, margin, materials and energy.
Formula: tasks × minutes ÷ 60 × realization × hourly cost − running cost; subtract one-time cost in year one. Financial savings require an actual budget change. No inputs leave your browser.
Method and sizing notes
The opportunity structure combines three value lenses—cash release, cost optimization and capital resilience—with process, contract, working-capital, customer-management and investment analysis. Historical cost-transformation and finance operating-model references inform the process coverage. Every hypothesis requires evidence, a test that could reject it and accountable validation.
Historical transformation benefit ranges are not current benchmarks or AI effect sizes. This guide uses transparent low/base/high sensitivity examples instead. The eligible baseline, proposed change and realization route must be established for the organization. The examples are not additive, forecasts or customer results.
Prioritize by net value, strength of evidence, feasibility, time to value and service or control consequences. Deduct implementation, transition and recurring costs; assign one owner and one benefit record to prevent double counting.
01
IT / investigate the opportunity
Application portfolio
The working hypothesis
Overlapping applications may create avoidable license and support cost, but apparent duplicates can hide critical dependencies.
What would establish or reject the case?
Map capabilities, users, integrations and retention needs; test a retirement candidate with its business owner.
Human action: Review dependencies and transition cost before approving retirement.
AI / analysis & workflow
Retirement impact analysis
OPERATING INPUT → REVIEW OUTPUT
Verified application dependencies and business usage
Produce an owner review list and a migration checklist for the candidate application.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
02
IT / investigate the opportunity
Cloud utilization
The working hypothesis
Idle and oversized workloads may explain part of cloud spend without contributing to service reliability.
What would establish or reject the case?
Replay utilization and service levels; test a reversible rightsizing change under representative peak demand.
Human action: Schedule the test environment with an owner-approved exception path; protect production.
AI / analysis & workflow
Cost anomaly explanation
OPERATING INPUT → REVIEW OUTPUT
Billing line items, tags and deployment events
Explain whether the cost change follows runtime, traffic or a deployment; flag missing tags.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
03
IT / investigate the opportunity
Software licenses
The working hypothesis
Purchased seats may exceed genuine demand when joiner, mover and leaver events are disconnected from renewals.
What would establish or reject the case?
Reconcile entitlement and actual usage; confirm seasonal users and contract minimums before reclaiming seats.
Measure the consequence
Paid active seats; verified reductions; access disruption
Enablers to investigate
IT asset interviews; identity; usage; contracts; entity matching
WORKED EXAMPLE 03Illustrative scenario
A renewal includes seats with no recent activity
ILLUSTRATIVE WORKING RECORD / IT-03
Entitlement
Seats
Evidence
Purchased
250
Renewal draft
Inactive candidates
45
Owner check required
Seasonal roles
12
Do not remove yet
ILLUSTRATIVE WORKING RECORD / IT-03
Entitlement
Seats
Evidence
Purchased
250
Renewal draft
Inactive candidates
45
Owner check required
Seasonal roles
12
Do not remove yet
Review interpretation Ask owners to confirm need; observed inactivity alone does not authorize removal.
Ask owners to confirm need; observed inactivity alone does not authorize removal.
Explore the applications
AI use cases: how could the work change?
Two visual examples · inputs, interpretation and human decisions
+
An illustrative AI application: inspect the source records, the interpretation and the human decision.
Inputs: IT asset interviews; identity; usage; contracts; entity matching.
Human action: Ask owners to confirm need; observed inactivity alone does not authorize removal.
AI / analysis & workflow
Contract renewal extraction
OPERATING INPUT → REVIEW OUTPUT
License terms and verified seat demand
Expose minimum commitments and renewal dates before calculating a reclaim opportunity.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
04
IT / investigate the opportunity
Service desk & knowledge
The working hypothesis
Repeated tickets may arise from hard-to-find guidance and missing context in initial requests.
What would establish or reject the case?
Group historical cases; pilot source-linked guidance and measure correctness, repeat contacts and escalation.
Measure the consequence
First-contact resolution; reopened cases; wait time
Enablers to investigate
Support interviews; ticket logs; knowledge articles; retrieval and triage
WORKED EXAMPLE 04Illustrative scenario
A familiar error arrives without diagnostic context
ILLUSTRATIVE WORKING RECORD / IT-04
Ticket
Context
Next step
IT-104
Access denied
Role approval required
IT-105
Known error code
Link current runbook
IT-106
Unrecognized fault
Technician review
ILLUSTRATIVE WORKING RECORD / IT-04
Ticket
Context
Next step
IT-104
Access denied
Role approval required
IT-105
Known error code
Link current runbook
IT-106
Unrecognized fault
Technician review
Review interpretation Gather approved diagnostic context and show documented steps; privileged actions require approval.
Gather approved diagnostic context and show documented steps; privileged actions require approval.
Explore the applications
AI use cases: how could the work change?
Two visual examples · inputs, interpretation and human decisions
+
An illustrative AI application: inspect the source records, the interpretation and the human decision.
AI / records & interpretation
Service desk & knowledge: evidence assist
SOURCE RECORD → REVIEW NOTE
Answer assist: cite the current runbook and route unsupported errors to a technician.
Link evidence · flag uncertainty
Inputs: Support interviews; ticket logs; knowledge articles; retrieval and triage.
Human action: Gather approved diagnostic context and show documented steps; privileged actions require approval.
AI / analysis & workflow
Knowledge gap detection
OPERATING INPUT → REVIEW OUTPUT
Resolved tickets and the current runbook library
Repeated solved issue has no current article → technician reviews a draft knowledge entry.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
05
IT / investigate the opportunity
Incident diagnosis
The working hypothesis
Telemetry may be abundant while the service dependency that explains an incident remains unclear.
What would establish or reject the case?
Replay known incidents with time-aligned evidence; test candidate ranking and missed causes with responders.
Human action: Present a source-linked timeline; the responder validates cause and rollback.
AI / analysis & workflow
Post-incident evidence synthesis
OPERATING INPUT → REVIEW OUTPUT
Validated event timeline and responder notes
Separate observed sequence from suspected cause and list the checks still needed.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
06
IT / investigate the opportunity
Delivery flow & rework
The working hypothesis
Slow delivery may reflect waiting and unstable requirements rather than insufficient coding capacity.
What would establish or reject the case?
Map work from request to release; distinguish queue time from active work and pilot a smaller release batch.
Measure the consequence
Lead time; escaped defects; change failure
Enablers to investigate
Team interviews; work records; CI events; test evidence; process mining
WORKED EXAMPLE 06Illustrative scenario
A two-day change waits ten days in queues
ILLUSTRATIVE WORKING RECORD / IT-06
Stage
Active time
Queue
Implementation
2 days
1 day
Review
1 day
5 days
Release
1 day
2 days
ILLUSTRATIVE WORKING RECORD / IT-06
Stage
Active time
Queue
Implementation
2 days
1 day
Review
1 day
5 days
Release
1 day
2 days
Review interpretation Reduce a verified queue while checking test coverage and operational readiness.
Reduce a verified queue while checking test coverage and operational readiness.
Explore the applications
AI use cases: how could the work change?
Two visual examples · inputs, interpretation and human decisions
+
An illustrative AI application: inspect the source records, the interpretation and the human decision.
AI / records & interpretation
Delivery flow & rework: evidence assist
SOURCE RECORD → REVIEW NOTE
Change review: group recurring rework causes and trace each theme to an observed issue.
Link evidence · flag uncertainty
Inputs: Team interviews; work records; CI events; test evidence; process mining.
Human action: Reduce a verified queue while checking test coverage and operational readiness.
AI / analysis & workflow
Requirements ambiguity review
OPERATING INPUT → REVIEW OUTPUT
Approved change request and acceptance criteria
Flag a missing failure condition before implementation; the product owner resolves it.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
07
IT / investigate the opportunity
Vendor & network spend
The working hypothesis
Unused circuits and inconsistent service rates may persist because invoices, sites and ownership records do not reconcile.
What would establish or reject the case?
Match invoices to active services and sites; confirm failover and contractual obligations before any cancellation.
Human action: Confirm redundancy and exit cost; a low-traffic backup may still be essential.
AI / analysis & workflow
Contract-rate reconciliation
OPERATING INPUT → REVIEW OUTPUT
Circuit inventory, invoice lines and rate cards
Match billed services to the agreed rate and termination terms for owner review.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
08
IT / investigate the opportunity
Data & control evidence
The working hypothesis
Repeated manual evidence gathering may consume effort because records are fragmented and controls lack clear ownership.
What would establish or reject the case?
Select a control sample; check completeness, freshness and reproducibility against the current evidence process.
Human action: Assemble traceable records for reviewer sign-off; summaries do not establish control effectiveness.
AI / analysis & workflow
Evidence completeness checking
OPERATING INPUT → REVIEW OUTPUT
Control requirements and collected source records
Identify the missing owner approval; leave control effectiveness to the reviewer.
Validate: Compare the draft interpretation with a verified sample and record missing or incorrect conclusions before changing the process.
What would weaken the hypothesis?
The proposed change fails the measured outcome, shifts work elsewhere, loses required controls or costs more than the verified benefit. Investigate those results before scaling.
Questions & answers
Before testing an opportunity
Where can AI help in it?
Potential areas include application portfolio, cloud utilization, software licenses, service desk & knowledge, incident diagnosis, delivery flow & rework, vendor & network spend, data & control evidence. Each is a hypothesis to test against operating evidence.
Are these savings or measured results?
No. All figures, records and overlays are illustrative scenarios. Validate the baseline, net cost, feasibility and service outcomes before making a business case.
Which enablers are needed?
Start with process interviews, reliable source records and a measurable baseline. Depending on the task, useful enablers include document extraction, retrieval, classification, forecasting and workflow integration. Assign a person to review exceptions.
What should a first pilot establish?
A pilot should establish whether a specific intervention changes the measured outcome against a credible baseline, how often it fails, who reviews exceptions and what it costs to operate.
