Type*:* Growth Test

Date*:* May 2020

Team*:* Product Growth

<aside> ℹ️ Result: A new product feature to build brand awareness

</aside>

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Background The feature was developed as a growth test, to see whether Sweatcoin could tap into social media as a growth mechanism. The initial insight for the design was based on the empirical evidence that multiple users were making screenshots of their tracking screen (where total steps and earnings are shown) and posting them on instagram: in their profile feeds or stories. Social media sharing functionality was aiming to "institutionalise" this through a more formal process of posting one's earnings inside the app.

Fig. 1: Sweatcoin user posting their tracking screen screenshot and writing about their earnings and steps.

Fig. 1: Sweatcoin user posting their tracking screen screenshot and writing about their earnings and steps.

First Wireframes For growth tasks, I prefer to wireframe experiences in Sketch straight away, from existing elements, without drawing the user journey by hand. At Sweatcoin, we usually have a few tests in design at the same time and so speed is of utmost importance. It's also important for growth tests in general too, as they are meant to allow us to get a signal from users and learn quickly.

Fig. 2: The very first wireframe was put together in a few hours. Users had two options: either post their tracking screen without a photo (default version), or use their own photo as the background. Instagram was the main sharing channel for us, as the test was specifically aiming at tapping into Instagram Stories.

Fig. 2: The very first wireframe was put together in a few hours. Users had two options: either post their tracking screen without a photo (default version), or use their own photo as the background. Instagram was the main sharing channel for us, as the test was specifically aiming at tapping into Instagram Stories.

Fig. 3: There were a number of different iterations of the feature.

Fig. 3: There were a number of different iterations of the feature.

Resulting Solution

Fig. 4: Latest iteration of the feature as seen in the app

Fig. 4: Latest iteration of the feature as seen in the app

Future Iterations