Thread:User talk:Guillom/Roles and responsibilities/How can we clarify responsibilities without deteriorating cross-functional teams?

I can appreciate the desire for clarity, but expect that mapping this out explicitly could solve one problem but cause another. Telling people "this is exactly what you are expected to do" which is clarifying is strikingly similar to telling them "this is the only stuff you are allowed to do", which is problematic.

We have a large number of people on staff who have experience working professionally as, and often contribute as, a variety of roles. Most commonly we have developers who are also designers and designers who are also researchers.

So, how could we map out responsibilities without restricting people's contributions in diverse areas of projects and picking up slack when others fall behind?