↙ Back to the poem
thenovbook
01 / 09VI

Gamification · Code Crush

A story behind the poem

Toyota

Requirements gathering, testing and reporting for the Toyota project

I supported Code Crush’s Project Manager on Hành trình vạn dặm xanh, helping clarify requirements, test game updates and check reports.

Hành trình vạn dặm xanh · Campaign artwork.
Hành trình vạn dặm xanh · Campaign artwork. Tuổi Trẻ Online / DNCC ↗
01

Project context and my role at Code Crush

Hành trình vạn dặm xanh is a gamification experience accessed through the Toyota Vietnam app. Players submit photos of their vehicle’s instrument display to record data, share results and participate in a community leaderboard.

I supported the PM in working with lead agency Digimind, recording meeting notes and implementation requirements. I also took part in testing, reporting and supporting operations after the game launched.

  • Brand: Toyota
  • Lead agency: Digimind
  • Implementation partner: Code Crush
  • My role: Business Development & Account Intern, supporting the PM
02

Photo submission requirements and result processing

The experience connects the interface, image reading, result notifications, prize-eligibility criteria and reporting data. A change to one step can mean that related parts need to be checked again.

The image-submission flow needs to distinguish complete data, missing values and invalid images. I helped compile feedback, clarify requirements and follow up on points needing confirmation.

Hành trình vạn dặm xanh · Campaign poster.
Hành trình vạn dặm xanh · Campaign poster. Toyota Phú Thọ ↗
03

Experience testing and issue tracking

“Updated” was my cue to check again.

I compared the approved interface with the test version and live game. I checked the wording of result, ranking and prize messages, then the conditions that made each message appear.

I brought feedback together, tried the player journeys and followed up with the technical team. After an update, I checked the relevant parts again and noted anything that still needed attention.

When image processing slowed or timed out, I helped document the issue, pass on information and follow up. The technical team investigated the causes and made the technical changes.

04

Report checks and definitions of participation metrics

The reports distinguished photo submissions, accounts, approved results and people listed on the leaderboard. I checked these definitions when reading the data.

I helped compile and cross-check the data and clarify the scope and reporting cut-off. The reports tracked six steps:

  1. 01Entered game
  2. 02Signed up / started playing
  3. 03Took an ODO photo
  4. 04Submitted result
  5. 05Approved
  6. 06Appeared on leaderboard
Six stages of participation tracked in the reports.

Fuel savings, estimated CO₂ emission reductions and the equivalent number of trees are metrics derived through conversions. The equivalent number of trees does not represent trees that have actually been planted.

05

Lessons from project coordination and reporting

I learned to ask what a number counted before saying what it meant.
  • Link each task to the agreed requirement, version and next step.
  • Understand the gameplay flow to ask focused questions.
  • Check the content alongside the data and display conditions.
  • Confirm the metric and reporting period before drawing a conclusion.

The letter goes on.

Back to the poem.
10 THINGS I HATE ABOUT MARKETINGkhoianluong@gmail.com ↗

NEXT PROJECTMODOLL ↗