<?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 Paula Chuchro on Medium]]></title>
        <description><![CDATA[Stories by Paula Chuchro on Medium]]></description>
        <link>https://medium.com/@paula.chuchro?source=rss-3a64cb248d70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iDVku6iY3R1mlV1z1CweRQ.jpeg</url>
            <title>Stories by Paula Chuchro on Medium</title>
            <link>https://medium.com/@paula.chuchro?source=rss-3a64cb248d70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:52:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paula.chuchro/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[Applying Human Centered Design to Human Centered Design Alumni]]></title>
            <link>https://medium.com/university-of-washington-hcde-alumni/applying-human-centered-design-to-human-centered-design-alumni-5f2653257750?source=rss-3a64cb248d70------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f2653257750</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[alumni]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[university-of-washington]]></category>
            <dc:creator><![CDATA[Paula Chuchro]]></dc:creator>
            <pubDate>Sat, 01 Feb 2020 21:43:26 GMT</pubDate>
            <atom:updated>2020-02-01T21:43:26.841Z</atom:updated>
            <content:encoded><![CDATA[<h4>How the Human Centered Design and Engineering Alumni Leadership Board at the University of Washington applied HCD to their own alumni</h4><p>When you graduate from a university program, you can expect some level of communication as you become an alumni. How effective do you find it? Do you feel connected to the department in a way that is meaningful to you? Or do you quickly scroll to the unsubscribe button at the bottom of the email?</p><figure><img alt="2019 HCDE ALB: Mike Berg, Nathan Bilbao, Matthew Carthum, Sharla Akers, Paula Chuchro, Gary Anderson, Kendall Avery." src="https://cdn-images-1.medium.com/max/800/0*d42_7bYx4fuXteWE" /><figcaption>2019 Human Centered Design and Engineering Alumni Leadership Board. From left to right: Michael Berg, Nathan Bilbao, Matthew Carthum, Sharla Akers, Paula Chuchro, Gary Anderson, Kendall Avery.</figcaption></figure><p>In January 2019, the University of Washington Human Centered Design and Engineering department formed the first <a href="https://www.hcde.washington.edu/alumni-board">Alumni Leadership Board (ALB) </a>to address the need for more intentional alumni and student community building, career connections, and industry skill sharing outside the academic curriculum. Our group of committed alumni have a desire to give back to the next generation of HCDE graduates and build the HCDE network for years to come.</p><p>Before we could truly appreciate our mission and principals or what events we wanted to create for our alumni and wider HCDE community, we wanted to learn more about our users: our fellow alumni. We wanted HCDE alumni to reengage with us, not unsubscribe.</p><p>So we did the only natural thing for a group of UX professionals to do: perform user research on our alumni. What were their needs? What challenges were they facing in their careers? How might the amount of time since their graduation inform their needs? If we were going to serve as a useful resource to fellow alumni, we first needed to research their goals, behaviors, contexts, and a variety of post-grad career trajectories.</p><h3>Leading a Directed Research Group</h3><p>During the summer of 2019, under the direction of former HCDE Department Chair, Dr. David McDonald, Michael Berg and I led a group of both undergraduate and graduate students in a<a href="https://www.hcde.washington.edu/research/directed"> Directed Research Group</a> (DRG) to answer: what needs do HCDE alumni have post graduation and how can we best enrich them as well as the department?</p><p>The students were split into two groups; one group studied recent grads who were early in their careers, and the other studied alumni who had been out of the program for a longer period of time and were more senior in their careers. The students did secondary research about alumni programs, developed interview scripts to conduct semi-structured interviews with representative users and completed an analysis of their interview findings. They then created user personas and a journey map for both the junior and senior career alumni. Finally, they presented their findings to a group of stakeholders: the Alumni Leadership Board as well as HCDE department staff.</p><h3>Summary of Findings</h3><h4>Early Career Alumni</h4><ol><li><strong>Steep “first job” learning curve. </strong>Recent grads felt prepared academically and had plenty of group project work to boot, but felt overwhelmed to be a one-stop-shop UX person at smaller companies, did not know how to navigate the UX role in their organization, or get buy-in for the value of UX research and user centered design processes.</li><li><strong>Dislike of traditional mixers. </strong>Events that were primarily social events, centered on mingling or drinking, felt awkward and unappealing to attend.</li><li><strong>Eager to give back.</strong> Junior career alumni have a huge sense of empathy for students who will follow in their footsteps and would like to help them through mentorship.</li></ol><h4>Senior Career Alumni</h4><ol><li><strong>Give and get value. </strong>Alumni look for opportunities where they can <em>get </em>value, such as professional development, industry connections, and updates on the latest UX trends. They also hope to positively contribute to the department and give.</li><li><strong>UX connections come from everywhere. </strong>This finding recognizes that alumni value connections that they made at different phases of their journey and many were not tied to the department. Many of their career paths were shaped by connections made outside of school. This is important to understand when defining the ALB’s purpose to alumni among other resources they already have.</li><li><strong>Clear and personal communication matters.</strong> Alumni are looking for clear and personalized communication from the department so they feel like they matter.</li></ol><h3>Putting these Findings into Practice</h3><p>As the summer drew to a close, the next best opportunity to put these findings into practice was at the annual HCDE Alumni BBQ, a casual event that brought alumni together on the Seattle campus before the academic year began.</p><p>Armed with our enlightened understanding of the needs of our HCDE alumni, we did the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*vRdi08LkQS5YRx-LqUJnAw.png" /><figcaption>Give and Get cards were filled out by alumni at our annual BBQ inspired by one of our findings about how alumni want to interact with their alma mater.</figcaption></figure><p><strong>Finding: Clear and personal communication matters.</strong></p><p><strong>Action: </strong>We sent out a personalized email to alumni from the ALB to reiterate our excitement to see them individually and increase attendance.</p><p><strong>Finding: Give and get value.</strong></p><p><strong>Action: </strong>We created “Give/Get” cards for alumni to fill out. These were handed out and explained at the sign-in table but also laid out on folding tables for alumni to fill out. The intent was to not only ask alumni what they can give to the department, but what they can <em>get </em>to advance themselves and their UX career goals. This will help the board plan future alumni events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*DgYrJL_2F0vGTUiR" /><figcaption>Introvert-friendly activity set up at our annual Alumni BBQ.</figcaption></figure><p><strong>Finding: Dislike of traditional mixers.</strong></p><p><strong>Action: </strong>We created introvert-friendly activities like a poster board for identifying yourself along a spectrum of career tenure and industry type as well as another poster board dedicated to giving new students advice on post-its (It’s not a UX event without post-its!)</p><p>We were able to have a great event and the research inspired Give/Get cards led us to a new treasure trove of alumni data to use when we want to plan future events and evolve how we serve our alumni and the department in the most meaningful way.</p><p>Human centered design is at its core an empathy driven endeavor and applying it to our own alumni so we can create meaningful experiences in the future is a quintessential application.</p><p><em>Thank you to the students of the summer DRG, HCDE 496, Michael Berg and Dr. David McDonald.</em></p><p><em>To learn more about the UW HCDE Alumni Leadership Board or to get involved, visit us here: </em><a href="https://www.hcde.washington.edu/alumni-board"><em>https://www.hcde.washington.edu/alumni-board</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f2653257750" width="1" height="1" alt=""><hr><p><a href="https://medium.com/university-of-washington-hcde-alumni/applying-human-centered-design-to-human-centered-design-alumni-5f2653257750">Applying Human Centered Design to Human Centered Design Alumni</a> was originally published in <a href="https://medium.com/university-of-washington-hcde-alumni">University of Washington Human Centered Design &amp; Engineering Alumni</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Amazon Will Eliminate Package Theft Once and For All]]></title>
            <link>https://medium.com/@paula.chuchro/how-amazon-will-eliminate-package-theft-once-and-for-all-4d01f97b0127?source=rss-3a64cb248d70------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d01f97b0127</guid>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[amazon-echo]]></category>
            <dc:creator><![CDATA[Paula Chuchro]]></dc:creator>
            <pubDate>Thu, 11 Oct 2018 05:40:38 GMT</pubDate>
            <atom:updated>2018-10-11T05:54:32.296Z</atom:updated>
            <content:encoded><![CDATA[<p>Amazon’s Alexa Fund, a $100 million VC arm within Amazon, recently participated in a <a href="https://www.fastcompany.com/90241545/alexa-powered-amazon-houses-may-be-closer-than-you-think">$6.7 million investment round raised by Plant Prefab</a>, a modular home manufacturer based in California. It is clearer than ever that Amazon’s dominance in smart things (Echo Dots and Shows, microwaves and outlets etc) will crescendo in the world’s first mass market smart <em>house</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qVKGuur1D_zU8AKj.jpg" /><figcaption>A Plant Prefab home in Santa Monica, CA.</figcaption></figure><p>The wave of Alexa controlled microwaves, mirrors, TVs and security systems coming will be endless, but the first thing that came to my mind was the next evolution of one of Amazon’s bolder yet contentious products, Amazon Key; in particular, its in-home delivery solution.</p><p><a href="https://www.amazon.com/b?ie=UTF8&amp;node=17861200011">Amazon Key</a> is a security and keyless entry system that can be extended to allow an Amazon delivery person temporary access to your home to deliver a package inside rather than on your doorstep.</p><p>When it was first announced in October 2017, the opinion pieces and ridicule came in like clockwork. Opinion writer for the Washington Post called it, “<a href="https://www.washingtonpost.com/blogs/post-partisan/wp/2017/10/25/amazon-key-is-silicon-valley-at-its-most-out-of-touch/?utm_term=.a1ad0936fe07">Silicon Valley at its most out-of-touch</a>” and Digital Trends said, “<a href="https://www.digitaltrends.com/home/amazon-key-delivery-seems-invasive-and-creepy/">I’d rather have porch pirates steal my sponges than let Amazon in my house.</a>”</p><p>But that’s just it — what if Amazon didn’t have to go into your house to deliver your sponges? What if you could get the convenience of the theft-less delivery without compromising on your privacy and security?</p><p>I think Amazon is perfectly positioned to do two things:</p><ol><li>Create a built-in, Alexa enabled package receiving portal for its Plant Prefab homes</li><li>Create an ad-hoc, Alexa enabled package receiving portal for customers to retrofit or place outside their current homes</li></ol><p>Amazon has had a similar solution with Amazon Locker, a physical, publicly located locker to receive your package without it getting stolen. But you had to leave home to get it.</p><p>Instead, this package receiving portal would bring the best of Amazon Locker and Amazon Key to your doorstep. It would have keypad access similar to the Amazon Key feature does today, but the beauty here is that the delivery person wouldn’t actually have access to your home.</p><p>For the built-in variety, the portal, closet, receiver or whatever you want to call it would be big enough to hold large or tall packages and would be contained and have dual access: a door to the outside and a door on the home side that would only be accessible from inside the home.</p><p>For the ad-hoc variety, the receiver would look like a standalone closet or shed and sit near your doorstep.</p><p>It would be Alexa enabled so that when the keypad was accessed and the corresponding package delivered, the homeowner would get an Alexa notification as well as a push notification on their phone, similar to today.</p><p>Most importantly, the built-in version solves the “creepy” concern of the Amazon Key feature in its current iteration. Homeowners would never have to think about or feel uneasy about being startled by the delivery; it would just work in the background and packages could be retrieved whenever the homeowner wanted to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rgaZ-otzGHwQszGY.gif" /><figcaption>Majestic Milk Advertisement.</figcaption></figure><p>This solution is not necessarily new and those who came before us had similar delivery needs. The analogous historical and mechanical precedent for the concept was the milk door. Ah, milk: delivered to early 20th century homes via a built-in two-sided door contraption, allowing the milkman to put the milk inside, close the “burglar proof latch”, and let housewives safely retrieve it from inside. The difference with what Amazon could build is that it would be digitized, fortified with Alexa and therefore <em>smart.</em></p><p>Technology has always shape-shifted the American home to make our lives easier, safer, more convenient or beautiful. I think about the attached garage as a great example of a technological advance which ultimately reshaped homes. It is completely commonplace today to see homes in North America and abroad with an attached garage, but it was not always the case. Before cars, wealthy homes had a coach house, then for early motoring enthusiasts and engineers the structure became the motor house. And finally by the 1930s the attached garage was marketed as a luxury home feature to combat the inconvenience of journeying the forty or so feet from garage to home.</p><p>As our society continues its dependence on the convenience of delivered goods, I believe a package portal of this kind is the logical next step and one that will forever change the way homes are designed. The inconvenience of a soggy or stolen package is still too high and the frequency with which these brown cardboard boxes show up at our door continues to grow. This is what the future will feel like for package delivery and the feature will be standard in new homes one day, whether Amazon builds them or not.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d01f97b0127" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Iconography of Sharing]]></title>
            <link>https://medium.com/microsoft-design/the-iconography-of-sharing-183a1ad9c6f1?source=rss-3a64cb248d70------2</link>
            <guid isPermaLink="false">https://medium.com/p/183a1ad9c6f1</guid>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[icons]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Paula Chuchro]]></dc:creator>
            <pubDate>Wed, 08 Feb 2017 17:43:56 GMT</pubDate>
            <atom:updated>2019-08-27T15:22:39.897Z</atom:updated>
            <content:encoded><![CDATA[<h4>Windows has updated its share icon — here’s why it matters</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/1*TqFrTQhRzRVtGy2JGS29YA.png" /><figcaption>Previous Windows share icon on the left and the new share icon, right.</figcaption></figure><p>Icons are charged with interpretative metaphors. The share icon in particular — and what it should look like — has been passionately debated over the past few years among web and app designers. The concept of sharing is a tough thing to communicate in just a few line strokes. As a result, many people have gotten used to whatever icon their mobile phone platform uses.</p><p>Recently, our own share icon got us thinking. Does the current visual representation convey sharing in the best way? From data in our usability labs, we’ve consistently seen people misunderstanding or looking past the icon in the user interface, especially when a label didn’t accompany it. When it stood alone, many people saw its circular shape and mistakenly interpreted it against other ring-shaped icons like sync or refresh or loading.</p><p>What to do? How do you define the metaphor, and better guide people to share?</p><h4>Meaningful vs. Ubiquitous Icons</h4><p>We believe an icon can be successful in two important ways. When it’s a meaningful icon, it’s a pretty literal representation. The icon does what it says it will do because it calls upon a real-world object or action. For example, a trashcan to mean delete, get rid of, or throw away is meaningful thanks to how we use trashcans in the real world.</p><p>An icon can also be successful in a ubiquitous way — something that’s universally accepted as a true representation regardless of its symbolic meaning. Think about the red octagon to represent stop in the United States and other countries. It works because it’s ubiquitous, not because an eight-sided shape means stop. If you live in Japan, the traffic sign is an inverted red triangle and in Papua New Guinea the stop sign is a curved shield. These things become understood, across a shared language.</p><p>With this in mind, we set out to explore a new share icon design. We wanted everyone to discover it, interpret it, and utilize it, without any confusion or clunky translation. Instantaneous, intuitive iconography. At the heart of it, we just want everyone to be able to easily share. After a round of thinking about what a meaningful icon could look like, there seemed to be less clarity rather than more. We considered different gift icons (gifting = sharing), we thought about how the word “share” translated in other languages, we sketched people handing each other objects and we even thought about hands grabbing pizza slices (we got weird about it), but they all seemed to stray from our goal of creating a simple, quickly understood icon.</p><h4>Opting for Familiarity</h4><p>In the end, we designed an icon that benefits from ubiquity and familiarity. We looked at the icons users were seeing out in the wild and tested similar variations to see which icons best represented what it meant to share. We A/B tested them against the old share icon in the Photos app, with and without labels. You may have seen us testing a few different kinds of icons in the past few months if you used the Photos app.<br> <br>The best performing icon was our new icon, a rectangle housing a swooping arrow that indicates motion out of the rectangle. An exit, a movement, a share from one point to another. Your favorite websites and apps use this same “swooping arrow” in varying designs, which helped with the familiarity factor we were after. It performed beautifully in A/B testing, and made us confident that making a significant change would ensure usability and clarity for millions of Windows users.</p><h4>It’s Official</h4><p>The new share icon shows up in some of your favorite apps in the latest Windows Insider build. Universal Windows app developers will see this icon available in the Segoe font as a replacement for the old share icon. As always, we’ll keep listening to your feedback and embrace the opportunity to iterate and improve as needed. We hope all app developers and users alike will find the new icon a welcome usability change to Windows! Happy sharing, everyone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHAbQ50XTjmizdkF7kElQQ.png" /><figcaption>You can see the new share icon being used in various apps and in the Segoe font.</figcaption></figure><p><em>To stay in-the-know with </em><a href="http://www.microsoft.com/design?source=post_page---------------------------"><em>Microsoft Design</em></a><em>, follow us on </em><a href="https://dribbble.com/microsoft?source=post_page---------------------------"><em>Dribbble</em></a><em>, </em><a href="http://www.twitter.com/microsoftdesign?source=post_page---------------------------"><em>Twitter</em></a><em> and </em><a href="http://www.facebook.com/microsoftdesign?source=post_page---------------------------"><em>Facebook</em></a><em>, or join our </em><a href="https://insider.windows.com/?source=post_page---------------------------"><em>Windows Insider program</em></a><em>. And if you are interested in joining our team, head over to </em><a href="http://aka.ms/designcareers"><em>aka.ms/DesignCareers</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=183a1ad9c6f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/microsoft-design/the-iconography-of-sharing-183a1ad9c6f1">The Iconography of Sharing</a> was originally published in <a href="https://medium.com/microsoft-design">Microsoft Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Zen of a Non-Technical PM]]></title>
            <link>https://medium.com/@paula.chuchro/the-zen-of-the-non-technical-pm-528b7512716c?source=rss-3a64cb248d70------2</link>
            <guid isPermaLink="false">https://medium.com/p/528b7512716c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[program-management]]></category>
            <category><![CDATA[non-technical]]></category>
            <dc:creator><![CDATA[Paula Chuchro]]></dc:creator>
            <pubDate>Fri, 19 Aug 2016 08:57:11 GMT</pubDate>
            <atom:updated>2017-01-05T10:07:09.662Z</atom:updated>
            <content:encoded><![CDATA[<h4>5 Helpful Tips for Getting Started as a Non-Technical PM</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ipOOUjdcMcc1XnNMO9Wy-Q.jpeg" /></figure><p>Congratulations on landing a <a href="http://www.quora.com/What-is-the-difference-between-Program-Product-and-Project-manager-roles">Product Manager (or Program Manager)</a> job without a Computer Science degree! You are a unique butterfly. You didn’t come from a CS background, and yet you convinced a company that you have the raw talent needed to be a successful PM. Through your interviews you have exhibited the tenacity and intellectual horsepower needed to learn the technical side. Well done.</p><p>But you also have a tall order ahead of you if you are going to succeed, and people will be watching to see if you can rise to the challenge. I experienced this first hand and would love to share what I learned.</p><p>Five years ago I graduated with a B.S. in Management from the University of Illinois and was getting ready to start my job at Microsoft as a Program Manager on the Internet Explorer team. From a product perspective, I knew my biggest strength was my ability to come up with meaningful and user-centered product designs. I could empathize, ideate and reason. I spent my spare time thinking of ways to improve the sites I used (MySpace, Gmail, thefacebook.com…) and annoying the people who worked on them with my feedback submissions. Yet from a technical perspective, I had taken only two Computer Science classes by that time and my only “shipped code” was some Pokémon and <a href="https://en.wikipedia.org/?title=Rocket_Power">Rocket Power</a> sites I made in 1999 using <a href="http://en.wikipedia.org/wiki/Netscape_Composer">Netscape Composer</a>. ☺</p><p>Today, I am a PM on the Core User Experience team in Windows and before that I worked on IE and Microsoft Edge, where I created many of the browser’s UX features people use everyday. While being technical is only one part of being a successful PM, you can’t be a <em>great </em>PM without it. I cannot stress this enough. You need to hone your technical skills to understand feature trade offs, propose implementation alternatives and learn how to become an asset to your devs instead of a burden. I hope I can help you with some very practical tips to get you off to a great start.</p><h4>1. Find Your “Can I Ask You a Stupid Question?” Buddy</h4><p><strong>The Situation: </strong>A very senior developer tells you to “take a dump of the content process.” Wait, what?</p><p>If you have an awesome manager, they’ve set you up with someone who can be your mentor. If that’s your situation, then lucky you! Utilize that person as your go-to for questions about how to do your job. But it’s understandable that even if you were assigned a mentor, sometimes those relationships don’t feel natural or you still don’t feel like you could truly ask that person a “stupid question.” No problem, but start to feel around for who you <em>can</em> ask those questions to. Here’s how to spot them.</p><p>Usually, the best “Can I ask you a stupid question?” buddy is also somewhat “junior” in that they have only been a PM themselves for about two to three years. These people make for great buddies, because they remember what it was like to learn all the ins-and-outs of the team and they will be more likely to empathize and help you. Plus, they’re not too senior and aren’t managers yet, so they don’t have as much on their plates and can spare the time.</p><p>Another way to spot these wonderful people are by noticing who stops by your desk, says hello, and seems to be friendly and welcoming. Usually this person is already trying to make you feel welcome and will be open to helping you or answering your questions.</p><h4>2. The Bug Database is Google (or Bing)</h4><p><strong>The Situation: </strong>You just started your new job and everyone is talking about CAT jobs.</p><p>Nothing can shake the confidence of a resourceful and smart PM-in-training like not being able to communicate with the rest of the team. The twist for someone coming from a non-technical background is that you can’t necessarily distinguish the <em>computer science</em> terms from the <em>company specific</em> vernacular and acronyms.</p><p>My first few days at Microsoft on the Internet Explorer team I thought “perf” was a reference to “perfect.” Two hours later I learned it meant “performance,” as in, how long it takes for a webpage to load. Another one? CAT jobs. Obviously this has something to do with cats going to work. Alas, it stood for Code Analysis Tool, which is what our devs use to track their code through code reviews and subsequently queue jobs for check-in into the code base at large.</p><p>So what’s the fastest way to “ramp up” when you don’t know what’s what? Well, all the information flow on most product teams is happening in three places:</p><ol><li>Meetings (or hallway conversations)</li><li>Email or Slack</li><li>The bug/issues database</li></ol><p>Since you don’t have magical access to everyone’s emails and you can’t attend every meeting, unlimited access to the bug database is the next best thing. People are commenting there, explaining things to one another, using acronyms within useful contexts, reasoning about the right fix, weighing the severity of issues and so on.</p><p>The bug database is a <em>gold mine</em> for finding information on any topic you want to learn more about. Of course, talking to people is the absolute best place to start, but eventually your coworkers have to do their jobs and don’t have hours to define things for you. Going into the bug database yourself is perfect because you can navigate mountains of information on your own time and at your own pace.</p><p>All you have to do is start querying for the terms you’re interested in, and before you know it, you’ll be able to paint a picture of how a feature is architected, the kinds of bugs it’s prone to getting, and what its technical limitations are. And even if you don’t emerge from the bowels of the database with a perfect understanding of how something works, you will surely be more equipped to ask more fully formed and useful questions of your peers the next chance you get.</p><h4>3. “Let’s draw it out.”</h4><p><strong>Situation: </strong>A technical issue is blocking your feature’s “Plan A” design and your dev warns you to start pulling out your “Plan B” design alternative, because it’s easier to implement. But “Plan B” is a serious feature downgrade and an insulting slap to the user’s face!</p><p>This tip is incredibly serious and not to be taken lightly. As someone who is less technical, it is your duty to help engineers come to the surface for air when a problem can seem impossible to overcome. This is where you use your ability to take a step back from a problem and ask the dev to “<a href="https://www.reddit.com/r/explainlikeimfive/">Explain Like I’m Five</a>” so you can use the whiteboard to draw out the logic of the code and talk through the constraints together.</p><p>Nine times out of ten this will bring both of you to a better understanding. The software engineer changes his or her cognitive modality from a verbal mode to a spatial and visual one by drawing on the whiteboard. A magical moment occurs. It is usually marked by the dev stopping mid-sentence as they step away from the whiteboard, scratching their chin and saying, “Oh, wait I think I know how we can do it now.” Eureka!</p><p>These are beautiful, win-win moments. As the PM you can use your acute observation skills to engage with the dev in the logic and mapping of the code and thus ask the very question that strikes a chord and leads them to a breakthrough.</p><h4>4. Have the Meeting Before the Meeting</h4><p><strong>Situation:</strong> You are having your first feature specification review and a dev manager who knows everything about the history of space and time will be there.</p><p>If you have set up the meeting for Friday, try to find time with the most important stakeholders on Wednesday or Thursday. Make sure this time is one-on-one, frame the problem and solution you are working on and walk through your deck or document as appropriate. This gives you time to get to know their working style, learn from them and create a positive relationship built on trust and transparency.</p><p>If you do not set this up ahead of time, you will be swimming in rebuttals and disagreement on the day of the review when there are numerous people in the room. It can be very difficult to lead a review as you realize there are holes in your arguments and major implications you did not consider. Don&#39;t do that to yourself! Get out all the technical nuances with folks beforehand so you&#39;re not caught off guard. You will see just how smoothly a meeting can go if you have the meeting before the meeting.</p><h4>5. Eat Lunch with Your Devs</h4><p><strong>Situation: </strong>You’re hungry. Your devs are hungry.</p><p>Eat lunch with the people you work with! This is a fun and simple one, because you’re likely to do this anyway. Lunch can be your most productive meeting of the day, because it’s a perfect time to catch up on what is happening on other teams. What are our managers focused on and how is the product vision changing? What features are in? What features are out? What big implementation decisions just got made?</p><p>Lunch is a relaxed way to get to know and build relationships with fellow engineers and to observe their strengths and areas of expertise. In the long run, getting this extra hour of stimulating discussion about the product has made me a more effective PM. When it’s time to clear our lunch trays and return to our desks, I’m able to make more informed and well-rounded decisions because I’ve consulted a variety of really smart and diverse people.</p><p>Best of luck to you and always feel free to reach out to me on Twitter @PaulaChuchro with any questions about being a PM!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=528b7512716c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Devil is in the Defaults: Flushing in the Ladies Room]]></title>
            <link>https://medium.com/@paula.chuchro/the-devil-is-in-the-defaults-flushing-toilets-and-females-13f51f043179?source=rss-3a64cb248d70------2</link>
            <guid isPermaLink="false">https://medium.com/p/13f51f043179</guid>
            <category><![CDATA[toilets]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Paula Chuchro]]></dc:creator>
            <pubDate>Fri, 19 Aug 2016 07:50:31 GMT</pubDate>
            <atom:updated>2016-08-19T07:54:55.514Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me forewarn you that, yes, what follows are some thoughts about the user experience of flushing public toilets. While this particular example may not be glamorous, it is a reminder that design is everywhere and affects every experience in our lives, no matter how life-changing or routine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*-cplE4VSAoOdM1d0STZ2Ww.png" /></figure><p>You have probably seen the water-saving, green handle on a public toilet near you — carefully instructing you to move the handle UP for #1 and DOWN for #2. This is the Sloan Valve Company’s environmentally friendly flushing system. It is an ingenious product that helps all of us do our part to make saving water easy.</p><p>What struck me on a recent visit to the ladies room, was the amount of instructions this one sign insisted on communicating. Take the capitalization of “UP” and “DOWN.” The fact that these words are underlined. The arrows. The dotted-line impressions of the handle in motion. The parenthesized types of waste just in case you are not familiar with the colloquial meaning of “#1” and “#2.” Don’t forget the water droplets. And last, but not least, the very small font used in a paragraph in a last ditch effort that begs the user, “Please, for the love of God, this only saves water if you follow the instructions.”</p><p>Why all the over explaining? Are people not following the instructions? In design, every additive design element has a story behind it, and here there were an overwhelming number of cues for what should otherwise be very simple instructions. I started to infer that even though the system is designed to save water — which I know for a fact it does — it might be able to save even more water if people used it correctly.</p><p>So why is it so hard to press up for #1 and down for #2? The devil is in the defaults. And I think it particularly affects women.</p><p>For years, we have been pressing down on toilet handles, or for the more bacteria fearing among us, using our foot to flush. This does not change over night, especially when the physical affordance communicates “push down.” Have you ever pulled up on a door handle? Yeah. As a start it would be helpful to make the most likely action the water-saving action so users can do the right thing without having to think about it.</p><p>But wouldn’t this result in…incomplete flushes? Yes, yes you are now getting a visual in your head about #2 unsuccessfully making it down the plumbing, because #1 doesn’t provide enough water to properly flush it away. If it’s the default, bathrooms might be grosser this way. Very true.</p><p>That’s why I think this is a design that can benefit from considering the differences between the sexes. Women’s and men’s restrooms differ and so do the behaviors of the people who use them. After all, men’s bathrooms almost always have urinals and stalls; women, only the latter.</p><p>Assuming that most men use the urinals for #1, you can deduce that men are using the stalls primarily for #2. In that case, make DOWN use more water for #2 in men’s bathrooms.</p><p>For women’s bathrooms, the stalls are the only option, so you can think about the frequency of each type of waste to determine the right default. Most adults go #1 every 2–4 hours or six to eight times a day as opposed to #2 which is less common, 1 or 2 times a day for healthy adults. In that case, make DOWN use less water for the more common, #1 in women’s bathrooms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*pTuMZltVXHYTm1M3H1vKjg.png" /></figure><p>A simpler sign design might also help and be more possible with the right defaults.</p><p>And unisex bathrooms? Perhaps the default for women proposal is the right choice, but conducting a study could help make the call.</p><p>Huge shout out to Sloan Valve Company if you are out there reading this— I love your products and surprised myself with how much time I spent thinking about toilet flushing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13f51f043179" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thomas Jefferson and the Pursuit of Multitasking]]></title>
            <link>https://medium.com/@paula.chuchro/thomas-jefferson-and-the-pursuit-of-multitasking-4117107edc75?source=rss-3a64cb248d70------2</link>
            <guid isPermaLink="false">https://medium.com/p/4117107edc75</guid>
            <category><![CDATA[thomas-jefferson]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Paula Chuchro]]></dc:creator>
            <pubDate>Sat, 11 Jul 2015 09:58:32 GMT</pubDate>
            <atom:updated>2015-07-11T15:19:39.259Z</atom:updated>
            <content:encoded><![CDATA[<p>I am always fascinated by the parallels we can draw between the technology we build today and the mechanical predecessors that solved similar user needs long before computers existed. My latest obsession is with a multitasking tool I saw when I visited Monticello, Thomas Jefferson’s home, gardens and slave plantation just outside Charlottesville, Virginia. The home features a variety of gadgets and early inventions of productivity, efficiency and scientific discovery that are worth taking a closer look at.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DZKfS5IOJxoPfk9AgkEC5g.jpeg" /></figure><p>What’s immediately evident as you tour the home is that Thomas Jefferson loved to learn. He loved books so much he continued to buy them for his personal library even when he was grossly in debt. He spoke five languages and studied many more. He taught himself architecture and designed the neoclassical residence that sits on Monticello, Italian for “little mountain.” He hated wasting space so as you walk throughout the house you notice that closet space was lofted, dining tables could be cleverly folded away and there were only small, winding staircases in the home, tucked out of sight and very unlike the neoclassical, grand staircases of the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*Ku8SloNZGgogLOlhm1WwsQ.jpeg" /><figcaption>The Hall at Monticello.</figcaption></figure><p>He was obsessed with novel innovations and science. The entrance hall to his residence compelled his visitors to take in a room that felt more like a museum than a foyer. Arrowheads from native tribes and a map of the Louisiana Territory hung on the wall while a dinosaur jaw sat in the corner. A dual-faced clock showed the time inside the home and on the outside of the home to the slaves and foremen in the fields.</p><p>Throughout the house, clues that Thomas Jefferson was a modern day technophile were strewn all around. Gadgets and interesting tools were everywhere. Some of the items were wooden contraptions put together by skilled slaves like John Hemmings at Jefferson’s whim. Jefferson appreciated invention and cared much more for enjoying a tool or novelty than claiming patents on it. I suspect that if Thomas Jefferson was alive today he would probably be wearing an Apple Watch, reading about SpaceX on his Kindle and sitting at a desk trying to take apart a Surface to understand the hinge mechanics. It was refreshing to imagine this once phantom character as a real person who lived a real and fascinating life outside of a few pages in a 5th grade history book.</p><p>As we entered his cabinet (a room used as an office and study), gadgets and books littered tabletops and a desk. You can look at a panorama of the room <a href="http://www.monticello.org/site/house-and-gardens/cabinet">here</a>. Our tour guide pointed out a peculiar, revolving wooden stand on the table. I stared at it closely as he goaded us to guess what it was for. The wooden cube had four sides and a top face that slid out to hold books at various angles. The top face could be positioned above one of the side faces, and the whole piece could be spun around by means of a wooden pole in the center.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*m91zPerW-WS1JAhZlfWWKQ.jpeg" /><figcaption>A replica of the revolving book stand.</figcaption></figure><p>What a fun and brilliant piece of early multitasking technology! For someone like Jefferson, who loved to read and needed to reference many books at a time, this was an ideal multitasking tool. He could keep the primary two books he was referencing or comparing in front of him at the same time and spin to any other book as needed.</p><p>I just loved the idea of this stand and how cleverly it allowed him to quickly reference pages across multiple books in the physical world. And yet the task for us in the 21st century is even more exciting and even more daunting with the existence of a library much greater, and less confined by physical space, than Thomas Jefferson could have ever imagined: the internet.</p><p>For about twenty years, browsers have acted as our very own “revolving book stands”; amazing tools for viewing, reading, comparing and creating the content that makes up the internet. The faces of Jefferson’s book stand remind me of a row of tabs you can switch between. The top and bottom ledges in front of you act as a version of side-by-side windows, letting you compare and reference two pages at once.</p><p>The best part is today you don’t have to be a founding father or wealthy Virginian to multitask in a world of knowledge and content. Millions of people everyday open a browser to read, work, play, create and get things done. The need to easily compare, consume, reference and/or create content is ever-present, but the tool we use has more to do with digital “tabs” or “windows” than wooden ledges. How incredible is it that as a human race we have the same need “to easily and efficiently find and consume information” over two-hundred years later?</p><p>This revolving book stand struck me in a nerdy way, because I spend a lot of time thinking about productivity. I work on the Microsoft Edge browser for Windows and we are always thinking about productivity and how to help people get more done. There’s something about working on a product that acts as a window to the world to so many people that makes me excited to keep thinking of ways to make it better. When you realize that someone over two-hundred years ago was trying to solve a similar problem, it’s humbling and inspiring.</p><p>Because of this little moment in pattern recognition between an antique and modern tool, I have found real value in thinking about a user need or task and how people used to complete it before computers. It works best with user facing features that require direct interaction or input. For example you can answer questions like, is there a natural or mechanical ancestor for the feature or product you’re building? What’s the core user problem you’re trying to solve? How have people solved this problem before computers? What physical limitations don’t exist in software that could make our product truly amazing?</p><p>As product designers, looking to the past to inform the problems we’re trying to solve today is valuable. This line of thinking can expose something about how a feature can be designed and the context it’s being created for.</p><p>On a final note, I’m pretty sure Thomas Jefferson would have loved the internet, don’t you think? :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4117107edc75" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>