Ballot

Does your team send a Drumbeat? Is it worth it?

Created almost 2 years ago
1126
I like seeing the Drumbeats from other teams, and I like the responses I get to our Drumbeats, but I'm not sure that I'm making them correctly. I'm in favour of individuality and innovation, but knowing what I really should include and what isn't important (or even interesting) is hard.Created almost 2 years ago
3 people found this
I read some of the drumbeats - those that I think have an impact on our work. I suspect and hope Pivnet's drumbeats are useful for internal teams, as much of our work supports internal teams (in addition to the work we do for customer users).Created almost 2 years ago
3 people found this
The drumbeats are valuable for the internal awareness and engagement we get from them, and I know that people who have a stake in our product read them. I do not read other teams though, unless I have a dependency on that team. I find once every two weeks to be more sustainable and to reflect more significant chunks of work and so often fall back to that.Created almost 2 years ago
0 people found this
occasionally we get comments thanking us for sharing information. but it's not necessarily consistent. sometimes the drumbeats don't seem to have much engagement.Created almost 2 years ago
0 people found this
I already have several mediums via which I must share my project status (CF PMC, project release notes, CF-release release notes, KPL, tracker, Aha), so I am reluctant to volunteer to write another status report that has not been explicitly asked of me.Created almost 2 years ago
0 people found this
The drumbeat emails are the only classification of email that I have an auto-archive filter for. The information density is far too high for the relevancy factor of them.Created almost 2 years ago
0 people found this
it's easier now that we've significantly thinned down what we report on the drumbeat. we did a survey waay back (a year from yesterday!) when on what people want/expect out of the drumbeat: (stack rank Likes: 1) Dates, 2) TL;DR / stay informed, 3)status of releases, 4 sharing blockers / issues) ... but not sure if needs are still the same or if the needs have shifted, since people may be getting these answers elsewhere. There are also a lot more drumbeats so unsure if people are experiencing drumbeat fatigue.Created almost 2 years ago
0 people found this
Every PLM or Support drumbeat generates two or three interesting replies. Sometimes I find out about new resources or challenges, and sometimes I find a new ally. Created almost 2 years ago
0 people found this
The CloudOps drumbeat e-mails have gotten a lot of positive responses, started good conversations, and are a useful way to make the broader R&D org aware of challenges (or neat stuff) that CloudOps encounters. Compiling the drumbeat is also useful for me (as a historical record of what happened in a given week).Created almost 2 years ago
0 people found this
We get feedback and comments and it has definitely helped to provide context for various parts of PCF to communicate. For example, PAs or other parts of R&D often reach out afterwards. Created almost 2 years ago
0 people found this
I read about half of them. They help me stay connected to what the teams are up to. Created almost 2 years ago
0 people found this
They’re worth it as PA/PCFS consume them as source of truth. I wish more people would read them, esp. directors and product leads.Created almost 2 years ago
0 people found this
I do think it's worth it but I don't regularly do it.Created almost 2 years ago
0 people found this
Vote Now