Gamification of the Platform - Catalyst POC

[ProfilaMitchell]

Table of Contents

• Housekeeping
• The Problem
• User Story
• Request Type A/B
• Request Category Feature/Capability
• Owner
• Summary
• Is This Really Necessary?
• Motivation
• Named concepts
• Examples, Risks & Assumptions
• Success Metrics
• Conceptual Design
• Requirements
• Drawbacks
• Alternatives
• New Data
• Business Release Date

Housekeeping

Make sure to clearly understand Type-A and Type-B requests, and the relevant limitations. Failing to follow the guidelines pertaining to the two acceptable types of RFWs will automatically lead to disqualification of the RFW.

Take time to complete each section below with as much detail as is required to establish a comprehensive understanding about the underlying product specification.

ALL BELOW FIELDS ARE REQUIRED

The Problem

There are currently no mechanics in place to receive ZEKE for actions taken on the platform

User Story

As a user, I want to receive ZEKE for certain actions that are taken on the platform so that I can view my progress and develop a sense of reward and investment in Profila.

Request Type A/B

Type A

Incentivising Profile building through quiz completion using ZEKE
Incentivising Brand interaction through use of ZEKE

Request Category Feature/Capability

Feature

Owner

Mitchell Goudie

Summary

Basic implementation of the gamification system is being introduced. This system described here is the minimum required here in order to close out two of our Catalyst proposals. Scope of this request:

• UI required for user to complete a quiz
• UI required for user to interact with a brand moment
• UI triggered when ZEKE is awarded
• Logic for triggering the awarding of ZEKE
• The mechanism for sending ZEKE to a user's wallet *

Is This Really Necessary?

Yes

Motivation

This is being developed to have the core foundation of the gamification logic of the Platform.

Named Concepts

N/A

Examples, Risks & Assumptions

1. Explain concretely what will manifest as a result of this RFW.

• Flow for users to complete a quiz and be rewarded with ZEKE
• Flow for users to interact with a brand moment and be rewarded with ZEKE
• Implementation of ZEKE being transferred to a user
• User will have a 'Profila level' which is indicative of the XP they have received
   

2. Explain how is it different from what is already manifesting i.e. what we already have?

N/A
 

3. Explain what Profila users/brands will experience as a result of this RFW. How will they feel as a result of it? How will they benefit as a result of it?

Individuals

• A way to be rewarded with ZEKE for completing category quizzes on various topics
• A way to be rewarded with ZEKE for authentically engaging with brand moments
   

4. If applicable, provide sample messages for any new messages the system will display as a result of this RFW.

See conceptual design section
 

5. Define what is out of scope in this request.

N/A
 

6. What are the data protection, privacy and security assumptions made for this request (example, should this be GDPR, HIPPA (healthcare), NIST compliant etc. - Speak to Michiel or Ipek!)

N/A
 

7. Explain how this user story will be supported (i.e customer support - if the user story fails technically, how will the user be supported).

N/A
 

8. Explain how this user story impacts revenue or billing (if applicable).

• Sending ZEKE to a wallet incurs two costs
  • The amount of ZEKE sent
  • The transaction cost
     

9. State any additional risks identified as a result of this user story.

N/A
 

Success Metrics

• User receives ZEKE for completing a quiz
• User receives ZEKE for carrying out specific interactions with a brand moment
• User has an XP counter as part of their Profila, which shows their Profila level

Conceptual Design

This RFW describes two flows for which the individual receives ZEKE. One for completing a quiz, the other for interacting with a brand moment. This RFW also describes the mechanics of levelling required.

Flow 1: Quiz completion

1. Go to UI where category of quiz is selected
2. Select the quiz " "
3. Complete the quiz
4. Once quiz is complete, show UI of XP points being received by the user
5. These points will be sufficient for the user to 'level up'

• User is originally at level 1
• After completion of the quiz, the XP bar completes and they become level 2
• The XP bar becomes empty again

7. The user will receive 2 ZEKE for reaching the next level

This demonstrates the use case of ZEKE as a form of XP for profile building

Flow 2: Brand moment interaction

1. Go to main feed UI (spotlight/brand moment feed) where the user can interact with brand content
2. User sees a preloaded moment from Funky Fashionista
3. The user provides the following interactions

• Clicks the reaction/emoji, and selects the emoji with heart eyes
• Clicks the link provided in the moment (opens in separate tab_
  • This link doesn't have to lead to a real page

4. For each action the user takes, the XP bar in the top right navigation fills up slightly (for the purpose of this demonstration, 50%)
5. After the user carries out step 3, the bar becomes full and the user levels up to level 3
6. UI is shown demonstrating this level up
7. UI shown awarding the user with 2 ZEKE

This further demonstrates the use case of ZEKE as a way to increase interaction with brand content

Levelling Logic

Within the flows above (carried out in order), the user will progress from level one to level three. For the purpose of this POC, we can define this in terms of XP earned per action for just these three levels.

XP Per Action
Completion of a quiz = 1 XP
Interaction with brand moment = 1XP

XP Per level
Level 1 - Level 2 = 1XP
Level 2 - Level 3 = 2XP

Given the actions described in the flow above, level 3 is achieved. The award for completion of each level is 2 ZEKE for the purpose of this POC.

Requirements

There needs to be a real transfer of ZEKE from one wallet to another, to indicate that the user is being rewarded.

Drawbacks

Alternatives

New Data

The users level
The amount of XP the user has in total
The number of actions the user has taken

Business release date

N/A