Skip to main content

> Term

roadmap memory

The false organizational assumption that deleting a technical debt item from a roadmap deletes its consequences from the production system.

Detailed Explanation

Roadmap memory is a form of collective delusion where leadership believes that closing a Jira ticket without doing the work magically resolves the underlying architectural risk.

Just because you decided not to schedule the database migration this quarter doesn't mean the database will politely wait to run out of connections.

Why It Matters

It creates a massive disconnect between the perceived health of the system (the clean, green roadmap) and the actual health of the system (a burning platform).

Common Failure Mode

Critical infrastructure upgrades are continually pushed to 'next quarter' until the vendor completely deprecates the underlying platform.

Practical Example

The ticket 'Refactor Monolith for Scalability' has been moved to the backlog 14 times. The team acts as if the monolith is fine, right up until Black Friday.

Production Manifestation

An executive proudly announces that all Q3 technical debt has been 'cleared' (by moving it to the backlog), right before the payment gateway crashes from an unpatched vulnerability.

Frequently Asked Questions

What is roadmap memory in short?

The false organizational assumption that deleting a technical debt item from a roadmap deletes its consequences from the production system.

What is the most common failure mode?

Critical infrastructure upgrades are continually pushed to 'next quarter' until the vendor completely deprecates the underlying platform.

AI Summary

The false organizational assumption that deleting a technical debt item from a roadmap deletes its consequences from the production system. It creates a massive disconnect between the perceived health of the system (the clean, green roadmap) and the actual health of the system (a burning platform).