Enterprises depend on technology systems that expand continuously and often evolve without consistent measurement of their structure or performance. Architectural decisions made during this growth are seldomly evaluated against long term efficiency or cost. Over time, these decisions create dependencies and redundancies that slow delivery and increase operational expense. Lack of measurement makes it more difficult for leadership to see the true impact of architectural choices on financial performance.
These factors inspired me to develop the Waypoint Methodology, a new Enterprise Architecture Methodology to quantify hidden debt within designs. Waypoint converts architecture from an abstract design function into a measurable operational framework. The purpose is to apply the same statistical and financial discipline to architecture that already exists in other business areas. Research supports, architecture practices must be measured continuously to control financial impacts.
Sutoyo et al. (2025) demonstrated that even the process of repaying debt has measurable structural consequences.
“We observed that ATD repayment increased class connectivity, with FAN-IN increasing by 57.5% on average and FAN-OUT by 26.7%, suggesting a shift toward centralization and increased architectural complexity after repayment. Moreover, ATD files were modified less frequently than Non-ATD files”
This analysis demonstrates architectural change alters measurable dependency structures. This supports the Waypoint concept that architecture must be observed with data rather than managed by opinion.
Daoudi et al. (2023) extended this thinking to the enterprise level. They defined enterprise architecture debts as quantifiable gaps between the current and optimal state.
“EA Debts represent blockers while moving from the current EA (as-is) towards a desired to-be-landscape. Typical consequences are complex application landscapes with legacy systems and redundancies, outdated or incomplete EA artifacts and documentation, procedures and organizational units in EA management that hamper IT innovations”.
This reinforces the need for continuous measurement and validation. Continuous measurement and validation are essential to Waypoint’s Gauge and Target phases which identify and quantify structural inefficiency before it compounds into financial loss.
Idris and Omar (2020) approached the problem through quantitative risk modeling. They proposed measuring the likelihood and severity of architecture smells to assess risk.
“Through tracking the architecture smells, we estimate their likelihood and impact (severity) on the components’ internal structures. By estimating the likelihood and severity of the ASs, we will assess software components’ ATD risk level”.
The researchers continued their analysis emphasizing measurable risk data improves decision-making and prioritization. Specifically they observed:
“Using risk assessment, we can identify troublesome components and prioritize them by making the technical debt picture clear to decision-makers to help them make better refactoring decisions”.
Idris and Omar’s research supports the Waypoint principle that risk, once quantified, becomes a financial variable that can be managed directly.
Sklavenitis and Kalles (2024) applied this measurement logic to artificial intelligence platforms. They created a structured questionnaire that assigns scores to technical practices, producing a cumulative technical debt index.
“A YES response, which signifies adherence to practices known to mitigate technical debt, results in a negative score, thereby indicating a reduction in technical debt. Conversely, a NO response suggests a deviation from these practices, and is consequently assigned a positive score, indicating an increase in technical debt. Responses marked as “Not Applicable” receive a score of 0, reflecting their neutrality in terms of impacting the technical debt calculation. Similarly, responses of “I Don’t know/I Don’t answer” are treated the same as NO responses, as they both imply the presence or potential accumulation of technical debt. The rationale for this scoring method is founded on the assumption that affirmative answers demonstrate compliance with best practices that lower technical debt, whereas negative or uncertain responses indicate areas where technical debt could either be present or likely to accumulate. The cumulative score derived from all responses thus provides a quantitative measure of the total technical debt associated with the entity being evaluated.”
This approach demonstrates that architecture, even within adaptive and evolving systems, can be expressed in measurable form. It supports the Waypoint objective of transforming architecture from an interpretive practice into a data-driven discipline.
Together these studies provide practical support for the viability of creating measurable architectures. Each shows that complexity, risk, and waste can be expressed as quantifiable data. The evidence confirms architecture can be evaluated through continuous measurement rather than static review.
The Waypoint Methodology builds on this foundation through its five phases:
Scout, Gauge, Target, Maneuver, and Watch. These 5 phases form a closed loop of measurement and improvement. They establish a process for converting architectural behavior into financial outcomes that can be validated with data. Waypoint replaces assumption with proof and transforms architecture into a repeatable system of control, precision, and measurable value.
Architectural debt is costing your enterprise money every day it remains hidden. Every delay in quantifying it allows inefficiency to grow, waste to multiply, and decision-making to remain based on assumption. The time to act is now. Measure your architecture before it measures you.
Contact me now to apply the Waypoint Methodology to expose the real numbers behind your technology and build an architecture function that pays for itself.
Together we will establish your baseline, calculate your “Cost of Poor Quality” (COPQ), and identify the top systems driving loss. The organizations that move first will not just survive modernization; they will master it.
The data is waiting.
The method exists.
The next move is yours.