I served as the spokesperson for both the Sprint 1 and Final presentations during the Osfast project. These were key milestones where we presented our research, design progress, and final brand deliverables to the client.
In Sprint 1, I presented:
Presentations to the client are essential for:
Oscar was very content with the final presentation and even mentioned that he would be using parts from both groups’ work. The presentation made our decision clear and showed that we listened to feedback throughout. It also reinforced our credibility and ability to deliver professional results.
I learned the importance of presentation planning and role delegation. In the first presentation, there was some overlap and unclear transitions. For the final, we divided the slides evenly, which made the flow smoother and gave everyone room to speak about their contributions. Going forward, I’ll make sure we assign speaking roles based on comfort and expertise — not everyone needs equal time, but everyone deserves a clear role.
Oscar, our client for the Osfast branding project, gave us a general overview of his target group. However, the description was too broad to make clear design decisions, so we refined it using user research methods, including surveys and design testing.
A collaborative effort from the project group, including myself, Ceyda, Fahri, Bianka and Constantin, handled the research and data collection of the survey.
Brainstorm and refine questions for the survey to get user feedback on two poster designs made by Ceyda, we used Microsoft Forms to create a structured survey
We needed user feedback to validate visual choices for posters that could be used both online and in print. Oscar was not the target audience, so we had to base design decisions on the actual users' preferences.
The user research provided clarity on which poster design was more effective and guided the visual direction for Osfast’s materials. It also gave us user-centered reasoning to explain our design choices in later presentations, ensuring our work was defensible and not just subjective.
This task taught me the importance of survey design. A weak or vague survey leads to useless data and wasted effort. In future projects, I’ll make sure surveys go through internal testing or feedback rounds before being sent out, to ensure questions are clear, specific, and useful. A well-made survey can be the difference between an informed design and a guess.
We were introduced to Belco Alliance, a non-profit organization looking to redesign their outdated website. The client asked us to create a functional prototype to eventually replace the current one, which lacked modern features and clear structure.
We came together to work on our project plan to define our deliverables at the end of the project and what our plans were for every 2 weeks of each sprint. On top of that we also split the tasks to each member, assign roles for the group and tackled our risks. For team charter we set group rules that we would follow semi-strictly.
The project plan gave our group a planning, phasing and goals to follow. The team charter allowed for better communication by setting team rules and contact information for each member of the team as well as a creation of a group chat to stay connected at all times.
The project plan prevented us from missing a deadline as we had split the tasks to not overload any member with work, as well as reaching our milestones we set for each phase. It also allowed us to be flexible to allow us to adapt if any deviation were to happen.
The importance of a project planner and team charter could not be overstated, it helps a team connect and set rules, along with the general plan to follow with a gap to adapt accordingly. For future projects I would refer back more to these documents as it was a start document that was later forgotten until the end.
Our group was tasked with improving the Belco website. I was tasked with doing early research into how similar non-profit organizations structure their websites and what user experience strategies are employed.
I conducted competitive research by analyzing websites from similar non-profits — most notably Blijtanken, SIDN fonds and Alzheimers Nederlands. The goal was to gather insight into common design standards.
Across multiple sites, I identified a consistent structure:
We used these insights to fill in the MoSCoW table with what we should focus on and what could be a later inclusion. We then used the data gathered to organize it into a shareable format to plan our design direction.
Belco’s original website lacked structure, visual engagement, and a strong identity. We couldn’t base our design decisions on assumptions, so this research helped establish what modern non-profit websites were doing right. Understanding these patterns allowed us to identify gaps in Belco’s site and build a plan grounded in real-world examples.
The insights I gathered shaped the early wireframes and directly influenced the group’s MoSCoW table, helping us define what features to prioritize. It also provided a shared visual language and gave the team a clearer sense of what to aim for in our prototypes — not based on abstract ideas, but on tested and effective designs.
This task emphasized the value of research before design. I now see how much time and effort can be saved by learning from existing websites that serve a similar purpose. It gave our group a clear starting point and helped avoid wasted work on unfocused designs. Going forward, I’ll apply this step early in all major projects to create more grounded, user-driven designs.
After two weeks of working on the Belco Alliance redesign, we had to present our first sprint findings to the client. Constantin and I were selected to be the group’s spokespeople. This sprint presentation was intended to show what had been done up to that point and how we planned to continue moving forward.
The presenters were myself and Constantin, with support and preparation from the rest of the team. The audience was Belco Alliance, our client and stakeholders.
We split the presentation equally, showcasing research progress, initial design concepts, and early prototypes. I encouraged team members to explain their thought process behind their designs to involve everyone and provide Belco with deeper insight into our collective work.
We were informed that our user research was lacking and that we were behind schedule. This feedback triggered a reassessment of our approach, and I personally shared the survey more widely to collect additional responses. The feedback realigned us with Belco’s expectations and underscored the importance of user research.
I learned that during client presentations, it’s important to speak for the team and not as an individual. Improvisation works, but it risks missing key points, so I plan to use cue cards or notes in the future. I also learned that user research holds more weight than the design alone — especially when the client isn’t the direct user. Next time, I’ll ensure research is embedded early to support every design decision.
Following the first sprint presentation, our team was tasked with gathering more qualitative feedback through interviews. I conducted two remote interviews with people who matched Belco’s target demographic.
I (Matthew) was the interviewer and two individuals who were part of the intended audience – people interested in studying abroad – were the interviewee.
We were behind on user research, and these interviews gave us deeper insight into how the site was perceived by real users. Unlike surveys, interviews reveal detailed reactions and usability issues.
These interviews helped confirm design flaws and gave direction for future changes. However, I noticed that users skipped over known issues unless specifically prompted.
I learned that interviews must be guided toward uncovering usability problems — simply asking questions isn’t enough. Next time, I’ll include task-based scenarios like applying to school, to ensure users interact more thoroughly with the prototype. Interviews offer unique, valuable feedback that complements survey results and are essential in validating design decisions with real users.
After the UI/UX design phase for the Belco Education website, we transitioned into development and were divided into smaller groups. Our goal was to turn the Figma prototypes into functioning HTML sites. To stay organized and prevent merge conflicts or idle time, we adopted Trello to plan our workflow effectively.
The development group was made up of 3–4 people, and everyone participated in maintaining the Trello board and assigning tasks.
We created a Trello board to visualize the work that needed to be completed. Each major webpage was broken down into subtasks to ensure coverage of all required elements. The board served as both a checklist and a communication tool, which we regularly updated as we progressed and reviewed our tasks. We also aligned our progress with teacher feedback.
We needed a system to keep the group coordinated, avoid redundant work, and minimize code conflicts in Git. Trello made it easier to track progress and assign responsibilities. It also encouraged personal accountability and gave each group member a clear focus.
Trello allowed us to maintain momentum and clarity during the two-week development sprint. It kept everyone on task and helped us meet our deadlines more efficiently. Discussions about the board also contributed to smoother collaboration and faster decision-making.
I learned that planning tools like Trello are very useful, especially in group settings. They create structure and reduce friction between team members. However, tools are only effective if used consistently. To ensure I stay on track in future projects, I’ll combine digital tools with reminders — like post-its or pinned tabs — to keep my goals visible and actionable. This discipline will help me avoid falling behind due to forgetfulness or disorganization.