Yeah thatās a good summation. I donāt see it as my place to micromanage my team on how they communicate between each other their tasks, works or collaboration. So in my scenario and environment if Iām seeing Asana tasks complete leading to project closure, with good quality and timely delivery, Iām not going to actively chase down where all the communications is happening and how.
If my team flag to me issues with communication, or if I see a trend of Tasks and Projects slipping, or having poor quality and delivery, I then might look into providing guidance or decisions on where collab should take place.
Because I guess itās at this point Iām looking at the specific communications and discussions. So if I see it spread across Teams, email, Asana and other platforms, maybe then Iād be in the mind to say āHold on guys, I spent more time trying to find your messages than actually reading them, lets get them all through Asanaā
At the moment Asana messaging for us sees a really good use for escalation or grabbing attention. But our teams day to day comms still goes through Teams or Email.
Shhhhhhhhh! My team has NO IDEA that Asana tasks can be created from Slack!!! 
Most project members love Asana after seeing how it can manipulate their personal tasks so the whole team can be transparent and on the same page. Are we talking about work or doing work? that was the ongoing question brought up when first training with asana in my group. Which later actually helps prove how useful Asana is in comparison to the others in mainstream like slack.