VISend JD
← Blog

Huy Bạch · 7 min read
  • Leadership
  • Story

Some afternoons I wear all four hats before dinner. Each one is hard in its own way. Wearing them together is hard in a different way entirely.

9 a.m.: a call with the client to pin down the delivery date. 10 a.m.: writing user stories for the next release. 2 p.m.: reading a pull request that looks worse for the architecture with every file. 5 p.m.: someone on the team asks for a quick chat and opens with “Do you have five minutes?”, which every lead knows is never five minutes.

I didn't write a single line of code that day. I got home more tired than after a week of crunch.

Four meetings, four hats: Project Manager, Product Owner, Tech Lead, Team Lead. I didn't put them on all at once. They arrived one by one, over a few years, and each one taught me something different.

The PM hat: promising with numbers you don't control

The first hat was Project Manager, on a project for an outside client. I managed the project, wrote full-stack code, deployed it and kept the servers running.

The hard part of being a PM isn't the timeline spreadsheet. It's that every time the client asks “Will it be ready?”, you answer with a number you don't fully control: the team's pace, bugs nobody has found yet, the new request that will show up next week.

And because I was also writing code, I fell into a very common trap. When we slipped, instead of sitting down with the client to talk about scope, I quietly made up the difference with my own evenings. It worked. A few times. Until I realised evenings are not a resource you can plan with.

What the PM hat taught me: the best “yes” usually comes with an “if”. “Yes, if we move this part to the next round.”

The PO hat: saying no to good ideas

When I added the Product Owner hat, I assumed the hard part would be coming up with features. It was the opposite. There are always too many ideas. Teachers want one thing, students want another, guardians want a third. And I had my own list too.

The hard part of being a PO is saying no. Saying no to a bad idea is easy. Saying no to a good idea, just because it isn't time yet, is hard. Especially when the person who suggested it is sitting across the table.

What helped most was writing the reason down. Not “later”, but “not now, because this release is about teachers assigning work, and this doesn't help with that”. People can live with a no that has a reason. A “later” gets asked about again every sprint.

The Tech Lead hat: being right isn't enough

Tech Lead was the hat I thought I understood best, because I came up through code. Its first lesson had nothing to do with code: being right isn't enough.

I can be right about an architecture decision. But if the team doesn't understand why, the next time a similar situation comes up they'll wait for me to decide again. I become the bottleneck of the very system I designed.

The harder lesson was letting other people decide in ways I wouldn't have. Once, a developer proposed an approach completely different from mine. Not wrong, just different. I was about to rewrite the whole direction in a review comment. In the end I asked two questions about edge cases and approved it. It worked fine. And they remember that decision as theirs, not mine.

The Team Lead hat: people don't have a roadmap

The last hat, and the one I find hardest: Team Lead. Not leading the technology, leading the people.

Code has tests. Products have roadmaps. People don't. One very strong developer on the team slowly went quiet. PRs still came in, quality was still fine, but the comments got shorter and the questions in meetings got fewer. No ticket reports that. I only noticed because something was missing.

In the one-on-one that followed, they were honest: same area for too long, feeling stuck. Nothing dramatic. But if I hadn't asked, a few months later the next thing I'd have received was a resignation letter. The week after, they picked up a harder piece of work in a new area. I took on a bit more schedule risk. Worth it.

What the Team Lead hat taught me: people problems never show up in Jira until it's too late. The monthly review isn't for grading anyone. It's the only place you hear the things nobody writes as a ticket.

When the four hats argue

Wearing each hat is hard. Wearing all four at once is hard in another way: they argue. The PM in me wants to keep the date we promised. The Tech Lead in me wants a sprint to pay down debt. The Team Lead in me can see everyone is tired. And the PO in me has already promised users something.

One small habit helped a lot: saying out loud which hat I'm wearing. “As PO, I want this in the next release. As Tech Lead, I'm worried this part turns into debt.” It sounds a bit silly. But the team immediately knows what I'm weighing, and they push back in the right place.

I also learned to take hats off. The first one to go is usually the one only I believe I have to wear. Reviewing every PR alone is an example. Now other people, and a bot, share that hat.

I don't think anyone should wear all four hats for long. But because I have, when I sit in a meeting now I understand what the PM is worried about, what the PO is being squeezed on, and why the developer in the corner is quiet today. For a Tech Lead, I think that's the most valuable thing you can bring along.

Contact

Looking for a Tech Lead?

I want to own the technical direction and help a team ship products that matter.

huybn.dev97@gmail.com