Loading...
culture

Idea Storm

Two weeks of ideas — the boldest contributor wins.

See it in MangoApps

Trusted by frontline teams 15 years of frontline software

Built for: Healthcare · Manufacturing · Retail · Education · Nonprofit

Overview

Idea Storm is a short, ranked idea-submission contest built around verified idea.submitted events. It is designed for a 14-day window, with individual entrants competing on the number of ideas they actually submit and earning points for the top ranks.

Use this template when you want a focused burst of participation, a clear deadline, and a simple way to recognize people who contribute ideas. It works well for culture programs, continuous improvement campaigns, and team challenges where the goal is to get more people speaking up. Because the scoring is based on tracked submissions, it is harder to game than a free-form poll or an open leaderboard.

Do not use this template as a permanent always-on leaderboard or as a replacement for a suggestion system that needs long review cycles. It is also not the right fit when the goal is to reward quality judged by a panel, compare external KPIs, or run a cooperative threshold-based effort. If your audience is mixed in size and you want fairness across teams, consider segmenting standings or using a different format. The best results come when the prompt is specific, the rules are simple, and participants can see that good ideas will be reviewed after the contest ends.

Standards & compliance context

  • Because this template scores verified idea submissions, it aligns better with Goodhart-resistant contest design than self-reported participation counts.
  • The individual structure is appropriate when speaking up is the behavior you want to encourage, but it should be presented as an opt-in contest rather than a performance ranking.
  • If you run this in a unionized or works-council environment, keep the format cooperative, transparent, and free of punitive bottom-ranking language.
  • Avoid using the contest to evaluate protected activity, employee discipline, or compensation decisions.
  • If submissions may include personal or confidential information, define a review process that removes sensitive details before sharing ideas broadly.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

How to use this template

  1. Set the contest window to 14 days and write one clear prompt that tells entrants what kind of ideas you want.
  2. Choose the audience and decide whether standings should be shown to individuals only or split by team or department for fairness.
  3. Publish the submission rules, including whether duplicates are allowed, whether ideas need a short description, and how you will handle incomplete entries.
  4. Promote the contest during the first few days with examples of strong submissions and reminders that only verified idea.submitted events count.
  5. Review the final standings, validate the top submissions, and award points to the ranked winners according to the template.
  6. Close the loop by summarizing the best ideas, naming what will be acted on, and capturing follow-up items for the next round.

Best practices

  • Write a narrow prompt so people know whether you want cost-saving ideas, customer ideas, safety ideas, or culture ideas.
  • Show examples of good submissions before launch so entrants understand the level of detail you expect.
  • Keep the contest time-boxed to the planned 14 days so the standings stay active and the finish feels real.
  • Review duplicate or near-duplicate ideas before finalizing winners so volume does not crowd out originality.
  • Use verified submission events only, and do not count comments, reactions, or informal mentions as entries.
  • If the audience is mixed in size, split standings by team or use separate contests so smaller groups are not buried.
  • Publish what happens after the contest ends so participants know the ideas will be read, grouped, and routed.

What this template typically catches

Issues teams running this template most often surface in practice:

People submit broad, vague ideas that are hard to act on.
Duplicate submissions appear when the prompt is too open-ended.
A few highly active entrants dominate the standings while quieter voices stay out.
Ideas are collected but not reviewed, which reduces trust in future contests.
The contest drifts into a permanent leaderboard instead of ending on schedule.
Teams with more people can appear to outperform smaller groups if the audience is not segmented.
Participants add implementation details that belong in follow-up, not in the initial idea submission.

Common use cases

Operations Manager Idea Drive
A plant or warehouse manager runs a two-week contest to collect ideas for reducing friction in daily workflows. The best submissions are grouped by theme after the contest and routed to supervisors for review.
HR Culture Sprint
An HR partner launches Idea Storm to encourage employees to speak up about onboarding, recognition, or meeting norms. The contest creates a visible window for participation without turning it into a permanent leaderboard.
Customer Experience Team Challenge
A service leader asks frontline staff to submit ideas for improving response times, handoffs, or customer communication. The contest helps surface practical fixes from people closest to the work.
School or Campus Improvement Campaign
An education team uses the template to gather ideas from staff about scheduling, student support, or facility issues. The short duration keeps the campaign focused and easy to communicate.

Frequently asked questions

What is Idea Storm best used for?

Idea Storm is best for collecting a short burst of ideas from employees, members, or volunteers when you want participation, not a long-running leaderboard. It works well for culture campaigns, process-improvement ideas, recognition themes, and suggestion drives. Because it scores verified idea.submitted events, it rewards actual submissions rather than self-reported effort.

How long should this contest run?

The template is set to 14 days, which fits the natural cadence of an idea drive. That gives people enough time to notice the contest, think through a submission, and participate without the event dragging on. If you extend it too long, the energy usually drops and the standings stop feeling urgent.

Who should run the contest?

A manager, culture lead, HR partner, or team coordinator can run it, as long as they can review submissions and communicate the rules clearly. The organizer should define what counts as an idea, whether duplicates are allowed, and how tie-breaks work. If you want broader adoption, assign one owner to post reminders and one reviewer to approve edge cases.

Is this fair for small teams and large teams?

Yes, because the template uses an individual structure with highest_score based on submitted ideas, so it is straightforward to understand and easy to compare within the same audience. If you are running it across mixed-size groups, you may want to segment standings by team or department instead of combining everyone into one list. That avoids making a small group feel outmatched by a much larger one.

How does this avoid low-quality or spammy ideas?

The contest only counts verified idea.submitted events, so you can review entries before they affect standings if you want a quality gate. A common pitfall is rewarding raw volume without any screening, which can encourage duplicates or thin submissions. Set a simple acceptance rule, such as one idea per distinct problem or one submission per person per day, if needed.

Can this be customized for different departments or themes?

Yes. You can change the prompt, the submission form fields, the prize type, and the ranking rules while keeping the same contest structure. Many teams use the same template for operations ideas, customer experience ideas, safety ideas, or onboarding improvements by changing the theme and examples.

How is this different from an always-on suggestion box?

A suggestion box is open-ended and often fades into the background, while Idea Storm creates a defined contest window with standings and a clear finish. That time box usually drives more participation because people know when to act. It also gives you a natural review point to sort, group, and respond to the best ideas.

What should I do after the contest ends?

Review the top ideas, group duplicates, and decide which ones move into action, pilot, or follow-up. Share the winning ideas and explain what happens next so participants see that the contest produced something real. If you plan another round, use the first contest to refine the prompt and submission criteria.

Go deeper on the topic

Related guides

Ready to use this template?

Get started with MangoApps and use Idea Storm with your team — pricing built for small business.

Get Started