Sustainment & Logistics
Multi-agency, multi-stakeholder programs where procurement, compliance, and mission alignment determine success.
Inside this journey
-
Pre-Discovery
Align decision-makers, program constraints, and success criteria before technical discovery.
-
Stakeholder Alignment
Confirm decision roles, timelines, risk tolerances, and what ‘mission-ready’ looks like for each military stakeholder.
Alignment Questions
Setting the Stage: Quick Snapshot
- Which service and program best describes the system we're discussing?
- What type of platform or subsystem is this (e.g., ground vehicle, aircraft subsystem, communications kit)?
- What is the current reported fleet readiness/availability rate (enter percentage or 'unknown')?
- What triggered this discovery now—select all that apply?
- Who is our primary POC for technical and program questions (name, role, and best contact)?
- How soon do you expect to receive initial findings or recommendations?
Are We Just Managing Decline or Ready to Fix It?
- How long have you tolerated availability below the program KPP, and what made the underperformance acceptable until now?
- When readiness dipped, how did leadership typically respond—temporary funding, ad-hoc repairs, mission tradeoffs, or longer-term changes?
- Which metrics besides fleet availability do you watch closely when things look bad?
- How do these trends make you feel about program sustainability—worried, resigned, motivated to change, or unsure?
- Can you point to one recent incident or week that best illustrates the current challenge? What happened and what was the immediate impact?
What's Truly Blocking Mission-Ready?
- Which single failure mode erodes mission capability most—parts lead-time, obsolescence, throughput, or workforce gaps—and why might leadership be overlooking it?
- Select the operational bottlenecks you believe are most constraining availability today.
- How long do those bottlenecks persist before a workaround is applied (days/weeks/months)?
- Give an example of a recurring failure mode (e.g., a part or subsystem) and the last time it required reverse engineering or long lead sourcing.
- What data sources do you currently rely on to diagnose these failure modes (select all that apply)?
- How confident are you that the root causes are understood and not just mitigated superficially?
Who Holds the Keys — and Who's Missing?
- If this program had to be fixed tomorrow, who would sign the approval and who could realistically block the solution?
- Select the stakeholders who must be aligned for a successful transition (pick all that apply).
- For each key stakeholder, what does 'mission-ready' look like to them (brief bullets or attachable summary)?
- Describe any past governance or decision friction that slowed sustainment changes—what caused it and how long did it take to resolve?
- What are the non-negotiable constraints from any stakeholder (e.g., data access restrictions, security requirements, hiring rules)?
- On a scale from 1–5, how risk-tolerant is the decision authority for trying an outsourced performance-based sustainment model?
Imagine 90 Days That Actually Work
- What would have to be demonstrably true on day 90 for you to call the transition mission-ready?
- Select the KPIs and targets you'd expect at initial acceptance.
- Please enter numeric targets for the most critical KPIs you selected (e.g., Availability: 90%).
- What specific knowledge-transfer activities are essential in the 90-day window (select all that apply)?
- Which transition constraint worries you most—time, funding, workforce willingness to transfer, or classified/data handling—and why?
- How comfortable would you be with a phased acceptance (e.g., capability-based milestones) versus an all-or-nothing handover?
What’s at Risk If We Don’t Change?
- Which single downstream consequence of inaction would be hardest for your team to absorb—mission delay, safety incident, budget overrun, or reputational damage?
- Select the top program risks you believe will grow if current trends continue.
- For each major risk you selected, estimate the likelihood and the operational impact (low/medium/high).
- Tell us about a recent near-miss or failure that changed how you view sustainment risk—what happened and who felt the pressure?
- How would unresolved risks affect your reporting to the service acquisition executive or congressional oversight (select all that apply)?
What Would Real Relief Actually Look Like?
- If a partner could restore readiness predictably, what would change operationally, politically, and personally for you?
- Which capabilities would signal meaningful relief to your team (pick top three)?
- How important is pre-positioning parts versus simply reducing lead times in your operational context?
- Would absorbing the incumbent workforce (with retention incentives) be acceptable—or are there policy or cultural barriers we should know about?
- What reporting cadence and format would make you feel informed but not overwhelmed during the first 90 days?
- What benefits—beyond the KPI targets—would make this partnership politically easier to justify to leadership?
Willingness, Constraints, and Practical Next Steps
- Assuming a credible plan, how quickly could you move from discovery to issuing an RFP or contract modification?
- Which procurement or approval milestones are fixed and which are flexible (briefly list constraints or dates)?
- How much access can you grant for assessment work—site visits, maintenance records, technical data packages, and contractor interviews?
- Are there existing contracts or incumbent terms that would complicate workforce absorption or data transfer?
- What evidence or deliverables would you need from a prospective partner to recommend moving to a pilot or award (select top three)?
- Would you be willing to run a targeted pilot (e.g., one depot or one subsystem) before full transition?
- What are the three most important next actions you'd like our team to take after this discovery?
-
Current State Mapping
Document fleet readiness trends, depot throughput, parts obsolescence, workforce gaps, and failure modes blocking availability targets.
Current State
Quick Snapshot: Where We Stand Right Now
- Can you give us a brief snapshot of your current fleet readiness—what percent of the fielded set is mission-capable right now?
- Over the past 12 months, how has that readiness trend behaved?
- Which specific platforms, subsystems, or units are driving the readiness shortfall? List the top three.
- When did readiness first cross below your program threshold or Key Performance Parameter?
- Who in your organization is most pressured to solve this (select all who apply)?
If This Keeps Going, What Breaks First?
- Which single failure mode, if it continued, would most quickly prevent units from meeting mission requirements?
- List the top three recurring failure modes you’ve observed (be specific—e.g., hydraulic pump seal, power distribution board fault).
- How often do these failure modes require depot-level teardown versus field-level corrective action?
- Tell us about a recent mission impact caused by one of these failures—what happened and what was the operational consequence?
- For your most common failures, what is the typical detection-to-return-to-service timeline?
Why Is Work Not Flowing Smoothly?
- Where in your maintenance pipeline does work most often stall—so often it feels like you’re running in place?
- How would you categorize current depot throughput in practical terms (average turnaround or units/month)?
- Which single bottleneck contributes most to backlog growth right now?
- How large is the current maintenance backlog (work orders or units) relative to planned capacity—give a number or range if possible.
- Which approvals, processes, or policies cause the longest delays (select all that apply)?
- Have you tried recent process improvements (e.g., lean cells, shift changes, priority lanes)? What worked and what failed?
Where Do Parts and Data Let You Down?
- Which specific part or data gap today most threatens your ability to repair within the time you need?
- Approximately what percent of maintenance events are delayed because parts are not available when needed?
- How many critical long-lead items do you actively track, and how many of those are currently out of production or at risk?
- Do you currently have authority and budget to pursue obsolescence fixes (reverse engineering, small OEM production runs, overhaul contracts)?
- How complete and searchable is the technical data package for the affected systems?
- Do you rely on cannibalization or depot bypass as stopgaps, and if so, how frequently?
Who’s Doing the Work — and What Keeps Them Awake at Night?
- If you could fix only one human problem in your sustainment chain, would it be hiring, retraining, reorganizing work, or bringing in contractor specialists—and why?
- What percentage of maintenance roles are currently vacant or filled by temporary/contract hires?
- Roughly how many technicians meet the certification level required for depot-level repairs today?
- Select the primary reasons technicians leave or decline challenging assignments (choose all that apply).
- How comfortable is your workforce with an external contractor absorbing roles or sharing work—what emotions or resistance exist?
- Are there union, labor, or clearance constraints that would complicate workforce transfer or contractor onboarding?
Hidden Costs and Risks You See but Don’t Always Say
- Where are you quietly spending the most money or risking the most capability to keep systems running?
- Estimate the percent increase in annual maintenance hours or cost compared to the original budget or expectation.
- Which capability trade-offs have you accepted to keep pace (reduced training, deferred upgrades, fewer preventive checks)? Describe briefly.
- What level of operational risk are you currently willing to accept to meet near-term mission demands?
- Are there contractual or acquisition levers (emergency funds, bridge contracts, prioritized procurement) you could exercise now to reduce risk?
What Would Mission‑Ready Actually Feel Like?
- Imagine waking up next quarter and every platform met your mission‑ready definition—what would you hear, see, and stop worrying about?
- List the top three KPIs that would prove success for you (e.g., availability %, MTTR, fill rate) and the numeric targets for each.
- What is the maximum acceptable downtime per platform during surge operations (90‑day requirement) before mission impact becomes unacceptable?
- How quickly must an alternative sustainment approach be operational to prevent mission degradation?
- Which constraints would most likely make a 90‑day knowledge transfer impossible (select all that apply)?
- Who are the must‑have stakeholders that must sign off on a new sustainment approach (list roles and offices)?
If We Could Help, What Would You Actually Want Us to Do First?
- What one immediate action from an external sustainment partner would convince you they understand the problem and can close the gap?
- Would you be willing to share operational and maintenance data under NDA so a partner can model fixes and forecast impact?
- What access, security, or export constraints would a partner need to plan for (e.g., classified networks, on‑site clearances, ITAR components)?
- Who from your team should be involved in a 2–4 week discovery pilot (roles and approximate FTE commitment)?
- If we ran a 30‑day proof of concept, which single measurable outcome would make you say it was worth pursuing (pick one)?
-
-
Outcome Discovery
Define target KPIs, acceptance criteria, transition constraints (90-day knowledge transfer), and the program’s top risks to readiness.
Discovery Questions
Setting the Finish Line: What 'Mission-Ready' Really Means
- How would you describe 'mission-ready' for this fleet or platform in one sentence?
- Which objective metrics do you currently treat as the authoritative indicators of readiness?
- Which of those metrics is the single most important for this program decision?
- What explicit acceptance criteria would you require at the end of the 90-day transition to consider transfer successful?
- How do these acceptance criteria map to contractual levers you can use—pass/fail gates, graduated payments, or performance holdbacks?
- Over what cadence would you want readiness reported during and after transition (e.g., daily, weekly, monthly)?
Are We Mistaking Symptoms for the Problem?
- If current readiness is low, why do you believe that is—people, parts, processes, or policy?
- What assumptions are we making about the incumbent’s capability that, if wrong, would change the plan?
- Where do you sense the most pushback internally when you propose change to the sustainment approach?
- Tell me about a recent instance where fixing a surface symptom didn’t improve readiness—what happened and how long did you spend on it?
- If we surfaced one overlooked root cause during discovery, what would you most hope it would be?
The 90-Day Handoff: Can Knowledge Travel Faster Than People?
- What parts of institutional knowledge do you worry will be lost if incumbent technicians don’t transfer to the new team?
- What would a successful 90-day knowledge transfer actually look like on day 91?
- Which transfer methods do you currently trust most—shadowing, structured training, documentation handover, or reverse engineering?
- How quickly does your team need new technicians to be independently proficient on key faults (hours, days, weeks)?
- What measures would convince you that knowledge transfer is durable (e.g., assessed proficiency, reduced repeat-failures, documentation completeness)?
What Would Failure Actually Feel Like — and When Would It Hurt Most?
- If the transition failed to meet targets, what would be the immediate operational consequence you fear the most?
- What has been the worst readiness-related surprise in the last two years, and how much time did it cost you to recover?
- Which program stakeholders would be most exposed politically or operationally if KPIs slip during transition?
- What early warning indicators would you want us to monitor to avoid that failure scenario?
- How long of a setback (days/weeks/months) would be tolerable before higher-level intervention is required?
The Parts, Tools, and Data You Can't Afford to Lose
- Which spare parts or subsystems are single points of failure for meeting your availability targets?
- How many parts are currently classified as obsolete or single-source, and how is that tracked?
- What lead times are you seeing for your top five critical parts today?
- How complete and accessible is your technical data package (TDP) and digital repair instructions for depot and field work?
- If we proposed pre-positioning X days of spares at forward nodes, what trade-offs would you worry about (cost, storage, obsolescence)?
Who Holds the Keys When Things Get Hard?
- Who must sign off on acceptance criteria and milestone gates during the transition?
- If an escalation is needed, what is your preferred governance path and maximum response time?
- Which decisions are politically sensitive and may require additional approvals or briefings?
- How do you prefer change requests be evaluated—fast-track for ops-critical items, or through full program review?
- Who on your team should we bring into weekly transition governance calls (names/roles)?
If We Hit the KPI, What Actually Changes for You?
- Beyond the headline KPI, what secondary outcomes would signal long-term success?
- How would improved readiness change daily life for operators and maintainers—give a concrete example?
- What reporting cadence and format would make you feel confident that improvements are real and sustainable?
- Which quantitative targets would make this transition a programmatic win in your stakeholders’ eyes (specify numbers where possible)?
- If we achieve those targets, what would your recommended next step be—scale, institutionalize, or re-compete?
-
Solution Experience
Walk through realistic scenarios showing how our sustainment model restores readiness, pre-positions parts, and absorbs the incumbent workforce.
Experience Meetings
- Solution Experience Kickoff — Current State & Consequence Alignment
- Readiness Recovery Scenario — 90-Day Surge Maintenance Walkthrough
- Parts Pre-Positioning Simulation & Inventory Economics
- Workforce Absorption & 90-Day Knowledge Transfer Playbook
- Integrated End-to-End Rehearsal & Executive Validation
- Lock the 90-day KT curriculum and the competency gates that map to acceptance criteria.
- Current Supply Chain State & Lead-Time Review
- Validate an inventory placement plan that supports the target forward fill rates for the scenario.
- Agree the economic boundary (max inventory spend) acceptable to the customer for pre-positioning.
- Identify high-risk obsolete items and the mitigation path with owners and timelines.
- Run the pre-positioning model with the customer's actual consumption data and deliver results in 72 hours.
- Seller to provide a prioritized parts picklist (A/B/C) for forward stocking and estimated costs.
- Customer to confirm budget constraints or approval thresholds for pre-position inventory purchases.
- Current Workforce Map & Critical Skillsets
- Agree the list of incumbent staff to be targeted for absorption and the timeline for offers/transfers.
- Introductions & Meeting Objectives
- Identify labor relations constraints and agree mitigation owners and actions.
- Customer to provide finalized incumbent roster with contactability and classification details within 5 business days.
- Seller to draft the KT curriculum schedule and competency checklists for customer sign-off.
- HR/legal teams to review and confirm any regulatory or union impacts to absorption plan.
- Recap: Agreed Current-State, Consequence, and Future-State
- Obtain executive validation that the demonstrated plan achieves the defined future state and KPIs.
- Secure agreement on next formal step (pilot, move to Solution Scope, or contract negotiations) with owners and target dates.
- Establish governance leads and a communication cadence for the transition phase.
- Seller to deliver an integrated turnkey plan (timeline, cost estimate, KPI targets) for executive review within 72 hours.
- Customer to confirm decision on pilot or scope progression and name governance leads within 5 business days.
- Schedule follow-up governance kickoff and sign-off meeting to transition to Solution Scope activities.
- Produce and lock a single-sentence current-state summary that all stakeholders accept.
- Document a quantified consequence statement (cost/time/mission risk) tied to the current state.
- Agree a one-sentence future-state outcome and the KPIs to validate it during scenario walkthroughs.
- Identify required data and SME inputs with owners and deadlines for follow-up simulation meetings.
- Owner to produce a 1-page Current State + Consequence statement and circulate within 48 hours.
- Customer to provide historical readiness, MTTR, parts lead-times, and incumbent workforce roster within 5 business days.
- Schedule the 90-day Surge Scenario walkthrough with required SMEs and data owners.
- Scenario Context & Assumptions
- Agree on a validated 90-day recovery timeline with named owners for each critical task.
- Confirm capacity proof that depot and field resources can meet the surge without degrading long-term sustainment.
- Lock the acceptance checkpoints and KPIs used to judge success at the 90-day mark.
- Surface any assumptions that, if invalid, would change the outcome and assign owners to resolve them.
- Seller to produce a day-by-day Gantt and resource plan for the 90-day surge and circulate to stakeholders.
- Customer to validate depot/field access windows and confirm any blackout dates within 3 business days.
- SME to provide missing capacity or constraints that could shift the schedule.
- One-Sentence Current State
- Integrated Scenario Walkthrough
- Simulation Walkthrough (Inputs -> Outputs)
- Day-by-Day/Week-by-Week Recovery Timeline
- Absorption Model & Org Transition
- 90-Day Knowledge Transfer Curriculum
- Inventory Economics & Tradeoff Analysis
- Quantified Consequence Statement
- Capacity & Throughput Proof
- Measure Expected KPIs & SLA Alignment
- Retention, Incentives & Labor-Risk Mitigation
- Decision & Next Steps (Pilot, Scope, Contract Path)
- Obsolescence & Alternate Sourcing Proof Points
- Parts Flow & Pre-Position Execution
- Define One-Sentence Future State (Target Outcome)
- Data Gaps & Pre-work for Scenario Sessions
- Milestones, Acceptance Checkpoints, and KPIs
- Validation: Competency Gates & Test Scenarios
- Validation & Tieback to Readiness Scenario
- Agree Success Criteria and Validation Approach
- Open Validation: 'Is this what you meant?'
-
Solution Scope
Define scope modules—depot & field maintenance, supply chain, obsolescence mitigation, technical data transfer, and measurable SLAs.
Scope Configuration
- Deploy embedded field technician teams
- Perform depot-level overhaul and rebuilds
- Execute 90-day surge maintenance campaigns
- Establish containerized mobile maintenance facilities
- Pre-position forward spare parts kits
- Source and procure critical long-lead components
- Reverse-engineer and manufacture obsolete components
- Install predictive sensors and analytics for fleets
- Provide remote diagnostic and troubleshooting support
- Perform test equipment calibration and repair
- Update technical manuals and illustrated parts breakdowns
- Deliver hands-on technician training and certification
Scope Questions
Deploy embedded field technician teams
- Do you require embedded field technician teams as part of the sustainment scope?
- How many embedded technicians are estimated per location?
- Which operating environments will technicians be deployed to?
- What minimum certifications, security clearances, or OEM qualifications must technicians hold?
- What shift coverage is required for embedded teams?
- What are the primary responsibilities expected of embedded technicians (e.g., diagnostic, hands-on repair, preventative maintenance)?
- Are there physical site constraints or infrastructure requirements (power, shelter, hazardous area classification) we need to plan for?
Perform depot-level overhaul and rebuilds
- Do you plan to include depot-level overhaul and rebuild services in scope?
- What annual or campaign volume of complete overhauls do you anticipate (units per year)?
- What turnaround time (TAT) targets are required for depot overhauls?
- Will depot work be performed at government facilities or contractor-owned depots?
- Which acceptance criteria/KPIs will define a successful overhaul (e.g., MTBF increase, acceptance test results, readiness %)?
- Are special test stands, calibration equipment or long-lead tooling already available, or must they be supplied?
- Are there hazardous materials, controlled commodities, or export-controlled components involved in overhauls?
Execute 90-day surge maintenance campaigns
- Do you require an explicit 90-day surge maintenance campaign capability?
- How many systems or line-items must be returned to mission-capable condition during a typical 90-day surge?
- What priority or sequencing rules should be applied during a surge (e.g., unit-deployment date, critical mission sets)?
- Are incumbent workforce transfer or immediate workforce absorption required during the 90-day period?
- What parts availability or fill-rate targets must be achieved to meet the 90-day surge objective?
- Are there staging/forwarding locations or interim depots designated for surge operations?
- What contingency actions should be pre-authorized if parts or labor constraints prevent meeting surge targets?
Establish containerized mobile maintenance facilities
- Is a containerized/mobile maintenance facility required?
- How many containerized units and what modular sizes are anticipated (e.g., 20ft, 40ft, expandable modules)?
- What environmental and mobility constraints apply (air transportable, C-17 pallet-compatible, climate/humidity control)?
- What internal capabilities must the container include (test benches, hoists, compressed air, power generation)?
- Will the mobile facilities require standalone power/water/sewage, or will they rely on host-site utilities?
- What security or CBRN hardening requirements apply to deployed containers?
- Are approvals or certifications required for operating mobile facilities on government ranges or ports?
Pre-position forward spare parts kits
- Do you want pre-positioned spare parts kits at forward locations?
- What target fill-rate or availability should kits achieve at forward sites?
- Which locations should be stocked (list bases, regions, CONUS/OCONUS, afloat)?
- Should inventory be contractor-owned, government-owned with contractor management, or mixed?
- What is the expected parts consumption rate or forecast window used to size kits (monthly, quarterly, campaign-based)?
- Are there temperature, shelf-life, or hazardous storage constraints for any parts in the kits?
- What replenishment cadence and reorder triggers do you require for forward kits?
Source and procure critical long-lead components
- Do you want the contractor to source and procure long-lead components on your behalf?
- Please list the critical long-lead components or categories and their typical lead times (if known).
- Are there approved vendor lists, OEM restrictions, or DFARS/ITAR constraints affecting procurement?
- What acceleration or expedited procurement options are acceptable (e.g., higher cost, alternate sourcing, approved substitutes)?
- Will the customer provide funding or advance inventory funding for long-lead buys?
- What delivery performance metrics are required for procured long-lead items (on-time delivery window, quality acceptance)?
- Are special packing, transport, or storage conditions required (classified handling, temperature control)?
Reverse-engineer and manufacture obsolete components
- Do you require reverse engineering and in-house manufacture for obsolete parts?
- For which parts do source drawings or OEM data not exist (list PN or assemblies)?
- Are there IP, copyright, or licensing constraints that would prevent reverse engineering?
- What qualification and test requirements must reverse-engineered parts meet (dimensional, functional, environmental)?
- What volume and lead-time expectations exist for manufactured replacement parts?
- Will newly manufactured parts require government acceptance testing or HEAT/OT&E prior to use?
- Are there preferred manufacturing locations (domestic, ally country) or sourcing restrictions?
Install predictive sensors and analytics for fleets
- Do you intend to install predictive sensors and analytics on the fleet as part of the solution?
- What fleet size and platform types are targeted for sensor installation?
- Which sensor types or data streams are required (e.g., vibration, temperature, voltage, fluid analysis)?
- What telemetry connectivity is available or preferred at operating locations (cellular, satellite, local mesh, none)?
- What analytics outputs or decision-support products do you need (RUL estimates, failure alerts, maintenance work orders)?
- Do analytics need to integrate with existing CMMS, logistics, or classified networks?
- Are there cybersecurity, accreditation, or ATO requirements for telemetry and analytics?
Provide remote diagnostic and troubleshooting support
- Do you require remote diagnostic and troubleshooting as a sustained service?
- What SLA response times are expected for remote diagnostic support (initial response, escalation)?
- Which remote tools are acceptable (secure video, augmented reality, remote desktop, telemetry dashboards)?
- Will remote support teams require access to government networks, classified systems, or PII?
-
Mutual Commit
Resolve contract modules, SLAs (availability, fill rates), 90-day transition commitments, governance, and escalation paths.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- Transition & 90-Day Knowledge Transfer Commitment
- Pricing & Payment Schedule
- Governance & Escalation Matrix
- Workforce Transfer & Labor Agreements
- Parts Inventory & Pre-Positioning Annex
- Technical Data Rights & IP Transfer
- Security & Facility Access Agreement
- Acceptance Criteria & Validation Checklist
- Performance Incentives & Liquidated Damages
- Change Order & Scope Management Process
- Obsolescence Mitigation & Reverse Engineering Annex
- Compliance, Certifications & Regulatory Attestation
- Subcontracting & Incumbent Handover Plan
- Data Reporting & KPI Dashboard Specification
- Termination, Renewal & Exit Plan
- Confidentiality & Non-Disclosure Agreement (NDA)
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Confirm access, data transfers, workforce onboarding, parts pre-positioning, and risk controls before execution.
Readiness Questions
Start Here: The One-Sentence Brief
- In one sentence, how would you describe the readiness issue or decision that brought you here today?
- Who are the three people (names or roles) we should involve immediately to get unfiltered context?
- How long have you been tracking this problem, and what specific trigger prompted you to seek a new sustainment approach now?
- How urgent is resolution on a timeline scale—must be solved in 90 days, within 6 months, within a year, or earlier/later?
- What’s the single promise you want a new sustainment partner to deliver that your current setup hasn’t?
If Nothing Changes, Whose Mission Breaks First?
- If we keep the status quo for the next 90 days, which unit, deployment, or mission will be most at risk and why?
- How far below your target availability/Fx rate are you today (percentage points or absolute numbers)?
- When readiness shortfalls occur, what are the immediate operational consequences you observe (training cancellations, delayed deployments, increased safety incidents, etc.)?
- Tell us about the last time you recovered from a readiness dip—what worked, who drove it, and what took the longest?
- Which external pressures (oversight, media, congressional, joint ops) amplify the consequences of not fixing this now?
Who’s Carrying the Pain (And Is Anyone Listening)?
- Who feels the pain most acutely on a day-to-day basis—depot supervisors, unit commanders, logisticians, or maintainers—and what do they say about it?
- How would you describe technician morale and retention where the work actually happens? Give a concrete example if possible.
- Which skill gaps or certifications are preventing workload throughput today (e.g., avionics, composite repair, engine teardown, EW systems)?
- How often do institutional knowledge holders (retiring techs, contractors) leave without formal transfer, and can you cite a recent example?
- Who currently makes the final call when tradeoffs are required (mission vs maintenance vs budget), and how transparent is that governance?
What Would Mission‑Ready Actually Feel Like in 90 Days?
- If you walked into operations exactly 90 days from now and everything was ‘mission-ready,’ what three concrete things would you see or hear?
- Which KPIs would you use to prove success at day 90 (availability %, MTTR, fill rate, throughput), and what are the numeric targets?
- What acceptance criteria would make you sign off on the transition at the 90‑day milestone (e.g., proficiency tests, SLA met for 30 days, inventory on hand)?
- What non‑negotiable constraints exist during transition (e.g., base access windows, security clearances, funding limitations)? List specific gates or deadlines.
- Who must explicitly sign off at day 90, and what will make their decision straightforward?
Which Parts Will Surprise You By Taking Months to Replace?
- Which components are currently showing obsolescence or DMS concerns that could create long lead times?
- What are typical current lead times for your critical spares (days/weeks/months) and which items exceed acceptable limits?
- How does inventory get prioritized today—historic usage, technical orders, or command-directed—and who owns that decision?
- Have you tried pre-positioning inventory before? If so, what worked and what caused waste or stockouts?
- Which single part or subsystem, if unavailable for 30 days, would cause the largest readiness drop?
Who Are We Planning To Put In Place—and Can They Stick Around?
- If the incumbent workforce does not transfer, how quickly would your maintenance capacity degrade and why?
- What incentives, approvals, or HR actions are required to absorb incumbent technicians into a new contractor workforce?
- Describe the baseline skills/credentials we must verify in the first 30 days to operate safely and effectively (list specific certifications or proficiencies).
- How do you prefer workforce onboarding to be demonstrated—checklists, observed proficiency runs, signed competency statements, or operational test missions?
- Do any labor agreements, local hiring rules, or security clearances create hard limits on who we can onboard quickly?
Which Everyday Assumption About This Program Is Probably Wrong?
- What commonly held belief in your program (about parts, people, timeline, or cost) do you suspect won’t hold up under scrutiny?
- Name the top three program risks that keep you or your leadership awake at night.
- For each risk you listed, what controls or mitigations are currently in place and why might they fail?
- How much risk transfer are you willing to accept to guarantee availability (low = keep most risk, medium = share, high = transfer to contractor)?
- Which consequences of a mitigation failing would be considered program-critical (e.g., mission cancellation, urgent funding request, leadership change)?
What Evidence Will Convince Your Leadership This Worked?
- Which single metric would you present to the acquisition executive to demonstrate that the transition succeeded?
- What is the current baseline data (last 3 months) for that metric? Please provide numbers or say 'unknown'.
- How accessible is the authoritative data (CMMS, ERP, maintenance logs) we need for verification—fully accessible, partial, or locked by policy?
- How often do you require reporting during transition and after (daily, weekly, monthly), and which format is mandatory (dashboard, CSV, brief)?
- Who will own the post-transition validation channel so issues get logged and resolved—name a role or office?
If We Tried a 90‑Day Transition Tomorrow, What Would Trip Us Up?
- What single operational constraint (site access, clearance transfer, data handoff, tooling) is most likely to derail a 90‑day handover?
- Describe the current state of your technical data and documentation—complete and current, incomplete with gaps, or largely legacy/manual.
- What clearance levels or IT boundary approvals must be obtained before our teams can access maintenance records and parts data?
- What contingencies would you expect us to build into the schedule (e.g., parallel activities, supplier backups, surge labor) to protect the 90‑day plan?
- Which checkpoints (dates or events) should be non‑negotiable on the transition timeline to allow early course correction?
What Would It Take for You to Commit to a Next Step This Week?
- What decision or approval would you need from leadership to move forward with a short‑list of sustainment partners?
- Which contractual terms are non‑negotiable in your view (e.g., 90‑day transition guarantee, availability SLA, fill rate threshold, liability caps)?
- What does a constructive next meeting look like to you—who must attend, what evidence should be ready, and what outcome should we target?
- How do you prefer to receive proposals and transition plans—detailed program brief, executive summary with appendix, or interactive workshop?
- What timeline would you set for a vendor decision if we present a viable plan—immediately, within 30 days, within 60–90 days, or longer?
-
Deployment Enablement
Schedule tasks, assign owners, and execute the transition plan with clear sequencing, checkpoints, and contingency actions.
-
Validation Checklist
Verify acceptance criteria, workforce proficiency, parts fill rates, and initial readiness metrics are met post-transition.
Validation Questions
Let’s Start With What Matters Most
- What is your primary role on this program and the organization you represent?
- Which platform or fleet does this discovery apply to (model/variant and unit or depot)?
- What is the current contractual state or governance model for sustainment on this platform?
- What triggered this conversation today? (Select all that apply.)
- Briefly, what outcome must be justified to your leadership to consider changing how sustainment is performed? (e.g., target availability, authorized risk tolerance)
Are You Comfortable With 'Good Enough' Readiness?
- If current readiness were allowed to drift another 5–10% down, how would that change operations or mission approval timelines?
- How often do you feel decisions are made that 'paper-over' readiness problems instead of fixing root causes?
- When you read incident reports about mission-impacting failures, do you see patterns repeating across months or years?
- How anxious or pressured do you personally feel when readiness shortfalls are raised to the acquisition or service leadership?
- If fixing readiness required structural change (workforce transfer, new supply chain, SLA enforcement), what internal barriers have prevented that so far?
Where the Fleet Actually Breaks
- What are the top three failure modes driving downtime or unavailability on this platform right now? Please list and estimate frequency.
- Which maintenance level is most constrained today (Depot, Field/TO, Intermediate)?
- Rate the severity of these systemic issues at present: parts obsolescence, depot throughput, workforce qualifications, technical data gaps.
- Which critical components are at risk from diminishing manufacturing sources or long lead times? (List top 5.)
- How predictable are failure occurrences today—do you have analytics that give 2–4 week lead time on component failures?
- How often do depot backlogs cause cascading effects to fleet availability (e.g., AOGs, mission aborts)?
Who Owns the Knowledge—and Is It at Risk?
- If the incumbent workforce were asked to transition to a new contractor, what percent do you realistically expect would move with the program within 90 days?
- Where are the largest competency gaps that limit meeting availability targets? (Select all that apply.)
- How complete and current is your technical data package (TDP) and maintenance documentation for sustainment handoff?
- Tell us a recent example where missing institutional knowledge caused a missed SLA, safety risk, or delayed deployment. What happened and why?
- How confident are you that a new sustainment provider could be fully operational within a 90-day knowledge-transfer window, given current data and workforce realities?
What Would Mission-Ready Feel Like in 90 Days?
- If we achieved a successful 90-day transition, what 3 KPIs would be non-negotiable to prove success to your leadership?
- For each KPI you listed, what is the numeric target or acceptance threshold?
- Which operational constraints must be honored during transition? (Select all that apply.)
- How would early indicators of success look within the first 30 days post-transition (examples: technician proficiency, parts fill rate, throughput)?
- Who are the internal stakeholders that must sign off on 'mission-ready' at 90 days, and what does each care about most?
If We Took Over, What Would We Have to Fix Fast?
- Here’s a hard one: what single failure today causes the most political risk or leadership scrutiny if it repeats?
- Which supply-chain actions would have the fastest impact on availability if executed immediately? (Pick top 3.)
- What operational or safety risks would we inherit that require immediate mitigation plans?
- How available is the historical maintenance and usage data we would need to build predictive models (hours of operation, failure logs, part usage)?
- If budget or access were constrained, what would be the one activity you would insist be prioritized during the first 90 days?
What Would a Safe Transition Actually Require?
- Which of these transition elements are already committed or available today? (Select all that apply.)
- What governance structure would you prefer during transition (frequency and participant types)?
- What data rights or access restrictions would we need to navigate (classified, CUI, supplier NDAs)? Please specify.
- Which SLA metrics are most politically sensitive and must be negotiated before go-live?
- In your view, what are acceptable escalation paths and response times for critical issues during the first 90 days?
Deciding Together: Next Steps and Signals of Commitment
- Which decision-makers need to be engaged next to advance a change in sustainment approach (names or roles)?
- What would be the minimal package of deliverables you would need from us to prepare an internal recommendation (examples: transition plan, risk register, cost/benefit summary)?
- How soon would you expect a draft transition timeline and risk mitigations if we agreed to proceed with discovery services?
- What internal approvals or procurement steps typically delay decisions in your organization, and how long do they take?
- What would you personally need from a sustainment partner to feel comfortable endorsing a transition to leadership?
Final Check — Anything Unsaid That Matters?
- Is there a piece of context, a past failure, or a political constraint we haven’t asked about that could change how we approach this work?
- Would you like to attach relevant documents to help us validate assumptions (maintenance logs, part lists, SLA excerpts)?
- How would you prefer we follow up after this discovery (email summary, executive briefing, workshop, technical scoping session)?
- Is there anything else you want us to know before we prepare the next deliverable?
-
-
Success
Review outcomes against KPIs, capture lessons learned, and maintain a shared channel for issues and enhancements.
Success Reviews
- KPI Review & Performance Assessment
- Validation & Acceptance Confirmation
- Lessons Learned & Continuous Improvement Workshop
- Governance, Issue Channel & Enhancement Handoff
- Sustainment Roadmap & Continuous Monitoring Plan
Issues & Enhancements
- Create the shared communication channel, provision access to identified participants, and post initial onboarding materials.
- Assign remediation owners for each KPI failing acceptance and set target recovery dates.
- Introductions & Objectives
- Ensure all acceptance evidence is captured and archived in the shared channel.
- Define verification steps and re-inspection dates for any conditional items.
- Prepare and circulate an acceptance certificate or conditional acceptance statement within 48 hours.
- Create remediation tickets for outstanding acceptance items with owners and re-verification dates.
- Upload all supporting evidence (training records, inventory snapshots, logs) to the shared repository.
- Workshop Framing & Rules
- Produce a structured lessons-learned document covering root causes and recommended changes.
- Create a prioritized improvement backlog with owners, effort estimates, and expected impact.
- Agree on how lessons will be disseminated and applied to future transitions.
- Draft the lessons-learned report and circulate for customer and seller review within 5 business days.
- Create backlog items in the shared issue tracker for top 5 improvements and assign owners.
- Update training materials and transition playbooks based on workshop findings.
- Governance Roles & Cadence
- Stand up a shared channel and agree access and usage rules for issues and enhancements.
- Finalize governance cadence, RACI, and escalation procedures for ongoing operations.
- Ensure all operational contacts and severity SLAs are documented and accepted.
- Document measurable success criteria and timeline for re-evaluation.
- Publish the issue severity matrix and triage workflow to the shared repository.
- Schedule recurring governance meetings (weekly ops, monthly SBR) and send calendar invites.
- Roadmap Objectives & Horizon
- Approve a prioritized sustainment roadmap with owners and timelines tied to KPI improvements.
- Define continuous monitoring rules and automated alerts to detect KPI drift early.
- Agree on reporting cadence and any needed SLA amendment proposals.
- Publish the approved sustainment roadmap to the shared channel with milestones and owners.
- Configure dashboards and automated alerts for agreed KPIs and validate with a 2-week pilot.
- Draft any proposed SLA amendments and circulate for legal and customer review.
- Confirm which KPIs meet acceptance and which require remediation.
- Agree on immediate corrective actions, owners, and deadlines for KPI shortfalls.
- Publish an updated KPI dashboard and variance report to the shared channel within 48 hours.
- Schedule a targeted follow-up review for unresolved high-impact KPIs in 2 weeks.
- Purpose & Acceptance Criteria Recap
- Obtain formal acceptance or a documented conditional acceptance with a remediation plan.
- Monitoring Strategy & Automated Alerts
- Workforce Proficiency Evidence
- KPI Dashboard Walkthrough
- Timeline Retrospective
- Shared Channel Setup
- Predictive Maintenance & Inventory Optimization Plans
- Issue Triage & Severity Matrix
- Variance Analysis
- Parts Fill Rate & Inventory Verification
- Successes & Pain Points
- Root Cause Breakouts
- Operational & Financial Consequences
- Initial Readiness Metrics Verification
- Contractual/ SLA Adjustments & Reporting Rhythm
- Enhancement Pipeline & Prioritization
- Escalation Paths & Contacts
- Prioritized Improvement Backlog
- Root Cause Hypotheses
- Funding, Resourcing & Implementation Timeline
- Outstanding Acceptance Items
- Close & Documentation Plan
- Close & Commitment
- Onboarding Process for New Stakeholders
- Immediate Remediation Options
- Acceptance Decision