<?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 Nathan Nannenga on Medium]]></title>
        <description><![CDATA[Stories by Nathan Nannenga on Medium]]></description>
        <link>https://medium.com/@nathannannenga?source=rss-893f8d5758c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*XPwddVizNZFPVnCZ.</url>
            <title>Stories by Nathan Nannenga on Medium</title>
            <link>https://medium.com/@nathannannenga?source=rss-893f8d5758c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:04:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nathannannenga/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[Product Management 101: Working with UX Designers]]></title>
            <link>https://medium.com/@nathannannenga/product-management-101-working-with-ux-designers-30d2ec254c1d?source=rss-893f8d5758c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/30d2ec254c1d</guid>
            <category><![CDATA[productmanagment]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-design]]></category>
            <dc:creator><![CDATA[Nathan Nannenga]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 22:14:11 GMT</pubDate>
            <atom:updated>2020-02-13T21:57:00.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1rEHboDSBsH60Nh69KNFg.png" /></figure><h3>Product Management 101: Working With UX Designers</h3><p>Wow. This topic was significantly more difficult for me to write about than I thought it would be. I thought I was going to cruise through this one, but I hit some serious writer’s block along the way. I think it’s because my experience working with UX has been really organic and having to step back and think about it from an objective, critical view has been difficult.</p><p>Because I suck at writing, and because I apparently REALLY suck at writing about PM+UX, I decided to cheat and ask my friend, coworker, and UX designer <a href="https://www.linkedin.com/in/lindseywhitefieldmartin/">Lindsey Martin</a> for some help. See her responses below.</p><p><strong>What is UX? What does a UX designer do?</strong></p><p><em>“User experience is the practice of making interactions between humans and non-humans, human-centered. A UX designer can mean a lot of different things — here at Lucid, we practice “full stack” design meaning the UX designer participates in design discovery, user research, prototyping, low- and high-fidelity design, user testing, and iteration activities. In some orgs, UXers may be more specialized (e.g., an information architect or UX architect vs a user researcher vs an interaction designer).”</em></p><p><strong>How do UX and product managers overlap?</strong></p><p><em>“They’re both working toward the same goal, which is to develop a product that successfully addresses market demand (customer needs), thereby contributing to company growth.”</em></p><p><strong>How are UX and product management different?</strong></p><p><em>“User experience is a design discipline. It’s important to the business function, but it comes from the world of design and is therefore guided by design principles. PM is primarily a business function that should be informed by the customer. We’re like a Venn Diagram with user needs (e.g., market opportunity) in the center.”</em></p><p><strong>As a UX designer, what do you rely on the product manager for?</strong></p><p><em>“Here are some ways I look to engage with my PM:</em></p><p><strong><em>Strategy</em></strong></p><ul><li><em>Prioritize product development against business objectives, user needs, and product strategy</em></li><li><em>Understand revenue sources and how they related</em></li><li><em>Project potential revenue +/- based on strategic direction (assess risk/reward)</em></li><li><em>Define and track key metrics (quant/qual)</em></li><li><em>Execute on company’s and/or stakeholders’ strategic objectives (ensure design/UX and engineering align with these needs)</em></li></ul><p><strong><em>Advocacy</em></strong></p><ul><li><em>Understand user research and user needs, advocate for user</em></li><li><em>Communicate with leadership, socializing/evangelizing product strategy and design direction</em></li></ul><p><strong><em>Documentation</em></strong></p><ul><li><em>Detailed understanding and documentation of use cases and edge cases (can look at proposed flows or wireframes and know immediately which use cases are missing or which ones could be problematic)</em></li><li><em>Document and understand product features</em></li><li><em>Document and understand strategic decisions</em></li><li><em>Document user stories</em></li></ul><p><strong><em>Activities</em></strong></p><ul><li><em>Ensure proper stakeholder involvement to remove blockers and keep product development moving forward</em></li><li><em>Participate in sprint planning, backlog grooming</em></li></ul><p><strong><em>Deliverables</em></strong></p><ul><li><em>Create BRDs (Business Requirement Documents), product roadmaps, user stories, stakeholder socialization materials, competitive reviews, etc.”</em></li></ul><p><strong>Do you have any tips for new product mangers on working with UX designers?</strong></p><p><em>“It’s all about communication. Help us understand your objectives and how you define success — we’re on the same team and working toward the same goal. Practice effective, actionable design critique and feedback with UX designers — focus on where you think the product/feature design is solving the problem, and where you are concerned the product/feature design is not solving the problem — this opens the door for debate, iteration, and (hopefully) improvement.”</em></p><p>It’s hard to improve on what Lindsey said. The only thing I will add is this: designers are really good at what they do — designing!</p><p>UX designers are masters of their trade. They know a design tool, like Sketch, inside and out. Many have a background in graphic design and have a robust understanding of good design or HCI (Human Computer Interaction) principles. While a product manager might have broad understanding of a new feature, UX designers are able to go deep and narrow, really focusing on making the flow awesome.</p><p>I can say that, as a product manager, I rely on UX to make kick-ass mockups and user flows. While I may have a good understanding of a feature’s requirements and what steps the feature needs to include, I rely heavily on my UX counter part to bring that feature to life.</p><p>What a UX designer should <strong>not</strong> be, however, is a tool. The worst way to use UX (and the fastest way to make them hate you) is to hand them a list of tasks and expect them to churn out designs. The product manager should collaborate with, not dictate to, the designer.</p><p>UX, like engineering, is a partner with the product manager. They should be involved since feature inception, helping with discovery and user research. Both should seek feedback from one another, driving together towards the best possible solution for the customer and the business.</p><p>Like what you read? Follow me on twitter <a href="https://twitter.com/Nathannenga">@Nathannenga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30d2ec254c1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management 101: Working with Software Engineers]]></title>
            <link>https://medium.com/@nathannannenga/product-management-101-working-with-software-engineers-ccd15ebdb98b?source=rss-893f8d5758c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccd15ebdb98b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Nathan Nannenga]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 15:59:50 GMT</pubDate>
            <atom:updated>2020-02-13T21:57:38.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1rEHboDSBsH60Nh69KNFg.png" /></figure><p><strong><em>Key vocabulary (largely for scrum and agile) in no particular order:</em></strong><br><strong>Standup</strong>: A daily meeting within scrum teams where software engineers talk about what might be blocking them from making progress. It’s called standup because originally you had to stand in the meeting to ensure everyone was uncomfortable enough to make it short. Sometimes at software companies non-engineering teams will adopt standups because everyone else is doing it, and that seems silly.<br><strong>Code: </strong>This one should be obvious. The actual code being written by the engineers.<br><strong>Regression: </strong>A regression is a bug introduced into the code that wasn’t there before, or breaks something that previously wasn’t broken. It’s regressed in quality. <br><strong>Blockers: </strong>At a high level, anything that prevents someone from making progress. “I am blocked because Steve hasn’t finished his implementation of feature X”. At a more technical level, a blocker is a bug or something similar that prevents code from being released to production on time. “We can’t release because the Integrations Team has a blocker”.<br><strong>Production: </strong>The public-facing version of the code. For example, the website version of Medium you’re viewing would be the production version. It is “in production”. There is likely a <strong>development environment</strong> of Medium that the public can’t see, where they are developing new code and features. Production versions should be the most stable and complete version of the code because it is live to the public.<br><strong>Bugs: </strong>A feature or event in the product that is not performing as intended, or was never intended.<br><strong>Features: </strong>Individual elements of the product that were intended. Example: clicking the button to share Medium articles is a feature.<br><strong>Stories: </strong>Sometimes, features can be broken down into smaller parts. The smallest part of development work is called a <em>story. </em>A story and a feature can be synonymous, but sometimes a feature can have multiple stories. <br><strong>Story Points: </strong>An imaginary unit of measure that scrum teams use to estimate how hard a story might be. It is completely arbitrary and subjective, and the points don’t carry over from team to team. In other words, a developer on one team might complete 5 story points in a sprint, while another equally talented developer might complete 7, yet the actual amount of work done was the same. On my team, an average developer should consider 5 points of work enough for one 2-week sprint.<br><strong>Epics: </strong>If a new feature is really big, it’s called an <em>epic. </em>An epic is just a series of smaller stories working together to make the final picture. The final picture would be the epic (the feature), and the individual pieces would be the stories.<br><strong>Retrospective: </strong>A once a sprint meeting where the team talks about how the sprint went, and what can be improved for the next sprint. It’s an opportunity for reflection and improvement.<br><strong>Estimation: </strong>A once a sprint (or more, if you want!) meeting where the developers gather to estimate how many points to allocate to stories so that the product manager can help plan accordingly. <br><strong>Planning: </strong>A once a sprint meeting where the scrum team gathers to plan out the next stories they will take. Estimation should happen prior to planning so that the team can gauge approximately how many stories they can take.<br><strong>Release: </strong>After a sprint cycle is completed code will be <em>released </em>to production, which means the new features developed will now be available for the public to use. Depending on how big of a company you’re at, this can actually be a pretty intense and laborious event.<br><strong>Sprint: </strong>A unit of time where engineers work on code. We use 2-week sprints, so we are developing code for 2 weeks, then releasing, then starting a new sprint. So every 2 weeks new code goes out.<br><strong>Scrum: </strong>A specific flavor of Agile where you have set working periods and roles. There are a bunch of articles on the web that go in depth on this, so you familiarize yourself. While scrum and agile do have set rules and defined expectations, most companies I know use hybridized versions adapted to their needs, with varying degrees of fidelity to actual scrum/agile principles.<br><strong>Agile: </strong>A development framework where the focus is iterating and releasing quickly. <a href="https://en.wikipedia.org/wiki/Agile_software_development">See wikipedia for more.</a><br><strong>Waterfall: </strong>A different, slower, more archaic form of software development. <a href="https://en.wikipedia.org/wiki/Waterfall_model">Wikipedia.</a><br><strong>Kanban:</strong> The other flavor of Agile that isn’t as characterized by defined sprint cycles, but rather working from a long list of to-do items. I have yet to work in a team that uses Kanban, but I think it would be fun to try and see the differences compared to Scrum.<br><strong>ER: </strong>An emergency release. When something is so broken or so critical it requires you to release outside your normal sprint release cycle. This typically means there is less time for testing and can be more risky, potentially introducing other/worse bugs.</p><p><em>Note: This is based on my time at </em><a href="http://golucid.co/"><em>Lucid Software</em></a><em>, a Utah based tech company. Details could vary from company to company, but I think the general principles are sound.</em></p><p>Working well with your software engineers will be key to your success. If they respect and trust you, and you respect and trust them, things will go smoothly and efficiently. If they don’t trust you to make good decisions, and you’re constantly having to persuade them, or worse yet, impose your will on them, then it’s not going to be a fun ride for anyone.</p><p>Typically, scrum teams will have an engineering lead. The engineering lead, or EL, along with the product manager and UX designer, form the trinity of product management. As a product manager, you should be working with the EL more than any other engineer, and potentially more than anyone else on the team. Additionally, the engineering lead is often the actual manager of the other engineers on the team, not you (remember, the product manager is rarely the actual manager of anyone).</p><p>The EL will provide the product manager with the expert engineering perspective. <a href="https://medium.com/@nathannannenga/product-management-101-who-makes-a-good-product-manager-e840a82c6c96">This is why I hold the opinion that product managers don’t need a technical background to be successful.</a> Even if I had a software development background, I would <em>still</em> defer to the engineering lead, because a) he is in the code everyday, and will have a better idea than I ever could and b) it’s his job and role to make the engineering decisions, and to dismiss his perspective would be disrespectful to his role and impede the progress of the organization as a whole. However, a product manager should be able to understand the nuances and trade-offs of engineering decisions, and be able to speak intelligently about the technical aspects of the product.</p><p>Here is an example of a frequent situation that can land product managers in hot water with engineers:</p><p>After presenting the proposed feature roadmap, an executive, let’s say the CEO, asks the product manager how soon the feature will be complete.</p><p><strong>Bad: </strong>Feeling under pressure, the product manager tells the CEO 4 weeks, without first consulting the engineers. He has committed the team to something without having their representation. In reality, the feature will take 6 weeks. When the feature misses the 4 week deadline and the CEO inquires about the delay, the product manager tells the CEO the engineers are behind, and passes the blame to them in order to save face. All the engineers now hate the PM.</p><p><strong>Good: </strong>The product manager responds with “I can’t commit the team to anything yet. I think it will likely take more than a month, but I need to consult with my engineering team first. Let me ask them and I’ll send you a follow up email.” The product manager feels sheepish, but doesn’t commit the team to an impossible deadline. He learns from the engineering team that the feature will take 6 weeks, let’s the CEO know via email, and sets expectations.</p><p><strong>Awesome: </strong>Being a smart person, the product manager thinks ahead and invites the EL to the meeting. When asked how long the feature will take, the product manager defers to the EL in the meeting to explain the challenges that are present, and the EL tells the CEO it will likely take 6 weeks. No one feels dumb, the expectations are realistic, and everyone is happy. The PM and EL share an epic handshake after the meeting a la the 1987 Predator movie</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qlVQEUafaLVcS_nS.png" /><figcaption>Huge biceps optional but encouraged</figcaption></figure><p>The setting in the above “Awesome” scenario should really be the de facto case. Have a user call coming up to do some discovery work? Invite the engineering lead. Reviewing mockups with the UX designer? Invite the engineering lead. When engineers are involved early in the development process, things go smoother, there are less hangups or unknown roadblocks, and they feel more involved.</p><p>Now, that being said, it is not necessary or required that the EL attend every meeting the product manager attends, but they should at least be considered. If you got hired as a PM, you’re probably an intelligent person. Use your best judgement to decide what meetings the EL should be a part of, and what meetings might be a waste of their time.</p><p>Perhaps the most important aspect to remember when working with software engineers is that, despite any stereotypes, they are just human, like you. They’ll make mistakes, you’ll make mistakes, everyone will make mistakes. Things might not be done on time, or they might break something in production. Rather than being on the side of demanding results or pointing fingers, you should consider yourself on their team. Go to bat for them when necessary. If a feature is behind schedule, a bad product manager will blame their engineers. A good product manager will shoulder part of the blame and adopt a “we” mentality, and work to explain why “we” are behind schedule. This will cement your position as a leader on the team, help to earn your teams respect, and make it easier to get sh*t done.</p><p>If you’re working in an agile environment, you’ll likely be physically located next to your scrum team. You’ll spend a lot of time with these people, so might as well make it fun. Supporting them, working with them directly, taking time to understand their perspectives and opinions, and just generally being their friend will all serve to not only make you a rockstar product manager, but also help to foster an awesome team culture rather than making work miserable for everyone, yourself included. Don’t be too uptight, we’re all in this together.</p><p><strong>Tl;DR. </strong>The engineers know more about the code and technology than you. You should understand what they’re talking about, but should defer to them when questions arise about development. Also, they’re people like you, so treating them like people will make work easier and more enjoyable for everyone.</p><p>Want to know what it’s like working with UX designers? Stay tuned for the next Product Management 101 piece!</p><p>Like what you read? Follow me on twitter <a href="https://twitter.com/Nathannenga">@Nathannenga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccd15ebdb98b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management 101: A Day in the Life of a Product Manager]]></title>
            <link>https://medium.com/@nathannannenga/product-management-101-a-day-in-the-life-of-a-product-manager-1aab0a0531d0?source=rss-893f8d5758c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1aab0a0531d0</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-product-manager]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Nathan Nannenga]]></dc:creator>
            <pubDate>Wed, 19 Sep 2018 21:55:24 GMT</pubDate>
            <atom:updated>2020-02-13T21:58:10.557Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1rEHboDSBsH60Nh69KNFg.png" /></figure><p>Here is a typical day, though this one was a little more meeting heavy than usual:</p><p><strong>7:00 AM:</strong> I hit the snooze button because I stayed up too late playing Fortnite with my roommate. Lesson learned.</p><p><strong>7:20 AM:</strong> Check my emails and Slack, make sure there aren’t any immediate fires to put out or low hanging fruit to clear.</p><p><strong>7:35 AM:</strong> Get the courage to roll out of bed and shower.</p><p><strong>8:26 AM:</strong> Pull into the parking lot at the same time the commuter train arrives. If I was sleepy before, I am fully awake now as I run to make it to the train. Catch up on more emails and Slack messages during my train commute.</p><p><strong>9:05 AM:</strong> The train pulls up right outside my office, just in time for a weekly team meeting where we catch up on the performance of the company, initiatives in action, new hires, and other general news.</p><p><strong>9:30 AM:</strong> Stand up with my engineering team, where we talk about who is blocked, any challenges they are facing, and if we are at risk of any delays. I spend the next half hour answering questions on designs they are working on implementing.</p><p><strong>10 AM:</strong> There is a product management team meeting where I meet with all the other product managers at the company. We talk about best practices, get training, and review other teams initiatives. Sometimes follow up meetings are scheduled if teams are working on things that have potential overlap.</p><p><strong>11 AM:</strong> There is a leadership meeting for my specific product where we review OKRs and other objectives, discuss team structures and potential changes, feature releases, or other upcoming or urgent events.</p><p><strong>12 PM:</strong> Lunchtime. I read TechCrunch and get caught up on news. Some people are playing a round of Super Smash Bros. in one of the conference rooms, so I swing down there and teach them not to underestimate Ganandorf.</p><p><strong>1 PM:</strong> I meet with the UX designer on my team to discuss upcoming design needs, review mockups, talk about timelines, and discuss how we feel about the state of the product and what we would like to see changed. During this time I also get a message on Slack about a bug in the product that is breaking a key feature. I assess which engineer is best suited to take it based on their current tasks and past experience with the feature. I slack them and kindly ask them to switch focus to fix the emergency issue.</p><p><strong>2 PM:</strong> I have a user call. We are reviewing mockups for design changes to our document and template pages. I try to dive down and understand their Jobs to be Done for our product and make sure that aligns with the new mockups.</p><p><strong>2:45 PM:</strong> I have fifteen minutes to kill before my next meeting, so I get outside to stretch my legs and see if the sun still exists.</p><p><strong>3:00 PM:</strong> I am interviewing a potential new product manager. I’m on the design portion of the interview today, which is my favorite.</p><p><strong>3:45 PM:</strong> Working time. Today I am reviewing the next sprint and feature stories we might take. I’m trying to decide what are the highest priorities and if we can cut anything out to hit our release deadline. Other days I might be doing some product brainstorming, trying to see where improvements need to happen, or where I would like to get a customers perspective. I’ll work with our customer success team to set up some user interviews. Or, I’ll be performing some analysis on the results of a recently released feature.</p><p><strong>5:15 PM:</strong> Checking emails again. I’m also reviewing action items and adding to my checklist of things to do tomorrow.</p><p><strong>5:30 PM:</strong> The train is pulling up outside the office. I’ll spend the remainder of the ride home writing this article.</p><p><strong>7:38 PM:</strong> My manager messaged me on Slack and asked me to present something in an update meeting tomorrow. I respond with 👍</p><p><strong>9:40 PM:</strong> My roommate asks me to play Fortnite again. He promises it will be just one match. I have completely forgotten my lesson learned from this morning.</p><p>Check out the next Product Management 101 entry to see what it’s like working with software engineers.</p><p>Like what you read? Follow me on twitter <a href="https://twitter.com/Nathannenga">@Nathannenga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1aab0a0531d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management 101: Who Makes a Good Product Manager?]]></title>
            <link>https://medium.com/@nathannannenga/product-management-101-who-makes-a-good-product-manager-e840a82c6c96?source=rss-893f8d5758c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e840a82c6c96</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nathan Nannenga]]></dc:creator>
            <pubDate>Thu, 13 Sep 2018 20:07:59 GMT</pubDate>
            <atom:updated>2020-02-13T21:58:32.271Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1rEHboDSBsH60Nh69KNFg.png" /></figure><p>If you read <a href="https://medium.com/@nathannannenga/product-management-101-how-one-becomes-a-product-manager-a7402bce64d5">how I got into product management</a>, you might glean that my background was pretty… generic. There wasn’t really anything special about me. So, who would make a good product manager?</p><p>I propose that the best product managers are people who are smart and capable of learning quickly, as being a product manager requires infinite adaptability. You never know what the next day will bring! And so, these qualifications can apply to a number of people from a number of diverse backgrounds.</p><p>Some companies really emphasize a computer science or technical background for their product managers. <a href="https://www.google.com/search?q=do+product+managers+need+to+be+technical">Other people argue against that</a>. I’ve picked up a few skills here and there, but I don’t have a hard technical background myself and I haven’t felt like that has been a hindrance in the least. That being said, I probably wouldn’t even be considered for an interview at Google based on this <a href="https://careers.google.com/jobs#!t=jo&amp;jid=/company/product-manager-google-building-41-1600-amphitheatre-2699240065">job description</a>.</p><p>I’ve mentioned it before, but if I could do school again I would probably study computer science. I think knowing how to code and having a software engineering background would be a tremendous help, but I don’t believe that <em>not</em> having one precludes anyone from being a successful product manager.</p><p>The world is a mishmash of perspectives on where product managers should come from because the career path is relatively new and undefined still. In Utah, where I reside, the product management landscape is quite diverse in terms of background, which you can see in this <a href="https://utahproductreport.org/">report.</a></p><p>However, I will emphasize again what I consider to be the 3 main pillars of product management: <strong>technology</strong>, <strong>design</strong>, and <strong>analytics</strong>. Having a good foundation in each of these, whether formal or informal, will really qualify someone in my eyes. The day-to-day life of a software product manager touches on each one of those. I’m communicating directly with software engineers, I’m working closely with designers, and I am constantly analyzing, measuring, and predicting results. Mix that with a healthy dose of customer empathy and you’ve got yourself a product manager.</p><p>In fact, when interviewed at <a href="http://golucid.co/">Lucid Software</a>, my interviews focused on those exact 3 areas. I participated in interviews, some with cases, that attempted to gauge my knowledge and capacity in each of technology, design, and analytics. Now, this is a sample size of 1, and each company will handle interviews differently, but I stand by my point that if you are well versed in those 3 areas you should do fine in any situation.</p><p>For clarification, when I talk about technology in this sense, I’m not talking about coding ability. What I mean in this regard is a clear understanding of how technology and software work and how humans interact with both. Even without coding, you should be able to discuss the process of how apps are built, and the best practices for how humans interact with them.</p><p>06/04/19 EDIT: After thinking on this some more, I think I would add an additional pillar: Leadership. The ability to lead and convince teams and stakeholders is instrumental to the success of a product manager. A large portion of the job requires you to convince or persuade others to join your cause.</p><p>So what is the day to day life of a product manager like? <a href="https://medium.com/@nathannannenga/product-management-101-a-day-in-the-life-of-a-product-manager-1aab0a0531d0">Check out the next Product Management 101 article!</a></p><p>Like what you read? Follow me on twitter <a href="https://twitter.com/Nathannenga">@Nathannenga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e840a82c6c96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management 101: How One Becomes a Product Manager]]></title>
            <link>https://medium.com/@nathannannenga/product-management-101-how-one-becomes-a-product-manager-a7402bce64d5?source=rss-893f8d5758c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7402bce64d5</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Nathan Nannenga]]></dc:creator>
            <pubDate>Thu, 30 Aug 2018 19:51:59 GMT</pubDate>
            <atom:updated>2020-02-13T22:00:15.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1rEHboDSBsH60Nh69KNFg.png" /></figure><p>If you read my <a href="https://medium.com/@nathannannenga/product-management-101-what-is-a-product-manager-a86839a6fcc3">first article</a>, you now know what a product manager is and does. If you’re reading this one, you’re probably curious how you can get into this sweet gig. First, I’ll tell how I got into product management.</p><p>Not knowing what I wanted to do in life, I graduated with a degree in business management, which is about as general and vague as you can get (in hindsight, I wish I had done computer science or industrial design. More on that regret another time).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*ugzSgPcFg-BDn_yv" /><figcaption>Look at all the business we’re doing!</figcaption></figure><p>After graduation, I ended up working for a solar company as an analyst. I spent a year and a half staring at spreadsheets for 8 hours a day before reaching the brink of my sanity. Not able to stomach another VLOOKUP, I started exploring other opportunities. I still wasn’t sure what job or career I wanted, but, what I had discovered over the last year, was that I definitely did not want to be an analyst anymore. That got in me in the mind set, though, of thinking about what what I <em>did </em>want. I opened up a Google Doc and started jotting down ideas. I narrowed it down to a few key concepts:</p><ol><li>I wanted to work in software. I realized this when I realized that all the news I was reading, the pieces that got me really interested, were about software companies. Software was the industry I wanted to be in. Utilities wasn’t my jam.</li><li>I wanted to be in a career that would help me be an entrepreneur later in life. It’s my goal to own my own thing someday, so I wanted to be in a role I felt would give me skills to get there.</li><li>I wanted to learn to work with software engineers. This is very related to point 2.</li><li>I wanted to work on a team. A year and a half of being an analyst taught me that I <strong>hated</strong> working on projects by myself. I longed for the opportunity to work in a team, to share and exchange ideas with other people. Crunching numbers in Excel by myself all day was crushing my soul.</li><li>I loved design work, and I wanted to be in a place where I felt I had an opportunity to contribute to the design. You can only make spreadsheets and graphs look so good.</li><li>I did not want to be doing the same thing everyday.</li><li>I wanted to be at a company that really cared about me and my growth.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*0oepCi0AdEOq_qQJ" /><figcaption>“I know you asked for a simple pie chart, but if you use your imagination I think this conveys our market share a lot better.”</figcaption></figure><p>Having actually sat down and written out these points, I felt like I had a good North Star for where I should be looking. I started doing some Google-fu and came across this job role called <em>product management</em>. (If it wasn’t obvious where this story was leading, I don’t know what to tell you.)</p><p>After reading the description, I felt like the role hit every point I was looking for. I decided then that I would be a product manager. I dusted off my resume, polished it up as best I could, and let it fly. I had a few interviews and opportunities, but I can attribute my role as a product manager at <a href="http://golucid.co/">Lucid Software</a> to having a good network.</p><p>While browsing <a href="https://www.linkedin.com/in/nannenga/">LinkedIn</a> one day, I came across an update that a friend from school had started a role at Lucid. I was curious how he liked it, so I reached out to him, and ended up telling him I was in the process of a career change. He asked what I was looking for and I told him product management. He said “Hey, we’re looking for one of those right now! Send me your resume”.</p><p>A whirlwind of interviews later and I had an offer. Total time from starting to search to sitting at a new desk in a new company surrounded by new coworkers: about 3 weeks.</p><p>So what is the secret? The disappointing answer is: there isn’t one, and a healthy amount of luck is involved (cue the audience groans). However, I think I inadvertently took a few replicable steps:</p><ol><li>I knew why I wanted to do product management (see the above points). I can’t stress this enough. Having since interviewed a number of candidates for product management roles, I can say that knowing what a product manger does and why you want to do it makes the difference between an okay candidate and a great candidate.</li><li>I had, through my own hobbies, rough experience with what I consider the 3 main pillars of being a PM: understand technology, understand design, and understand analytics. I wasn’t a programmer, but I was enough of a hobbyist with building websites that I knew what I was talking about. I wasn’t a designer either, but I had mocked up ideas before. And I wasn’t an analyst… oh, wait. I actually was an analyst at the time, but you get the idea. More on the 3 pillars of product management later.</li><li>I had a solid resume and background showcasing that I was capable of learning.</li><li>I sent out a LOT of resumes and applications, despite going with the position that came through networking.</li><li>I was in the right place at the right time and knew the right people. I know this may feel like pure luck, but it isn’t. It means being open to new opportunities and pursuing them from all avenues. Put yourself in the right place, be there at the right time, and get to know the right people.</li></ol><p>So what skills make a good product manager? What was the interview process like? <a href="https://medium.com/@nathannannenga/product-management-101-who-makes-a-good-product-manager-e840a82c6c96">Find out in the next product management 101 piece!</a></p><p>Like what you read? Follow me on twitter <a href="https://twitter.com/Nathannenga">@Nathannenga</a></p><p>(Image credit to <a href="https://medium.com/u/2053395ac335">Unsplash</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7402bce64d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Management 101: What is a Product Manager?]]></title>
            <link>https://medium.com/@nathannannenga/product-management-101-what-is-a-product-manager-a86839a6fcc3?source=rss-893f8d5758c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a86839a6fcc3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[software-design]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Nathan Nannenga]]></dc:creator>
            <pubDate>Mon, 20 Aug 2018 22:42:39 GMT</pubDate>
            <atom:updated>2020-02-13T22:00:44.904Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1rEHboDSBsH60Nh69KNFg.png" /></figure><p>If you’re reading this, you’re probably either interested in product management as a career, or somehow you got hired into a product manager role and are currently sitting at your desk wondering what the heck you’re supposed to be doing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*9Xz9AfqgZfULL8m7" /><figcaption>It helps if you turn the computer on first</figcaption></figure><p>Don’t worry, I got you covered.</p><p>The role of product manager is relatively new and increasing in popularity. As such, the definition is somewhat ambiguous, and, if you were like me, you might not have known the job existed until you applied for it.</p><p>So, what is product management? The answer to that question probably depends on who you ask and what company they work for. Each company has their own flavor of product management, but I think there are a few common themes in each, and I’ll do my best to break that down for you.</p><p>While what I discuss will mostly be through the lens of my experiences working as a product manager at SaaS company called <a href="https://www.golucid.co/">Lucid Software</a>, I believe they hold true in a general sense.</p><p>A product manager’s (PM) responsibility can be summarized like this: Build the right thing, for the right people, at the right time. As a PM, your job is to make sure the product you are responsible for is not only moving forward, but also moving in the right direction.</p><p>The PM works to define what needs to be built, and then be the liaison between the customer, the software engineers, the designers, and the key stakeholders. That means being the chief decision maker, the negotiator, the mediator, the mentor, the strategist, the researcher, the design adviser, the donut buyer, and every other role that needs to be filled to keep things moving smoothly.</p><p>So how do you know what needs to be built? You talk with customers. A lot. In fact, the most important aspect of being a PM is your ability to talk to customers and sift out the jewels of insight they might have. Doing primary research is a big part of being a PM, but analyzing data and understanding trends are also key tools in the PM arsenal.</p><p>That being said, being a PM means wearing a lot of hats, which makes the job very fun, challenging, and rewarding. Just ask the <a href="https://www.wsj.com/articles/coveted-job-title-for-m-b-a-s-product-manager-1456933303">Wall Street Journal</a>.</p><p>“Oh, I have a friend who does project management for XYZ”. Many people often confuse a project manager with a product manager. They are not the same role, so make sure you don’t confuse the two yourself in an interview!</p><p>A project manager is typically in charge of a specific project, and making sure that project reaches completion on time and on budget. There is typically a set life to the project (like the launch of an event, for example), and then they move on to the next project. Their goal is to ensure everything moves smoothly, keep on top of people, forecast the budget, etc. (but don’t quote me on any of this, I’ve never actually been a project manager).</p><p>Conversely, a product manager is on a product or feature indefinitely. Their feature might include a launch date, but that does not signal the end of their work. In addition to that, they are (or should be) less concerned about making sure that people are on task (thats the engineering leads responsibility) and much more concerned with solving problems and figuring out solutions.</p><p>“How do we improve retention?” is a great problem for a product manager. “How do we launch this product line by Christmas?” is a great problem for a project manager. You want to be solving the former problems more than the latter.</p><p>Lastly, A product manager is not really a manager of people, but more a manager of expectations. Some companies might give you the ability to fire someone, but most companies won’t. You aren’t the software engineers manager. You aren’t the UX designers manager. You’re the <em>products</em> manager, so don’t let the title go to your head.</p><p>The product is your baby. You should know it inside and out. You should understand where it came from, and where it’s going, and why the product is where it is right now. If someone has questions about something product related, you should be the person they go to get it answered.</p><p>So how do you become a PM? <a href="https://medium.com/@nathannannenga/product-management-101-how-one-becomes-a-product-manager-a7402bce64d5">Check out the next Product Management 101 piece!</a></p><p>Like what you read? Follow me on twitter <a href="https://twitter.com/Nathannenga">@Nathannenga</a></p><p>(Image credit to <a href="https://medium.com/u/2053395ac335">Unsplash</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a86839a6fcc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Last Product Development Framework You’ll Ever Need…]]></title>
            <link>https://medium.com/@nathannannenga/the-last-product-development-framework-youll-ever-need-284a84e64d11?source=rss-893f8d5758c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/284a84e64d11</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Nathan Nannenga]]></dc:creator>
            <pubDate>Wed, 25 Apr 2018 16:05:00 GMT</pubDate>
            <atom:updated>2018-04-25T16:05:00.962Z</atom:updated>
            <content:encoded><![CDATA[<p>…And it was developed a long-ass time ago by a guy named Francis Bacon. It’s called “The Scientific Method”. Look, I love a good framework as much as the next guy. They provide a structured way to think about unstructured data. Pick your framework, throw in some numbers, add some clip art and BOOM you’ve got a presentation ready to share with your CEO. Sometimes I think we go a little overboard though.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOqLJxRG-pIcI0MLUuT6Ew.png" /><figcaption>Barf.</figcaption></figure><p>In product development, the only framework you really need is an adaptation of the scientific method. Maybe it’s been a while since you had to think about that concept, so here’s a refresher:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*X3H5zdzc7xQwq4qjD5jmDA.png" /><figcaption>Mmm, bacon.</figcaption></figure><p>Pretty simple right? Because it is. It’s simple, and it works. Lets walk through it piece by piece:</p><p><strong>Ask a question:</strong></p><p>“Why don’t users click this?” “How can we reduce churn?” “How can we improve conversions?”</p><p><strong>Do background research:</strong></p><p>I cannot emphasize this step enough. This should be the backbone of all your product development. When you have a question, you should focus on figuring out the <em>why.</em> Identify the job to be done, understand the user, understand the <em>problem.</em> The real kicker? This should happen before you even think about the solution. Problem first, then solution. Got it? Good.</p><p><strong>Construct a hypothesis:</strong></p><p>Great, you’ve got a question you’re trying to answer and you did some research to understand the problem. NOW you get to develop the solution, feature, growth test, modal, whatever. Come up with your solution (based on your data, of course) and bask in its glory.</p><p><strong>Test with an experiment:</strong></p><p>Wait what? I’m a product god! I don’t need to test this, my feature is flawless. WRONG. Test your hypothesis to make sure it holds up to your research. This can be done in a number of ways, but ultimately you have to get it out in front of users. Usability testing, AB testing, Beta testing. Whatever you want. Test that shiz. Might I suggest that whatever you test be the MVP of your ideal feature? Because if it fails, it’s going to save you a lot of explaining later if you didn’t waste a bunch of resources/time to find out you were wrong.</p><p><strong>Analyze your data and draw a conclusion:</strong></p><p>Was your hypothesis correct? Did you reduce churn? Did you increase conversions? If you correctly did your research you should have a good understanding of why your feature worked. Synthesize that data and decide how it went. If it didn’t pass your threshold, take it back to step 3. Wait, scratch that. Take it back to step 2. When in doubt, research it out.</p><p><strong>Communicate results:</strong></p><p>Aw yes. You nailed it. Conversions are up 10000%. You ARE a product god. But don’t forget to report it! This is how your organization learns and grows, and how you get recognition.</p><ol><li>Record it. Record the questions, the research, the notes, the proposed solution, the process, the experiment, and the results. Then publish it somewhere visible to your team, like in Google Drive or Confluence.(Bonus points if you can standardize this template for the future).</li><li>Share it. Let your manager know, let your team know. Send an email to stakeholders or give ’em a nice @channel (just kidding, don’t do the @channel). Celebrate the results and share your documentation. Let them know what you learned and how to improve it for the future.</li></ol><p>Communicating your results is one of the most important steps. Don’t forget to manage up, down, side to side. Be open and clear about what happened, and you’ll have that VP spot on your LinkedIn in no time.</p><p>I just started a <a href="https://twitter.com/Nathannenga">Twitter</a>, so follow me for more stupid stuff → <a href="https://twitter.com/Nathannenga">@nathannenga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=284a84e64d11" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>