I started as a Tech Lead thinking that everyone else knew what this job is about better than I did.
I did reports that were not mine to do.
I attended meetings that were not for me to attend.
Anything that came my way, I took it on.
I told myself: “They must know better what being a Tech Lead means.”
Underneath that was fear.
Fear I was not good enough.
A need to prove myself.
A need to feel useful.
Unaware of any of it.
So I worked 10, 12, sometimes 14 hours a day.
I was exhausted.
But I was young, so I pushed through.
I thought I could keep pushing.
I was wrong.
I still carry back problems from those years.
Lack of role clarity is one of the biggest contributors to burnout.
And it is not only about burnout.
It is also about losing sight of where you truly get satisfaction as a Tech Lead.
I kept chasing it in fixing bugs and completing tasks.
I wish someone had told me:
Caring does not mean working 12 hours a day.
You deserve clarity, so go get it!
Imagine knowing exactly what is yours to do, and what is not.
Imagine balancing coding and the other responsibilities in a way that helps you instead of draining you.
Imagine finding satisfaction in your Tech Lead role, without burning out.
That clarity is possible. And it changes your work life.
That is exactly what we will explore in the Tech Lead Role, Decoded workshop.
You will get clear on how to get clear on your responsibilities and what others expect from you.
You will learn how to balance coding and leadership so you do not burn out.
You will discover where your sense of satisfaction as a Tech Lead really comes from.
If this speaks to you, join me. Registration details here.
And feel free to forward this to a Tech Lead you know who could use some clarity.
I believe in you.