How do you share feedback with Information Architects?

1 Understand the context

Before you give or ask for feedback, make sure you understand the context of the IA project. What are the goals, scope, constraints, and assumptions of the project? What are the expectations and preferences of the stakeholders? What are the current challenges and opportunities of the IA design? By clarifying the context, you can align your feedback with the project objectives and avoid misunderstandings or conflicts.

2 Use a common language

IA can be a complex and abstract field, with many terms and concepts that may not be familiar to everyone. To avoid confusion and miscommunication, use a common language that everyone can understand and relate to. Explain the meaning and purpose of any technical terms, acronyms, or jargon that you use. Use examples, scenarios, or visuals to illustrate your points. Avoid vague or subjective terms, such as "good", "bad", "intuitive", or "user-friendly", and instead use specific and measurable criteria, such as "consistent", "clear", "accessible", or "usable".

3 Be respectful and supportive

Feedback is not a one-way street, but a dialogue between peers who share a common goal. Therefore, be respectful and supportive of the other person's work, perspective, and feelings. Acknowledge their strengths and efforts, and appreciate their contributions. Express your feedback in a positive and constructive way, focusing on what can be improved, not what is wrong. Avoid personal attacks, criticism, or blame, and instead use "I" statements, such as "I think", "I feel", or "I suggest". Listen actively and empathetically to their feedback, and ask questions to clarify or understand their point of view.

4 Be specific and actionable

Feedback should be specific and actionable, meaning that it should address a particular aspect of the IA design and provide a clear direction or suggestion for improvement. Avoid general or vague feedback, such as "it looks nice", "it's confusing", or "it needs more work", and instead provide concrete examples, explanations, or recommendations, such as "the navigation labels are clear and consistent", "the search results are not relevant to the query", or "the content hierarchy could be simplified by using subheadings". Use the SMART criteria (Specific, Measurable, Achievable, Relevant, and Time-bound) to help you formulate your feedback.

5 Choose the right medium and timing

Feedback can be delivered in different ways, such as verbally, in writing, or through annotations or prototypes. Choose the medium that best suits the type, level, and urgency of your feedback. For example, verbal feedback can be more effective for high-level or strategic feedback, while written feedback can be more suitable for detailed or technical feedback. Similarly, choose the right timing for your feedback, depending on the stage, progress, and deadlines of the project. For example, early feedback can help shape the direction and scope of the IA design, while later feedback can help refine and polish the final product.

6 Follow up and iterate

Feedback is not a one-time event, but a continuous process that requires follow-up and iteration. After you give or receive feedback, make sure you document and summarize the main points, actions, and outcomes. Check in regularly with the other person to see how they are implementing or responding to your feedback, and offer your support or assistance if needed. Review and evaluate the changes or results of your feedback, and provide additional feedback if necessary. Celebrate your achievements and learn from your challenges, and keep improving your IA design and your feedback skills.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?