(SJRK) July 11, 2019 Partners Meeting
Liam
- TIG is rejigging entire staff orientation process
- Have some new people and realised they need to standardize an orientation package
- Means the work Liam has been doing on this project will be streamlined into that process
- One of staff revealed that she has a disability - took the orientation package and broke it down into chunks - in order to make it more accessible for her
- Going to work from her version of it - accessible bite-sized format
- Organization is catching up to what LIam has been doing - Liam doens’ tneed to make a case for it! Whoop
- Had been wondering when to address this - and now it’s already happening
- Liam can advocate for the HOW
- Looping back in AODA training, but also the more inclusive organisational stuff
- Have been using the stuff Liam has been putting together - at staff meeting - decolonising prided, other units - they get added to the toolkit - starts with why and how and also reflections on the activities from those who ran them - reflecting and iterating
- Liam leading staff meetings in next 2 weeks
- Feedback and draft text from Jay
IDRC
Gregor - Storytelling tool
- Major changes to the tool aimed at making Customization of the look and feel of the site easier
- Adding new themes
- Customizing existing themes
- Storytelling a major part of Floe going forward
- Hope to work with TIG on this
- Any pre-work or relationship building - should we have a conversation?
- Let’s talk in September - it’s a bit early
Face to face meeting
- Idea to have each partner lead a short co-design session
- Pass on the knowledge of co-design
- How to make our interactions useful to folks on the project
- Content that the group can chew through together
- Knowing what each other are working on
- Flex the muscle of co-design practice
- Can be vulnerable to present unfinished work - but good to practice this and detach from the work
Website
- Let us know if there is any new content
- TIG - Create to Learn - as they move from Phase 1 to 2 there will be more content
- More images coming in next while
- http://www.createtolearn.ca/
- Many video stories available at http://www.createtolearn.ca/digital-stories.html
Bahati - UWEZO
- Will soon start collecting stories from young people with learning differences, so is interested in the conversation about story telling
- Training workshops (on inclusive design) for young people with learning differences
- Conducting by end of July
- Opportunity to know what could be the challenges of this group
- Refugees , learning differences, other barriers to learning
- Interested in using the tools that are available
- Was going to schedule a chat with TIG about the story kit
- Will bring folks on board who have experience in collecting stories
- IDRC storytelling tool
- Only in English right now
- Bahati could have it translated - Kinyrwanda and also other language for refugees - Swahili, Kirundi, probably French as well
- User-friendly format - braille would be good too
- Could we create different versions in different languages?
- Low bandwidth would likely be an issue
- Screen-reader accessible too?
- The tool is working reasonably well now with screen-reader, but there may be some bugs to work out
- We should think of other ways to collect stories if low-bandwidth is a major issue
- Could Bahati try it out and let us know?
- Most young people in Rwanda are using WhatsApp
- Literacy is also a barrier
- Timing?
- ID workshops end of July
- Presenting research from James
- Building a network of youth orgs to engage in dialog
- Identifying the organisations and the young people
- Need anything from us?
- Storytelling - don’t know the timing yet -
- Need to identify the young people to be involved
- Bring IDRC on board to help run sessions
- will the tool load and be usable in lower bandwidth environments?
- Michelle, 8:41 AM
- this is a very good question.
- I suspect not right now
- The site isn't currently optimized for low-bandwidth, the total load side for each page is in the 3~4mb range, iirc
- may be useful to test it in english first, to determine if it can be used in the context before scheduling to translate into languages used in country
- (we ran into a similar issue with a project we had in Rwanda a few years ago)
- we were asked to build a job skills platform, however the folks who were supposed to use it didnt have access to computers
- no email addresses etc
- solving for braille and the low bandwidth context may be linked together :)