<div dir="ltr"><div class="" id="magicdomid39"><span class="">HI everyone, <br><br>HOT In Person Board Meeting - Day 1 summary</span></div><div class="" id="magicdomid3437"><br></div><div class="" id="magicdomid3723"><span class="">The
HOT Board is convened in Washington DC for a meeting facilitated by
Allen Gunn (Gunner) of Aspiration Tech. The method is highly interactive
and participatory with small group work. Please see the Aspiration Tech
wiki for further details on how this process works for collaboration
and inclusiveness while prioritizing items. [1]</span></div><div class="" id="magicdomid236"><br></div><div class="" id="magicdomid243"><span class="">Agenda</span></div><div class="" id="magicdomid330"><ol start="1" class="">
<li><span class="">Introductions, Guidelines</span></li></ol></div><div class="" id="magicdomid3434"><ol start="2" class=""><li><span class="">Presenting
about role of board, why people are on the board and what each person
deemed the most important thing that the board needs to accomplish?</span></li></ol></div><div class="" id="magicdomid3436"><ol start="3" class=""><li><span class="">Provide visions of future goals for programming, community and organization for the next 12 months</span></li>
</ol></div><div class="" id="magicdomid697"><ol start="4" class=""><li><span class="">Map of everything that needs work, prioritize items</span></li></ol></div><div class="" id="magicdomid826"><ol start="5" class=""><li>
<span class="">Discussion with HOT's lawyer on governance, bylaws, legal guidelines and conflict of interest.</span></li>
</ol></div><div class="" id="magicdomid3155"><ol start="6" class=""><li><span class="">Identify
key items to be resolved for the remainder of the 2 days. And, of
course, roadmap actions for future review and iteration with you
(community, membership).</span></li></ol></div><div class="" id="magicdomid1631"><br></div><div class="" id="magicdomid2044"><span class="">We
began a brainstorming process around our goals for HOT, splitting ideas
across categories of programming, community and organization. In
separate groups, we identified things that we agreed on (which was the
majority!) and things that we disagree on or need to discuss further.</span></div><div class="" id="magicdomid3967"><span class="">We
fleshed out these goals into many discussion areas, and began the
process of prioritizing these. The method was to brainstorm on the
topics and sort like items and flesh out other key points. This was done
with sticky notes and a process of colour and taxomony.</span></div><div class="" id="magicdomid3331"><br></div><div class="" id="magicdomid4191"><span class="">The
discussion with the lawyer assisted the Board members to better build a
common language around what our collective and individual
responsibilities are for the Board, organization, membership and
community. We had some specific questions around conflict of interest.
As per our previous notes on conflict of interest, we obtained further
context on these key questions. We do promise to surface these in our
actions and share back next steps for review/input. From these
conversations we build a list of bylaws to be changed (e.g. 2/3 quorum
of membership) and key processes to be written to make discussions and
decisions more productive. </span></div><div class="" id="magicdomid3334"><br></div><div class="" id="magicdomid3982"><span class="">This
is to be continued tomorrow and Sunday. Here is a selection of topics
and questions coming out of this process which are to be discussed
tomorrow (from all of the ninety (90!) issues identified today and from
your input):</span></div><div class="" id="magicdomid2723"><ul class=""><li><span class="">The board and ED should actively work to delegate as much work as possible</span></li></ul></div><div class="" id="magicdomid4311">
<ul class=""><li><span class="">We
need the membership to be well informed/consulted about HOT strategy.
The Board will, of course, provide any iterative documents for feedback.</span></li></ul></div><div class="" id="magicdomid2718"><ul class=""><li><span class="">Hiring more HOT staff</span></li></ul></div><div class="" id="magicdomid4363">
<ul class=""><li><span class="">How to define unacceptable behavior/ Code of Conduct or Conflict resolution handing.</span></li></ul></div><div class="" id="magicdomid4384"><ul class=""><li><span class="">We need a clear definition of what makes a HOT project (as an organization)</span></li>
</ul></div><div class="" id="magicdomid4216"><br></div><div class="" id="magicdomid3335"><span class="">Note
that the above are not at least yet defined top priorities. Gunner, our
facilitator, will work on tasks for us to deliver concrete items for
your review. Further prioritization work will take place tomorrow. The
inputs from the community have been embedded in our work - thank you for
your input!</span></div><div class="" id="magicdomid3380"><br></div><div class="" id="magicdomid4464"><span class="">More Questions and comments are welcome. We'll provide another summary tomorrow. </span></div><div class="" id="magicdomid3420">
<br></div><div class="" id="magicdomid3379"><span class="">thank you again</span></div><div class="" id="magicdomid3330"><span class=""> </span></div><div class="" id="magicdomid1629"><br></div><div class="" id="magicdomid1629">
Heather on behalf of the Board (who co-wrote this)<br><br>[1] <a href="http://facilitation.aspirationtech.org/index.php?title=Main_Page">http://facilitation.aspirationtech.org/index.php?title=Main_Page</a><br></div></div>