Building the Feedback Engine Behind Onboard's Features
Launched and managed a community of product testers who validated new features before they ever reached the public
Emmanuel Onoja, Onboard Test Pilot
We had just launched Onboard 3.0 a few months back and we were optimising our product to be the best. Every new feature we shipped needed real users to break it, question it and tell us what wasn't working, before it reached the public. Without that, we were just guessing
02 · Our Approach
We turned testers into co-builders
We built a community of verified product testers who got early access to new features and gave honest, structured feedback and raw ideas
What I Did
- Launched and managed Onboard Test Pilots, a private community of verified remote workers and users testing new features before launch
- Managed the structure for how testers accessed new features, submitted feedback and flagged issues
- Worked directly with product and engineering teams to translate feedback into actionable fixes and improvements
- Built ongoing engagement within the community, keeping testers active and invested beyond a new test cycle
- Recognised and highlighted standout contributors within the community, turning testing into a two-way relationship, not just a feedback group
03 · Results
Smooth user experience and battle-tested features for Onboard users
Before a feature reached the public, it had already been tested, roasted and improved by real users
04 · Wins
Some testers went on to get hired
Some of our testers didn’t just help us build. They built their own careers along the way.
Chat screenshots from the Onboard Test Pilots community
05 · Credits
Who made this happen
- Marketing AssociateIfeoluwa Taiwo
- CEO (now Chairman)Yele Bademosi
- Product ManagerPaul Oladimeji
- Dev Squad3 Engineers
- CommunityTest Pilots
