To Ignite a Personalization Practice, Run this Prepersonalization Workshop

Image this. You’ve joined a club at your business that’s designing innovative product features with an focus on technology or AI. Or perhaps your business only started using a personalization website. Either way, you’re designing with information. What then? When it comes to designing for personalization, there are many warning stories, no immediately achievement, and some guidelines for the baffled.

The personalization gap is real, between the dream of getting it right and the worry of it going wrong ( like when we encounter “persofails” similar to a company’s constant plea to regular people to purchase additional bathroom seats ). It’s an particularly confusing place to be a modern professional without a map, a map, or a strategy.

There are no Lonely Planet and some tour guides for those of you who want to personalize because powerful personalization depends so much on each group’s talent, technology, and market position.

But you can ensure that your group has packed its bags rationally.

There’s a DIY method to increase your chances for victory. You’ll at least at least disarm your boss ‘ irrational exuberance. Before the group you’ll need to properly plan.

It’s known as prepersonalization.

Behind the song

Take into account Spotify’s DJ feature, which was introduced last season.

We’re used to seeing the polished final outcome of a personalization have. A personal have had to be developed, budgeted, and given priority before the year-end prize, the making-of-backstory, or the behind-the-scenes success chest. Before any customisation have goes live in your product or service, it lives amid a delay of valuable ideas for expressing consumer experiences more automatically.

How do you decide where to position customisation wagers? How do you design regular interactions that hasn’t journey up users or—worse—breed mistrust? We’ve discovered that several budgeted programs second required one or more workshops to join key stakeholders and domestic customers of the technology in order to justify their continuing investments. Make it matter.

We’ve closely observed the same evolution with our consumers, from major software to young companies. In our experience with working on small and large personalization work, a program’s best monitor record—and its capacity to weather tough questions, work steadily toward shared answers, and manage its design and engineering efforts—turns on how successfully these prepersonalization activities play out.

Effective workshops consistently save time, money, and overall well-being by separating successful future endeavors from unsuccessful ones.

A personalization practice involves a multiyear effort of testing and feature development. It’s not a tech stack switch-flip. It’s best managed as a backlog that often evolves through three steps:

1. customer experience optimization ( CXO, also known as A/B testing or experimentation )
2. always-on automations ( whether rules-based or machine-generated )
3. mature features or standalone product development ( like Spotify’s DJ experience )?

This is why we created our progressive personalization framework and why we’re field-testing an accompanying deck of cards: we believe that there’s a base grammar, a set of “nouns and verbs” that your organization can use to design experiences that are customized, personalized, or automated. These cards are not necessary for you. But we strongly recommend that you create something similar, whether that might be digital or physical.

Set the timer for your kitchen.

How long does it take to cook up a prepersonalization workshop? The activities we suggest including during the assessment can ( and frequently do ) last for weeks. For the core workshop, we recommend aiming for two to three days. Details on the essential first-day activities are included in a summary of our broad approach.

The full arc of the wider workshop is threefold:

Kickstart: This specifies the terms of engagement as you concentrate on both the potential and the team’s and leadership’s readiness and drive.
1. Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.
2. Work your plan: This stage consists of making it possible for team members to individually pitch their own pilots that each include a proof-of-concept project, business case, and operating model.

Give yourself at least a day, split into two large time blocks, to power through a concentrated version of those first two phases.

Kickstart: Apt your appetite

We call the first lesson the “landscape of connected experience“. It looks at the possibilities for personalization in your company. A connected experience, in our parlance, is any UX requiring the orchestration of multiple systems of record on the backend. This might be a marketing-automation platform combined with a content-management system. It could be a digital-asset manager combined with a customer-data platform.

Create a conversation by mentioning consumer and business-to-business examples of connected experience interactions that you admire, find familiar, or even dislike. This should cover a representative range of personalization patterns, including automated app-based interactions ( such as onboarding sequences or wizards ), notifications, and recommenders. We have a list of these in the cards. Here’s a list of 142 different interactions to jog your thinking.

The table must be set up for this. What are the possible paths for the practice in your organization? Here’s a long-form primer and a strategic framework for a broader view.

Assess each example that you discuss for its complexity and the level of effort that you estimate that it would take for your team to deliver that feature ( or something similar ). In our cards, we break down connected experiences into five categories: functions, features, experiences, complete products, and portfolios. Size your own build here. This will help to draw attention to both the benefits of ongoing investment and the difference between what you currently offer and what you intend to deliver in the future.

Next, have your team plot each idea on the following 2×2 grid, which lays out the four enduring arguments for a personalized experience. This is crucial because it emphasizes how personalization can affect your own ways of working as well as your external customers. It’s also a reminder ( which is why we used the word argument earlier ) of the broader effort beyond these tactical interventions.

Each team member should decide where they would like to place your company’s emphasis on your product or service. Naturally, you can’t prioritize all of them. Here, the goal is to show how various departments may view their own benefits from the effort, which can vary from one department to the next. Documenting your desired outcomes lets you know how the team internally aligns across representatives from different departments or functional areas.

The third and final KickStart activity is about filling in the personalization gap. Is your customer journey well documented? Will ensuring data and privacy is a major challenge too much? Do you have content metadata needs that you have to address? ( We’re pretty sure you do; it’s just a matter of recognizing the need’s magnitude and its solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six protracted behavior that is harmful to the development of our country.

Effectively collaborating and managing expectations is critical to your success. Consider the potential obstacles to your progress in the future. Press the participants to name specific steps to overcome or mitigate those barriers in your organization. According to research, personalization initiatives face a number of common obstacles.

At this point, you’ve hopefully discussed sample interactions, emphasized a key area of benefit, and flagged key gaps? You’re all set to go on, good.

Hit that test kitchen

Next, let’s take a look at what you’ll need to create personalization recipes. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. They give you a variety of options for how your organization can conduct its activities because of their broad and potent capabilities. This presents the question: Where do you begin when you’re configuring a connected experience?

The key here is to avoid treating the installed software ( as one of our client executives humorously put it ) like some sort of dream kitchen. These software engines are more like test kitchens where your team can begin devising, tasting, and refining the snacks and meals that will become a part of your personalization program’s regularly evolving menu.

Over the course of the workshop, the ultimate menu of the prioritized backlog will come together. And creating “dishes” is the way that you’ll have individual team stakeholders construct personalized interactions that serve their needs or the needs of others.

Recipes have ingredients in them, and those recipes have ingredients.

Verify your ingredients

You’ll ensure that you have everything you need to create your desired interaction ( or that you can determine what needs to be added to your pantry like a good product manager ) and that you have validated with the right stakeholders present. These ingredients include the audience that you’re targeting, content and design elements, the context for the interaction, and your measure for how it’ll come together.

This is not just about identifying needs. Documenting your personalizations as a series of if-then statements lets the team:

1. compare findings to a common method for developing features, similar to how artists paint with the same color palette,
2. specify a consistent set of interactions that users find uniform or familiar,
3. and establish parity between all important performance indicators and performance metrics.

This helps you streamline your designs and your technical efforts while you deliver a shared palette of core motifs of your personalized or automated experience.

Create a recipe.

What ingredients are important to you? Consider a who-what-when-why construct:

• Who are your key audience segments or groups?
• What kind of content will you offer them, what design elements, and under what circumstances?
• And for which business and user benefits?

Five years ago, we created these cards and card categories. We regularly play-test their fit with conference audiences and clients. And we still come across fresh possibilities. But they all follow an underlying who-what-when-why logic.

In the cards in the accompanying photo below, you can typically follow along with right to left in three examples of subscription-based reading apps.

1. Nurture personalization: When a guest or an unknown visitor interacts with a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.
2. Welcome automation: An email is sent when a newly registered user is a subscriber and is able to highlight the breadth of the content catalog.
3. Winback automation: Before their subscription lapses or after a recent failed renewal, a user is sent an email that gives them a promotional offer to suggest that they reconsider renewing or to remind them to renew.

We’ve also found that sometimes this process comes together more effectively by cocreating the recipes themselves, so a good preworkshop activity might be to think about what these cards might be for your organization. Start with a set of blank cards, and begin labeling and grouping them through the design process, eventually distilling them to a refined subset of highly useful candidate cards.

The later stages of the workshop could be characterized as moving from focusing on a cookbook to a more nuanced customer-journey mapping. Individual” cooks” will pitch their recipes to the team, using a common jobs-to-be-done format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.

Architecture must be improved to produce better kitchens.

Simplifying a customer experience is a complicated effort for those who are inside delivering it. Avoid those who make up their mind. With that being said,” Complicated problems can be hard to solve, but they are addressable with rules and recipes“.

When a team overfits: they aren’t designing with their best data, personalization turns into a laughing line. Like a sparse pantry, every organization has metadata debt to go along with its technical debt, and this creates a drag on personalization effectiveness. For instance, your AI’s output quality is in fact impacted by your IA. Spotify’s poster-child prowess today was unfathomable before they acquired a seemingly modest metadata startup that now powers its underlying information architecture.

You can’t stand the heat, in fact…

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach can achieve the necessary concentration and intention. So banish the dream kitchen. Instead, head to the test kitchen to burn off the fantastical ideas that the doers in your organization have in store for time, to preserve job satisfaction and security, and to avoid unnecessary distractions. There are meals to serve and mouths to feed.

You have a better chance of lasting success and sound beginnings with this workshop framework. Wiring up your information layer isn’t an overnight affair. However, if you use the same cookbook and the same recipes, you’ll have solid ground for success. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.

Although there are costs associated with purchasing this type of technology and product design, time well spent on sizing up and confronting your unique situation and digital skills. Don’t squander it. The pudding is the proof, as they say.