[HSU-CoordBoardInternal] Apology to Fundcom

[Breonna Mabry]

Unfortunately, the letter to fundcom was sent on Tuesday from the
coordboard email (hence why I asked for revisions ASAP) .

I do not understand what you are interpreting as defense in the apology
that was sent. I think the letter encompasses all aspects of a sincere
apology: 1.) Intent 2.) Clear outline of the event we are apologizing for
3.) How/what we learned from our mistake to ensure it won't happen again.
4.) Allow for further discussion

The apology clearly states that our actions were unexcusable and
disrespectful. Can you elaborate on what was defensive?

One thing I must note is that Coordboard cannot "back" a proposal the way
you did in your revision. We are supposed to be an objective body. Though I
personally think fundcom deserves a stipend, it I'd not our place to say
"let's get the funding you deserve" or that their proposal obviously this
needs to be in the agenda for the next town meeting.

Lastly, Coordboard takes responsibility for all of their shortcomings in
this email. I am morally opposed to apologizing for anything other than my
own shortcomings. I do not accept responsibility for others mistakes, and I
do not think coordboard should either. Our miscommunication should be a
learning experience for both parties.

Best,
Bree
On Feb 12, 2014 11:28 PM, <da11 at hampshire.edu> wrote:

>
> Hi,
>
> I think Chris has a really good point here. I think it might come across
> negatively if the apology contains a defense. Especially since I think that
> the mistake was not just adding it to a full ballot. It was also going back
> on a vote to have it on the ballot, and town hall, and not communicating
> this decision to the students, and scope ground, who sent the proposal.
>
> Thank you,
> Dina
>
>
> Quoting cjp12 at hampshire.edu:
>
>  Hey, I just saw this and did a quick rewrite. I just dropped most of the
>> parts where we defended ourselves. We look back either way so its better to
>> just suck it up and apologize for things even if it isn't our fault. I
>> would actually be happy to handle apologies in the future. Sorry about the
>> delayed response.
>>
>>
>> Fundcom,
>>
>> Coordinating Board would like to apologize for its miscommunication and
>> failure to get the FundCom proposal on the agenda on January 28th, 2014.
>>
>> In retrospect, we believe the situation resulted from internal
>> miscommunication between ourselves and Fundcom. CoordBoard made an error
>> when we suggested that your proposal would likely be on the agenda for the
>> 1/28/2014 Town Meeting. At the time in which we had conversed with your
>> representative, our agenda was already full and advertised to the
>> community. Clearly we both need to do better at communicating. Though in
>> this case the breakdown of communication in this case lies more clearly at
>> our doorstep. We are called the Coordinating Board after all.
>>
>> We apologize for our failure to get your funding into town meeting.
>> Obviously, we need to get this funding into the next town meeting. So
>> discussion of this matter with your representative(s) at the next Coord
>> Board meeting would be a good idea.  Please feel free to email us at
>> coordboard at hampshire.edu. We look forward to hearing from you and regret
>> taking so long to get back to you. Lets get you the funding you deserve.
>>
>> Regretfully,
>> CoordBoard
>>
>> The single biggest problem in communication is the illusion that is has
>> taken place. -George Bernard Shaw
>>
>>
>>
>> Quoting Breonna Mabry <breonna.mabry at gmail.com>:
>>
>>  Below is the draft of the apology letter I will send to FundCom. Please
>>> send me your revisions asap:
>>>
>>> Fundcom,
>>>
>>> Please accept this letter as CoordBoard's formal apology for the
>>> miscommunication that occurred regarding the Town Meeting agenda on
>>> January
>>> 28th, 2014.
>>>
>>> It was not our intention to cause any damage or inconvenience. In
>>> retrospect, we believe the situation resulted from both internal
>>> miscommunication and poor communications with your governance body.
>>> CoordBoard made an error when we suggested that your proposal would
>>> likely
>>> be on the agenda for the 1/28/2014 Town Meeting. At the time in which we
>>> had conversed with your representative(s), our agenda was already full
>>> and
>>> advertised to the community. While this is by no means an excuse for our
>>> shortcomings, knowing the cause will help us guard against future
>>> mistakes.
>>> Please note that we acknowledge that our oversight was completely
>>> disrespectful and inexcusable.
>>>
>>> If there was any good that came out of this unfortunate experience, it is
>>> that we have grown and learned how to better communicate with the student
>>> community and better manage internal communication.
>>>
>>>
>>>
>>> Again, we are truly sorry for what happened. If you would like to
>>> continue
>>> this conversation, please feel free to email us at
>>> coordboard at hampshire.edu.
>>> We look forward to hearing from you and putting this matter behind us.
>>>
>>> With greatest sincerity,
>>>
>>> CoordBoard
>>>
>>> --
>>> Breonna M. Mabry
>>> At-Large Member, CoordBoard
>>> breonna.mabry at gmail.com
>>> School of Natural Science/ School of Cognitive Science
>>> Hampshire College
>>> Amherst, Massachusetts
>>>
>>
>>
>>
>> ------
>> This is the INTERNAL mailing list for Coordboard. For the sake of
>> transparency, all internal communications via email must go through this
>> listserv, where they are publicly archived (that means that all emails sent
>> through this listserv /are public publications/ and anything you say on
>> this listserv could be reproduced legally by anyone). If there are any
>> changes to meeting times or locations, then those emails must still be sent
>> out to the Coordboard MAIN listserv (HSU-CoordinatingBoard at lists.
>> hampshire.edu) so that the meetings can be open to all members of the
>> Hampshire community. Listservs are not a secure method of communication and
>> any sensitive info such as passwords or classified infomation should not be
>> sent via listserv. Do not publish anything on the listserv that you would
>> not be okay with being seen by people who aren't on coordboard!
>> _______________________________________________
>> HSU-CoordBoardInfo mailing list
>> HSU-CoordBoardInfo at lists.hampshire.edu
>> https://lists.hampshire.edu/mailman/listinfo/hsu-coordboardinfo
>>
>
>
>
> ------
> This is the INTERNAL mailing list for Coordboard. For the sake of
> transparency, all internal communications via email must go through this
> listserv, where they are publicly archived (that means that all emails sent
> through this listserv /are public publications/ and anything you say on
> this listserv could be reproduced legally by anyone). If there are any
> changes to meeting times or locations, then those emails must still be sent
> out to the Coordboard MAIN listserv (HSU-CoordinatingBoard at lists.
> hampshire.edu) so that the meetings can be open to all members of the
> Hampshire community. Listservs are not a secure method of communication and
> any sensitive info such as passwords or classified infomation should not be
> sent via listserv. Do not publish anything on the listserv that you would
> not be okay with being seen by people who aren't on coordboard!
> _______________________________________________
> HSU-CoordBoardInfo mailing list
> HSU-CoordBoardInfo at lists.hampshire.edu
> https://lists.hampshire.edu/mailman/listinfo/hsu-coordboardinfo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.hampshire.edu/pipermail/hsu-coordboardinfo/attachments/20140213/4ec6c5ce/attachment-0001.html>