<?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 Jori Bell on Medium]]></title>
        <description><![CDATA[Stories by Jori Bell on Medium]]></description>
        <link>https://medium.com/@jobe1130?source=rss-1b2ba126c4af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DPX9LEltVburVUZc.jpeg</url>
            <title>Stories by Jori Bell on Medium</title>
            <link>https://medium.com/@jobe1130?source=rss-1b2ba126c4af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:30:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jobe1130/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[The Happiest Place on the Internet]]></title>
            <link>https://medium.com/@jobe1130/the-happiest-place-on-the-internet-263dc32bb46e?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/263dc32bb46e</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[internet]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Fri, 25 Aug 2023 13:06:21 GMT</pubDate>
            <atom:updated>2023-10-02T16:16:19.930Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*svDBhQr2ELd_MGqKFGDgpA.png" /></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>Five months ago, in the middle of a networking binge, I cold emailed <a href="https://www.linkedin.com/in/connieliu95/">Connie Liu</a>. I was taking many calls at the time, but there was a distinctive difference in our 30 minutes spent together. Our connection was instant and the conversation left me glowing. Though, I imagine that many people leave conversations with Connie feeling that way.</p><p>When riffing on product ideas for her company <a href="https://www.trytandem.com/">Tandem</a>, I shared that I was yearning for a place to connect with other coaches. I was seeking a space to ask dumb questions and learn from others with years (perhaps decades) of experience.</p><p>Connie met the moment, quickly spinning up Coaching Corner — a slack channel —<a href="https://www.jointheogc.com/"> inspired by another slack community</a> we’ve both grown to love. We each invited coaches we knew to help bring the space to life. And now, only a few months in, we have a small, engaged member base filled with coaches. The group represents a mix of industries, locations and specialities. We’ve self organized rapidly, probably because many of us come from tech (many former product managers and builders!). And within these few months, it’s come to be a space I absolutely cherish. Some highlights from my time in the Coaching Corner (with Connie) #alliteration:</p><ul><li><strong>Accountability</strong>: A group of us meet on Mondays to set intentions for the week. Many of us are still setting up rituals as soloprenuers. Holding weekly space and creating a sense of group accountability, in an intimate setting, has been incredibly grounding.</li><li><strong>Training</strong>: Nine of us signed up to participate in Shirzad Chamine’s <a href="https://www.positiveintelligence.com/100x-g/?utm_matchtype=p&amp;ad_id=585674495487&amp;utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=Brand&amp;utm_content=Positive_Intelligence_for_Coaches&amp;utm_term=pq%20coaching%20grant%20program&amp;hsa_acc=2889677219&amp;hsa_cam=14383207148&amp;hsa_grp=129253712867&amp;hsa_ad=585674495487&amp;hsa_src=g&amp;hsa_tgt=kwd-2088887278229&amp;hsa_kw=pq%20coaching%20grant%20program&amp;hsa_mt=p&amp;hsa_net=adwords&amp;hsa_ver=3&amp;gad=1&amp;gclid=Cj0KCQjw_5unBhCMARIsACZyzS3Gg-Qeb5jdVHOeSeYjKjbJi4jVbAcp4RjHtPWBUOSeFwh9M6CpYb4aAqczEALw_wcB">Positive Intelligence program</a>. The program — and the collective group participation — helped me in more ways that I could have imagined. There’s new language, habits, frameworks, etc. Plus, learning is always much more enjoyable in a group.</li><li><strong>IRL</strong>: Our group spans coasts, and continents, but so far I’ve had the pleasure of bringing a handful of online connections to life. A walk through my neighborhood with Kelly and a long coffee with Annie drew me closer into the community quicker.</li><li><strong>Knowledge</strong>: Our varying degrees of experience gives us a peer group that you can’t get in certification programs. The tenured coaches meet the new coaches without judgement. The new coaches show up with gratitude and respect. There’s a kindness culture. We push each other to hit publish on dangling drafts and we celebrate wins, because running your own business can be lonely.</li></ul><p>Coaching Corner is kind of the opposite of what you think of when you think about “meeting people on the internet.” It’s a safe, inspirational, warm kind of space to be. And it’s my happiest place on the internet.</p><p>&gt; Are you a coach looking for community?</p><p>&gt; Do you know any coaches that might benefit from community?</p><p><a href="https://docs.google.com/forms/d/e/1FAIpQLSd1piDBQpbYH-OEO8H4pM4H-EkxbpJLbK_9hCgjlDzlkUuQcQ/viewform">We’ve love to bring you into the fold</a> ❤</p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=263dc32bb46e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Experimentation to Launch a Career Pivot]]></title>
            <link>https://medium.com/@jobe1130/using-experimentation-to-launch-a-career-pivot-9ea95cd675df?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ea95cd675df</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Fri, 04 Aug 2023 18:43:06 GMT</pubDate>
            <atom:updated>2023-10-02T16:15:51.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*flqBWR0OFkQ75kIfuZaerQ.jpeg" /><figcaption>Making experimentation look sexy. (<a href="https://www.tibco.com/blog/2015/11/18/innovation-through-experimentation/">Photo Source</a>)</figcaption></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>This spring, I made a <a href="https://www.linkedin.com/posts/jori-bell-b5287317_after-12-years-as-a-product-manager-im-activity-7089239528724406273-hfT9?utm_source=share&amp;utm_medium=member_desktop">big</a> career transition. I resigned from my role as Director of Product Management — giving up the compensation and stability that I worked a decade to earn — to begin a solo venture in <a href="http://www.joribell.com/">product coaching &amp; consulting.</a> For this transition, there was no clear map. Instead, I forged my own path by leaning on a series of experiments to uncover opportunities and mitigate risk incrementally. Driven by my entrepreneurial spirit and armed with my project management tool of choice (<a href="http://trello.com/">#teamtrello</a>), I became the customer in order to find out what lay on the other side of corporate life. <em>Yes, the product manager ‘product managed’ herself. </em><strong>Here’s how I did it… ↗️</strong></p><p>I spent the last 12 years climbing the career ladder as a product manager in tech. In that time, I reaped huge rewards: I launched groundbreaking B2C products while collaborating with some of the smartest brains in the industry. I experienced the perks that tech had to offer when growth felt endless. I was incredibly lucky.</p><p>But, like many others, I increasingly found <a href="https://www.nytimes.com/interactive/2023/01/23/magazine/cal-newport-interview.html">the digital workplace bringing me down</a>. Working remote over the past 3+ years, I spent more time drowning in emails, stuck on zoom calls and fielding slack messages. I had zero left in the tank at the end of each day. I sought support in a <a href="https://womenpm.org/programs/">peer coaching circle</a> and with dozens of product people online. <strong>Here’s what I learned… ↗️</strong></p><p>Through connecting with folks I met online, I learned a lot about myself and what was possible:</p><ul><li>Through the peer coaching circle and mentoring I provided other product managers, I learned I loved helping other people solve their career challenges. I felt most energized empowering others to beat their blockers and gain confidence in their professional and personal lives.</li><li>Through my interviews with dozens of product people, I discovered alternative career paths. I saw that professional fulfillment wasn’t just a far fetched millennial cliche, but a possibility so many around me were already living.</li><li>I realized virtual networking wasn’t so hard once you got the hang of it. I made internet friends. Some internet friends became IRL friends.</li></ul><p><strong>Here’s where I did about it… ↗️</strong></p><p>So I did the product thing: I created a vision, an experimentation plan and OKRs to go with it.</p><p>Those who know me say that entrepreneurship is in my blood. I’ve been ideating businesses since the ripe age of 10 (notably a travel agency, a restaurant, a clothing swap service BEFORE Rent the Runway was a thing — <em>yes, I was a true innovator</em>). But, I’ve never bet on myself in a real way. Though I’ve been ambitious in my own career as an employee, I remained a “<a href="https://medium.com/@kya.nguyen/are-you-a-shadow-artist-too-how-finding-art-helped-me-to-heal-8ab84a67e641#:~:text=In%20the%20best%2Dselling%20book,believe%20that%20they%20are%20artists.">shadow artist</a>.”</p><p>So, I started coming out of the shadows. I used cheap, rapid experimentation to learn and move quickly. And just like that, I product managed myself out of the doldrums. <strong>Here’s how I tested… ↗️</strong></p><h4>Experiments I Ran</h4><p><strong>(1) The Question — Should I stay or should I go? </strong>I’ve only ever known corporate life. It wasn’t anything I ever questioned until it started bringing me down in ways that were all consuming. Because the days were a blur, I couldn’t reliably piece together how and when to step away. Product Leader <a href="https://www.linkedin.com/in/hazel-chi-0167a21b/">Hazel Chi</a>, inspired me to conduct a simple exercise. It involved running a quantitative experiment on myself to make sense of my qualitative emotions. 🎢</p><p><strong>Method: </strong>For a month, I rated my days (terrible, ok, great ← <em>super scientific, right?</em>) If I had the energy for it, I would add details. The details identified patterns and I easily saw what energized me, what depleted me, how who I spoke to and how I spent my time had a profound impact on my rating.</p><p><strong>Results</strong>: Using this exercise helped me quantify my struggle and paint a more accurate picture of my experience. It was a practical, reliable tool when emotions ran high. And in the end, it helped me see that a departure from corporate life wasn’t possible but necessary (for now).</p><p><strong>(2) The Question — Should I coach other product managers? </strong>Following my participation in the <a href="https://womenpm.org/programs/">peer coaching circle</a>, I set out to learn why I liked it so much and what value I brought to others. I took my talents outside of the circle and started mentoring other product managers. 🏀</p><p><strong>Method</strong>: I plugged into a handful of mentoring networks (<a href="https://www.get-merit.com/">Merit</a>, <a href="http://adplist.org/">ADPlist.org</a> to name a few) and offered my support to dozens of product managers around the world. While my tactical product experience was the hook, it was my empathy and relatability that made these sessions successful.</p><p><strong>Results</strong>: I didn’t take on mentoring to become a coach. I mentored other product people because it felt good. But once I started mentoring, I uncovered a new path. The sessions taught me where people needed help and where I was able to offer the best support. My consistency gave me clarity on my value prop. And the sessions gave me confidence to move from mentorship (free) to coaching (paid) rapidly. Without experimentation, tweaking my approach, my language, my tools, I wouldn’t have moved into coaching as quickly as I did.</p><p><strong>(3) The Question — Should I create a website? </strong>When I was finally ready to bring on paying clients to coach, I immediately concerned myself with branding and packaging. Amid the incredible competition out there, I struggled with how to represent myself. My identity was a product manager and now, I was calling myself a coach. Imposter syndrome at its finest. 👹</p><p><strong>The Method</strong>: It was on my networking journey in conversation with<a href="https://www.wynnproductconsulting.com/"> Rachel Wynn</a>, a product leader and consultant, that I remembered to start with an MVP. Rachel reeled me in and suggested creating a google doc. Soon, others (many in <a href="https://www.jointheogc.com/">The Old Girl’s Club</a>) reinforced the concept of a 1-sheeter as the next step. So, I made a google doc with my offerings, my rates and an about me section.</p><p><strong>The Result</strong>: It wasn’t perfect, but the 1-sheeter combined with my LinkedIn got the job done. It saved me time and got me going sooner than I would have if I focused on building a website from the start (plot twist: I eventually built a<a href="http://joribell.com/"> website</a>). It was here that I harnessed one of my <a href="https://www.linkedin.com/in/suttonkauss/">best friend’s</a> mantras: <strong>a right next step</strong>. It’s tempting to figure out the big picture from the start. But the reality is, its usually wrong. Now, I reel <em>myself</em> in and focus less on the end goal and more on what a right next step is. Needless to say, getting things done has gotten a lot easier.</p><p><strong>(4) The Question — How should I sell sessions? </strong>Charging people for coaching was a scary process. I’ve done my share of willingness to pay research in product roles but never for myself. Most of all, asking people to pay was straight up uncomfortable. So I tried a lot of different things. 🤑</p><p><strong>Method: </strong>I A/B tested different packages, price points, and language. At one point, I was redoing my rate sheets on a daily basis. Through all of these tests, I learned to communicate my own value as a product coach.</p><p><strong>Results</strong>: I learned what worked well for some worked terribly for others. I pitched too high and lost some potential clients. I lowballed when there was room to go bigger. Similar to booking travel, dynamic pricing options and models seemed to be key, especially in a rapidly changing economy when people’s elasticity is in constant flux. Similar to the website debacle, if I worried about nailing pricing from the get go, I wouldn’t have worked with as many coachees as I have today.</p><p>Though I’ve taken the leap, I’m still actively experimenting to learn more about how I can improve my approach, my offering and myself. Aside from experimentation, I lean heavily into conducting my own customer research, collecting data to continuously learn and improve. Best of all, I found using rapid experimentation wasn’t only effective, it was just straight up fun. I guess it’s what made me fall in love with product management in the first place. I look forward to experimenting even more in the future and sharing more about my results here in the coming months. And last but not least…</p><h4><strong>1) A shameless plug</strong></h4><p>Are you looking for product support? Do you know someone who might benefit from coaching? <a href="https://www.joribell.com/contact">I’d love to connect! </a><em>(Yes, you saw this one coming) (I also have some limited availability for product consulting!)</em></p><h4>2) A list of related reading on experimentation</h4><ul><li><a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/150112174X/ref=asc_df_150112174X/?tag=hyprod-20&amp;linkCode=df0&amp;hvadid=266094129756&amp;hvpos=&amp;hvnetw=g&amp;hvrand=13053836160537045402&amp;hvpone=&amp;hvptwo=&amp;hvqmt=&amp;hvdev=c&amp;hvdvcmdl=&amp;hvlocint=&amp;hvlocphy=9004338&amp;hvtargid=pla-436091533585&amp;psc=1"><strong>Sprint: How to Solve Big Problems and Test New Ideas in Five Days</strong></a><strong> </strong>— Jake Knapp (my experimentation bible!)</li><li><a href="https://open.substack.com/pub/kellyhliu/p/the-experimental-mindset?r=4yrbz&amp;utm_campaign=post&amp;utm_medium=web"><strong>The experimental mindset</strong></a> — Kelly Liu</li><li><a href="https://www.michaellinwrites.com/p/what-would-you-do-if-you-had-to-start?utm_source=substack&amp;utm_medium=email"><strong>What Would You Do If You Had To Start a Career Coaching Business? </strong></a>— Michael Lin</li></ul><h4><strong>3) A Thank You</strong></h4><p>Thank you to the long list of product people who inspired me to take this next step. Time is money and your time means everything to me. I’m looking forward to paying<em> </em>it forward.</p><p>And a special thank you to all my mentees. Without you, I certainly would not be on this path today.</p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ea95cd675df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#23WIP — Musings from the Annual Women in Product Conference]]></title>
            <link>https://medium.com/@jobe1130/23wip-musings-from-the-annual-women-in-product-conference-24ad28446f9?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/24ad28446f9</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Thu, 11 May 2023 12:26:01 GMT</pubDate>
            <atom:updated>2023-10-02T16:15:12.374Z</atom:updated>
            <content:encoded><![CDATA[<h3>#23WIP — Musings from the Annual Women in Product Conference</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vFEyH0bF4mMA5LaGr4AOFA.png" /></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>As I noted <a href="https://www.linkedin.com/posts/jori-bell-b5287317_episode-41-networking-your-way-activity-7057352271977705472-pF_8?utm_source=share&amp;utm_medium=member_desktop">recently</a>, The <a href="https://www.linkedin.com/company/women-in-product/">Women In Product</a> group — with its extraordinary community and resources — has been instrumental in my career development. From local mixers, to executive coaching, I’ve always had a reliable community of women in my field to collaborate with.</p><p>I’ve been fortunate to attend two annual conferences — virtual and in-person — and they’ve always been overwhelming, in the good kind of way. Name a thought leader, a helpful peer, a company you’ve wanted to connect with — she’s there.</p><p>Before this year’s conference, <a href="https://open.spotify.com/episode/4T7c31Vd40QsIQ5SPWBG4M?si=1b8ea068f53140b2">I spoke with Arianna Black about networking </a>— what it means in today’s world and how to network smarter in a virtual setting. I surprised myself with how much I had to say on the topic. Maybe because I’ve leaned into networking more intentionally over the past six months. And even more, its been an energizing experience for me to do so.</p><p>The Women in Product conference is the ultimate way to exercise your networking muscle. So, I did just that. Here were some of my musings &amp; highlights from this year’s #23WIP conference.</p><h3>Musings</h3><h4><strong>From </strong><a href="https://www.linkedin.com/in/amvora/"><strong>Ami Vora</strong></a><strong>, Chief Product Officer at Faire</strong></h4><p>During the first day’s keynote, Ami spoke vulnerably about her career trajectory. I especially loved her reframe of “what a failure” to “what an experiment.” I’ve personally tried to adopt this language as well. The word fail, despite our best efforts and slogan creation (i.e. fail fast), carries a negative connotation. Ami spoke about using failures, or experiments, as key data gathering moments throughout her own career development. As PMs, we can’t and shouldn’t expect every product to work. In fact, we have an incredibly high failure rate. So let’s take Ami’s suggestion and rebrand failure into experimentation to achieve a healthier growth mindset.</p><h4><strong>From </strong><a href="https://www.linkedin.com/in/trisha-price-3063081/"><strong>Trisha Price</strong></a><strong>, Chief Product Officer at Pendo.io</strong></h4><p>Trisha reinforced the well known adage that the best ideas and results come from a diverse group. She encouraged us to surround ourselves with different types of people because “innovation doesn’t happen in a room where everyone is nodding their heads yes.” We learn a lot about this from a company standpoint, but my mind actually went to the networking component. I’m constantly seeking validation from people who look and sound just like me. Trisha served as an important reminder to seek out the opinions and ideas of others during my networking adventures.</p><h4><strong>From </strong><a href="https://www.linkedin.com/in/kimberlylucioblight/"><strong>Kim Blight</strong></a><strong>, Director of Product Ops at ActiveCampaign</strong></h4><p>I got the chance to pop into a great discussion around horizontal movement, led by Kim Blight. <a href="https://medium.com/u/e93bb14d2a10">Kimberly Lucio Blight</a> shared her story about seeing and creating opportunities for herself, even when they don’t exist. The group ideated on using job descriptions as a helpful means of doing this. Kim also told the group, looking back on her career that “my future depends on me, this is all on me.” I deeply related to this aha! moment Kim shared. Whether in my own experience or in coaching other PMs, I find that the biggest blocker to change is ourselves. Our career development <em>is</em> only on us. Once I internalized this, I gained tremendous power in knowing that me, myself and I had the power to shape my own destiny.</p><p><strong>From </strong><a href="https://www.linkedin.com/in/phylterry/"><strong>Phyl Terry</strong></a><strong>, Author &amp; </strong><a href="https://www.linkedin.com/in/allisonmnookin/"><strong>Allison Mnookin</strong></a><strong>, Director at HBS</strong></p><p>Aside from the energy these two brought to a remote, pre-recorded virtual conference (HARD TO DO!), I was shocked I had never encountered their phenomenal resource “<a href="https://www.phyl.org/">Never Search Alone</a>.” Tools like the <strong>Job Search Council</strong> and the <strong>Mnookin 2-pager</strong> are free resources that I wish I found sooner. I loved and deeply related to <a href="https://medium.com/u/88ce23859904">Phil Terry</a>’s advice on going after the work you love rather than the title you want. I cannot wait to dive into and recommend their work to folks I’m coaching.</p><h3>The Last Word</h3><p>As mentioned on the <a href="https://open.spotify.com/episode/4T7c31Vd40QsIQ5SPWBG4M?si=bc94348f84154ac3&amp;nd=1">WIP podcast</a> I noted above, I am offering product coaching! If you or someone you know might be interested please send them <a href="https://forms.gle/xyoYN2eE1f52J6tAA">this way. </a>I’m excited at the prospect of working together!</p><p>Happy conferencing!</p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24ad28446f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding the right support as a new product manager.]]></title>
            <link>https://medium.com/@jobe1130/finding-the-right-support-as-a-new-product-manager-326aa2d4faca?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/326aa2d4faca</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[career-change]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Sun, 13 Nov 2022 21:20:01 GMT</pubDate>
            <atom:updated>2023-10-02T16:14:47.695Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*2H9B3JjYvoxG08LjkW8aSw.gif" /></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>This Fall, I connected with a handful of new product managers. The common pain point was clear: it’s really hard for new product managers to find the right support. Starting as a new product manager is uniquely hard because product is practiced differently company to company. This results in differing <a href="https://medium.com/@jobe1130/i-fell-into-product-management-9975a31290cf">starting points</a>, varying expectations, unexpected reporting lines, etc. Because product roles are riddled with more ambiguity than roles like engineering or design, it can be harder to find steady ground early on.</p><p>Whether I’ve been new to product management or new to a company, various kinds of support helped me during the always rocky transition as the new person. While there are no silver bullets, these tools will undoubtedly help you find footing quickly as a new product person.</p><h4>Support yourself with customer data</h4><p>A product manager is a lot of things. But, fundamentally a product manager is the voice of the customer. A good product manager champions a customer’s problems. A great product manager understands the root cause of the problem and backs it with data. Needless to say, the customer is always a sound place for a new product manager to start.</p><p>Data come from many places. Sometimes from a data science team and fancy dashboards to develop deep quantitative insights. More often though, insights come from customer support or sales teams where rich qualitative data resides. Scrappier DIY data might emerge from online forums like Reddit or Discord. Or direct emails to customers. Regardless of the source, there’s a good chance that your data will be imperfect. Good news is, you don’t need perfect data, you just need directional data. Armed with customer data, you can represent the customer quite quickly as the new product manager.</p><p>Diving deep into whatever customer data you have available will ground you in your work and help inform decisions, big and small, in the first few months of your new role.</p><h4>Surround yourself with a cross-functional team</h4><p>I am fortunate enough to have worked in the “squad” setup, <a href="https://www.chameleon.io/blog/spotify-squads#:~:text=and%20terminology%20optional.-,What%20is%20the%20Spotify%20Squad%20framework%3F,responsibility%20for%20any%20product%20built.">pioneered at Spotify</a> but adopted by many companies. This is the trifecta leadership model of design, tech, product, walking hand in hand to build a product with impact. This setup is good for many reasons, which you can read about in the link above. Personally, I’ve found this setup best because it maximizes productivity and boosts creative thinking. The hard reality is that most companies aren’t staffed or organized to enact this setup. So what do you do when you can’t get that squad model? Hack it!</p><p>As a new product manager, find ways to involve engineering and design early and often. While there might be challenges — i.e. outsourced engineers, a leader who doesn’t agree with this model or resource constraints — cross-functional teams are a vision worth fighting for.</p><p>There’s a common stereotype that product managers are the great visionaries of the development team. That their solutions are the ones to implement. While some product managers <em>are</em> visionaries, they rarely have the right solutions. I love getting my ideas challenged by leaner, strategic ideas that come from other team members, from design to QA. While it’s a product manager’s job to know the customer’s problem, it is <em>not</em> only their job to have the solution to their problem. Great ideas aren’t born in a silo and it should never be on a product manager to go at it alone. Solving customer problems requires collaboration with stakeholders with different skillsets and perspectives. The product manager brings these various stakeholders together, manages the trade offs and comes up with the best solution based on all the information known at the time.</p><p>The best product managers rally cross-functional teams around customer problems. They get the right people in the room* to evaluate and solve a problem collaboratively. Solutions built by a team are always stronger than the ones you dream up on your own.</p><p><em>*Ever gotten pushback on including engineering in an early discovery meeting? Try some of these </em><a href="https://medium.com/@jobe1130/the-art-of-an-inexpensive-meeting-9018b58e0feb"><em>tips</em></a><em> to running inexpensive, effective meetings.</em></p><h4>Supplement with a mentor</h4><p>In talking to new product managers, especially at smaller companies, a common issue is that they don’t report into other product managers. This leaves many new product managers without the direct apprenticeship they need to get their footing.</p><p>First, explore working more closely with adjacent functions, like design or tech leaders. Be open minded — many non product managers are often product-minded people. Incorporate these mentors into your rituals, meeting with them often to get the product support you’re lacking from your product manager manager.</p><p>Second, explore general mentorship outside your own line of management, and perhaps outside your company. Getting an “outside” perspective to the work you do can be illuminating and powerful. This of course is easier said than done, but the flip side is that it’s never been easier to find a mentor*.</p><p><em>*I’ve begun early stage product management mentoring— </em><a href="https://forms.gle/nyrrJqu8Ft8Cq6TD8"><em>click here</em></a><em>*</em></p><h4>Sketch a career vision</h4><p>Whether you’re brand new to product management or a seasoned product manager, we all need a career vision. Driving your own development, outside of mandated performance reviews helps you think bigger than the six month or annual time frames we’re accustomed to. These visions give you focus, which can empower you with clarity on day-to-day decisions.</p><p>A simple framework comes in really handy here. I like filling out something like this on my own, or perhaps with a mentor to establish a loose vision of where I’m heading. More times than not, my vision is imprecise and needs regular tweaking. Which is ok. But like a compass, it’s directional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*aL6Y5D3U2X2s0RwWcqvJ6Q.png" /></figure><p>I have nothing revolutionary to offer here other than a probe: This is your sign to take 5 minutes today and chart out some simple goals. Zoom out and think about where you want to be and what you want to accomplish. Like a product roadmap, your vision shouldn’t be filled with deliverables, but rather, experiments, research and small steps that drive towards your goals.</p><p>Product management is non-linear and non-uniform. Take some small steps to set yourself up for success as you learn how to do this product thing.</p><p>–</p><p><em>I’d love to hear what has worked for you as a new product manager. And a reminder in case you missed it, I am offering limited mentorship right now. If you’re interested or know someone who might be, send them </em><a href="https://forms.gle/nyrrJqu8Ft8Cq6TD8"><em>here</em></a><em>.</em></p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=326aa2d4faca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The art of an inexpensive meeting]]></title>
            <link>https://medium.com/@jobe1130/the-art-of-an-inexpensive-meeting-9018b58e0feb?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/9018b58e0feb</guid>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[efficiency]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Thu, 10 Nov 2022 19:00:26 GMT</pubDate>
            <atom:updated>2023-10-02T16:14:19.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*p1Y3a3SeCgtWgSlumVw58g@2x.jpeg" /><figcaption>Really my ideal kind of meeting. Source: <a href="https://www.inprnt.com/gallery/brontosaurus/a-very-important-meeting/">Inprnt</a></figcaption></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>As someone who spends at least 50% of their time in meetings, I feel quite passionately about making them worthwhile. Since I strongly believe in bringing cross-functional teams together early and often, I need to be intentional with my preparation and execution. I don’t agree with a lot of Elon’s strategies these days, but this one speaks to me:</p><blockquote><strong>“Walk out of a meeting or drop off a call as soon as it is obvious you aren’t adding value.</strong> <strong>It is not rude to leave, it is rude to make someone stay and waste their time.” — </strong><a href="https://www.inc.com/nicholas-sonnenberg/in-just-4-sentences-elon-musk-gave-tesla-employees-a-masterclass-on-how-to-run-efficient-meetings.html#:~:text=%22Walk%20out%20of%20a%20meeting,stay%20and%20waste%20their%20time.%22"><strong>Elon Musk, Inc.</strong></a></blockquote><p>While meeting etiquette may feel obvious, here are some of my top tricks to implementing quality meetings.</p><h4>Pre meeting</h4><p>In your invite clearly…</p><p><strong>(1) State the goal / meeting type</strong></p><p>By the time your meeting ends, what do you hope to achieve? Be clear about what people are coming together to do and where you hope to be by the end. Keep your goals appropriate to the time you have booked. Don’t try and solve world hunger in a 30 minute meeting, if you catch my drift.</p><p><strong>(2) Include an Agenda</strong></p><p>Be detailed about how you aim to get to your goal with an agenda. I’ll be honest, I look down upon and at times, decline agenda-less meetings. Show your team how you’ll guide them to their goal. And encourage others to add pressing topics to the agenda that might be crucial for this group to discuss.</p><p><strong>(3) Include a Pre-Read</strong></p><p>Documentation is king. Whenever you can, take a few minutes to put your goals and agenda in a doc with any additional context that’s important for the group to read through to have a meaningful discussion. At a minimum, give folks a 3-sentence overview of the background.</p><p><strong>(4) Invite all the right people</strong></p><p>Getting the right people in the room is 70% of the battle. Having shared your goals and agenda, encourage invitees to forward the meeting invite if there are other coworkers important to your meeting. The more the merrier model works <em>if </em>you have an agenda.</p><h4>During meeting</h4><p><strong>(5) Make it human</strong></p><p>Connect with your meeting attendees on a human level before you begin. Skip the lengthy ice breaker and promote inclusivity in simpler ways: turn your camera on, give people bio breaks, make space for quieter folks. Don’t be a robot.</p><p><strong>(6) Give people context</strong></p><p>Allow attendees time at the top of the meeting to review the pre-read materials and drop in additional agenda items. Like you, attendees are most likely context switching from another meeting. Give them space to reorient.</p><p><strong>(7) Delegate for rotational help</strong></p><p>Ask for help: ensure there’s someone taking notes, someone monitoring the chat (which is always lit in WFH days) and someone keeping time to ensure that you are moving through the agenda. The meeting leader cannot be expected to juggle it all. You are only human.</p><p><strong>(8) Call it if it’s not working</strong></p><p>This is one of my favorite things to do: If you don’t have the right info or people in the meeting, don’t be scared to end it early! Don’t waste people’s time because you have the time blocked. Plus, everyone loves time back.</p><p><strong>(9) Outline next steps/action items</strong></p><p>Ensure you leave the meeting knowing what happened and what’s next. The best way I’ve found to implement accountability is to assign action items. Nothing moves people to action like being assigned a task :)</p><h4>Post meeting</h4><p><strong>(10) Send out notes and action items</strong></p><p>Someone wasn’t paying attention. Someone wasn’t even there. Send out the next steps/action items to bookend the meeting with clarity in a follow up meeting. Let people know if you’ve achieved your goal or not.</p><p>Were these obvious tips? Or were they totally new? I’ve found these tips work in meetings well beyond my professional sphere. I’d love to hear how you drive efficient meetings in your organization and in your personal life. I love an agenda and I love an efficient meeting.</p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9018b58e0feb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The concepts (not code) I know to work effectively with Engineers.]]></title>
            <link>https://medium.com/@jobe1130/the-concepts-not-code-i-know-to-work-effectively-with-engineers-59ce57ea84a4?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/59ce57ea84a4</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Thu, 02 Jun 2022 13:51:33 GMT</pubDate>
            <atom:updated>2023-10-02T16:13:49.086Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I engage with Engineering teams as a Product Manager who doesn’t know how to code.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lxg2VY3t0S-FmCLYYzMECQ.png" /></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>The Product School <a href="https://medium.com/@jobe1130/im-not-a-technical-product-manager-18e787074754">talk </a>I shared recently, from years ago, still resonates with so many folks to this day. I’ve wondered why this talk hits home for many. Qualitatively, I think it’s because those <a href="https://medium.com/@jobe1130/i-fell-into-product-management-9975a31290cf">transitioning into Product Management</a> view technical skills as a blocker. Code <em>is</em> another language and working with people who speak another language can be intimidating.</p><p>In my talk years ago, I I highlighted that Product Managers need to know “enough” to work with engineers. Today, that guidance feels really abstract. In this post, I’ll break this down further to make my thoughts more applicable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hueZ5sd8savQoAwCIjhOeQ.png" /><figcaption>A slide from the talk I gave years ago, <a href="https://www.youtube.com/watch?v=8eev-eI0yFk">“How to Succeed as a Non-Technical Product Manager.”</a></figcaption></figure><p>So what does knowing “<em>enough</em>” mean?</p><h4>Concepts Not Code</h4><p>In my presentation, I used the word “concepts” which is a comically vague. Let’s break that down further.</p><p><strong>Getting Started — What you need month one:</strong></p><ul><li><strong>System Design &amp; Architecture</strong>: This is the technology stack that powers the products you build. It’s important to know the interrelatedness of systems, how they’re powered, what’s homegrown and outsourced and generally how stable they are. I find making yourself a visual here to be extremely useful. Find your <a href="https://medium.com/@jobe1130/trust-me-im-a-product-manager-3981b6cd8946">Tom</a> and make sure to understand the basics of the tech stack you’ll build atop of.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0lAZG_Om-9sm-6OBfYS_Ew.png" /><figcaption>This is a very old, simplified tech visual I created for myself to understand how we were serving Ads at SoundCloud. This is mine and doesn’t reflect what the company does today to serve ads.</figcaption></figure><ul><li><strong>Engineering Roles</strong>: It’s important to understand how and what different engineers do. A Front End (FE) engineer’s skillset can look different than a Back End (BE) engineer, which is different from a QA engineer or a Data engineer. Knowing some of the key differences between engineering roles will be helpful in planning conversations. Partner with your Engineering Manager to make sure you understand the composition of your team.</li></ul><p><strong>Day to Day</strong></p><p>Below are some key engineering concepts I think about when I discuss product development with engineering teams:</p><ul><li><strong>Feasibility</strong>: Before we decide to build a feature, we scope out a project to determine what is possible to build. Engineers are going to be the experts here, but conceptually, it’s helpful for you as the Product Manager to know which problems are costly to solve. This usually comes in the form of sizing…</li><li><strong>Sizing</strong>: Engineering teams size work to understand how complex a feature is to build. Sizing is an art form. You may not know how, nor should you know how to size work properly, but if you attend grooming and planning sessions, you’ll start to learn which work is trivial and which is costly. The more you understand this, the more you’ll be able to advocate for your team and in turn, plan better. If you understand team velocity (i.e. efficiency), you’ll better budget towards working deadlines.</li><li><strong>One Way vs. Two Way Doors</strong>: We used this concept at Spotify a lot, especially in the latter half of my tenure, and I loved it. It’s important, as your engineers make foundational decisions, to know which solutions are reversible and which aren’t. Having a good grasp on these decisions will help you manage and communicate tradeoffs to your stakeholders.</li><li><strong>Reusable Tech</strong>: As I noted above, it’s incredibly helpful to understand systems and architecture. Knowing this helps you learn about how tech may or may not be reusable. You don’t want your teams building many one-off solutions to singular customer problems. Rather, you want to ensure that solutions are flexible and strategic so that you can repurpose and reuse existing technology, whenever possible. Prioritizing scalable tech solutions and embracing automation makes teams efficient. Which leads to my next note on scale…</li><li><strong>Scaleability</strong>: Understanding scale is tightly tied to your product vision. Are you building a tool that scales to many international markets or requires a high volume of simultaneous visits (think streaming!). Knowing which pieces of technology enable or limit your ability to scale is key. In these conversations, it’s helpful to understand what your breaking points are. I tend to ask questions like “At what point does this setup break?” Product health, also known as reliability, will make or break the customer experience. So it can’t be ignored.</li></ul><h4>Ask the Right Questions + Collaborate Smarter</h4><p>I spoke about this in one of my previous <a href="https://medium.com/@jobe1130/trust-me-im-a-product-manager-3981b6cd8946">posts</a> but I’ll dig in a bit more here. Over the years, I’ve learned that most times, bringing engineering into the conversation as early as possible, when we have an unsolved customer problem, results in the best team solutions. In fact, I’ve invited many engineers to listen in on research sessions with real customers. Nothing creates empathy more than when you hear about a problem first hand!</p><p>When I rally a team around a customer problem, I like to bring a set of user stories to a meeting. I do this not as a means of dictating a solution or requirements, but rather, as a place for us to start. More times than not, I’m enlightened by the conversation that ensues and how engineers interpret the customer problem. This kind of discourse leads to the best kinds of solutions.</p><p>After determining a solution collaboratively, I like to lead with a proposed solution. I’ll also include all the other solutions we considered but didn’t move forward with and why. It’s more work upfront , but it’s a great way to show stakeholders and leadership the full scope of your thinking. And it’s also a great way to document decisions for your team when you inevitably forget why you chose a certain path. Because you <em>will</em> forget.</p><h4>Inform Decision Making</h4><p>Much of this I covered above, but it’s another reminder that your job as a Product Manager is not only to define scope, but to defend it. As a Product Manager you sit in between many functions that have competing interests. <strong>The more you understand about the engineering setup and products, the better questions you’ll be able to ask to help you advocate for your plans. </strong>And, the more you engage with engineering to learn the concepts (not the code!) the better you’ll get at writing clear product requirements, sequencing your roadmap, and communicating decisions and tradeoffs to leadership. And, the better your team will function :)</p><p>All-in-all you can be a great Product Manager whether you know how to code or not. In my experience, the more you get to know the tech behind the product, the better product you will build. I’ll leave you with a quote that still resonates with me completely:</p><blockquote><em>“So while it’s good if you have a strong technology understanding, it’s not good to use that knowledge to try and do their (engineer’s) job for them.” — </em><a href="https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers-ebook/dp/B077NRB36N"><em>Inspired</em></a></blockquote><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59ce57ea84a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I fell into Product Management.]]></title>
            <link>https://medium.com/@jobe1130/i-fell-into-product-management-9975a31290cf?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/9975a31290cf</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Mon, 09 May 2022 00:10:30 GMT</pubDate>
            <atom:updated>2023-10-02T20:53:55.870Z</atom:updated>
            <content:encoded><![CDATA[<h4>My path into Product was unconventional. Here’s what I recommend to people trying to break into Product today.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*F-nlSWk1KHOeIm0-1-jbAA.jpeg" /><figcaption>I found this yellow duck on another Medium post about being unconventional. Thanks <a href="https://medium.com/u/53050cfb32a8">Nyla Pirani</a>! I’m the yellow duck.</figcaption></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>These days, the number one question I get professionally is, “How do I break into Product Management?” From my vantage point, there’s not one clear journey to becoming a Product Manager. Product Managers come from all walks of life! But, without a conventional path, many looking to break in don’t know where to start.</p><p>Here, I’ll share my path <em>and</em> some advice I give to those looking to get started.</p><h3>An accidental start.</h3><p>After undergrad, I dreamed of moving to New York City, at all costs. I began my job search in the aftermath of the Great Recession. At best, grads were receiving internship offers. And if they were lucky, they were paid. It was a precarious time.</p><p>I focused my search on what I studied: Journalism and Advertising. After connecting with a recruiter at the Huffington Post, she shuffled me to a different role at AOL, with a higher salary (AOL freshly acquired Huffington Post — and yes I needed all the salary I could get out of school). The job title was simply “Associate Producer.”</p><p>Recruiting phone calls went well, but because I wasn’t local, the team wasn’t interested in moving forward with me (what a time!). So, I covered my travel expenses to fly to NYC for the day to interview, demonstrating my excitement for the role (this day <em>really</em> deserves its own post…). My day trip paid off and I soon found myself with a rare salaried position after graduation.</p><p>In my new role, I reported into a Product Manager. And because of that, I got a daily view into what a Product Manager did. As an entry-level “Producer,” I dabbled in engineering, design, marketing and sales. Essentially apprenticing in Product Management. Quite literally, by accident.</p><p>One day, my manager suggested I too could be a Product Manager. So far, it looked pretty good and fit my budding skillset. With my manager as a mentor, I sought out a path in Product Management.</p><p>While I focused on what I knew how to do (build relationships and write), my manager encouraged me to learn things I didn’t know how to do, like familiarize with engineering concepts and engage with our cross-functional team. On my own, I attended classes at <a href="https://generalassemb.ly/?&amp;topic=&amp;mkt_account_id=1056949875&amp;mkt_campaign_id=688004765&amp;mkt_ad_group_id=34925049026&amp;mkt_device_type=c&amp;mkt_keyword=general%20assembly&amp;mkt_matchtype=e&amp;mkt_placement=&amp;mkt_ad_id=155457987540&amp;mkt_network=g&amp;mkt_target_id=kwd-459322816&amp;mkt_feed_item_id=&amp;utm_source=google&amp;utm_medium=paid-search-bra&amp;utm_campaign=TS:TX:BRA:NYC:BR:GeneralAssembly&amp;utm_content=campus-lead-lander&amp;utm_term=general%20assembly&amp;gclid=Cj0KCQjwsdiTBhD5ARIsAIpW8CJrnCIrilZgFf-wwh0hddOHmDzpPqojApYkwdxTAFRXF2JFXtqkZNwaAkndEALw_wcB">General Assembly</a> and participated in events, like a Fashion Hackathon.</p><p>By the time I left AOL, I had the early makings of a Product career ahead of me. At the time, Product Management, especially in NYC, was still nascent. Product Managers were expected to be technical, and many roles were still Silicon Valley-based. But, the tides were shifting. Besides more roles popping up on the East Coast, Product Management was becoming less technical and more generalist. Companies had an appetite to take on non-technical Product Managers, like me.</p><p>I think a lot about the “hard work vs. luck” question from Guy Raz’s podcast, <a href="https://www.npr.org/series/490248027/how-i-built-this">How I Built This</a>. In my early days, there was a lot of luck. Yet, the opportunity and the path forward was mine to lose — so I like to think the luck, combined with my determination, set me up for success.</p><p>Today, Product Management is more accessible, in many ways. This is so exciting! But, because of my unique path into the field, I find it hard to share a relatable experience of breaking into Product Management today. Despite my experience, I’ve bore witness to others breaking in sucessfully. Below are some thoughts on what I’ve seen work well.</p><h3><strong>Before we begin…</strong></h3><p>…I want to call out the elephant in the room 🐘: I haven’t seen many companies hire Product Managers without any prior Product experience (even entry-level roles). I’m not saying it can’t happen, I’m just saying I’ve never seen it. If an Associate Product Manager role requires 2–3 years of Product experience, where do you get that experience? It’s really a classic chicken and egg.</p><p>It’s not insurmountable, but it’s important to call it out. Now, let’s dive in.</p><h3><strong>More seamless starts</strong></h3><p>I’ve seen a few things work really well as an entry into Product Management. These aren’t accessible paths for everyone, but if you have the chance, take them.</p><h4>Lateral Moves</h4><p>The most successful transitions I’ve witnessed into Product Management happen internally. Anecdotally, I’ve seen lateral moves from roles in <strong>UX Research, Data Science, Business Analysis and Program or Project Management</strong>. These transitions work really well because these roles usually work closely with Product Managers. So, aside from getting a view into the day-to-day responsibilities, there’s a sense of familiarity overall.</p><p>I also believe that lateral moves from customer-centric roles, like <strong>Customer Support and Account Management</strong>, make for great transitions into Product. Product Managers are meant to be customer-driven, so roles that center around the customer tie the transition story together nicely.</p><h4>Associate Product Manager (APM) Programs</h4><p>Rotational APM programs (like <a href="https://apmlist.com/">here</a> &amp; <a href="https://medium.com/agileinsider/product-management-digest-apm-3c2631683139">here</a>) are becoming more common. If you get the chance to enter an APM program, this would be ideal IMO.</p><h3><strong>Playing the long game</strong></h3><p>Here are other ideas I’ve been sharing with future Product Managers.</p><h4>Start in an adjacent roles.</h4><p>To further my point above, starting with customer-centric roles, especially if they fit your skillset, is a great way to get into a tech company that has a strong Product team. <em>This is not a short term play</em>. But, it‘s a tactful way in. Bring your existing skills to adjacent roles, get in, and eventually, transition to Product. Some off the cuff ideas*:</p><ul><li><strong>“I work at an ad agency.”</strong> → You work with clients, i.e. customers! Perhaps a customer support, success or solutions team could be a great fit.</li><li><strong>“I am a teacher.” </strong>→ You think constantly about strategic communication. Perhaps a project or program management role would work for you.</li><li><strong>“I work in consulting.” </strong>→ You handle research and data analysis. Perhaps a research or business analyst role might make sense.</li></ul><p>At it’s core, Product Management is customer-centric. Use your current version of “customer focus” to connect the dots and highlight clear, transferable skills.</p><p><em>*These are obviously over simplifications.</em></p><h4>Get “real world” experience.</h4><p>I always advocate for “real world” experience above everything. There are so many unconventional ways to get “real world” experience as a Product Manager, including but not limited to contracting, volunteering, hackathons, networking events and internships.Of course, it’s a privilege to be able to take on unpaid work. If you don’t have the financial flexibility, prioritize contract work.</p><h4>Market yourself better.</h4><p>Making the case for a career pivot to a future employer is about marketing — the language you use to describe your experience and the way you sell yourself. When matching your current experience to a job description of a different role, look critically at the language used. More often than not, your existing experience meets the job requirements. Don’t get caught in the tech jargon. Let’s walk through an example I grabbed from <a href="https://www.linkedin.com/jobs/view/3060312795/?alternateChannel=search&amp;refId=jencyi8tmRKuwypK4ghHlw%3D%3D&amp;trackingId=tW6nKihYSnWjPowb7zyrYg%3D%3D">one of the first APM job listings</a> I saw on LinkedIn.</p><p>Job Description Says:</p><ul><li><em>“Build and actively manage a product backlog of features and capabilities that are refined and prioritized.” </em><strong>This is strategically managing a task list that maps back to business goals.</strong></li><li><em>“Identify the root cause of platform issues and come up with the approach to resolve for both short and long term.” </em><strong>This is problem-solving.</strong></li><li><em>“Collaborate on release plans and set expectation for delivery of new functionalities.” </em><strong>This is managing timelines and communicating effectively.</strong></li></ul><p>Job descriptions can be loaded and overwhelming. But, they can be really helpful tools if you know how to use them.</p><p>Aside from finding the right language, career pivoting also comes down to how you sell yourself. <strong>If you’re asking someone to consider you for a Product Management role without any Product experience, they are taking a chance on you! </strong>Because there are start-up costs associated with bringing on someone without prior experience, take on some of that responsibility. Vocalize what skills you’re bringing to the table to compensate for your lack of Product skills. This might come in the form of industry experience, adjacent experience, etc. Help build the business case on why you’re worth the risk. In other words, help them, help you.</p><h4>Nice-To-Have: Take a class or get certified.</h4><p>I get lots of questions about certifications. In my experience, certifications don’t make or break candidates. Work experience is priority. That being said, I do believe classes and certifications are great for learning and networking. And, if you can leverage your instructor as a mentor or for advice, get after it!</p><p>Over the past five or so years, MBA → Product Management has become a popular path. I know many people who took this path to get to where they are today (and they are crushing it 💪🏻). But I don’t believe that this is a necessary step to becoming a successful Product Manager. I do believe this is a path for some — for those looking to restart their careers, those more entrepreneurial, those looking to build a strong network in tech, etc.</p><p>A few years ago, surrounded by some badass female Product Managers, all fresh out of MBA programs, I asked myself if I needed a MBA to be successful in Product Management. I determined that the answer for me was no (this decision is deserving of a whole post…) This was a <em>highly</em> personal decision.</p><p>As you can imagine, there’s not one silver bullet into Product Management. There’s lots of winding paths to Product, which is unlike other careers with more clearly defined paths — like engineering, design, etc. Product Management is fuzzier. Hopefully the fuzziness can be advantageous.</p><p>I’d love to hear what your journey has been.</p><p>How did you get into Product? How are you trying to get into Product? What are the hurdles? What’s worked? I’d love to refresh my arsenal of tips and tricks :)</p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9975a31290cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trust me, I’m a Product Manager.]]></title>
            <link>https://medium.com/@jobe1130/trust-me-im-a-product-manager-3981b6cd8946?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/3981b6cd8946</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Fri, 15 Apr 2022 14:03:22 GMT</pubDate>
            <atom:updated>2023-10-02T15:15:47.900Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building and earning trust when you’re brand new to an established engineering team.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ge9ZPPlIK8Vd7uy8QA5kRg.jpeg" /><figcaption>Actual footage of me joining a new team. (<a href="https://homeword.com/jims-blog/tuesday-video-trust-fall-fail/#.Yll7RpPMKqA">Photo credit</a>)</figcaption></figure><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>The week before I started my new role at <a href="https://www.audible.com/">Audible</a> (yay!), a Product Manager reached out to me asking for advice. She asked: <strong>How can I be confident as a new Product Manager when joining an established team?</strong> It was a timely probe for me as I would be doing the same thing, very soon. I have years of product experience but, I would <em>still</em> be starting from square one with a new set of engineers.</p><blockquote>So — what steps could I take as a new Product Manager to build and earn trust with my established engineering team?</blockquote><p>I’ve started at new companies and started with new teams over and over again. Here are some of the tips and tricks I’ve used to help me acclimate quickly to an established engineering team as the incoming Product Manager.</p><h4><strong>1. Ask what engineers need, one on one.</strong></h4><p>Whenever I start a new role, or join a new team, I like to connect with engineers in one on one sessions. I ask questions like…</p><ul><li><em>“What’s working for you?”</em></li><li><em>“What’s not working? What’s your biggest pain point?”</em></li><li><em>“What’s your preferred way of working? Do you prefer email or Slack?”</em></li><li><em>“What’s your history of working with Product Managers?”</em></li><li><em>“How can I, as a Product Manager, make your life easier?”</em></li></ul><p>When I schedule these sessions, many engineers aren’t used to PMs asking these kinds of specific questions. Many, unfortunately, are used to being treated like one big engineering unit.</p><p>I’ve learned after working with <strong>many</strong> engineering teams, that taking the time, as a PM, to understand the individuals on your team, their needs, skillsets and goals, makes all the difference and is, in fact, the anomaly. Starting here establishes you not just as a nice person, but as a PM partner willing to go beyond the basics, to help your team thrive.</p><p>If I’m lucky enough to have a dedicated engineering team, I try to continue these one on one sessions, with a regular cadence. It helps me stay accountable and creates a clear line of communication. This is more important than ever, as most development teams maintain some level of remote collaboration for now, and maybe, forever.</p><p><em>*I’ll also note that this practice isn’t and shouldn’t be limited to engineering &lt;&gt; product relationships. It’s expansible and strategic for PMs to think about their various stakeholders as the customer.</em></p><h4><strong>2. Find your engineering partner.</strong></h4><p>This might be a Senior Engineer, a Junior Engineer or even an Engineering Manager. For me, it was Tom. When I started at SoundCloud, I had never encountered an Ad Server before. Tom took me under his wing and patiently sat with me, white boarding the tech stack . Tom allowed me to ask dumb questions, present back to him what he taught me (my preferred method of learning) and invested in me, because it was an investment in our team.</p><p>Find your person, use your preferred method of learning and spend time asking really dumb questions. It’ll be worth it.</p><p>Tom also taught me to restart my computer when it seemed broken. I do that for others now. Thank you for putting up with me, Tom.</p><h4>3. Lead with vulnerability.</h4><p>Yes, I’m a <a href="https://www.ted.com/talks/brene_brown_the_power_of_vulnerability?language=en">Brene Brown</a> junkie, so I’m always thinking about what it means to connect with others, in deeper ways. Yes you got the job, but, you are not set up to know how the technology, the business or the team works on day one. Own what you don’t know or don’t understand. I promise you’ll look a lot smarter being honest about your knowledge gaps than pretending that you’re an expert.</p><p>This is a <strong>really</strong> uncomfortable, vulnerable practice for many people. But it’s an important way to connect with the members of your team.</p><h4><strong>4. Seek out data and frameworks for prioritization.</strong></h4><p>Who is any PM, from any company, to come into an established engineering team and tell the team “no”<strong>, </strong>change their plans or implement new ways of working? A PM that’s informed on the product and business is who.</p><p>Existing data is your guide. Make friends with your local data scientist and get access to their handy dashboards. <strong>Understanding performance, in relation to OKRs, is going to be one of easiest, unbiased ways to assert your right to say no and weigh in on prioritization conversations.</strong></p><p>Further, understand your product’s standards: What’s considered a bug? What’s considered critical? Seek out existing frameworks. When you can’t find them, develop frameworks (with your engineer friend!) to guide your decision making.</p><p>And when you find yourself forced to make “controversial” decisions, take the time to illustrate your decision making: explain your thinking process, what you’re optimizing for and what else you considered. Make sure it maps back to the goals. The sooner you create transparent frameworks, backed by data, the sooner you’ll start to build real trust with your engineering team (and others too).</p><h4><strong>5. Phone a (PM) friend.</strong></h4><p>Find a PM friend at the company that’s not on your team. Meet with them and ask similar questions that you did to your engineering team. Find a mentor, who’s not your manager, to lean on. Because adjusting to a new role, a new team and a new company takes more time than we think.</p><blockquote>A wise designer told me “It’ll take about six months for you to feel comfortable here,” as I sat slack jawed, fighting to stay awake at my first 9–5.</blockquote><p>Seek out support, early on, and most importantly, be compassionate with yourself as you transition. I’m working on that one too.</p><p>There’s no perfect science to building trust with an established engineering team. But there’s small things you can do to set yourself up for success. Be patient, be humble and ask lots and lots of “dumb” questions.</p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3981b6cd8946" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m not a Technical Product Manager.]]></title>
            <link>https://medium.com/@jobe1130/im-not-a-technical-product-manager-18e787074754?source=rss-1b2ba126c4af------2</link>
            <guid isPermaLink="false">https://medium.com/p/18e787074754</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Jori Bell]]></dc:creator>
            <pubDate>Tue, 05 Apr 2022 15:18:39 GMT</pubDate>
            <atom:updated>2023-10-02T15:15:00.938Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s what I’m known for.</h4><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><p>Five years ago, I gave <a href="https://www.youtube.com/watch?v=8eev-eI0yFk">a talk at The Product School</a> about being a non-technical Product Manager. It was one of a handful of talks I gave, but, it is by far, my most popular talk. Over the years, the video has gained comments but most strikingly, I get contacted regularly from strangers about how the talk resonates with them. It’s an entry point for many folks trying to learn about product management and it leads to so many other questions about my career and about product management in general.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JDibmhbFcXYo1JCaz0kSWQ.png" /><figcaption>A still from the infamous “How to Succeed as a Non-Technical PM” talk I gave in 2017. TBT to real-life networking events.</figcaption></figure><p>And so, over the years, I’ve replied to LinkedIn messages, Instagram DMs and cold emails to connect with future and current Product Managers on what it means to succeed as a non-technical PM. I find myself doling out a lot of helpful tips I learned, not from a formal education in product management, but from my direct experience, on the front lines. And I found that a lot of this advice could be helpful to more than just the few brave souls who reach out to me online.</p><p>What I said five years ago, and what I’m saying today in 1:1 conversations resonates with people. Naturally, like a Product Manager, I’m thinking about how to make this experience more effective and scalable. And the simplest way to do that might be to write this all down. Not only because I love a good blog and newsletter (I’ve created both of these in the past). But, because I think my 10+ years of experience could offer people a real perspective on what it’s like to be a Product Manager, today.</p><p>And so, here we are. Years after I retired my acclaimed travel blog (To F’Italy and Beyond) and sold my beloved weekly newsletter (The Lunch Read), I find myself writing again.</p><p>I’ll use this space to discuss the musings of my professional path: <strong>life and learnings of a real product manager who is not technical and who most certainly doesn’t have all the answers.</strong> I’ve got a lot to share that could be useful in your current or future journey in Product Management or tech. Notably, a lot of the focus here will be on the role of a Product Manager, but, I hope a lot will be applicable to more than just the Product Manager role. I’ll start with the top questions I get asked but I’ll share other thoughts too.</p><p>I’m not entirely sure what this will become but at a minimum, I hope it helps a few of you out there looking to gain confidence to become a Product Manager.</p><blockquote>Hey — I’m now on Substack. <a href="https://joribell.substack.com/">Subscribe to get the latest from me here.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18e787074754" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>