3 ms·
This makes a lot of sense at deep tech places that don't sell to enterprises where one can put their head down and just work on technical challenges. A similar
by wavelander 3y ago
This makes a lot of sense at deep tech places that don't sell to enterprises where one can put their head down and just work on technical challenges. A similar place like Mongo DB or the hardware division of NVidia comes to mind. But if you're supposed to iterate with any input from more than 2 people that isn't highly objective (technical metrics that can correlate well with product satisfaction), communication and diffused collaboration is important and necessary. That doesn't mean it has to suck. But the Netflix model you described isn't applicable everywhere and shouldn't be blindly replicated.
- gervwyk 3y agoThis. In our tiny company, Lowdefy, we try to distinguish when something is done as part of innovation, or as a deliverable or chore. The work that falls into the two categories are vastly different in nature, stakeholder expectations and outcomes. Being deliberate about what category of work you are busy with provides freedom to thrive when innovating required while introducing the structure needed when deadlines are on the table. Mixing the two results in frustration and reduces quality and output. I would be interested to know if this applies same to larger orgs?