Oracle Events
User Interface Design
User Interface Design
The Oracle Open World experience has always served as a resource for attendees during the event offering schedules, session catalogues and, once they occurred, content from the events including videos, images and summaries. However, we wanted to do more for attendees. Helping attendees get the most out of Open World meant keeping them engaged on social and helping them navigate the physical journey.
The experience needed to be more of a gateway that they could visit frequently and absorb quickly.
Beyond offering the schedule, we wanted to make the schedule more actionable by serving up the most relevant or exciting sessions they could experience now or in the immediate future as well as make previous sessions content more visible.
Moscone Center can be a bit of a maze, especially when utilizing all of the various conference and exhibit areas. We created an interactive overview of the conference area allowing users to plan their day and find their next session much more conveniently. We also played with the idea of offering exhibit highlights and local spots for lunch they might want to try.
As a Senior Interactive Designer on the design team responsible for digital event marketing, designing responsive web pages, UI components and adding motion design to Oracle’s sites promoting and supporting their live events.
We launched four conference sites annually: Oracle Open World, Oracle Code One, Oracle Modern Customer Experience (MCX) and Oracle Modern Business Experience (MBX). While built with a shared component library, each site has a unique design system and a thoughtfully crafted user experience.
This project was a bit of a challenge because the team wanted a voting system designed for twitter with no mechanism for automation. Anybody has the ability to nominate a programmer for a Groundbreaker Award by using a submission form. Then, our team manually vets the nominees and posts a curated ballot. Users are asked to tweet their vote which would then also be manually counted.
I would need to design a ballot experience for an unfamiliar experience that doesn’t confuse the users and result in un-submitted votes or an insignificant number of nominations.
Because nomination submissions would need to be manually checked, we needed to prevent users from spamming the nomination submissions. After the user clicked the vote button there was no mechanism available that would check that a vote had been tweeted and therefore we could not confidently show a success message so I needed to figure out how the user would know the tweet was their vote, not just an interaction to share the ballot.
How the content flowed would be important, as well as clear instructional copy and obvious visual markers to guide users through the process. I included a captcha to make it harder to spam the nomination submissions. In addition to a descriptive paragraph at the top of the page, I created a vote button that provided a visual nod to twitter as a function of the process and added a footer with the clear instructional CTA saying “Tweet to Vote.”
Because the sites all use the same components, each was designed with functionality, extensibility and scalability in mind. While the component should be simple to customize, designers should feel like they can get creative within the constraints available to them.
This component was to replace a similar menu component which consisted of up to 3 static images. Several feature requests needed to be filled. The new menu needed to include:
The result was a menu tile component which animated on hover and allows designers some creative freedom.
This component was intended to give viewers a visual overview of the events without requiring excessive engagement. The background is designed to enable background images or colors. This component required UI, visual and motion design.