Week 8 Blog

What Feedback Taught Me This Week

This week, I shared my agent-institution partnership designs with the senior designer for feedback. I expected some suggestions, but some of the feedback also showed areas where my understanding of the product was still incomplete. Even though it felt a little uncomfortable at first, the discussion helped me improve the designs a lot.

One thing I learned this week is that feedback is about improving the design, not criticizing the designer. I know this in theory, but during real feedback sessions it still takes effort not to feel personally attached to the work. I think I handled it better this time by focusing more on learning instead of defending every decision.

The feedback session also reminded me how important a second opinion is. The senior designer noticed a navigation inconsistency that I completely missed because I had been working on the same screens for too long. It showed me that fresh eyes can catch things we stop noticing ourselves.

Another important lesson was understanding that iteration is normal. Going back and refining screens after feedback does not mean the first version failed. It simply means the design process is working the way it should.

Key Learnings & Insights

  • Feedback helps improve the work, not attack the person.
  • Small issues become easier to notice when someone else reviews the design.
  • Revising designs after feedback is part of the process.
  • Staying calm and open during feedback discussions is important.
  • Good design decisions should be explained with reasoning.

    • Application in Practice

    After the feedback session, I updated both partnership screens and improved the component structure based on the suggestions I received. The revised version felt much cleaner and more consistent.

    Reflection

    One challenge I noticed this week is that I sometimes agree with feedback too quickly, even when I have a reason behind my original design choice. I think I avoid pushing back because I prefer keeping discussions smooth and comfortable.

    I want to improve at explaining my reasoning more confidently instead of immediately changing things without discussion.

    Next Week Goals

    • Present the revised screens to the Product Manager.
    • Practice explaining my design decisions more clearly.
    • Keep improving consistency in the shared design system.
    • Become more comfortable with feedback and iteration.

    Comments

    Post a Comment

    Popular posts from this blog

    Week 6 Blog

    A Week of Listening and Learning This week was probably one of the most educational weeks I’ve had since joining the company. The senior designer walked me through the overall design structure of Globaly.io, explaining not just what was designed, but why certain decisions were made. It gave me a much clearer understanding of how the product fits together as a whole. One thing I noticed immediately was the difference in how experienced designers think. The conversations were rarely focused on individual screens. Instead, almost every decision connected back to the larger system, user behavior, or future scalability of the product. It made me realize that strong product design is really about understanding relationships between flows, not just creating visually good interfaces. I also became more aware of how important it is to ask thoughtful questions. Before the walkthrough, I spent time reviewing the product on my own so I could ask more meaningful questions instead of basic ones. I...
    Read more

    Week 9 Blog

    Learning How Design Reviews Really Work This week felt important because some of the Globaly.io designs were submitted for CEO review before going to development. Even though the screens were not directly mine, watching the review process helped me understand how design decisions are evaluated at a higher level. One thing I learned is that CEO reviews are not mainly about whether the design looks good visually. The bigger focus is on whether the design matches the product vision, supports the approved user flow, and solves the right problem. It made me realize that product design is connected closely with business goals, not just UI design. I also understood why the company follows a two-step approval process where user flows are approved first and designs are reviewed later. Earlier, I thought this process slowed things down, but now I can see how it helps avoid confusion and reduces rework during development. Another thing I noticed this week was how important presentation and org...
    Read more

    Week 3 Blog

    Learning to Design Together without Losing Consistency This week involved a lot of collaboration with the mid-level designer I work with on Orderlay. We both ended up working on the same component, but with slightly different approaches, which led to several back-and-forth discussions to realign the design direction. This experience made me realize how easily inconsistency can appear when ownership is shared but direction is not clearly documented or agreed upon early. Even small differences in structure or logic can affect how unified the final product feels. A key part of this week was learning how design systems actually function in practice. I started seeing them less as static files and more as shared agreements between designers. When those agreements are not followed consistently, the entire product starts to feel fragmented. Another important learning was around documentation. I realized that when design decisions are not clearly recorded with reasoning, the same discussions...
    Read more