about writing building hire me now contact Work with me →
← All writing
Lessons

How I went from intern to Team Lead without a plan, just principles

There was no roadmap. There was a process, a bias toward ownership, and a consistent refusal to wait for permission.

Jun 2026 · 2 min read
Technology professional organizing documentation, workflows, and system knowledge that grows into team trust and leadership

People ask for the roadmap. I don’t have a neat one. I didn’t set out to become Team Lead on a timeline. I didn’t copy a LinkedIn playbook. What I had were a few principles I kept applying — sometimes awkwardly, often imperfectly — until the role found me.

Principle 1: Own the problem, not just the task

Intern work is often defined as tasks. Do this ticket. Fix this bug. Update this doc. I tried to understand the problem behind the ticket — who it affected, what happened if we didn’t fix it, what we’d done before that didn’t work.

That curiosity wasn’t performative. It made my work better. It also made me the person people looped in when something was unclear.

Principle 2: Document what you learn

Every time I solved something non-obvious, I wrote it down — for the next person, but honestly for future me too. SOPs, notes, short Loom-style explanations. Not polished articles. Working memory the team could share.

Documentation scaled my impact without scaling my hours. That’s not a hack. It’s how teams survive growth.

Principle 3: Don’t wait for permission to care

I didn’t reorganise the company. I did fix small broken things without being asked: unclear handoffs, missing checklists, silent failures in workflows. I flagged risks early. I proposed process before code when code wasn’t the bottleneck.

There’s a line between initiative and overstepping. I crossed it sometimes. I learned. But the default of “someone else will decide” would have kept me waiting forever.

Principle 4: Make others successful

The shift toward lead work happened when my success stopped being measured only by my output. Did the intern understand the system? Did the client trust the release? Did the junior dev have a clearer path after working with me?

Leadership, I think, is mostly that — multiplied.

There was no roadmap. There was repetition: show up, understand the system, leave it better than you found it.

What I’d tell past-me

You don’t need a five-year plan. You need a consistent standard for how you work when nobody’s watching. The title follows that standard more reliably than the other way around.

I’m still learning what Team Lead means. The principles haven’t changed — the scope has.