Week 10 Blog

Designing Search Flows for a Large Platform

This week, I started working on the search flow for courses, institutions, and agents in Globaly.io. Since the platform is quite large and supports different types of users, the search system includes many filters and options. While going through the flow, I realized how important it is to organize information properly so users can find what they need without feeling confused or overwhelmed.

One thing I learned this week is that search design is not only about displaying results. It’s also about helping users narrow down choices in a simple and comfortable way. With so many filters involved, even small decisions about layout and hierarchy can affect how easy the experience feels.

I also started understanding the importance of showing information gradually instead of putting every option on the screen at once. Some filters are useful only in specific situations, so revealing advanced options only when needed helps keep the interface cleaner and easier to use.

Another thing I noticed while working on this flow is how challenging it can be to balance functionality with simplicity. Since Globaly.io serves users from different backgrounds and countries, the design cannot assume everyone is familiar with complex digital systems. The experience needs to stay clear, guided, and easy to understand for everyone.

Key Learnings & Insights

  • Search flows become more complex in large multi-user platforms.
  • Filters should help users, not overwhelm them.
  • Information hierarchy plays a big role in usability.
  • Showing options gradually can make complex systems feel simpler.
  • Simplicity is important when designing for a global audience.

    • Application in Practice

    This week, I focused mainly on organizing filters and improving the structure of the search layout. I tried to make the interface easier to scan by grouping related options together and avoiding too much information on one screen.

    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

    • Continue refining the search and filter experience.
    • Start designing the mobile version of the search flow.
    • Improve the hierarchy and structure of search results.
    • Get feedback from the senior designer on usability and clarity.
    • Focus on making complex flows feel simpler and more intuitive.

    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