The question at hand
Your board wants answers. When will quantum computers break your encryption? When should you start investing in post-quantum cryptography? And how much will it cost?
You can't pinpoint the exact date. The U.S. National Institute of Standards and Technology plans to phase out vulnerable cryptographic algorithms by 2035. Google has set a 2029 target for its own quantum migration. But predicting Q-Day itself is impossible.
So here's the real question: Do you invest in post-quantum readiness now, based on uncertain timelines, or wait for clearer evidence that quantum computers pose an imminent threat?
The case for starting now
The "start immediately" camp offers three compelling reasons.
First, lead time is crucial. Even if you knew quantum computers would break current encryption by 2033, you'd still need to start now. Discovery alone takes 12 to 18 months. You need to inventory vulnerable cryptography, identify critical services, map third-party dependencies, and assess which systems can't be patched. Then you build and execute the plan, which can take five to 15 years depending on complexity.
Second, "harvest now, decrypt later" attacks create present-day risks. Adversaries don't need working quantum computers today. They just need to collect encrypted data that will remain valuable when those computers arrive. Healthcare research data, biometric records, financial archives, and intellectual property all hold value for decades. If you're protecting long-lived sensitive data, you're already exposed.
Third, the cost of waiting compounds. Organizations that react late will pay more. They'll face compressed timelines, vendor capacity constraints, and premium pricing for urgent work. They'll also miss the learning curve. Teams that start early build internal capability, establish vendor relationships, and develop the skills needed to execute cryptographic changes at scale.
A staged-investment approach makes this practical. You don't ask the board to approve an undefined enterprise-wide migration. You ask for funding to understand your exposure and produce a defensible plan. Spend 18 months assessing critical services, vulnerable cryptography, and third-party readiness. Then return with a scoped program sized to your actual risk and capacity.
Pair that request with a quick win. Many organizations start with hybrid post-quantum configurations on external endpoints, which requires only configuration changes and lets you test compatibility with legacy clients. It builds trust while you address the deeper problem.
The case for waiting
The "wait for clarity" camp has valid points.
First, quantum computing timelines are speculative. Research breakthroughs happen, but so do setbacks. Funding decisions based on uncertain threats can misallocate resources that could address known risks today. Your board might reasonably ask why you're prioritizing a theoretical future threat over active vulnerabilities in your current environment.
Second, early adoption carries risks. Post-quantum algorithms are new. NIST finalized its standards recently, but implementation experience is limited. Organizations that migrate early could face compatibility issues, performance degradation, or the need to re-migrate if standards evolve. Waiting lets others find the problems first.
Third, vendor readiness varies widely. If your critical systems depend on third-party software that hasn't implemented post-quantum support, your migration timeline is constrained regardless of when you start. You might be better off waiting until your vendor ecosystem matures rather than funding internal work you can't fully execute.
The cost argument cuts both ways. Yes, waiting raises the price if you're caught unprepared. But premature spending on immature technology also wastes money. Some organizations will pay twice: once for early adoption that doesn't work, and again for the real migration when standards stabilize.
Where practitioners actually land
Most organizations aren't choosing between "start now" and "wait indefinitely." They're calibrating their response to risk exposure and implementation capacity.
Organizations protecting long-lived sensitive data, particularly in healthcare, finance, and government, tend to start discovery immediately. The "harvest now, decrypt later" threat is real for them, and they can't afford to wait for Q-Day confirmation.
Organizations with shorter data lifecycles or less sensitive information often take a measured approach. They monitor vendor roadmaps, track NIST guidance, and prepare budget forecasts, but they don't launch full migration programs until timelines firm up.
The staged approach works because it decouples discovery from commitment. Funding an 18-month assessment doesn't lock you into a decade-long migration. It gives you the information needed to make that decision intelligently. You learn which services are vulnerable, which vendors are ready, and what the full program will actually cost.
Metrics matter here. Track the percentage of critical services assessed, unsupported systems identified, and vendors evaluated. Tie goals to specific outcomes like certificate-management coverage by a target date. This gives your board visibility into progress without requiring them to understand quantum entanglement.
Our take
Start the discovery work now, but be honest about what you're asking for and why.
The uncertainty around Q-Day is real, but it's not a reason to delay understanding your exposure. You need 12 to 18 months just to map vulnerable cryptography, assess critical services, and produce a credible migration plan. That work pays off even if quantum computers arrive later than expected. You'll have better visibility into your cryptographic infrastructure, cleaner certificate management, and documented third-party dependencies.
The "no-regrets" framing is correct. None of this investment is wasted. But don't oversell the urgency. If your board asks whether you should start this year or next year, the honest answer for most organizations is that starting next year is still defensible, as long as you actually start.
What's not defensible is waiting until you have certainty about Q-Day. By the time quantum computers demonstrably break current encryption, you'll be five years behind organizations that started discovery in 2025 or 2026. You'll pay more, move slower, and face vendor capacity constraints that don't exist today.
The real risk isn't choosing wrong between "now" and "wait." It's confusing a decision to fund discovery with a decision to fund full migration. Fund the assessment. Build the plan. Then make the bigger call with actual data about your exposure, your vendors' readiness, and what the program will cost.
