Rise / Spark the Rise

Read the campaign story

Mahindra introduced Rise as a group-wide position in January 2011, crediting StrawberryFrog’s work on its development. Spark the Rise followed later that year, connecting project ideas with collaboration, visibility and potential support. This case treats the corporate platform and its participation programme as one family. It is distinct from the existing SUV-focused Live Young, Live Free case: the subject here is a cross-business promise translated into a project-support mechanism.

Editorial interpretation: a broad verb becomes more concrete when people can act on it through a defined process. A platform for ideas can make a corporate promise observable, but the organisation must support the work after attracting attention. The difficult design question is not simply how to gather many proposals. It is how to give contributors a fair understanding of selection, ownership, available help and what happens when their idea is not chosen.

The programme interview contains reported participation and impact claims that are not adopted as independent causal findings. An application, vote or grant is not proof that a project produced its intended social outcome. This analysis does not recommend a public popularity contest for allocating consequential resources. Its adaptation uses a small, noncompetitive adult workshop with no funding decision, public ranking or collection of proprietary business plans.

Translate the brand verb into a complete participant journey

A call to act should explain what someone can actually do, what they must provide and what response they can expect. Map the journey beyond submission: acknowledgement, review, feedback and any support all need owners. A small organisation should choose a scope it can sustain rather than invite an unlimited stream of ideas. Test the instructions with someone unfamiliar with the programme and ask them to describe both the opportunity and the limits. If the promise sounds larger than the available support, narrow it before launch. A brand experience is created by the whole process, including what happens to people who receive no further opportunity.

Separate visibility from merit and support needs

Public enthusiasm can help spread a project, but it may reflect existing networks rather than quality or need. Do not treat a popular vote as a neutral measure of social value. If resources are allocated, use transparent criteria, appropriate expertise and safeguards against conflicts or exclusion. A small learning exercise can avoid allocation entirely and focus on helping participants clarify ideas. The useful lesson is that a platform can connect people, not that competition automatically identifies the best solution. Review whether the mechanism rewards presentation skill more than substance and whether less-connected contributors have an understandable route to participate on fair terms.

Protect ideas while making collaboration possible

An invitation to share can expose intellectual property, personal information or untested claims about communities. Explain what will be public and obtain permission before reusing material in advertising. Provide a way to discuss an idea at a high level without disclosing confidential details. Collaboration also needs a clear distinction between introductions, advice and commitments to deliver work or funding. For a small programme, use fictional briefs or openly shareable projects during initial testing. The platform should help people understand each other’s capabilities without turning access to support into an obligation to surrender ownership or provide promotional content for the organiser.

A bounded test for another brief

Proposed adaptation: an adult community makers’ group could run a noncompetitive idea-clarification session using fictional projects such as organising a public craft display. Compare an open invitation with a structured worksheet explaining the problem, available resources and unanswered questions. Give every participant the same optional feedback time, with no prizes, public votes or funding promises. Keep worksheets private unless contributors explicitly choose to share. Ask whether the structure helps people identify a useful collaborator and a realistic next action. This tests how a broad invitation becomes a workable process without deciding eligibility for consequential support or collecting proprietary proposals.

Measure understanding of the process, clarity of the next action and recognition of what support is not promised. Record participant effort and confusion, not just the number of submitted ideas.

Stop if the exercise creates an implied funding commitment, exposes confidential ideas or uses public popularity to determine access to important opportunities.