Week 4 Blog

A Sudden Shift in Direction

This week brought a major shift in my role. The CEO announced that I would be transitioning from Orderlay to Globaly.io. Since Orderlay already had two designers covering the work including me, the decision was made to move me to Globaly.io, which is still in its pre-launch stage and needed additional design support alongside a senior designer.

At first, the transition felt sudden, but the reasoning behind it was clear from a company perspective. It helped me understand that product decisions are often driven by broader business needs rather than individual project timelines. Learning to step back and see that bigger picture became an important part of my reflection this week.

This change also tested my flexibility as a designer. I’ve often identified myself as someone who thinks strategically, but this situation made me question how well I can actually adapt when priorities shift quickly. It pushed me to think about how fast I can adjust and still contribute meaningfully in a completely new context.

Another important part of the week was around transitions and responsibility. Moving between products is not just about leaving work behind, but ensuring nothing is lost in the process. I spent time preparing structured handoff documentation so the remaining designer on Orderlay could continue smoothly without missing context.

Key Learnings & Insights

  • Business decisions often override individual project timelines and design plans.
  • Adaptability is a critical skill in fast-moving product environments.
  • Professional transitions require structured handoffs, not informal exits.
  • Documentation ensures continuity when team responsibilities shift.
  • Feeling uncertain during transitions is normal, especially in new product environments.

    • Application in Practice

    I created a detailed handoff document for all my Orderlay work. It included annotated screens, progress status, and clear notes on what was completed and what still needed attention. This helped ensure a smooth transition for the designer continuing the work.

    Reflection

    This week came with mixed emotions. On one hand, I felt nervous about moving to a new product and working closely with a senior designer on a pre-launch system. On the other hand, I also felt trusted, especially since this move came directly from leadership.

    I’m trying to hold onto that trust instead of focusing too much on uncertainty. It feels like a reminder that I’m being placed where I can add value, even if the environment is unfamiliar.

    Next Week Goals

    • Understand Globaly.io’s purpose, users, and product vision.
    • Review existing design work and systems already in place.
    • Align with the senior designer on workflow and expectations.
    • Get comfortable with the new product context before contributing heavily.

    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