This document provides a concise overview of a voluntary, rapid product initiative. It's designed to swiftly align all stakeholders, laying out our objectives, timelines, and key deliverables for a quick turnaround. This feature was fully executed in just 3 weeks before Christmas 2019.

A document of this length is obviously not suitable for all efforts. This project was purely voluntary, and so a large part of the document was focused on getting people to sign up.

Our typical PRD for roadmap projects is a more robust single source of truth throughout the project.

We were optimizing for delight with this project, both for users and for our team. We ended up creating these for ~150 customers, and at least 30 of them reached out and wrote to us about how much they appreciated it!

We deprioritized this because it lacked the interactivity that we wanted.

Voluntary work happens quite often at MindTickle. Currently, AI is causing many developers to volunteer for different projects.

Ninad Phadke

Here’s how I aligned a team of stakeholders for a voluntary end-of-year feature project that delighted our users.


Pull data on people’s activities in the MindTickle platform and showcase them in the best way possible to them directly.




Mainly because it would be fun and awesome.
But since we need “more logical reasons”

Celebrate people’s achievements in the MT Platform

Make them feel good about themselves and therefore indirectly about MindTickle

Not sure if we can do it for all sites (we’ll have to see if some customers might object)

We have to identify the right set of users

Do we have enough eligible users with enough activities to make this worthwhile?

 - Create a beautiful template that can be filled with personalized data and send that to everyone

 - Leverage the stories format used by Snap, FB and Spotify too to make it a richer experience.

For learners, admins or both? - PM
Decision - For admins. Safer, more acceptable to customers + MT

How to classify users/companies into eligible and not eligible? - PM + Engg

Decision - Active Customer Sites Only - Get this list from Product Analytics

What to highlight and how much conditionality to put on that? - All
See below

What representation to choose? - Engg + Design
Decision - Story Cards

For learners, do we take permission from admins?

If stories, do we allow them to save/share it?
Decision - Let’s try to make it socially shareable (Twitter/LinkedIn)

If stories then do we show it in the mobile app?
Decision - Not relevant if admin is the only interface

Do we bother with sanity/safety stuff like rigorous QA, analytics etc?
Decision - Take basic feedback (Good/bad) and do basic data sanity


Until this is in a stable/good enough stage, this is off-the-books in the sense that 

 No one should complain that we are ignoring our work to do this. Do it after-hours, on weekends.

Treat this like a hackathon project. Should be doable in 10 days.



Rapid Project One-Pager at MindTickle

MT Wrapped 2019

Sign up to see more