<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pallavi Thampi on Medium]]></title>
        <description><![CDATA[Stories by Pallavi Thampi on Medium]]></description>
        <link>https://medium.com/@pallavitee?source=rss-5ae8ba7fd28a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*duMWVbi5658QJCGVXksN7w.jpeg</url>
            <title>Stories by Pallavi Thampi on Medium</title>
            <link>https://medium.com/@pallavitee?source=rss-5ae8ba7fd28a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:27:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pallavitee/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Zeroing in on User Insights]]></title>
            <link>https://medium.com/code-for-canada/zeroing-in-on-user-insights-cb1d211d9601?source=rss-5ae8ba7fd28a------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb1d211d9601</guid>
            <category><![CDATA[fellowship]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[what-we-do]]></category>
            <category><![CDATA[code-for-canada]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Pallavi Thampi]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 14:01:00 GMT</pubDate>
            <atom:updated>2019-04-11T14:01:00.932Z</atom:updated>
            <content:encoded><![CDATA[<h4>Findings from user research are helping Code for Canada fellows improve how data is used by Toronto’s Traffic Safety Unit.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*osZfMI92JcKJZBORh9tpHw.jpeg" /><figcaption>A cyclist waiting behind the open doors of a streetcar along King Street. Thanks <a href="https://www.flickr.com/photos/cityoftoronto/">City of Toronto Flickr</a>!</figcaption></figure><p><em>This series follows our journey as a product team through </em><a href="https://codefor.ca/"><em>Code for Canada</em></a><em>’s nine-month fellowship within the public sector. Andrew Konoff, Evan Savage &amp; myself are embedded within the </em><a href="https://www.toronto.ca/services-payments/streets-parking-transportation/road-safety/big-data-innovation-team/"><em>Big Data Innovation Team</em></a><em> in the Traffic Safety Unit. Read Andrew’s intro to the project </em><a href="https://medium.com/code-for-canada/the-intersection-of-road-safety-and-data-in-toronto-7e5804cfdb57"><em>here</em></a><em>.</em></p><p>Last year, 45 people died walking or cycling on Toronto streets.</p><p>Launched in 2016, the City of Toronto’s <a href="https://www.toronto.ca/services-payments/streets-parking-transportation/road-safety/vision-zero/vision-zero-plan-overview/">Vision Zero Road Safety Plan</a> is an ongoing effort to reduce — and ultimately eliminate — serious injuries and deaths on our streets by implementing various safety measures and redesigning roadways.</p><p>As frequent cyclists and pedestrians, Andrew, Evan and I care deeply about Vision Zero and what it represents. We’re keen to apply our tech skills to this literal life or death issue, to discover how we can use the traffic data the city collects to prevent tragedies, and help everyone, especially the most vulnerable road users feel safe on our streets.</p><p>To achieve this, we’ve spent the past five months learning how City staff are using decades worth of traffic data, and more importantly, how they’d like to be using it to further the goals of Vision Zero.</p><h3>How is traffic data being used?</h3><p>As a resident, you might have dialed 311 because you noticed an unsafe crossing area in your neighbourhood. Transportation staff take your request, go onsite, and use traffic volume and collision data as part of their evaluation of potential safety improvement to the street. Engineers can identify dangerous hot spots and take action through safety interventions like new mid-block signals or pedestrian crossovers, narrowed streets, speed humps to calm traffic, leading pedestrian intervals to increase pedestrian safety, flashing ‘Watch Your Speed’ signs, or ultimately even automated enforcement to make drivers slow down.</p><p>Vision Zero Planning, a team focused on the <a href="https://www.toronto.ca/services-payments/streets-parking-transportation/road-safety/vision-zero/emphasis-areas/">six emphasis areas</a> outlined in the safety plan, looks at how those structural changes to our streets can privilege more vulnerable road users and how data can help make those proactive decisions. <a href="https://www.toronto.ca/services-payments/streets-parking-transportation/walking-in-toronto/">Pedestrian Projects</a> and <a href="https://www.toronto.ca/services-payments/streets-parking-transportation/cycling-in-toronto/">Cycling Infrastructure</a> use the traffic and collision data to frame umbrella strategies (like the 10-Year Cycling Plan), while <a href="https://www.toronto.ca/city-government/planning-development/">City Planning</a> staff use the data to determine the impact of new developments or major infrastructure projects on traffic flows.</p><p>Staff are deeply committed to their missions, but they’re hindered by the limitations of the City’s data tools. The current data management systems used by Transportation Services, dubbed CRASH for collision data and FLOW for traffic volume data, were built on a legacy Oracle database in the early 90s, and the applications are now, well… limited.</p><h3>What’s the current user experience like?</h3><p>Right now, staff are primarily using CRASH and FLOW to pull reports. Simply put, they can retrieve the data they need, but there’s not a lot of functionality to enable them to <em>do</em> things with that data, like compare historical counts, put it on a map, or see collision data and traffic volume data together at the same location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y63EZu2jGqpNm_UiYYmXOQ.png" /><figcaption><em>Pictured above is the current FLOW to access volume data. Not only are the maps are outdated, but FLOW only works on Internet Explorer — an annoyance for most City staff.</em></figcaption></figure><p>A desire we heard a lot was for a “one-stop shop” for pulling data <em>and </em>working with it. To understand what that might look like, we first needed to understand how users inside and outside of Transportation interact with collision and volume data.</p><p>In other words, we needed to dive deeper into user research.</p><p>We conducted 23 interviews across eight user groups. We spoke to data collection and analysis supervisors managing the transfer of data, support staff and mail clerks verifying the data, and engineers loading and using the data to recommend safety interventions. From there we met with users across departments like Traffic Operations, Pedestrian Projects, Cycling, City Planning, Vision Zero Planning, and Police Services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCS2IsAq19VPXlWbNjQdnA.jpeg" /><figcaption>Just one wall of our work room plastered with user research.</figcaption></figure><p>In parallel, Evan was conducting technical interviews with staff at the Geospatial Competency centre, Open Data, Big Data Innovation Team and Cloud Services to scope out the technical landscape, requirements, and constraints.</p><h3>What did we learn?</h3><p>There’s a real appreciation for the value of data across the city with a shift toward making data (barring personal information) public and available. People at the City really care about making data-driven decisions to make the streets safer. They also recognize that the way the current systems exist can be reimagined to engage internal staff, but also be used as a tool of discovery and exploration for the public since there’s so much historical data that has been collected within CRASH &amp; FLOW. Though the mindset is positive and there’s a real desire for progression, we noticed some recurring patterns in our research.</p><h4><strong>1. Users don’t find data sources reliable (and making them reliable takes work)</strong></h4><p>When a non-fatal, or non-serious collision occurs (ie. a fender-bender), those involved are asked to self-report at Collision Reporting Centres. As you can imagine, the stories of those involved in collisions don’t always line up, and coding clerks at the Traffic Safety Unit said they often have to do some detective work to get the full “data” picture.</p><p>Users also expressed frustration verifying the data contained in the police reports that accompany more serious collisions. Privacy concerns mean some of the information is redacted, and the reports do not include officers’ field notes, which makes it difficult to verify and clean data.</p><blockquote>“Each Motor Vehicle Accident Report is filled out mostly manually from field notes, and data problems we experience are largely because officers don’t then go back our digital record to update fields there.” -<strong>Police Traffic Services</strong></blockquote><p>The existing applications also leave room for users to create their own standards for entering data, which leads to errors, inconsistency and confusion. For example, North-South or East-West directions are often misrepresented or flipped.</p><p>Finally, different applications appear to calculate and catalogue speed — a <em>major </em>factor in the severity of collisions — differently.</p><blockquote>“You have to take the speed data with a grain of salt.”<em> </em><strong>-Traffic Ops Engineer</strong></blockquote><h4><strong>2. There’s an emphasis on repetitive, manual work across multiple applications to do a single task.</strong></h4><p>There’s no one stop shop for all the staff’s data needs. When using CRASH and FLOW, users are constantly context-switching. At the Traffic Safety Unit, there is no single tool to load, clean, verify and pull reports or queries.</p><blockquote>“Right now, I’ve got four different windows open just to tell where we’re going with this count…now we’ve got six different windows open, all to do one request.<em>”</em>-<strong>Staff at Traffic Safety Unit</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qm7YOVSuyQl3WGFEi4-dAA.jpeg" /><figcaption>Staff have become pros at navigating a patchwork of programs that support the front-end of CRASH and FLOW, as well as some supplementary applications, like Google Maps.</figcaption></figure><p>This is working at the moment, but there’s definitely room for improvement; even a small amount of automation could make this process much easier and efficient for staff.</p><h4><strong>3. There’s an opportunity to integrate more — and more diverse — data</strong></h4><p>Users of CRASH and FLOW are aware of data at the City that could help them, but these aren’t included in their databases. For example, Traffic Operation investigators do their own four-hour volume counts that are not available in FLOW. Similarly, pedestrian delay counts and comprehensive cycling counts are also absent in FLOW.</p><p>One of the pieces of data most frequently on users’ wish-lists was information about <a href="https://twitter.com/hashtag/nearmissto">incidents that aren’t classified as <em>motor vehicle</em> <em>collisions</em></a><em>, </em>things like cyclist doorings, or pedestrian near-misses, or video analytics of the moments prior to a collision are not included current CRASH data.</p><p>There was also a real desire across departments to move away from car-centric data, and incorporate more information about how everyone, from pedestrians to cyclists, seniors or those with mobility devices, use our roads.</p><h3>Where do we go from here?</h3><p>First up, we want to thank each and every public servant and stakeholder who made time to speak with us. Speaking with so many people who use CRASH and FLOW helped us truly understand pain points and identify opportunities.</p><p>Our user research has shown us that <em>integrating CRASH and FLOW into a single data platform </em>would have an immediate and significant impact for users. It will reduce both the amount of manual work involved in generating reports, and the opportunities to introduce human error into those reports.</p><p>We also learned that requesting information to assess a traffic warrant (internally referred to as “requesting a count”) is one of the most common queries to CRASH and FLOW. So we’re going to start with this process, and see how we can make it easier, simpler and more automated for Traffic Operations staff using the data to conduct investigations.</p><p>So, with those key findings in mind, we’ve transformed our previous problem statement into a product vision:</p><blockquote><strong>We believe that by building an integrated collision and volume data platform for Data Supervisors from the Traffic Safety Unit and the Engineers in Traffic Operations, we’ll achieve a seamless data request to traffic warrant process.</strong></blockquote><blockquote><strong>We will increase access and extraction of data, cultivate trust in data sources, imbue transparency in the data pipeline, while continuing to work toward a shared vision of road safety for all.</strong></blockquote><p>During our next six-week sprint, we’ll be diving into the process of requesting data for a warrant. We’ll look look at both sides of the process: what Traffic Operations needs from the Data Collection Supervisor to request a count fand what the Data Collection Supervisor needs to process the request and collect the required data.</p><p>Throughout that process, we can tell if we’re going in the right direction by using our product vision as a compass. We want to build just enough to learn, to test with users, evolve our statement and experiment again; and we can’t wait to share the results with you!</p><p><strong><em>The Code for Canada fellowship embeds product teams into government, where they work alongside public servants to build great digital services. To learn more about becoming a fellow, or hosting a team of fellows in your department, visit </em></strong><a href="https://codefor.ca/fellowship/"><strong><em>codefor.ca/fellowship</em></strong></a><strong><em>.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb1d211d9601" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-for-canada/zeroing-in-on-user-insights-cb1d211d9601">Zeroing in on User Insights</a> was originally published in <a href="https://medium.com/code-for-canada">Code for Canada</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sink, Swim, or Cross a Bridge]]></title>
            <link>https://medium.com/itsbridgeschool/crossing-the-bridge-reflections-from-cohort-1-a192225c4333?source=rss-5ae8ba7fd28a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a192225c4333</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[tech-education]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <dc:creator><![CDATA[Pallavi Thampi]]></dc:creator>
            <pubDate>Sun, 20 Jan 2019 20:30:17 GMT</pubDate>
            <atom:updated>2019-01-21T18:59:23.434Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Reflections from 4 Product Design Grads on Cohort 1</em></h4><p><em>Bridge for Product Designers </em><a href="https://docs.google.com/forms/d/e/1FAIpQLSeZw6paKXPX6pdV0HEWU6mJc_UwCDQ-pN-jY01_IrsXfAZYJw/viewform"><em>Cohort 2 applications</em></a><em> are now open until January 22, 2019.</em></p><p>It has been a few months since Bridge’s first <a href="https://bridgeschool.io/apply-design/">Product Design</a> program wrapped up, and having taken up a new opportunity since then, my life got very busy <em>very</em> quickly, with little time to look back. I’m grateful to now have an opportunity to reflect on the program that re-routed my career and introduced me to so many wonderful people. To shed some light on the experience, I reached out to three of my classmates, <a href="https://twitter.com/heyimjen">Jen Zhang</a>, <a href="https://twitter.com/pavi_design">Pavi Logeswaran</a>, and <a href="https://twitter.com/sweetlimeca">Marjorie Castro</a> from Cohort One.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pXhSowJhztLrP95GQTDeBg.jpeg" /><figcaption>Jen presenting her final product on the last day of class.</figcaption></figure><h4>Education that Empowers</h4><p>Bridge is accessible tech education like no other. Built on the basis of amplifying the voices of women, non-binary and agender folks in software development and product design, Bridge offers free, hands-on 11-week courses that empower junior developers and designers to transition to intermediate, and eventually senior roles.</p><p>In the first Product Design cohort, all 12 of us were keen on deepening our product design practice, delving into discovery, facilitation, user research, prototyping and pitching. We were a diverse bunch, coming from various pathways that had led us into building products or bettering services. Some of us came from early stage startups, some from agencies or larger companies, and some of us were between jobs. We were united in a common intention: to cross the Bridge and land that next opportunity.</p><p>Jen was a Visual Designer in title, but took on journey mapping experiences as well as designing interfaces. Marjorie was working at a fin-tech startup transitioning from interaction design to Product Design. Pavi on the other hand, was pivoting from an entirely different career path when she applied to Bridge.</p><blockquote><strong>Pavi:</strong> “After hitting a glass ceiling in my prior career as a Biochemist, I wanted to pursue my true passion. I taught myself UX Design while handling a full time job and part time responsibilities of teaching. Eventually, I quit my full time job to take an immersive course at General Assembly to further my knowledge.”</blockquote><p>When I started Bridge, I was working on a mobile app at a startup that delivered meal kits. My excitement at guiding the creation of the app was quickly overshadowed by the fact that I was initially seen by my team as an UI designer. Advocating for the user’s experience and for conducting research were my main challenges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4LP-v-tQrhZ6Nw7EpSZM9A.jpeg" /></figure><h4><strong>Bridge was the next logical step for all of us</strong></h4><p>We were there to develop more catalytic skills (more commonly referred to as “soft skills”) like facilitation, research synthesis, pitching to clients, and product design strategy. But most of us were drawn to Bridge for the safe space where we could be ourselves, make mistakes, and fail headfirst.</p><blockquote><strong>Jen: </strong>“I wanted a sense of validation that, I too, can be a part of the product’s roadmap from beginning to end… In a sense, I felt building on my skills would help ease my feeling of imposter syndrome while at work.”</blockquote><blockquote><strong>Pavi:</strong> “I had the knowledge, but I always wondered if I was using the right toolkit. I was tired of being judged as a Junior Designer and I want to understand and know my worth. I wanted to learn from expert designers in an open environment where I could confidently ask questions and advance my skills. I was ready for the next step.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TLRG1a0BZaILFRLvOOF1gg.jpeg" /><figcaption>Pavi charting a user journey map.</figcaption></figure><p>My reasons for applying to program like Bridge were twofold. Yes, I wanted to broaden my skill-set, but I also knew I wanted to grow my design community and share my experiences with other designers and women.</p><p>Speaking from my experience as a racialized woman, the consequences of “failing” in a mostly white, mostly male startup feel all too real. In unsupportive environments, it’s easy for your knowledge and skills to get discounted and your credibility to be under constant scrutiny despite your experience. There are few ways you can actually grow without the right mentorship and support.</p><h4>Really, we learned the most from our mistakes</h4><p>During our classes, we had to confront some of our weaknesses and insecurities, such as, public speaking, time management, and making mistakes in front of others. In one of the first classes on facilitation, we were split up into groups of two, leading a facilitation activity through <a href="https://blog.rangle.io/clarity-canvas/">Clarity Canvas</a> (Rangle’s stakeholder discovery framework). The “Fakeholders” were giving us a hard time as per instruction, but I remember inserting myself into a point of contention between them to move conversation along. I realized it was more important to guide the process through probing questions and use the ‘Parking Lot’ generously to facilitate more productive meetings.</p><blockquote><strong>Jen:</strong> “Public speaking is not my forté. Having to present your work and your progress almost weekly was certainly a challenge. One of the most memorable pieces of advice given to me was by <a href="https://twitter.com/ergosomething">Naomi Bower</a>. She told me to remember that people generally want each other to do good, that the room is rooting for you, and sincerely care about what you have to say.”</blockquote><p>While balancing full-time roles with 6 hours of in-class learning per week, and 10–15 hours of homework was no piece of cake, the intensity and immersion of Bridge propelled our learning. Pavi focused on creating short and concise presentations to stakeholders to manage her time more effectively. She overcame the temptation of presenting design artifacts and process and focusing on pitching in a compelling business language that stakeholders could understand.</p><blockquote><strong>Marj:</strong> “One the biggest challenges I faced was allowing myself to make mistakes in front of others during the learning process. I overcame this with time by reminding myself that we were all there to grow and sharing our mistakes was valuable to all during our journey. Also, Bridge instructors reminded us that this was a safe space where we could experiment without judgement.”</blockquote><p>These challenges we encountered made us trust our own abilities and embrace the learning process whatever form it took.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4vq3nv2vS5iFR7UU-5qEQ.jpeg" /><figcaption>Instructor, Lindsie leading a session.</figcaption></figure><h4>Levelling Up: Tips from Bridge Grads</h4><p><strong>1. To align and clarify business and user objectives, ask the right questions.</strong></p><p>Facilitation was a favourite session amongst all of us. We learned how to ask questions that provoke answers and how to stop conversations from deviating during a stakeholder meeting.</p><p>Jen reflected her time at Bridge has made her more critical — whether it is of the questions she asks stakeholders or the type of words she uses to check her own bias.</p><blockquote><strong>Jen:</strong> “I found the facilitation fundamentals super insightful and valuable. When the business and the job is more or less placed on your hands, you have to know how to conduct these workshops with stakeholders, and how to conduct them well.”</blockquote><p><strong>2. To persuade someone, know what they want to hear.</strong></p><p>Our instructors at Bridge emphasized the importance of communication throughout the course. As designers we “pitch” in small ways everyday to convince our internal teams and stakeholders of design decisions.</p><blockquote><strong>Marj:</strong> “Pitching is a 100% learnable skill. There are three main tactics Aristotle and Naomi Bower say we can use to persuade our audience — ethos, pathos and logos — adding these into a pitch will allow us to establish trust, awaken listeners emotions, and use data to backup a pitch.”</blockquote><p><strong>3. To improve, lean into discomfort (like a <em>badass</em>).</strong></p><p>We all rallied around the idea that there are facets of Product Design that don’t come naturally for a beginner. The only way to crush impostor syndrome was to go for the things that made us mad anxious.</p><blockquote><strong>Marj:</strong> “Requesting and giving feedback is essential to becoming a badass. To quote one our fearless leaders Naomi Bower, “Lean into the discomfort”. I practiced asking for and giving feedback during design reviews and at the end of each class.”</blockquote><blockquote><strong>Jen:</strong> “I learned that everything takes practice and time to finesse; those questions we ask the stakeholder will become more intuitive as you conduct more interviews, and pitching to clients will be less scary! I realized that a lot of us suffer from imposter syndrome, but should hold confidence that we are capable of so much as product designers.”</blockquote><p><strong>4. To grow, know where you’d grow best.</strong></p><p>The ethics session led by <a href="https://twitter.com/lindsiecanton">Lindsie Canton</a> has a special place in my heart. It solidified the fact that it wasn’t simply enough for me to find a product role at any start up. I was able to shed the limitations I’d placed on myself to pursue what was most aligned with myself and my sense of worth.</p><p><strong>5. To keep learning, stay connected in the community.</strong></p><p>All of us were in agreement that learning together and from each other was invaluable. Without Bridge and the community it fosters, we couldn’t have grown in depth as well as breadth.</p><blockquote><strong>Jen:</strong> “I now know where I am the weakest, strongest, or hold the least interest in, as well as how I want to shape my role in my company. It was a wonderful experience deep diving into each module (research, facilitation, research synthesis, strategy, ideation, usability testing, pitching) and being truly open to making mistakes and learning together as a cohort.”</blockquote><blockquote><strong>Marj:</strong> “Applying for the program and taking the opportunity to level up was my biggest win. I learned a variety of skills and met an amazing group of people I respect and admire.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmM7n8CaTrCKQNLa5H1mrw.jpeg" /><figcaption>From left to right: Keiko, Jen, Marj and Evelyn.</figcaption></figure><h4>What makes Bridge unique?</h4><blockquote><strong>Jen:</strong> “Having taken a full time UX course before, it’s evident how much more initiative the cohort must have to be able to juggle full time jobs and life on top of your Bridge workload. But the key difference is certainly how the entire room always felt comfortable with being vulnerable with each other. Knowing that we are constantly in a safe space made me feel human, respected, and valued.”</blockquote><blockquote><strong>Pavi:</strong> “Bridge school gave us hands on experiences and real time application. In addition, all of this takes place in a safe learning environment where you feel comfortable to ask questions and make mistakes. The rewarding part of this was sharing my learnings and being able to apply it to my job.”</blockquote><p>I found my other educational experience in UX were focused on outputs and deliverables. I knew the right things to do, and the processes, what made something successful, but I lacked the finesse of a more practiced designer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLaMrSlTPOmIwCwa-CiUCg.jpeg" /><figcaption>Some of our amazing instructors and TAs from Cohort 1!</figcaption></figure><p>Bridge gave us a space to be ourselves and learn from each other, but it also gave me more transferable skills than any other program I’ve done, in facilitation, pitching, and running workshops. I felt like the staff (all of whom were doing this on their own time), were completely dedicated, supportive and genuinely cared about each student. You were more than a metric at Bridge.</p><h3><strong>Six months later…</strong></h3><blockquote><strong>Marj:</strong> “I’m working as a Product Designer for Explorux. I have taken greater initiative to facilitate design sessions, usability testing and research, using the skills I gained during the program. I’m grateful to the entire Bridge School team for this initiative and dedication to the program. You are making a significant impact on the tech industry and your students lives. Thank you!”</blockquote><blockquote><strong>Pavi:</strong> “During the program I was offered a Product Designer role at Capital One. I’m able to apply and share my learnings from Bridge School. It’s made me appreciate continuing education, Now, I’m always on the lookout to learn something new and apply it to my career. I loved meeting and getting to know all the amazing folks in the program. I learned so much from just observing the instructors in their element.”</blockquote><p>Jen was also promoted from a Visual Designer to a UX Designer at her company, doing what she loves.</p><p>While wrapping up Bridge, I knew I was ready for an opportunity that aligned with my values and was the direction I wanted to run in. I was a better advocate for myself. I’m currently a UX Design Fellow with <a href="https://codefor.ca/">Code for Canada</a>, a non-profit that embeds product teams within the government for 9 months. I have agency and say in my role, and have just wrapped up two months of leading intensive user research to a complex problem in the public sector. I owe this transition to the wonderful mentors I met through Bridge, who encouraged me to assess my worth and more importantly, act on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5q6Y6KgU431lMdmG37KdzQ.jpeg" /><figcaption>That post-presentation glow.</figcaption></figure><h4><strong>We need more spaces like this</strong></h4><p>If education is the first step in empowerment, we need more spaces like this that support women and non-binary folks, programs that are free of barriers, and which are built iteratively for and <em>with</em> marginalized groups in tech. Our experiences, the lenses through which we view the world are doubly important, especially in disciplines like Product Design that have an impact on our built and virtual environments. Diverse representation is simply not enough. Bridge not only builds capacity at the junior or intermediate level, but the kind of capacity required in leadership roles that design and shape technology used by all of us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a192225c4333" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itsbridgeschool/crossing-the-bridge-reflections-from-cohort-1-a192225c4333">Sink, Swim, or Cross a Bridge</a> was originally published in <a href="https://medium.com/itsbridgeschool">itsbridgeschool</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>