How does Mars Challenge work?

Mars Challenge does not work as a question handed out in the morning followed by a pitch at the end of the day.

There may be intensive moments.

Prototyping.

Presentations.

Competition.

But the system is larger than any one of them.

The permanent logic is a journey:

mission → problem → team → investigation → decision → creation → return to Earth → feedback → iteration → evidence.

The specific format may change from one mission to another.

What remains is the intention to place knowledge in a situation where choices genuinely have to be made.

The first step is not a lesson explaining the answer.

It is entering a context.

Each edition may organise different missions, and each mission defines the relevant challenge, audience, conditions, timetable and route.

A challenge creates a situation that needs to be understood before it can be “solved”.

What problem are we actually facing?

What do we know?

What are we merely assuming?

Who is affected?

What resources and constraints exist?

What information is still missing?

Before creating something, we need to understand what is worth creating.

Real problems rarely belong to one discipline.

Mars Challenge therefore creates space for different forms of knowledge, experience and ways of looking at the same problem.

One person may see the technical dimension.

Another may identify a behavioural issue.

Someone else may recognise an economic, legal, cultural, environmental or communication challenge.

A team is not simply a way of dividing tasks.

It helps make each person's blind spots visible.

Specific composition requirements may vary by mission, phase and edition. The underlying principle is not to confuse one perspective with the whole problem.

Mars Challenge uses a guided process.

Participants are asked to make visible what would normally remain hidden between “we received the problem” and “here is our solution”.

How did we arrive at this definition?

Which hypothesis did we reject?

What evidence changed our minds?

Why did we choose this alternative?

Which constraints did we encounter?

What did we change after feedback?

Previous implementations have formalised this logic through sequenced phases and specific deliverables.

The detailed structure can evolve between missions and editions.

The principle remains: learning is not only about presenting an outcome. It is also about making visible the journey that produced it.

Being supported does not mean being given the answer.

A mentor helps the process move forward.

They can ask questions.

Facilitate reflection.

Help a team organise itself.

Draw attention to what has not yet been considered.

Encourage collaboration and improvement.

But they should not solve the challenge, impose their own decision or become the author of the project.

Guidance exists to increase the team's capacity, not to replace it.

Mars Challenge needs participants' decisions to remain visible.

If somebody else makes those decisions for them, an essential part of the learning disappears.

An idea changes when it stops existing only in conversation.

Mars Challenge asks teams to make their thinking visible.

Through a concept.

A model.

A physical or digital prototype.

A system.

A representation.

Something concrete enough for other people to question.

Then comes a crucial question:

what returns to Earth?

Earth-Back Thinking connects what has been developed under extreme constraints to a real context.

What learning transfers?

Which problem can we now see differently?

Which assumption has changed?

Which part of the proposal deserves further exploration?

A prototype does not need to pretend it is a finished product.

Its value is in making a hypothesis discussable, observable and improvable.

Presenting an idea does not close the process.

It exposes it.

Other people ask questions.

Criteria force the team to justify what it is proposing.

Weaknesses appear.

Assumptions are challenged.

New evidence may require change.

That is why Mars Challenge combines evaluation with reflection and feedback.

The purpose is not only to produce a score.

It is also to create a moment in which the team must explain why it decided, what it can support, what it still does not know and what it would change in another iteration.

A good question can improve a project more than a quick answer.

Some Mars Challenge missions and routes may include competitive evaluation, selection, national stages or international convergence.

That does not make Mars Challenge simply a competition.

Competition is one possible mechanism inside the wider experience.

It can introduce pressure.

Make decisions public.

Compare projects using common criteria.

Open access to subsequent stages.

But the rules are not timeless.

Eligibility, dates, format, progression, number of stages, criteria and recognitions belong to the relevant edition and mission.

The mission page tells you how to participate this year. This page explains how the system works.

Mars Challenge aims to document not only what a team presents but also what is created through the journey.

Projects can become units of programme memory.

They allow us to return to a question.

Compare approaches.

See what different teams imagined.

Connect projects with missions, institutions, countries and concepts.

And, when sufficient evidence exists, understand more clearly what the programme is actually producing.

That requires an important distinction:

a documented project is not automatically a validated solution.

The record should preserve what really exists — an idea, hypothesis, prototype, experience or evidence — without turning it into something it is not yet.