This is a thoughtful post that exposes a real tension in how we build tools for growth. The author has created a Development Tracker that clearly works, it houses master controls, individual tabs, quantitative formulas, and conditional visibility based on job title and promotion status. That's real work, and it solves a genuine problem for managers who need to document skill progression. But the question about year-over-year reuse reveals the limits of traditional spreadsheet design. Manual copies, VBA macros, endless tabs, or screenshots are workarounds, not answers. Each one adds friction, and friction is the enemy of adoption.
The core issue here is that the spreadsheet was built to track a static moment in time, but professional development is inherently dynamic. Skills from 2025 don't disappear in 2026; they form the foundation for what comes next. The author intuitively understands this, which is why they don't want managers to delete old inputs or force them to add rows that break formulas. But the current structure treats each year as a separate container, not a continuous thread. The VBA macro is the most elegant of the options listed, but it still asks the user to remember a manual trigger and manage file versions. That extra step, however small, will be skipped by busy managers who just need the tracker to work.
What this situation really asks for is a tool that understands time as a dimension, not a reset button. An AI-native spreadsheet could allow each skill entry to carry a date stamp, so the same row grows with the employee. Formulas could reference the most recent year by default, while preserving every prior entry in the same cell, no new tabs, no duplicate files, no broken calculations. The tracker already shows thoughtful design; the missing piece is a system that treats historical data as an asset, not an inconvenience. The next evolution of this tracker isn't a better macro, it's a smarter foundation that makes year-over-year maintenance invisible to the user.