Rebuilding a Site Map Took Weeks to Design, Nearly a Year to Ship

The first concrete number in a newly published information architecture case study is a timeline: the initial redesign work took a few weeks, but prioritizing and implementing that work consumed almost a year. Author Alex Hrisov published the account on Medium under the title "Rebuilding the map: an information architecture case study." The gap between those two figures — weeks of design against roughly twelve months of implementation — is the story's central data point, and it quantifies a reality most UX teams know anecdotally: the map is redrawn faster than the territory can be rebuilt.

The study frames its subject as the map, the structural layer that determines where content lives and how users reach it. Information architecture work of this kind typically involves inventorying existing content, testing category schemes with users, and validating navigation paths before any interface is touched. Hrisov's timeline suggests the analytical phase compressed into weeks, while the organizational cost of acting on the findings stretched across the better part of a year.

That ratio deserves translation for practitioners. If discovery and structural design occupy a few weeks, and implementation prioritization occupies a year, then roughly 90 percent of the project's calendar went to sequencing and rollout rather than to the architecture itself. A team planning a similar restructuring should read the case as a budgeting signal: the design sprint is the cheap component, and the change management around it is the long one.

What does this change for teams planning an IA overhaul?

The practical question any reader will ask is what a near-year implementation cycle implies for staffing and expectations. The case study's own framing — "initial work was done in a few weeks, but it was an ongoing project" — indicates the author treats the redesign not as a deliverable but as a continuous program. Teams that scope information architecture as a one-off workshop should recalibrate toward a sustained roadmap, where findings from the structural phase compete for engineering and content capacity over multiple quarters.

The one-year prioritization figure also carries a second implication. Work that takes twelve months to sequence is work that intersects with other product decisions, roadmaps, and stakeholder negotiations along the way. The architecture does not wait in a vacuum; it ages while it waits. A taxonomy validated in week six may face different content realities by month nine, which argues for iterative validation rather than a single up-front sign-off.

For editors and design leads, the study joins a familiar genre: the post-hoc structural retrospective that documents both the analytical method and the organizational friction. Its value lies less in novelty than in the candor of its arithmetic — two durations, stated plainly, that together describe the true cost curve of rebuilding how a product is organized.

Hrisov positions the project as ongoing, which suggests further installments may document the implementation phase in the same detail as the initial mapping work. Readers tracking the full lifecycle of an information architecture effort will find the continuation worth following as the remaining months of the rollout are documented.