Week 13 Blog

Building the Student Profile Experience

This week I started working on the student profile module in Globaly.io. After focusing on search flows and mobile interactions in previous weeks, this felt like a shift toward a more structured and personal part of the platform, where all student-related information comes together in one place.

The student profile is not just a static page. It includes personal details, application status, activity history, and other important data points that different stakeholders rely on. Because of that, the main challenge was figuring out how to organize a large amount of information in a way that feels clear and easy to navigate.

One thing I realized while working on this module is that profile design is really about hierarchy and clarity. Different types of information need different levels of visibility. Some data should be immediately visible, while other details should be placed in secondary sections to avoid overwhelming the user.

I also started thinking more about how different users interact with the same profile. For example, agents, students, and university stakeholders may all view the same data but for different reasons. This made me more aware of designing flexible structures that support multiple perspectives without changing the core layout too much.

Key Learnings & Insights

  • Profile design is about structuring information, not just displaying it.
  • Information hierarchy is critical when handling large datasets.
  • Different stakeholders interact with the same data differently.
  • Good profile systems balance visibility and simplicity.
  • Consistency becomes more important as modules become more data-heavy.

    • Application in Practice

    This week, I started mapping out the structure of the student profile and organizing different sections based on importance and usage. I focused on making the layout easy to scan while still keeping all necessary information accessible.

    Reflection

    One challenge I faced was deciding how much information should be visible at once. It was easy to overpack the screen because the profile contains so many data points, but I realized that simplicity and structure are more important than showing everything at the same time.

    This week also helped me understand that as the product grows, design work becomes more about organizing complexity than adding new features.

    Next Week Goals

    • Refine the student profile structure based on feedback.
    • Start designing interactions within the profile (edit, view).
    • Ensure consistency with previous modules like search and dashboards.
    • Get feedback from the senior designer before moving forward.

    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