The overall design and organization of the product was a difficult problem. The elements that needed to be included were:
- Pragmatic admin tools to: create a community, create an event (duration, location, etc)
- Data visualization to track progress
- Recommendation system to guide users throughout deploying a single event and also over time to measure the effectiveness of Braindates
I applied a lot of approaches to understanding the information architecture for this product.
For pragmatic admin tools, I did an inventory of the properties, organized them in a wireframe and tested with event organizers.
For data visualization, I matched the data points with uses cases (and their moments in time), mapping them to the actions that could be taken according to the values of the data.
For the recommendation system – I created an ‘event timeline‘ which would serve as the home base for all the actions the admin needed to take and in what order. For urgent recommendations they were located on the timeline and embedded within the page(s) where the data (and corresponding functionality) were housed.
Through careful evaluation of the above areas of functionality, the information architecture evolved from a more standard ‘build, measure, learn’ to a specifically event-oriented structure, which maps to how event organizers think about this workflow.