design-critique

6 posts

figma

Figma’s feedback gift guide | Figma Blog (opens in new tab)

Feedback is most effective when it is treated as a thoughtful, context-dependent exchange rather than a generic “gift.” Figma argues that good feedback depends on timing, project stage, team culture, and the relationship between the people involved. Matching feedback to the work’s level of development helps teams stay open to possibilities while still making progress toward clear goals. ## Match Feedback to the Design Stage - **Brainstorming:** Keep feedback expansive so it does not eliminate promising directions too early. - **Early concepts:** Use research and data to narrow options while preserving an open mind. - **Product reviews:** Check that the work supports product and business objectives. - **Design critiques:** Offer detailed UX and visual suggestions and encourage consistency. - **Prototypes:** Focus on usability and animation. - **High-fidelity designs:** Examine detailed decisions that may benefit from another perspective. - **Final designs:** Identify overlooked flows, use cases, or remaining gaps. - When requesting feedback, explain what type of input would be most useful at that stage. ## Adapt to Team Culture - Feedback practices should reflect where a company is in its shift toward collaboration. - Teams early in that transition may need more context, frequent critical conversations, and patience while feedback relationships develop. - Teams with an established feedback culture can rely on direct communication through proven channels. - Feedback should meet teammates where they are rather than assuming every team has the same norms. ## Respect Timing and Working Styles - Timing matters as much as content; feedback is more constructive when people are ready to receive it. - Consider project deadlines, teammates’ schedules, time zones, and personal preferences. - Avoid sending work-related messages at inconvenient hours without setting expectations. - Communicating your own working style and accommodating others’ schedules can reduce friction. Thoughtful feedback helps turn conversations into action, but it requires adapting both the message and delivery to the project, people, and culture involved.

figma

FIT’s principles for fostering a collaborative classroom | Figma Blog (opens in new tab)

Professor Christie Shin of the Fashion Institute of Technology uses Figma to create a virtual classroom centered on systems thinking, frequent feedback, and open collaboration. Her approach treats design as an evolving process rather than a finished object, helping students build habits that mirror professional design teams. She organizes coursework into Figma teams, projects, files, and templates while preserving space for experimentation and individual expression. ## Celebrate Early Work - Students share unfinished ideas regularly instead of waiting for polished presentations. - They visit one another’s files and provide feedback both verbally and directly in Figma. - This reduces the fear of exposing imperfect work and reinforces design as a way of thinking. ## Guide the Process While Leaving Room to Grow - Coursework—from exercises to final presentations—is kept in Figma. - Students receive structured files with named pages and templates for each activity. - The infinite canvas leaves room for sketches, iterations, and exploratory work. - Each file becomes a “creative journey,” documenting research, summaries, wireframes, and development over time. ## Work Individually, Together - Students complete individual projects within study groups. - For a project involving an MTA app design system and video case study, students presented progress incrementally rather than waiting for final critiques. - Continuous peer feedback reflects real-world cross-functional collaboration and helps students become less attached to initial solutions. ## Embrace Influences - Students are encouraged to share work openly instead of hiding ideas to prevent others from copying them. - Shin frames influence as a normal and valuable part of design practice. - Each project requires students to collect and credit visual references from professional designers and classmates. - Discussing these influences during critiques makes the design process more transparent. The article recommends combining clear structure with open collaboration: provide students with organized tools and milestones, but give them room to experiment, share early work, learn from peers, and acknowledge the influences shaping their designs.

figma

How to pair design (and convince your boss to invest in it) | Figma Blog (opens in new tab)

Design pairing is a collaborative practice in which two designers synchronously solve the same problem, rather than splitting a project into separate tasks. One designer drives the design while thinking aloud, and the other navigates by observing, asking questions, and identifying edge cases. The approach can improve design quality, accelerate feedback and knowledge sharing, reduce meetings and documentation, and strengthen team morale. ## What Design Pairing Means - Two people work on the same design problem at the same time. - It differs from “divide and conquer,” where designers independently handle separate parts of a project. - Pairing can be applied to tasks such as designing a signup flow, exploring ideas, or refining a user experience. ## Common Pairing Styles - **Generator and synthesizer:** One designer produces many ideas while the other organizes them into a coherent UX flow. - **Lead and support:** A more experienced designer leads while another develops skills through participation. - **Screenshare pairing:** Adapted from pair programming, with designers collaborating directly in the same file. ## Structuring a Pairing Session - Set up shared access to the same design file; tools like Figma enable real-time multiplayer collaboration. - Assign two roles: - **Driver:** Controls the file and performs the design work while explaining decisions aloud. - **Navigator:** Observes without editing and asks constructive questions about patterns, user confusion, and potential edge cases. - The navigator should raise questions rather than criticize, bringing critique and future user feedback into the design process immediately. ## Practical Tips - Agree on the problem before starting, using sketching or inspiration gathering to establish shared context. - Decide who will drive and navigate. - Set a session length, whether it is 10 minutes, a day, or a week. - Take breaks because sustained collaboration can be tiring. - Switch roles so both designers practice driving and navigating. - Use supportive improv principles: build on ideas first and defer rejection when possible. - Normalize the vulnerability of having someone watch you work. - End with a brief retrospective about what worked and what felt uncomfortable. ## Making the Business Case Although pairing appears to use two designers on one task, it can make the overall process more efficient by: - Providing immediate, contextual feedback. - Reducing distractions and later critique cycles. - Sharing knowledge faster and reducing documentation and meetings. - Producing more ideas and uncovering more errors, bugs, and edge cases. - Keeping design files more organized. - Increasing confidence in design decisions. - Improving team morale, which can further improve the quality of the work. Teams should experiment with short pairing sessions, evaluate the results, and expand the practice where it improves speed, quality, and collaboration.

figma

Inside Figma: the product design team’s process | Figma Blog (opens in new tab)

Figma’s product design team uses deliberate rituals and meeting cadences to maintain connection, consistency, and a high quality bar across designers embedded in different product areas. The article distinguishes the horizontal design-team culture from the vertical product-team culture, arguing that both require investment. Its processes are intended as adaptable examples rather than prescriptions, especially during the disruption of the COVID-19 pandemic. ## Two overlapping team cultures - Designers belong to both: - A **horizontal design team**, which supports consistency, craft, and shared quality standards. - A **vertical product team**, which focuses on shipping improvements and building expertise in a product area. - As companies grow, designers tend to move from close collaboration across the whole design team into specialized product-area groups. - Figma, with around 10 product designers, was encouraging designers to prioritize relationships with product teams while relying on design-team processes for alignment and community. ## Process during the pandemic - The article was written during COVID-19, when remote work and personal disruption affected productivity and morale. - Design leadership encouraged people to make space for mental health and acknowledged that output might fall significantly. - Regular collaboration became especially valuable because it helped replace some of the social connection normally created in an office. - The author cautions teams not to adopt new rituals automatically; each organization should decide whether it has the capacity for process changes. ## Weekly processes ### Monday warm-up - **Participants:** Product designers, with optional participation from research and brand team members. - **Schedule:** Mondays, 9:30–10:00 a.m. Pacific Time. - **Purpose:** Start the week with a light, social activity rather than immediately focusing on work. - The 30-minute meeting includes a “weekend update” segment lasting roughly five to ten minutes, along with additional activities designed to help the team reconnect. ## Scope of the article - The post focuses on **design-team processes**, not the broader product-development process. - It covers recurring weekly activities, monthly and quarterly rituals, and practical advice for designing team activities. - Product roadmapping, product-team collaboration, hiring, and design critiques are treated in other Figma resources. Figma’s approach emphasizes creating intentional, repeatable moments for connection while keeping the process flexible. Teams should adapt these rituals to their size, structure, working environment, and the personal needs of their members.

figma

How we do design critiques at Figma | Figma Blog (opens in new tab)

Figma argues that design critiques should be motivating, useful, and psychologically safe—not intimidating or discouraging. After identifying problems in its own critique process, the team redesigned critiques around clear goals and several formats suited to different stages of design work. The result is a more flexible practice focused on unblocking designers, improving quality, sharing context, and encouraging collaboration. ## Improving the Critique Process Figma began by “critiquing critiques” and gathering feedback from its design team. Common problems included: - Overcrowded meetings - Shallow or unactionable feedback - Complex problems squeezed into short time limits - Groupthink, excessive agreement, and reluctance to be honest - Critiques that failed to help designers move forward The team documented issues in a shared Figma file, identified the productive and creative energy in that workshop, and continued iterating through a dedicated Slack channel. ## Goals of Design Critique The team aligned on four primary purposes: - **Unblocking problems and generating ideas:** Helping designers overcome difficult problems or explore early possibilities. - **Elevating quality:** Improving visual design, interaction details, and broader product direction. - **Encouraging consistency:** Reusing established patterns and identifying when new patterns are needed. - **Sharing context:** Keeping the design team informed about company, product, and project developments. ## Standard Critiques Standard critiques are structured sessions in which a designer presents work and receives feedback from peers. They are most useful when the presenter explains the project’s context, goals, and specific questions before discussion begins. - The facilitator keeps the discussion focused and balanced. - Feedback should be concrete, honest, and actionable. - Participants should critique the work rather than the person. - The format works best when the group size and scope are limited. ## Jams and Workshops Jams and workshops are collaborative formats for situations that need ideas rather than evaluation. - Designers work together actively instead of simply commenting on a presentation. - They are useful for early-stage exploration, brainstorming, and complex problems. - The shared activity reduces the pressure placed on one presenter. - Their informal, energetic quality can produce the kind of creative collaboration Figma wanted in regular critiques. ## Pair Design Pair design places two designers together to solve a problem collaboratively. - One designer can explain their thinking while the other contributes ideas and challenges assumptions. - The format encourages deeper discussion and immediate iteration. - It is particularly useful for focused problems that benefit from sustained attention. - Pairing can produce more actionable feedback than a large-group discussion. ## Silent Critiques In a silent critique, participants review work and write feedback before discussing it aloud. - Everyone has time to inspect the work carefully. - Written comments reduce the influence of the most vocal participants. - The approach helps limit groupthink and “+1” feedback. - Discussion can focus on patterns and themes that emerge from the individual responses. ## Paper (“Print-Out”) Critiques Paper critiques use printed screens or designs placed around a room for participants to annotate. - Designers can review work at their own pace. - Feedback is often more detailed and specific than verbal comments. - The physical format encourages participants to engage directly with the work. - It is useful for reviewing multiple screens or flows without a presentation dominating the session. ## FYI Critiques FYI critiques are informational rather than feedback-driven. - A designer shares work mainly to provide context or visibility. - Participants are not expected to solve the problem or offer extensive critique. - This format avoids turning every design review into a decision-making meeting. - It helps the team stay informed while preserving critique time for work that needs active input. ## Principles for Effective Critiques Figma’s recommendations emphasize adapting the format to the work and creating a constructive environment: - Define the purpose of the session in advance. - Invite only people who can contribute relevant perspective. - Share context and specific questions before asking for feedback. - Match the critique format to the project’s stage and needs. - Use a facilitator to manage time, participation, and focus. - Encourage direct, respectful, actionable feedback. - Avoid groupthink and uncritical agreement. - Separate critique from final decision-making when appropriate. - Keep sessions focused enough that participants can engage deeply. - Treat the process as something to continually evaluate and improve. The practical recommendation is to stop treating critique as a single meeting format. Teams should establish clear goals, experiment with methods such as workshops, pair design, silent reviews, and FYI updates, and regularly assess whether critiques are genuinely helping designers feel inspired, challenged, and empowered.

figma

Figma feature highlight: Observation Mode | Figma Blog (opens in new tab)

Figma’s Observation Mode lets one person mirror another collaborator’s screen in real time. By clicking a teammate’s avatar, users can follow cursor movements, navigation, text changes, and prototype interactions as they happen. Figma presents it as a useful alternative to traditional screen sharing for critiques, client feedback, and user testing. ## How Observation Mode Works - When multiple people are viewing a Figma file, click a person’s avatar in the upper-right corner. - Your view then follows everything that person sees and does. - The mirrored activity includes: - Moving through the file or prototype - Editing text inside frames - Selecting objects - Expanding design elements - Moving the cursor - Observation Mode is available even to users with view-only access, provided sharing is enabled for the file or project. ## Real-Time Design Critiques and Feedback - Designers can watch clients or teammates explore a design instead of relying only on verbal explanations. - The feature makes remote critiques more interactive by allowing everyone to follow the same part of the file. - Clients can demonstrate their reactions and questions directly within the design. ## User Testing in Figma - Researchers or designers can observe users as they move through a prototype. - Watching interactions live reveals: - Where users hesitate - Which elements cause confusion - Where navigation breaks down - Which interface areas create pain points - This provides more direct evidence than collecting anecdotal feedback after a test. ## Sharing and Privacy Considerations - Anyone with access to a shared file may be able to use Observation Mode, including viewers. - Designers should be comfortable being observed before sharing a design URL. - Teams should consider file-sharing permissions when using the feature for sensitive work. Observation Mode is best used as a lightweight collaboration and research tool: enable sharing, ask participants to explore the file or prototype, and follow their activity live to gather more precise feedback.