What if we called them "experts" instead? It needs to be clear to newcomers that they're the go-to people for certain tasks within the design team, and that requires a semi-formal mention on e.g. the wiki.
2014-06-19 18:14 GMT+02:00 Michael Meeks <michael.me...@collabora.com>: Hi Mirek, > > On Thu, 2014-06-19 at 17:56 +0200, Mirek M. wrote: > > Astron told me that the idea to have positions within the design team > > was not well-received and that I should discuss it with you. What do > > you find problematic about having positions within the team? > > :-) so - it's a good question. In my experience putting a badge > marked > "Leader" on someone doesn't per-se make them a leader - indeed, you know > who the leader is by whether they have followers; indeed - putting the > badge on the wrong person bears significant risk. > > > To be clear, leads would be there to make sure that things get done, > > that the process by which they get done produces the best results, and > > to resolve controversial issues if they arise. > > Of course, if the team want to informally agree that people have > responsibility and/or deeper wisdom in certain areas and defer to their > insight there - then surely that makes sense :-) eg. in the code we have > subject area experts who are listened to more than elsewhere. > > Does that work for you ? of course, you can call each other what > you > like =) I'm just concerned about the "team lead" description spreading > and/or being used by people to describe themselves in slides, > collateral, cards, marketing etc. =) Can the same thing be achieved > without a semi-formal title ? > > ATB, > > Michael. > > -- > michael.me...@collabora.com <><, Pseudo Engineer, itinerant idiot > >
