To Ignite a Personalization Practice, Run this Prepersonalization Workshop

This is in the photo. 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. In any case, you’re designing using files. Then what? There are many warning tales, over successes, and several personalization design books for the perplexed.

The personalization space is real, between the dream of getting it right and the fear of it going wrong ( like when we encounter “persofails” in the spirit of a company that regularly asks regular people to buy more toilet 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 customisation is so dependent on each group’s talent, technology, and market position.

However, you can make sure your team has properly packed its carriers.

There’s a DIY method to increase your chances for achievement. You’ll at least at least disarm your boss ‘ irrational exuberance. You’ll need to properly plan before the celebration.

We call it prepersonalization.

Behind the song

Take into account Spotify’s DJ element, which was introduced last month.

We’re used to seeing the polished final outcome of a personalization function. A personal have had to be conceived, budgeted, and prioritized before the year-end prize, the making-of-backstory, or the behind-the-scenes success chest. A delay of thought-provoking tips to enhance customer experiences is present before any personalization function is implemented in your product or service.

So how do you understand where to position your personalization bet? How can you create regular interactions that hasn’t irritate users or worse, breed trust? We’ve found that for many well-known budgeted programs to support their continued investments, they initially required one or more workshops to join vital technologies users and stakeholders. Make it count.

We’ve closely monitored the same evolution with our consumers, from major software to young companies. How effective these prepersonalization actions play out, in our experiences working on small and large customisation efforts, and how effective is the program’s supreme track record and its ability to weather challenging questions, work steadily toward shared answers, and manage its design and engineering efforts.

Time and again, we’ve seen successful workshops individual coming success stories from fruitless efforts, saving many time, resources, and social well-being in the process.

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

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

We think there is a base grammar, a set of “nouns and verbs” that your organization can use to create experiences that are personalized, personalized, or automated, which is why we created our progressive personalization framework and why we’re field-testing an accompanying deck of cards. 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 the kitchen.

How long does it take to prepare a workshop on prepersonalization? The surrounding assessment activities that we recommend including can ( and often do ) span weeks. We suggest aiming for two to three days for the core workshop. Here are a summary of our broad approach and information on the most crucial first-day activities.

The full arc of the wider workshop is threefold:

Plan your work: This is where the card-based workshop activities take place, giving you a work plan and the work scope.
Work your plan: This phase is all about creating a competitive environment for team participants to individually pitch their own pilots that each contain a proof-of-concept project, its business case, and its operating model.

Give yourself at least a day, divided into two long time blocks, to work through a concentrated version of those initial 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. Any UX that necessitates the orchestration of multiple systems of record on the backend is a connected experience, in our opinion. This could be a content-management system combined with a marketing-automation platform. A customer-data platform and a digital asset manager could be combined.

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. To jog your mind, here is a list of 142 different interactions.

This is all about setting the table. What are the potential paths the practice could take 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 ). We break down connected experiences into five categories in our cards: functions, features, experiences, complete products, and portfolios. Here, you can size your own build. This will help to focus the conversation on the merits of ongoing investment as well as the gap between what you deliver today and what you want to deliver in the future.

The following 2 2 grid, which lists the four enduring justifications for a personalized experience, should be used as the starting point for each idea. This is crucial because it emphasizes how personalization can affect your own methods 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 vote on where they see your product or service putting its emphasis. You can’t give them all a priority, of course. Here, the goal is to demonstrate how various departments may view their own advantages over the effort, which can be different 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 the customer journey well documented in your business? Will data and privacy compliance be too big of a challenge? Do you have any needs for content metadata that you must address? It’s just a matter of acknowledging the magnitude of that need and finding a solution ( we’re fairly certain that you do ). In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable behaviors that prevent progress.

Your success depends on collaborating effectively and managing expectations. Consider the potential barriers to your future progress. Ask the participants to list specific actions you can take to help your organization overcome or reduce those obstacles. According to research, personalization initiatives face a number of common obstacles.

You should have, at this point, discussed sample interactions, emphasized a significant benefit, and identified significant gaps. Good—you’re ready to continue.

Hit the 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. Their capabilities are broad and potent, and they give you a variety of ways to organize your company. When creating a connected experience, where do you start?

What’s important here is to avoid treating the installed software like it were a dream kitchen from some fantasy remodeling project ( as one of our client executives memorably put it ). These software engines are more like test kitchens where your team can begin creating, testing, and improving the snacks and meals that will be a part of your personalizedization program’s constantly evolving menu.

Over the course of the workshop, the final menu of the prioritized backlog will be created. And by creating “dishes,” you can expect individual team members to create personalized interactions that either serve their or others ‘ needs.

The dishes will come from recipes, and those recipes have set ingredients.

Verify your ingredients

Like a good product manager, you’ll make sure you have everything you need to make your desired interaction ( or that you can figure out what needs to be added to your pantry ) and that you validate with the right stakeholders present. These elements include the audience you’re targeting, content and design elements, the interaction’s context, and your idea of how it’ll come together.

This isn’t just about discovering requirements. The team can: Describe your personalizations as a series of if-then statements by documenting them as follows:

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

As a result, you can deliver a common palette of the main themes of your personalized or automated experience while reducing the number of technical efforts required.

Compose your recipe

What elements are significant to you? Consider a who-what-when-why construct:

Who are your key audience segments or groups?
What content, what design elements, and under what circumstances will you give them?
And for what business and user advantages?

We first developed these cards and card categories five years ago. We regularly test their suitability with clients and audience members at conferences. 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.

When a visitor or an unidentified visitor interacts with a product title, a banner or alert bar appears that makes it simpler for them to read a related title, saving them time.
Welcome automation: When there’s a newly registered user, an email is generated to call out the breadth of the content catalog and to make them a happier subscriber.
Winback automation: A user receives an email before their subscription expires or after a recent failed renewal to request that they reconsider or remind them to do so.

We’ve also found that cocreating the recipes themselves can sometimes be the most effective way to start brainstorming 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 standard jobs-to-be-done format to ensure consistency and outcomes, and from there, the resulting collection will be prioritized for finished design and production delivery.

Better kitchens require better architecture

For those who are inside delivering it, simplifying a customer experience is a challenging task. 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. Every organization has metadata debt to go along with its technical debt, which contributes to a drag on the effectiveness of personalization, much like a sparse pantry. Your AI’s output quality, for example, is indeed limited by your IA. Prior to their acquisition of a seemingly modest metadata startup that now powers the underlying information architecture, Spotify’s poster-child prowess today was beyond comprehension.

You can’t stand the heat, unquestionably…

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a deliberate and cooperative approach will produce the desired outcome. Banish the ideal kitchen in all its glory. Instead, hit the test kitchen to save time, preserve job satisfaction and security, and safely dispense with the fanciful ideas that originate upstairs of the doers in your organization. Both food and mouths must be fed.

This organizational framework gives you a fighting chance at long-term success as well as solid ground. 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 created these activities to ensure that your organization’s needs are clear and concise before the risks start to accumulate.

While there are associated costs toward investing in this kind of technology and product design, your ability to size up and confront your unique situation and your digital capabilities is time well spent. Don’t waste it. The pudding is the proof, as they say.