# Information Architecture Sat, 08 Mar 25 ## 1. Conceptual Overview of the Session - **Focus:** A guided **retrospective** on participants’ recent design projects (web design assignment) and an introduction to how retrospectives feed into upcoming tasks (e.g., mobile app design, information architecture). - **Format:** Time-boxed prompts in a shared FigJam file, followed by group breakout discussions, then live Q&A on workflow best practices, licensing, AI usage, etc. **Key Takeaway:** Retrospectives serve as a structured way to learn from a completed project before moving on, ensuring continuous improvement in both process and collaboration. ## 2. Retrospective Activity: Goals and Structure 1. **Purpose of a Retrospective** - Surface honest reflections on what went well, what didn’t, and how to improve. - Create a “snapshot in time” capturing thoughts, blockers, and breakthroughs. - In a team setting, it prevents toxicity by clarifying issues early rather than blaming individuals later. 2. **Prompts Used** - _Design decisions & rationale_: Which choices were you proud of? How did you align with the brief? - _Challenges & limitations_: Where did you get stuck, and how did you handle it? - _Time & process management_: Did you structure your time efficiently? What would you do differently? 3. **Method** - **Time-boxing** each segment (~7 minutes) to force quick, concise reflection. - **Posting comments** directly onto a shared FigJam board as a central repository. **Action Tip:** Adopt a similar format in real-world team retrospectives – short, specific prompts plus group discussion/clustering of feedback. ## 3. Common Themes & Observations from the Retrospective 1. **Design Strengths** - Establishing small design systems (consistent color, type, spacing) improved cohesion. - Early feedback from peers/mentors led to clearer alignment with the brief. 2. **Challenges & Blockers** - Time management: Underestimating research/wireframing phases. - Getting stuck in iterative loops or perfectionism, leading to late deliveries. - Fear of judgment/criticism sometimes hindered open sharing. 3. **Tools & Workflows** - Wireframing was _essential_ for clarity, yet often skipped. - Some used AI for idea generation or to synthesize feedback but were unsure how best to integrate it. 4. **Emotional/Energy Factors** - “Overwhelm” surfaced as a frequent concern—particularly under tight deadlines. - Many recognized that more structure or frequent check-ins can mitigate stress. ## 4. Turning Feedback into Action **How the facilitator demonstrated “analysis > action”:** - Exported ~800 Figma comments to a spreadsheet. - Used AI (e.g., Claude, ChatGPT) to cluster, summarize, and extract patterns. - Derived suggestions for next assignment (e.g., mandatory wireframing, structured mid-project feedback, time-boxed research). ### Practical Ways to Make Retrospection Actionable 1. **Cluster & Synthesize:** - Group similar sticky notes/comments to see the most common pain points. - Pick the top 1–2 issues to address for the _next_ project (e.g., “Scope your research,” “Schedule interim feedback sessions”). 2. **Share & Discuss** - Discuss the clusters in a smaller team or breakout group to clarify root causes. - Decide on changes to workflow or deliverables (e.g., “No skipping wireframes,” “Team check-ins twice weekly”). 3. **Document & Reference** - Keep a living doc of retrospective notes and update them for each new project. - Refer back to these notes before kicking off a new sprint or assignment. ## 5. Upcoming Assignment & Information Architecture - **Next Project:** A **mobile app** assignment starting shortly, focusing on: - **Information Architecture:** Expanding from a single-page or simpler structure to a more complex multi-flow app. - **Mobile Patterns & Usability:** Designing consistent, user-friendly flows across various screen sizes. - **Design Systems:** Possibly more advanced setup of typography, color, and component libraries. **Action Tip:** - Plan your app design process early (wireframes → mid-project feedback → final visuals). - Create a small design system with color tokens, typography scales, and repeated UI components to stay consistent across screens. ## 6. Q&A Highlights and Best Practices 1. **Time Management & Avoiding Overwhelm** - Time-box tasks (research, wireframing) to avoid endless loops. - Break larger deliverables into milestones with frequent check-ins. - Regularly share progress with a peer or mentor to get small, quick feedback. 2. **Responsive & Mobile Design** - Converting desktop to mobile: typically stack columns vertically and adjust font sizes or entire layouts if needed. - You _can_ shorten copy for mobile if it’s too cramped, but communicate changes clearly to the client/developer. 3. **Font Licensing & Asset Use** - If using paid fonts, inform the client early, show them how it looks, and confirm willingness to purchase. - Provide alternatives or replacements if the client balks at licensing. - Keep a “mini design spec” to document chosen fonts, color usage, and layout grids. 4. **AI Tools & Workflows** - It’s normal to experiment with multiple AI models (ChatGPT, Claude, NotebookLM, etc.) for different tasks (e.g., summarization, real-time data scraping, analysis of large text corpora). - Maintain data privacy (especially with sensitive client info) and avoid letting AI usage overshadow basic design fundamentals. ## 7. Recommended Action Steps 1. **For Retrospectives** - **Schedule** a formal retrospective at every major project milestone (mid-project + project end). - Use **structured prompts** and short time boxes to keep the discussion focused and productive. 2. **For Next Assignment (Mobile App)** - Draft a **mini design system** early (typography, color, components). - **Wireframe** your flows first; finalize content hierarchy before diving into polished visuals. - Plan at least **one midpoint feedback** session—peer or mentor—before finalizing. 3. **For Ongoing Growth** - Try AI-based clustering for user feedback or personal notes; it saves time synthesizing large volumes of data. - Build or adopt a personal library of references for mobile-specific design patterns. - Keep a personal log of “what went well/wrong” after each sprint to track improvement over time. --- ### Final Note By deliberately reflecting via retrospectives and structuring each design phase (research, wireframing, feedback, final visuals), you minimize last-minute chaos and ensure each project improves on the previous one. Use these notes as a checklist for your next assignment and as a reference for future team or solo retrospectives.