UC San Diego: Leadership (PIQ 1)

When our robotics captain graduated, the team did not so much fall apart as quietly stop showing up. Attendance dropped from fourteen to five. I was the only sophomore left who knew how to wire the drivetrain, so by default the soldering iron and the group chat became mine.¹My first instinct was to do everything myself. That lasted three weeks, until I missed a deadline because I was hand-checking code I did not write. I realized the team had not collapsed from lack of talent. It had collapsed because no one felt ownership of any single part.So I stopped assigning tasks and started assigning territories. Priya owned pneumatics. Marcus owned the intake. Each person became the one human who knew their subsystem cold, and I made them teach it to one other member so no knowledge died with a single absence.²Disputes still came. Marcus and Priya fought for two days over whether the intake or the lift got priority on our shared motor controller. Instead of ruling from the top, I made them each defend their case to the full team with a sketch and a time estimate.³The team voted for the intake, and Marcus, having heard everyone's reasoning, accepted it without resentment. I learned that people will lose an argument gracefully if they believe the process was fair.We did not win regionals. We placed eleventh of twenty-six, which for us was a resurrection. But the number I am proud of is this: the next year, eighteen students signed up, and four of them asked to lead subsystems they had learned from someone I trained.⁴Leadership, I found, is not being the smartest person in the room. It is making sure the room keeps working when you are not in it.