<?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 Robert Wallace on Medium]]></title>
        <description><![CDATA[Stories by Robert Wallace on Medium]]></description>
        <link>https://medium.com/@robw3?source=rss-a7fef633fe8c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gtX-CuavA-R78bFfRrAQAQ.jpeg</url>
            <title>Stories by Robert Wallace on Medium</title>
            <link>https://medium.com/@robw3?source=rss-a7fef633fe8c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:42:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@robw3/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[Behavioral Interviewing for Product Leaders — Part 2]]></title>
            <link>https://medium.com/@robw3/behavioral-interviewing-for-product-leaders-part-2-2b174b97ae64?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b174b97ae64</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Wed, 11 May 2022 20:19:10 GMT</pubDate>
            <atom:updated>2022-05-11T20:19:10.963Z</atom:updated>
            <content:encoded><![CDATA[<h3>Behavioral Interviewing for Product Leaders — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y7TwupwaoWMPeYNHYOlQHQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@linkedinsalesnavigator?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">LinkedIn Sales Solutions</a> on <a href="https://unsplash.com/s/photos/interview?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Check out Part 1 if you haven’t. It’ll make this post easier to consume.</p><p>In follow-up to Part 1 I want to spend a moment clicking into INTERACTING behavior for a product leader.</p><p>So much of what product management gets done in an organization is through influence, not ownership. Product teams are typically small compared to engineering teams. Outside of a couple brand managers I know, the engineering, marketing, QA organizations don’t report to the product tier.</p><p>What we get done is what we influence, not what we own.</p><p>So, how we interact with the organization is I believe a very important behavior to drill into with a candidate product leader.</p><p>My model of traits for interacting are collaboration, communication, and persuasion. I describe these traits as follows:</p><ul><li><strong>Collaboration </strong>— enjoys sharing their expertise with other professionals, builds team bonding, and open to a variety of inputs from across the organization.</li><li><strong>Communication </strong>— adept at speaking to the audience (vs. an audience), enjoys public speaking, and articulate</li><li><strong>Persuasive </strong>— skilled listener, probes, questions, and strives to influence others.</li></ul><p>For each of these traits we can build questions that test for the trait. Think about how you want your product leader to interact with the organization at large.</p><p><strong>INTERACTING</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*XNK5hETUd4oIu8TGxf7s_g.png" /></figure><p>What questions would you ask to look for evidence of a communication trait? Something like, “tell me about your most recent public speaking opportunity?” Do you need to test for PowerPoint skills? Do they use group polling while presenting?</p><p>Hiring for behaviors and traits helps you land the product leader you and your organization need.</p><p>What traits would you add or remove?</p><p>Be brief. Be bright. Be done.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b174b97ae64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Team Maturity Model]]></title>
            <link>https://medium.com/@robw3/product-team-maturity-model-6ccb08f250f2?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ccb08f250f2</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Wed, 11 May 2022 20:06:36 GMT</pubDate>
            <atom:updated>2022-05-11T20:06:36.417Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0dLpFWFy-UBeiS3kAtTDw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@h4x0r3?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thao Le Hoang</a> on <a href="https://unsplash.com/s/photos/karate?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Most of us know that as a new martial arts student, you start as a white belt and progress through various hues to black. There are also achievement milestones within each belt, usually called a stripe.</p><p><strong>In short, there’s a maturity model in martial arts.</strong> <strong>White belt to black belt.</strong></p><p>I used to teach a martial art called Kenpo (as a head student). My responsibility was to train the new students in a class just for us when they joined the school. First, I would help them settle into the flow of a class. For example, coach the new student on where to stand and how to enter &amp; exit the school training floor. I also taught them their first kicks, blocks, punches, and breathing techniques.</p><p>Then, when they joined the regular class in session, they would blend in seamlessly, having been acclimated to how a class runs. My teaching was part of my growth to a black belt.</p><p>Within a martial arts maturity model are categories to measure progress, such as proficiency in belt-appropriate kata, one-steps, class participation, sparing, and attendance, to name a few.</p><p><strong>Do you have a maturity model for your product team?</strong></p><p>If not, how do you know you are getting better as a team?</p><p>Do you have a plan for how to get better as a team?</p><p><strong>A maturity model can help you be a better product leader.</strong></p><p>In the martial arts, it’s plotted out, belt by belt. In product management, we need to do the same.</p><p>Google “product management maturity model” when you have a moment.</p><p>A favorite, which I’ve modified for my use, is from the Product Focus folks (<a href="https://www.productfocus.com/">https://www.productfocus.com/</a>). (I have no affiliation with them. But, just like their approach.)</p><p>The six categories I use are Leadership, Organization, Metrics, Process, People, and Systems. Within those categories, I have measures to show advancement — the progress tracking in my model has five tiers (think white belt to black belt).</p><p>I work with my direct reports to tune the measures appropriate to our business. My managers have a say in how they, and the teams, are getting measured. And we have a progression path, just like the martial art Kenpo.</p><p>Be bright. Be brief. Be done.</p><p>Rob</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ccb08f250f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Persona Software Journeys]]></title>
            <link>https://medium.com/@robw3/persona-software-journeys-33bd9affaf5f?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/33bd9affaf5f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Wed, 11 May 2022 20:04:06 GMT</pubDate>
            <atom:updated>2022-05-11T20:04:06.519Z</atom:updated>
            <content:encoded><![CDATA[<p>Somebody posted this on LinkedIn (wish I could remember who). I laughed out loud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*341QnwlvgZl-pKwVne6zfw.png" /><figcaption>From a LinkedIn post I found (IM me for credit)</figcaption></figure><p>Are you detailed enough to draw out the <em>pains, gains, jobs-to-be-done</em> for the appropriate persona?</p><p>In a recent job, I had a handful of customers who bought thousands of units a month from my website, and many that purchased a couple of units a month. Their needs within my software to achieve the volumes they needed for their business were very different. We had 9 distinct personas with volumes, and technical needs detailed. I’ll talk about only 2 of them here for brevity, and look at the persona needs as they “journey” through my website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*hHZmx2pgG1MhODcLXkrddA.png" /></figure><p>As you might expect the personas had different needs from my website. Appraisal tools were meaningful to one but irrelevant to another. Bidding was wildly different.</p><p><strong>Do you have your personas mapped to their journeys in your software?</strong></p><p>How many distinct personas do you use, monitor, and track?</p><p>Do you think about the <strong>value </strong>one persona brings to your business vs. another? In the example above a change in the website appraisal tool may well be prioritized behind the integration feature for the large volume buyer.</p><p>Be brief. Be bright. Be done.</p><p>Rob</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33bd9affaf5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing HIPPOs]]></title>
            <link>https://medium.com/@robw3/managing-hippos-3bfa197114a7?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bfa197114a7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hippos]]></category>
            <category><![CDATA[roadmaps]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Wed, 11 May 2022 19:58:14 GMT</pubDate>
            <atom:updated>2022-05-11T19:58:14.935Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4QT71o1V0C-VHPbc46w9A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@perventuator?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Bibhash Banerjee</a> on <a href="https://unsplash.com/s/photos/hippopotamus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>One of the best questions I’ve ever been asked when interviewing for a product leadership role is; <strong>“how do you manage the power change dynamic when you bring a product management process to an organization that’s been building software directed by a founder or senior leader?”</strong></p><p>This is something I learned to do at McKesson, but I didn’t have a theme for the practice back then. A founder or senior leader can also be called a “highest-paid person.” They definitely have opinions on what the product needs. And needs now now. Not now, later.</p><p>How do you manage the “HIghest-Paid Person’s Opinion?” Or how do you manage your HIPPOs?</p><p>Since about 2005, I’ve been bringing product management practices to organizations. Essentially, I‘ve created a Way of Working (WoW) for developing products. I’ve invented nothing. I’ve only pulled together practices of the last 15 years into a framework that has worked for my organizations.</p><p><strong>Product management frameworks move an organization away from “gut feelings and emergencies” to prioritized, researched, data-driven roadmaps.</strong></p><p>Here’s how you manage your HIPPOs.</p><p><strong>#1 — Collect your HIPPOs into an Investment Steering Committee.</strong></p><p>Meet monthly with your HIPPOs.</p><ul><li>Present to them monthly:</li><li>“What we are working on now, and why,”</li><li>“What we want to work on next, and why,”</li><li>“Success, and failures, on released features.” In other words, did we create the benefit we promised, or not?</li></ul><p>Then we have them vote. We have them approve or disapprove of what’s inflight now and what’s coming next in the queue. I like to use PI’s (program increment) vs. Sprints for time blocks. By the way, Poll Everywhere is an excellent tool for voting and many other interactive presentations. A topic for another day.</p><p>You can use the inertia of the herd of HIPPOs to deflect another HIPPO’s request. HIPPOs aren’t bashful about challenging each other. It could be in that meeting the idea is approved for research. We need to talk about Stage Gates® another time. I.e., how items get into the “what we want to work on next, and why” bucket.</p><p><strong>#2 — Data and Research</strong></p><p>To manage HIPPOs, you need to present data and research. Our roadmaps aren’t indiscriminate choices. Right? We are pursuing outcomes of revenue, retention, or cost savings with our roadmaps. We have a “whole offer map” on our “stairway of value strategy.” Where would this idea fit? Or not fit?</p><p><strong>#3 — Understand Existing Commitments</strong></p><p>A HIPPO understands an existing promise to a customer or internal/external stakeholder. We may have to explain what would change with the roadmap to accommodate their idea. Who would we disappoint, disrupt, or discourage with a roadmap change?</p><p><strong>Last Thought</strong></p><p>HIPPOs are well-meaning. We all are trying to do the right thing.</p><p>Your CTO, and much of the rest of the organization, are counting on you not to enable big swings in the roadmap. Swapping out objectives on an engineering team is demoralizing. The engineering team loses trust that they are now working on the priority.</p><p>NOBODY LIKES TO MAKE SHELFWARE.</p><p>An organization has asked you to create a product management process because it has recognized waste (i.e., no outcome for the work), the demoralizing impact on engineering, or some other negative impact to “gut feelings and emergencies” as the way to build something.</p><p>Be brief. Be bright. Be done.</p><p>Rob</p><p>Photo by <a href="https://unsplash.com/@perventuator?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Bibhash Banerjee</a> on <a href="https://unsplash.com/s/photos/hippopotamus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bfa197114a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Can’t Be A Good Product Leader Without UX]]></title>
            <link>https://medium.com/@robw3/you-cant-be-a-good-product-leader-without-ux-6ea05afc2d43?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ea05afc2d43</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Fri, 25 Mar 2022 21:44:06 GMT</pubDate>
            <atom:updated>2022-05-11T20:21:03.732Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oasuCPvCVj5IqdVYfcHBaQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@alvarordesign?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alvaro Reyes</a> on <a href="https://unsplash.com/s/photos/ux?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Hiring strong UX leaders has taught me to be a better Product leader.</p><p>Co-locating UX and Product into a single organization has taught my product teams be better product leaders. Not always comfortable for product leaders. Seems that UX’ers speak truth to power whether you want to hear it or not. Thank goodness. Reminds me of a general surgeon I used to work with at McKesson. Brilliant. Plain. Straight. Shooters. Maybe plumbing the depths of software, or people, creates a proclivity for honesty?</p><p>To be clear. The product lead owns the embodiment of the product. But you better listen to your UX’er.</p><p>Friend of mine is a big wig engineer at AMD. He travels around to Dell, Apple, etc. He tells a story that at Apple the “designers” sit at the table, the engineers sit in chairs along the wall. At other firms it was reversed. I aspire to have my “designers at the table” on my teams.</p><p>I really want to brag about <strong>my great UX experience</strong>. I’m a fair hand at Sketch, Balsamiq, and Figma. I have an “eye for design.” Bad user experiences make me nuts. From elevator controls, settings panels on software, or my SUV entertainment system. I notice and critic everything. But the truth is, while I can navigate the software, create my own wireframes, and medium fidelity prototypes, it pales in comparison to what a UX pro brings to the team. You can’t be a strong product leader without UX.</p><p>I’ve been most successful as a UX leader when I, 1) hire the right leader, 2) stay out of her way, and 3) give her the resources needed to get the job done. One of my hardest lessons as a leader? Stay out of my team’s way. Maybe a topic for another blog?</p><p>On other blogs I’ll share some aha moments UX created for my products.</p><p>Examine how you are using UX. Are they at the “table?”</p><p>Be brief. Be bright. Be Done.</p><p>Rob</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ea05afc2d43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Be Brief. Be Bright. Be Done.]]></title>
            <link>https://medium.com/@robw3/be-brief-be-bright-be-done-f166a37cff24?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f166a37cff24</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Fri, 25 Mar 2022 20:00:23 GMT</pubDate>
            <atom:updated>2022-05-11T20:22:00.645Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JvUr-f_mxQcCzJt_8pV6SA.png" /><figcaption>Photo by <a href="https://unsplash.com/@frostroomhead?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Rodion Kutsaev</a> on <a href="https://unsplash.com/s/photos/light-bulb-idea?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In 2010 I was lucky enough at GE to join my general manager and his direct reports in “Leadership, Innovation, &amp; Growth” training series. The great Bob Cancalosi led us through a weeklong session focused on “Leading Global Growth in a Reset World.” Professors from Wharton, Harvard, and leading business authors joined us for condensed master Jedi training in their many specialties. Talk about a competitive advantage for an organization like GE! This is one of many I observed while working there. LIG has become part of my competitive advantage. Thank you, GE!</p><p>Bob led us off, there were several business units represented, with an opening that’s become a <strong>coachable moment for me and my teams for many years</strong>. I will never forget his advice.</p><p>Forgive me, I paraphrase, it’s been 12 years and my handwritten notes are messy. He said, “… you will be participating in Q&amp;A with these amazing instructors, all of whom have years of expertise in leadership, innovation, or growth. You will be <strong>brief</strong> in your comments having given thought to your comments before you speak. You will be <strong>bright</strong> in your comments having given thought to your comments before you speak. You will give the microphone back and sit down and be <strong>done</strong> after your comments.”</p><p><strong>Be brief. Be bright. Be done.</strong></p><p>How many meetings or presentations can you remember where this wasn’t an operational objective?</p><p>I’ve shared Bob’s advice with my product &amp; UX teams for many years. I try to adhere to his advice when I present, “having given thought ….” I don’t always achieve brief, bright, done. But I try.</p><p>I got a LinkedIn message from a product manager who worked with me for several years. She was in a new role and carrying Bob’s advice on to her new team. The next generation of product managers benefit from LIG a decade later. Building our competitive advantage as product practitioners.</p><p>Be brief. Be bright. Be done.</p><p>Rob</p><p>P.s. thank you Fran, Bob, and GE. And thank you Abi for your encouraging message.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f166a37cff24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behavioral Interviewing for Product Leaders — Part 1]]></title>
            <link>https://medium.com/@robw3/behavioral-interviewing-for-product-leaders-part-1-a07c5a9879c9?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a07c5a9879c9</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Fri, 25 Mar 2022 19:00:26 GMT</pubDate>
            <atom:updated>2022-03-25T19:00:26.610Z</atom:updated>
            <content:encoded><![CDATA[<h3>Behavioral Interviewing for Product Leaders — Part 1</h3><p>Around 2004 to 2005 McKesson Health Solutions (MHS) offered “Behavioral Interviewing” for its managers. They even went so far as to bring in contractors for the day to pretend to be interviewing for roles on your team. We had class time, followed by practical time. Really cemented the practice into my brain. I learned so much over my almost 10 years at MHS. Thank you MHS!</p><p>Over the years I’ve collected more materials to add to the BH model offered in the McKesson training. It’s a model I’ve been using now for 15 years. I’ve done a ton of hiring in product management in particular, and been on hiring panels for QA, engineering, customer success, marketing, sales, etc. A behavioral approach works. Here’s how to set it up for yourself.</p><p>A little background first. To be a strong product leader, at any level of the organization, there are <strong>behaviors</strong> I believe make you more successful. Behaviors that improve the success in hiring the right person. With in these behaviors are <strong>traits</strong> that fill out the behavior and make it observable to the interviewer.</p><p>The behaviors I interview for are:</p><ul><li><strong>Motivations</strong> — what motivates the candidate? I believe there are specific motivations that separate a great product leader from an average product leader.</li><li><strong>Thinking</strong> — how does the candidate think? How does the candidate gather information and then sort, parse, problem-solve, and analyze? I believe there are proclivities that separate great from good.</li><li><strong>Acting</strong> — how does the candidate act? Here we interview about skills like time management, prioritization of time, work focus, mental stamina.</li><li><strong>Interacting</strong> — how does the candidate interact with people? I believe how the candidate interacts is a critical behavior pattern to delve into. What the product team gets done is usually through influence, and not direct ownership. Call it high EQ vs. high IQ. High IQ is nice, but not without EQ in a product role.</li></ul><p>There may be more behaviors you want to add like Learning, Training, Selling, etc. These behaviors are a starting point for you to build your own model. These four are a good starting point.</p><p>Think about the <strong>traits</strong> that exemplify the MOTIVATIONS, THINKING, ACTING, and INTERACTING you want in a product leader. What motivations do you want in a product leader? Make a list. Then ask your self the same question for each behavior you’ve identified.</p><p>So, my model for motivations are Servant Leader, Achiever, and Accountability. No doubt there are few other we could list. In the back of my mind is we are going to have 30–60 minutes at best to interview the candidate. So we have to prioritize. I pick two or three of the more important, to me, motivations.</p><ul><li>A <strong>Servant Leader</strong> is a team player, and service oriented. We can build questions that test for those traits.</li><li>An <strong>Achiever</strong> shows confidence and self-assuredness, seeks independence, and wants to accomplish goals. We can build questions for this trait.</li><li><strong>Accountability</strong> refers keeping a high Say/Do ratio. They stay committed to delivery of tasks. And take ownership of the good and bad in their products. Again, we can build questions for this trait.</li></ul><p>Think about how you want a product leader to “think, act, and interact,” or whatever behavior you added/replaced. Pick one or two traits for each. Build your list of traits. Create your questions to test for that trait. Next, jot down what answers you think would demonstrate evidence that the candidate has this trait.</p><p>Let’s click into Servant Leader and build out the model as an example. The order of execution on the model is: Motivation &gt; Servant Leader &gt; Service Oriented &gt; Question &gt; Evidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EqZVZt4THxE3dy29_mnsWg.png" /></figure><p>Does this make sense? You want a candidate that is motivated to be a servant leader so you ask them prepared questions while looking for evidence in their answer which you’ve thought about in advance.</p><p>In another post I’ll share what I believe are the behaviors and traits we want in product leaders Interactions between peers, org leadership, teams, and customers. As I mentioned, I think it’s a critical behavior that deserves more attention, and more detail then we have room here.</p><p>Any thoughts or comments? Does this model make sense to you?</p><p>Be brief, be bright, be done.</p><p>Rob</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a07c5a9879c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do You Have a Hiring Model For Product Management?]]></title>
            <link>https://medium.com/@robw3/do-you-have-a-hiring-model-for-product-management-bb39fba54060?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb39fba54060</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Thu, 24 Mar 2022 19:41:16 GMT</pubDate>
            <atom:updated>2022-03-24T19:57:05.306Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*qG4w3cT1D7iyXeI25prqwA.png" /></figure><p>Do you have a trait driven hiring model for finding the right product manager for your team?</p><p>I was dissatisfied with my hiring. I needed to change my approach. After speaking with a friend in HR (McKesson, circa 2005) it became obvious to me I didn’t have a firm “idea” of what I was looking for in a product manager. Also, around that time McKesson trained its managers on a behavioral interview approach, which I still use today. (I’ll share a behavioral interview approach in another post).</p><p>Armed with this new skill I’ve greatly improved my hiring of product leaders into my teams. What I propose works for product managers, directors, and VP’s. To this day I use behavioral questions along with a mental model I cooked up.</p><p>My trait model is called SINFA. An abbreviation for:</p><ul><li><strong>S</strong>kills</li><li><strong>I</strong>ndustry Experience</li><li><strong>N</strong>atural Aptitudes</li><li><strong>F</strong>it</li><li><strong>A</strong>ttitude</li></ul><p>The first couple traits are hard skill sets, the last couple are soft skill sets. I define each as follows:</p><ul><li><strong>Skills </strong>— Is the candidate able to be a storyteller of the product management methodology. Have they practiced the art/science of product management? What do they think product management is? Truthfully, I worry less about this skill set then you might imagine. We can coach product management methodologies. Or, get training at 280 Group, or Pragmatic.</li><li><strong>Industry experience</strong> — Does the candidate have applicable experience in your industry, or facet of your industry? I’ve been in healthcare most of my career. Healthcare is a HUGE category. Examples of facets from this business category are: Pharmacy, EHR/EMR, Financial, Risk Adjustment Medical Advantage, Hospital, Payer, Provider, etc. The list can go on, and on. But you’d expect that for a $4+ trillion sized market (US). There are opportunities for overlap in some areas. Likely true for your industry too. Look for them in the candidate.</li><li><strong>Natural Aptitudes</strong> — while interviewing can you envision the candidate standing in front of the teams pitching the next sprint? Do they speak fast, medium, or slow? Are they good at telling their story? Can they explain something complex they’ve worked on simply? What’s the last three books they read for fun?</li><li><strong>Fit </strong>— another soft skill assessment. I’ll leverage some behavioral questions for this characteristic (different post). Product typically owns very little but must influence a lot. “We in product get what we influence, not what we own.” <strong>Don’t hire people just like you. That is not what fit means.</strong> Would you like to have a coffee, eat lunch, talk sports, or professionally argue with this candidate? A co-worker once told me in a big important meeting, “…<em>no Rob, you’re wrong about that.</em>” (Hi Marion :-) ). That to me is fit. That to me is progress.</li><li><strong>Attitude </strong>— What’s the attitude of the candidate? I had an HR recruiter tell me once he frequently encounters arrogant candidates when interviewing for director and above roles. Those candidates didn’t make it past his screening calls. My assessment is that stuffs going to break. How is this candidate going to behave sitting next to you when things break at 2AM? I measure the candidate against folks I’ve worked with who have remained cool under fire when the site went down. Thank you, Claire, Q, Sri, Ed, and Max, for being those examples I compare candidates against.</li></ul><p>So, product leader what’s your model? Use mine. Cook up your own. But have a trait driven mental model when hiring. Refine it. Build questions around it. Be mostly consistent so you get repeatable results.</p><p>Stay curious!</p><p>Rob</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb39fba54060" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Only Three Reasons for Software Feature]]></title>
            <link>https://medium.com/@robw3/only-three-reasons-d4f452344ea2?source=rss-a7fef633fe8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4f452344ea2</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Robert Wallace]]></dc:creator>
            <pubDate>Wed, 16 Mar 2022 22:15:09 GMT</pubDate>
            <atom:updated>2022-03-24T19:50:58.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/78/1*GRBYiajc3XJ0oD1-Z3sUjQ.png" /></figure><p>There are only three reasons to invest your organization’s time into a chunk of software.</p><ol><li>Revenue</li><li>Retention</li><li>Cost Savings</li></ol><p>The fourth reason is “politics” but I won’t cover that here. We’d need to get beers first.</p><h3>Revenue</h3><p>You invest your organization’s time into a piece of software for revenue. As in, you’re going to make more money from the software, then building, testing, and maintaining. Makes sense no?</p><h3>Retention</h3><p>From time to time we have to add capabilities to retain our customers. Maybe a competitive response, or regulatory, or that capability that encourages the customer not to scratch somebody else’s software itch.</p><h3>Cost Savings</h3><p>Another legitimate investment of your limited calories. The cost savings can be for your organization or your customers. The more the better. Remember the cost of building, testing, and QA’ing over many years when you calculate your savings.</p><p>Be Brief, Be Bright, Be Done.</p><p>Chief Tinkerer</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4f452344ea2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>