Most of our team is focused on delivering this new project. It's due in a month, and we haven't even really started the backend yet. I want to call out why I think we're so behind, but I don't if it will be well-received, or how to.

I have 3YOE (so barely made the cut here). I work in retail at Amazon (I know). Very doc heavy culture, and all that customer obsession jazz.

Basically, it's because my team loves talking way too much, but can't commit for shit. We didn't finalize the MVP until like last week, and there's still some debate. We bring up the same topics over and over again during meetings. We have too many meetings. We debate a lot, but no one shuts down bad ideas. We will spend a whole meeting debating and have no resolution at the end. And then do it over again on the same topic the next three meetings. We're also kind of stuck in design hell, where we keep iterating on designs.

This project is greenfield, has zero prod traffic, and zero prod data. It's isolated from everything else, and can't negatively impact other services. The data that we need is coming from one team. There isn't much "ambiguity" imo. But we have some strange obsession with having to nail everything before implementing.

It's just so dumb. Even if we don't have all the product specs, we still have a good idea on what we'll need for sure. and a lot of the technical debates we have are two door solutions that would take like a day to swap between options.

I basically want to mention this next sprint planning when we do retro, but idk if it'll be well-received by management. They love virtue signalling and citing customer obsession and all that. I know most engineers agree with me.