Quick Program Snapshot — Tell Us One Thing

• In one sentence, how would you summarize this hardware program's verification and DO-254 objective?
• Who is the primary program contact we should talk to about certification progress and decisions? Options: Hardware Design Lead, Program Certification Manager, Verification Lead, Systems Engineer, Procurement/Contracts, Other — specify
• Which hardware types are included in scope for this program? Options: FPGA (single device), Multiple FPGAs, ASIC, SoC/Complex PLD, Board-level with multiple devices, Other
• What Design Assurance Level (DAL) has been assigned or is expected for the safety-critical functions? Options: DAL A, DAL B, DAL C, DAL D, Unknown / Not yet assigned
• What phase is your project currently in? Options: Requirements definition, Architectural design, RTL development, Verification in progress, Pre-certification / audit prep, Post-certification maintenance
• Target certification or delivery milestone (month/year) — if you don’t have one, tell us the driver that will set the date.

What’s Been Sneaking Up on You?

• What’s the single verification failure, evidence gap, or inefficiency you’ve been tolerating that you suspect is most likely to derail certification?
• How often do unexpected coverage gaps or failed audits appear late enough to impact schedule? Options: Almost every release, Several times per year, Occasionally (once per project), Rarely, Never
• When those surprises happen, what is the usual root cause you observe? Options: Insufficient requirements traceability, Incomplete structural coverage, Toolchain incompatibility, Poor testbench design, Configuration management failures, Human process errors, Other — describe
• Tell us about a recent incident where verification problems cost time or credibility — what happened, who noticed it, and how long did recovery take?
• How does this situation make the team feel — frustrated, anxious, resigned, stretched thin, or something else? Options: Frustrated, Anxious, Overworked, Resigned/used to it, Motivated to fix it, Other — describe

If a DER Opened the Door Today, What Would Make You Nervous?

• Which specific artifact types do you worry are weakest or most likely to fail scrutiny? Options: Requirements-to-test trace matrices, Structural coverage reports, Configuration management records, Test procedure documentation, Tool qualification notes, Other — specify
• What percentage of your RTL modules currently meet your internal structural coverage targets (approximate numbers welcome)? Options: 0–25%, 26–50%, 51–75%, 76–90%, 91–100%, Don't measure consistently
• How are you producing traceability today? Options: Manual spreadsheets, Scripted export from tools, Integrated requirements management tool, No formal traceability yet, Other — describe
• Which of these is mostly manual in your evidence chain (select all that apply)? Options: Coverage aggregation, Traceability mapping, Artifact formatting for audit, Configuration management snapshotting, DER sign-off tracking
• Have you ever had evidence rejected or required rework by a certification authority or DER? If yes, what was rejected and why? Options: Yes — coverage-related, Yes — traceability-related, Yes — CM/process-related, No, Prefer not to say

Who Decides and Who Silently Blocks?

• Which decision-maker on your program could stop momentum and hasn’t been part of the technical conversations yet?
• Which roles are actively approving verification strategy and artifacts today? Options: Program Certification Manager, Hardware Design Lead, Verification Lead, Systems Engineering, DER (assigned or consulted), Procurement/Legal
• What level of DER involvement have you anticipated or already secured? Options: DER fully engaged from planning, DER consulted intermittently, DER to be engaged at audit time, No DER planned yet, Unknown
• How long does it typically take to get a certification-related decision or budget approval on your programs? Options: <1 week, 1–2 weeks, 2–4 weeks, 1–3 months, >3 months
• Who on your team feels the most pressure around DO-254 delivery, and what keeps them up at night?

Design the Perfect Verification Week — What’s Different?

• Imagine one verification run produced audit-ready evidence at the end of a single week — what outputs must it include to be believable? Options: Per-module structural coverage reports, End-to-end traceability matrix, Repeatable regression scripts, CM snapshot and baselines, DER review notes
• What numeric coverage thresholds or criteria would your team and the DER agree are acceptable for each module or design level? Options: Statement/Toggle/Condition goals, MC/DC equivalent for hardware, Function-level acceptance only, No firm numeric goal — narrative acceptance
• What schedule constraints (freeze dates, critical tests, supplier deliveries) would limit your ability to run a concentrated verification effort?
• How automated are your current regression and evidence-collection pipelines? Options: Fully automated with CI, Partially automated, Manual test runs + scripts, Entirely manual
• If we could eliminate one repetitive manual task in your verification flow, which would have the biggest impact?

Rethinking Your Toolchain — What’s Sacred?

• Which tools are you actively relying on today for simulation, synthesis, and coverage analysis? Options: ModelSim/Questa, VCS/Incisive, Xilinx/Intel vendor flows, In-house scripts, Third-party coverage analyzers, Other — list
• Which integrations are non-negotiable because of vendor, certification, or supplier constraints? Options: Specific simulator, Requirements tool (DOORS/Polarion), CM system (Jenkins/Git/SVN), DER-preferred formats, None — flexible
• What integration or compatibility problems have cost you time recently (give a concrete example)?
• How open is your team to introducing a new verification tool or module if it reduces manual evidence work? Options: Very open — ROI needed, Open with POC, Skeptical — needs DER buy-in, Not open due to constraints
• What IT, security, or licensing constraints would govern how new tools are deployed (air-gapped, on-prem, cloud, license model)? Options: Air-gapped/on-prem, Hybrid (on-prem + cloud), Cloud allowed, License-centralized, Floating licenses required, Other — describe

Buying, Budget, and the Real Decision Timeline

• How have commercial terms or procurement cycles forced technical compromises on past certification projects?
• What is your procurement timeline for verification tools or consulting services? Options: Immediate (30 days), Short (1–3 months), Medium (3–6 months), Longer (6–12 months), Undetermined
• Which commercial models do you prefer for verification and consulting engagements? Options: One-time license + services, Subscription + services, Time & materials for consulting, Milestone-based payments, POC then purchase
• Would your team require a proof-of-concept (POC) with sample artifacts before committing? If yes, what would success look like for the POC? Options: Yes — pass specific coverage metrics, Yes — produce DER-acceptable traceability, No — confident to buy, Undecided
• Who must sign off commercially before we can start a POC or pilot? Options: Program Manager, Procurement, Legal, CFO/Finance, Technical Lead

If We Had 30 Days — The Smallest Test That Proves Progress

• What is the smallest, most convincing deliverable we could produce in 30 days that would reduce your certification risk? Options: Module-level coverage reports + trace, Automated regression demonstrating repeatability, DER-ready artifact package for a critical module, CM baseline + reproducible runbook, Other — specify
• Which piece of data, access, or artifact would unblock that 30-day win?
• Who would own the day-to-day execution and who would be the DER or reviewer during this 30-day test?
• What internal blockers could stop us from starting this 30-day work immediately? Options: No budget, No DER assigned, No tool licenses, Access restrictions (air-gap), Team bandwidth, Other — describe
• If we delivered that 30-day package, what would you expect as the next decision or milestone? Options: Proceed to roll-out, Extend POC to more modules, Request additional consulting, Bring DER for formal review, Procurement negotiation

Quick Snapshot: Your Current Verification Setup

• In one sentence, how would you describe your current HDL verification setup and what it’s supposed to prove?
• Which HDLs and source-control formats hold your primary flight-critical designs? Options: VHDL, Verilog, SystemVerilog, Mixed VHDL/Verilog, Chisel/Other RTL, Not sure / multiple repos
• Which simulator(s) or emulation platforms do you regularly use for functional verification? Options: ModelSim/Questa, VCS, Xcelium, Cocotb/Python + simulator, FPGA hardware-in-the-loop, Formal engines (Jasper/OneSpin), Other, None / ad-hoc
• How would you characterize the balance between automated testbench runs and manual test activities today? Options: Mostly automated regression suites, Balanced automation + manual, Mostly manual directed tests, Ad-hoc smoke tests only
• Roughly how often do you run full verification cycles that aim to collect structural coverage (e.g., daily, per commit, per milestone)? Options: Per commit/CI, Nightly, Weekly, Per milestone, Rarely / only at reviews

Are You Comfortable With What You Don't See?

• What would it mean for your program if there were unknown blind spots in the HDL verification evidence that only surface during certification?
• Which types of coverage do you trust less today—statement/line, branch, condition/decision, toggle/bit, FSM transition, or other? Options: Statement/line, Branch, Condition/Decision (C/D), Toggle/bit coverage, FSM state/transition coverage, Functional coverage, I don't know the difference
• How often have late-discovered coverage gaps forced scope changes, test rewrites, or schedule slips on past projects? Options: Frequently, Occasionally, Rarely, Never
• When a gap is found, who typically owns triage and remediation—verification lead, architecture, certification manager, or an external DER/consultant? Options: Verification lead, Architecture/Design lead, Certification manager, DER / external consultant, Shared responsibility, Not defined
• Tell us about the last time a coverage gap felt inexplicable—what evidence did you have, how long to diagnose it, and how did it make the team feel?

Where Coverage Keeps Slipping Through

• If I told you some of your most critical requirements might lack traceable structural evidence today, how surprised would your certification lead be? Options: Very surprised, Somewhat surprised, Not surprised, I don't know
• Which verification artifacts do you currently produce and store as part of your design baseline? Options: Test vectors/scripts, Waveform captures, Coverage reports (tool-specific), Requirements-to-test trace matrix, Design review minutes, Build and toolchain logs, No consistent artifact set
• How do you currently map requirements (system/avionics) to HDL units and to verification tests? Options: Automated traceability tool, Manual spreadsheets, Partial automation + manual, Ad-hoc notes, We don't map requirements yet
• Which parts of the design tend to have the worst coverage or longest debug cycles (e.g., interrupts, safety logic, clock domain crossings, reset sequences)? Options: Interrupt handling, Safety-critical state machines, Clock domain crossing logic, Reset and power-up sequences, Bus/AXI/AVALON interfaces, Sparse datapaths, Other
• Can you point to a recent module or feature where coverage metrics stalled despite more tests—what did you try and what changed (if anything)?

Toolchain Reality Check — What’s Really Running?

• What would it cost you (time, budget, schedule risk) if your existing toolchain artifacts were later rejected by a certification authority?
• Which commercial or open tools form the backbone of your static and dynamic verification (select all that apply)? Options: Vendor structural coverage analyzer (e.g., tool A), Simulator vendor coverage (e.g., tool B), Open-source coverage tools, Static checkers (lint/formal), In-house analysis scripts, CI orchestration (Jenkins/GitLab/Other), We rely on manual processes
• How mature are your build and CI pipelines for repeatable, traceable runs of verification artifacts? Options: Fully automated and versioned, Partially automated, Manual with scripted steps, Ad-hoc manual only
• What integrations matter most to you for any new verification tool (select top three)? Options: Simulator compatibility, VCS/Git integration, Requirements tool integration (DOORS/Polarion), Artifact packaging for audits, CI/CD pipelines, DER review workflows, ERP/Procurement
• Describe any custom wrappers, scripts, or vendor patches you depend on to get coverage reports into an auditor-friendly format.

Artifacts and Evidence — Audit vs. Day-to-Day

• If an auditor asked for the ‘single source of truth’ proving a DO-254 objective for a module, could you assemble it in under a week? Options: Yes, under a day, Yes, under a week, No, would take several weeks, No, would take months, Unsure
• Which certification artifacts do you already produce in a repeatable way (traceability matrix, coverage baseline, verification plan, test summaries)? Options: Requirements Traceability Matrix (RTM), Verification Plan/Procedures, Coverage Baselines, Test Reports and Logs, Configuration Management records, DER correspondence, None consistently produced
• Who currently owns artifact packaging and CM for certification—program CM, verification engineer, procurement, or external support? Options: Program Configuration Manager, Verification engineer/team, Certification manager, External consultant/DER, Shared/Not defined
• How do you demonstrate that coverage and tests are tied to the released baseline (tags, build IDs, signed artifacts)? Options: Versioned artifacts in SCM with tags, Build server artifacts with hashes, Manual archival (Zips/Shared drives), Not consistently documented, Other
• Describe any past audit findings related to artifacts or traceability and how they were resolved (what was missing, and what fixed it).

Process Friction: Who Gets Blocked, When?

• What’s the most common reason a verification cycle stalls—test failures, environment setup, unclear requirements, tool bugs, or staff availability? Options: Test failures / non-determinism, Environment/setup issues, Ambiguous requirements, Toolchain problems, Lack of personnel/skill, Other
• Which role experiences the most day-to-day friction: RTL engineer, verification lead, configuration manager, certification engineer, or DER? Options: RTL engineer, Verification lead, Configuration manager, Certification engineer, DER / external consultant, Other
• How long does a typical verification/coverage iteration take from discovery to artifact update and re-run? Options: Hours, A day, Several days, Weeks, Undefined / varies
• When timelines compress, where do you typically cut scope or compromise on evidence (e.g., fewer regression runs, limited traceability, lower coverage thresholds)? Options: Reduce regression frequency, Skip detailed traceability, Lower acceptance thresholds, Defer DER review, Delay non-critical modules, We don't compromise
• Tell me about a recent moment when the team felt blocked—what was the blocker and what helped (or failed) to get past it?

The One Change That Would Unlock Your Schedule

• What single capability—faster root-cause, automated traceability, regulator-friendly coverage packaging, or DER signoff support—would move your critical path most? Options: Faster root-cause for coverage gaps, Automated requirements traceability, Pre-packaged auditor-friendly evidence, DER engagement & templates, CI-driven reproducible runs, Other
• How open is your team to swapping a core tool or workflow if it shortened certification risk by 20–40%? Options: Very open, Open with pilot, Skeptical / needs proof, Not open
• What internal constraints would make adopting a new verification approach difficult (budget, procurement cycles, tool qualification, staff training)? Options: Budget, Procurement timelines, Tool qualification/acceptance, Staff ramp-up/training, Integration with legacy repos, None of the above
• If we designed a short pilot to prove DER-acceptable evidence on a representative module, which module would you pick and why?
• Realistically, what timeline would you need from pilot agreement to usable artifacts for an audit (weeks/months)? Options: 2–4 weeks, 1–2 months, 3–6 months, Longer than 6 months, Unsure

Technical Deep-Dive: Show Me the Flows

• If we walked through your verification flow step-by-step, where would you say the chain of custody for evidence breaks most often?
• Which verification techniques are part of a normal run for flight-critical units (select all that apply)? Options: Unit-level directed tests, Randomized/functional coverage, Constrained-random + functional coverage, Formal verification, Hardware-in-the-loop / FPGA prototyping, Power/clock-domain stress tests, Other
• Do you version and archive verification runs with metadata (tool versions, seed values, environment, commit id)? Options: Yes, fully versioned and archived, Partially (some metadata), No, not consistently, We don't archive verification runs
• How do you currently handle non-deterministic or flaky tests—re-run policy, quarantine, root-cause process, or ignore? Options: Auto re-run until stable, Quarantine flaky tests, Track and root-cause, Ignore and accept noise, We don't have a policy
• Please list the top 3 reports or outputs you’d expect to hand an auditor after a successful verification milestone.
• Would you be willing to share a sanitized flow diagram or sample coverage report for a short technical workshop? Options: Yes — can share now, Yes — after NDA, Maybe with internal approval, No

Quick Check — Where Are You Right Now?

• On a scale from 'we're just starting' to 'fully deployed', how would you describe your current verification readiness for this project? Options: Just starting (no infra), Planning phase (some infra identified), Partially provisioned (some benches/environments), Mostly ready (minor gaps), Audit-ready (we believe so)
• Which FPGA/ASIC families and HDL languages are primary for this program? Options: Xilinx/AMD (Vivado), Intel/Altera (Quartus), Microchip/Microsemi, Custom ASIC (many PDKs), Mixed (multiple vendors), Other
• Who on your team will be the day-to-day owner for verification runs and evidence collection? Please name role(s) and how they prefer to be contacted.
• What timeline milestone do you need verification evidence to be audit-ready by? Options: Within 2 weeks, 1 month, 2–3 months, 3–6 months, More than 6 months
• Briefly describe your existing HDL toolchain and the main simulation/synthesis tools you rely on.

If an auditor asked for a complete verification run tomorrow, could you hand them everything with confidence?

• Where do you currently run most functional verification (local workstations, on-prem cluster, cloud, hybrid)? Options: Local workstations, On-prem cluster, Cloud (public), Cloud (private/VPC), Hybrid
• How automated are your test benches and regression runs today? Options: Fully automated (CI-driven), Mostly automated with manual steps, Ad hoc scripts/manual runs, No automation yet
• Do you have a dedicated hardware lab for bring-up and HW-in-the-loop testing? If yes, briefly describe access policies and availability windows. Options: Yes — freely available, Yes — scheduled/shared, Limited hardware (prototypes only), No hardware lab
• What visibility and debug capabilities do your benches provide (waveform capture, logic analyzers, emulation hooks)? Options: Waveforms + post-sim debug, On-target logic analyzer, Emulation with checkpoints, Limited debug (log-only), Other
• Which parts of running a verification cycle cause the most friction for your engineers (setup time, flaky tests, environment flakiness, long runtimes, licensing)? Options: Setup time, Flaky tests, Environment flakiness, Long runtimes, License constraints, Other

What’s the one recurring failure that forces runs to be restarted or abandoned?

• How often do configuration or toolchain changes invalidate in-flight verification evidence? Options: Almost every change, Often, Sometimes, Rarely, Never
• Describe your current configuration management process for testbenches, DUT RTL, and simulation environments (branching strategy, baselining cadence, artifact tagging).
• Who has permission to modify test environments or push changes that would affect verification runs? Options: Individual engineers, Team leads only, Change board approval, DevOps/infra team only, Other
• Have you experienced verification runs that produced good results locally but failed when reproduced in another environment? If yes, tell us one representative incident and impact.
• Are external consultants or DERs currently allowed access to your environments for verification work? If not, what are the main blockers? Options: Yes — full access, Yes — limited/scheduled access, No — policy restrictions, No — security concerns, No — not needed

Would you hand your current coverage and traceability artifacts to a DER and feel confident they’d sign off, or would you expect rework?

• Which tools produce your structural coverage and traceability artifacts today? Options: Built-in simulator coverage, Third-party coverage tools, Homegrown scripts, No coverage tooling yet, Other
• How do you map requirements to tests and coverage reports (manual spreadsheets, integrated tool, semi-automated pipeline)? Options: Integrated requirements->tests tool, Semi-automated with scripts, Manual spreadsheets, No mapping currently
• What format do you typically present traceability and coverage artifacts in for internal review or audits (CSV, PDF, HTML, proprietary)? Options: HTML dashboard, PDF report, CSV/Excel, Proprietary tool output, Combination
• Which coverage metrics are non-negotiable for your program (statement, toggle, condition, functional, MC/DC, other)? Options: Statement, Branch/Decision, Condition, Toggle/Toggle-aware, Functional/Assertion-based, MC/DC, Other
• Where do you currently track known coverage gaps and required mitigations, and how often are they reviewed? Options: Issue tracker (JIRA/etc.), Spreadsheet, Coverage tool with backlog, Informal/meetings only, Other

If a late design change wiped out two weeks of verification evidence, how confident are you that your team could recover without schedule slip?

• Do you have a formal rollback and rebaseline plan tied to change categories (minor/major/config)? Options: Yes — documented and practiced, Yes — documented but untested, No formal plan, We handle ad hoc
• What redundancy or containment controls do you use to protect verification artifacts from accidental overwrite or corruption? Options: Immutable artifact store, Frequent backups, Branch protection in VCS, Manual checkpoints, None
• How do you quantify and prioritize risk items that could block verification completion (likelihood × impact, owner assignment)? Options: Formal risk register with scoring, Risk list in project plan, Ad hoc prioritization, No formal risk tracking
• When a risk turns into an issue during a run, what’s your escalation path and typical resolution SLA? Options: Immediate team fix (<24h), Next-business-day fix, Escalate to program leads, Escalate to supplier/vendor, Undefined
• Tell us about one past incident where risk controls prevented a failed audit or major rework — what changed afterward?

Could your infrastructure scale to run thousands of small, targeted regressions overnight if needed?

• Do you have CI/CD orchestration for verification (Jenkins, GitLab CI, Azure Pipelines, internal system)? Options: Yes — fully integrated, Partially — some pipelines, Manual scheduling only, No CI/CD
• Where would you prefer to run large-scale regressions given constraints (on-prem cluster, cloud burst, vendor-managed cloud)? Options: On-prem cluster, Public cloud burst, Private cloud/VPC, Vendor-managed service, Mixed approach
• What licensing or security constraints might limit using cloud or shared compute for verification? Options: Security policy prohibits cloud, License per-seat restrictions, Export control/ITAR concerns, No major constraints, Other
• How reproducible are your environments—can another engineer run the same job and get byte-for-byte equivalent artifacts? Options: Yes, reproducible, Mostly reproducible with minor diffs, Often environment-specific differences, Not reproducible
• Describe any current automation for environment provisioning (containers, VM images, Ansible/Chef, custom tooling).

Imagine waking up the day before an audit: what three things would you need to see to feel calm?

• Which single artifact gives you the least peace of mind today (coverage report, traceability matrix, CM log, test logs, other)? Options: Coverage report, Traceability matrix, Configuration management log, Raw test logs/waveforms, DER sign-off, Other
• How often would you want consultant or DER checkpoints during deployment to feel supported (weekly, milestone-based, on-demand)? Options: Weekly, Milestone gates only, On-demand as issues arise, Kickoff + final only
• What would a minimum 'audit-ready' checklist look like for your program? Please list the top 5 items.
• If we proposed an initial remediation plan to close the top three blockers you just identified, how open is your team to a short paid pilot to prove the approach? Options: Very open, Somewhat open, Unsure, Not open
• Who needs to be involved from your side to approve a deployment plan and consultant/DER access (roles, not names)?

Let’s make the first practical step obvious — what can we commit to together in the next 7–14 days that will unblock verification runs?

• Which of the following immediate actions would help most (pick up to two)? Options: Environment audit & baseline, Small automation pilot, CM policy review & fixes, Coverage gap triage session, DER access enablement
• If we ran a 1-week readiness sprint with your engineers and one of our consultants, which objectives would you prioritize (rank top 3)? Options: Reproducible environment build, Automated regression demo, Traceability baseline, Coverage report generation, DER evidence package
• What constraints (budget, security, calendar, licensing) could prevent starting a short pilot within the next month? Options: Budget, Security approvals, Key personnel availability, Licensing, None
• Who should receive a one-page readiness brief from us after this discovery, and what single decision would make it easiest for you to say 'go'?

Who Are We Talking To? (Easy start)

• Which role best describes you on this program? Options: Hardware Design Lead, Verification Lead, Certification Manager, Program Manager, Systems Engineer, DER / Consultant, Other
• Which hardware type is this program primarily focused on? Options: FPGA, ASIC/ASIC-like PLD, SoC with FPGA fabric, COTS module integration, Other
• What Design Assurance Level (DAL) has been assigned or targeted? Options: DAL A, DAL B, DAL C, DAL D, Unknown / Not assigned
• Which phase best describes where you are today? Options: Requirements definition, RTL design, Functional verification, Certification preparation/audit, Production / sustaining
• What is the single most important outcome you want this engagement to deliver?

If the Auditor Showed Up Tomorrow, What Would Happen?

• If a certification authority requested audit-ready DO-254 evidence today, would you feel comfortable handing it over? Options: Yes—fully ready, Partially ready (some gaps), No—significant work needed, Unsure
• When was your last internal or external audit, and what were the top two findings?
• Which of the following artifacts do you currently produce automatically? Options: Structural coverage reports, Requirements traceability matrix, Test execution logs, Change history/CM records, Configuration baselines, None
• Who on your team ultimately owns artifact acceptance for certification? Options: Program Certification Manager, DER, Hardware Design Lead, Verification Lead, Configuration Manager, Other
• How often do certification acceptance criteria change during your program? Options: Frequently, Occasionally, Rarely, Never

Which Coverage Gaps Keep You Awake?

• Which coverage gap would be most likely to jeopardize your certification if it remained open? Options: Requirements-to-test gaps, Uncovered RTL branches, Clock-domain crossing issues, Safety-critical state coverage, Configuration/CM inconsistencies, Other
• How do you currently identify coverage gaps (tools, metrics, manual review)? Options: Coverage tool (VCD/UCDB), Custom scripts, Manual review / inspections, Requirements traceability checks, We don't have a consistent method
• On average, from detection to closure, how long does a critical coverage gap take to resolve? Options: <1 week, 1–2 weeks, 2–4 weeks, 1–2 months, >2 months
• Tell us about the most recent gap that forced a re-test or schedule slip—what happened and why?

Is Your Test Strategy Closing Risk—or Growing Tests?

• Does your current verification approach produce lots of tests without closing the root risk? Options: Yes—test count grows, risk remains, No—tests are targeted and close risk, Mixed results, Unsure
• Which verification methodologies are in use for this design? Options: Directed tests, Constrained-random (UVM), Formal verification / static analysis, Hardware co-simulation / emulation, White-box structural testing, Other
• Which simulator and verification flow do you run in CI/REGRESSION? Options: Mentor Questa/ModelSim, Synopsys VCS, Cadence Xcelium, Vendor-supplied simulator, Open-source / Custom, We don't have a standard
• How automated is your regression execution and report generation? Options: Fully automated with nightly runs, Partially automated, Manual runs only, No regression practice
• What would reduce test-suite bloat for your team—better coverage tools, smarter test generation, formal methods, or something else?

If Traceability Is the Spine, How Healthy Is Yours?

• If you had to prove requirement-to-RTL-to-test linkage today, how complete would that trace be? Options: Complete and verifiable, Mostly complete with some links missing, Sparse or fragmented, No formal tracing
• Where are your source requirements stored? Options: DOORS / DOORS Next, JAMA / Polarion, Jira, Word/Excel, In-code comments, Other
• How do you manage traceability updates when requirements change? Options: Automated re-trace via tools, Manual update by engineers, Controlled through CM but often delayed, No formal process
• Which artifact templates do you currently use for DO-254 evidence? Options: Pre-built DO-254 templates, Custom internal templates, Tool-generated templates, Ad-hoc documents, None
• Who is accountable for maintaining the traceability matrix day-to-day? Options: Requirements engineer, Verification lead, Configuration manager, Program certification manager, No single owner

Would a DER Accept What You Produce Today?

• If you handed current artifacts to a DER, would they require significant rework? Options: Yes—major rework, Some rework, Little to no rework, We haven't engaged a DER
• Have you involved a DER or certification authority early in the verification planning? Options: Yes—engaged early, Engaged late, Not yet engaged, Unsure how to engage
• What DER feedback have you received about tool-generated evidence in previous programs?
• Which artifacts have historically been the most contested in audits? Options: Coverage metrics, Traceability matrices, Test procedures/logs, Configuration records, Tool reports / logs, Other

Hidden Schedule Risks: What Nobody Tells You

• Which schedule blind spot could realistically derail certification in the next 90 days? Options: Lab access delays, Late requirement changes, Staff turnover / LACK of expertise, Tool integration delays, Unexpected DER requests, Other
• Do you have dedicated test benches and environment access for verification runs? Options: Yes—fully provisioned, Partially available, No—shared or limited, No dedicated environments
• Is your configuration management process able to produce a reproducible baseline for a given test run? Options: Yes—automated baselines, Partially—some manual steps, No—hard to reproduce
• Do licensing, network, or export-control restrictions limit what tools or cloud services you can use? Options: Yes—significant constraints, Some constraints, No constraints, Unsure
• Who on your team is responsible for ensuring environment and CM readiness? Options: Configuration Manager, Verification Lead, DevOps / Build Engineer, Program Manager, Other

What Trade-offs Are You Actually Willing to Make?

• If you had to choose, which would you prioritize: speed to certification, minimal manual evidence work, or smallest possible budget? Options: Speed to certification, Minimal manual evidence effort, Lowest cost, Balance of the three
• Would you be open to swapping some legacy tools for an integrated toolchain that generates regulator-oriented artifacts? Options: Yes—open to replace, Only hybrid approach, No—must keep existing tools, Unsure
• How important is an on-site consultant or DER presence versus remote collaboration? Options: Prefer on-site, Prefer remote, Hybrid, Depends on phase
• Are you willing to commit engineers to a short pilot to validate evidence acceptability with your DER? Options: Yes—can commit resources, Maybe—depends on timeline, No—resources constrained

What Early Wins Would Calm Leadership?

• What single measurable KPI would make leadership feel the program is back on track within 60 days? Options: Coverage % (e.g., 90%+), Number of critical gaps closed, First audit-ready artifact delivered, Regression stability / pass rate, Other
• Which artifacts would you accept as a prioritized deliverable in the first month? Options: Traceability matrix for a feature, Coverage report for a module, Test procedure + logs for critical function, CM baseline and build recipe, Other
• Who must sign off on these early wins inside your organization? Options: Program Manager, Certification Manager, DER, Design Lead, Verification Lead, Other
• What are the top three blockers that must be removed to achieve those early wins?

Partnering Practicalities: How Would This Work?

• If we were to partner, what would feel like success at the three-month mark?
• Which engagement model do you prefer for a first step? Options: Pilot with tool + consulting, Consulting assessment only, Tool trial only, On-site DER workshop, Proof-of-concept using your design
• What constraints govern data sharing or uploading design artifacts to external systems? Options: Export control / ITAR, Company policy prohibits external uploads, Allowed under NDA, No constraints
• Which sample artifacts could you realistically share for a pilot (select all that apply)? Options: A small RTL module + tests, Requirements subset, Previous coverage reports, Configuration baseline, None available
• What legal, procurement, or budget steps must occur before we can start a pilot?

Final Reflection: How Is This Program Really Feeling?

• When you think about the certification timeline, what emotion comes up first? Options: Confident, Anxious, Frustrated, Indifferent, Hopeful
• What keeps you personally motivated to push this program across the finish line?
• What would make you say, after a collaboration, 'That was the right decision'?
• What is the most helpful next step from our side—demo, proposal, pilot scope, or an on-site workshop? Options: Schedule a demo, Receive a detailed proposal, Define a pilot scope, On-site scoping workshop