1 of 23

OKR & PRODUCT METRICS

Rahmi Syahputri

FSPM Class of July 2022

Team 5 - Amsterdam

2 of 23

hello

I am Amik, from Team 5 Section Amsterdam

This presentation deck is an intermediate assignment from FSPM Class of July 2022 Week 2.

This will help me be able to derive the product metrics and set up events to track the intended metrics.

3 of 23

LIST OF

CONTENT

About Company

01

Product Metrics

02

Event Track

03

4 of 23

about

#SenyamanDiRumah

Kost Coliving:

(product)

Rukita is a coliving housing with comprehensive facilities and services, that will make you feels like home.

Kost coliving is one of the major products that Rukita's offers.

Kost coliving is an upgraded ordinary-kost-life with a modern design, complete facilities, strategic location, and warm-friendly community.

5 of 23

Rukita's Activation Metric

How do visitors turn into users who are enrolled and actively interact with Rukita's products?

Signups

# of Register & Book Kost/Apart

*For the first time

Enrollments

6 of 23

Enrollments

Enrollments is a process when users register in the Rukita application and become one of the Rukees (name of Rukita's member).

If the user has succeeded in becoming a member, then the user can use various features provided by Rukita.

Otherwise, the user can only see the products offered.

This metric will help Rukita to know how many users have enrolled and become a Rukees.

Signups

After completing enrollments, Rukees can access Rukita apps page by signing up to the account that has been registered.

To be able to use the features in Rukita's, the Rukees must first sign up. If not, then the Rukees can only see the products offered.

This metric consists of Rukees who sign up for the first time after enrolling and registered users.

# of Register & Book (1st time)

After registering, Rukees can see various boarding houses offered by Rukita.

Rukees can choose the kost they want, then register & book through the help of Nikita (Rukita's Whatsapp customer service).

This metric shows Rukees who made successful first-time registrations and bookings.

Rukita's Activation Metric

(CONT)

7 of 23

Rukita's Retention Metric

How do convince users to come back repeatedly using Rukita's product?

# of Transaction

*within a month

# of Returning Users

% of Users Churn Rate

*within a month

*within a month

8 of 23

# of Transaction

Transactions are when Rukees have completed the entire registration, booking, and payment process for their new kost.

This metric shows how many transactions occurred in a month.

The more transactions that are made, the closer Rukita is to achieving its goals and it implies that Rukees like and trust Rukita in their experience of searching a kost.

# of Returning Users

This metric shows the number of Rukees who return to the Rukita's apps to make transactions or just look for the kost they want. Those Rukees have already visited before.

A new Rukees can end up getting counted as a returning user as well if the new Rukees returns within the tracking period.

This metric is calculated on a monthly basis.

% of Users Churn Rate

Churn rate is the rate at which Rukees stop doing business with Rukita over a given period of time. Churn may also apply to the number of users who cancel or don’t renew a transaction. The higher Rukita's churn rate, the more Rukees stop making transactions from Rukita.

Rukita's Retention Metric

(CONT)

9 of 23

EVENT TRACK

A way to track exactly what each of Rukees do when using Rukita app.

From the previous slide, we already know the Activation metrics of Rukita Kost Coliving. Next, we'll track the whole complete set of events to get insights of the Activation journey in the future.

*P.S: The event track is based on mobile apps, not website.

10 of 23

KOST COLIVING'S OKR

Objective

Key Results

Make transactions of registering and booking kost in Rukita mobile apps easier for new Rukees.

Achieve new Rukees by 100K in Q3

Increase # of transaction to 2 million night in Q3

11 of 23

USER JOURNEYS & HYPOTHESES

User Journeys

    • Every journey that new Rukees take for enrollment (KR1).
    • The Rukees transaction journey, from searching the kost, look the bedroom, and making a waiting list request or asking by Whatsapp, until the payment success (KR2).

Hypotheses

    • Are there a lot of new users taking a register feature to the Rukita app? Or do they prefer the searching one (Telusuri Unit)?
    • Can the transaction method that Rukita provides (waiting list and ask by Whatsapp) meet the user's booking kost needs?

12 of 23

Event Track (1)

User finished download and open Rukita's app

Triggers when

Homepage

Event name

Source

Properties to track

Daftar/Masuk

Telusuri Unit

Example property value

Event property - String

Data/property type

    • Intent: User download the app and opens it
    • Success: The Rukita app successfully opened and so the homepage
    • Failure: The app error or stuck or suddenly closed.

Description

Typical Subtypes of Events

This property will tell us when user opens the app on their phone.

13 of 23

Event Track (2)

User select/clicks the "daftar/masuk" icon.

Triggers when

Signup Selected

Event name

Source

Properties to track

Phone number

Selanjutnya

Masuk

Syarat & Ketentuan

Kebijakan Privasi

Hubungi CS Rukita

Example property value

People property - Numeric

Event property - String

Data/property type

    • Intent: User clicks the "daftar/masuk" icon
    • Success: The signup page successfully opened
    • Failure: The app's error or stuck or it suddenly closed.

Description

Typical Subtypes of Events

This property will tell us when user clicked "daftar/masuk" on homepage.

14 of 23

Event Track (3)

User input the phone number and click next

Triggers when

Phone Number Confirmed

Event name

Source

Properties to track

    • Ya, benar
    • Ubah nomor

Example property value

Event property - String

Data/property type

    • Intent: User inputs phone number and clicks next
    • Success: The user's phone number successfully confirmed
    • Failure: The user's phone number is wrong, or the phone number is already registered.

Description

Typical Subtypes of Events

This property will tell us when user clicked "selanjutnya" on the previous page.

15 of 23

Event Track (4)

User click "Ya, benar"

Triggers when

OTP Code Inputed

Event name

Source

Properties to track

Kirim ulang

1234

Example property value

    • People property - Numeric
    • Event property - String

Data/property type

Description

    • Intent: User clicks "Ya, benar" .
    • Success: The OTP code is successfully input.
    • Failure: The OTP code is wrong, or user don't get the OTP code.

Typical Subtypes of Events

This property will tell us when the user clicked "Ya, benar" on the previous page.

16 of 23

Event Track (5)

User clicks resent the OTP code

Triggers when

OTP Code Resented

Event name

Source

Properties to track

OK

Example property value

People property - String

Data/property type

    • Intent: User clicks "kirim ulang" icon.
    • Success: The user successfully gets the OTP code.
    • Failure: User doesn't get the OTP code, or the app's error or stuck or suddenly close.

Description

Typical Subtypes of Events

This property will tell us when the user clicked "kirim ulang" icon on the previous page.

17 of 23

Event Track (6)

User success input the OTP code and the complete data page open

Triggers when

Sign Up Data Completed

Event name

Source

Properties to track

Rahmi Syahputri

syhptrrhm1@gmail.com

Avadakedavra1

Example property value

People property - String

Data/property type

    • Intent: User success input the OTP code & the complete data is open
    • Success: The user successfully completes the data.
    • Failure: The password is not correct (missing one of the rules/t&c), the email is wrong (format), or the email is already registered.

Description

Rahmi Syahputri

syhptrrhm1@gmail.com

Avadakedavra1

Typical Subtypes of Events

This property will tell us when the user clicked "OK" icon on the previous page and user successfully input the OTP code.

18 of 23

Event Track (7)

User complete the data and click "simpan". User lands on the homepage by default.

Triggers when

Homepage

Event name

Source

Properties to track

    • Mau ngekost di daerah mana?
    • Lihat semua kost di Jakarta Selatan
    • Jakarta Selatan, Jakarta Barat, Jakarta Pusat, Depok, dll.
    • Footer button (Explore, MyHome, Community, Notifikasi, Akun)

Example property value

    • Event property - String
    • Event property - Numeric
    • Event property - Boolean

Data/property type

    • Intent: User click "simpan" icon & the homepage open.
    • Success: User successfully landed on the homepage.
    • Failure: User can't open the homepage, the app's error or stuck or suddenly close.

Description

Typical Subtypes of Events

This property will tell us when the user clicked "simpan" icon on the previous page after filled the form and user successfully landing to the homepage.

19 of 23

Event Track (8)

User choose kost from the listing on the homepage

Triggers when

Specific kost clicked

Event name

Source

Properties to track

    • Lihat Galeri
    • Saya Tertarik
    • Tanya di WA
    • Fasilitas, Kamar, Lokasi, Tata Tertib.

Example property value

    • Event property - String
    • Event property - Numeric
    • Event property - Boolean

Data/property type

    • Intent: User click/choose specific "kost listing" icon.
    • Success: User successfully opens the kost listing homepage.
    • Failure: The app's error, or stuck or suddenly close.

Description

Typical Subtypes of Events

This property will tell us when the user clicked specific "kost listing" icon on the previous page after searching the kost.

20 of 23

Event Track (9)

User click "Saya Tertarik" icon on the previous page.

Triggers when

Saya Tertarik Clicked

Event name

Source

Properties to track

    • Gunakan kontak profil saya
    • Punya kode referal?
    • Kabari Saya Jika Kamar Tersedia
    • Whatsapp

Example property value

Data/property type

    • Intent: User clicked "Saya Tertarik" icon.
    • Success: User successfully filled the form.
    • Failure: User failed to filled the form, or the app's error or stuck or suddenly close.

Description

Typical Subtypes of Events

This property will tell us when the user clicked "Saya Tertarik" icon on the previous page.

    • Event property - String
    • Event property - Boolean

21 of 23

Event Track (10)

User click "Kabari Saya Jika Kamar Tersedia" on the previous page.

Triggers when

Kabari Saya Jika Kamar Tersedia clicked

Event name

Source

Properties to track

    • Lihat Riwayat Pesanan
    • Cari Coliving Lainnya

Example property value

Data/property type

    • Intent:User click "Kabari Saya Jika Kamar Tersedia" icon.
    • Success: User successfully booked the kost.
    • Failure: The app's error, or stuck or suddenly close, so user failed to booked the kost.

Description

Typical Subtypes of Events

This property will tell us when the user clicked "Kabari Saya Jika Kamar Tersedia" icon on the previous page.

Event property - String

22 of 23

Event Track (11)

User click "Tanya di WA" on the previous specific kost listed page.

Triggers when

Tanya di WA clicked

Event name

Source

Properties to track

Halo, Nikita Saya melihat unit ..... dan tertarik dengan kamar .... Boleh tanya lebih lanjut?" (Template greeting message from Rukita's Whatsapp)

Example property value

Event property - String

Data/property type

    • Intent: User User click "Tanya di WA" on the previous specific kost listed page.
    • Success: User successfully booked the kost via Rukita's Whatsapp
    • Failure: The linked is error, or stuck, or suddenly close so user failed to booked the kost via Rukita's Whatsapp

Description

Typical Subtypes of Events

This property will tell us when the user clicked "Tanya di WA" icon on the previous specific kost listed page.

23 of 23

thank you

syhptrrhm1@gmail.com

EMAIL

+62-821-7007-2737

MOBILE

linkedin.com/in/rahmi-syahputri

LINKEDIN