What information should be shared within the team
On any project team, it's incredibly important to share:
- failures and mistakes
- obvious things and solutions
- useful innovations and opportunities
đ§ Failures and mistakes
If something happened once, a chance it will happen again at least exists. If the same mistake happens again to different employees, those employees or their managers will spend time working through the consequences of the mistake that could have been saved if they had worked through the mistake the first time around
đ¯ The obvious things
There's so much information and tools surrounding us that there's no shame or embarassment in not keeping up with everything. Getting into the habit of sharing some obvious useful finds within a team can improve its overall efficiency
đšī¸ Useful new things
If all of Facebook or Twitter is talking about a new AI-tool or book, it just means that your sector of those social networks is talking about it. This information could very well pass someone by - and it should be shared if it's potentially useful
It sounds elementary, but in order for this to work in an organisation, there needs to be an appropriate culture: so that employees don't try to hide their mistakes for fear of punishment or slanted glances; so that there is no ridicule of colleagues for saying something obvious; and so that there are channels for sharing this information.
And building that culture is the responsibility of the leader. Well.
