ALV-9-May-2014 lessons

From Technologia Incognita
Revision as of 08:59, 10 May 2014 by Becha (talk | contribs) (Created page with "Lessons learned =What went right= * being very organised: having clear deadlines, clear rules, communicate in advance * reviewing the agenda points WITH the proposer, to cla...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Lessons learned

What went right

  • being very organised: having clear deadlines, clear rules, communicate in advance
  • reviewing the agenda points WITH the proposer, to clarify the text
  • having the time period between the deadline for votable points, and announcing the agenda
  • sending reminders, often
  • LOCKING the draft agenda to prevent editing by random "contributors" (because then the changes get un-noticed by the secretary)

What can be improved

  • add an agenda point - half-hour before the end of ALV - "NEW ACTION POINTS"
    • PLAN this into the time for the whole ALV
    • STOP the ALV half-hour earlier, and go through the new action points
    • this would make it clearer for everyone what are they suppoused to do after
    • alternatively, or in addition, add "FORMULATE AN ACTION POINT" (what, who, deadline) after each votable point
  • INCREASE the time period between the deadline for votable points and the announcement (now it was only 3 days, due to the circumstances of travel of two board members) -- two weeks would be better -- PLAN that into the scheduling!
    • this would give
  • be even more organised!!!
    • PLAN the next ALV MUCH MORE IN ADVANCE!! e.g. 3 months in advance!!
    • DOCUMENT the planning procedure!!
  • REPEAT repeat repeat
    • make it even more clear to the members HOW the process should work, and WHY
    • do this in person! not only on email!
  • add the "duration of ALV" in the planning
    • every time we say "this is not needed", and every time we end up cutting the ALV because "it's getting too late", "it's been going on for too long".
    • lets learn from this -- no-one can stand to sit at the meeting longer then 5 hours!!
  • be MORE STRICT when accepting points!
    • DO NOT Accept too many points!!
    • accept that it is OK to REJECT the points, on account on: it is not well formulated - try again; it was not discussed before on the list; there are too many other points, sorry, wait for the next ALV
    • (personal opinion: suggest that some proposed points can be resolved IN REAL LIFE, without voting for them... but by talking to the fellow members, seeking consensus rather then majority, talking at the members meetings, or in the Circle...)
    • INSIST on the points being discussed before they are submitted to the agenda!
  • DO NOT accept any changes after the deadline!! (example: Philip's "Addendum" to Wizzup's point) (example1)
    • (Q: what will be the additional two weeks period be used for, then??)
    • (A: word-smiting of the submitted points, ONLY between the maintainer & the secretary/board)
    • (Q: do we need to split this into "one week when the changes will still be accepted, and one week lock-out?")
    • (A: NO -- the "3 days" should be "two weeks", so that the board does not get burned-out with the pressure & stress of working in the last moment! )
    • AFTER the deadline, maintainer has the responsibility to chase the board to make any additions, that he/she has gotten from the community.
    • the board has the responsibility to make the clarification of the submitted points TO THE LEVEL OF CLARITY that they require
    • the board has NO RESPONSIBILITY to read through the mailing-lists or wiki-pages-history to "fish" for the additional points!! (example1)


  • ask the "maintainer" of the point to add it to the wiki page
    • each point can have a separate wiki page, not the "draft agenda"
    • it will be linked from the draft agenda
    • this page can be used for discussion / additions / smiting / collecting support / alternative version .... BEFORE the deadline!
    • AFTER the deadline, maintainer has the responsibility to chase the board to make any additions, that he/she has gotten from the community.
    • the board has the responsibility to make the clarification of the submitted points TO THE LEVEL OF CLARITY that they require
    • the board has NO RESPONSIBILITY to read through the mailing-lists or wiki-pages-history to "fish" for the additional points!! (example1)