My role in the Architect team
I've been working on the Architect as its Product Design Lead and formerly Senior Product Designer since joining Insider in 2021. My main responsibilities include contributing to design of new/improved features, propelling UX research, intermediation, and contributing to product decisions.
Meet the Architect
The Architect is known as the most versatile journey builder in the global market (#1 as per G2 Rankings, IDC Marketscape & Gartner Report) as it encompasses the capabilities of of utilising every cross-channel operation for all possible marketing scenarios. It enables marketers to engage with the customers by allowing them to creating journeys for all the scenarios they might ever need to cover.
In order to preserve confidentiality, I'll only be sharing the promotion material published by Insider in order to convey the type, capabilities, and scope of the product as you might find below.
As taken from Useinsider.com: "We designed Architect based on a collective of needs: those of the users, those of the marketers and those of the brands. We looked up to our partners and heard their feedbacks with care; we aligned our in-house data experts to understand the singular needs of the eighteen regions we’re currently settled.
Architect speaks to a global market, it stands for personalized, contextual and in-time communication, all of that while helping marketers achieve their most challenging KPIs. With it, building the perfect journey has become a reality and the approach is rather easy to understand. Every journey has four main components..."
"...The Trigger: Making the user part of a journey.
Architect decides when a user should be part of a journey according to their behavior, like viewing a certain product, abandoning a shopping cart, purchasing a product, and more.
The Channel: Communicating with the user
Deciding which channel to use to communicate with your users is critical to the success of your journey. Architect provides an ever growing list of channels that include Web push, Email and Ads for now.
The Flow: Keeping the user within the journey
Architect waits for either for a certain predefined time or for the user to take a specific action that is custom to each journey. Based on the outcome of this action it decides to either keep or remove a user from the journey. The action could be viewing an email or opening a push notification, for example.
The Exit: Finishing a journey
When does the user finally finish a journey? When they have either reached the goal of the journey, for example buying a product or when you have communicated enough but don’t see a chance to recover their attention any longer.
Since a picture (sometimes) is worth a thousand words, let’s see how these stages unfold in different contexts and for different industries."