I approach strategic planning as a process of making explicit choices about where the company will focus, what it will deliberately not pursue, and which capabilities it must strengthen to execute successfully.

A good strategic plan should not require executives to approve every operational choice. It should give people a clear framework for deciding what deserves attention, what can wait, and what does not belong in the current strategy.

Ultimately, strategic planning is not primarily about accurately forecasting the future. It is about preparing the organization to allocate resources intelligently while remaining capable of responding when reality differs from the original plan.

We begin with the external context: customer needs, market changes, competitive pressure, technology shifts, and regulatory or economic factors that could affect demand.

We then compare those factors with our internal position—our products, delivery capacity, commercial pipeline, financial resources, and organizational strengths.

From there, we identify a limited number of strategic priorities.

I believe a plan becomes less useful when everything is classified as important. Each priority, therefore, needs a clear business outcome, an accountable owner, measurable milestones, and an understanding of the required resources and dependencies.

In a technology company, strategic planning must connect commercial ambition with delivery reality.

A new market or product opportunity may appear attractive, but we also need to ask whether we have the technical capacity, domain knowledge, implementation resources, and sales capability to pursue it without weakening existing commitments.

I also treat the strategy as a set of assumptions that must be reviewed, not as a document that becomes fixed for a year. We establish regular checkpoints to assess whether customer behavior, costs, delivery performance, or market conditions support those assumptions.

My objective is to create enough direction for teams to make aligned decisions independently.

The first question is whether the investment supports one of the company’s core strategic priorities. An initiative may deliver an attractive return on its own, but if it diverts critical people or capital from a more important objective, it may still be the wrong investment.

Second, I evaluate the expected value. This may include revenue growth, margin improvement, customer retention, operational efficiency, risk reduction, or building a capability that creates future opportunities. Not every investment delivers an immediate financial return, but its value hypothesis should always be specific and testable.

Third, I assess execution risk by considering technical complexity, implementation time, internal capacity, dependencies, customer adoption, and how reversible the decision is. When two opportunities appear equally valuable, I usually favor the one that can be tested through a smaller, staged commitment rather than a large, irreversible investment.

Opportunity cost is equally important. In a growing company, the constraint is often not capital one. It may be senior leadership attention, experienced engineers, sales capacity, or the organization’s ability to absorb change. Every approved initiative consumes part of that capacity.

One practice I find particularly valuable is requiring every major proposal to identify what will be delayed, reduced, or stopped if it is approved. This keeps investment discussions grounded in realistic organizational capacity rather than a collection of individually attractive projects.

I also distinguish mandatory investments from discretionary ones. Security, compliance, contractual obligations, and critical infrastructure often require funding even when their primary return is risk reduction.

The decision is therefore not simply, "Which project has the highest projected return?" It is, "Which combination of investments creates the strongest strategic position without exceeding our financial or operational capacity?"

I balance short-term performance with long-term objectives by treating them as connected responsibilities rather than competing philosophies.

A company needs near-term revenue, cash discipline, customer delivery, and operational stability. Without those foundations, it will not have the resources or credibility to pursue long-term opportunities.

At the same time, optimizing only for the current quarter can lead to underinvestment in products, people, systems, and market capabilities that determine future competitiveness.

I therefore separate commitments into three categories. The first protects the current business: customer delivery, cash flow, service quality, and essential operating performance. The second improves the business: process automation, capability development, product refinement, and commercial efficiency. The third creates future options: new products, markets, technologies, or partnerships.

The allocation between these categories changes according to business conditions, but none should disappear entirely. During a difficult period, future-oriented investments may become smaller or more selective, yet eliminating them completely can create a larger strategic problem later.

I also try to distinguish productive long-term investment from activity that is merely labeled strategic. Every long-term initiative should have intermediate evidence to determine whether the original thesis remains credible. For example, before fully scaling a new solution, we may look for customer interest, pilot adoption, implementation feasibility, or a repeatable sales case.

When business conditions change, I first determine whether we are seeing temporary volatility or evidence that a core planning assumption is no longer valid.

Reacting to every short-term movement creates instability, confuses teams, and weakens execution. At the same time, sticking to the original plan after the market, customer behavior, costs, or competitive conditions have materially changed can be just as damaging.

We therefore review the assumptions behind the plan, not just actual results against budget. These assumptions may include customer demand, pricing, sales-cycle length, implementation capacity, hiring, supplier costs, or financing. When a key assumption changes, we assess the operational and financial impact.

I prefer scenario planning over relying on a single revised forecast. We typically develop a base case, downside case, and opportunity case, each with predefined actions. This allows management to respond quickly because spending, hiring, investment, and commercial decisions have already been discussed.

Prioritization is equally important. We protect activities that support customers, cash flow, security, and core strategic capabilities, while lower-priority initiatives may be delayed, scaled back, or tested with smaller commitments. Broad, across-the-board cost-cutting often weakens strong areas without solving the underlying problem.

Communication is essential. Teams need to understand not only what changed, but why, which assumptions shifted, and what the revised priorities mean for their decisions.

Adaptability does not mean abandoning discipline. It means allowing evidence to challenge assumptions and reallocating resources without losing strategic focus. The objective is not to preserve the original plan, but the company's ability to achieve its most important outcomes under changing conditions.

Corporate Finance and Strategy

Report

Report

Report