Topic on User talk:Guillom/Roles and responsibilities

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?

This post was posted by Trevor Parscal (WMF), but signed as Trevor Parscal.

The goal is clearly not to restrict or to prevent people from doing stuff that isn't listed in their responsibilities. The goal is to have accountability and make sure everything gets done. In the end, it doesn't matter if you end up doing someone else's work (as long as they know it and agree with it), as long as someone is responsible for getting that work done.