A better ramp starts with an oops.

An oops is something you can use.

In OOPS! LAB, a missed landing can reveal more than a lucky success. Before rebuilding, describe what happened: did the object stop on the ramp, leave too quickly, or overshoot its target? Those are different observations, and each suggests a different next test.

Gravity acts downward. On an incline, part of that force acts along the slope. For a simple object sliding down an otherwise identical ramp, a steeper angle increases the downhill component of gravity. Friction opposes relative sliding at the contact surface. A rougher surface can reduce a sliding object’s acceleration or prevent it from starting.

Compare a simplified slider.

Change the angle below, then add friction. This is an idealised block sliding down a fixed slope, not a simulation of a rolling ball or the game. When friction is enabled, the model uses the same coefficient, 0.4, for starting and sliding friction; real surfaces can behave differently.

Keep one thing different.

1. Choose a goal. Aim for a controlled arrival, rather than the greatest possible speed. Read the mission’s target and constraints first.
2. Make a prediction. Say what you expect a small change to do. Keep the object and starting point the same while you test the ramp.
3. Compare the attempts. Change one piece or angle, play again and look for the difference. A different launch position as well as a different ramp makes the cause harder to identify.

Notice the limits of the model.

A rolling mango is not a sliding block. Shape, collisions, rotation and the arrangement of the game’s pieces matter. Use the small slider to explore one relationship, then use the game’s actual feedback to understand the mission.

At the end, ask for a comparison: “The second ramp was different in this way, and we observed this result.” That explanation is more useful than “It worked.” For another kind of evidence challenge, try Detective Zero and compare a witnessed clue with a guess.