Technology decisions too often begin with the product. Which platform should we buy? Where should we add AI? Should we replace the current system or build something new?
Those questions come too early.
A better technology decision process starts by imagining the ideal business outcome, determining what is preventing that outcome, and only then asking what intervention is justified. For commercial real estate leaders, that means working through three questions in sequence.
What outcome are we trying to create?
Step 02What is preventing us from achieving it?
Step 03What intervention is economically justified?
What outcome are we trying to create?
Not every technology investment produces the same kind of value. Some improve efficiency by reducing cost, time, or manual effort. Others improve effectiveness by producing better decisions, execution, controls, or customer outcomes. A smaller number create alpha, a differentiated capability competitors cannot readily obtain by purchasing the same technology.
Defining the intended return first changes the investment discussion. It connects the technology decision to the economic result leadership actually wants.
What is preventing us from achieving it?
The next question is whether the current technology environment can reasonably support the desired outcome.
The constraint may be economic: workarounds, reconciliation, consulting, integration, and manual labor are becoming too expensive. It may be operational: information stops at system boundaries, employees create shadow processes, and execution suffers. Or it may be strategic: the standard platform cannot apply proprietary data, institutional knowledge, or company-specific decision logic in ways that matter competitively.
The issue is not whether the existing software is imperfect. Every system is imperfect. The question is whether the operating cost of accommodating the software, together with the potential loss of alpha, now exceeds the benefits of maintaining the status quo.
What intervention is economically justified?
Only after defining the return and diagnosing the constraint should leadership decide what technology to change.
Buy common capabilities when parity is sufficient and the market already provides an economical solution. Configure and integrate when existing platforms are fundamentally sound but need to fit the organization’s workflows, data, and operating requirements. Build selectively when proprietary knowledge, workflow, data, or decision-making can create enough economic advantage to justify ownership and maintenance.
Custom software is not inherently better. Off-the-shelf software is not inherently safer or cheaper. The right answer depends on the economics and which capabilities the business is trying to leverage.
Define the return. Diagnose the constraint. Choose the intervention.
Those three questions provide a more disciplined way to make technology decisions before product selection begins.