Design of an administration product interface for a marketing personalization cloud platform

Overview

My tasks
- Solution-problem fit validation
- Segmentation and personas
- Value proposition and brand concept
- Brand design and brand-book
- Design system development
- Continuous product discovery
- From wireframes to prototypes
- Touchpoint & Journey management
- Content design and strategy
- Mentoring

Yuspify is a marketing automation SaaS product, developed by Gravity R&D made for the e-commerce SME sector, by leveraging the robust enterprise-grade personalization engine that is present in the enterprise solution.

While enterprise clients configured their recommendation instances with the support of Gravity integration and data teams, Yuspify customers will have to integrate and configure the solution themselves to harvest the revenue-increasing potential of the product.

My task was to design and ship a completely new product utilizing the existing personalization engine for a target group who possibly never heard about recommendation systems, or data-driven machine learning terms.

Solution-problem fit validadtion

Product strategy
Business plan
Business design
SLA creation
Concept validation
Lean UX
Value proposition design
Fake door testing
Riskiest assumotion test

Our initial attempt was to sell the existing enterprise solution as an SME product on the local market to recruit early adopters for the new product concept.

We tested how local and CEE regional resellers would resonate with the value proposition, and collected feedback.

With a six-month-long experiment we tested how local and CEE regional resellers would resonate with the value proposition, and we were able to demonstrate clear demand and mitigate significant risks in terms of feasibility.

From experiment to service

Data strategy
Problem deffinition
Persona creation
Qualitative data collection
Discovery interviews
A / B testing
Brand design
Pricing

After the validation phase we had to build a support operation to onboard new SME users, from which we built a solid and deep understanding of their needs and mindsets - both based on our own experiences with their integration and from their direct feedback as well.

Aligned with the products' inherently data-driven nature, we continuously conducted A/B tests to improve recommendations performance on the newcomer target group’s e-commerce stores and websites.

While the self-serving aspect is essential in the life of a b2b platform, where marketing, e-commerce, and cx managers would set up, configure, and optimize their recommendations we started to build the yuspify administration platform.

Building a B2B saas product

Data strategy
Problem deffinition
Pricing
Pricing
Value porposition design
Qualitative data collection
UX / UI design
Discovery interviews
A / B testing

After we had paying customers, the demand to further scale the product grew significantly.We aimed to create a more comprehensive, self-service system that would "outsorce" integration and configuration tasks as much as possible to the customers.

A birght product vision was emerged, guided by the following principles:

  • Providing a usage-based pricing model that offers an ROI-positive solution for the customers.
  • Outsource integration as much as possible to the customer side and automatie it wherever possible.
  • Replacing configuration options with one-size-fits-all recommendation logics.
  • Delivering multichannel, respsonsive, high-quality recommendations.

From the perspective of the entire user journey, we had to start from a very rudimentary state, where, in the early stages, users after logging in could upload databases and set up tracking codes through a tutorial system.

The design in focus

Roadmapping
Sprint planning
Design strategy
Value porposition design
Product strategy
Dual track agile
Goal setting
Team management

It became a strategic goal to optimize the initially sufficient but rudimentary solution from a UX perspective, so that an average Central European e-commerce shop owner or operator should accomplish the folowing jobs, in a reasonable time:

  • Tracking code insertion
  • Initiate database synchronization
  • Designing a recommendation box
  • Publish recommendation boxes, and the system itself
  • Interpret simple analytics with common KPI-s around the industry

Every line from above have become a recurring design and development project, with continuous - data collection - problem definition - ideation - design - test - develop - deploy development circle.

Strategy to UI

Vendor management
Partner management
Design reviews
Agile UX
Journey management
Leading front-end development
UX / UI design
Usability testing
Design system development
Mentoring designers

After the first wireframes, we onboarded a component library in vue.js - as a preliminary design system, the design team started to define and design a core set of components as the scope of the product MVP.

We quickly reached a point where these few building blocks were no longer sufficient, and a well-considered prioritization process and roadmapping became necessary.

With a better understanding of our target audience's mindset, we re-evaluated our value proposition and the strategic goals for the coming years, taking a deeper look at the European e-commerce and Shopify markets.

As a result, we rebranded the product, further distinguishing it from the enterprise service, and on this foundation, we began developing the design system.

Continous improovement

Mentoring designers
Release management
Scoring models (KANO & RICE)
Qualitative & Quantitative data collection
Design management
Smartlook & Hotjar
Design reviews
Design affinity model
Journey management

We reached certain limits in several areas where it became clear that, considering the competencies and capabilities of our target audience, even with significantly more resources and perfect processes, we would not achieve breakthrough success.

Therefore, we began focusing on areas where users can achieve the greatest business impact with minimal contribution and the least task complexity.

Personal takeaways

  • During the project I couldn't realize that not every stakeholder was as convinced about the solution as we thought - people originally in love with CLI and self-written Python scripts not necessarily would trust in a strongly visual solution - luckily, they ended up being the product's biggest fans.
  • I learned how to adapt to a rapidly changing startup environment as a designer and a problem solver.
  • Separating problem space to solution space on a human level is a wise practice of human centered-design. Letting blinking ideas go never was as hard as when I wanted to solve users' problems with this intensity.
  • Building an awesome team of smart, curious, and dedicated people can be a larger fun than building a useful product.