Describe a change you made so more people could participate in a group.
What the evaluator is looking for
Readers look for a real group need, choices the writer personally made, collaboration, and impact described without inflated claims.
Planning approach
For Two Chairs at Every Laptop, select the central scene, identify the consequential choice, trace the specific response, and reserve the ending for evidence-supported reflection.
Model response
By October, our coding club's attendance had split in half. Experienced members crowded around two laptops, typing fast while new students watched solutions appear. We called the meetings open to beginners, but three beginners stopped coming after their second week. When I texted one of them, she replied, “I never get to touch the code.”
At the next meeting, I placed two chairs at every laptop and introduced rotating roles. The driver controlled the keyboard; the navigator read the problem, asked questions, and checked each decision. Roles switched every twelve minutes. Advanced members worried that progress would slow. It did. The first maze challenge took almost twice as long, but the conversation exposed assumptions that had previously passed silently from experienced fingers to the screen.
Our first pairing system was uneven because friends chose one another. I began matching partners by what they wanted to practice and let people request a change privately. We also reserved the final ten minutes for a demonstration by someone who had not presented that month. In December, the student who had texted me returned and showed a maze with two solutions. Her partner explained the debugging process, and neither claimed the work alone.
Opening a club door had not created access. Participation depended on who controlled the tools, who could ask a slow question, and whether contribution was visible before expertise. I learned to look beyond attendance when evaluating inclusion. Now we track keyboard time, demonstrations, and which questions become shared notes. The club still has faster and slower programmers, but speed no longer determines who gets to build. Leadership meant redesigning the room so beginners could become practitioners rather than permanent spectators. We still allow solo work when a member needs it, but nobody reaches a keyboard by seniority. The two chairs remain a visible reminder that learning code includes explaining decisions and yielding control.
Structural breakdown
Two Chairs at Every Laptop progresses from a concrete situation through observable decisions and results. Its closing insight stays proportionate to the events shown instead of claiming a universal transformation.
- Verify that every detail in Two Chairs at Every Laptop serves its central question.
- Replace broad character claims with actions a reader can observe.
- Preserve other people as participants rather than props.
- Keep the final insight within the evidence of the response.
Format reference: Common App, Essay Prompts. This model is original and is not an official or accepted submission.