This week I learned that working with a team you can actually depend on changes everything. Even having just one other person who is fully present and engaged makes such a difference when creating something meaningful. It is not just about splitting the work evenly. It is about feeling like you are building something together.
Having someone to bounce ideas off of made the process feel lighter. I was able to ask questions without feeling unsure, and I felt more confident sharing early drafts instead of waiting until something felt perfect. The conversations shaped the design in ways I would not have reached on my own. Ideas that felt fine at first became stronger and more intentional simply because we talked through them.
I think the title comes from something we have all experienced. The quiet promise of “I will do my part later.” Sometimes it comes from procrastination. Sometimes from overconfidence. Sometimes from assuming someone else will carry it. But this week showed me how much better the outcome is when everyone shows up early and stays engaged throughout the process.
It also made me reflect on accountability. When you know someone else is investing their time and energy, it naturally pushes you to rise to that level too. The work becomes less about checking a box and more about contributing to something shared.
This project reminded me that collaboration is not just dividing tasks. It is trust. It is communication. It is momentum. And when it works, it feels less like a group assignment and more like a creative partnership.
On the more academic side of tangible skills taught this week, I learned the differences between wireframes and what low-, mid-, and high-fidelity wireframes can look like and how they function. Honestly, this week felt like I learned more than I have in past modules, and I actually retained the information because it made sense and felt strangely intuitive. It reminded me of how school has conditioned us to follow structured systems, similar to UX and UI design, the scientific method, and the engineering design process taught since elementary school.
I now understand the UX process as identifying the objective and challenge, then creating a user persona to represent a real user and humanize the experience. This helps with brainstorming what users might be looking for, need, or get frustrated by. From there, you compare competitor websites and note what they do well or poorly, especially when compared to your main competitor. Nielsen’s 10 Usability Heuristic Principles act as an additional guideline for evaluating design choices. Interviews and usability testing with potential users help determine whether their needs align with the site and reveal what challenges or positive experiences they notice while using the product.
The common deliverables in the UX process include user personas, wireframes, prototypes, heuristic evaluations, competitive and comparative analysis, and usability testing results. Following the UX process improves a design project overall by helping teams understand user needs, visualize solutions, evaluate usability, and make informed design decisions.
In the case of my client’s blog, applying the UX process could enhance it by helping me better appeal to the typical user I want to visit the site. I would focus more intentionally on the user persona and their needs. I also looked at competitor blogs and identified what worked well and what did not, which helped guide what to include or avoid. If I had done usability testing, I would have gained a clearer understanding of how the site feels to real users. By following the heuristic principles, I could more clearly identify challenges and address them in an organized, user-centered way.
