Conflicting ideas
|
“What features” vs.
“Who you are.” |
While I was designing for the product on-boarding for another project, I learned something and thought this approach of using user types as tabs might have been very risky.
|
|
Users generally have hard time wanting to identify themselves as one role (this is quite different from choosing whether you’re a designer or engineer as a role for the purpose of collecting metrics, because this is to show the content they’re about to see)
|
This can also throw them off because we’re putting ourselves in the box of thinking that "this is what you are” without actually knowing them or what they are interested in learning about Mode. This potentially can drive people away because we’re making guesses on individual level.
|
Websites we looked into that are using the tabs are mostly using for the purpose of showing either the features or the services so that it doesn’t matter who the user is, the information is available to click through.
|
We saw on A/B testing that users were interacting with the section with higher engagement than static sections.
EventWatch
EventWatch synchronizes the qualitative information and reports collected from the event fields into client's database. This is to automate the process of communication and reports in between tour managers and their current clients.
BACKGROUND OVERVIEW
EventWatch is part of an Event Lifecycle Management tool.
The project was kicked off with SPR Agency and the mock up below was provided.
The project was kicked off with SPR Agency and the mock up below was provided.
