As Integrate's Demand Acceleration Platform expanded its reach, the complexity of its features began to overshadow its utility, especially for small-to-medium-sized clients. The Marketing Initiative Builder project was launched to tackle this challenge by enhancing user interface intuitiveness and simplifying the configuration process. This initiative focused on creating a seamless user experience across all marketing channels, enabling marketers to quickly understand, manage, and execute their initiatives with greater efficiency and fewer hurdles.
Role: Product Lead, Design Lead
Project: Web app
Industry: MarTech
initiative builder.
By simplifying the complexity of multi-channel configurations, we reduced friction for users, enabling faster launches and broader adoption of multiple marketing channels. These changes streamlined workflows, cutting launch times by 22%, and improved onboarding efficiency by 30%. Beyond these metrics, the redesign strengthened Integrate’s identity as an intuitive, user-centric platform built to support the diverse needs of modern marketers.
approach.
Identify Everything We Build.
What does our system need to be able to build, from the high-level to the abstract supportive pieces? Each campaign type within a marketing initiative has both shared components and unique needs. What are they?
Catalog, Associate & Categorize Data Points.
Identify all of the data the platform currently handles. Revisit the groupings and associations and normalize the language so that creating different types of initiatives becomes intuitive after learning the first.
Define and Outline the Flows.
How should a user navigate through building an initiative, and how does that builder relate to the larger lead-flow ecosystem?
Power User vs White Glove Experience.
Initially, most of the long-tenured power users with Integrate’s Customer Success team expressed the desire for a UI that would deliver them access to everything at the same time. After sharing early sketches, they began to agree such a UI would become overwhelming.
Alternatively, a linear wizard progression would create unnecessary friction for a power user. The optimal path that seemed to work for experienced and inexperienced users was creating a non-linear stepper pattern that allowed users to move freely while also focusing on the task at hand.
Wizard Ideation.
Rapid exploration of patterns that would allow non-linear navigation with adequate instructional support for newer users of the platform.
Low-fidelity mapping of the data points and functionality required by each section across each initiative source type. Seeking not only a comprehensive outline, but also to identify trends and opportunities for normalization and reuse.
Testing & Validation.
Over three rounds of moderated usability testing with 6-8 participants each, we learned a few notable insights:
outcome.
Nonlinear Progression.
Unintrusive Support.
Progress & Accuracy Indicators.
Consolidated Point-of-Use Configs.
Clear Path to Conflict Resolution.
Localized Analytics.