Communications and IT
- One summarised digest of the week should be put together and emailed out / made present on Learn. This will ensure that people are kept in the loop about key developments. Should we create it at the end of each session with input from everyone, or delegate it to different people every week?
- In which ways can we make our project open to the public? Use of Facebook page to collate our resources and work, and to regularly update with our activities and reflections? Start using the University’s curated collections system and academic blogging to keep certain features of our work open to the public?
- End of each session we should offer individual recaps, reflections and assessments on how we feel it went; willing to be open, honest and critical about the process, and to ensure everyone’s voice is heard and that the course stays open and dynamic, rather than getting stuck on a particular track.
- Saying people’s name when they begin to speak; helps reinforce a sense of community and so that everyone can easily learn each other’s names.
- Create a informal time before each session for people to come together, eat lunch and chat before the session formally begins.
- Move onto the academic blogging site / Learn and find the best way we can be in communication with one another through live chats, comment threads or a forum-like system; better than having to move onto other platforms like Slack or Facebook which require learning to use them, signing up etc and will keep it centralised on University software.
- (Spend a session/time reflecting on how standard courses are structured, to reflect on how much work is put in, and to understand what we can learn from them in terms of IT usage.)
