Nikita Gupta

speaker

173 appearances 1 recordings 1 series first heard Jul 2023 last heard Jul 2023

Nikita Gupta’s voice in public audio — every appearance, attributed to the second.

Trend

recordings per month · last 12 months

No recordings in the last 12 months.Older appearances are listed below; set an alert to hear about the next one.

Appearances

newest first · ▶ plays the moment

Top Founders · Product vs. Engineering: The surprising way to create alignment in 2023 · 11 Jul 2023 podcast

How are we going to evaluate some of the bottlenecks and understand the signals and act fast?

So what is the bottleneck and how to spot some of these signals?

So thinking that product versus engineering is really that simple is going to be one of the first causes of a bottleneck.

The lack of new features being pushed to production, which means that there's no increase in revenue or no customers that are wanting to come because of the lack of innovation is also a good indicator that there is a problem going on.

There's also very little trust between the product and engineering teams and lots of excuses and blame and finger pointing.

So the product team is, they want to establish a list of projects, aka the roadmap, and they're responsible for working with various stakeholders.

So we got to get the sales and the marketing into play as well.

But engineers, on the other hand, have to bring this roadmap to life.

And they're the ones that build the stuff that works, but they not only have to think about what individual projects they have to work on, they also have to keep in mind the technical debt.

And sometimes there's delays that happen, and it

It causes a domino effect, and it's not as easy as just putting duct tape and a Band-Aid onto the problem and moving on to the next one.

So there's a lot of tension coming in, and this is what helped our team understand that there was a bottleneck because we were not delivering features, and there was no clear understanding between product and engineering on what we were trying to sell and how to be innovative.

So this happened because our product leaders were throwing requirements over the wall and treating our engineering team like a feature factory.

Like I said, one feature a month for the next 12 months.

We need this.

This is it.

There's no understanding of why features are being built.

Product team was also canceling projects without any prior indication because of some of the KPIs that weren't being met.

And engineering teams continuously missed delivery dates without warning that may have happened due to other delays.

So there was definitely an imbalance here.

Showing 61–80 of 173 · page 4 of 9