How We Built Bridge for Design

How might we foster a more inclusive and diverse environment in the tech industry? We often talk about the urgent need for more diversity, but few take action. Where do you start, what do you do to help, and who do you employ to help with a potentially complex and often difficult subject?
At Bridge we build and run part-time courses that are free for students with the goal of making the tech industry more inclusive, diverse, and accessible space. Our courses are designed to remove barriers for junior to intermediate professionals who are women, non-binary, or agender. They’re built and run by volunteers and hosted at tech companies in Toronto. We’re able to efficiently build courses that are tailor made for these groups using design thinking and lean development methodologies such as project discovery, user research, usability testing, and iterative improvement.
In 2017 Bridge School built a brand new course – Bridge for Product Designers. This is the story of how and why we did it.
Sprint 0
First I gathered information on how Bridge for Software Developers was built, and what they learned along the way. I asked a lot of questions, and turned to these insights frequently when building out this course.
Next, I began the process of building our community of volunteers. This task was easy, lots of designers and scrum masters at Rangle were eager to help. We also rallied some senior leadership in the industry as advisors. Once we had our team we were ready to get started building our beta Bridge for Product Designers course.
Project Discovery
For the project discovery process we had a facilitated discussion about target users and project outcomes. In this case our users were our potential students, and our outcomes were what we wanted students to gain as a result of completing the course successfully. The outcome of this session was designed to serve as a hypothesis that we could then validate or re-imagine.
During the kickoff we realized we needed to do more user research with potential students before we could move on to thinking about the user journey or course structure. We wanted to see what our users needed most and we wanted to validate some of our assumptions.
User Research
To conduct our user research we did informational in-person interviews and asked the same questions online in an anonymous survey. Our questions were designed to produce information about our potential students: their academic background; their career and current role; their pain points with their career and learning; and finally, whether any kind of barriers were getting in their way.
Once we had all the results of the user research we did an interview synthesis exercise. This allowed us to qualify and quantify our results. We gathered the interview notes and for each mention of a pain point phrase (for example, “mentorship” or “communication”) we wrote that phrase on a sticky note and put them up on a wall. Once they were all up on the wall we grouped the stickies and gave the category a name using different coloured stickies. The photo below is the output of this exercise.

The research taught us that what students needed the most was a course that would provide mentorship and focus on building up their skills in the areas of communication and confidence, facilitation and discovery, as well as user research and usability testing.
In addition to speaking with prospective students, we spoke to people heading up design and talent departments at innovative tech companies in Toronto. We asked them a similar set of questions about where the opportunity space might be for a course like this. This research validated what our users were expressing, and enriched our perspective.
User Journey Mapping
Our next step was to begin mapping the user journey (course structure) based on the synthesis of the user research. Top of mind was balancing wanting to teach everything we thought would be valuable to users, as well as thinking about what we could reasonably get done within our timeframe of 7 weeks. This was an exercise in creating our MVP.
Once we had our course structure, we divided it into weekly modules, the equivalent of epics in user journey mapping. Our seven modules were: Discovery, Research, Strategy, Ideation and Prototyping, Feedback, Selling and Pitching, and lastly, Course Learnings.
Sprint Planning
We then went through an exercise of dividing and conquering. People signed up to teach, TA, and/or write content for classes. We had three core teachers, a handful of TAs, a scrum master, and everyone helped out writing content.
Writing content was done in a lean fashion, since we knew that while teaching the course things might change along the way (and they did!). Generally speaking, we wrote content a week or two in advance of class. This might sound strange, but it really pays off to be able to dynamically adapt content based on the needs of our student group. For example, our project discovery facilitation class ran a little long, and we were able to adapt our research module to accommodate this.
Usability Testing
At the end of each class, TAs led a five minute exercise asking students to tell us what worked well, and what could have been better. We reminded them this was a beta and their feedback was both welcome and very important; we received a lot of great information this way. Students were forthcoming and interested in helping us incrementally improve the course for them as well as for future students.

In addition to daily feedback, we also collected overall course feedback. On the last day of the course we did a facilitated retrospective with students and a scrum master to get overall course feedback. We’ll use this feedback to build an even better course for the next cohort.
The results of building and running this tailor made course are encouraging, empowering our students to get that next level job or promotion. In fact, within a couple months of completing our course, several students did get better positions. They are also able to better advocate for themselves because of our team communication and career development components. They are ready to work at a more advanced level, and have developed key professional and leadership skills. We were able to quickly build an amazing and dynamic product because we utilized design thinking and lean methodologies.
Bridge is a reusable, sustainable model for positive grassroots change in tech, and we’re excited to share our challenges, results, and next steps.

Link: http://blog.rangle.io/how-we-built-bridge-for-design/