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

So all of the ways that we thought about our product strategy, how we conducted interviews, who had to do the interviews, the types of questions we asked in the interviews.

I'm happy to share all of that.

And you can definitely connect with me on that later.

So we basically got all hands on deck until necessary.

So we had to have our sales and product leader, our sales leaders conducting really informative sales conversations when we were talking to new business opportunities.

So really getting their input on what their exact pain points were, what they were looking to solve and kind of like what they needed.

We didn't really talk about what we offered in Simba until we heard what exactly they needed.

Biggest lesson learned was we also fostered empathy and we lowered the ego of the product and engineering team.

something I want to talk about this here is that engineers have to feel that they're building a product that supports, that they're building a product and product needs to support that with data.

Over communication is really important as to why a feature needs to be developed and it has to be there because only when the engineers understand the value of the product that they're building, then they will be able to build it with

empathy and understand what the users are going through.

So that was a big surprise for us was that before, and originally what we were doing was that we were giving our engineers just designs and telling them whip out these features in the next six weeks because we need them, our customer needs them by this date.

But instead, we actually sat down with them, we shared them the GOM recordings of the interviews that we were conducting,

they heard from those users or the potential customers firsthand that we need this because it's going to help us solve XYZ.

And when they started to understand that there's actually a need for this feature that they're building, that's when they got more excited about it.

And that helped them bring the entire team

to alignment.

We also, depending on what stage you're at, you also, and evaluating the resources that you have available, it's also important to understand to, it's important to understand to what extent you want a certain feature to be built.

Is it allowed for the engineers to create a simplified version in terms of the design, so long as their customer is able to do, or able to succeed in the original mission of that feature, as well as get to A to B?

But what kind of trade-offs are there?

Showing 101–120 of 173 · page 6 of 9