Here's how you can ensure the quality of deliverables as a project manager in Information Architecture.

Define Goals Establishing clear goals is the cornerstone of any successful project. In Information Architecture, this means understanding the end-users' needs and the business objectives. You must articulate what success looks like for the project and set measurable targets. This clarity will not only guide your team's efforts but also provide a benchmark against which you can measure the quality of your deliverables. Remember, if goals are not clearly defined, your team may produce high-quality work that misses the mark because it doesn't align with the project's intended outcomes.

Engaging stakeholders throughout the project is crucial for maintaining the quality of IA deliverables. Regularly involving them in discussions and decision-making ensures their needs and insights inform the IA strategy. This collaborative approach aligns the project with business goals and user expectations. Stakeholder feedback is invaluable for refining deliverables, preventing costly revisions later, and ensuring the final product resonates with its intended audience. By fostering continuous engagement, you enhance the relevance and effectiveness of your IA outcomes

This is an important aspect to consider and implement. This also helps to ensure you can hire new talent as needed. So standardization is a golden rule, though at same time allow for creative ways of getting things done. That is the challenge of an IT manager to maintain so that team is cross skilled and happy team.

As a project manager, when ensuring the quality of deliverables, testing is needed not just by the users, but also internally. The project manager needs to provide clear, precise acceptance criteria for testing the update. There should also be a baseline of testing for any update to catch common issues like bugs, UI issues, performance lags, unintended interactions, and more. Internal testing is a team effort. Updates should be demoed to the project manager and stakeholders to determine if they meet expectations. Developers should implement unit testing and carefully test their work before it goes to QA. QA should provide the final sign-off after testing, ensuring that the update meets or exceeds the acceptance criteria and baseline.