Your link to the AX framework article led me to read Dive#98. Curious to hear your thoughts on the evolution of RTFKT's commnuication strat, especially considering the community backlash regarding execution, but also their communication?
Lots of nuance, but one way to think about it is there are communication best practices but also each team/project has a different communication style, one of the dimensions being how often and how detailed.
RTFKT tends to be pretty quiet until there's a larger development where they build up GTM and announcements for. That approach is great when it happens but leads to a long quiet periods. Feels like that's their general approach and they've accepted the pros/cons that comes with it.
That said that's for the average community member. I think if you're a RTFKT Creator it's a richer ecosystem and somewhat diff comms approach.
Your link to the AX framework article led me to read Dive#98. Curious to hear your thoughts on the evolution of RTFKT's commnuication strat, especially considering the community backlash regarding execution, but also their communication?
Lots of nuance, but one way to think about it is there are communication best practices but also each team/project has a different communication style, one of the dimensions being how often and how detailed.
RTFKT tends to be pretty quiet until there's a larger development where they build up GTM and announcements for. That approach is great when it happens but leads to a long quiet periods. Feels like that's their general approach and they've accepted the pros/cons that comes with it.
That said that's for the average community member. I think if you're a RTFKT Creator it's a richer ecosystem and somewhat diff comms approach.