When Your Engineers Fight For Your Product (You Know You've Won)

I just did another PBR with my team (Product Backlog Review, for those unfamiliar). After we wrapped up, I had to recognize something: I am so lucky to be working with this engineering team.

Everything can be summarized in one phrase: Having engineers ready to fight for your product.

The Theory vs. The Reality

In theory, we all know the deal:

• Product defines the why, the what, the vision, the strategy
• Engineering discusses the how—the execution

But that’s on paper.

In reality, we’re all human. We all have opinions (which is actually good). Sometimes from the product side, you want to impose a solution. Sometimes from the engineering side, they push back: “This vision isn’t good for reasons X, Y, Z.”

When You’ve Won: Engineers Fighting For Your Vision

When engineers are willing to fight for your vision—that’s when you know you’ve won. And that’s what happened today.

It means a lot:

1. You’ve Created a Healthy Relationship

There’s trust. They listen. They want to go the extra mile.

2. Your Vision is Compelling

You communicated it so well, it’s so exciting, that they’re willing to do extra work to make it happen.

3. They’re Not Just Software Engineers

They’re developers in the truest sense—not just writing code, but deeply understanding your use case.

As I like to say: They make your product dream come true.

My Current Company

At the company I’m working for now, I’ve had the pleasure of meeting an amazing engineering team. Amazing colleagues who work hard to achieve our vision (not just “my vision”—it’s our vision).

I’m proud of this.

The Question

Now, what if your team isn’t performing this way?

The questions are always the same:

• Are you sure it’s all about them?
• Maybe.
• What can you do from a product standpoint to prove value, convince them, show them the real impact?

Open question. Mic drop.