Litmus Personalize
Background
With the acquisition of Kickdynamic personalization tool the team soon realized that the product had severe usability problems that weren't easy to fix. Most of the Kickdynamic customers required assistance from the Account Managers in order to achieve what they need. Not scalable. On top of that the technology behind Kickdynamic was .NET, not Rails which was the standard Litmus framework which meant the engineering team either should navigate through unfamiliar code and climb the steep learning curve or build using known tools which would be faster and more reliable.
Design artifacts for now — a full case study is in progress.
This is what the Kickdynamic personalization tool looked like initially.
The project
Create in a short period of time (a few quarters) a lightweight version of Personalization product that is intuitive and easy to use. Minimal set up, core capabilities for styling. Template-driven approach promised benefits like getting the customer into the editing flow quicker, a visual representation of what the widget is and what is possible, showing editing capabilities upfront.
The first iteration of the Litmus Personalize homepage.
The second iteration of the Litmus Personalize homepage based on the collected data and customer feedback.
With the new product in development both the Kickdynamic product (Litmus Personalize Pro) and Litmus Personalize Essentials should be available for Pro customers who were confused about the difference between the two. A few design options below show the visual treatment of the Litmus Personalize duality.
High fidelity user flows from the Index page for each content type start of authoring content to getting HTML. Three-step flow in the Editor was consistent across all content types (we haven't decided on what to call each widget, so it's still a "content type"). We launched with two widgets—Countdown timers and Progress bars—but within a year the number of widgets grew to a dozen.
An exploration of empty states and index pages for each widget type.
An exploration of grouping of the UI elements in the sidebar for an Add-to-Calendar widget.
Analyzing the UI elements with the help of the Heap analytics tool to capture usage patterns for further optimization.
An exploration of layouts and template organization on the homepage.
An exploration of Content Editor layouts and UI elements.
