...
We had started talking about how to make recommendations on the last call, and shared the inventory at the beginning of the week – not surprisingly, with no feedback so far.
Thinking that the recommendations could follow the categories instead of the domains --
- One way : for example, should we focus on development as a domain – invest in this, stop doing that, tighten up development
- and we could similarly write recommendations about governance or training
- Alternative : look at the types of resources, such as email lists, and solve them across purposes based on the best solution for that type of communication
- Or deal with each asset
- Would it be helpful to establish goals or principles
- e.g., reduce redundancy to reduce maintenance and improve the ability for people to find things
- Paul – everything has to justify its ongoing existence – we have a baseline level of noise from having too many things out in the ether – everyone should be able to understand the overall structure so not only the most involved people know where things are
- May need some temporary resources, like the Hackathon email list – we just need to get rid of them when we're done, but would be valuable to preserve the knowledge that a person participated in a CRM function
Action items