The September Surge: Why the Failure to Plan Now is a Corporate Death Wish

Reading Time: 6 minutes

In the high-stakes theater of modern business, a silent killer lurks in the shadows of the boardroom. It doesn’t wear the face of a competitor or a market crash. Instead, it wears the mask of “Agility”—the seductive, yet often fatal, excuse for a “Fix-it-Now” Culture.

As we navigate 2026, the data is staggering. Organizations collectively waste millions every hour due to poor project management. Professionals with high business acumen—those who plan ahead—experience 27% fewer project failures than their reactive counterparts.

In my years as a professional Project Manager, I have seen the same tragedy play out in a loop: companies that prioritize immediate quarterly profits over long-term business stability. They treat planning as a luxury for “quiet times,” ignoring the fundamental law of preparation. But stability is not an accident. It is the architectural result of decisions made months, and sometimes years, in advance.

If you aren’t talking about next year by the first week of September, you aren’t leading; you are merely reacting to a disaster that has already begun.

1. The Fallacy of the Immediate

The “Immediate” is the enemy of the “Excellent.” Most organizations operate in a state of perpetual reaction. When a system breaks, they patch it. When a customer complains, they apologize. When a project falls behind, they throw more bodies at the problem. This “moment-to-moment” management style is often mislabeled as “pivoting,” but the reality is far bleaker: it is a lack of foresight that erodes the very foundation of the company.

The statistics back this up. Only 38% of organizations mostly or always complete projects on time. Why? Because the focus remains on the “Now.” When profit is the only metric, business stability becomes a secondary concern. However, profit is a lagging indicator—it tells you how well you did. Stability is a leading indicator—it tells you how well you will do.

To achieve stability, you must master the Fundamental Law of Planning with Time. This isn’t just a task for the Project Manager; it is a requirement for the entire ecosystem. It ensures that the resources needed for the project are actually available, that the main users are prepared for the change, and most importantly, that you avoid the reputational suicide of failing your customers.

When you ignore the future, you aren’t just procrastinating; you are actively sabotaging your own resources. Companies that dynamically reallocate resources nimbly in the face of shifting opportunities materially improve their odds of economic profit, yet many stay stuck in rigid, reactive cycles.

2. The Architect’s Questions: A Checklist for Survival

To move from reactive to proactive, executives must stop asking “How do we fix this?” and start asking the hard questions about capacity and architecture. I’ve found that a project’s success is determined long before the first line of code is written. If you cannot answer these questions by the time the September air hits, your project is already in trouble:

Capacity and Manpower: Do we have the actual bandwidth, or are we hoping our best people can work 80-hour weeks? Research shows that over-allocation is the #1 cause of burnout.
The Parallelism Trap: Is this project running in parallel with three others that require the same key personnel?
Vendor Integrity: Are we onboarding a new vendor? Do we trust them? Have we audited their security protocols, or are we just picking the lowest bidder?
The Learning Curve: Do we need training? (Hint: You always do).
Operational Security: How often do security check-ups occur? In 2026, where cyber threats are AI-driven, a “check-up” from six months ago is a lifetime ago.
Access Control: How often is system access reviewed? Who will be the ultimate Product Owner?
The Regulatory Cost: What happens if we miss the deadline? Is there a legal consequence? 37% of projects fail because of inaccurate requirements gathering.

These questions aren’t just boxes to tick. They are the structural pillars of your enterprise architecture. Whether you are improving a system or centralizing software to align with a business strategy, the architecture must be there to support the request.

3. The September Threshold

Why September? In professional project management, September is the “Golden Window.” It is the bridge between the current year’s execution and the next year’s vision.

There are companies that take three to four months just to approve a resource request or a software purchase. If you start your next-year planning in November, you won’t have your resources until March. You’ve already lost the first quarter. By starting in September, you ensure that the requirements are set, the Enterprise Architecture team has vetted the request, and the budget is locked before the holiday season creates a vacuum of productivity.

Organizations with high business acumen achieve higher adherence to budgets (73% vs. 68%) and schedules compared to those who lack a strategic, planned approach.

Planning is not just about “what” we are doing; it’s about “how” we are prepared. Sometimes a software request comes in because the current system “doesn’t work,” but the architecture reveals that the software is fine—the business strategy has simply shifted toward centralized systems, and the current tool is an isolated silo. Without planning, you buy a new tool. With planning, you fix the strategy.

4. The Graveyard of Poor Planning: 5 Public Scandals

To understand the gravity of future planning, look at the wreckage of companies that thought they could skip the “boring” parts of project oversight. These are not just mistakes; they are cautionary tales of what happens when profit-focus overrides stability-planning.

Company	Financial Impact	The Planning Failure
Knight Capital	$440M in 45 mins	Failed to decommission “dead code” before a new launch.
TSB Bank	£330M loss	Attempted migration without full data-center testing.
Target	$202M total cost	No plan for network segmentation of third-party vendors.
Boeing	Billions in losses	Prioritized speed over pilot training and safety planning.
Lidl	€500M write-off	Tried to force modern software to fit legacy processes.

1. The Knight Capital Bankruptcy (2012)

Knight Capital lost $10 million per minute because of a botched software installation. They reused a “flag” in their code without removing the legacy functionality it was once attached to. When they went live, the old code triggered millions of unintended trades. The Lesson: If you don’t plan for the retirement of old systems, they will eventually sabotage the new ones.

2. The TSB Bank IT Migration (2018)

TSB’s board failed to ask “common sense” questions about testing. They migrated 1.9 million customers to a new platform that had only been tested on one of two data centers. The result? Total lockout and massive regulatory fines. The Lesson: Testing is not a checkbox; it is a survival requirement.

3. The Boeing 737 Max Crisis (2018-2019)

Boeing’s rush to compete with Airbus led to the MCAS software failure. To save on pilot training costs, they downplayed the system’s impact. The lack of a plan for “User Preparation” resulted in 346 lives lost. The Lesson: When profit conflicts with safety and training, catastrophe is inevitable.

4. The Target Data Breach (2013)

Hackers entered Target’s network through an HVAC vendor. Target had no architectural plan to segment vendor access from their payment systems. The Lesson: Your planning must extend to your vendors. Their security is your security.

5. Lidl’s SAP Disaster (2018)

Lidl spent seven years trying to customize SAP to fit their old inventory methods. They eventually scrapped the €500M project and reverted to their old system. The Lesson: If you are not willing to plan for business process change, technology cannot save you.

5. The Executive’s September Playbook

If you want to avoid being the sixth name on that list, you must implement these techniques the moment the calendar hits September:

Training as a Non-Negotiable: Allocate 15% of every project budget to training and user preparation.
The 1.5x Capacity Rule: Assume every project will take 50% more time and manpower than predicted. If your “Resources Needed” list exceeds your actual headcount, cut a project.
The Architecture Veto: Give your Enterprise Architects the power to veto any project that doesn’t align with the move toward centralized, stable systems.
The “September Sync”: Every September, hold a “Vendor Audit.” Look at their security check-up frequency and their own business stability.
The Regulation Roadmap: Identify every compliance change hitting in the next 18 months. Planning for a regulation after it’s passed is too late.

Conclusion: The Cosmic Law of Preparation

ThIn the end, Project Management is not about checking boxes on a Gantt chart. It is an act of Enterprise Architecture—building a structure that can withstand the pressures of the future. The “Fix-it-Now” culture is a house of cards. It looks profitable until the first wind of a vendor breach or a software failure blows it down.

The “Cosmic Architect” doesn’t build for today; they build with the understanding that time is the most valuable resource. By starting your planning in September, by asking the hard questions about manpower and capacity, and by prioritizing stability over the quick win, you aren’t just managing projects. You are ensuring the survival of your legacy.

The data is clear: the cost of planning is high, but the cost of not planning is everything.

Are you ready to build for 2027, or are you still putting out yesterday’s fires?

Contents hide

1 References:

1.1 Share this:

1.2 Like this: