Opening: Who’s Actually in the Room?

• Which of the following roles are formally assigned to sponsor or approve this modernization effort today? Options: CIO, CTO, CFO, Head of Regulatory Affairs/Compliance, Chief Risk Officer, Board Chair/Committee member, Head of Operations, Other (name role)
• Who is the single executive we should treat as the primary sponsor or decision-owner for phase approvals? (name and title)
• Who is the person we will be meeting with most frequently during discovery and program planning? (name, role, preferred contact)
• Which stakeholders are currently missing from your internal RACI that you think should be added before we finalize the phased business case? Options: Board representative, Internal audit, Legal/General counsel, Business line heads (Retail/Commercial), Data governance lead, Third-party vendor manager, Other
• How comfortable are the identified sponsors with a phased delivery that requires sign-off at each gate? Options: Very comfortable, Somewhat comfortable, Neutral/undecided, Apprehensive, Strongly opposed

If This Stalls Midstream, Who Gets the Blame?

• If the program were to stall after phase one, whose reputation or role would be most exposed internally or externally? Options: CIO, CFO, Head of Regulatory Affairs, Board/committee members, Project sponsor (name), Other
• How worried are you about headlines, examiner findings, or customer impact if two platforms run in parallel for an extended period? Options: Very worried, Somewhat worried, Occasionally worried, Not worried
• Tell us about a past program at your bank (or a peer) that encountered reputational or regulatory fallout—what happened and why did it stick with you?
• Which impact would feel worst to you if the initiative slowed unexpectedly: increased run-cost, regulatory scrutiny, customer disruption, or lost strategic opportunity? Please rank in order of severity. Options: Increased run-cost, Regulatory scrutiny, Customer disruption, Lost strategic opportunity
• How would your leadership team measure reputational or external risk during the program (metrics, signals, or triggers you monitor)?

Show Me the Mandate — How Real Is the Board Timeline?

• Does the board mandate include a formal deadline (e.g., digital account opening live within X months) or is it directional guidance? Options: Formal board resolution with deadline, Board expectation without formal deadline, Executive-level mandate (not yet escalated to board), Informal timeline discussion
• What is the exact target timeline the board has set for the first public-facing milestone (months from today)? Options: <6 months, 6–12 months, 12–18 months, 18–24 months, >24 months
• Are there intermediate board gates or milestones explicitly tied to funding releases? If so, what are they?
• What documentation or metrics does the board insist on seeing at each gate to continue funding (e.g., cost-savings forecast, regulator briefing, successful parallel run)? Options: Cost takeout forecast, Regulatory sign-off evidence, Phase acceptance test results, Reference checks, Project team staffing validation, Other
• How flexible is the board on sequencing if we present evidence the original timeline needs adjusting for safety or compliance? Options: Highly flexible, Moderately flexible, Skeptical but open to evidence, Not flexible

Regulator’s Bar: What Will OCC/FDIC Need to Sign Off?

• If an examiner asked today ‘Why is a phased modernization safer than a big-bang swap?’, how would you answer?
• Which of the following regulator-facing artifacts would your Head of Regulatory require before recommending contract signature? Options: Integrator references at comparable banks, CV/interview with proposed Project Director, CV/interview with Lead Architect, Phased delivery and rollback plans, Regulatory communication plan, Independent risk assessment
• When is your next major exam window that we must avoid or sequence around? Options: Next 3 months, 3–6 months, 6–12 months, 12+ months, Unsure
• Have you previously presented a phased migration plan to an examiner? If yes, what feedback or conditions were imposed? Options: Yes — approval with conditions, Yes — informal acceptance, No — never presented, Unsure
• Describe any outstanding regulatory concerns (data residency, audit trail, third‑party controls) that must be explicitly addressed in our phase acceptance criteria.

What ‘Measurable Cost Takeout’ Actually Looks Like to Your CFO

• What minimum percent reduction in run-rate maintenance would the CFO expect to see after phase one to greenlight the next phase? Options: <10%, 10–20%, 20–35%, 35–50%, >50%
• Which cost categories are non‑negotiable for measurement (e.g., mainframe MIPS, middleware licenses, headcount, third‑party support)? Select all that apply. Options: Mainframe processing/MIPS, Middleware licensing, Support/maintenance contracts, Headcount/operations, Hosting/cloud costs, Incident remediation costs, Other
• How does your finance team prefer to validate cost takeout—actual run-rate savings, forecasted NPV, or operating expense reclassification? Options: Actual run-rate savings (monthly), Forecasted NPV over 3–5 years, One-time transition costs vs ongoing OPEX, Mixture — please explain
• Who in finance will be responsible for certifying phase-level savings (name and role)?
• Are there any CFO non-financial conditions tied to continuation (e.g., minimal headcount impact, vendor diversity, capital treatment)?

What’s Really Getting in the Way of a Clean Migration?

• What’s the single most common reason past modernization efforts at your bank (or peers) failed to hit their milestones? Options: Underestimated legacy complexity, Poor governance/decisioning, Regulatory pushback, Data quality surprises, Loss of institutional knowledge, Vendor delivery problems, Other
• Tell us about the legacy holdouts—systems, teams, or processes you suspect will resist being retired. Who are they and why?
• How accurate is your current inventory of mainframe programs, middleware integrations, and undocumented interfaces (select best fit)? Options: Highly accurate (>=90%), Mostly accurate (70–90%), Partial (50–70%), Fragmented/unknown (<50%)
• What internal knowledge risks exist (single points of expertise, retirees, contractors) that could derail cutover or stabilization?
• If we identify large undocumented complexity, how willing are you to pause funding until we re-baseline scope and cost? Options: Very willing, Somewhat willing, Prefer to continue with contingency, Not willing

Who Signs Off — Your Practical Acceptance Model

• Which of the following will be required to formally accept a phase into production? Options: Business acceptance tests, Data integrity certification, Regulatory checklist completed, Operational runbook and playbooks, Rollback plan validated, Independent third‑party validation
• Who has final sign‑off authority for each phase (name and title) and are their sign‑off criteria documented today?
• How long of a stabilization window do you require after each cutover before declaring a phase successful? Options: 1 week, 2–4 weeks, 1–3 months, >3 months
• What rollback triggers or KPIs would automatically require us to revert to legacy operations?
• Are you open to an independent acceptance authority (e.g., external auditor or industry peer) participating in phase sign-offs? Options: Yes — preferred, Maybe — with defined scope, No — internal only

Proof You Can Trust — References, People, and Past Performance

• What evidence will most reassure your Head of Regulatory and Board that we can deliver without exam headaches: bank references, CVs, a pilot, or a written risk mitigation plan? Options: Bank references (similar asset size), Interviews with Project Director and Lead Architect, A small pilot/proof-of-value, Detailed written risk mitigation and rollback plan, All of the above
• Which comparable banks (asset range, core platform) would you like us to provide as references? List names or describe the profile.
• Would your regulator want to interview our proposed Project Director or Lead Architect before contract signature? Options: Yes — required, Maybe — on request, No — not required
• What track record details matter most when evaluating references (time on similar program, outcomes delivered, examiner feedback)? Options: Program duration and on-time delivery, Measured cost takeout achieved, Regulatory acceptance/feedback, Quality of cutover/stabilization, Retention of business continuity
• Are there any red flags in a vendor’s past work that would automatically disqualify them (e.g., subcontracting core work, missing regulatory experience)?

Data, Access, and Runbooks — Pre-Deployment Signals We Need Now

• How would you rate current data quality for accounts, transactions, and customer profiles that will migrate in phase one? Options: High (minor clean-up), Moderate (targeted remediation needed), Low (extensive remediation), Unknown
• What access or environment constraints will slow discovery and planning (restricted production access, segmented teams, third‑party gatekeepers)? Options: Restricted production access, Siloed teams with separate SLAs, Third-party vendors with limited cooperation, No constraints identified, Other
• Do you maintain runbooks and rollback playbooks that are current and tested for critical core processes? Options: Yes — current and tested, Yes — but not recently tested, Partially — some runbooks, No
• Who owns data quality certification and where is that responsibility reflected in acceptance gates?
• Would you be willing to fund a short initial sprint to remediate immediate data risks before the main discovery effort? Options: Yes — recommended, Maybe — depends on estimate, No — keep within discovery

Where Do We Start—Immediate Next Steps and Early Wins

• If we could secure one early win in the first 8–12 weeks, which would matter most to your board and CFO: a validated phase one cost model, a regulator briefing accepted, or a small pilot demonstrating parallel-run capability? Options: Validated phase one cost model, Regulator briefing acceptance, Pilot demonstrating parallel-run capability, Other
• What timeframe would your leadership expect for delivery of a phased business case after discovery begins? Options: 4 weeks, 6–8 weeks, 8–12 weeks, 12+ weeks
• Who needs to attend a technical kickoff within the first two weeks to unblock discovery (names/roles)?
• What constraints (procurement windows, board meetings, exam cycles) must we plan around for initiating phase one?
• On a scale from 1–5, how ready are you to proceed with a formal phased business case and vendor evaluation after this discovery (1 = not ready, 5 = ready now)? Options: 1, 2, 3, 4, 5

Quick Snapshot — Who's in the Room?

• Which role are you completing this with today? Options: CIO/CTO, CFO, Head of Regulatory Affairs, Head of Operations, Enterprise Architect, Other
• Tell us your bank's total assets (approximate range). Options: $20B–$50B, $50B–$100B, $100B–$200B, Other / Prefer not to say
• When did the board mandate for digital account opening land, and what is the target launch window? Options: Within 6 months, 6–12 months, 12–18 months, 18+ months
• Who is the executive sponsor and who is the day-to-day project owner?
• Is there an existing budget envelope or a requirement for phased business-case milestones? Options: Preset budget with phases, Budget requires phase approvals, No budget yet — concept stage, Other

If You Could Wave a Wand, What Would Stop Costing You a Fortune?

• What would it feel like if 40–60% of your IT budget were freed for innovation instead of maintenance? Options: Transformational — we could accelerate product roadmaps, Meaningful — would fund several initiatives, Marginal — other constraints block value, Unsure
• Estimate the percentage of your IT budget currently consumed by mainframe and legacy maintenance. Options: <20%, 20–39%, 40–59%, 60%+
• Which cost categories add up to that maintenance burden (select all that apply)? Options: Mainframe capacity (MIPS/CPU), Software licenses, Third-party support/outsourcing, Long-tenured in-house staff, Incident remediation (outages/fixes), Regulatory reporting & controls
• Give a recent example where maintenance costs or technical debt directly delayed a business initiative.
• How would your CFO judge acceptable cost-takeout per phase (range or percent)? Options: <5% per phase, 5–10% per phase, 10–20% per phase, Target-driven by business case

Are We Just Living With It? — The Mainframe Reality Check

• When you think of your mainframe footprint today, what single sentence captures its biggest constraint?
• How many core applications and supported subsystems run on your mainframe (approximate counts)? Options: 1–3, 4–7, 8–15, 16+
• Which languages and runtimes are dominant in your mainframe estate? Options: COBOL/CICS, Assembler, PL/I, DB2/IMS, Other / mixed
• How often do you perform releases to core systems and how long does a release window typically take? Options: Weekly, Monthly, Quarterly, Ad hoc / only for critical fixes
• Share a recent incident where legacy limitations caused customer impact or regulatory attention.
• On a scale from 1–10, how confident are you in your current ability to roll back a failed core change without major customer disruption? Options: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

How Tangled Is Your Middleware? — Unpacking Integration Sprawl

• If we traced every integration point today, would you describe it as clean and documented or a web of one-off adapters? Options: Mostly documented & standardized, Significant one-off integrations, Mostly point-to-point spaghetti, We don't know — no inventory
• Approximately how many distinct middleware products or custom integration layers are in production? Options: 1–3, 4–7, 8–15, 16+
• Which patterns describe your current integration approach (select all that apply)? Options: Point-to-point interfaces, Enterprise Service Bus (ESB), API gateway, Batch file exchanges, Screen-scraping/legacy adapters, Event-driven messaging
• How long does it typically take to onboard a new third-party partner or fintech for a production integration? Options: Days, Weeks, 1–3 months, 3+ months
• How often do integration failures lead to operational incidents or manual reconciliation work? Options: Daily, Weekly, Monthly, Rarely
• Share one integration that keeps showing up as a blocker in projects—what makes it hard?

Who Holds the Keys? — Mapping Institutional Knowledge Risk

• How concentrated is critical systems knowledge in a small number of people? Options: Highly concentrated (1–2 people), Moderately concentrated (3–6 people), Distributed across teams, We don't know
• What proportion of the team maintaining legacy systems has tenure of 10+ years? Options: >70%, 40–70%, 10–40%, <10%
• Do you have current runbooks, architecture diagrams, and test suites that would support a phased migration? Options: Comprehensive and current, Partial and outdated, Minimal or missing, Planned but not executed
• Have any key maintainers signaled retirement or potential departure in the next 12–24 months? Options: Yes — several, Yes — a few, No, Unknown
• When institutional knowledge is lost, describe the typical downstream impact you experience.
• What steps (if any) are in place to capture tribal knowledge and convert it into testable, automatable artifacts? Options: Document capture & pairing, Automated tests & CI, No formal approach, Pilot initiatives underway

Show Me the Money — Run-Rate, Hidden Costs, and True Spend

• What is your best estimate of annual run-rate spend attributable to legacy systems (maintenance, licenses, vendors, staff)? Options: <$5M, $5M–$15M, $15M–$50M, $50M+
• Which of these categories drive the largest portion of that run-rate spend? Options: Mainframe capacity/hosting, Third-party maintenance contracts, In-house FTEs, Incident remediation/overtime, Regulatory reporting effort
• Have you tracked unplanned legacy-related spend over the past 12 months (yes/no) and can you share examples? Options: Yes — documented and quantified, Yes — anecdotal only, No tracking, Prefer not to share
• How do you currently measure cost-takeout once a migration phase completes? Options: Actual budget reductions, Workforce redeployment, Avoided upgrade costs, We lack a formal metric, Other
• What would a credible, CFO-acceptable savings milestone look like at the end of Phase 1? Options: Hard dollar savings in <12 months, Measurable FTE redeployments, License elimination, Risk reduction with quantified cost avoidance
• Describe the last time an unexpected legacy cost eroded your business case—what happened and how was it handled?

If the Regulator Walked In Tomorrow — Controls, Exams, and Comfort

• What would the OCC/FDIC ask first if they reviewed your proposed phased migration plan today?
• Have prior exams flagged technology risk areas tied to your legacy stack (select all that apply)? Options: Change management, Business continuity, Access controls, Vendor management, Data integrity, None
• How close is your current control documentation to 'exam-ready' for a vendor-led modernization? Options: Fully exam-ready, Mostly ready with gaps, Significant gaps exist, We haven't assessed
• Who in your organization would the regulator expect to meet with about the phased plan (roles/titles)?
• What evidence or reference points does the Head of Regulatory typically require before green-lighting a contract? Options: References at similar banks, Resume of project director/lead architect, Phased delivery & rollback plan, Exam calendar mapping, All of the above
• Have you had conversations with examiners about sequencing work around exam cycles? If so, what constraints emerged?

What Would a Successful Phase Actually Look Like?

• What are the non-negotiable acceptance criteria we must demonstrate to sign off a phase? Options: Data integrity verified, No critical production incidents, Regulatory acceptance, End-to-end reconciliation, Performance SLAs met
• What quantitative KPIs will you use to judge cost-takeout and operational improvement? Options: Annual run-rate reduction (%), FTEs eliminated/redeployed, Incident count reduction, Processing latency improvement, Other
• What would be an acceptable percent cost reduction after a single phase to keep the CFO comfortable? Options: <5%, 5–10%, 10–20%, >20%
• What rollback triggers or safety nets are essential for your team to approve a cutover? Options: Data mismatch threshold, Customer-impact threshold, Time-to-stabilize limit, Regulatory escalation
• Who must approve phase acceptance (list roles), and what scheduling constraints do they impose?
• Describe a successful phased delivery you've seen—what made it feel safe and credible to stakeholders?

Constraints, Calendars, and Commitment — Are the Windows There?

• Which upcoming regulatory exam cycles are immovable and must be respected in scheduling work? Options: Next 3 months, 3–6 months, 6–12 months, Not applicable / flexible
• What blackout periods (e.g., quarter-end, peak season) would prohibit cutovers or major releases? Options: Monthly/quarter-end close, Peak consumer season, Audit windows, No major blackout periods
• How quickly can your governance forum make a decision to proceed with a phase once a business case is presented? Options: Within 1 week, 1–4 weeks, 1–3 months, Longer / ad hoc
• What internal approvals or committees (and their cadence) will a phased business case need to pass?
• If we proposed a discovery assessment this month, what constraints might prevent you from starting within 30 days? Options: Resource conflicts, Budget timing, Exam scheduling, No constraints
• Which stakeholders must be engaged before a discovery can access environments, logs, and runbooks? Options: CIO/CTO, Head of Ops, Security/InfoSec, Regulatory Affairs, Vendor managers

Deciding to Move — Practical Next Steps

• Given everything we've discussed, what would be your single highest-priority outcome from a current-state mapping? Options: Accurate scope & cost estimate, Regulator-aligned phased plan, Target architecture options, Quick wins for cost reduction
• Which artifacts would you want delivered at the end of our discovery engagement? Options: Inventory of mainframe apps & interfaces, Run-rate cost model, Knowledge-risk heat map, Phase sequencing & rollback playbooks, Regulatory readiness checklist
• What decision criteria will you use to choose a systems integrator for the implementation phase? Options: Banking domain expertise, Proof of work at similar banks, Delivery capacity, Regulatory comfort, Commercial terms
• How would you prefer we present findings to your board and regulators (formats and audiences)? Options: Executive one-pager & board deck, Technical annex for examiners, Workshop with execs & regulators, All of the above
• Realistically, who's needed from your side for a discovery that uncovers the true scope (roles & estimated hours)?
• On a scale from 1–5, how ready are you to commission a rigorous current-state mapping now? Options: 1 - Not ready, 2 - Slightly ready, 3 - Somewhat ready, 4 - Mostly ready, 5 - Fully ready

Quick Snapshot: Who’s Steering This Ship?

• In one sentence, what is the single most important outcome you need from the upcoming cutover?
• Which executives will actively sponsor or block this deployment? (select all that apply) Options: CIO, CFO, Head of Regulatory Affairs, COO/Head of Operations, CEO, Board Committee member, Other
• Who will be the single point of accountability (RACI: A) for executing the cutover on your side? Options: CIO, Project Director, Head of Ops, Head of Reg, Third-party Delivery Lead, Other
• Which timeline best matches your target for the next deployment phase? Options: Within 30 days, 1–3 months, 3–6 months, 6–12 months, 12+ months
• What are the top three stakeholder emotions you’re hearing about the cutover (e.g., fear of disruption, urgency to save costs)?

If An Examiner Walked In Today, What Would Make You Nervous?

• If an OCC or FDIC examiner asked whether you’re ready to cut over this month, what gap would make you lose sleep?
• Which regulatory approvals must be demonstrated before a phase gate is closed? (select all that apply) Options: OCC technology risk checklist, FDIC examiner sign-off, State regulator acknowledgement, Internal audit attestation, Board or committee approval, External auditor review
• Do you have a documented pre-contract regulatory checkpoint for this modernization effort? Options: Completed and approved, In progress, Planned but not started, Not done
• What concrete artifacts would you present to an examiner to prove controls were preserved during migration? Options: Test results and reconciliations, Runbooks and rollback scripts, Change logs and approvals, Reference bank visit reports, Operational runbooks, Other
• How would your Head of Regulatory describe their current confidence in the acceptance gates and evidence package? Options: Very confident, Somewhat confident, Hesitant, Not engaged

What’s Really Lurking in Your Data?

• If we only migrated the ‘clean’ records today, how much remediation would still be required to meet business and regulator expectations? Options: Negligible (<5%), Small (5–15%), Moderate (15–35%), Large (35–60%), Very large (>60%)
• Which systems are the authoritative sources for customer, account, and transaction data? (select all that apply) Options: Mainframe core, Middleware ledgers, CRM/Customer master, Data warehouse/data lake, Third-party processors, Branch/local systems
• Rate your overall data quality today across completeness, correctness, and timeliness (1 = broken, 5 = production ready) Options: 1, 2, 3, 4, 5
• Do you have automated reconciliation and validation pipelines? If yes, where are they run and who owns them? Options: Yes — CI/CD pipeline (DevOps), Yes — Scheduled jobs (Ops team), Partial — manual steps exist, No
• Describe a recent migration or release where data issues surfaced unexpectedly — what happened and how long did remediation take?

Access and Environments: Can Our Teams Get in and Run?

• If our engineers requested environment access today, what obstacle is most likely to slow them down?
• Which of these environments are available and refreshed with production-like data? (select all that apply) Options: Dev (internal), QA (internal), Staging / Pre-Prod (near-prod), UAT (business-owned), Pre-Prod with masked data, Production (restricted)
• Are environment refresh windows, lead times, and request owners documented and SLA’d? Options: Yes — documented with SLAs, Partial — informal SLAs, Planned but not documented, No
• What access controls or approvals block integrator engineers from running high-fidelity tests (select all that apply)? Options: VPN / network restrictions, Jumpbox with approvals, MFA / SSO policies, Background checks / contractor onboarding, Vendor NDAs / contractual limits, None
• Share an example of a time environment access delayed a release — what was the root cause and impact?

Runbooks, Rollback, and the Moment of Truth

• What single real-world failure would force you to trigger rollback during cutover, and why would that be non-negotiable?
• Do you have cutover and rollback runbooks that are version-controlled and regularly tested? Options: Complete and tested, Drafted but untested, Partially documented, No runbooks
• Who has the explicit authority to call a rollback and how is that decision governed? Options: CIO, Project Director, Head of Ops, Cross-functional committee, Head of Regulatory Affairs, Other
• How often have you rehearsed a full rollback or simulated cutover in the last 12 months? Options: Never, Once, 2–3 times, Quarterly, Monthly
• Which key metrics will be watched in real time to validate success or trigger rollback (list the top 5)

People Risk: Who’s Holding the Keys?

• If three senior legacy platform experts left tomorrow, how would you keep critical services running during migration?
• How many staff today have deep, operational knowledge of the legacy mainframe and batch processes? Options: 0, 1–3, 4–10, 11–25, 25+
• Do you have an executed knowledge-transfer and shadowing plan tied to the cutover schedule? Options: Yes — formal and scheduled, Partial — informal plan, Planned but not started, No
• Which roles are mission-critical for day-one post-cutover? (select all that apply) Options: Core ops team, Batch scheduler, DBA, Middleware admin, Network/security, Business operations/desk, Customer service
• Are there any upcoming retirements, notices, or contractor expirations that could create a knowledge gap during the next 6–12 months? Options: Yes — specific people, Yes — several roles at risk, No, Unsure

What Would the CFO Want to See in 30 Days?

• If the CFO asked for a one-line business-case headline 30 days after phase-1, what result would make you look like a hero?
• Which phase-level cost-takeout targets are currently defined (choose one)? Options: Not defined, <10%, 10–20%, 20–30%, 30–50%, >50%
• Which KPIs will determine whether a phase is accepted? (select all that apply) Options: Run-rate cost reduction, Incident rate / severity, Transaction latency, Reconciliation success rate, Regulatory compliance incidents, Customer experience metrics
• How will cost-takeout be measured and validated (accounting line, FTE reductions, run-rate)? Options: Run-rate / Opex, FTE count and roles, Total cost of ownership (TCO), Business-case KPIs, Other
• If a phase misses its cost or reliability targets by 10%, what remediation levers are acceptable to your leadership?

Readiness Checklist — Let’s Be Brutally Honest

• Which of these readiness items are fully complete today? (select all that apply) Options: Data quality >95% for migrated scope, Environments provisioned and refreshed, Cutover runbooks written and versioned, Rollback plan defined and tested, Staff trained for day-one operations, Regulatory approvals in hand, Integration endpoints certified, Monitoring and alerting configured
• For any item not complete above, please state the expected completion date and primary blocker.
• How confident are you in proceeding to deployment as currently planned? Options: Very confident, Somewhat confident, Hesitant — needs mitigation, Not ready
• What single action would most increase your confidence in go/no-go decisions over the next 30 days?
• Would you agree to a joint readiness review with our delivery leads and your Head of Regulatory Affairs within the next two weeks? Options: Yes — schedule it, Maybe — need to check calendars, No — prefer a later date

Start: The Board Gave You a Deadline — Tell Us the Story

• What was the exact board mandate or trigger that started this modernization conversation?
• What is the deadline the board set (or the window they expect) for delivering digital account opening capability? Options: < 6 months, 6–12 months, 12–18 months, 18–24 months, > 24 months
• Who at the executive level is most invested in meeting that deadline (title or names)?
• How would you describe the tone from the board—urgent, cautious, financially strict, politically sensitive, or other? Options: Urgent, Cautious, Financially strict, Politically sensitive, Other
• What happens if the deadline is missed—what are the consequences the board or exec team has communicated?
• If you could summarize in one sentence what success looks like to the board, what would it be?

Are We Building the Future or Stacking Two Platforms for Years?

• Do you accept the risk of running a legacy and new platform concurrently for multiple years, or is single-platform transition non-negotiable? Options: Accept risk of long parallel run, Prefer phased single-platform with strict gates, Undecided
• Please quantify your current mainframe footprint: number of cores/apps, years in production, and approximate % of transactions flowing through it.
• Which middleware, third-party layers, or bolt-on systems were added after serial M&A and are hardest to untangle?
• What percentage of your annual IT budget is currently spent on maintenance and run-rate support (best estimate)? Options: <20%, 20–40%, 40–60%, 60–80%, >80%
• How confident are you that your documented inventory reflects the true estate (apps, interfaces, batch jobs)? Options: Very confident, Somewhat confident, Low confidence, We don’t have an inventory
• Who holds the deepest institutional knowledge of the legacy systems, and how likely are they to stay through migration?

Who Really Pulls the Levers Here?

• If the modernization introduces any regulator comment or examiner question, who must be briefed and who signs off before going forward?
• Beyond CIO and CFO, which roles must be engaged—Head of Regulatory, Chief Risk Officer, business-line heads, operations—and who has final say? Options: CIO, CFO, Head of Regulatory Affairs, CRO, Business Head(s), Board committee
• How structured is the governance forum you expect for this program (steering committee cadence, escalation path, decision SLAs)? Options: Mature (weekly steering, clear SLAs), Informal (monthly check-ins), Ad hoc
• How does the Head of Regulatory typically evaluate an integrator—references, interviews, prior exam language, or something else? Options: References, Live interviews with proposed leads, Regulatory-friendly runbooks/demos, Proof of exam-friendly experience, Other
• Describe a recent executive decision where competing priorities (speed vs. risk vs. cost) forced a compromise—what was chosen and why?

Show Me Measurable Wins—or We Can’t Sign

• What minimum cost-takeout or run-rate reduction per phase will satisfy the CFO and keep the program funded? Options: <5%, 5–10%, 10–20%, 20–30%, >30%
• How do you currently measure run-rate cost—by application, by FTE, by vendor spend, or a blended metric? Options: By application, By FTE, By vendor/licencing spend, Blended metric, Unknown
• What acceptance criteria must be met at each phase before commercial payments or next-phase funding is released?
• Who in finance will validate the cost-takeout numbers (controller, FP&A, external auditor)? Options: Controller, FP&A, External auditor, CFO personally, Other
• Would you accept an external third-party cost validation (e.g., independent run-rate audit) as part of phase acceptance? Options: Yes, required, Yes, optional, No
• How should savings be tracked and reported—quarterly dashboards, rolling 12-month view, or milestone-based snapshots? Options: Quarterly dashboards, Rolling 12-month, Milestone snapshots, Ad-hoc reports

What Would 'Safe' Look Like to Your Regulators?

• What specific evidence or artifacts would satisfy your regulator that risk remains controlled during migration? Options: Parallel run results, Rollback plans, Security test reports, Detailed runbooks, Audit logs, Other
• Has your institution had recent OCC/FDIC examiner findings related to technology, vendor oversight, or data quality that we need to consider? Options: Yes—material findings, Yes—minor findings, No, Unknown
• How closely do exam cycles constrain your production cutover windows (must avoid exams, can align, or no constraint)? Options: Must avoid exam periods, Can align with exam windows, No constraint / flexible
• Would the regulator require interviews with our proposed project director and lead architect before sign-off? Options: Yes, Maybe / case-by-case, No
• What format of regulator-facing documentation do you prefer—executive brief + technical annex, or full risk assessment and test evidence? Options: Executive brief + annex, Full risk assessment with evidence, Informal Q&A, Other

If This Stalls, What Breaks First?

• Which single outcome would you consider mission-critical to protect if a phase stalls (customer onboarding, transaction integrity, liquidity reporting, regulatory compliance)? Options: Customer onboarding, Transaction integrity, Liquidity/reporting, Regulatory compliance, Other
• Rank the top three program risks you fear most: scope creep, data remediation delays, institutional knowledge loss, vendor delivery failure, cost overruns. Options: Scope creep, Data remediation delays, Institutional knowledge loss, Vendor delivery failure, Cost overruns
• How long can the organization tolerate running parallel operations before costs or operational risk becomes unacceptable? Options: <3 months, 3–6 months, 6–12 months, 12–24 months, >24 months
• What contingency reserves (time or budget) have you set aside for unexpected remediation or extended parallel runs? Options: None, Small (5–10%), Moderate (10–20%), Significant (>20%)
• Tell us about a past IT program that stalled—what were the root causes and what lessons should we apply to avoid repeating them?

How Do You Want to See the Work Sequenced Around Exams and Business Cycles?

• Do you prefer a phased approach that delivers measurable functionality and cost reductions each quarter, or larger waves that consolidate risk but deliver bigger chunks less often? Options: Quarterly small phases, Larger waves, Hybrid
• Which business processes should be in the earliest phases because they unlock the most value or reduce the most risk?
• What are your hard no-go windows for cutovers and why (peak business periods, regulatory exams, seasonal processing)?
• What level of parallel-run validation do you require—full synthetic reconciliation, partial shadow mode, or business-line spot checks? Options: Full synthetic reconciliation, Partial shadow mode, Business-line spot checks, Other
• What rollback triggers would force an immediate stop and rollback to the legacy platform?

People, Roles, and Who's Actually Doing the Work

• Do you have internal SMEs and dedicated FTEs who will be assigned to this program, or will resources be nominated on an as-needed basis? Options: Dedicated FTEs available, Nominated as-needed, Mix of both, No internal capacity
• Which roles must remain in-house for compliance or continuity (data stewards, core ops leads, security owners)?
• How do your teams feel about change—energized, cautious, or resistant—and how has that manifested in prior large tech changes? Options: Energized, Cautious, Resistant, Mixed
• What training, shadowing, or knowledge-transfer cadence do you want built into each phase to minimize knowledge loss? Options: Weekly shadow sessions, Documentation + workshops, Train-the-trainer, On-job mentoring, Other
• Who will own day-to-day decisions on technical trade-offs—your CTO office, a program director, or a joint governance team? Options: CTO office, Program director, Joint governance team, Other

Data and Integrations: What Keeps You Up at Night?

• How would you describe current data quality and reconciliation maturity across accounts, customer records, and transaction history? Options: High maturity, Moderate, Low, Unknown
• Which datasets are most fragile or mission-critical during migration (e.g., balances, loans, KYC, transaction history)?
• What level of environment access will our teams need for profiling, testing, and reconciliation, and are there constraints (masking, PII rules)? Options: Full access with masking, Restricted access, No access without signoffs
• Do you have existing reconciliation tools or automated data pipelines we should integrate with, or will reconciliation be manual initially? Options: Automated tools available, Some tools, some manual, Mostly manual
• What acceptable error rates or reconciliation tolerances will the business accept during parallel runs? Options: Zero tolerance, <0.1%, <1%, <5%, Negotiable

Decision, References, and Regulatory Proof: What Will Make You Press 'Go'?

• What evidence from an integrator would make the Head of Regulatory comfortable—case studies, examiner testimonials, direct reference calls, or shadowed demos? Options: Case studies, Examiner testimonials, Direct reference calls, Shadowed demos, Other
• How important is working with a team that’s bank-specialist rather than a generalist consultancy when it comes to passing exams? Options: Critical, Important, Nice to have, Not important
• How will you validate the proposed project director and lead architect—live interviews, recorded sessions, or onsite meetings with your regulators present? Options: Live interviews, Recorded sessions, Onsite meetings, No validation
• Are there procurement or contractual checkpoints that must be cleared before technical work can begin (insurance, SOC reports, SLAs)? Options: Yes—many checkpoints, A few standard checkpoints, No major checkpoints
• What reference profile matters most—banks of similar asset size, same core platform experience, or documented regulatory-friendly migrations? Options: Similar asset size, Same core platform, Regulatory-friendly migrations, All of the above

Near-Term Next Steps: What Will Put This Program on a Safe Path?

• If we agreed on a pilot or discovery sprint next, how soon could you commit to start (and what would 'start' look like)? Options: Immediately, In 2–4 weeks, 1–3 months, Longer / need prep
• What are the top three milestones you need to see in the first 90 days to feel this is going in the right direction?
• How would you prefer progress and risk updates—weekly tactical, biweekly steering, monthly exec summaries, or a mix? Options: Weekly tactical, Biweekly steering, Monthly exec summaries, Mix
• Which single metric would convince your CFO and board this program is on-track (cost takeout %, time-to-live for digital account opening, regulator sign-off, or another)? Options: Cost takeout %, Time-to-live for digital account opening, Regulator sign-off, Other
• Who should we put in the room for a 90-minute discovery working session to validate assumptions and co-design the first phase?