Working with junior techs taught me that clarity is kindness.

You can be technically right and still leave someone stuck. So I write error messages that tell people what to do next — not just what went wrong. I build systems that scale, not just patch problems.

Empathy isn’t a soft skill. It’s an operational advantage.

Photos

I’ve had situations where support techs asked me to generate reports — even though those reports were accessible through the same tools they use every day. At first, I treated it like a quick favor. But over time, I realized those favors created dependence, not enablement.

So I stopped doing the work for them, and instead nudged them to the vendor or to training resources. It wasn’t out of frustration — it was to protect their growth and keep the support system sustainable.

Another moment came when building workflows in Freshservice. I noticed how easy it is to build something clever that only one person can understand. Instead, I started asking myself:

“Will this make sense six months from now — even if I’m not here?”

I documented logic in plain terms, designed for adaptability, and structured workflows that junior techs could expand on — not just use.

That’s when I realized: I wasn’t just solving problems. I was building systems meant to outlast me.

🧠 Reflection:
Leadership isn’t always loud. Sometimes it’s in the details — in how you name a variable, write an error message, or decide when to say no.
Lead with logic, but guide with empathy. That’s how you help others level up — and how you build trust that lasts longer than any ticket.