Why this matters now
Learning environments increasingly use:
projects;
challenges;
internships;
prototypes;
teamwork;
simulations;
AI;
real-world experiences.
But active experience is not automatically deep learning.
A learner can finish a project without understanding why a particular decision worked.
A team can repeat the same mistake with greater confidence.
Feedback can be received and ignored.
Success can happen by luck and be mistaken for good judgement.
Reflection creates the possibility of separating:
what happened
from
what we should learn from what happened.
Real-Life Readiness makes reflection an explicit condition of preparation: learners make their reasoning visible, learn from results and revise their approach.
Experience does not automatically become learning
An experience produces an event.
Learning requires interpretation.
What do I understand now that I did not understand before?
What assumption changed?
What would I choose differently?
What can I transfer?
Without that movement, experience may remain memorable without becoming reusable.
Make the reasoning visible
A final product hides much of the work behind it.
We see:
the solution;
prototype;
presentation;
result.
We may not see:
the assumption;
rejected option;
evidence;
trade-off;
reason for revision.
Reflection externalises enough of that reasoning for it to be examined.
This matters both for the learner and for anyone trying to understand the learning.
Description is not reflection
Description:
“We tested the prototype and users found some problems.”
Reflection:
“We expected users to recognise the first step without instructions. Several people interpreted it differently. We realised that our own familiarity with the design was hiding an assumption, so we will redesign that step and test again.”
The second statement contains:
expectation;
evidence;
interpretation;
revision.
That is a different level of learning.
| Description | Reflection |
|---|---|
| What happened? | Why did it happen this way? |
| What did we do? | What reasoning guided us? |
| What feedback did we receive? | What does the feedback change? |
| How did it end? | What will we do differently? |
Expectation versus reality
A simple reflective structure begins with two questions:
What did we expect?
What actually happened?
The gap creates a third:
Why were they different?
That difference can reveal:
a hidden assumption;
an incomplete model;
a new constraint;
unexpected behaviour;
or something that worked better than expected.
Reflection lives in this gap between prediction and reality.
Feedback introduces information we cannot generate alone
Creators know their own intention.
Users do not.
That difference matters.
Someone external may see:
confusion;
friction;
risk;
a missing explanation;
a hidden assumption.
Mars Challenge's prototype process asks teams to show their work and ask what others understand, what is unclear and what they would improve, before incorporating the most relevant feedback.
The sequence is not:
receive comment → obey comment.
It is:
receive → interpret → judge → revise.
Feedback is not raw opinion
Different feedback carries different informational value.
“I prefer blue.”
“I do not understand what happens first.”
“This component cannot operate within the stated temperature.”
These are not equivalent.
The learner needs to distinguish:
preference;
observation;
expert constraint;
evidence;
repeated pattern.
Feedback itself requires judgement.
Receiving feedback does not mean surrendering authorship
This is where Reflection and Feedback connects with Agency.
A mentor can ask an excellent question.
A jury can identify a weakness.
A user can dislike a feature.
The participant still needs to decide:
What does this tell us?
Does it matter?
What evidence supports it?
What should change?
What should remain?
Feedback strengthens Agency when it improves judgement without replacing authorship.
Good feedback points toward a next move
“Bad idea.”
has limited formative value.
“I cannot see how this mechanism addresses the water constraint you defined.”
is different.
The second creates a question the team can work on.
Good formative feedback usually connects:
current state;
desired purpose;
observable gap;
possible next investigation or action.
Feedback should address the work, not define the person
“This argument does not show its evidence.”
is actionable.
“You are bad at research.”
is identity-level judgement.
The first leaves room for revision.
The second can close it.
Learning-oriented feedback should preserve the possibility of improvement and authorship.
Formative means there is still time to act
Mars Challenge Teacher Training includes observation and formative feedback of learning processes beyond the final product and explicitly prioritises assessment for learning through formative feedback.
This distinction matters.
Feedback received while change is still possible can shape learning.
Feedback received only after everything is over may explain the past, but cannot improve that version of the work.
Reality also gives feedback
Feedback does not only come from a person.
Reality responds.
The prototype breaks.
The user hesitates.
The cost exceeds the budget.
The material behaves differently.
The claim fails verification.
A system creates an unexpected consequence.
These outcomes are feedback.
Real-Life Readiness pairs CONSEQUENCE and REFLECTION: decisions create effects, obligations, feedback or costs that need to be recognised, and reflection examines what those results mean.
Let the consequence challenge the reasoning
When something goes wrong, teams often repair the artefact immediately.
Sometimes the more valuable question is:
What did our reasoning miss?
Was there:
a weak assumption?
poor evidence?
an absent user?
an ignored constraint?
a misunderstood need?
a rushed decision?
Changing only the artefact may leave the underlying thinking untouched.
Learn from success too
Reflection should not become a compulsory search for failure.
If something worked, ask:
Why?
Under what conditions?
Would it work again?
What should we preserve?
Success can produce learning when it is examined rather than celebrated superficially.
Version history makes learning inspectable
Mars Challenge asks teams to document feedback received, adjustments made and multiple versions of their prototypes.
This creates a visible path:
Version 1.
Feedback.
Decision.
Version 2.
A final product shows where the team ended.
The history can show how its judgement changed.
- Version 1
- FeedbackWhy did it change?
- DecisionWhy did it change?
- Version 2Why did it change?
- TestWhy did it change?
- Version 3Why did it change?
Revision needs a reason
A newer version is not automatically better.
Iteration becomes meaningful when the team can explain:
What changed?
Why?
What evidence or feedback justified the change?
What new question does the version test?
Otherwise iteration can become motion without learning.
Reflection should change something
Not every reflection requires a redesign.
But it should usually change at least one of:
understanding;
confidence;
question;
criterion;
future action.
A reflection that changes nothing may still be interesting.
But the learning cycle remains incomplete.
The next action is the test
“We learned that user input is important.”
Then the team creates the next version without users.
The statement has not yet changed practice.
Learning becomes more visible when the team can say:
We used to assume X.
Evidence showed Y.
We now do Z.
Real-Life Readiness includes adapting through feedback directly inside ACT.
Reflection and Feedback vs Experiential Learning
The concepts overlap but are not redundant.
Experiential Learning describes the wider learning cycle in which action, consequence, reflection and revised action interact.
Reflection and Feedback focuses on the learning mechanism in the middle:
How do we interpret what happened?
How do other perspectives alter our understanding?
How do we decide what changes next?
Experiential Learning provides the architecture.
Reflection and Feedback provides part of the conversion mechanism.
Reflection and Evidence
Feedback can be evidence.
But its evidentiary strength varies.
One opinion may indicate a question.
Repeated observation may suggest a pattern.
A structured test can provide stronger support.
Evidence and Verification asks:
What can this feedback legitimately support?
Reflection asks:
What should we reconsider because of it?
Reflection and Decision-Making Under Uncertainty
Every action changes the evidence available.
Feedback updates the state of knowledge.
The next decision should therefore begin from a revised model of reality.
Reflection is not separate from decision-making.
It is one of the mechanisms by which future judgement improves.
Reflection and Agency
Feedback should not train learners to search for the answer the evaluator wants.
That weakens authorship.
A stronger learner can say:
This is the feedback we received.
This is what it revealed.
This is the part we accepted.
This is the part we did not.
This is why.
That is reflection with Agency.
AI can provide feedback too
AI can:
review;
question;
suggest alternatives;
identify inconsistencies;
simulate reactions.
It can be useful.
But its feedback still needs human interpretation.
The system may not know:
local context;
real constraints;
stakeholder values;
the complete goal.
The principle remains:
feedback informs judgement; it does not own the next decision.
Reflection and feedback loop
- Action
- Consequence
- Observation
- Feedback
- Reflection
- Revision
- Next action
- New evidence
ACT
What did we do?
EXPECT
What did we think would happen?
OBSERVE
What actually happened?
LISTEN
What feedback did people or the system give us?
INTERPRET
What does that information mean?
QUESTION
Which assumption or decision needs reconsideration?
CHOOSE
What should we preserve, change or abandon?
ACT AGAIN
What will we do next?
TRANSFER
What is reusable beyond this specific experience?
The complete movement is:
ACTION → CONSEQUENCE → REFLECTION → REVISION → NEW ACTION
Five high-value reflection questions
What did we expect?
What happened?
What evidence or feedback explains the difference?
What changed in our understanding?
What will we do differently next?
These questions keep reflection connected to action.
A feedback filter
Before changing the work:
Is this feedback relevant to the goal?
Is it an observation or preference?
Does the person hold relevant experience?
Does other evidence support it?
Does it expose a blind spot?
What change would it imply?
What trade-off would the change create?
This turns feedback from a collection of comments into input for judgement.
- Relevant to goal?
- Observation or preference?
- Supported elsewhere?
- Reveals a blind spot?
- What change?
- What trade-off?
What Reflection and Feedback is not
It is not compulsory journaling.
It is not a chronological description of events.
It is not blame.
It is not accepting every criticism.
It is not waiting for a teacher to provide the answer.
It is not only final evaluation.
It is not assuming failure equals learning.
It is not assuming success equals understanding.
It is not constant revision without criteria.
It is not reflection detached from action.
And it does not need to occur only at the end.
Reflection can happen throughout the process.
What the evidence says
Real-Life Readiness defines REFLECTION as making reasoning visible, learning from outcomes and revising the approach. It also describes repeated encounters with reality, decision, consequence and reflection as an operating principle for preparation.
ACT includes adapting through feedback.
Its proposed evidence architecture includes whether participants revise decisions after receiving feedback.
Mars Challenge's prototype process explicitly asks participants to obtain feedback, interpret what is most relevant, adjust and document those changes.
Teacher training reinforces formative observation and feedback beyond the final product.
These sources support the conceptual and programme architecture.
They do not provide causal evidence that the programme independently improves reflective capability.
What this means for educators
Reflection becomes stronger when educators stop asking only:
“What did you learn?”
and begin asking:
What did you expect?
Which decision mattered?
What evidence informed it?
What happened?
What surprised you?
Which feedback changed your view?
Which feedback did you reject?
Why?
What will you change?
What will you preserve?
The educator is no longer only grading an answer.
They are helping make reasoning visible.
The purpose of feedback similarly shifts.
From:
judging the completed work
to:
providing information that improves the next move.
Related concepts
Projects and evidence in practice
Mars Challenge Prototype Process
Participants gather feedback, choose what is relevant, make adjustments and document those changes.
Mars Challenge Teacher Training
Teacher development includes observing and giving formative feedback on processes beyond the final product.
Evidence status: documented programme design and process, not causal learning-outcome evidence.
Frequently asked questions
Is reflection just thinking about what happened?
No. Useful reflection connects expectations, decisions, evidence and results. It asks what has changed in understanding and what should change in the next action.
Should all feedback be acted upon?
No. Feedback needs judgement. Learners should consider its relevance, evidentiary value, context, the experience of the person offering it and the trade-offs created by any proposed change.
What is the difference between feedback and evaluation?
Evaluation can judge the quality of a performance or result. Formative feedback is designed to improve what happens next. Its value depends on whether the learner still has an opportunity to act on it.
Does failure automatically create learning?
No. Failure creates an outcome. Learning requires interpreting why it happened, what it reveals and how that insight changes subsequent action.
Why preserve earlier versions?
Because they make change visible. Earlier versions can show assumptions, feedback, rejected alternatives and reasons for revision. Mars Challenge explicitly asks teams to document feedback and adjustments.
Can positive feedback support learning?
Yes. It can identify elements worth preserving and help learners understand why something worked. Reflection should examine successful outcomes as well as problems.
Can AI provide useful feedback?
Yes. AI can critique, question and suggest alternatives. But its feedback still requires contextual judgement and verification, and responsibility for the next action remains with the learner or team.
References
Real-Life Readiness — A Foundational Framework
Adelino Sousa / Mars Challenge / Virtual Educa, 2026.
Reflection, consequences, feedback, adaptation and transfer.
Mars Challenge Participant Guide 2026
Mars Challenge, 2026.
Prototype feedback, adjustments and documentation of iterations.
Mars Challenge Teacher Training
Mars Challenge.
Formative observation and feedback; assessment for learning.
Explore next
Next step
Deepen: Explore Experiential Learning, Evidence and Verification and Agency.
Explore the process: See how feedback, iteration and documented revisions appear in the Mars Challenge process.
Act: After the next test or action, answer: what did we expect, what happened and what will we change next?
Updated: 14 October 2026
