I’m Fynn, one of the two new Whalers. The next 17 weeks me and my buddy in crime Erik, are part of one of the youngest creative agencies in Arnhem. Filled with creative and technical mind’s of the boys that work here, I believe we’re gonna have a great internship.
The purpose of this microblog is to keep our schools’ teacher up to date of all the work we do here, and to let her know we’re still living and learning.
So every friday I will post some little story about that week, what I’ve learned, what I did.
This week we did some heavy User Experience practice. I don’t know if you guys know Noombers.com (be sure to check it out). Anyhow, for anyone out there unknowing, Noombers is a online platform for the sports community. There are a few key features in Noombers, starting with a powerful tool that helps organizers to create and manage tournaments with great ease.
This tool may be is the core of Noombers, but thats not what the platform is all about.
In my eyes, the main goal of Noombers is to provide for the whole sports community, the player as an individual and as part of a team, the organizer, the managers, and even the fans and the ref’s. Passionate players and ambitious organizers is what Noombers needs at this moment.
Where do I fit in?
As a ‘user experience’ / ‘user interaction’ designer, my job is to make every user-process as easy and intuitive as possible. This goes for the most basic activities, like signing up for Noombers, to the more complex features of the platform like managing a tournament or keeping track of the statistics of a team or a player.
Past week we made a huge step towards understanding what our users need and how we, in the near future, are able to provide in those user needs.
The method we are using for this maybe one of the best UX methods there is in regard to understanding your users, which is the ‘Customer Journey Map’, short: CJM. Something like this.
At this moment we’re in the starting phase, which is breaking down the path of the two main usertypes on our platform: the player and the organizer. We divide our user paths into small steps so we can see what a user is supposed to do at a certain point in a process. Later we will match user-needs to those specific steps so we can find out what the best way is to support our user within that step.
Hungry for more? Leave a comment and i’ll try to answer your questions A.S.A.P.
A little office-toilet-calendar-bullshit-bonus: