<?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 Jeremy Segal on Medium]]></title>
        <description><![CDATA[Stories by Jeremy Segal on Medium]]></description>
        <link>https://medium.com/@jdsegal?source=rss-a7b3debc8503------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*n8vDEDY0DLnE7WoB.jpg</url>
            <title>Stories by Jeremy Segal on Medium</title>
            <link>https://medium.com/@jdsegal?source=rss-a7b3debc8503------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:56:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jdsegal/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[MProduct Club Update: One Year Later]]></title>
            <link>https://medium.com/mproduct/mproduct-club-update-one-year-later-e08838d4dd70?source=rss-a7b3debc8503------2</link>
            <guid isPermaLink="false">https://medium.com/p/e08838d4dd70</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[university-of-michigan]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jeremy Segal]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 19:01:34 GMT</pubDate>
            <atom:updated>2020-06-13T22:11:39.867Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GWASH40EU-_HEtlt.png" /></figure><h3><strong>Overview</strong></h3><p>Since MProduct’s founding last summer, the club has grown into a strong organization of students all working to become better product managers. MProduct was the first club at Michigan to offer recruiting and educational resources for PM. Our organization has grown to 102 total members, 49 of which were in our winter cohort. This past semester, we hosted biweekly meetings with educational lectures as well as extra workshops. Since moving to a virtual setting, we have had bonding, recruiting, and informational events to keep our club engaged. Our teams have also pursued many different opportunities to encourage club growth and improvement. We also have many new initiatives in progress, and we can’t wait for what’s to come.</p><p><strong>In this article:</strong></p><ol><li><strong>Updates on each of our teams:</strong></li></ol><ul><li>Product Guide: Creating a complete guide to all things product</li><li>Product Commercialization: Help give more hands on PM experience to MProduct club members</li><li>Industry Engagement: Trying to connect the club with PMs and more people in industry, and writing a weekly newsletter sent to our entire organization</li><li>Kode Labs: Consulting and cross-disciplinary team with the company KODE Labs</li><li>Education: Educating the MProduct club members on important product topics and skills</li><li>Content: Writing and publishing articles for the wider Michigan and PM community</li><li>Conference: Planning a conference for student PMs and industry speakers</li><li>Voxel51: Consulting team with the company Voxel51</li></ul><p><strong>2. Q&amp;A Section with the following questions:</strong></p><ul><li>What has been the most enjoyable or meaningful part of doing this work?</li><li>What has been challenging?</li><li>What have you learned?</li><li>Are there ways the community can help you out?</li><li>Anything else your team would like to share with the world?</li></ul><p><strong>3. Overall club progress update and vision</strong></p><h3><strong>Team Updates:</strong></h3><p>The MProduct teams have been busy over this past semester. Even with the transition to virtual meetings, our teams stayed focused and made real progress in developing the club’s many resources and initiatives. The teams have been working on various tasks including two product management consulting projects, sending out a weekly newsletter, creating new educational and recruiting content, connecting with product leaders, and much more. We would like to share some of our work during the Winter 2020 semester.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2y6nhPtNS4ptgrcKUdqkjw.png" /></figure><h4><strong>Product Guide:</strong></h4><p><em>Stephanie Shoo, Jenny Suh, Neil Gurnani, Vineet Parvathala, Erik Wihlborn</em></p><p>The product guide team is in the process of building a one-stop-shop for all product-related wants or needs. After searching for MProduct members’ pain points, the team decided on having four key components:</p><ol><li>Alumni Database</li></ol><ul><li>Get in touch with those who have gone through the process and have been successful in industry, and learn their tools and insights.</li></ul><p>2. Recruiting Information</p><ul><li>What is the recruiting timeline? How do I land an interview? How do I ace my interview? These are some of the many questions that will be answered in this part of the guide focused on getting you a job in PM.</li></ul><p>3. How to start a product</p><p>4. Community Engagement</p><ul><li>Find out what other MProduct members are working on and get involved.</li></ul><p>The team is in the process of filling up the Product Guide with useful, relevant content through reading books, researching online through sites such as Medium, talking to other PMs in industry or college students with product experience, and personal experience.</p><p>Over the next semester, they’re working on customer discovery for the MVP (minimum viable product) of the guide, transitioning this bare-bones MVP into a more full-fledged website, gathering feedback, and continuously iterating. The vision for the product guide is to be a one-stop-shop for all PM reference material including recruiting and PM skills.</p><h4><strong>Industry Engagement:</strong></h4><p><em>Sean Stapleton, Akul Vijayvargiya, Salik Aslam, Mary Vogler</em></p><p>The Industry Engagement team has also managed a lot of change since our campus went virtual. Originally, they recruited guest speakers to allow MProduct members to better understand the industry and to find networking opportunities. Now, they are focused on keeping the MProduct community engaged with the PM industry.</p><p>They’ve had two main achievements. The first is creating a weekly newsletter that is in its sixth week and reaches 109 people with a 63% open rate and a 28% click rate, both very high numbers for an email newsletter. The second is organizing an AMA (Ask Me Anything) with Liam Bolling, a Product Manager at Google Maps. This was actually set up by cold emailing Liam after finding him on Sherpa (joinsherpa.co), a site for finding tech mentors.</p><p>Coming up, they’re working on continuing and receiving more feedback on the highly popular newsletter, as well as trying to connect more members of MProduct to PMs in industry.</p><h4><strong>KODE Labs:</strong></h4><p><em>JC Tan, Jessie Singh, Oliver Li, Rithik Aggarwal, Samay Shamdasani</em></p><p>The KODE Labs team had one of the most unique projects; getting the chance to work with local Detroit startup KODE Labs. The company uses existing building data to make an accessible interface for building operators to diagnose problems and cut costs. At KODE Labs, the MProduct team was brought on to design a smart interface dashboard for executives to analyze building data. The team performed two rounds of customer discovery and interviews including cold emailing and LinkedIn messaging many executives and “C-suite” level employees. They then used the information gathered to present a product proposal to the company. After receiving feedback, the team designed a prototype for the chief product officer and head PM. This was a semester-long project that was wrapped up at the beginning of May.</p><h4><strong>Product Commercialization:</strong></h4><p><em>Aniket Jain, Noah Gustafson, Max Walts, Steven Dirjayanto, Divyansh Agarwal, Benjamin Walton, Saadat Zaman, Yash Ramchandani, Sean Stapleton</em></p><p>We’re going to have to be vague since the Product Commercialization team’s project is still mostly confidential and is likely to change quickly through iteration. However, one purpose of the team is to launch a product within MProduct that will continue to grow and be iterated upon by the team and its current and future members. One of the best, if not the best, ways to gain experience as a PM is hands-on experience with a product. As the team continues to iterate upon the product, they will gain the experiences of actual PMs in industry.</p><p>Initially, they had tried to create a product targeted at UX designers and small businesses in Ann Arbor; however, it didn’t work out since their product didn’t address the needs of their customers. Thus, they stopped that project and have been in the process of building a new app. Their process has included planning ahead, creating product timelines, and developing in React.</p><p>Sometime around September, expect to see an app pushed out. Their initial user base will consist of University of Michigan students, and they will proceed to expand afterwards.</p><h4><strong>Conference:</strong></h4><p><em>Ria Joshi, Connor Turco, Charles Bruckman, Atharva Talpade</em></p><p>The conference team was forced to adapt to the circumstances more than most teams. They originally aimed to arrange a MProduct-hosted product management conference, including guest speakers from different companies from startups to Big Tech, where students would be able to connect with and learn from product leaders and expand their network.</p><p>With our sudden change to virtual-everything, the team made adjustments. Since the team realized that an in-person conference would be far more beneficial due to better networking opportunities as well as other factors, the conference is tentatively pushed to Fall 2020. MProduct will continue connecting with product leaders in a virtual setting, and we hope to resume in-person events as soon as it is safe to do so. If you or any product leaders you know would like to participate as speakers or panelists in a future conference, please send an email to <a href="/service/mailto:mproduct-contact@umich.edu">mproduct-contact@umich.edu</a>!</p><h4><strong>Education:</strong></h4><p><em>Austin Haag, Ashwin Sreevatsa, Jeremy Segal, Kelley Sweitzer, Samay Shamdasani, Sasha Golubova, Sim Sandhu</em></p><p>One of the founding principles of MProduct is to educate the next generation of PMs. This team’s task has been to educate the MProduct body on various topics through seminars and workshops. Over the past few months, the education team has made new lectures for the fall semester on topics including marketing and growth. They also recently hosted a recruiting panel and are about to host a virtual internship discussion. With this physical distance separating our members, the team has also begun to host virtual social events to help everyone keep connected in these tough times. In the future, the team is also preparing mock interview sessions for students to prepare for fall recruiting, ways to stay engaged in product discussions through Zoom seminars and book clubs, and much more!</p><h4><strong>Voxel51:</strong></h4><p><em>Anand Dukkipati, Chairul Kim, JC Tan, Max DiFazio</em></p><p>This team worked with the Ann Arbor based startup Voxel51, which uses AI on video data. The company takes large data files of video surveillance to annotate on images in the video to analyze movement. Voxel51 had primarily worked for the government, but was trying to shift to the private sector. Our team assisted them with this transition by creating a roadmap for future growth. They first conducted lots of customer interviews to find a new client base for the company, then created user stories from the interviews. Part of the new plan for the company was creating a better interface for clients to interact and organize the data files. This would help for users to help better get the insights they want from the videos and filter unnecessary information. The team also made the suggestion to be able to use video replay to regression test against a newly trained model to see if the model has become better or worse. Another part of the plan was to make a cost estimation for video annotations for other companies to use Voxel51’s services. The project finished at the end of the semester.</p><h4><strong>Content:</strong></h4><p><em>Austin Haag, Jeremy Segal, Rohan Prashant</em></p><p>Content’s main purpose is to educate the MProduct and general product management communities through articles such as the one you’re currently reading. We post biweekly articles on our Medium and LinkedIn pages with this being our fourth article of the semester. Since the club’s founding, we’ve grown our LinkedIn to hundreds of new followers. Articles have included spotlight pieces on real-life PMs, design principles and what to do with your summer. Our most viewed article, on Microsoft PM Philip Ruffini, has been our biggest success! You can check out the article here. You can look forward to recruiting posts on topics including job postings and interviewing tips. The content team also has an article on a PM from industry that will be published soon.</p><h3><strong>Q&amp;A:</strong></h3><p><em>Q: What has been the most enjoyable or meaningful part of doing this work?</em></p><p><strong>Conference</strong>: Seeing how much value we could be adding to students, especially underclassmen with little product knowledge, and also not just to the MProduct community but to all University of Michigan students.</p><p><strong>Product Guide</strong>: Building the team and getting to know them on a deeper level, understanding the importance of leading a team and how it stems from getting to know members, and the fun icebreakers we’ve done in our meetings.</p><p><strong>Product Commercialization</strong>: Getting more of a hands-on, experience-based learning approach than most of my classes. Trying out an Agile approach and being the scrum master.</p><p><strong>Industry Engagement</strong>: Learning while reading content and teaching other people through the newsletter. Having so many people in the club reach out and say that the newsletter is cool, and wanting to have their content added to the newsletter.</p><p><strong>Kode Labs</strong>: Having independence for how the project would go was a very valuable experience. The team of course had to use customer feedback, but they made many of the final decisions. It was also great to be on a team with other students interested in product that all were dedicated to the work.</p><p><strong>Education</strong>: It’s been valuable to learn about PM while making new educational experiences for other students in MProduct. Through creating workshops and lectures, they’ve gained a new mastery of material.</p><p><strong>Voxel51: </strong>The most challenging and enjoyable part was that they were given a blank canvas to decide what to do next. It was definitely stressful at first, but a great experience.</p><p><strong>Content:</strong> It has been great to explore a wide variety of topics and article ideas to keep our readers engaged! We also get to connect with so many people in MProduct and the PM community.</p><p><em>Q: What has been challenging?</em></p><p><strong>Conference</strong>: With COVID, it’s really hard to figure out a timeline for our conference. We can’t reach out to firms until we have a timeline set.</p><p><strong>Product Guide</strong>: There’s so much information out there, and finding the best resources to build a concise list is hard.</p><p><strong>Product Commercialization</strong>: After conducting a lot of customer research on our original idea, it didn’t work, so we had to make a large pivot, which cost a lot of time.</p><p><strong>Industry Engagement</strong>: With such a new team and product, it’s hard to understand what our audience likes, so we had to conduct many surveys.</p><p><strong>Kode Labs</strong>: When the customer research and preliminary product was presented to the company, it was difficult at first to understand the feedback and more forward. The team was in charge of designing the product, so it was challenging to take ownership over the entire process.</p><p><strong>Education</strong>: The team has lots of ideas and progress they want to make, so it’s hard to get everything done at once.</p><p><em>Q: What have you learned?</em></p><p><strong>Conference</strong>: Mission and value statements.</p><p><strong>Product Guide</strong>: The importance of outlining milestones as a team and getting feedback from all team members, and understanding why something is a problem along with how we can solve it.</p><p><strong>Product Commercialization</strong>: Workflow tools such as Trello and Figma. Realizing that PMs are not necessarily the leaders; sometimes engineers are the ones leading the discussion and explaining things to the PM. Learning that PMs aren’t all business and technical skills can be frequently used.</p><p><strong>Industry Engagement</strong>: Different mediums of knowledge (video, text, audio, diagrams) can engage different people better. People didn’t seem to like the practice interview questions; maybe it’s too far away from recruiting. Checking to see if we’re working towards the right purpose and if users agree with that purpose. Learning how to work with a team virtually.</p><p><strong>Kode Labs</strong>: As you adopt a product, feedback is crucial to iteration and change. Coordinating with your whole team is incredibly important to move forward. How to effectively speculate over the process of designing a product; they needed to measure success and give Kode Labs a plan for how they’d proceed when they didn’t know how.</p><p><strong>Education: </strong>Just from holding talks and creating lectures, they have gotten such a greater understanding of product. Since moving to virtual, the team has also needed to learn how to stay connected and communicate effectively.</p><p><strong>Voxel51:</strong> Interviewing someone on a topic where the interviewee knows far more than you do. The team often had to interview data scientists and engineers with expertise in AI and computer vision so they needed the confidence to ask the questions and research some of the answers later. They also started meeting right when Michigan moved to virtual learning, so there were lots of learning opportunities in coordinating and taking ownership of their individual work.</p><p><em>Q: Are there ways the community can help you out?</em></p><p><strong>Product Guide</strong>: If you have any resources that you think would belong in the guide, please send them to any of the team members!</p><p><strong>Industry Engagemen</strong>t: We’d love it if you could fill out the surveys we send out to the MProduct community, it really helps us improve the newsletter!</p><p><strong>Education</strong>: Make sure to answer our MProduct surveys. We are always open to feedback on new events and educational topics.</p><p><strong>Content</strong>: Feel free to reach out by commenting on our Medium or LinkedIn with any feedback or ideas for new articles!</p><p><em>Q: Anything else your team would like to share with the world.</em></p><p><strong>Product Guide</strong>: The best way to learn is to teach, such as building a guide or writing articles. The product guide is a great way to learn but you can always try building your own to learn even better.</p><p><strong>Product Commercialization</strong>: We’re really excited for our first deployment!</p><p><strong>Kode Labs</strong>: Working on a project with other MProduct members is a really solid way to get experience. There are lots of learning opportunities from working with other team members. The PM consulting setup in MProduct is very unique to the club with lots of strategy and independence to make a difference at a company.</p><p><strong>Content: </strong>We have lots of new articles and content coming up so stay tuned on our Medium and LinkedIn pages!</p><h3><strong>Collectively Building the Future of MProduct</strong></h3><p>This past semester, MProduct has continued to make amazing progress throughout all its teams, despite many challenges out of our control. All of our active members have received experiences that have made them better PMs and more familiar with the product field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WArayd-WfogFsSnnHYDhUA.png" /></figure><p>Our members stated that forming a friend group or network of product-minded people was one of their biggest hopes when joining the club, and aside from the future plans described above, we are creating a new team to organize social events. Further details will be announced to our members by the next semester. MProduct also has more recruiting support and resources coming soon.</p><p>Finally, in the future, MProduct aims to provide more opportunities for members to create teams and projects within the club. It’s great to already see our members being proactive and starting new projects to shape the club’s future, and we want all members to be empowered to do the same. The board has been working with the Ginsburg center to create the best community culture possible, and to create infrastructure that supports and empowers all of our current and future members to create change and new initiatives. If you ever have any ideas you’d like to share, please reach out to anyone on the board at <a href="/service/mailto:mproduct-contact@umich.edu">mproduct-contact@umich.edu</a> or on Slack. We can’t wait for the year ahead, and we’re glad to have you helping shape the future of MProduct!</p><p>As always, we are committed to creating the next generation of Product leaders. If you’re someone passionate about product management, we hope you will join our community. If you want to keep up with MProduct, follow us on <a href="https://medium.com/mproduct">Medium</a> and <a href="https://www.linkedin.com/company/mproduct">LinkedIn</a>, or check out our <a href="https://www.mproduct.org/">website</a>!</p><p>Go Blue!</p><p>MProduct Links:</p><p>Medium: <a href="https://medium.com/mproduct">https://medium.com/mproduct</a></p><p>LinkedIn: <a href="https://www.linkedin.com/company/mproduct">https://www.linkedin.com/company/mproduct</a></p><p>Website: <a href="https://www.mproduct.org/">https://www.mproduct.org/</a></p><p>This article was written by Rohan Prashant and Jeremy Segal, with help from Austin Haag and all the MProduct PMs</p><p>Rohan is a junior at the University of Michigan College of Engineering studying Computer Science with a possible minor in Entrepreneurship.He enjoys all racquet sports, cars, gadgets, weightlifting, podcasts, Rocket League, and reading.</p><p>Jeremy is a rising junior at the University of Michigan studying Industrial and Operations Engineering with an International Minor.He enjoys skiing, hiking, and everything outdoors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e08838d4dd70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mproduct/mproduct-club-update-one-year-later-e08838d4dd70">MProduct Club Update: One Year Later</a> was originally published in <a href="https://medium.com/mproduct">MProduct</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MProduct <Education>: Product Design Principles]]></title>
            <link>https://medium.com/mproduct/mproduct-education-product-design-principles-1a2f778a7a4f?source=rss-a7b3debc8503------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a2f778a7a4f</guid>
            <dc:creator><![CDATA[Jeremy Segal]]></dc:creator>
            <pubDate>Thu, 21 May 2020 19:36:13 GMT</pubDate>
            <atom:updated>2020-05-21T19:36:13.108Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to MProduct Education. The primary function of this series is to consistently provide product managers (PMs) with valuable tools, frameworks, and resources. Whether you have just learned the operating functions of a PM or are well into your career within the realm of product, our educational content will always be created for those hungry to become a better PM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*swf6jn_LHvSN2Rd-" /></figure><p><strong>Why do design principles matter for PMs?</strong></p><p>Almost every tech company has product design principles or guidelines to help guide the course of their products. As a PM, you want to make sure your team focuses on a shared vision to bring forth a product that serves your consumers and aligns with your company’s mission. In this article, we’ll talk about how to make these effective design principles. Design principles commonly refer to visual design. However, today we will be discussing product design principles.</p><p><strong>What are product design principles?</strong></p><p>First off, these guidelines need to accomplish a few things. This includes reflecting on the state of the product and defining a future vision. It is important to see how a product has developed from your set of principles. Then use these principles to steer it into the future. This should also mean focusing the team on a common vision so that everyone understands the direction and desired outcome from a project. A PM will often work with a team of developers, engineers, data scientists, as well as management. These many roles bring differing perspectives on development, so design principles should help align your team around shared a goal and idea for the final concept. Everyone not only needs to know the purpose of the product, but also the need it is filling.</p><p>Product principles can be applied to creating standards used for evaluating new and existing features, and for guiding tradeoff decisions. With every project, there are constraints of time, money, people and technology that have to be addressed. Having clear design principles from the start allows a PM to answer the question of what is more important to the consumer, and therefore the company.</p><p>A more well-known set of design principles are Apple’s “Human Interface Guidelines” for each of their technologies. One example from iOS is <strong>User Control</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/315/0*mhy_B-WmtnrbVLnj" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/0*KAxFqyG0qpve-arq" /></figure><p>These guidelines can easily be seen in their Photos app. For example, if I go to edit a photo, I have the ability to edit a photo however I feel fit. However, Apple allows me to revert to the original image even after I implement the changes. Additionally when I delete an image, it’s not permanently gone. First, the app will show a message asking me to confirm my action. Then, once “deleted”, the photo will still be in my trash folder for another 30 days before it is permanently deleted. So if my action is ever a mistake, the app allows me to avoid unwanted outcomes.</p><p><strong>What are effective design principles?</strong></p><p>Now that you have an overview of what design principles are and why they are important, let’s move on to defining qualities of successful ones.</p><p><strong>Effective design principles should be:</strong></p><ul><li><strong>Broad enough to apply universally to our product</strong></li><li><strong>Specific enough to help us make decisions</strong></li><li><strong>Focused on a consistent vision</strong></li><li><strong>Able to inspire us to create better outcomes</strong></li><li><strong>Simple and memorable</strong></li></ul><p>From the Apple example, it is clear their principles are broad enough to apply to all of their iOS products and this characteristic is true for any organization. Because these principles are specific for each product or company, they should help us remain focused on a consistent vision of what makes our product experience valuable or unique.</p><p>On this very website, Medium’s principles guide their decisions to make a valuable experience for us as content creators and readers. One such example is “Appropriate over Consistent”. On either the website or app, Medium will give you the information in the header relevant to what you are reading. If you access the article through their business page, Medium will have a “Medium Business” header. Instead if you access the article through a specific author or publication, the Medium header will include their information. This small feature isn’t that impactful overall but demonstrates Medium’s choice guided by their design principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_72RKRz1hJHIW-J7" /></figure><blockquote>Medium: “Appropriate over Consistent”</blockquote><p>Another quality listed is that they should inspire us to create better outcomes. No product is perfect or final, we can always improve to make a new or better version. And for all of these qualities to be effective, the principles need to be simple and memorable for your team so that they are remembered through the lifetime of creating a product.</p><p><strong>How to decide on design principles</strong></p><p>Because design principles are specific to you and need to guide your team, they should be based on your customer base, product, and team. This means looking at metrics of interest and asking “What metrics are we trying to improve via new product principles?” They should also start with the minimum viable product (MVP) with just core functions because these principles will drive iteration on your product in the future. Even though everything we do is for the customer, design principles should align with the brand as well as the core values you and your team believe in. You also need to decide how these values help and cater to the customer. Finally, take a step back and focus on what the product is really for — What is its utility? What is its purpose? What are its aesthetics? This decision making process should help guide the design principles for your product so that they are effective and useful for your team.</p><p><strong>Examples of design principles</strong></p><p>Another set of design principles from a product that many of us use are Android’s. Examples of these include “Make important things fast” and “Only show what I need when I need it”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2lMqjAyJeLg_cHiL" /></figure><p>In Google Drive, the first options on the left are creating a new doc or sheet, then what’s in your drive as well as shared and recent documents. These options allow users to go directly to what they want quickly. There is no need to sort through a whole list or click through too many pages. The second design principle I listed can also be seen in Google Drive. Under the “New” button, users can choose what type of document they’d like to create; a doc, sheets, slides, file upload, etc. Instead of having every option listed on the homepage, users get to choose what to show when they need to create a new document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/0*GCmbjX-b0JDaHJA9" /></figure><p>Below we listed more examples of design principles as well as the ones used in this article:</p><p>Apple: <a href="https://developer.apple.com/design/human-interface-guidelines/">https://developer.apple.com/design/human-interface-guidelines/</a></p><p>Medium: <a href="https://medium.com/@dustin/thanks-for-writing-the-article-julie-8362fd235ae0">https://medium.com/@dustin/thanks-for-writing-the-article-julie-8362fd235ae0</a></p><p>Airbnb: <a href="https://airbnb.design/building-a-visual-language/">https://airbnb.design/building-a-visual-language/</a></p><p>Android: <a href="https://www.designprinciplesftw.com/collections/android-design-principles">https://www.designprinciplesftw.com/collections/android-design-principles</a></p><p>Google: <a href="https://material.io/design">https://material.io/design</a></p><p>As always, we are committed to creating the next generation of product leaders. If you’re someone passionate about product management, we hope you will join our community. If you want to keep up with MProduct, follow us on <a href="https://medium.com/mproduct">Medium</a> and <a href="https://www.linkedin.com/company/mproduct">LinkedIn</a>, or check out our <a href="https://www.mproduct.org/">website</a>!</p><p>Go Blue!</p><p><strong>MProduct Links:</strong></p><p>Medium: <a href="https://medium.com/mproduct">https://medium.com/mproduct</a></p><p>LinkedIn: <a href="https://www.linkedin.com/company/mproduct">https://www.linkedin.com/company/mproduct</a></p><p>Website: <a href="https://www.mproduct.org/">https://www.mproduct.org/</a></p><p><strong>Sources Used In Article</strong></p><ul><li><a href="https://medium.muz.li/design-principles-behind-great-products-6ef13cd74ccf">https://medium.muz.li/design-principles-behind-great-products-6ef13cd74ccf</a></li><li><a href="https://www.designprinciplesftw.com/">https://www.designprinciplesftw.com/</a></li><li><a href="https://www.cultofmac.com/486340/apple-design-principles-sketchnotes/">https://www.cultofmac.com/486340/apple-design-principles-sketchnotes/</a></li></ul><p>Written by Jeremy Segal, with help from Austin Haag, Rohan Prashant, Stephanie Shoo, and Atharva Talpade.</p><p>Jeremy is a rising junior at the University of Michigan studying Industrial and Operations Engineering with an International Minor.</p><p>He enjoys skiing, hiking, and everything outdoors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a2f778a7a4f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mproduct/mproduct-education-product-design-principles-1a2f778a7a4f">MProduct &lt;Education&gt;: Product Design Principles</a> was originally published in <a href="https://medium.com/mproduct">MProduct</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MProduct <Spotlight>: Philip Ruffini, Program Manager on Microsoft’s Cloud and AI Team]]></title>
            <link>https://medium.com/mproduct/mproduct-spotlight-philip-ruffini-program-manager-on-microsofts-cloud-and-ai-team-5ff2895d5d55?source=rss-a7b3debc8503------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ff2895d5d55</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Jeremy Segal]]></dc:creator>
            <pubDate>Thu, 23 Apr 2020 14:35:53 GMT</pubDate>
            <atom:updated>2020-04-23T14:35:53.813Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey MProduct Community!</p><p>In December, we got a chance to sit down with Philip Ruffini, a program manager at Microsoft (program manager is Microsoft’s version of a product manager). We’d like to share a few things he had to say about his PM experience and his advice to become a great PM.</p><p><strong>Philip’s Background</strong></p><p>Philip Ruffini graduated from the University of Michigan in 2019 with a Bachelor’s in Business Administration and a minor in Computer Science. During his time at Michigan, he interned at a startup called Juicero and at Anheuser Busch’s venture capital arm, ZX Ventures. He also started his own profitable office product company with yearly revenue in the mid-six figures before selling the business. Philip currently works at Microsoft and recently founded an online PM course, HackingPM. His team at Microsoft mainly contributes to their Azure and AI software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L9gL_AmyRfKZ6f8a" /></figure><p><strong>Getting a job or internship in Product Management</strong></p><p>For some, there is a very defined path to enter a PM career: major in CS, earn a soft skill minor such as in business, and TA for a technical CS class. Land a software internship followed by a PM internship, and finally, earn a full-time offer.</p><p>Philip, however, does not have a degree in computer science and pursued experiences he would enjoy that would also build skills for a PM job. “The most important skills to develop are how to lead a team, working with people from different backgrounds, launching a product and dealing with ambiguity in your role.” Many tech companies will recruit computer science majors, but Philip says that it is more important to show that you can communicate with the engineers and understand what they’re doing.</p><blockquote>“The most important skills to develop are how to lead a team, working with people from different backgrounds, launching a product and dealing with ambiguity in your role.”</blockquote><p>One skill he suggests working on (and one he wished he had when starting at Microsoft) is being able to ask intelligent questions instead of basic ones. This allows for better communication with colleagues in technical and engineering roles.</p><blockquote>Basic Question: “How does this code work for our project?”</blockquote><blockquote>Insightful Question: “How can we make the interface of our product more efficient and helpful for the user?”</blockquote><p>He also suggests aligning college experiences around one central goal. For Philip, it was landing a job in product management. One of the main reasons for this is to show employers’ your passion and breadth for a certain area of expertise. Many recruiters will state they want to see students who are passionate and focused in what they are involved in. At Michigan, Philip was mainly involved with his company, as well as the University of Michigan consulting club, 180 Degrees Consulting. Philip also got the chance to take an independent study through Ross to learn how to expand his start-up. These experiences all developed his skills as a PM as discussed above.</p><p><strong>Going from “zero to one” on a project</strong></p><p>One of the hardest things to do in college is finding time between classes, clubs and social life to launch a product or tackle a side project. Most of the heavy lifting comes when first getting your idea off the ground: going from “zero to one.” Philip said this experience is extremely valuable because you will learn different skills and lessons every time you start something new. It is something that will differentiate you from others in interviews, and so much learning happens just from quick rounds of trial and error.</p><p>One example of a project Philip started is his e-commerce service, First Rate Suppliers, which imported office products. He says he was able to do this because it was a realistic idea, and ended up becoming a very successful business. During his freshman year, he and his friends also attempted to found a start-up that required partnering with nursing homes and being aware of medical information that was out of scope for Philip and his friends. This idea failed because it wasn’t within his constraints to start a company in a field they had no expertise in. Philip took this failure with a positive attitude and was sure to simplify his later ideas to an MVP he was sure he could get off the ground.</p><blockquote>“Everyone knows that failing is learning, but few actually execute and actually try building something.”</blockquote><p>Philip recommends learning what other people have done that has led to success and copying these skills to your project. He also says it is helpful to write down the small steps that lead to an ultimate goal. A great way to break down your project into achievable steps is by using “SMART” goals. These are specific, measurable, achievable, relevant, and time-bound (S.M.A.R.T.). For a product, Philip said these steps could look like: what’s the solution, what’s the easiest way to test it, how do I gauge interest, and how do I get it made?</p><blockquote>“It’s all about coming up with an idea and trying something.”</blockquote><p>Another suggestion from Philip is no matter what that goal is, keep practicing going from “zero to one”, and be sure to spend time reflecting and learning from the inevitable little successes and mistakes along the way.</p><p><strong>What is </strong><a href="https://hackingpm.com/"><strong>HackingPM</strong></a><strong>?</strong></p><p>Philip’s newest side venture is an online course that helps students earn PM offers, from the first steps one can take during their freshman year to negotiating full-time job offers. His service provides coaching, lessons and full interview preparation. The first three lessons are available for free! The website also has additional free resources such as resume templates and interview recordings. HackingPM is a great resource for students interested in recruiting for PM, and it has also helped Philip refine his skills in product. It is only one of his many examples of taking an idea from zero to one, and we are sure he is taking notes of his learnings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SJNx3d7uSdmX2bqe" /></figure><p><strong>One Last Question: What skills were directly transferable from University of Michigan to Microsoft?</strong></p><p>In college, Philip would reserve a private room in the business school or the undergraduate library to work out problems and plans on a whiteboard. He would use this before starting a product or before taking on a new client for 180 Degrees Consulting and plan out the next three months. Before he starts a new project at Microsoft, Philip will do the same thing to plan out the entire process. This has been very helpful for him to see each step and visualize the project.</p><p>As always, we are committed to creating the next generation of Product leaders. If you’re someone passionate about product management, we hope you will join our community. If you want to keep up with MProduct, follow us on <a href="https://medium.com/mproduct">Medium</a> and <a href="https://www.linkedin.com/company/mproduct">LinkedIn</a>, or check out <a href="https://www.mproduct.org/">our website</a>!</p><p>Go Blue!</p><p>MProduct Links:</p><p>Medium: <a href="https://medium.com/mproduct">https://medium.com/mproduct</a></p><p>LinkedIn: <a href="https://www.linkedin.com/company/mproduct">https://www.linkedin.com/company/mproduct</a></p><p>Website: <a href="https://www.mproduct.org/">https://www.mproduct.org/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ff2895d5d55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mproduct/mproduct-spotlight-philip-ruffini-program-manager-on-microsofts-cloud-and-ai-team-5ff2895d5d55">MProduct &lt;Spotlight&gt;: Philip Ruffini, Program Manager on Microsoft’s Cloud and AI Team</a> was originally published in <a href="https://medium.com/mproduct">MProduct</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>