You make very good points, and it's great to hear the experience from a smaller team :)
In our company, two of the devs in our full-remote team have been working here for more than 10 years (literally longer than anyone else), so they know the product down to the most minute details, and have happily spread the knowledge to our team.
So the funny part is that UX, design, or product-wise, we usually find a lot of edge cases that they didn't think of.
We have more than 100 million users (around 30 million are active), some have been using the product for a decade. It happened before that we didn't share our point of view directly with Prod/Design for fear of been too naggy, and guess what, support tickets flooded our staff when we released new features and a bunch of legacy functionality was not there.
We build things fast (some features that take other teams months take us weeks), so it has been hard for QA, Product, and Design to keep up.
This becomes quite frustrating so we have worked hard as a team to reduce the amount of criticizing (that's hard for me!), and to praise first. Usually there will be 10 to 30 missing details that we will need to let them know slowly, without overwhelming them.
This considerably slows down development, so I've resorted to doing documentation, refactoring, and developer-friendly features such as maintining our Storybook in the meantime.
Hurray for remote! π₯³π₯³π₯³
(BTW, not sure what is the best way to reach you or someone on your team, but I noticed getflow is using a development build of React, in case you want to check it out -> image )
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You make very good points, and it's great to hear the experience from a smaller team :)
In our company, two of the devs in our full-remote team have been working here for more than 10 years (literally longer than anyone else), so they know the product down to the most minute details, and have happily spread the knowledge to our team.
So the funny part is that UX, design, or product-wise, we usually find a lot of edge cases that they didn't think of.
We have more than 100 million users (around 30 million are active), some have been using the product for a decade. It happened before that we didn't share our point of view directly with Prod/Design for fear of been too naggy, and guess what, support tickets flooded our staff when we released new features and a bunch of legacy functionality was not there.
We build things fast (some features that take other teams months take us weeks), so it has been hard for QA, Product, and Design to keep up.
This becomes quite frustrating so we have worked hard as a team to reduce the amount of criticizing (that's hard for me!), and to praise first. Usually there will be 10 to 30 missing details that we will need to let them know slowly, without overwhelming them.
This considerably slows down development, so I've resorted to doing documentation, refactoring, and developer-friendly features such as maintining our Storybook in the meantime.
Hurray for remote! π₯³π₯³π₯³
(BTW, not sure what is the best way to reach you or someone on your team, but I noticed getflow is using a development build of React, in case you want to check it out -> image )