To understand the positioning of a company, we must begin by determining what the product is, who the product is intended for, and how that product is to be used. For this week’s assignment, I continue to look at the photo-sharing service, Trover. Trover describes its service stating: “Take an instant adventure: Join savvy explorers who love to find and share hidden gems.”
What? I previously posted about Trover, and continue my research into their services and offerings by examining their positioning in the mobile photo sharing space. Trover offers mobile applications for both android and ios to view and provide content, and a viewing-only platform online. Trovers main focus is about users, from around the world, providing content to their online database of photos (with small descriptive captions). The content on Trover is mostly of landscapes and architecture, although food dishes and wildlife are also prevalent in the content.
Who? Ultimately, this positioning helps differentiate Trover from their competitors like Instagram. Trover is about finding those “hidden” items in your life, whether a place or a dish you have savored, and sharing them with others, either to not-so-secretly elicit feelings of jealousy and seek validation or happiness from friends. They call their users “explorers”, which will help people feel like there are contributing to a larger “map” or “treasure trove” of content. This utilization helps create more content and helps users stick to the site, two crucial elements of success for both positioning and long-term viability.
How? While their positioning makes them effective toward users who want to add content to a larger database, rather than just share their content with “friends” and “followers”, Trover could be more effective by elaborating on the “How” of their positioning. Currently, their product is for explorers who want to take an adventure through semi-curated content. However, what is the benefit from building a treasure trove? That much is not readily clear from their site. Nonetheless, perhaps the benefit, or the “How” might be different for each user, thus negating a need to outline a specific “How” and leaving that task to their users at hand.