IBM Watson Activations Experience

To futher seat Watson as the go-to AI platform for business, IBM needed a series of experiences that utilized Watson services on real-life data. Our team created 2 experiences based on specific packages of services that are geared for specific business problems.

I dug into Watson's capabilities and found the best technological match for ideas that were actually executable within our time frame. This deep understanding of the client's technology's capabilities was critical in being able to deliver an experience that fit their needs but also wowed participants.

Senior Designer – Jonathan Haggard
Created At – AKQA

Creative Director – Felix Roos
Senior Designer – Sungjoon Hoon
Copywriter – Crystal Yu
Motion Designer – Ryan Jones
Creative Developer – Yagiz Mungan
Client Director – John Freshwater

Working together with subject matter experts on IBM's Visual Recognition and Discovery teams, we came to our final concepts. One experience that correlated the price of Bitcoin on specific dates to what was happening in the news that day. The other was using Watson to surface insights from popular app's terms of services and privacy policies. This was thoroughly vetted by our own tech team and also IBM Watson's specialists.

Tight collaboration between creative developer Yagiz Mungan and accompanying development team was critical to the execution of the concepts. Above you can see a clickthrough of the live code. The dot visualization was built in WebGL, with a layer of React for the UI.

I crafted the initial concept for the activation's shape and presence, with the IBM's internal team finalizing production on the physical object.

Since this was going to be an accompanying piece to the IBM Watson Primer, it needed to share a visual language. We chose to use dots as our main interactions and to create infographic displays.

I developed the look and feel of the data visualizations in After Effects using Trapcode Form and Particular. Ryan Jones provided animation direction with specific comps for the development team to work from.

The design language was developed was developed with the rest of the design team to be extensible across multiple executions. Since the IBM team was looking to build 6 experiences in total, the design needed to be a framework that was rigid enough to be consistent but also flexible enough to house unique visualizations.

Let's start talking