HR Dashboard
Register Hire
Pit Crew
Tasks Template
Hiree Dashboard
Hiree Progress

🏆 Onboarding Grand Prix

Inspiration

We've all been there — Day 1 at a new job, drowning in a sea of emails, scattered documents, and that dreaded spreadsheet with 50 tasks nobody explains. Studies show 88% of organizations don't onboard well, and new hires complete only 54% of their onboarding tasks on average.

We asked ourselves: What if onboarding felt less like paperwork and more like a game?

The racing metaphor clicked instantly. Every new hire is on a journey — a race to become a fully productive team member. They need a pit crew (IT, HR, Finance) supporting them. They want to see progress, earn achievements, and cross that finish line feeling like a champion.

That's how Onboarding Grand Prix was born.

What it does

Onboarding Grand Prix transforms the traditional new hire experience into an engaging "race to Day 1" — built natively inside Atlassian's ecosystem.

For New Hires:

🏎️ Visual race track showing their onboarding journey
📊 Speedometer displaying real-time completion percentage
🏅 Badges and achievements for hitting milestones (Pole Position, Halfway Hero, Speed Demon)
🤖 AI-powered Co-Driver (via Rovo) that answers questions 24/7

For HR Admins:

⚡ One-click new hire registration
📈 Live dashboard with all active onboardings
🚨 Blocker alerts and overdue detection
📝 Customizable task templates by role, department, and location

For Pit Crew (IT, Finance, Security, HR, Manager):

🎯 Automatic task assignment based on department
👤 Issue panel showing new hire context right in Jira
✅ Seamless task completion without leaving their workflow

How we built it

Platform: Atlassian Forge (serverless, runs natively in Atlassian Cloud)

Tech Stack:

TypeScript for type-safe backend logic
React + Vite for the three UI modules (Admin, Race Track, Issue Panel)
Forge Storage API for data persistence
Jira REST API for issue/board management
Confluence Search API for knowledge base integration
Rovo Agent for AI-powered assistance

Architecture:

Clean separation: Resolvers → Services → Storage
Modular design with dedicated services for each domain (newHire, template, gamification, etc.)
Property-based testing with fast-check for robust validation

Key Forge Modules:

jira:projectSettingsPage — Admin dashboard
jira:globalPage + confluence:globalPage — Race track visualization
jira:issuePanel — Pit crew context panel
webtrigger — External API access

Challenges we ran into

1. Gamification that doesn't feel gimmicky Finding the right balance was tricky. Too many badges = meaningless. Too few = boring. We landed on a tiered system: stage-based badges (complete Week 1), progress-based badges (reach 50%), and special achievements (finish 5 days early).

2. Cross-product coordination Making the app feel seamless across Jira AND Confluence required careful state management. A task completed in Jira needs to instantly reflect on the Confluence race track. Forge Storage helped, but we had to design our data model carefully.

3. Forge Storage limitations No relational queries, 128KB per key limit. We had to denormalize data and implement our own indexing patterns (e.g., task:newhire:{id} for quick lookups).

4. Making the race track actually look like a race track CSS art is hard. Getting the car to animate smoothly along a curved track while showing accurate progress took more iterations than we'd like to admit.

5. Rovo integration complexity Designing agent actions that are genuinely useful (not just demos) required thinking deeply about what questions new hires actually ask.

Accomplishments that we're proud of

✅ It actually works end-to-end — From HR clicking "Add New Hire" to the new hire earning their Grand Prix Champion badge, the whole flow is seamless.

✅ The race track visualization — It's genuinely delightful. Watching your car move forward as you complete tasks creates real motivation.

✅ Zero external dependencies — Everything runs on Forge. No servers to maintain, no databases to manage, no security headaches.

✅ Smart task assignment — The system automatically routes tasks to the right department based on templates. IT gets laptop provisioning, Finance gets payroll enrollment, etc.

✅ The badge system — People actually want to collect them. "Speed Demon" for finishing 5 days early has become a point of pride in our testing.

✅ Clean architecture — The codebase is maintainable. Services are decoupled, resolvers are thin, and we have solid test coverage.

What we learned

1. Forge is production-ready We were skeptical at first, but Forge handles real workloads well. The developer experience is solid, and not worrying about infrastructure is liberating.

2. Gamification requires restraint Our first version had 20+ badges. It was overwhelming. We cut it down to 9 meaningful ones, and engagement actually increased.

3. Context is everything The issue panel that shows new hire details to the pit crew was an afterthought — but it became one of the most-loved features. Knowing WHO you're helping changes how you help.

4. AI assistants need guardrails The Rovo Co-Driver is powerful, but we had to carefully scope what it can and can't do. It searches the knowledge base and reports status — it doesn't make decisions.

5. Onboarding is a team sport Building this made us realize how many people touch a new hire's first month. The "pit crew" metaphor isn't just cute — it's accurate.

What's next for Onboarding Grand Prix

Short-term:

📊 Advanced analytics dashboard (bottleneck identification, department performance)
🌍 Multi-language support
📱 Mobile-optimized race track view
🔔 Slack/Teams notifications for task assignments

Medium-term:

🏢 Multi-tenant support for enterprise (different tracks per department/location)
📋 Pre-built template library (Engineering, Sales, Marketing, etc.)
🤝 Buddy system integration (pair new hires with mentors)
📈 Predictive analytics (identify at-risk onboardings before they stall)

Long-term: