Technology Portfolio Management (TPM) Best Practices

Overview

Building an enterprise-specific Technology Radar is not a one-time publication exercise. It is a semi-annual governance discipline that requires the architecture governance function to systematically review the organization’s position on a defined set of technologies, make explicit decisions about positions that should change, build organizational consensus around those decisions, and communicate them in a format that is accessible to the full engineering community. The process of building the Radar is as valuable as the Radar itself, because it forces the explicit deliberation about technology positions that governance without a radar process tends to defer.

Best Practice

Establish a semi-annual Enterprise Technology Radar update cycle with a defined governance process. The cycle should include: a technology position review phase in which the architecture governance function reviews all technologies currently on the Radar, assesses any significant developments since the last update, and identifies position changes that should be made; a deliberation phase in which proposed position changes are reviewed by the Architecture Review Board or Technology Review Board and formally approved or rejected; a community input phase in which engineering teams are invited to propose technologies for addition to the Radar or to provide evidence for position changes; and a publication and communication phase in which the updated Radar is distributed to all teams and the rationale for significant changes is communicated.

The enterprise Radar quadrants should reflect the IF4IT Technology Categorization Taxonomy rather than adopting the Thoughtworks quadrant structure directly, unless the Thoughtworks structure happens to align well with the organization’s taxonomy. The enterprise Radar rings should map to the organization’s Standards Register statuses and lifecycle stages, providing a visual representation of the same information the Standards Register captures in structured data form.

Benefit(s)

A semi-annual Enterprise Technology Radar update cycle provides the recurring forcing function that ensures technology positions are reviewed and updated regularly rather than drifting from organizational reality between infrequent comprehensive reviews. The community input phase creates a feedback loop between the engineering teams making day-to-day technology decisions and the governance function setting technology standards, producing standards that are informed by operational experience rather than set in isolation from the people who must follow them. And the published Radar creates organizational transparency about technology positions that builds governance credibility and reduces the shadow technology adoption that occurs when teams cannot find or trust the official organizational position on the technologies they are considering.