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 organization are. The senior designer prepared the Figma files very clearly with proper labels, annotations, and organized flows. It showed me that the way work is presented also reflects professionalism.

Key Learnings & Insights

  • Design reviews focus on product goals, not only visuals.
  • Approval processes help reduce mistakes later in development.
  • Organized Figma files make reviews easier and clearer.
  • Presentation skills are important for designers.
  • Patience is necessary during review and approval stages.

    • Application in Practice

    This week, I observed how the senior designer prepared files for review and took notes on how everything was organized. I want to apply the same approach when preparing my own design files in the future.

    Reflection

    One challenge this week was dealing with the waiting time after designs were submitted for review. I realized I need to use that time more productively instead of just waiting for feedback.

    Watching the review process also made me think about my own growth. One of my goals is to confidently present designs to stakeholders one day, and this week showed me that presentation is an important professional skill that takes practice.

    Next Week Goals

    • Start working on the search flow of course/ institution/ agent for Globaly.io.
    • Improve the organization of my design files.
    • Continue learning how stakeholder reviews work.
    • Use waiting periods more productively.

    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 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