A makerspace ramp project succeeds only after its designers give users control over the testing process.
Our makerspace celebrated the first portable stage ramp before anyone had rolled across it. The plywood held the required weight, the hinge folded cleanly, and our measurements matched the published slope. Maya, a wheelchair user from the theater group, stopped halfway up. The transition strip caught her front casters, and the handrail blocked the angle she used to push. We had designed for a specification and photographed success before asking whether the object worked.
Maya declined our offer to ‘fix it quickly.’ Instead, she asked for three versions she could compare. We built removable transition strips, shifted the rail, and marked force readings at different slopes. At the next test, performers evaluated setup time, turning space, and what happened when a cable crossed the landing. Maya chose a design none of us preferred visually because it let her approach independently. We documented her reasoning beside the dimensions so a future builder would understand why the awkward-looking clearance mattered.
The ramp changed our makerspace rules. Projects involving a community now name who defines success, who can stop a test, and who controls the final documentation. My contribution was not the winning design; it was helping turn an embarrassing failure into a repeatable review process. Community collaboration, I learned, begins when the people affected can reject the problem statement as well as the prototype. I still enjoy the moment a mechanism moves for the first time, but I no longer confuse motion with function. The more important test is whether the person expected to use a design can recognize their decisions inside it.
Original teaching sample written by the Writivia team. It is not a real student's submitted essay and does not imply admission to Massachusetts Institute of Technology.