People:removing roadblocks to productivity/project broken comms: Difference between revisions
(Created page with "==Broken or Too Many Communication Channels== Project manager: Sean Rich ===How to get involved=== ===What we heard=== ===Work already in progress=== ===Shorter term acti...") |
|||
| Line 6: | Line 6: | ||
===What we heard=== | ===What we heard=== | ||
Mozilla has grown up as a decentralized organization. That's the way we like it - innovation and contribution from the fringe. As we grow, however, the number of communication pathways increases and communication becomes harder. This leads to trouble keeping up on messages. It becomes more difficult to find information. Right now we are failing to provide and access the information people need to support the mission. We think that by centralizing information from various knowledge repositories and providing robust search capabilities across knowledge repositories we can improve the effectiveness of communication. Therefore, we are going to take a first step by exploring whether consolidating information between Mana and Intranet would be useful. We're also going to explore whether providing a centralized search function across Wiki, Mana/Intranet, etc might be useful. | |||
===Work already in progress=== | ===Work already in progress=== | ||
Revision as of 22:59, 7 May 2014
Broken or Too Many Communication Channels
Project manager: Sean Rich
How to get involved
What we heard
Mozilla has grown up as a decentralized organization. That's the way we like it - innovation and contribution from the fringe. As we grow, however, the number of communication pathways increases and communication becomes harder. This leads to trouble keeping up on messages. It becomes more difficult to find information. Right now we are failing to provide and access the information people need to support the mission. We think that by centralizing information from various knowledge repositories and providing robust search capabilities across knowledge repositories we can improve the effectiveness of communication. Therefore, we are going to take a first step by exploring whether consolidating information between Mana and Intranet would be useful. We're also going to explore whether providing a centralized search function across Wiki, Mana/Intranet, etc might be useful.
Work already in progress
Shorter term actions
These are things we expect to accomplish in 2014.
Longer term changes / shifts
These are things we expect will take time, influence, and repetition to shift.
Responses in this category
- Excessive amount of communication channels. 133 votes
- Finding information on the multiple intranets and wikis. 104 votes
- A not anonymous survey about removing roadblocks to productivity. Something we would never speak out is really hindering us, but it needs basic anonymous protection to publish. 65 votes
- Far too many communication channels to keep up on, requiring an inordinate amount of time reading, responding, and chatting at any given moment. 32 votes
- Mailing lists and newsgroups are terrible. As a result, we turn to even worse forms of communication, such as CCing four employees on an email. 21 votes
- MediaWiki (wiki.m.o, intranet) vs MANA -- why 2? We should prefer internally the tools we use with the community. 10 votes
- Scanning 100s of bugmail, mailing lists and newsgroups to try and keep abreast of the projects I'm involved in. 10 votes
- Intranet vs Mana: why 2? 7 votes
- We often don't even believe on our own tech that we try to push. FirefoxFlicks requiring Flash and or non-free video. Not using webrtc even a little, etc. 7 votes
- No clear communication channels on a per-project basis. 4 voteS