The Adjacent User Theory

Adjacent User Theory demands an entirely different approach to being ‘user centric’. Static personas are OUT. Dynamic evolving personas that incorporate product adoption behavior are the standard to strive for. Every 3-6 months during hyper growth, you have to reorient your team around the next adjacent user, what they care about, and what problems... See more

The second technique is to watch the adjacent user using your product through usability tests. Ideally this is done with trained researchers when possible. Watch the adjacent user try to sign up, activate, see what they struggle on, have them talk about why they are having challenges and what their expectations of the experience are.

You need to force the team to be the adjacent user by experiencing the product in the conditions and settings that the adjacent user is experiencing. This is commonly referred to as dog-fooding. This starts by making sure the team is constantly experiencing new user flows, empty states, and product states that require a certain amount of usage befo... See more

Once you have hypotheses for who is successful and why they are successful, you can hypothesize possible adjacent users segments. This will involve changing one or more of the vectors that you identified.

To understand your adjacent users, it is helpful to understand the attributes of who is successful today and why they are successful. The reason this is helpful is that your adjacent user is different on one or more of these attributes (but not all). These attributes create vectors of expansion.

Until you recognize that they are adjacent users and commit to helping them, they will remain adjacent. They aren’t going to get there on their own. You have to be passionate about them and learn to view the product from their eyes. If you don’t focus on them, growth slows and your cohorts decay.

Solving for your adjacent user is not short term thinking; it is this disciplined sequential execution that will enable your longer-term roadmap and faster growth.

Product teams overvalue hitting home runs vs hitting 100 singles back to back. This leads them to take bigger swings by going after bigger markets of new users. They get bogged down by trying to establish product-market fit for a new set of users and never fulfill the potential of their current product-market fit.

Product teams by nature are power users of their own product. The parts of the product that the product team uses, tend to automatically get improved as the pain is right in front of them. But this leads to building for yourself (or your friends). While that can feed the ego, if you are only building for yourself or power users, you won’t grow. You... See more