As a Senior UX/UI Designer in the AI recruitment space, I’ve learned to embrace last-minute changes with a positive outlook. Often, these adjustments make sense and enhance the overall product. Revisiting the structure or waiting to make improvements after release only leads to wasted time, energy, and resources. While it may take a few extra hours or days to implement, accommodating these logical, last-minute changes ultimately benefits everyone.

The first, it's to understand the scope project, everybody need to understand de initial scope and evaluate if we can change or add another gap in the project, but if so important include the demand we need to dispriorice other issue. The steakholder need to be aprt of the team to decide the new planning project.

To keep the project on track despite last-minute changes to the IA structure, I would prioritize effective communication with stakeholders to understand their needs, assess the impact of the changes, and adjust the project plan accordingly. I’d also ensure that the team is aligned and focused on key deliverables, potentially implementing a phased approach to integrate changes incrementally while maintaining momentum.

Last minute changes from leadership or other departments are common—they have different priorities, and real-world events can shift what the company needs to communicate. I make it a point to understand where these change requests are coming from: are they research-backed or driven by a specific goal or idea? I evaluate the risks, time, and cost to determine if the updates make sense. If we proceed with the changes, I define what success looks like and assess whether it impacts the rest of the information architecture.

Prioritize the Changes, assess Impact, communicate transparently, leverage Agile Methodology, manage Scope Creep, and lastly, update Documentation. In other words, stay calm, be transparent, make new agreements, stick to the plan, and document everything along the way.