Leadership Essay Examples

The Millbrook Public Library occupied a former insurance office with fluorescent lights, industrial carpet, and exactly 847 books—I counted one slow afternoon when Mrs. Chen, the part-time librarian, asked me to help with inventory. Our rural town of 2,300 people had lost funding for a proper library years before I was born. “This is what we can afford,” Mrs. Chen said, gesturing at the cramped space. She didn’t sound defeated, just factual.

I was fifteen and desperate to pad my college application with impressive leadership experience. Starting a library expansion project seemed suitably ambitious—I’d recruit volunteers, hold fundraisers, maybe organize a book drive. I imagined cutting ribbons and giving speeches. I wrote a passionate proposal to the town council, printed flyers, and scheduled an organizational meeting at the library.

Three people showed up: Mrs. Chen, my mother (obligated by parental duty), and Mr. Petersen, who’d clearly come for the free cookies. My grand vision of mobilizing the community evaporated in that empty room. But Mrs. Chen said something that stuck: “Big projects don’t start big. They start with one person doing the next right thing, then the next.”

So I did the next thing. I organized the existing books by actual categories instead of the random system Mrs. Chen had inherited. Then I researched grant opportunities and spent three weeks learning how to write grant applications. My first seven applications were rejected. The eighth, to a state literacy foundation, awarded us $3,000—enough to buy 400 new books and basic shelving.

The delivery day, I expected celebration. Instead, I found Mrs. Chen standing in the storeroom, overwhelmed. “I don’t know how to catalog this many books,” she admitted. She was seventy-two and had been teaching herself library science from YouTube videos. I realized my ambitious project had created more work for someone already stretched thin.

That’s when the project became real leadership rather than résumé building. I spent my summer learning the Dewey Decimal System, training two other student volunteers, and creating a simple database system Mrs. Chen could maintain. When she confessed she’d never asked for help because “everyone’s so busy,” I started recruiting differently—not asking people to join a big abstract project, but inviting them to spend an hour shelving books or reading to kids. Seventeen people said yes to an hour who’d said no to the big vision.

By senior year, we’d expanded to 2,100 books, established a children’s reading program, and secured recurring funding. But the transformation I’m proudest of isn’t the library—it’s Mrs. Chen. The last time I visited, she was teaching a library science workshop for volunteers, confident and energized. “You showed me,” she said, “that asking for help isn’t admitting defeat. It’s how things actually get done.”

I learned that leadership isn’t about having brilliant visions or mobilizing masses. It’s about showing up consistently, doing unglamorous work when nobody’s watching, and making it easy for others to contribute their small pieces. The Millbrook Library Project didn’t make me a “natural leader.” It taught me that effective leadership is usually quiet, incremental, and far more about enabling others than showcasing yourself.

“Understudies don’t lead. They follow.” That’s what my theater teacher said when I suggested understudies should attend all rehearsals, not just their designated practice times. She meant it practically—we had limited space, limited time. But I heard it differently: understudies don’t matter.

I’d understudied three shows in two years. While leads rehearsed, I sat in the audience memorizing lines I’d probably never say. I watched blocking I’d likely never execute. I was prepared for a performance that would probably never happen. Theater people call understudies “insurance policies”—necessary but hopefully unused.

Then Sarah Martinez, our leading actress in “The Crucible,” developed pneumonia two days before opening night. I’d understudied her role of Abigail Williams, but I hadn’t stood on stage with the full cast in six weeks. My director, Ms. Chen, made the announcement: “Jasmine will perform tomorrow. Everyone, make her feel supported.” Then she moved to contingency planning—adjusting lighting for my different height, revising stage business that depended on Sarah’s physicality, calming the panicking cast.

That night, I couldn’t sleep. Not from performance anxiety—I knew the lines cold. I couldn’t sleep because I kept thinking about the other understudies: Marcus for Proctor, Yuki for Elizabeth, Devon for Danforth. They’d prepared as thoroughly as I had. They felt as invisible as I’d felt. And if we pulled off tomorrow’s performance, it would be because they’d stayed ready despite never being needed.

Before opening night, I did something that felt presumptuous: I gathered the understudies in the green room. “I need your help,” I told them. “I need you to stand by side-stage every scene you’ve covered. When I’m on stage, I need to know that if I miss a line, you’ll whisper it. If I lose my blocking, you’ll gesture. If I’m drowning, you’ll throw me the rope.”

I thought they might resent being asked to support someone finally getting the chance they’d been denied. Instead, Marcus said: “We’ve been here for every rehearsal. We know this show as well as the leads. Let us do our job.”

Opening night, I stepped into Sarah’s blocking, but I wasn’t performing alone. Stage left, I felt Marcus’s presence during the confession scene, ready if I needed him. Yuki stood by during the courthouse confrontation. When I temporarily blanked on a line in Act Three, Devon mouthed it from the wings. The audience saw one understudy stepping into a lead role. I experienced a team of understudies embodying what they’d prepared for—supporting, anticipating, enabling.

The performance succeeded. But more importantly, it revealed something I’d missed about leadership in theater: it’s not about being the lead. It’s about understanding how every role contributes to the collective performance and ensuring that contribution is recognized and activated. After closing night, I started an Understudy Leadership Initiative—creating a formal role for understudies as assistant coaches who give feedback during rehearsals, document blocking, and support ensemble building.

Now when people ask about my theater leadership, I don’t talk about the roles I’ve played. I talk about the roles I’ve understudied and what they taught me: that leadership often means enabling others to shine, that preparation matters even when you’re not in the spotlight, and that the most essential people in any production are often the ones the audience never sees.

When my grandmother received an email notification from her doctor’s office about scheduling a telemedicine appointment, she stared at her phone screen like it was written in hieroglyphics. “How do I…?” she started, then stopped, embarrassed. My abuela, who’d raised six children and managed household finances for forty years, felt helpless before a simple digital interface. She wasn’t alone. In our predominantly immigrant neighborhood, sixty-three percent of residents over fifty-five reported low digital literacy in a recent community survey—and COVID-19 had suddenly made that gap a barrier to healthcare, employment, and social services.

I was seventeen, comfortable with technology but uncomfortable with the growing divide I saw between my generation and my grandparents’. When my high school’s computer lab sat unused during pandemic remote learning, I recognized an opportunity. I drafted a proposal to the principal: allow me to run free computer literacy workshops for community seniors using our empty lab space after school. The pitch emphasized mutual benefit—seniors would gain critical skills while I’d develop leadership and teaching experience.

The principal approved, but recruitment proved harder than I’d anticipated. I posted flyers in Spanish and English at the community center, grocery stores, and church. First session: five people showed up, four of them my grandmother’s friends obligated by her persuasion. But those five people changed everything. Mrs. Nguyen videocalled her daughter in Houston for the first time in six months and cried when she saw her granddaughter’s face. Mr. Rodriguez successfully applied for unemployment benefits online after weeks of failed phone attempts. My grandmother scheduled her telemedicine appointment and proudly told everyone she’d “done it herself.”

Word spread through the network that actually matters in immigrant communities—personal testimony from trusted neighbors. By week three, we had eighteen participants. By month two, thirty-seven. The waiting list grew to fifty-two. I’d massively underestimated both the need and my own capacity. Managing one three-hour Saturday session while keeping up with AP coursework was feasible. Managing three sessions per week wasn’t.

That’s when I learned that effective leadership isn’t doing everything yourself—it’s building systems that can grow beyond your individual effort. I recruited eight bilingual student volunteers from my school’s technology club and National Honor Society, created a structured curriculum with simple visual guides that reduced language barriers, established a buddy system where each student volunteer worked with four to five seniors, and partnered with the public library to provide weekday open lab hours with volunteer support.

The tangible outcomes: 127 seniors completed our eight-week digital literacy program over two years. Post-program surveys showed 94% could now send emails, 87% could videocall family, 81% could access essential online services, and 73% felt “confident or very confident” using smartphones and computers independently. But the numbers don’t capture what I witnessed: Mrs. Patel applying for jobs after three years of unemployment, Mr. Kim accessing mental health teleservices he’d avoided because he didn’t want to burden anyone for transportation, seniors forming a Facebook group to share recipes and stay connected.

The program also changed trajectory for the student volunteers. Three discovered interests in computer science or education technology. Two used the experience as basis for successful science fair projects on human-computer interaction. All reported improved Spanish language skills and deeper community connections. Leadership isn’t just about the person leading—it’s about creating opportunities for others to discover and develop their own capabilities.

This scholarship would enable me to study information systems and community development at [University Name], where I plan to research and implement technology access initiatives in underserved populations. My grandmother’s confusion over a simple email wasn’t an isolated incident—it’s symptomatic of systemic inequities in digital access and literacy. The seniors I’ve worked with taught me that technology’s value isn’t in its sophistication but in whether it empowers people to connect with loved ones, access opportunities, and maintain dignity and independence. This program wasn’t charity—it was justice work, addressing a fundamental barrier to full community participation.

The computer lab at my school now runs year-round with student leadership. My successor, María, is already expanding to include smartphone repair workshops. The system sustains itself because we built it to be bigger than any individual. That’s the kind of leadership I want to practice: creating lasting structures that elevate communities, one empowered person at a time.

The overnight stocking shift at SaveMart paid $13.50 an hour—$2 more than daytime positions—which is why I took it despite the 11 PM to 7 AM schedule conflicting with being a functional high school senior. My family needed the income. My father’s construction work had become sporadic after his injury. My mother’s housekeeping jobs didn’t include benefits. My younger siblings needed school supplies, groceries, stability. The overnight premium meant an extra $80 weekly. That math was simple.

What wasn’t simple was the overnight stocking crew itself. Eight employees from six different countries, ages nineteen to sixty-four, with varying English proficiency and zero communication with day shift staff. Our manager, Dave, worked remotely from home monitoring via security cameras. He left instructions on clipboard and expected efficient execution. It usually worked—we stocked shelves, cleaned, reset displays, worked independently.

Then corporate announced an inventory restructuring requiring complete store reorganization over two weeks while maintaining regular stocking duties. Dave emailed instructions: “Just follow the planogram. Let me know if issues.” The planogram was twenty-seven pages of technical retail jargon and store layout codes. Half our crew couldn’t decipher it. We spent the first three nights making costly mistakes—putting products in wrong sections, disrupting day shift workflows, falling behind schedule.

On night four, I was moving pallets near the break room when I overheard Luis, our sixty-two-year-old Colombian crew member, explaining to Fatima, who’d arrived from Somalia six months earlier, how to interpret the color-coding system he’d figured out in the planogram. His English was broken, her English was improving, but through gestures and pictures drawn on receipt paper, communication happened. I realized our crew possessed collective knowledge we weren’t sharing systematically.

I didn’t have any official authority—I was the youngest, newest hire, still in high school. But I had an idea. I asked Luis and Fatima if I could borrow their visual diagram system. That night, I created a simplified one-page visual guide to the planogram using symbols instead of technical language: arrows for direction, colors for departments, numbers for aisle sections. At the next shift’s beginning, I nervously presented it to the crew.

The reaction wasn’t grateful enthusiasm. It was skepticism and some resentment. “Who made you manager?” Chen asked. He wasn’t wrong—I’d presumed authority I hadn’t earned. But Luis backed me up: “It’s just helping. Try it one night.” The visual guide helped, but more importantly, it created space for crew members to contribute their own insights. Yuki suggested rotating partners so everyone learned from everyone else’s techniques. Ming proposed brief pre-shift meetings to coordinate. Ahmed, who’d worked retail management in Egypt, offered to translate the planogram into clearer sections for English language learners.

Within a week, we’d transformed from eight individuals working parallel to an actual coordinated team. We completed the reorganization two days ahead of schedule. More significantly, our improved efficiency meant finishing stocking by 5:30 AM instead of 6:45 AM—giving everyone extra paid time for side projects or rest. Productivity metrics improved 23%. Dave noticed, praised us in an email, never asked how it happened.

The overnight shift taught me that leadership isn’t about formal authority or brilliant individual solutions. It’s about recognizing collective intelligence that exists within groups and creating structures that allow that intelligence to organize and deploy itself. It’s about having enough confidence to propose ideas while remaining humble enough to step back when others contribute better ones. It’s about understanding that the people doing the work often know more about how to improve the work than managers watching from remote locations.

As a first-generation college student from a working-class immigrant family, I’ve learned leadership not from textbooks or elected positions but from the practical necessity of solving problems with limited resources and diverse teams. This scholarship represents opportunity to bring that hard-won understanding of grassroots leadership into academic study of organizational behavior and labor relations. The overnight crew at SaveMart didn’t need a manager. We needed someone to help us recognize what we already were: capable, experienced people who just needed better ways to work together.

When I joined TechFlow Manufacturing as a project manager in 2022, the company had spent $2.3 million on a new enterprise resource planning (ERP) system that sat 40% implemented after eighteen months. The production supervisors I needed to train on the system weren’t just reluctant—they were actively hostile. “Another corporate initiative that makes our jobs harder,” one supervisor told me in our first meeting. “You’ll be gone in six months like the last three project managers. The system will fail like it deserves to.”

He wasn’t wrong to be skeptical. Previous implementation approaches had been top-down mandates: attend training sessions, use the new system by deadline, adapt your workflows. No one had asked the supervisors what they actually needed or why the current system worked for them despite being antiquated. The ERP project had become organizational shorthand for “management doesn’t understand production.”

My initial instinct was to power through—set deadlines, mandate compliance, escalate resistance to senior leadership. That’s what my project management training suggested: establish authority, drive toward milestones, overcome obstacles. But three weeks of escalating tension and zero progress made me recognize that I was treating a people problem as a technical problem.

I cancelled the remaining mandatory training sessions and instead asked each supervisor for an hour of their time—not to train them, but to learn from them. I asked them to show me their current workflows, explain why they worked, and identify what they feared losing in the transition. Over two weeks of shop floor conversations, patterns emerged. The supervisors weren’t resisting change—they were protecting workflows they’d optimized over years to meet production targets management had imposed. The ERP system, as configured, would eliminate shortcuts that kept production running during equipment failures or supply chain disruptions.

Armed with this insight, I did something project managers aren’t supposed to do: I advocated to reconfigure the expensive ERP system around the supervisors’ workflows rather than forcing supervisors to adapt to the system. This meant customizing modules, extending timeline, and arguing to senior leadership that our initial approach had been backwards. “We bought the system to improve production efficiency,” I told the VP of Operations. “But our supervisors have already optimized for efficiency within current constraints. We should adapt the system to preserve that knowledge.”

The VP was skeptical but gave me three months to prove the approach. I formed an implementation team with three supervisors as co-designers rather than end-users. We mapped their existing workflows, identified which ERP features would enhance rather than replace their practices, and configured custom dashboards that gave supervisors control they lacked in both old and initially-proposed systems. For the first time, supervisors saw the ERP not as a threat but as a tool that amplified their expertise.

The results exceeded expectations. Within four months, we achieved 87% system adoption—up from 23% under previous approach. Production efficiency metrics improved 14% in first quarter post-implementation. Most significantly, supervisors became system advocates. When corporate visited to review the project’s turnaround, supervisors demonstrated features and improvements they’d helped design. The resistant supervisor from my first meeting now leads ERP training for new hires.

The project taught me three lessons about leadership that I’ll bring to Booth and beyond. First, resistance is often legitimate feedback disguised as obstruction—the leader’s job is decoding the underlying concern. Second, authority derived from position is less powerful than authority earned through demonstrating respect for others’ expertise. Third, successful change management isn’t about overcoming resistance; it’s about transforming potential resisters into co-creators who have genuine ownership of outcomes.

My leadership style previously emphasized driving toward goals efficiently, viewing obstacles as problems to overcome. This experience showed me that sustainable organizational change requires slowing down initially to build genuine buy-in, sharing control rather than consolidating it, and recognizing that frontline workers often understand operational realities better than project plans reflect. At Booth, I’m particularly interested in organizational behavior coursework that will deepen my understanding of change management, stakeholder engagement, and leadership approaches that build coalitions rather than mandate compliance.