<?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 Joanna Beltowska on Medium]]></title>
        <description><![CDATA[Stories by Joanna Beltowska on Medium]]></description>
        <link>https://medium.com/@jbeltowska?source=rss-dbc1d16a19f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*U1-FnlxG2KQMWOBO.png</url>
            <title>Stories by Joanna Beltowska on Medium</title>
            <link>https://medium.com/@jbeltowska?source=rss-dbc1d16a19f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:10:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jbeltowska/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[8 Ways to Accelerate Your Product Manager Growth]]></title>
            <link>https://medium.com/@jbeltowska/8-ways-to-accelerate-your-product-manager-growth-db05ac0ccf23?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/db05ac0ccf23</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[professional-development]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 21:00:14 GMT</pubDate>
            <atom:updated>2017-12-13T02:41:18.739Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmS0rK-0EtZTTqAOoO8wtQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/ziwuqMZNRvs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Bench Accounting</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote><strong>To be successful as a product manager, you need to develop strong ownership not just of the product you work on but also of your own professional growth.</strong></blockquote><p><strong>Product management is hard. </strong>It’s a discipline that is deep as well as broad. No matter how senior you are, there are always new things to learn.</p><p><strong>Product management is still a relatively nascent discipline. </strong>The way the role is defined and evaluated can vary tremendously between companies and even between teams within the same company. Experience gained in one context may not readily translate to another.</p><p><strong>The PM role is inherently a leadership role; the expectations placed upon you are high and typically, you’re the only PM on your team.</strong> You may not get many opportunities to interact with other PMs to learn how others approach the role and its challenges. If you’re at a company that is just beginning to establish a product organization, you may even be the only person in a product role. In other words, you’re often on your own to figure things out.</p><p><strong>Software and hardware are constantly changing.</strong> The way we think about, use and rely on technology does as well. The landscape that a PM needs to understand and navigate is always evolving.</p><p>Lastly, <strong>product management is highly competitive.</strong> Every time you decide to go for a promotion or interview for a new job, you’re going to be up against lots of smart, ambitious, and talented people with interesting and valuable experiences.</p><blockquote><strong>If you’re not actively honing your craft, you’re falling behind.</strong></blockquote><p>One way I’ve found to navigate this is to seek out others’ experiences. While I’m convinced that the best way to learn is by doing the work and reflecting on it, I believe the second best way to learn is by studying others.</p><p>One of my favorite things about being in product is the community. It’s big, vibrant and generous.</p><p>Whenever I’ve found myself stuck, wanting inspiration, or looking for new ideas I’ve turned to the product community. I’ve built this into my routines. I read books, blog posts and articles on my commute. I listen to podcasts when I work out. I keep a list of interesting tools, frameworks, case studies, examples and stories that I return to whenever I’m looking for something specific (like how others use roadmaps for long term planning). I’ve subscribed to newsletters and digests to regularly get interesting content pushed to me.</p><p>These habits have helped me get unblocked numerous times, enabled me to better understand my craft and how I want to grow as a product manager and leader, and analyze gaps in my skills and knowledge and seize opportunities to narrow them. I’ve been able to expand my toolkit of concepts, frameworks and tactics much more rapidly than if I’d relied on personal experience alone. As I’ve built up this mental map of helpful resources and how to leverage them, my confidence in my ability to solve tricky problems and maneuver difficult situations has grown by leaps and bounds. Perhaps most importantly, I’ve become a better critic of my own ideas and work because tapping into how others think has expanded my own thinking.</p><p>I’ve compiled my favorite avenues for learning about product management below. I’d love to hear about yours, and the habits you’ve built up around them. Leave a response or a comment so we can compare notes!</p><p>(As a side note: to learn efficiently, you should also have clear goals in mind for your learning. Ellen Chisa has written a <a href="https://blog.ellenchisa.com/learning-in-product-6cb06292a98c">great piece</a> about how to do just that.)</p><h3>Mentors</h3><p>This is perhaps the first thing people think of when they think of how to grow in their careers. Mentorship is a big topic that has been <a href="https://www.thisisproductmanagement.com/episodes/mentorship/">addressed</a> <a href="https://www.quora.com/How-do-I-find-product-manager-mentors/answer/Vince-Law?share=2fc3c209">well</a> by <a href="https://medium.com/emerging-tech-insights/hacking-your-product-management-career-cce227a9c39a">others</a> so I won’t say more about it here aside from this: mentorship doesn’t need to be a big, official thing. It can simply be semi-regularly grabbing coffee or a bite to eat with someone whose perspective you value or whose career trajectory you admire.</p><h3>Books</h3><p>Reading books is perhaps the second thing people think of when it comes to learning. Many much better read people than myself have compiled lists of book recommendations for PMs. Two excellent starting points, with some overlaps, are</p><ul><li>Noah Weiss’ <a href="https://medium.com/@noah_weiss/50-articles-and-books-that-will-make-you-a-great-product-manager-aad5babee2f7">77 articles and books that will make you a great product manager</a> and</li><li>Ken Norton’s <a href="https://www.kennorton.com/essays/books-for-product-managers.html">Books for Product Managers</a></li></ul><h3>Meetups and conferences</h3><p>This is yet another avenue for learning that I suspect most PMs are familiar with, but perhaps not all PMs have explored.</p><p>Meetups are a wonderful way of getting involved with your local product community and learning about local product companies. The best way to find the good meetups is to explore meetup.com or to ask others (perhaps using some of the forums I’ve listed below).</p><p>Conferences are a wonderful way of meeting people from other cities and countries, and learning about the latest trends and case studies. If you have a professional development budget through work, definitely see if it covers all or some of a conference trip. I can highly recommend <a href="https://www.mindtheproduct.com/2017/09/mind-product-conferences-2018/"><strong>Mind The Product</strong></a> and <a href="https://leanstartup.co/"><strong>Lean Startup</strong></a>, both leading product conferences that happen several times a year in a few different locations. For a more comprehensive list of product conferences, check out <a href="https://www.producttalk.org/2017/04/2017-product-conferences/">this blog post</a> (scroll to the bottom for 2018 dates and locations).</p><h3>Slack and Facebook groups</h3><p>I’ve found Slack and Facebook groups to be one of the best ways to connect and interact with other product people. To join a group, you typically have to request to be invited and answer a few questions about yourself.</p><p><a href="https://medium.com/@merci/a-year-of-women-in-product-2f7ff56c5846"><strong>Women in Product</strong></a>, founded by Merci Victoria Grace, former Director of Product @SlackHQ, is specifically for – you guessed it – women in product roles. The group currently has close to 3,000 members. Apply to join the Slack group <a href="https://docs.google.com/forms/d/e/1FAIpQLSeY71YlA1HzQchNgwLo7WHgRmEqiyiaREiR9EDLhQx72bQogw/viewform">here</a>. This is my personal favorite and a group I spend time on daily.</p><p><a href="http://www.womenpm.org/"><strong>Women in Product</strong></a>, a non-profit founded by a group of women product leaders at Facebook, has a <a href="https://www.facebook.com/womeninproduct/">closed Facebook group</a> that I visit daily, too (yes, these are two different groups with the same name). This group has around 5,000 members.</p><p><a href="https://www.hiretechladies.com/join"><strong>Tech Ladies</strong></a> is another women-only community that I visit daily. They have a <a href="https://www.facebook.com/groups/techladies/">closed Facebook group</a> and a newsletter. Tech Ladies is for everyone who identifies as a woman or non-binary and works in tech, so the topics span more than just product.</p><p><a href="https://www.productschool.com/"><strong>Product School</strong></a> offers PM courses (in addition to a podcast and a blog) and has a <a href="https://www.productschool.com/slack-community/">Slack group</a> with 17,000+ members. Their Slack group regularly hosts AMAs with PMs and PM leaders.</p><p><a href="https://www.mindtheproduct.com/"><strong>Mind The Product</strong></a> is one of the biggest communities and conferences for product people. Their <a href="http://mindtheproduct.slack.com/">Slack group</a> is currently 11,000+ members strong.</p><p>Pivotal Labs (where I work) uses Slack to help people connect across offices. It’s become an effective tool for us to learn from one another asynchronously and across time zones. If you have PM colleagues inside your organization that you wish you could interact more with, try setting up an internal Slack group.</p><h3>Podcasts</h3><p>I love podcasts. I find them to be the most convenient way of learning new things because I can do something else, like go for a run or cook dinner, while listening to an episode. They’re are a great way to learn about other PMs’ careers, specific companies product cultures and to go deep on specific topics. Below are the podcasts I find myself returning to regularly.</p><ul><li><a href="https://www.google.com/search?q=inside+intercom+podcast&amp;oq=inside+intercom+podcast&amp;aqs=chrome..69i57j0l5.3328j0j7&amp;sourceid=chrome&amp;ie=UTF-8"><strong>Inside Intercom</strong></a></li><li><a href="https://itunes.apple.com/us/podcast/how-i-built-this-with-guy-raz/id1150510297?mt=2"><strong>How I Built This</strong></a></li><li><a href="https://itunes.apple.com/us/podcast/masters-of-scale-with-reid-hoffman/id1227971746?mt=2"><strong>Masters of Scale</strong></a></li><li><a href="https://itunes.apple.com/us/podcast/the-product-podcast/id1219400787?mt=2"><strong>The Product Podcast</strong></a></li><li><a href="https://itunes.apple.com/us/podcast/this-is-product-management/id975284403?mt=2"><strong>This is Product Management</strong></a></li></ul><h3>Product leaders</h3><p>Below are some of my favorite product leaders who frequently share their experiences, thoughts and insights in writing, and also curate content from the broader product and tech community.</p><p>I’ve linked their blogs; make sure to also follow them on Twitter and LinkedIn if you use either platform habitually.</p><ul><li><a href="https://medium.com/@melissaperri"><strong>Melissa Perri</strong></a></li><li><a href="https://www.producttalk.org/"><strong>Teresa Torres</strong></a></li><li><a href="https://medium.com/@ellenchisa"><strong>Ellen Chisa</strong></a></li><li><a href="https://www.kennorton.com/"><strong>Ken Norton</strong></a></li><li><a href="https://svpg.com/articles/"><strong>Marty Cagan</strong></a></li><li><a href="https://medium.com/@gibsonbiddle"><strong>Gibson Biddle</strong></a></li><li><a href="https://medium.com/@johnpcutler"><strong>John Cutler</strong></a></li><li><a href="https://medium.com/@joshelman"><strong>Josh Elman</strong></a></li><li><a href="http://www.romanpichler.com/blog/"><strong>Roman Pichler</strong></a></li><li><a href="https://medium.com/@nireyal"><strong>Nir Eyal</strong></a></li><li><a href="https://medium.com/@BrandonMChu"><strong>Brandon Chu</strong></a></li></ul><h3>Medium publications</h3><p>As you probably know since you’re reading this on Medium, Medium is another excellent way to discover great content. In addition to following some of my favorite product influencers on Medium, I also follow a number of publications and am subscribed to topics that interest me like Technology, Work and Psychology. I use the Medium Digest feature to receive recommended reads via email.</p><p>Some of my favorite publications are:</p><ul><li><a href="https://medium.com/pminsider"><strong>PM Insider</strong></a></li><li><a href="https://productcoalition.com/"><strong>Product Coalition</strong></a></li><li><a href="https://uxdesign.cc/"><strong>uxdesign.cc</strong></a></li><li><a href="https://hackernoon.com/"><strong>Hacker Noon</strong></a><strong> </strong>(this is technically a publication about technology, not just product, but I’ve found its content to be interesting often enough to include it here)</li></ul><h3>Newsletters</h3><p>Newsletters are lovely. They regularly show up in your inbox with advice and carefully curated lists of articles, upcoming events and job openings, and you don’t have to do anything other than read what you like.</p><p>My personal favorites include:</p><ul><li>Ken Norton’s “<a href="https://www.kennorton.com/newsletter/"><strong>Bringing the Donuts Newsletter</strong></a>”</li><li>Mind the Product’s “<a href="https://www.mindtheproduct.com/product-management-newsletter/"><strong>Prioritised: The Product Management Newsletter</strong></a>”</li><li>Intercom’s “<a href="https://blog.intercom.com/"><strong>Inside Intercom</strong></a>”</li><li>Nir Eyal’s “<a href="http://productpsychology.com/"><strong>Product Psychology</strong></a>”</li><li>First Round’s “<a href="http://firstround.com/review/"><strong>The Review</strong></a>”</li><li>Women in Product’s “<a href="http://www.womenpm.org/join/"><strong>Weekly PM jobs and events</strong></a>”</li></ul><h3>Anything missing?</h3><p>Leave a comment or response if you know of any other awesome learning resources for PMs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gtulLxsOXeIz-RtFJ32P5g.png" /></figure><p><strong>This story is published in </strong><a href="http://blog.usejournal.com/"><strong>Noteworthy</strong></a><strong>, where 10,000+ readers come every day to learn about the people &amp; ideas shaping the products we love.</strong></p><p><a href="http://blog.usejournal.com/"><strong>Follow our publication</strong></a><strong> to see more product &amp; design stories featured by the </strong><a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post&amp;utm_content=joanna_beltowska"><strong>Journal</strong></a><strong> team.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wuw1kCUUftwOONwl6PjdjQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db05ac0ccf23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A(nother) Day in the Life of a Product Manager at Pivotal Labs]]></title>
            <link>https://medium.com/built-to-adapt/a-nother-day-in-the-life-of-a-product-manager-at-pivotal-labs-2da29c342ce8?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2da29c342ce8</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[working-at-pivotal-labs]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Thu, 01 Dec 2016 18:15:17 GMT</pubDate>
            <atom:updated>2017-12-13T20:19:50.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VPVjxwjTi3OZLYbqiMF7Kg.jpeg" /><figcaption>Caroline Hane-Weijman is a Product Manager at Pivotal Labs, New York.</figcaption></figure><h2>Caroline Hane-Weijman</h2><blockquote>PRODUCT MANAGER, PIVOTAL LABS, NEW YORK</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*YjbmsJ_-GKsYS9XGUCnFcA.jpeg" /></figure><p><strong><em>I found Pivotal Labs…</em></strong><em> </em>through a friend of a Product Manager who worked at Pivotal Labs. I had breakfast with her at the office and got to experience our morning, office-wide standup. I remember I immediately sent my friend a text message saying I wanted to work here! It seemed like an awesome culture.</p><p><strong><em>I decided to join Pivotal Labs because… </em></strong>the collaborative and flat culture I saw really appealed to me. And when I asked around, everyone thought of Pivotal Labs as a leader in agile software development and product management practices and pointed out how much I’d be able to learn. Pivotal Labs has so much accumulated knowledge, great practices and knows how to create talented, agile product teams. I was also excited to be able to work on different types of products. In my previous role I wouldn’t had been able to work on web and mobile, because those were different parts of our organization. Here, I can do that.</p><p><strong><em>I am currently working on…</em></strong> a subscription payment platform.</p><h3>9 am: Morning Stand Ups</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VbnOpXsxYxyYQFTtdV5axw.jpeg" /></figure><p>My day starts with breakfast in the office with other Pivots and clients, and then office standup. Office standup is always right after 9 am. It’s very invigorating and a great way to start the day. It reminds you that you’re part of a community.</p><p>My team’s daily stand up is at 9.15. Our team consists of 9 members: me, a client product manager, a Pivotal designer, two Pivotal engineers and four client engineers.</p><p>Our client is a payments provider. We are helping evolve their existing subscription payments platform. The current solution is fragmented across multiple systems. We are designing and building a new system that will integrate into an existing ecosystem to leverage existing functionality while enabling customers to access one unified system for their solutions.</p><p>We are currently in the midst of Discovery and Framing. It’s a process that helps us get to a shared understanding of what we’re building, for who and why. We start by understanding what unaddressed or underserved problems or desires our customers have, before we start to think about what solutions we could build.</p><p>One of the most important things we do this stage is identify and test our most risky assumptions about the users, the feature set, the technology and the business model — assumptions that, if we get them wrong, might put the entire project at risk. This helps us gain confidence in what we plan to build first so that we don’t waste design and development cycles building features that no one will want to use. Sometimes we learn that we shouldn’t be building any software at all, and that’s a valuable outcome too. It means we’re not building software that shouldn’t be built.</p><h3>10 am: Planning for Product Inception</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ui7ewASGpp9wKntVNzwPw.jpeg" /></figure><p>Our team has put together a list of questions that we want to answer this week, before we incept. <a href="https://blog.pivotal.io/labs/labs/agile-inception_knowing-what-to-build-and-where-to-start">Inception</a> is our starting point for development. The product team and our stakeholders get together and define the initial backlog of development work together, based on what we have learned during the initial Discovery &amp; Framing and on what the project goals are.</p><p>If we answer these questions, we will have enough confidence in our feature ideas to feel comfortable committing them to code. For instance: How do we define success from a business perspective? What merchant segment is most accessible and valuable for the business? What are the highest value features for merchants? What does the competitive landscape look like? What does it mean for developers to have an easy to use API? Are there dependencies on other teams that we need to get ahead of? What’s the right tech stack for this app and team? Do we have documentation for all the integrations we expect?</p><p>I am going to collaborate with Francisco who is the designer on the team, and my client PM to do user research to help inform what features we should build and in what order. I will work closely with my client PM to make sure that we understand the business needs driving this initiative, to inform our strategy for the product.</p><p>Meanwhile, the engineers will work on drafting a very high level systems diagram so that we get ahead of reaching out to the client teams whose services we will depend on and systems we need access to. The systems diagram will also help us decide what tools we’ll need for development.</p><h3>11 am: Customer Interview Prep</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q_W56z33DSVyssBX6vXtWg.jpeg" /></figure><p>I’m collaborating with Francisco and our client PM on preparing today’s customer and stakeholder interviews. We have 5 interviews scheduled for today and 4 for tomorrow. By the end of this week, we will have done 14 interviews with a mix of merchants who are existing and prospective customers of our client, as well as internal client stakeholders from sales, account management, and solutions implementation teams.</p><p>This first round of user research will be focused on informing the feature set we should be building for our first release. We need to understand the needs of each customer segment as well as how important that customer segment is for our client’s business. We also need to understand the business’ capability of selling a solution to that customer segment. Even if we were to build a solution tomorrow for one of the customer segments, we wouldn’t necessarily be able to sell it. So, we need to define a very narrow focus for the first version of the platform we’re building, and make sure it’s a validated high value opportunity that can be realized by our client’s organization.</p><p>In the interviews, Francisco, the client PM, and I will take turns leading the interviews and taking notes. One of the engineers on the team will sit in so that they can see the process. It’s important that everyone on the team understands who we are designing the product for, and what those people want or need from it.</p><h3>12 pm: First Customer Interview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J0bVf5JFSbzaOJrIL-yoAg.jpeg" /></figure><p>We got some early signals from our first interview that several of our user assumptions are valid. We also learned some new and interesting things about how unaware customers might be of our client’s offering, and that they need more handholding during the sales process than what we have assumed.</p><p>If this feedback is consistent, an intuitive API won’t be enough. We’ll need to think about how to create an experience that helps the customer become aware of the full breadth of our client’s offering. In addition to the sales process, we will need to explore how documentation and a sandbox environment might impact the user experience. We also assumed that customers are familiar with certain concepts and naming conventions, because they are industry terms. Turns out they had no idea what these things mean.</p><p>Another interesting early observation is that customers don’t know their pain points if they haven’t experienced anything else than the platform they’re currently using. They haven’t vetted other solutions because they already have a great sales relationship with our client. They either consider building a solution themselves or going with our client’s solution. They haven’t considered the competition at all. So, we’re learning that our end users aren’t comparing us against other products; they don’t know what they don’t know.</p><h3>12.30 pm: Lunch</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YzavtVnqwe80rLXaw4LbgQ.jpeg" /></figure><p>Today is one of my favorite lunchtime activities — PM Article Time! <a href="https://medium.com/@jimthomson">Jim Thomson</a>, one of the PMs in the NY office, sends out two short articles or videos in advance that showcase product development practices at other companies or from different thought leaders in the industry. Pivots and clients across design, PM, and engineering then get together over lunch (usually sushi!) and discuss. These lunches have generated really interest conversations and ideas for how we can improve our practices. It is important that we learn from others and don’t become an echo chamber.</p><h3>1.30 pm: Second Customer Interview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ic8dgfXnlj6s58TrccF0Yg.jpeg" /></figure><p>We’re preparing for two interviews starting at 2pm. First, we’re talking to an internal stakeholder who heads up the IT solutions implementation team inside of our client’s organization. After that, we’re meeting with business line lead from one of our client’s customers.</p><h3>3.00 pm: PM Practice Time</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JzPI_vCv4l06WvxMKDKAeA.jpeg" /></figure><p>We’re taking a 30 minute break from interviews, so I’m working through a couple of tasks related to our Product Management practice in the NY office. We think a lot about continuous improvement when it comes to how we work. An important aspect of that is sharing our experiences with other PMs at Pivotal Labs and with the broader product community outside of our own company.</p><p>I recently attended a Women In Product meetup hosted by Capital One Labs, that I really enjoyed. Their head of design strategy had interesting experiences to share about iterating on their teams’ agile process. I am doing a quick writeup of my thoughts that I am sharing in our NY PM slack channel. I also take a few minutes to laugh at the daily gifs that are shared.</p><p>I’m also working with a designer in our office to set up a series of lunch talks about our Discovery and Framing practice. I’m writing a draft email to the PMs and designers in our office that I want to run by her before I send it out.</p><h3>4.00 pm: Interview Synthesis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XSuDQdEhsLijd59raFJXKw.jpeg" /></figure><p>We’ve completed four interviews and are summarizing what we’ve learned so far today.</p><p>It’s really important to remember to develop deep empathy for the user — to feel with them, rather than for them. We may think we know that features to build, but unless we spend time with the people we’re building for, to really understand what is important to them and what they’re trying to accomplish, we’re going to end up making a lot of risky guesses. That’s why it’s so important that we constantly test our ideas, and use data from research to inform our decisions. For example, our client had come in with the assumption that building this one particular feature was the most important thing for the team to do based on conversations with a large prospective client. After talking to the business line lead, we not only learned that this feature may not satisfy the needs of the customer but that the sales process was in early stages and discussions regarding detailed features would not be had for another 4–6 months. We can build other features that could capture smaller merchants in a shorter time frame.</p><p>However, at the end of the day, our team doesn’t set the strategy for this product. This is one of many solutions that our client offers in their portfolio and there are many pieces that need to fit together in order for the client to move towards a high-level strategy for their business. It crosses product, engineering, DevOps, sales, customer support, etc. We need consider all perspectives as we make recommendations for and decide on product priorities.</p><h3>5.00 pm: Team Sync</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T9Evb3El9YwR27S323dUBA.jpeg" /></figure><p>We’re all getting together to sync up on what we’ve done today. We’re also going to do a quick retrospective of the day and do a recap of the two different tracks of work; the user interviews and the engineering working sessions.</p><p>While Francisco, the client PM, and I have been talking to users, the engineers have been doing high level systems design. They’ve focused on the scheduling system in particular as we will need it to support a specific feature we know we need to build. They’ve also worked on getting our development tools and environments set up with pairing stations, CI/CD and github.</p><h3>6.00 pm: Time To Go Home!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4i2XZG0_2YCqnFczFhKumQ.jpeg" /></figure><p>I just finished writing a email for our stakeholders to keep them up to date on our progress.</p><p>The first thing we’ll do tomorrow is to continue synthesis from our user interviews and map what we’ve learned to the different customer segments to see if there are any commonalities in terms of user needs. This will also help inform any changes we want to make to our questions for our interviews tomorrow. We want to get to a clearly prioritized and validated feature list this week, so that we can review the features with our key stakeholders before we incept next week.</p><p>But that’s for tomorrow. It’s 6 pm and time to go home and cook something fun!</p><p><a href="http://www.pivotallabs.com/"><strong>Pivotal Labs</strong></a><strong> </strong><em>is an lean + agile software consultancy. We collaboratively build and design mobile and web apps for the world’s largest brands.</em></p><p><em>If you’d like to learn more, please visit our </em><a href="http://pivotal.io/careers"><strong>careers page.</strong></a></p><p><em>This profile of Caroline Hane-Weijman was written by </em><a href="http://twitter.com/jbeltowska">Joanna Beltowska</a><strong>.</strong></p><p>Other parts in this series:</p><ul><li><a href="https://medium.com/product-labs/a-day-in-the-life-of-a-product-manager-at-pivotal-labs-ead9149af629#.32cgl9s2o">A Day in the Life of a Product Manager at Pivotal Labs</a></li><li><a href="https://medium.com/product-labs/a-day-in-the-life-of-a-pivotal-labs-engineer-49749e587165#.s65p7jtdn">A Day In The Life of an Engineer at Pivotal Labs</a></li><li><a href="https://medium.com/product-labs/a-day-in-the-life-of-a-product-designer-at-pivotal-labs-9b3ee049a0c6#.scc4nl3qy">A Day In The Life of a Product Designer at Pivotal Labs</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/72/1*iEKCWRbNP-1ba9QuxporEA.jpeg" /></figure><p><em>Follow us on </em><a href="http://www.twitter.com/pivotallabs"><em>Twitter</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/203/1*CiZ1ufd9WswfXL9JVmHKpg.jpeg" /></figure><p><em>Visit our </em><a href="https://pivotal.io/careers"><em>careers page</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2da29c342ce8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/a-nother-day-in-the-life-of-a-product-manager-at-pivotal-labs-2da29c342ce8">A(nother) Day in the Life of a Product Manager at Pivotal Labs</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Steps to Landing any Product Manager Interview]]></title>
            <link>https://medium.com/built-to-adapt/3-steps-to-landing-any-product-manager-interview-a60c3f54f7b7?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a60c3f54f7b7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Wed, 14 Oct 2015 00:22:38 GMT</pubDate>
            <atom:updated>2017-12-13T20:17:17.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kJ-k_bvnO1BxtO5We9UMeQ.jpeg" /></figure><p>In my role as hiring manager for Product Management at Pivotal Labs NYC, I’ve been at the receiving end of hundreds of resumes.</p><p><a href="https://medium.com/who-what-why/why-i-didn-t-look-at-your-resume-2a8ed1f4a5bb">Mikael Cho’s post about resume red flags</a> resonates with me.</p><p>I too am eagerly looking for the next candidate who will join our team. I too get excited each time a new application pops up in my inbox — and I too am frustrated by how many of these applications end up going in the “no” pile.</p><p>It’s easy to spot a great application. However, a typical application takes me around 15 minutes to review as I try to decipher the resume and hunt down the candidate’s LinkedIn, Twitter, personal blog and portfolio, trying to work out whether they do indeed have what we’re looking for but just aren’t presenting it well in their application.</p><p>This — the time I invest in each application — is an exception. In most cases, you have <a href="http://cdn.theladders.net/static/images/basicSite/pdfs/TheLadders-EyeTracking-StudyC2.pdf">seconds</a> to make an impression in the hiring manager’s inbox.</p><p>Think of it this way:</p><blockquote>You are the product and your resume is the elevator pitch.</blockquote><p>An elevator pitch is a short and succinct summary of what you have to offer — just like a resume.</p><p>Thus, in addition to Mikael’s advice on the basics of what NOT to do, I would like to offer up the following guidance on how to craft a strong Product Manager application.</p><h3>1. Demonstrate how you match my company’s flavor of Product Manager.</h3><h4><em>Or: Tailor your elevator pitch for your intended market.</em></h4><p>Product Manager roles vary quite a bit across product organizations based on what products the PM is expected to work on, what product teams look like and what the culture in which product teams operate is like. (PM roles can even vary substantially <em>within</em> the same organization.)</p><p>At <a href="http://pivotal.io/labs">Pivotal Labs</a>, the lean and agile values and principles we practice shape our PM role:</p><ul><li>Our teams are small, cross-functional and co-located which means that PMs collaborate directly and continuously with engineers and designers.</li><li>We de-risk product ideas through user research and usability testing so that when we to commit our ideas to code we are confident that they are the <em>right solutions</em> solving for the <em>right problems</em>.</li><li>We define development work from the user’s perspective by writing and prioritizing user stories in a backlog. We measure progress in user value delivered.</li><li>We estimate upcoming development work weekly, and we continuously update the backlog (daily) to reflect our current priorities.</li><li>We release early and often and use working software — not decks or prototypes or demos — as our ultimate measure of success.</li></ul><p>Pivotal Labs is a consultancy. For our Product Managers, this means that we don’t own the products we work on and that we typically work on a couple to a handful of products each year. Our mission is to <strong><em>transform the way the world builds software</em></strong>. We do this by working side by side with our client teams, in our offices, helping them define and launch successful digital products — and by doing so, helping them build successful product teams who can go back to their own organization and continue to effectively deliver customer value through software. Thus, our Product Managers, in addition to being capable product people, must also be skilled coaches and advisors, consensus builders and communicators, and have the ability to build strong and effective relationships with the client PMs they partner with.</p><p>A candidate who can’t demonstrate in their application that they have enough experience in these areas — defining, de-risking and shipping successful software products, consulting, working in small, cross-functional, autonomous and iterative teams — simply won’t be successful in the role and will go into my “no” pile.</p><p>The cultural stuff, albeit fuzzy, is equally important.</p><p>Pivotal Labs’ values are <strong>“Be kind, Do what’s right, Do what works, Keep it simple”</strong>. While I look primarily for the right level and mix of skills and experiences in an application, I also look for early signs of cultural fit (and no, this has nothing to do with how good you are at playing ping pong).</p><p>We believe that empathy is a tremendously important trait (“Be kind”) and only hire highly empathetic individuals. Empathy makes us better team mates and consultants, helps us design great products, and enables us to productively work through challenging situations. A candidate who cannot demonstrate empathy or how they’ve been successful in situations where empathy was needed won’t be happy or do well on our team. For instance, peppering your application with acronyms that the person at the receiving end may or may not be familiar with is not very empathetic.</p><h3>2. Tell me what you’ve accomplished, not what you’ve been responsible for.</h3><h4>Or: Instead of listing all its features, explain what value your product offers.</h4><p>A strong Product Manager delivers concrete and valuable results. She knows exactly what problem(s) her product solves for, for whom and how, can explain in simple terms what success looks like, how to quantify it and how to measure it. When she applies for a new product role, her resume reflects this approach.</p><p><a href="https://en.wikipedia.org/wiki/Peter_Principle">Responsibility does not correlate with demonstrable success</a>. I don’t care, per se, that you’ve held a VP title or that you’ve overseen important teams or functions. I don’t care about the roadmaps, backlogs, requirements lists, prototypes or other deliverables and outputs you’ve created. I don’t care that you’re a CSC, CAPM, PSM, CSPO or any other three or four letter combination. These things tell me that you may know how to talk the talk, but they don’t reveal much about your ability to walk the walk. The truly important stuff is <em>at</em> <em>the end</em> of the title, the artifacts or the certificate, namely the outcomes they helped you realize. Tell me about the value you delivered to users, to your company, to your team — this is what really matters.</p><p>Have you shipped software? Did you play a vital role in defining and executing on the product? Did users find it valuable? Could you prove it? Would your team love to work with you again? Great — let’s talk!</p><h3>3. Be deliberate about what you say and how you say it</h3><h4>Or: Make your pitch easy to understand.</h4><p>The hiring manager is looking to understand one essential thing about you from your application: <strong><em>Might you be a good fit for us?</em></strong></p><p>A great hiring manager also tries to understand a second equally important thing: <strong><em>Might we be a good fit for you?</em></strong></p><p>What you say and how you say determines how easily the hiring manager can answer these questions.</p><p>I can easily glean a number of important PM skills and traits from a candidate’s resume and cover letter. For instance:</p><ul><li><strong>Storytelling</strong>. Can the candidate effectively tell me why my company is the right place for her, and the PM role is the right next step in her career? It’s disappointing how many applicants don’t actually tell me <em>why</em> they are interested in joining Pivotal Labs. More surprising yet is how many manage to string together a bunch of words that don’t say convey anything of substance (or, occasionally, coherence). Don’t be this gobbly goop person.</li><li><strong>Prioritization. </strong>Does the candidate know what is important to share and what is not? So many candidates tell me ALL THE THINGS (I once received an 8-page resume in my inbox). If you can’t differentiate the crud from what matters, you lack focus. If you lack focus, you don’t understand what it is you’re trying to achieve. If you don’t understand what you’re trying to achieve, you’re going to cause a lot of waste and perhaps never get to anything valuable in the end.</li><li><strong>Consulting</strong>. Does the candidate understand what I am looking for? Has she done her research? Can she help me quickly understand all the interesting things she’s done without having all of her context and background? Has she built empathy for the person or team at the receiving end of her application, and can she convey that empathy? A strong consulting PM can create clarity amidst complexity and guide a client towards making informed decisions by presenting the right information.</li></ul><p>To summarize, position yourself for the job the way a Product Manager would position her product to her customers.</p><ol><li><strong>Understand your audience:</strong> Demonstrate how you match my company’s flavor of Product Manager.</li><li><strong>Demonstrate your value:</strong> Tell me what you’ve accomplished, not what you’ve been responsible for.</li><li><strong>Communicate well:</strong> Be deliberate about what you say and how you say it.</li></ol><p>Good luck! <em>(And when you’ve written that awesome resume, consider </em><a href="http://pivotal.io/careers/"><em>sharing it with us</em></a><em> — we’re looking for experienced Product Managers to join our growing team.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a60c3f54f7b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/3-steps-to-landing-any-product-manager-interview-a60c3f54f7b7">3 Steps to Landing any Product Manager Interview</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day in the life of a Pivotal Labs Engineer]]></title>
            <link>https://medium.com/built-to-adapt/a-day-in-the-life-of-a-pivotal-labs-engineer-49749e587165?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/49749e587165</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[working-at-pivotal-labs]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Thu, 12 Mar 2015 12:47:46 GMT</pubDate>
            <atom:updated>2017-12-13T20:16:19.784Z</atom:updated>
            <content:encoded><![CDATA[<h2>A Day In The Life of an Engineer at Pivotal Labs</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*w2mClnNs4rqgVBzl2knVyA.jpeg" /><figcaption>Micah Young is an Engineering Manager at Pivotal Labs, New York.</figcaption></figure><h2>Micah Young</h2><blockquote>ENGINEERING MANAGER, PIVOTAL LABS, NEW YORK</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*m8H_QtuyPbeSNoPxvn4-0g.jpeg" /></figure><p><strong><em>I found Pivotal Labs… </em></strong>through another developer in NYC who recommended the company to me. I had been an independent Rails developer for a while. I felt like I wasn’t learning a lot and like I was at the whim of whoever was able to sit with me and teach me something. I wanted to go to a place where I could really level up my skills and learn the right way to build software, not just read Stack Overflow suggestions for how to do things.</p><p><strong><em>I decided to join Pivotal Labs because… </em></strong>I wanted to get into consulting. I found myself getting tired of working on the same product. I felt like I was surrounded by like minded people as soon as I stepped in the door — people who like to build high quality software, talk about the best ways to do it, and who have a sense of humor and self awareness. Something that I didn’t see anywhere else is the explicit focus on constant improvement. It’s built into the process.</p><p><strong><em>I am currently working on… </em></strong><a href="http://www.singlestopusa.org/">Single Stop</a>, which is a nation wide application for people in need of financial or social services. The app lets the user find and apply for government benefits and get face to face support if they need it. It’s a Ruby on Rails web app, using Slim as a template engine and Sass with Bourbon for CSS. The app is hosted in the cloud and we use RubyMine IDE in our development environment.</p><h2>9 AM</h2><blockquote>PROGRESS REVIEW</blockquote><p>Our project for <a href="http://www.singlestopusa.org/">Single Stop</a> is a screening tool to allow people in need to find out if they are eligible for government benefits. The tool also helps people find service providers in their area.</p><p>Our client developer Hector and I are reviewing the progress we made yesterday. We’re going to put together a plan for today so that we have an idea of what we need to discuss in team standup at 9.15 and if there are any blockers in our way.</p><p>Both of our client developers are new to Rails. They come from a .NET background and are familiar with MVC. To provide a better environment for learning we keep things simple and follow Rails best practices. This approach also facilitates project hand-off at the end of the engagement.</p><h2>10 AM</h2><blockquote>SOLUTION PROTOTYPE</blockquote><p>I’m pairing with Hector, our client developer. He is relatively new to the team. Right now we are talking through a tough business logic problem together to figure out what the simplest solution to it is. In a situation like this it’s invaluable to be working directly with a client developer who knows the business logic well and combining that with our general knowledge as Pivots to come up with a solution that makes sense. Since our client developer will be owning this project in the long term, we want to make sure that any decisions we come to he is comfortable with and believes in.</p><p>What we do first is that we break down the problem in the story into a set of tasks. Then we go through the code and mock out what we think will solve the problem. It’s a first stab and not the code we want to live with. We are just creating an initial prototype of the solution. When it starts to feel right we drop what we have and rewrite it — tests-first — and come up with a better implementation. We don’t always spike out a prototype first. Sometimes we know exactly what we want to do and jump into the first test.</p><p>This forces me to understand the problem and learn about what is really going on on a technical level. By making sure it won’t be my own code but that it will be shared with someone else, you get over the embarrassment of putting something out there because you know that someone else will review it. It also forces you to clean it up before you commit it. That’s where we rely on tests and it helps us end up with clean code.</p><h2>11 AM</h2><blockquote>PUSH TO GREEN</blockquote><p>We knocked out the first part of our story. Now we’re finishing the second part of it so that we can deliver it.</p><p>We have a continuous integration server (CI) that runs the complete test suite every time we push. After each successful build, CI will trigger a deployment to our acceptance environment, where the project Product Manager can test and accept the work we’ve done.</p><p>It took us a few iterations to get this running smoothly, experimenting on different tools to make sure this process is reliable. We iterated until we got to a point where it was mature enough and did not demand attention from developers so we can focus on working on stories.</p><h2>12 PM</h2><blockquote>ONE-ON-ONE LUNCH</blockquote><p>I’m heading out to a one-on-one lunch with one of my reports. I’m an engineering manager which means that I am a normal developer on the floor and a professional mentor to other developers. As engineers, most of our time is spent pairing and talking to people on our project teams. We take advantage of lunch time to talk with the people we mentor and don’t work with on a day to day basis. We usually grab lunch once a month to go through the person’s recent peer feedback and their professional goals. A big part of helping someone achieve their goals is to identify blockers, help them set up feedback loops with team members and track progress. If there’s something the developer can’t solve themselves, that’s where I can come in and help. I can provide a second opinion and help them work through it, whether it’s a project challenge, an interpersonal challenge, or even getting Pivotal Labs to try something new we haven’t tried before.</p><p>Feedback is essential on all levels for what we do. We try to get regular feedback that is specific, actionable and kind as much as we can in person. To get feedback spanning longer periods of time or to track progress over time, we use a feedback tool that we have developed ourselves. Pivots can also request feedback from their colleagues through the tool.</p><h2>1 PM</h2><blockquote>REFACTOR</blockquote><p>We’re adding a new screen to the app today. It introduces some changes to one of our main user flows. These changes made us rethink how we did the architecture for the flow leading up to it. We got our first integration test to pass, and now we’re documenting the user flow in our tests, as it exists now. We did some refactoring to make the code we are about to write fit better with our current architectural patterns.</p><h2>2 PM</h2><blockquote>PAIRING</blockquote><p>There’s always this uncomfortable moment in pairing when you have to take the mouse or the keyboard away from someone else. You either have to say “Hey, can I take over for a second?” or talk about line numbers on the screen. The best way to do it is to just point on the screen but that doesn’t work with two screens. That’s why we’ve developed a tool for it. We’ve hooked up a Leap Motion motion tracker with the shortcuts app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*SMddJz-8C27VuDe9qcT-3g.gif" /></figure><p>If I am training someone else on tools or on good development practices, it’s best if they do most of the legwork. By using a tool like this, I can avoid interrupting them all the time and I can communicate the minimum amount of information required so that they can do the rest.</p><h2>3 PM</h2><blockquote>REFACTOR</blockquote><p>We got to delete a lot of the code and it felt great. We thought about it a lot before and then spent 20 minutes looking at how our refactor would affect the rest of the application. We have lots of confidence that we are deleting the right code and it ended up being a relief once we took it out.</p><h2>4 PM</h2><blockquote>PASSING TESTS</blockquote><p>We are finally adding more stuff to our integration test. It’s the finer details of the new user flow. On the left side is the app in its current state. This is the minimum that made our tests pass and we got it all done today. On the right is the final design for the app which is the goal we are working towards.</p><p>We have a good feedback loop from product and design. Linda, our designer, sits with us which makes it really easy to collaborate. A lot of the design has been done already and is available to us in our live style guide which has all the markup and styles. All we have to do is to bring in the styles from the guide and it just works.</p><p>I’ve learned a lot about getting more results with less code today. By having a real world use case, we got some validation that the software we use is flexible. I really feel like we have been doing the right thing. A pretty big architecture change only took us a few hours. Our tests are passing so we have created a pretty good process. All of this is from a story we hashed out pretty recently. We are able to go and implement these stories on Monday and now we are picking up a story with a big tech change.</p><h2>5 PM</h2><blockquote>DESIGN PROGRESS</blockquote><p>We have finally started to pull in completed designs. The app looks a bit fancier now. Since we already had our passing tests, there’s nothing more to do here code wise. We just want to avoid breaking anything we already have in here.</p><p>We realized something that made our refactor even better. We had different styles from what we had coded up a while ago from what we have now. Because of how we have separated up our codebase it makes it easier to use the new style.</p><h2>6 PM</h2><blockquote>END OF DAY RETRO</blockquote><p>We’re wrapping up the story for the day. We try to leave ourselves a good failing test so that when we come back tomorrow we know exactly what to do next.</p><p>By being able to leave at 6 pm each day we can plan ahead for the end of the day. Hector and I do a mini pair retro at the end of each day. We talk about what went well today and what was difficult that we should try to change tomorrow. We’ll look back at the exact same retro items we did yesterday to see if we fixed what we said we’ll fix. This is especially useful when you work with another developer for the first time. The other person may not yet be comfortable telling me not to do things that they find annoying. This way we can surface issues quickly and solve them constructively together.</p><p><a href="http://www.pivotallabs.com/"><strong>Pivotal Labs</strong></a><strong> </strong><em>is an agile software consultancy. We collaboratively build and design mobile and web apps for the world’s largest brands.</em></p><p><em>If you’d like to learn more, please visit our </em><a href="http://pivotallabs.com/careers/"><strong>careers page</strong></a><strong>.</strong></p><p><em>This profile of Micah Young was edited by </em><a href="http://twitter.com/jbeltowska">Joanna Beltowska</a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/72/1*iEKCWRbNP-1ba9QuxporEA.jpeg" /></figure><p><em>Follow us on </em><a href="http://www.twitter.com/pivotallabs"><em>Twitter</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/147/1*0aLgrdaxZi2k9Vsl-fsrIg.jpeg" /></figure><p><em>Visit our </em><a href="http://pivotallabs.com/careers/"><em>careers page</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49749e587165" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/a-day-in-the-life-of-a-pivotal-labs-engineer-49749e587165">A Day in the life of a Pivotal Labs Engineer</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day In The Life of a Product Designer at Pivotal Labs]]></title>
            <link>https://medium.com/built-to-adapt/a-day-in-the-life-of-a-product-designer-at-pivotal-labs-9b3ee049a0c6?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b3ee049a0c6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[working-at-pivotal-labs]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Fri, 19 Dec 2014 14:17:11 GMT</pubDate>
            <atom:updated>2017-12-13T20:19:18.454Z</atom:updated>
            <content:encoded><![CDATA[<h2>A Day in the Life of a Product Designer at Pivotal Labs</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*ZTBLmpC2GnaU2V_2KHHXEg.jpeg" /><figcaption>Josh Franklin is a Product Designer at Pivotal Labs, New York.</figcaption></figure><h2>Josh Franklin</h2><blockquote>PRODUCT DESIGNER, PIVOTAL LABS, NEW YORK</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*k6D5GdJCxIjYMaJFVpdyUA.png" /></figure><p><strong><em>I found Pivotal Labs… </em></strong>through my colleague <a href="http://twitter.com/jonathanpberger">Jon</a>, who heads up design in NYC and who I knew previously. I worked at an agency in Vermont and wanted to move to NYC. I had recently started participating in hackathons and learning about software development. I hit up Jon to hear what was going on with design in NYC, and he suggested I come in to Pivotal Labs.</p><p><strong><em>I decided to join Pivotal Labs because… </em></strong>I liked the opportunity to bounce between professions while being a designer. You get to wear a bunch of different hats here. Right now I’m working on a social networking app. Before that, I worked on an app for a non-profit. Before <em>that</em>, I worked on an enterprise app. I also liked that there are all sorts of balanced teams. As designers, we don’t just sit in our own design ivory tower, we’re integrated with the rest of the team. I get to pair with developers. I get to learn a lot of new things. I’ve learned so much about front end web development since being here.</p><p><strong><em>I am currently working on… </em></strong>A social networking app. Users can create events and the events last only as long as the event itself.</p><h2>9 AM</h2><blockquote>DESIGN PARITY TWEAKS</blockquote><p>I’m creating new assets for our iOS app so that we have better parity on design between our iOS app and our Android app. We started to work on the Android app after we had started to work on the iOS app. I want to make sure that the design decisions we have made on Android are carried back through to the iOS app.</p><p>I’m simultaneously prepping for a work session in the next hour where I’ll walk the developers through a set of adjustments to our new user onboarding flow. I’ve found that it’s really valuable to involve all the perspectives on a team when working on a new chunk of work. Anyone can have great ideas that will make the product better, not just designers.</p><h2>10 AM</h2><blockquote>NEW USER FLOW WALKTHROUGH</blockquote><p>I’m walking a developer pair on the team through a new user flow. We previously used Facebook to log users in and to help users find people to connect with in the app. We are switching to using users’ own contacts instead. We made this decision because we want to be less reliant on another social platform. Today you have to already be friends on another platform before you can become friends on ours.</p><p>I want to get the developers familiar with the new design so that when we get to next week’s <a href="http://pivotallabs.com/running-an-ipm/">Iteration Planning Meeting</a> and look at the new user stories, it won’t be the first time that they see this stuff. It’s generally a good idea to get some buy-in and help everyone understand the rationale behind your design decisions before you throw new work at them to estimate. I like to share ahead of the Iteration Planning Meeting as much as possible. Typcially, I’ll grab one pair of developers. This time, I grabbed just the iOS pair.</p><h2>11 AM</h2><blockquote>COPY WRITING</blockquote><p>The work session went well. The devs had some notes about the complexity of certain pieces of the onboarding flow where we show notifications.</p><p>Now, I’m working with my client <a href="https://medium.com/product-labs/a-day-in-the-life-of-a-product-manager-at-pivotal-labs-ead9149af629">Product Manager</a> on the copy for in-app notifications. The app is very location and notification specific so we are trying to figure out how to get users to grant the app the permissions it needs. We want to make sure that people grant the app the permissions it’s asking for before they sign in so that they have a great experience using it.</p><h2>12 PM</h2><blockquote>USABILITY TESTING</blockquote><p>Normally our team does standup at noon, but today I’m running a usability testing session with a group of college students.</p><p>I’m testing whether users find the new onboarding flow too complex. Because we’re replacing Facebook with contacts to help users find friends in the app, there’s now a bunch of new permissions that an iOS user has to accept. I want to understand whether users are ok with how we’ve designed for this.</p><h2>1 PM</h2><blockquote>PRODUCT OFFICE HOURS</blockquote><p>Every other week we do something called <a href="http://pivotallabs.com/productofficehours/">Product Office Hours</a> at the NYC office. One startup team joins us for lunch and we help them work through a product-related challenge. A couple of Product Managers and designers will typically be in the room to help.</p><p>Today we had <a href="https://thursdayfinest.com/">Thursday Finest</a> come in. They offer customizable neck ties. We did a design critique on their new ecommerce site.</p><p>This is the first design critique we have done for an outside company, and it was pretty awesome. We are often asked to opinionate on existing design solutions, but the Thursday Finest team gave us problems to solve instead. The techniques we have developed internally for working through design problems transferred really well to this session.</p><p>The Thursday Finest team got a lot out of our session together. They’re excited about taking some of these practices back to their company. They want to figure out how to best utilize Agile and Lean practices in their own product development and design process.</p><h2>2 PM</h2><blockquote>DESIGN BACKLOG GROOMING</blockquote><p>Because we’re developing the app for two platforms simultaneously, iOS and Android, we have two backlogs. I’m going through both of them to see which stories still need design assets so I can make sure that we have covered our bases by the end of the week and feel good about this week’s progress.</p><p>We thought a lot about whether we wanted to keep the backlogs separate or combined. In the end we decided to keep them separate. The iOS work has been progressing slower than the Android work and with separate backlogs we avoid getting blocked. I can still work on design stories across both backlogs simultaneously so that the design stays consistent across platforms.</p><h2>3 PM</h2><blockquote>ONBOARDING FLOW TWEAKS</blockquote><p>I’m making adjustments to the onboarding flow. Because we are creating our own social graph rather than using Facebook’s, we need to handle edge cases where you pull in people into the app who you are not already friends with. It’s similar to Snapchat. They’ll have the app installed, you’re not friends, you search for them and then you add them. I just went over the step of adding users by searching for their phone number.</p><h2>4 PM</h2><blockquote>PING PONG BREAK</blockquote><p>Usually I like to take a ping pong break maybe two or three times a day. If I am solo:ing that day, as opposed to pairing with someone, I’ll grab another designer or a developer from my team who is also solo:ing.</p><p>It’s just nice to step away for a bit. Some things click when you come back to the computer. You either go “It all makes sense now!” or “This doesn’t make sense at all, what was I thinking?”</p><h2>5 PM</h2><blockquote>WEEKLY TEAM RETROSPECTIVE</blockquote><p>At 5 PM it’s time for our weekly <a href="http://pivotallabs.com/retro-best-practices/">retrospective</a>, or retro in short. The team gets together to talk about what went during the week, what did not go so well and what there’s confusion or uncertainty about. We end the retro by capturing action items and assigning an owner to each one. We also make sure to follow up on last week’s action items. It’s a a nice way to end the week.</p><p>I’m going to bring up that we need to do more feature validation and usability testing before diving into big chunks of development work. I think several people will bring up how great it is that we’ve had more client developers join the team this week. We’re about even now between Pivots and client developers which is great.</p><h2>6 PM</h2><blockquote>WEEKEND!</blockquote><p>It’s 6 pm so I’m packing up for the week.</p><p>I’m heading out to get dinner with some friends and then it’s the weekend. My girlfriend and I are planning to look at apartments. I’m pretty excited about that.</p><p><a href="http://www.pivotallabs.com/"><strong>Pivotal Labs</strong></a><strong> </strong><em>is an agile software consultancy. We collaboratively build and design mobile and web apps for the world’s largest brands.</em></p><p><em>If you’d like to learn more, please visit our </em><a href="http://pivotallabs.com/careers/"><strong>careers page</strong></a><strong>.</strong></p><p><em>This profile of Josh Franklin was edited by </em><a href="http://twitter.com/jbeltowska">Joanna Beltowska</a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/72/1*nhY4NwysuSWvQUvEnKOY3A.jpeg" /></figure><p><em>Follow us on </em><a href="http://www.twitter.com/pivotallabs"><em>Twitter</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/147/1*0aLgrdaxZi2k9Vsl-fsrIg.jpeg" /></figure><p><em>Visit our </em><a href="http://pivotallabs.com/careers/"><em>careers page</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b3ee049a0c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/a-day-in-the-life-of-a-product-designer-at-pivotal-labs-9b3ee049a0c6">A Day In The Life of a Product Designer at Pivotal Labs</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Day In The Life of a Product Manager at Pivotal Labs]]></title>
            <link>https://medium.com/built-to-adapt/a-day-in-the-life-of-a-product-manager-at-pivotal-labs-ead9149af629?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ead9149af629</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[working-at-pivotal-labs]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Tue, 16 Dec 2014 17:18:42 GMT</pubDate>
            <atom:updated>2017-12-13T20:20:12.106Z</atom:updated>
            <content:encoded><![CDATA[<h2>A Day in the Life of a Product Manager at Pivotal Labs</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*q3OqsucAy1iDAUwE8KQNug.jpeg" /><figcaption>Arielle Silverman is one of six Product Managers at Pivotal Labs, New York.</figcaption></figure><h2>Arielle Silverman</h2><blockquote><em>PRODUCT MANAGER, PIVOTAL LABS, NEW YORK</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*mHiW0z8RKwZD6n5tT30N3Q.jpeg" /></figure><p><strong><em>I found Pivotal Labs…</em></strong><em> </em>through a former boss who once worked with Pivotal Labs as a client Product Manager. He told me I should apply because I’d love the agile product development process. He was right.</p><p><strong><em>I decided to join Pivotal Labs because… </em></strong>One of the things that stands out to me about Pivotal Labs is that it’s sane here. There’s an emphasis on sustainable pace.<em> </em>Another<em> </em>thing is that you are not assigned to one project forever. I also like our motto of doing what’s right. I have worked places where we have known that something is not a great decision but we have had to do it anyway. Having “do what works and do what’s right” as a guiding principle is really attractive to me.</p><p><strong><em>I am currently working on…</em></strong> A customer-facing iOS app for an enterprise organization.</p><h2>9 AM</h2><blockquote>OFFICE STANDUP</blockquote><p>I come in around 8.45 am and grab some breakfast in the cafeteria. Office standup is right after 9 am. Our team of 80 Pivots gather in the main office space. It takes us short of five minutes. We welcome any new faces (who are either new hires or visitors), see whether anyone is asking for help with something, and share anything interesting we’ve come across.</p><p>After office standup, I head over to my team’s daily standup. We have remote team members so we do our standup on the phone. Due to the nature of our client’s business, we’re restricted from using video chat. We haven’t found a good video solution that works in this particular corporate setting yet. I’m constantly thinking about how we might make this process better.</p><h2>10 AM</h2><blockquote>INTERVIEW PREP</blockquote><p>I’m getting ready to interview a candidate for our Chicago office. I like our interview format. We give Product Manager (PM) candidates a homework assignment which they present to one of our PMs when they come in. We also do a collaborative exercise with them.</p><p>I feel like I can empathize with the candidates I am interviewing because I remember being in their shoes. I like the collaborative exercise. I won’t reveal what it entails, but it covers all the things that are our bread and butter – defining product goals, deciding how to measure success, wireframing, prioritizing features and writing user stories. It’s fun to do that process at a small scale.</p><h2>11 AM</h2><blockquote>CANDIDATE EVALUATION</blockquote><p>I just finished the interview. I like to write down my notes on how it went right away. I’ll type up my feedback later and share it with our recruiter Monica as well as the other PMs who interviewed the candidate today.</p><p>Earlier this morning I did some work on a client proposal. I’m refining a scoping document that I started writing yesterday. I have to review the content and polish the language today. I enjoy being involved in the process at such an early stage, and seeing the business side of things.</p><h2>12 PM</h2><blockquote>PRODUCT AND DESIGN STANDUP</blockquote><p>At noon <a href="http://www.twitter.com/jonathanpberger">Jon</a>, who heads up our design team, summons all the Product Managers and Designers with his ukulele to the daily product and design standup.</p><p>We go around and share the status of our projects. I like knowing what everyone else is working on. There was one day when I was summarizing a round of user research that I had done. A designer had just done the same thing and we got a chance to compare notes. This is also really helpful when we rotate on to new projects. I have some context on every product that we are working on. I’ll know at least a bit about what’s going on when I join a new team.</p><h2>1 PM</h2><blockquote>LUNCH TIME TECH TALK: TANNER FROM BUZZFEED</blockquote><p>We host a lunch time tech talk every Tuesday. Lunch is catered by our chefs Brian and Carla. The speaker will either be a fellow Pivot or someone from another company.</p><p>Today’s tech talk was from Buzzfeed editor Tanner Ringerud. Tanner talked about the evolution of the wildly popular Buzzfeed quizz and Buzzfeed’s culture of product experiments. It was interesting to hear how they have learned that the most popular quizzes are the ones that reveal something about our identity (like the <a href="http://www.buzzfeed.com/awesomer/what-level-geek-are-you">Geek quiz</a> or the expert level <a href="http://www.buzzfeed.com/jarettwieselman/the-hardest-mean-girls-quiz-youll-ever-take">Mean Girls quiz</a>).</p><h2>2 PM</h2><blockquote>USABILITY TEST PLAN</blockquote><p>I’m working on a usability testing plan for my team. We met with the client yesterday. Our client PM wants to validate a list of things. We test each week but this time around we’re going to travel to our client’s office in Washington DC and their usability lab there. It will definitely be more hardcore. We’ll do a full day of user interviews. I have to figure out what activities we should do, articulate what it is we want to learn and what we need to prepare for the trip. Our client will do the recruiting. We’re used to doing it all ourselves but we’ll just observe and take notes this time.</p><h2>3 pm</h2><blockquote>MEETING WITH THE OTHER PRODUCT MANGERS</blockquote><p>The PM team meets each week to talk about the product practice and trade experiences with each other.</p><p>Today we talked about pairing with designers. It was a good conversation. I especially liked talking about how we collaborate with designers in usability testing sessions. I didn’t know usability testing was going to be part of my role when I got here but I really like it.</p><p>If I were to pick the three most valuable skills I’ve learned at <a href="http://pivotallabs.com/">Pivotal Labs</a> so far, I’d say it’s usability testing along with scope writing and workshop facilitation. With facilitation, everywhere else I have been the PM has dictated things and been the sole voice of the product in meetings. Here, it’s much more collaborative. It’s not your job to tell everyone the answers. It’s much more about being a good listener and stepping in at the right moments as a facilitator.</p><h2>4 PM</h2><blockquote>CLIENT CHECKIN</blockquote><p>I’m getting ready to discuss our backlog with the client. I have to re-set some deadline expectations. It can be tricky to work these sort of things out when agile meets quarterly planning. We work in a realm of uncertainty towards defining <em>some</em> certainty. At any given moment things can change. It’s a bit of a struggle to give people the certainty and comfort they want. But we have to recognize that other organizations operate differently than we do. Part of the job is coaching people how to live with that constant change.</p><p>The saving grace is that I have a wonderful Product Owner who helps me prioritize the work. Even if we don’t get through it all, I know we’ll get through what’s most important.</p><p>We sat down together last week and went through all the stories in the backlog, moved lots of them to the icebox and came up with new ones. She owns the business opportunity and decides what we should do next. We act as advisors. It’s a very different relationship than at most client services firms, where one person on the client side is the owner of the precious thing called the product. Here, it’s a partnership.</p><h2>5 PM</h2><blockquote>PROPOSAL WRAP-UP</blockquote><p>I just wrapped up the proposal. I have to pair with <a href="https://twitter.com/FranciscoHui">Francisco</a>, who is the designer on my team, tomorrow to get his feedback on it before we send it to the client.</p><p>I have some more work to do on the usability testing plan. I have to book our travel so we make it out to the client’s test lab.</p><h2>6 PM</h2><blockquote>TIMESHEET</blockquote><p>The day is almost over. I’m doing my timesheet real quick before I head out to meet up with some friends for dinner.</p><p><a href="http://www.pivotallabs.com/"><strong>Pivotal Labs</strong></a><em> is an agile software consultancy. We collaboratively build and design mobile and web apps for the world’s largest brands.</em></p><p><em>We are currently hiring Product Managers for all of our offices. If you’d like to learn more, please visit our </em><a href="http://pivotallabs.com/careers/"><strong>careers page</strong></a><em>.</em></p><p><em>This profile of </em><a href="http://www.twitter.com/@_asilverman">Arielle Silverman</a><em> was edited by </em><a href="https://medium.com/@jbeltowska">Joanna Beltowska</a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/72/1*iEKCWRbNP-1ba9QuxporEA.jpeg" /></figure><p><em>Follow us on </em><a href="http://www.twitter.com/pivotallabs"><em>Twitter</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/147/1*oUiFShZp8JVdzIM2Xgsx1A.jpeg" /></figure><p><em>Visit our </em><a href="http://pivotallabs.com/careers/"><em>careers page</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ead9149af629" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/a-day-in-the-life-of-a-product-manager-at-pivotal-labs-ead9149af629">A Day In The Life of a Product Manager at Pivotal Labs</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minimum viable demo]]></title>
            <link>https://medium.com/product-labs/minimum-viable-demo-ce81e2c92969?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce81e2c92969</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Mon, 27 Oct 2014 18:51:22 GMT</pubDate>
            <atom:updated>2017-05-01T20:25:28.815Z</atom:updated>
            <content:encoded><![CDATA[<h4>Use animated gifs to explain your awesome new features</h4><p>Imagine you are a Product Manager inside a large organization.</p><p>Your team has just finished a new feature for internal users.</p><p>As the PM, you need your colleagues to understand and use the new feature. Your colleagues, however, are busy and have priorities of their own.</p><p>Thus begins the challenge of coordinating and scheduling demos so that you can collect feedback and drive internal adoption. You know how it goes: people are hard to track down, they are spread across time zones, they’re fully booked for weeks and when you finally manage to find a time that works for everyone, scheduling conflicts cause some of your participants to not show up.</p><p>What if there was an easier way to explain your new feature?</p><h3>How to demo a feature in seconds</h3><p><strong>Step 1: Grab your favorite tool for creating animated gifs. </strong>I use <a href="https://github.com/lepht/licecap">LICEcap</a>, a free and open sourced app for creating animated screen-caps.</p><p><strong>Step 2: Record your screen as you use the new feature.</strong></p><p><strong>Step 3: Email your animated gif to your users. </strong>Keep it short and sweet. Explain what your animated gif shows and why it’s great:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4jv3ZAs52D6JxPcLgHJpug.gif" /><figcaption>Example email with gif demo.</figcaption></figure><h3>Here’s why this approach is worth trying</h3><p><strong>It’s cheap:</strong> It won’t take you more than 5 minutes to create a gif demo and share it.</p><p><strong>It scales: </strong>It will take the same amount of effort whether you’re sharing with 10 people or 100.</p><p><strong>It’s asynchronous:</strong> The .gif demo doesn’t need to care about time zones.</p><p><strong>It’s considerate: </strong>The .gif demo asks for seconds, not minutes (or hours), of the recipient’s time.</p><p><strong>It shortens the feedback loop: </strong>The .gif demo surfaces feedback faster than a traditional demo meeting because it gives the users something to react to faster.</p><h3>But my feature is more complex than a small UI change</h3><p>If you’re launching a larger feature, you’ll probably want to set up in person demo to walk people through the changes.</p><p>The gif demo can still be your friend: use it to share one or more previews of the changes to get your users excited and help them understand how the new feature will affect them.</p><h3>Taking your gif demo from good to great</h3><ul><li><strong>Keep it short. </strong>You’re recording a gif, not a video. Keep it under 10 seconds. (For inspiration, check out Lowes’ <a href="https://vine.co/Lowes">Fix in Six campaign</a>, a series of instructional 6-second videos)</li><li><strong>Plan ahead. </strong>To make the most of the time you have, think about what it is you need to show – you’ll have to be selective. Is it an entire workflow, or perhaps just one key step?</li><li><strong>Practice. </strong>Practice a couple of times so that you know exactly what workflow you want to demonstrate. This will help you keep your gif short. It will also show off the feature better as you won’t hesitate or look where to click next.</li><li><strong>Don’t forget to loop.</strong> Your recipients will probably want to watch the demo more than once. Help them do so by looping your gif.</li></ul><p><em>I work at Pivotal Labs. We are currently hiring product managers for all of our offices. If you’d like to learn more go to </em><a href="http://pivotallabs.com/careers/"><em>http://pivotallabs.com/careers/</em></a><em> or ping me @jbeltowska.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce81e2c92969" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-labs/minimum-viable-demo-ce81e2c92969">Minimum viable demo</a> was originally published in <a href="https://medium.com/product-labs">Product Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So you want to be a Product Manager?]]></title>
            <link>https://medium.com/@jbeltowska/advice-to-those-considering-transitioning-into-product-management-ad65f8b26f8f?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad65f8b26f8f</guid>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Wed, 15 Oct 2014 17:34:44 GMT</pubDate>
            <atom:updated>2014-10-27T21:34:50.881Z</atom:updated>
            <content:encoded><![CDATA[<h4>A 4-step transition plan for aspiring PMs</h4><p>A couple of weeks ago I had breakfast with an aspiring Product Manager. She asked me what advice I could offer someone who is considering a transition into Product Management from another field.</p><p>I made this transition at the beginning of the year, moving from being a strategy consultant to a Product Manager at Pivotal Labs.</p><p>I remember how daunting the idea felt when I first made the decision to go for it. I had a perception of Product Management as a very competitive field (at least considering the organizations I wanted to join), and an increasingly popular one at that.</p><p>Here’s the advice I shared with her, based on my own experience.</p><h3>1. Explore it.</h3><p>Before you make the decision to pursue Product Management, educate yourself.</p><p>Do you have a good understanding of what the work looks like, day to day? Do you have a sense of how the role varies between industries and organizations? Do you have some idea of what Product Managers are measured on?</p><p>A few starting points:</p><ul><li><strong>Go to product meetups. </strong>Hearing real Product Managers talk about what they do and how they do it is invaluable to aid your understanding of the role. If you’re in NYC, the <a href="http://www.meetup.com/Product-Council-NYC/">Product Council</a> meetup is a great one to go to: it’s structured around a panel of experienced product people helping startups and entrepreneurs with product challenges.</li><li><strong>Read things written by Product Managers.</strong> I’ve found the writings of <a href="http://www.svproduct.com/articles">Marty Cagan</a> (partner at Silicon Valley Product Group), <a href="https://medium.com/@ellenchisa">Ellen Chisa</a> (previously a Product Manager at Kickstarter, currently a student at HBS), <a href="https://medium.com/@Bosefina">Bo Ren</a> (Product Manager at Facebook), <a href="https://medium.com/@joulee">Julie Zhou</a> (product design director at Facebook), and <a href="http://melissaperri.com/">Melissa Perri</a> (consulting Product Manager) to be really helpful. I’ve also come across some really good stuff in the Medium collections “<a href="https://medium.com/on-product-management">On Product Management</a>”, “<a href="https://medium.com/what-i-learned-building">What I learned building</a>”, “<a href="https://medium.com/art-of-product-design">Art of Product Design</a>”, and “<a href="https://medium.com/building-things-on-the-internet">Building Things on the Internet</a>”.</li><li><strong>Explore Noah Weiss’ </strong><a href="https://medium.com/@noah_weiss/50-articles-and-books-that-will-make-you-a-great-product-manager-aad5babee2f7"><strong>great list</strong></a><strong> of articles and books about working on product.</strong></li><li><strong>Take an introductory class. </strong><a href="https://generalassemb.ly/education?format=classes-workshops">General Assembly</a> and <a href="http://www.skillshare.com/search?query=product+">Skillshare</a> both offer workshops and classes on the fundamentals of Product Management.</li></ul><h3>2. Try it on.</h3><p>Before you commit yourself to making a big change, find small ways of trying it on.</p><p>This could be a side project, helping a startup founder friend on the weekends or developing a new product for the place you work. (I define “product” loosely here as some thing that people are willing to a pay for, if not with money then at least with usage).</p><p>Think about the products you currently use, both the ones you love and the ones that frustrate you. What problems are they trying to solve? For whom? Are they doing a good job or might you have some ideas for improvements or even for a completely different solution?</p><blockquote>Your mission at this stage is to start thinking like a Product Manager.</blockquote><p>This is one very important thing that you CAN control while you are working towards finding the right position and getting it.</p><p>When I started getting serious about transitioning into Product Management I sought out opportunities to act as a Product Manager. For instance, I started advising companies in my network on customer development, product strategy and how to build product teams. I led product-focused strategy engagements. I designed and ran a <a href="https://medium.com/@jbeltowska/the-10x-workshop-1cd67cd3c56c">week-long product prototyping workshop</a> (the Medium post I wrote about it generated a couple of interviews, so definitely share your work online!)</p><p>These experiences confirmed to me that product was what I wanted to do, that I really enjoyed doing it and that I’d be good at it. I learned a lot about what kind of Product Manager I wanted to be and developed an initial version of my own product development process and philosophy.</p><p>All of this was tremendously helpful when I was interviewing: I could easily speak to what I believed was needed to build successful products, and the things I said were informed by my own experience rather than by things I’d read or heard from others.</p><h3>3. Define your goals</h3><p>Now that you have a better, perhaps even tactile, understanding of the Product Manager role, it’s time to set some goals to inform your job seeking.</p><p>Think about what kind of Product Manager you want to be, what industry you want to work in and what sort of company you’d like to be at.</p><p>Then, think about what’s <em>realistic</em> for your first Product Manager role (but still a valuable step towards your long-term career objectives), given your experience.</p><blockquote>You will most likely not land your dream Product Manager role at first but you can do your best to find one that becomes a great stepping stone.</blockquote><p>I knew that I wanted to work on software products and that I wanted to be able to use my experiences as a strategy consultant to inform my product work. I assumed that I wouldn’t be able to get my ideal Product Manager job at first; my objective became to find a <em>legit</em> first Product Manager role – I wanted to go somewhere with an established product practice so that I could learn the foundations of good Product Management and build the experience I needed to get a role closer to my ideal (at the end of the day, I was lucky enough to land my dream job, but I had set my ambitions significantly lower).</p><h3>4. Find your story.</h3><p>When you start interviewing, you’ll need to be able to motivate your potential future employer to take a bet on you. Even if you haven’t had the Product Manager title before, they’ll want to feel confident in your ability to handle the job.</p><p>The story you tell in the interview should explain why Product Management is a great fit for you and why it is a natural next step in your career (and why the place you’re interviewing at is the right place for you to realize that step).</p><p>Prepare by identifying all the strengths you would bring to the role and get comfortable speaking to them. Make sure you can provide a few examples of how you have wielded these strengths. Having put out client fires, made something for the Internet that has gone viral, designed and implemented a successful workshop or event, gotten others to rally behind an idea which you then successfully implemented with their help – these are just a few examples of things that might indicate to an interviewer that you have the right chops.</p><p>You should also have a good sense of what the interviewer may perceive as weaknesses or gaps in your experience, and be able to speak to them (you might have even started addressing these things in step 2).</p><p>After the interview, your lack of previous Product Management experience should be a non-issue — your story should have clarified that you have enough relevant experience and the mindset and thinking tools to handle the job.</p><p>And in case you suffer from impostor syndrome: I had a strong, nagging internal voice telling me that I’d have a hard time convincing the companies I was interviewing with to hire someone as inexperienced in product as myself. To quench that voice, I wrote out my story in the Notes app on my iPhone, practiced it in front of my husband and read it several times on my way to interviews until I could tell it swimmingly from beginning to end.</p><p>The truth is that it doesn’t really matter whether you are confident in yourself or not, as long as you can <em>tell</em> your story with confidence.</p><p>Good luck!</p><p><em>I work at Pivotal Labs. We are currently hiring product managers for all of our offices. If you’d like to learn more go to </em><a href="http://pivotallabs.com/careers/"><em>http://pivotallabs.com/careers/</em></a><em> or ping me @jbeltowska.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad65f8b26f8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 decision-making techniques all Product Managers should know]]></title>
            <link>https://medium.com/built-to-adapt/6-decision-making-techniques-all-product-managers-should-know-429fe4d13654?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/429fe4d13654</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Fri, 01 Aug 2014 13:10:46 GMT</pubDate>
            <atom:updated>2017-12-13T20:18:14.420Z</atom:updated>
            <content:encoded><![CDATA[<h2>6 Decision-Making Techniques all Product Managers Should Know</h2><h4>How to productively make collaborative decisions</h4><p>As a Product Manager you constantly make decisions.</p><p>Many of the decisions you make are made in collaboration with others; business stakeholders, designers, developers, subject matter experts, and other Product Managers.</p><p><strong>Involving other people in the decision making process can be fruitful but also painful.</strong></p><p>It can be a huge time saver, because you may be able to benefit from others’ expertise and experience to quickly understand a problem from many different angles. Additionally, decisions informed by many different perspectives <a href="http://books.google.com/books/about/The_Difference.html?id=FAFVHnJ7uK0C">tend to be better</a>.</p><p>However, as you’ve probably experienced more than once, reaching agreement with many, often passionate, voices in the room can be challenging. Disparate opinions can lead to <a href="http://en.wikipedia.org/wiki/Design_by_committee">too many compromises</a> which in turn lead to mediocre output.</p><p>The techniques described below will help you make decisions confidently and productively together with others, so that you can focus more of your time and energy on building your product.</p><p><em>This write up was inspired by a workshop facilitation training session run at Pivotal Labs, NY, by Janice Fraser (</em><a href="https://twitter.com/clevergirl"><em>@clevergirl</em></a><em>), co-founder of </em><a href="http://luxr.co/"><em>LUXr</em></a><em> and Adaptive Path.</em></p><h3>1. The self-edited idea dump</h3><h4>When to use it</h4><p><strong>When you are generating ideas early on in the process and/or when you need to move beyond the obvious ideas.</strong></p><p><em>Example scenario:</em> You are the Product Manager of an eCommerce site. Its performance has been declining for the past month despite following conversion best practices, so you’ve gathered your team for a brainstorm. How do you come up with new ideas beyond the tried-and-true to improve sales?</p><h4>How it works</h4><p>Give everyone a stack of sticky notes and sharpies, and make sure you’re seated around a table or otherwise close to each other.</p><p>Take one minute to come up with 10 ideas each. Write one idea per sticky. Work individually and in silence.</p><p>Next, ask everyone to select the 5 ideas they want to move forward to the next step. Don’t spend more than 30 seconds doing this. It’s important to frame this section around selecting which ideas to move forward with, rather than which ideas are good vs. bad. Deciding what’s good vs. bad can be a difficult decision, whereas what to move forward with vs. not should be relatively straightforward.</p><p>Now ask the participants to give the 5 ideas they chose to put on hold to the person on their left.</p><p>Next, ask the participants to rip up the ideas they just got from their neighbor. This makes tangible that the ideas the group didn’t move forward are discarded. Oftentimes, participants have a hard time letting ideas go, clinging on to them as if they were precious gems. Ideas are cheap, and the best ideas are rarely the ideas that come to us first. In fact, our first ideas tend to be the safe and obvious. To get to the interesting stuff, you need to move beyond the obvious and this requires you to feel empowered to abandon your ideas.</p><p>You now have 5 ideas per participant that have passed through an initial quality filter. You also have a group of participants who have moved beyond the apparent, into the interesting.</p><h3>2. The 2x2 triage</h3><h4>When to use it</h4><p><strong>When there are so many things to choose between that you can’t easily tell which things really matter.</strong></p><p><em>Example scenario:</em> Imagine that you are planning your next product iteration. You have to balance feature requests from your stakeholders, feature ideas spurred by user research and maintenance work your development team wants to do. How do you decide what work to include and what work to exclude in the iteration?</p><h4>How it works</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*JbAoPvSDv6qEm9mjxDjzBA.png" /></figure><p>This exercise works best with a small number of participants. 3 participants is ideal so that you can make decisions quickly without longwinded discussion.</p><p>Start by writing down all tasks on sticky notes, one task per sticky. You can do this individually or collaboratively.</p><p>Construct a 2x2 matrix on a wall. If you don’t have a whiteboard available, use masking tape.</p><p>Select your axes. Urgent vs. important (also known as the <a href="http://en.wikipedia.org/wiki/Time_management#The_Eisenhower_Method">Eisenhower Matrix</a>) is a good go-to. Effort vs. impact is another alternative when you are less concerned with time.</p><p>A note about naming: you may intuitively want to make your axes polar opposites, e.g. “Urgent vs. Not Urgent” and “Important vs. Not Important”. The problem with this naming convention is that it forces participants to make hard decisions. It can be too difficult to determine in the moment <em>how</em> urgent something is. It’s easier to decide whether something is more urgent or less urgent, especially when compared to other things. Additionally, for someone who feels strongly about an item it’s easier to concede to “Less important” than to “Not important”. Thus, the better naming convention is “More… vs. Less …”; “More urgent vs. Less urgent”.</p><p>Now, start placing the stickies inside the four quadrants. Do this in silence. After all the stickies have been placed on the wall, have a quiet read for a minute and then start asking questions: Is this thing really that important? Are we sure that this thing isn’t more urgent?</p><p>Keep moving the stickies around collectively until you have placed half of them below the horizontal line. Be strict with this; challenge every single sticky that has been placed above the horizontal line until you have moved half of the set to the bottom half.</p><p>You now have clear direction on how to process your items:</p><ul><li>The top right quadrant holds the items that are obvious. These are your definite yeses.</li><li>The top left quadrant holds the items that are up for debate. These are your maybes.</li><li>The two bottom quadrants hold the items that are either unnecessary or not worth the effort.</li></ul><h3>3. The dot vote</h3><h4>When to use it</h4><p><strong>When you have a large set of fairly well-defined ideas and need to decide which subset of ideas to move forward with.</strong></p><p><em>Example scenario: </em>You and your team are designing a new product. It’s a mobile app that allows runners to find other runners in their neighborhood to go running with. Each member of your team has prepared several sketches of what the app’s user experience and interface could look like. How do you decide which design and feature ideas to explore further?</p><h4>How it works</h4><p>Each participant gets a set number of votes. 3 — 5 tends to be a good number; it’s small enough to force hard decisions but big enough to produce patterns. You can either use <a href="http://www.amazon.com/Avery-Self-Adhesive-Removable-Diameter-05468/dp/B00005QT7Y/ref=sr_1_21?ie=UTF8&amp;qid=1406669905&amp;sr=8-21&amp;keywords=sticky+dot">sticky dots</a> or markers to represent votes.</p><p>Next, define what to vote on. In the example with the sketches of the mobile app, you could cast votes on complete sketches (for instance, Jane’s clean registration screen), or on specific ideas in the sketches (for instance, Mark’s clever drop down menu).</p><p>Ask the participants to cast their votes. A participant can choose to put more than one vote on a single thing. If they really like something, they can choose to put all their votes on it.</p><p>Tally up the votes. If you decided to explore all ideas that received at least one vote, you’re done. If you decided to move forward with a fixed number of items, identify which items qualify based on most votes received.</p><h3>4. The stack rank</h3><h4>When to use it</h4><p><strong>When you have a list of items to process but not enough scope to process all of them.</strong></p><p><em>Example scenario: </em>You are working on a tool to help adults learn how to write software code. Your office is being visited by an expert on adult learning, but you’ve only been able to get one hour with them and you have a list of 15+ questions. You think you’ll be able to get through 5 of your questions, but which ones? And which questions should you bring to ask as extras if time permits?</p><p>(<em>This tactic is similar to the dot vote in that it generates a subset of most valuable/most important items. However, the stack rank generates a list of items in order of importance whereas the dot vote doesn’t capture information about the relative importance or value of items.</em>)</p><h4>How it works</h4><p>The participants write down each item on a sticky note or an index card. It’s important that you only write one item per piece of paper because you’ll be moving the items around.</p><p>Next, organize all the items in one column. If you’re working with sticky notes, do this on a wall. If you’re working with index cards, do this on a table.</p><p>Now it’s time to collaboratively sort the items in order of importance. Start rearranging the items, placing the most important item at the top of the column and the least important item at the bottom of the column. Everyone participating in the stack rank exercise are free to move items up and down. Once people stop rearranging the items, the facilitator asks everyone to take a step back, review the column and make any last changes.</p><p>You now have a prioritized list of items. Start processing items from the top. If you only have scope to process 5 out of 15 items, you now know which ones: the top 5 on your list. Should you have additional scope, you now also know which items are your extras.</p><h3>5. The Roman vote</h3><h4>When to use it</h4><p><strong>When you need to concretely select <em>a </em>thing.</strong></p><p><em>Example scenarios: </em>Should we break for a few minutes or keep going? Should we keep this idea or should we throw it out? The Roman vote gives the facilitator an opportunity to formulate an end state to a situation and get the rooms permission to go there. It’s a great tactic to use when a decision has clearly been made by the group but not made explicit yet.</p><h4>How it works</h4><p>Anyone in the room can call a Roman vote. The person who does so should have a proposal ready that can be answered by the group with a yes or a no. For example: “Do we feel comfortable moving forward with this idea?”</p><p>The owner of the proposal then initiates the vote by asking the participants to raise their right arm over their head with their fist clenched.</p><p>On a count of three, to ensure that everyone casts their vote simultaneously to avoid participants influencing each other, every participant casts their vote:</p><ul><li>An upward pointing thumb for a yes</li><li>A downward pointing thumb for a no</li><li>A sideways pointing thumb to go with the will of the group</li></ul><p>Tally the yeses and noes to determine whether the proposal was accepted or rejected by the group.</p><h3>6. The decision matrix</h3><h4>When to use it</h4><p><strong>When you need to process a set of well-defined alternatives from many different angles.</strong></p><p><em>Example scenario: </em>You are debating which one of several possible new features to implement. They are all good ideas but your stakeholders and product sponsors have different ideas about which feature is best. You have also spoken to customers and gotten a basic understanding of how big of a need each feature would solve for. How do you leverage the input of your stakeholders and the feedback of your customers to determine which feature is your best bet?</p><h4>How it works</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*Dzy6Dxh3lRJXnCpklPSbKw.png" /></figure><p>Begin by determining the columns of your decision matrix. Which aspects of the items you’re choosing between are most important? If you are deciding between feature you might want to consider early customer feedback, the ease of technical implementation, how on-brand the feature is. If you need to incorporate the input of certain stakeholders and/or subject matter experts, choose columns representing their expertise.</p><p>Ask every participant to score each idea. When examined against each column, how well does the item score? Use a system of High, Medium and Low.</p><p>After everyone is done, tally up the scores: a High equals 3 points, a Medium equals 2 points and a Low equals 1 point.</p><p>You should now have one winning item, all important angles considered ( if you end up with a tie, repeat the exercise with the items that tied).</p><h3>Bonus: The rapid feedback round</h3><h4>When to use it</h4><p><strong>When you need to process many well-defined ideas in little time with people who are unfamiliar with the ideas.</strong></p><p><em>Example scenario: </em>Your team is working on a mobile step tracking app. You have just launched the MVP. It’s time to determine a direction for the next quarter, and you have identified several future directions for the product based on what you have learned so far. You want to gather the input of internal stakeholders and subject matter experts to better understand the feasibility and value of each proposed direction (for instance, you may be looking to understand dependencies, technical integrations, what data your organization can track or has available about users, etc).</p><h4>How it works</h4><p>Select a facilitator. This person will lead the exercise and keep time.</p><p>Prepare a short description of each idea that you want to collect feedback on. You should be able to describe the idea to your stakeholder group in 60 seconds or less. A good format is to answer key questions like:</p><ul><li>What it is? E.g., <em>it’s a weight tracking feature that shows the user’s weight over time on a beautiful and easy-to-understand chart.</em></li><li>What problem does it solve? E.g., <em>it helps users track their weight against their activity level so that they stay motivated to keep walking.</em></li><li>For whom? E.g., <em>Busy people whose only exercise is walking to and from work, to and from the grocery store, etc.</em></li></ul><p>When you gather with your participants, explain to them first how the exercise works: you will process a certain number of ideas very rapidly.</p><p>First, you will describe the idea in 60 seconds. (Pro-tip: set a timer on your phone for each segment so that everyone can clearly hear when time is up.)</p><p>Next, you will open up to the participants for clarifying questions, such as: Where will the user’s weight data come from? Have you also considered tracking the user’s BMI? Are you planning to capture weight data daily or weekly or at some other interval? You will spend 2 minutes doing this.</p><p>Lastly, ask the participants to contribute amendments to the idea. Spend 3 minutes doing this. The guiding principle here is: Don’t hate, iterate — encourage constructive feedback that makes the idea better. Remember, what you’re looking for is subject matter expertise that makes your idea stronger, not to validate the idea (stakeholder feedback is <em>not</em> validation).</p><p>In an hour you should be able to get through ~10 ideas.</p><p>You now have a set of ideas that have been improved upon leveraging internal expertise. Use one or a few of the other techniques described here to decide which ideas to move forward with and validate with real users.</p><p><em>* This technique was inspired by </em><a href="http://holacracy.org/"><em>Holacracy</em></a><em>, which is a system for distributing decision-making inside organizations.</em></p><p><em>I work at Pivotal Labs. We are currently hiring product managers for all of our offices. If you’d like to learn more go to </em><a href="http://pivotallabs.com/careers/"><em>http://pivotallabs.com/careers/</em></a><em> or ping me @jbeltowska.</em></p><p>This story was <a href="http://pivotallabs.com/6-decision-making-techniques-product-managers-know/">originally published</a> on the Pivotal Labs blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=429fe4d13654" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/6-decision-making-techniques-all-product-managers-should-know-429fe4d13654">6 decision-making techniques all Product Managers should know</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Strategist: You Have To Earn That Title]]></title>
            <link>https://medium.com/@jbeltowska/strategist-you-have-to-earn-that-title-2e7fd5e9a094?source=rss-dbc1d16a19f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e7fd5e9a094</guid>
            <dc:creator><![CDATA[Joanna Beltowska]]></dc:creator>
            <pubDate>Mon, 03 Feb 2014 20:14:26 GMT</pubDate>
            <atom:updated>2014-05-27T21:21:20.834Z</atom:updated>
            <content:encoded><![CDATA[<h4>Because many self-proclaimed strategists aren’t</h4><p>(This was sparked by @sherifsalti’s <a href="https://medium.com/ux-ui-design/4f96aa7fb547">piece</a> about the proliferation of unqualified designers)</p><p>“Digital Strategist” has been one of <em>those</em> titles for a while: it seems to be popping up everywhere, anyone can lay claim to it, and there’s no unified definition of it.</p><p>I’ve worked as a digital strategy consultant for the past 4 years. Here are a few clues I look for to tell me if someone has strategist DNA.</p><p><strong>You understand what strategy is</strong></p><p>Strategy is not planning. It is not tactics. It is the practice of figuring out <a href="https://medium.com/on-management/79d9a039f5dc">how to get from point A to point B</a>. Digital strategy is not social media, it’s not making websites/apps/banners, and it’s not IT. It’s <em>the practice of figuring out how to get from point A to point B</em> — because digital is ubiquitous by now, digital strategy is just strategy. It’s about identifying and realizing opportunities for digital technology to create competitive advantage, sometimes going as far as <a href="https://medium.com/on-management/f19160f61500">transforming organizations</a> from the inside out.</p><p><strong>You are a systems thinker</strong></p><p>A strategist can see the big picture.</p><p>A strategist can identify the parts of a larger system, and how those parts should work together, to make a strategy successful.</p><p>A strategist can identify where to apply force in a system for impact.</p><p>A strategist understands that feedback loops are important, and knows how to find them or otherwise incorporate them into their work.</p><p><strong>You’ve been in the trenches</strong></p><p>You can only evaluate the success of a strategy if you execute said strategy; thus, a strategist has been through the process of identifying, articulating, selling through, realizing and evaluating a strategy at least once, <em>with measurable outcomes that align with or surpass the strategic objectives</em>.</p><blockquote>Comments? Feedback? Add your note here!</blockquote><p><strong>Thanks</strong> to <a href="https://medium.com/@dbbradle">Derrick Bradley</a>, <a href="https://twitter.com/tokyohanna">Johanna Beyenbach</a> and <a href="https://medium.com/@mikearauz">Mike Arauz</a> for reading drafts of this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e7fd5e9a094" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>