CR003 - Specialist Group Advocate Portolios

Suggestion:

Create and support a new advisory (not mandatory) portfolio for Branch committees. A Specialist Group Advocate (SGA) portfolio to become the direct contact for Specialist Groups to support collaboration. This portfolio would default to the Member Group Chairperson if not re-assigned within the Member Group committee.

A central communications (Basecamp?) area for the holders of both BA and SGA portfolios would be created.  The objective is to encourage/drive Branch and SG collaboration.  Portfolio generic email addresses should be created and added to the Branch website.

Category on Map Diagram:
COLLABORATION

Instructions:
Please complete Add New Comment section fields as requested below:

 

FIELD REQUESTED INPUT
Your name:
WILL BE PUBLISHED
With your name !
Email:
WILL NOT BE PUBLISHED
With your email – this will not be made public
Homepage
WILL NOT BE PUBLISHED
LEAVE BLANK
Subject
WILL NOT BE PUBLISHED
LEAVE BLANK
Comment
WILL BE PUBLISHED
Please type JUST ONE these three response options on the first line.AGREE
DISAGREE
REFER
REFER is to be used to either get more information, or if you like the principal, but have concerns about the implementation.
Then from the second line onwards please add any personal comments if you would like to.

Comments

REFER

REFER
You suggest "Create and support a new advisory (not mandatory) portfolio for Branch committees" - should this not suggest "Create and support a new advisory (not mandatory) portfolio for Specialist Group committees"?

Apologies if is isn't so

Apologies if is isn't so clear John.

The recommendations are

CR002 - Branch Advocate (BA) portfolio is needed on a SG committee to advocate on behalf of and be the contact for (communicate with) Branches
CR003 - Specialist Group Advocate (SGA) portfolio is needed on a Branch committee to advocate on behalf of and be the contact for (communicate with) SGs.

The word "portfolio" was chosen on purpose to imply that a separate role is not necessary, more that a formal relationship and support processes should be set up between the SGs and Branch networks.

Thanks for taking the time to comment.

DISAGREE - Don't see the need

DISAGREE - Don't see the need for a a role to exist for this to happen. Where there is a will there is a way, it is the desire to communicate and collaborate that is missing, giving someone the job of doing it won't change that.

REFER

REFER

my other thought around this is that we can already contact branch chairs through the groups team, but it often fails because the chair is a single point of failure. You need more than one contact and / or you need to have the groups teams co-ordinating as they know who is active and responsive in groups and who isn't. For instance, the always send stuff to me because they know I'll respond, rather than to our Chair who is pretty hands off from day to day SG management.

Add new comment