1. Leadership isn’t about knowing everything

Let me tell you, I didn’t have all the answers and that’s okay! I quickly realized that leadership doesn’t mean being the smartest person in the room. Instead, it’s about being open to ideas, asking the right questions, and making sure everyone feels heard.

There was a moment early on when our team hit a roadblock. The prototype we’d been working on wasn’t resonating with users, and honestly, I felt like I’d failed. But instead of trying to “fix” everything myself, I gathered the team and said, “Let’s figure this out together.” That one conversation turned everything around. It reminded me that leadership is about guiding, not controlling.

2. Communication is your superpower

If there’s one skill that saved me time and again, it was communication. Whether it was explaining my design decisions to stakeholders or clarifying project goals for the team, I learned how important it is to communicate clearly and confidently.

I remember one meeting where I had to present our design to a group of stakeholders. My hands were practically shaking as I clicked through the slides. But I grounded myself by focusing on the “why” behind every decision: Why this layout? Why this color scheme? Why this feature? By connecting each decision to user needs and research, I gained their trust—and walked out of that meeting feeling ten feet tall.

3. Agility is everything

Spoiler alert: Things rarely go as planned. Designs get scrapped. Feedback changes the scope. Deadlines shift. I learned pretty quickly that being rigid only makes things harder.

There was this one feature we all loved a cool interactive element we thought users would adore. But during usability testing, it flopped. People found it confusing, and it didn’t add much value. It stung to let it go, but we pivoted, simplified the design, and moved forward. That experience taught me to view feedback as a gift, not a setback.

4. Own your mistakes (and learn from them)

I’m not going to lie there were moments when I dropped the ball. Like the time I misunderstood a stakeholder’s feedback and sent my team in the wrong direction for a week. When I realized the mistake, I felt awful.

But instead of beating myself up, I owned it. I called a team meeting, admitted the error, and we regrouped. To my surprise, my team appreciated the transparency, and we quickly got back on track. That moment reinforced a simple truth: mistakes happen. What matters is how you handle them.

5. Growth happens outside your comfort zone

Leading this project stretched me in ways I didn’t expect. From handling tough conversations to managing timelines, I was constantly stepping into unfamiliar territory. It wasn’t easy, but it was worth it.

By the end of the project, I looked back and realized how much I’d grown—not just as a designer, but as a collaborator, a communicator, and a problem-solver.

If you’d told me a year ago that I’d lead a design project and live to tell the tale, I probably would’ve laughed nervously and changed the subject. But here I am, sharing this story with you.

Taking on a leadership role as a junior designer wasn’t just about completing a project it was about discovering what I was capable of. So, to anyone out there wondering if they’re ready to lead: You are. Say yes, lean into the discomfort, and trust that you’ll figure it out along the way.