One issue that I've experienced is the sharing of work well before it even reaches the implementation phase so that other designers can offer feedback. We've tried wake but it's a little too loose and is essentially a Pinterest board with commenting, and when integrated with Slack the comments still get lost between the channel and the platform. Another tool we're trying is redpen.io which offers a bit more structure and context into the feedback.
I don't believe that where you store your assets is where the critique and feedback should live because I believe designers are inherently too keen on sharing complete and perfect work. I'd rather see a very rough sketch or prototype based on a problem/thought and immediately comment than go through different versions of assets because that's the point where the most important decisions are actually made
On the product side if you're creating a new feature or redesigning an existing experience, it's better to have an idea of what you're trying to solve and create a very very rough prototype that can be shared. If you're commenting on Github commits I think that's too late in the process to have meaningful feedback - it should be more about the implementation and technical opinions at that point and less about the actual design.
One issue that I've experienced is the sharing of work well before it even reaches the implementation phase so that other designers can offer feedback. We've tried wake but it's a little too loose and is essentially a Pinterest board with commenting, and when integrated with Slack the comments still get lost between the channel and the platform. Another tool we're trying is redpen.io which offers a bit more structure and context into the feedback.
I don't believe that where you store your assets is where the critique and feedback should live because I believe designers are inherently too keen on sharing complete and perfect work. I'd rather see a very rough sketch or prototype based on a problem/thought and immediately comment than go through different versions of assets because that's the point where the most important decisions are actually made
On the product side if you're creating a new feature or redesigning an existing experience, it's better to have an idea of what you're trying to solve and create a very very rough prototype that can be shared. If you're commenting on Github commits I think that's too late in the process to have meaningful feedback - it should be more about the implementation and technical opinions at that point and less about the actual design.