VISend JD
← Blog

Huy Bạch · 5 min read
  • Product
  • Story

Being Product Owner and Tech Lead at the same time means some debates happen entirely inside your own head.

There's one planning meeting I'll always remember. Not because it was tense. But because the person who pushed back on me hardest in the room that day was me.

As Product Owner, I wanted that feature in the next release. Users had asked for it many times, and I had promised. As Tech Lead, I knew full well that making it in time meant cutting a corner through part of the architecture, which the whole team would pay for later.

There was no one to blame. No "product is pushing too hard" or "dev keeps saying it's difficult". Just me, a deadline, and a decision.

An unexpected advantage

At first I thought holding both roles was a burden. It turned out to have an unexpected advantage: every argument between product and engineering had to happen in my head first, before it reached the meeting room.

That day I chose to cut scope. The next release would have only the part users needed most. The rest would go in a later release, when there was time to do it right. I wrote down the reasons, clearly, so the whole team understood why.

The part that got cut, I removed from the document entirely, without leaving a "later" item dangling. I've seen too many documents with items like that, sitting there until no one remembers what they meant.

The PRD nobody read

Another habit I had to drop in the PO seat: writing PRDs like writing code.

Engineers writing PRDs tend to stuff in service names, field names, endpoint names. It feels rigorous when you finish. Send it to the business side for review and you get a very long silence back.

Since then I keep one reminder: a PRD that the business people can't understand is a tech spec dressed up as a PRD. Now my PRDs call features by the name shown on screen, and answer only four questions: who, does what, to get what, under what rules. Technical details are still there, but they live on the task page.

Open the code first

The biggest advantage of knowing the code as a PO: before writing a user story, I open the code to see whether the feature already exists.

It sounds obvious. But duplicate stories, written only because nobody checked whether that screen already existed, happen more often than people think. Every redundant story is a few days of the team's time burned on something that's already there.

Doing both roles at once isn't easy. Some days I have to ask myself: am I saying this as PO or as Tech Lead? But if I could choose again, I'd still choose to sit right where product decisions and their technical cost meet.

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