Sterling Proffer

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.

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

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... See more

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.