Mutual performance monitoring
If I was to pick two of these in which I had a positive experience it would be back-up behaviour and adaptability.
The context under which I was working at that time (2006 - 2010) was section leader for computing in an FE college. It was a medium sized department (15 - 20) teaching staff. There was a head of department and another 2 section leaders. Each section leader was responsible for leading their own curriculum area. I was responsible for managing the computer systems and networking curriculum and led a team of 6 teaching staff. I was also responsible for managing the college Moodle VLE.
Each of the section leaders had other responsibilities for example, quality processes and timetabling. Each SL was encouraged to learn about the other roles; we worked almost holistically and not in 'silos'. This was incase a backup was needed, so for example if the timetabler was not around and a member of teaching staff was off ill, another could access the timetabling system and organise class cover. We could each easily provide backup and adapt temporarily to the environment.
In our group, there will be allocated roles. It will be important however for us to use an effective communication mechanism, synchronous and/or asynchronous to let each other know what is happening - keeping each other in the loop in case we need backup and to temporarily provide support.
The key here for MAODE students is the synch/asynch communication solution and scheduling skills because not everyone will be able to meet (conference wise) at the same time due to large geographical spread.