!GuidPrinsLdrs.jpg!We wanted to ask "What are the guiding principles we should use to vet the draft list of IS&T Core Products and Services?" Here's what YHS captured:
An extremely rough transcription of that brainstorm activity follows:
- Is maintained
- Promotes collaboration across MIT
- Critical to MIT mission
- Enhances workspace -- helps people study, teach, admin. and collaborable
- All other things equal, should serve the many, not just a few
- We help people use the service
- Responds to community need
- It should also be needs-driven
- "Most" DLCS don't want to do it OR were told they can't do it
- IS&T is not the sole provider of central IT services
- Is IS&T at least a "good" provider of the service?
- Sustainable
- Reduces "cost" in total across MIT -- might be financial cost, or could be other qualitiative factors
- Guides prioritization, for example, research computing inside IS&T vs. NOT inside IS&T vs. SOMEWHAT inside IS&T
- Should not be stated in terms of "product" name
- Easy to explain and easy to use
- Practical (this needs defintion)
- Has explicit policy, governance and a roadmap
- Predictable and consistent -- no surprises!
- Reliable
- Measurable
- Keeps "current" with technology trends
- Represents "best practices" in some sense
- Is legal
...