Do you include a lot of people in your emails and receive feedback that you shouldn't do that due to ESG considerations or if that leads to inbox clutter? 

Here are some reasons why you should include colleagues in your emails:

1. There are times when colleagues hate it that you don't keep them in loop even when they don't have any actionables as they want to feel part of the project and stay informed about each and every step of what's happening in the project. 

2. When an email trail is going on with a lot of people (relevant still), and a stakeholder sends out a request, even if you will 1:1 email to stakeholders that the particular request shouldn't be catered to, someone in the loop would still go ahead and take action on the request as they weren't informed about your 1:1 conversations. This can lead to funny situations. 

3. Leaders surely don't need to be included in all emails as their inbox would get insanely cluttered if everyone would start including them in cc but what about the high stake projects (which also is very relative as what could be potentially high stakes to you might be just a trivial for them).

4. In corporate everything must be document as when you are on line of fire, it's the trail of communications that becomes your sole saviour as even the lovely bosses won't be there to take your side or god forbid if they have left the firm before that. Nothing crazy really happens but to hold anyone accountable and during the times of escalations or when the corporate is turning against you, these could be really useful.

5. Keeping people in cc reduces depedency. For example, you (a digital marketing person) are working with a content writer, a designer and a stakeholder. Now either content writer can work along with the stakeholder directly without keepinng designer and you in cc, or designer can do the same and so can you. The trouble starts when either of them goes away and you are stranded as you don't know the status of something and you want to follow up with the stakeholder to get the required information. It just causes a big mess, therefore, when you are working on a project closely, always include people in cc so that dependency is reduced and everything is kept informed.