<?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 Vincent C. Huang on Medium]]></title>
        <description><![CDATA[Stories by Vincent C. Huang on Medium]]></description>
        <link>https://medium.com/@HuangV?source=rss-36a80bef138e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8B2Vu2JfDhU_TVQj.png</url>
            <title>Stories by Vincent C. Huang on Medium</title>
            <link>https://medium.com/@HuangV?source=rss-36a80bef138e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:17:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@HuangV/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[It’s Not About the Software, It’s About the Solution]]></title>
            <link>https://medium.com/@HuangV/its-not-about-the-software-it-s-about-the-solution-aefbd589153b?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/aefbd589153b</guid>
            <category><![CDATA[great-resignation]]></category>
            <category><![CDATA[hrtech]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Tue, 10 May 2022 15:48:44 GMT</pubDate>
            <atom:updated>2022-05-10T15:48:44.681Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Finding problems you love solving lead to more innovative solutions</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n0eNkEcv81HGDWpe" /><figcaption>Photo by <a href="https://unsplash.com/es/@clarktibbs?utm_source=medium&amp;utm_medium=referral">Clark Tibbs</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Solve problems that you empathize</h3><p>More than four million people voluntarily left their job last year <a href="https://www.nemiss.news/great-resignation-record-4-5-million-people-left-their-jobs-in-november-national-international-news-wed-5jan2022/#:~:text=Great%20Resignation%3A%20Record%204.5%20million%20people%20left%20their,and%20Labor%20Turnover%20Survey%20report%20for%20November%20yesterday.">in a single month</a>. We’ve never seen this number of people leave since… well… ever. Companies are struggling to tackle not only a talent gap but a skills gap as well, and HR has been tasked with the challenge of figuring it all out. As a former interim Global Head of People, I’ve gained tremendous empathy toward HR practitioners and believe in the necessity of solving this retention problem.</p><p>I recently joined 15Five largely because of my unique experience of being an HR and Product leader. I was <strong>drawn</strong> to a company that takes a human-centered approach to its design and builds flexibility and configurations for HR, but also invests in the cycles to create a smooth end-user experience.</p><h3>Work on problems where ideation is natural</h3><p>Companies historically purchased a performance management system to help them automate and scale an existing process, like annual reviews. Today, all that is table stakes. We need to go further.</p><p><em>Our </em>approach at 15Five is to ask the HR buyer, “What are the problems you are trying to solve?”Reviews or ratings may help solve them, but there’s a rationale behind doing reviews. Measuring your team’s performance is important, but just a first step. Companies today need<strong> to take active action to retain their employees</strong>. HR no longer needs a performance management product, they need a performance transformation solution.</p><p>Sourcing problems and reframing them has allowed us to think differently about ways that HR can measure performance and also take action. We develop software that’s intuitive, easy to use, and also provides leverage for HR so that they can take on the additional strategic responsibilities that are being asked of them- helping to identify ways to improve engagement across the organization, identifying skilled managers versus ineffective ones, and inspiring people to stay longer.</p><h3>Work with people with shared mission and trusted actions</h3><p>Here at 15Five, the founders have built something different. I feel authenticity, openness, and trust-building embedded inside impactful management practices, cultural rituals, and especially our product. We are helping to evolve “performance management”, and extract so much more value out of it. We are going beyond measurement to make a meaningful improvement in how people can bring their best-self to work.</p><p>I feel <strong>fulfillment</strong> in joining a group of humans working together, doing extraordinary things, and becoming agents of transformation for our customers’ cultures as well.</p><p><em>Version originally published at </em><a href="https://www.linkedin.com/pulse/its-software-solution-vincent-huang/?trackingId=jYxgo%2BwxQx6tuPT5nR94AA%3D%3D"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aefbd589153b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning How to Lead — Lessons from a VP of Product]]></title>
            <link>https://medium.com/@HuangV/lead-with-curiosity-beaea53b184f?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/beaea53b184f</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Wed, 19 Jan 2022 19:14:42 GMT</pubDate>
            <atom:updated>2022-02-04T21:22:48.089Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Become a better leader when you adopt a learning mindset</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*28GYFSEl3XqGyK-lDjEdiA.jpeg" /><figcaption>teamLab “Story of the Time when Gods were Everywhere”</figcaption></figure><p><em>To my Springboard colleagues: Thanks for an amazing and rewarding journey for the past 3.5 years. My experience at Springboard has challenged and ultimately changed my thinking, behaviors, and philosophy. I am grateful to have joined such an exceptional team that encourages growth and learning.</em></p><h3>What I learned at Springboard:</h3><ol><li>It’s more important to <strong>make sure people are heard</strong> vs. convincing others that you’re right</li><li>We all have <strong>different biases in how we trust</strong> each other</li><li><strong>Context is more important</strong> than the decision itself</li><li>Adapt <strong>feedback across contexts and levels</strong></li><li>Big impact starts with <strong>tiny gestures of gratitude</strong></li></ol><h3>My Experience at Springboard</h3><p>I am grateful for the trust that Springboard put in me to build out the Product team and lead its growth. What started as a team of 2 has now grown to my managing teams across learning, product, design, analytics, and support. World-class investors (<a href="https://telstraventures.com/">Telstra Ventures</a>,<a href="https://www.reachcapital.com/"> Reach</a>,<a href="https://learncapital.com/"> Learn</a>,<a href="https://www.costanoavc.com/"> Costanoa</a>, and<a href="https://sjfventures.com/"> SJF</a>, to name a few) have supported us in our mission to transform 1 Million lives.</p><p>I am immensely proud of the integrated system that we’ve built to produce such amazing outcomes. Upon reflection, it’s been the journey that’s been vastly more rewarding. While I initially thought my joining Springboard was about what value I could bring, it turns out that I’ve gotten so much in return from my time here.</p><p>Unsurprisingly, Springboard, an Ed-Tech startup, has a deep culture of learning. In fact, all employees get a monthly stipend to spend on whatever learning activities they want! The journey is filled with many lessons that I know will stay with me.</p><h3>Empathy</h3><p><strong>I’ve learned that it’s more important to make sure people are heard vs. convincing others that you’re right.</strong></p><p>Springboard is filled with ambitious, mission-oriented people who care about their job and want to make an impact. When you work with people who are passionate and who care, working through conflicts can be harder because individuals are driven by both their minds and their hearts.</p><p>Product thinkers are trained to be user-centric, not only within their own work but within the company as well. The benefit of a user-centric approach with stakeholders is that it’s not just one interview; it’s an ongoing conversation where you can dive deeper.</p><p>Instead of trying to figure out how to win an argument against another or disprove their POV, spend time understanding what has led them to their point of view.</p><p><em>Tactics</em><strong><em>: </em></strong><em>Specifically, ask questions to understand their assumptions. Make those assumptions visible. For example, “Are you saying we should do this because of X?” Why is that important?” Multiple friends at Springboard recommended I read: </em><a href="https://amzn.to/3KpFpAu"><em>Nonviolent Communication</em></a><em>.</em></p><h3>Trust</h3><p><strong>I’ve learned that we all have different biases in how we trust each other.</strong></p><p>At Springboard, we give product managers, product and learning designers, and data analysts a greater latitude. Individuals often drive their own projects to completion, and managers are responsible for setting initial constraints while also providing guidance throughout the project.</p><p>Today, many managers want to empower and give up control. To do so, you need to build trust with your team — however, everyone establishes trust differently. At one of the Springboard company offsites, we learned about the <a href="https://worldofwork.io/2019/07/the-trust-equation/">Trust equation</a>. In it, I learned that we all have a dominant way by which we establish trust, whether the person has the credentials and is credible, can be depended upon, how open they are about their doubts and insecurities, and the balance between service to others/themselves. Specifically, I learned that we seek our dominant axis in others.</p><p>To strengthen our bonds, I wanted to understand my trust axis by articulating my needs and their trust axis by understanding what I needed to modulate.</p><p><em>Tactics: Identify what your dominant trust axis is by assessing relationships that were fraught and very rocky — how did you gain/lose trust. When trust has been broken, we tend to optimize on our own axis to try to regain trust. To build trust, how might you approach things differently through another axis?</em></p><h3>Context</h3><p><strong>I learned that context is more important than the decision itself</strong>.</p><p>To empower individuals to make the right calls, you want to set up an environment where there is trust and where good judgment can be made (and learned from when it’s a bad call). Good judgment is a skill that can be taught. The key is to provide sufficient context by not explaining what needs to get done but what’s driving that decision.</p><p>However, not all context is equal. Most people focus on the series of events that led to a decision. This is a recap of what happened. Instead, the context that’s most valuable is to understand the drivers that led to each point. <em>We were optimizing for X when we built this. </em>This also has the added benefit of making the change in a decision less personal.</p><p><em>Tactic: Outline your assumptions and be open about which assumptions are the weakest (and therefore need extra attention) and which needed be true for the feature to be successful.</em></p><h3>Feedback</h3><p><strong>I learned to adapt feedback across contexts and levels.</strong></p><p>Context is a great way to build empathy and learn how others have made decisions. But what’s more impactful (though less scalable) is direct feedback. Different contexts permit and need different types of feedback. One also needs to be mindful of one’s position stature. Most people wait to receive a performance review to get some feedback. To be honest, sometimes in the midst of a performance review, feedback can also be clunky if heard for the first time. At Springboard, we created different venues for feedback.</p><p>The Product Team has created different venues by which to provide feedback. For example:</p><ul><li>A show-and-tell where everyone from the Product Specialist to the VP can opt-in (I <em>voluntold</em> the leads to share the first few to prime the pump) to share current WIPs — we say, “the dirtier, the better!”</li><li>High-priority projects we have regular product reviews where leads share wins, worries, and whiffs (misses).</li><li>Product designers love feedback and run different crit both amongst the team and with me.</li></ul><p>I’ve learned that I need to be more delicate when providing feedback to a skip. Direct feedback can’t be given until you’ve established a trusting relationship. After which I will typically send bullet points right after the call highlighting strengths to encourage positive behaviors and suggest things that they might want to consider differently.</p><p><em>Tactics: I’ve found that feedback is more likely to be adopted when I frame it as something they should try next time. I’ve been experimenting with async feedback using the </em><a href="https://jackiebo.medium.com/do-try-consider-how-we-give-product-feedback-at-asana-db9bc754cc4a"><em>do/try/consider</em></a><em> framework.</em></p><h3>Gratitude</h3><p><strong>I’ve learned that to have a big impact, start with tiny gestures of gratitude.</strong></p><p>Overall, I really loved my team at Springboard. Together, we weathered a global pandemic. Together, we fought isolation and survived juggling working and kids’ remote learning. Together, we looked out and cared for each other.</p><p>I still remember when I was going through a rut and the team sent me a care package — Bonchon fried chicken. It was such a small gesture, but one where I felt seen by my peers (both that I was emotionally drained and that I can eat fried chicken all day, every day).</p><p>At Springboard, I felt both appreciated and supported.</p><p><em>Tactic: Show and express gratitude privately.</em></p><p>Our views of the world are colored by our unique experiences. Our views change as they get tested resulting in an evolution in our thinking. I’ve grown immensely over my time as I’ve been the opportunity to test, debate, teach, iterate, and evolve into a better leader and human.</p><p>Warmest.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=beaea53b184f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Review Haiku: Work Rules!:]]></title>
            <link>https://medium.com/book-haiku/book-review-haiku-work-rules-8bb36d2bc689?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bb36d2bc689</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[book-review-haiku]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Tue, 21 Aug 2018 14:11:01 GMT</pubDate>
            <atom:updated>2018-08-21T14:11:01.728Z</atom:updated>
            <content:encoded><![CDATA[<h3>Book Review Haiku: Work Rules!: Insights from Inside Google That Will Transform How You Live and Lead</h3><p>By Laszlo Bock</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/198/0*jcU8TbkG73UZKqd-.jpg" /><figcaption><a href="https://www.amazon.com/gp/product/1455554790/">By Laszlo Bock</a></figcaption></figure><blockquote>Ten steps to transform<br>Sourcing XP and research<br>People at the core</blockquote><p>Check out the book on <a href="https://amzn.to/2LbLEIh">Amazon</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bb36d2bc689" width="1" height="1" alt=""><hr><p><a href="https://medium.com/book-haiku/book-review-haiku-work-rules-8bb36d2bc689">Book Review Haiku: Work Rules!:</a> was originally published in <a href="https://medium.com/book-haiku">Book Haiku</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Product Manager’s Guide to finding Product Market Fit with our Chatbot]]></title>
            <link>https://medium.com/hackernoon/spend-time-with-your-market-if-you-want-to-find-product-market-fit-cd2b0108e572?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd2b0108e572</guid>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[product-market-fit]]></category>
            <category><![CDATA[enterprise-bots]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Thu, 16 Aug 2018 17:37:38 GMT</pubDate>
            <atom:updated>2023-05-30T23:37:31.148Z</atom:updated>
            <content:encoded><![CDATA[<h4>Lessons learned from building an enterprise ai bot</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kpa0Gi_o00H0rSfXVo6RoA.png" /><figcaption>Toy is my neighbor’s © Vincent Huang.</figcaption></figure><p>This is one of two posts sharing our learnings from launching a bot. The first was a <a href="https://chatbotsmagazine.com/a-product-managers-guide-to-building-your-first-bot-fde15ba2757d">guide to launching your first bot</a>. This second highlights lessons learned to make it a valuable experience for our users.</p><p>In 2018, we <a href="https://www.clarizen.com/bot-slack/#">launched</a> a AI Bot, an enterprise bot to help our customers manage their projects and portfolios. We launched with a single use case — the ability for a project manager to get a pulse on their project status <a href="https://slack.com/apps/A63JPUAH5-clarizen-bot">in Slack</a>. Over the past year, we systematically grew the MVP and expanded the product’s value. Reflecting over the past year, I wanted to share three insights we learned — two we learned along the way, and one that we got right — on the journey to <a href="https://hackernoon.com/tagged/product">product</a> market fit.</p><h3><strong>Insight 1: Find your evergreen product values</strong></h3><p>Admittedly, we got caught up in <a href="https://uxdesign.cc/how-to-design-a-robust-chatbot-interaction-8bb6dfae34fb">scripting the bot</a> instead of understanding the user’s goal when interacting with the bot. We had dreams of our users having conversations and our bot telling the user what they needed to do next. This resulted in user-bot conversations being step-by-step.</p><p>When I visited one of our early adopters, I noticed that the champion after a day of using the bot, was trying to type in power commands. After a cursory experience with the Bot, users wanted to get the information quickly, without having to go through the steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*M1sAoJFzqddSMDaMl2S9yQ.png" /><figcaption>Just give me what I want!</figcaption></figure><p>We got our product values wrong. As Jeff Bezos describes:</p><blockquote>You can build a business strategy around the things that are stable in time…When you have something that you know is true, even over the long term, you can afford to put a lot of energy into it.”</blockquote><p>We ended up retooling our product strategy to focus on<em> evergreen</em> product values. We ended with three core values:</p><ul><li><strong>Faster: </strong>Our users want to reach their goals faster</li><li><strong>Easier:</strong> <a href="https://hackernoon.com/tagged/learning">Learning</a> a new app is always hard. Reduce the friction from learning how to use a product by making it more intuitive</li><li><strong>More Proactive:</strong> Our users wanted to make sure that nothing fell through the cracks.</li></ul><p>For example, our users wanted the experience to be <em>faster. </em>The responsibility of the bot is to let the user accomplish their intent as quickly as possible. This manifests in two ways: user takes less steps, and speed up bot’s reaction time. The team spent hours agonizing how to reduce steps from three to two steps.</p><p>To speed up the bot’s reaction time, we starting tracking performance to prioritize where our optimization efforts should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*C2Rjpqf76Vogwbt3hWnTjw.png" /><figcaption>Figure out what’s slowing you down so that you can speed up</figcaption></figure><blockquote>Figure out what your customer will always want from the product experience and work to achieve that lofty goal.</blockquote><h3><strong>Insight 2: Use a different lens</strong></h3><p>Another missed assumption was who our growth user was. We had assumed that our core user was the Project Manager persona — after all we are a project management app.</p><p>However, while Project Managers drive strong usage, we found that our growth user was a wholly different persona. We had made the mistake of assuming that our core users were exactly the same as our web product.</p><p>Users that find more value from the Bot have a more causal interaction with our app. They were either managers that wanted some lightweight reporting to see how their teams were doing, or individual contributors who were responsible for logging their time on a project.</p><p>Turns out our sweet spot was less about being in the middle, but being at the edges:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*c12zGr2gjCYWRW_tpMh_Xg.png" /><figcaption>Your growth market may not be who you think</figcaption></figure><blockquote>Don’t assume that your core users in one platform are the same when you extend to a new channel. Apply a different lens starting from the benefits of the channel to find your core audience.</blockquote><h3><strong>Insight 3: Meet your users where they are</strong></h3><p>We’ve been able to grow the product with the help and advice from our users. What we did right was to continually communicate with our users — even those that said ‘<em>No</em>’ during the early stages. When someone ‘<em>No</em>’ to your product, its because the cost of adoption outweighs perceived value. To get them to say ‘<em>Yes</em>’ you’ll need to demonstrate that the <a href="https://hbr.org/2006/06/eager-sellers-and-stony-buyers-understanding-the-psychology-of-new-product-adoption">value is 9x the cost</a>.</p><blockquote>Customers partnered with us because of a shared vision, <br>but left because we failed to execute.</blockquote><h4>Find users who want to love you</h4><p>When searching for traction, your best users are ones that once said ‘<em>Yes</em>’ but now say ‘<em>No</em>’. Every month, we’d continue to update all users (including those who churned) in a simple monthly note on our progress. In the update, I’d include new improvements and ask a simple question. The update made them aware of what’s going on, but the question made them invested into what’s going on.</p><p>The constant communication served as feedback loops for us to recover from missed opportunities. Ultimately, we were able to find hot problems to solve and successfully execute against it.</p><blockquote>Openly and consistently communicate with former and current customers</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*ILmE9tmowiWwS8WG02N2sQ.png" /><figcaption>Ride the rollercoaster of value with your user</figcaption></figure><p>Over the last year we’ve learned a lot about how to build better team chat experiences for our enterprise user-base. This year, we’re expanding the Bot from <a href="https://slack.com/apps/A63JPUAH5-clarizen-bot">Slack</a> to <a href="https://appsource.microsoft.com/en-us/product/office/WA104381748">Microsoft Teams</a>. Our ability to find the growth market have been largely due to the following insights:</p><ol><li><strong>Find your evergreen product values</strong></li><li><strong>Use a different lens</strong></li><li><strong>Meet your users where they are</strong></li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd2b0108e572" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/spend-time-with-your-market-if-you-want-to-find-product-market-fit-cd2b0108e572">A Product Manager’s Guide to finding Product Market Fit with our Chatbot</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Product Manager’s Guide to Building Your First Bot]]></title>
            <link>https://medium.com/chat-bots/a-product-managers-guide-to-building-your-first-bot-fde15ba2757d?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fde15ba2757d</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Wed, 18 Oct 2017 16:08:06 GMT</pubDate>
            <atom:updated>2020-07-26T23:56:35.525Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MNr0DY0K_3g9oD5hL_WxDw.jpeg" /><figcaption><a href="https://unsplash.com/@agkdesign">Alex Knight</a></figcaption></figure><p>This is one of two posts sharing our learnings from launching a bot. The first was a <a href="https://chatbotsmagazine.com/a-product-managers-guide-to-building-your-first-bot-fde15ba2757d"><em>guide do launching your first bot</em></a>. This second highlights how we found <a href="https://medium.com/hackernoon/spend-time-with-your-market-if-you-want-to-find-product-market-fit-cd2b0108e572"><em>product market fit with our bot</em></a><em>.</em></p><p>So you think your company needs to build a bot, and you’ve been tasked with making it happen. This guide reflects the key decisions and questions I had to answer as the Product Manager to launching our bot in six weeks.</p><h3>TL;DR</h3><p><a href="https://docs.google.com/document/d/1noRVPg0M7VqF51qX32fFhMXL0T9SO4_NtBt2DRK1weg/edit?usp=sharing">50 questions</a> you need to answer when building your bot, which roll up to these 5 top-level questions:</p><ol><li>What’s the problem and how will you solve it?</li><li>What will the bot do?</li><li>How will you build the bot?</li><li>How will you know if the bot is successful?</li><li>How will you launch the bot?</li></ol><h3>Part 1: Set Scope and Strategy</h3><p>Your first priority is to define and articulate the scope and strategy of this product. Frankly, defining the problem and your solution should happen for all your projects, not just for bots. The questions you want to answer are: What is the problem you are trying to solve? How will you solve the problem? How will you measure success?</p><h4>What is the problem?</h4><blockquote>“Unsolved problems are where you’ll find opportunity” Peter Thiel</blockquote><p>Start with defining your problem. When you’re launching a new product, unknowns are everywhere. Defining a crisp articulation of the problem enables you to focus and align the team around the same problem.</p><p>Don’t build a bot because you think it’s the the new hot thing (because it might cool down in the <a href="https://thenextweb.com/opinion/2016/03/24/chatbots-and-chat-interfaces-fad-or-the-next-big-thing-in-tech/">next minute</a>). This can be a risk for an established business as they’re building based on trends, or “me too” play, without spending enough time on articulate a clear problem to solve. Arte Merritt, CEO of <a href="https://www.dashbot.io/">Dashbots</a>, an analytics platform for chatbots, notes that in general brand bots don’t as well as independent bots. While scoping it is critical that you spend the time spelling out your <a href="https://medium.com/@HuangV/reduce-the-ramp-tips-for-your-first-30-days-as-a-product-manager-7a04218aa62a">known knowns, known unknowns, and unknown unknowns</a>.</p><p><em>Scope the Problem<br></em>To determine the problem to solve, answer these questions:</p><ul><li>Who is it for?</li><li>Is this a pain or a desire, and where does it fit on the scale?</li><li>How many people feel this pain?</li><li>How many people have agency to act on on it?</li></ul><p>Take for example, getting stuck in hour-long traffic is really painful for many. But many people don’t have theagency to act — one can mitigate it through dynamic rerouting, like Waze, or have the authority/funds like Google/Tesla to spend a lot of money on autonomous driving. Understanding this helps to map out how difficult it may be to solve.</p><h4>How you will solve it?</h4><blockquote><em>“There are only two ways to establish competitive advantage: do things better than others or do them differently.”</em></blockquote><blockquote><em>Karl Albrecht</em></blockquote><p>With a problem in hand, the next step is to determine how you are going to solve it. What will separate your product from the competition is if you can find a unique value proposition that separates you from the pack. Three questions can help you get there:</p><ul><li>Why you?</li><li>Why now?</li><li>What do you believe?</li></ul><p><em>What is your advantage?<br></em>Start looking internally at you, your team, and your company to take log of what makes you unique. Building a bot is hard. Not only because of the development time, but because you need to find a way for the user to discover and install your bot, much less retain the user (<a href="https://venturebeat.com/2016/10/04/5-metrics-every-chatbot-developer-needs-to-track/">40% of chatbot</a> users only engage in one conversation).</p><p>Identify why you are uniquely able to solve the problem. Your strengths are your launchpad. Our bot at Clarizen is an extension of the core product’s experience. Further, we realized that a unique advantage is that we’ve had over a million users finish their projects with Clarizen, and with that knowledge, we had a competitive advantage in understanding best practices of project management at enterprise-scale.</p><p><em>Why now?<br></em>Is there urgency behind why you need to build this now? Products success can be attributed to perfect timing. Take, for example, WhatsApp or WeChat, these chat apps grew due to a window of opportunity; they provided a free alternative to having to pay SMS fees. For us, a driver is the commoditization of NLP technology. Our bot’s AI engine is run by API.ai (<a href="https://api.ai/">https://api.ai/</a>) providing the ability for project managers to type simple queries to get answers on complex projects..</p><p><em>What do you believe?<br></em>The best weapon for the product manager is having a unique point of view. The bedrock of developing a unique POV comes from deriving good, edgy hypothesis. A simple framework is this madlib:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/0*5aAqn_oZHKbtM0j5." /></figure><p>Spend 20 minutes by yourself writing as many of these sentences down as possible. Yes. 20 minutes. The first few are pretty soft. There comes a point in time, where you’ll hit a wall and run out of ideas. Keep pumping them out.</p><p>When you finish, review all the hypothesis and prioritize. A compelling hypothesis is one that if true, would have a material impact on how you design the product.</p><h3>How do you know if you have solved it?</h3><blockquote><em>“Count what is countable, measure what is measurable, and what is not measurable, make measurable”</em></blockquote><blockquote><em>Galileo Galilei</em></blockquote><p>Congratulations, you’re almost finished with the first stage. Now that you have identified a problem for a target market, and how you will uniquely solve it, you want to set some metrics in place to know if you’ve reached your goals. Many people have written about finding the right metrics (Some of my favorites: <a href="http://leananalyticsbook.com/">Alistair Croll</a>, <a href="https://news.greylock.com/the-only-metric-that-matters-now-with-fancy-slides-232474cf414c">Josh Elman</a>, and <a href="https://blog.intercom.com/finding-the-metrics-that-matter-for-your-product/">Kevin McNally/Nick Odlum</a>)</p><p>For many of us, you’re product is successful if you can find people who want to and continue to use it. Broadly speaking you can track value in either usage (engagement metrics like DAU/MAU or time spent) or happiness (NPS).</p><h3>Part 2: Define your Bot’s Scenarios</h3><blockquote><em>“You make different colors by combining those colors that already exist”</em></blockquote><blockquote><em>Herbie Hancock</em></blockquote><p>In Part 1, you’ve laid the groundwork, parameters, and strategic direction of the bot. In this section, we’ll get into the more unique aspects of development the bot.</p><h4>What are my bot’s key scenarios?</h4><p>As a business utility app, the purpose of the bot is to as quickly as possible deliver on the intent of the user. In our case, it’s to interact with project data. Prioritize scenarios based on what your target user will find most valuable.</p><p>We started with user stories, but it ended up being a bit clunky. Instead, Arie our Engineering Lead suggested, “Why don’t you just list what the user is going to ask and what they expect in return?”. Focusing on the bookends of the conversations helped us understand the trigger and the goal. This technique was also great for brainstorming with our early customers. “What would you say to the bot? And what would the bot respond?”</p><p><em>How can I prioritize my scenarios?<br></em>With all the potential scenarios that you can use, I apply a framework of which I’ve modified from <a href="https://en.wikipedia.org/wiki/Kano_model">Kano</a> to something I call the 3Ms: Must, Maybes, and Marvels (I’m a former consultant and I’m predisposed to find alliteration).</p><ul><li><strong>Must: </strong>You need to have these features. These are fundamental features that without the user will think that the product is lacking. Building a car, you probably must have a door, steering wheel, or wheels (however, there are always exceptions)</li><li><strong>Maybe: </strong>These are features that might work for you. You may have seen it in other bots. As a PM you need to critically assess the feature relative to your problem and strategy. To assess whether or not it makes sense for your bot, compare it against your hypothesis and problems you hope to solve. This will help you prioritize. You’ll consider different options whether you’re building for the car enthusiast or the dad of three.</li><li><strong>Marvel</strong>: These are the scenarios that people get excited about when they see. Some call it customer delight or aha moment. If you were to demo this to someone, you’d want to end on this to serve as the high note. This could be ludicrous speed or a dryvac built into your minivan (did I mention I own a Honda Odyssey?)</li></ul><p><em>What are some Must scenarios?<br></em>For the must category there are a few foundational elements a day bot should support. Many of them are outlined in Amir’s book (an amazing resource), <a href="http://amzn.to/2zuXOHJ"><em>Designing for Bots</em></a><em>.</em> There will be a series of scenarios that you’ll need to build for that are specific to your bot. Here’s a list of features that most bots today support — many of these features are pretty common sense and seek to nudge the user back towards the happy path.</p><ul><li>Help: Tell the user the most popular commands. We also use this is part of the FTUE flow.</li><li>Error script: While you try to avoid dead ends with your bot, you should always have a fallback error message. It’s usually a simple, “Sorry, I didn’t get that”</li><li>Feedback: When user types feedback, they can have a direct line to the product team.</li><li>Bug: User can also submit bugs (this was less for users, but something we built for our team internally while we were dog fooding it)</li></ul><p><em>How do I discover some Marvel scenarios?<br></em>Chat interfaces enable unique interactions. When the user asks the bot for information, at a base level, the bot needs to provide the answer. During the answer, the bot can also provide additional information or insight related to the user’s intent. Shailesh Shilwant, from <a href="http://kritiidesign.com/">Kritii Designs</a>, says, “Here’s what you asked for, <em>but also…”</em></p><h4>How does it flow?</h4><p>The next step is to convert the scenarios into flows.</p><p>With chat apps, users can easily go off track. Unlike web or mobile where navigation is structured, with bots users can say anything anytime. We’ve gotten random messages like, “the click of death… now on your TV!”</p><p><em>What is the Happy Path?<br></em>There some <a href="https://developers.google.com/actions/design/walkthrough">great advice</a> on how to get started. In general, start with the happy path for each scenario. The happy path is the perfect interaction and script between human and bot. I love using <a href="https://walkiebot.co/">Walkie Bot</a>to mock up these conversations. (Though I hear <a href="https://botsociety.io/">Botsociety</a> is another great tool).</p><p><em>How can things go wrong?<br></em>Practically, your users rarely follow the happy path. Invest the time to help nudge the user back to the happy path. <a href="https://developers.google.com/actions/design/walkthrough">Google</a> provides a really great, disciplined way of layering complexity on your conversation flows. Generally speaking consider the following elements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*p5wM6-3EAJJoN76y." /></figure><ol><li>Start with the <strong>happy path</strong>. This is perfect alignment between customer actions and your designed intent.</li><li>Expand to the <strong>long path</strong>. More often than not, there’s a huge gap between what you’ve designed versus what the user sees. Assume that it takes the user twice as long to get to the payoff.</li><li>Provide hints to<strong> guide the user back to its path</strong>. There are some easy ways to help the user stay within guardrails. Visually, you can use buttons or quick replies (FB Messenger and Slack supports this) to nudge them in the right direction. Additionally, you can progressively show information to the user. For example, with the <a href="https://www.clarizen.com/bot-slack/">Clarizen Bot</a>, if the user asks for a status on projects, since the bot doesn’t know which one, we segment all projects by status (Red / Yellow / Green) making it easier for them to identify which project needs their attention.</li><li>Lastly, make sure that the user can leave the current conversation flow. Whether it’s typing “quit”, timing out, or even erroring out. The bot should always allow you to exit gracefully without making the user feel guilty.</li></ol><h3>Part 3: Bot building blocks</h3><p>As a Product Manager, you set a framework and outline the questions to ask. Here are some tactical key questions we had to answer when building our Bot.</p><p><em>What should be the first channel we build on?<br></em>As a business integration bot, the strategy that we plan to pursue is a horizontal one. If our users are on Slack, we needed to build a Slack bot. If the users are on MS Teams, we will be there. Factors we considered: market, developer friendliness, growth potential, user’s attitude in trying new things.</p><p><em>What should be the Bot’s tech stack?<br></em>While this responsibility can be led by Engineering, the PM needs to approach this from a strategy and business point of view. For example, the decision to bake <a href="https://en.wikipedia.org/wiki/Natural_language_understanding">NLU</a> into the bot should be predicated on whether there’s a good value driver for it.</p><p><em>How does the bot interact with the user?<br></em>If the tech stack is the back-end, the front-end experience for the user will manifest in the bot’s personality and tone. Should the bot be silly, irrelevant, or professional? Things aren’t so clear. Prior to Slack we had always assumed the enterprise-focused apps need to be “professional”.</p><h3>Part 4: Monitor Health of the Bot</h3><p>By now, you’ve probably started building the bot and are starting to consider how to launch the bot and how to manage it once it’s live. It’ll be important to start setting up metrics.</p><p>Beyond the typical metrics like engagement or retention, there are a few bot-specific metrics you should consider:</p><ol><li><strong>Confusion Triggers</strong>: The entire funnel is wrought with ways for things to go wrong. Given this range of possible user inputs, bots often misinterpret or simply can’t determine what the user wants. Closely track when the bot responds with an “Sorry, I don’t understand”.</li><li><strong>Conversation Steps</strong>: Knowing the average conversation steps enable you to start segmenting good or bad experiences between the user and the bot. A conversation step is a single back-and-forth exchange between user and bot. Your average steps will be different depending on the type of the bot. İlker Köksal, Co-Founder of Botanalytics notes, “Utility-driven chatbots have lower average conversation steps versus entertainment-driven chatbots. Regardless of the chatbot type, conversations that either significantly exceed or fall short of the average conversation step usually indicate a bad user experience. Either a user gave up too quickly or a bot took too long to complete a user’s goal”</li><li><strong>Conversations Per User: </strong>Associated with the number of average steps is the average number of conversations per user. This indicates engagement with the bot. Köksal notes that the average conversations per month range from 1.42 to 4.79.</li><li><strong>Active vs. Engaged Users:</strong> If your bot supports both push and pull interactions, then you will want to compare the differences in how users interact with your bot. Active users will consume messages sent by the bot, whereas engaged users will respond. This is important because you can learn from users who are engaged. These are your happy users that are leaning into the experience. You will want to accommodate these types of conversations.</li><li><strong>Response Time:</strong> Know how long it takes for your bot to respond. Know the latency period between command and response. This impacts the overall user experience. You’re looking for median time as well as outliers here.</li></ol><p>Just like web and mobile analytics you have a bunch of options. You can go with 3rd party providers (Dashbot and Botanalytics) or you can <a href="https://www.getbotmetrics.com/">roll your own</a>.</p><h3><strong>Part 5: Marketing</strong></h3><p>As you get ready to launch the bot, there area few decisions you’ll need to make. Beyond the standard marketing components such as product positioning, messaging, collateral, and recruiting launch partners, there are a few bot-specific factors to consider:</p><p><em>How do you plan to raise awareness?<br></em>There are multiple ways to raise awareness from the bot. You’ve got standard marketing and social channels like Email, blog post, or twitter. Also consider product and bot specific channels like: Product Hunt, Bot Directories (like <a href="https://bots.directory/facebook-messenger">Messenger</a>’s, or general directories like <a href="https://botlist.co/">botlist</a>), and developer channels (like <a href="https://dev4slack.slack.com/">dev4slack</a>).</p><p><em>What should the bot’s name be?<br></em>The strategy and the supported use cases will help you with the name. Overall, there are 4 categories of names:</p><ol><li><strong>Branded Name: </strong>The bot inherits the company brand as the bot serves as an extension of the core product. This creates a consistent brand between the company and bot. However, it’s not really the most compelling from a marketing perspective. Further, if you plan to have more than one bot, it creates complications — what are you going to call the second Jira bot? Examples include: <a href="https://slack.atlassian.io/">Jira Bo</a>t, <a href="https://slackhq.com/slack-google-partners-at-work-13039a1010b8">Google Drive Bot</a>.</li><li><strong>Shorted Name: </strong>The bot is a play on the company’s existing brand. Much like United launching Ted as its low cost airline. Consider this strategy when you are extending the existing branding but it’s a wholly new product.</li><li><strong>Functional Name: </strong>The name perfectly describes what the bot does. A friend from South Africa told me that Americans tend to call things by their functional purpose. “It’s not a bin, it’s a trash can; not a rubber, but an eraser.” Consider this is you are considering a horizontal play and you have little brand recognition. Example: Pipedrive’s <a href="https://thehuangs.slack.com/apps/A2VG0CJAE-dealbot-by-pipedrive-crm">Dealbot</a>, Kuoll’s <a href="https://www.producthunt.com/posts/bugbot-by-kuoll">BugBot</a>, or CareerLark’s <a href="https://www.careerlark.com/">Micro-feedback</a> Bot.</li><li><strong>Person Name: </strong>Some companies will give their bot a name. Consider this strategy if you’re a B2C bot that needs personality (I’m looking at you <a href="https://poncho.is/">Poncho</a>), or your a B2B company looking to monetize the product. This also has a bit more marketing zing (for now). However, this means that you’ll need to invest marketing dollars to build out the new brand.</li></ol><p><a href="https://medium.com/hackernoon/spend-time-with-your-market-if-you-want-to-find-product-market-fit-cd2b0108e572">How we found Product Market Fit with our Chatbot</a></p><h3>Coda</h3><p>Building a bot these days is relatively easy. There are so many off the shelf pieces that have been open-sourced or free services you can readily use to get started. For example, <a href="https://dialogflow.com/">Diagram Flow </a>for our NLU, and <a href="https://www.dashbot.io/">Dashbot</a> for our baseline analytics to launch an MVP product in 6 weeks.</p><p>What will make your bot unique (especially when you are just starting out), isn’t the technology. It’s going to be how the bot interacts with the user and what it has to say. To create compelling bot interactions, start with a clear strategy, invest time in identifying and prioritizing key scenarios, map out ways to control and optimize the conversation flow, and discover how to delight the customer through tiny moments.</p><p>The second key differentiator will be your ability to find a unique data set and turn it into something that is useful for the customer. At <a href="https://www.clarizen.com/">Clarizen</a>, our customers are running thousands of projects through our platform. This means that not only can we provide a personalized experience on helping the user with their individual projects, but we can use the entire user-bases data to optimize how to get their projects done! For us the Bot is the medium by which that message can be delivered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/0*PoczhvtSY8LqvJMe." /><figcaption><a href="https://docs.google.com/document/d/1noRVPg0M7VqF51qX32fFhMXL0T9SO4_NtBt2DRK1weg/edit?usp=sharing">50 Questions by Vincent Huang</a></figcaption></figure><p>Thanks to <a href="https://twitter.com/dbreger">David Breger</a>, <a href="https://www.linkedin.com/in/drewgorham/">Drew Gorham</a>, and <a href="https://twitter.com/denykhoung">Deny Khoung</a> for reading drafts of this guide.</p><h3>Further Reading</h3><p>As this was the first Bot I worked on, I leaned heavily on the expertise, advice, and experience of others. Great resources include:</p><ul><li><a href="https://www.amazon.com/Designing-Bots-Creating-Conversational-Experiences-ebook/dp/B0723B91XD/">Design Bots: Creating Conversational Experiences</a>, Amir Shevat</li><li><a href="https://developers.google.com/actions/design/walkthrough">Crafting a Conversation</a>, Google</li><li><a href="http://www.uxbooth.com/articles/chatbox-ux-crafting-a-valuable-conversation/">Chatbot UX: Creating a Valuable Conversation</a>, Jennifer Leigh Brown</li><li><a href="https://venturebeat.com/2017/03/01/why-business-chatbots-must-understand-customer-intent/">Why Business Chatbots Must Understand Customer Intent</a>, Scott Horn</li><li><a href="https://chatbotsmagazine.com/the-bot-playbook-7bb6d181a6a9">The Bot Playbook</a>, Sebastian Krumhausen</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F58521e%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F58521e%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/c90883b0516ddbe5c59960c12a04bc64/href">https://medium.com/media/c90883b0516ddbe5c59960c12a04bc64/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fde15ba2757d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chat-bots/a-product-managers-guide-to-building-your-first-bot-fde15ba2757d">A Product Manager’s Guide to Building Your First Bot</a> was originally published in <a href="https://medium.com/chat-bots">Chatbots Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Review Haiku: Intercom on Jobs-to-be-done]]></title>
            <link>https://medium.com/book-haiku/book-review-haiku-intercom-on-jobs-to-be-done-daccc9c4ac0d?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/daccc9c4ac0d</guid>
            <category><![CDATA[ebooks]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[haiku]]></category>
            <category><![CDATA[ebook]]></category>
            <category><![CDATA[jtbd]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Sat, 29 Jul 2017 15:48:53 GMT</pubDate>
            <atom:updated>2017-07-29T15:49:36.907Z</atom:updated>
            <content:encoded><![CDATA[<p>By Intercom Team</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*hV-hkZcRSgVg5zxyGoiQVw.png" /></figure><blockquote>Build around struggles</blockquote><blockquote>Get your product hired, by</blockquote><blockquote>Using this framework</blockquote><p><a href="https://www.intercom.com/books/jobs-to-be-done">Intercom on Jobs-to-be-Done</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daccc9c4ac0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/book-haiku/book-review-haiku-intercom-on-jobs-to-be-done-daccc9c4ac0d">Book Review Haiku: Intercom on Jobs-to-be-done</a> was originally published in <a href="https://medium.com/book-haiku">Book Haiku</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Book Review Haiku: Chaos Monkeys — Obscene Fortune and Random Failure in Silicon Valley]]></title>
            <link>https://medium.com/book-haiku/book-review-haiku-chaos-monkeys-obscene-fortune-and-random-failure-in-silicon-valley-31be62a05eab?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/31be62a05eab</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[haiku]]></category>
            <category><![CDATA[silicon-valley]]></category>
            <category><![CDATA[book-review-haiku]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Mon, 26 Dec 2016 00:28:31 GMT</pubDate>
            <atom:updated>2016-12-26T00:28:31.177Z</atom:updated>
            <content:encoded><![CDATA[<p>by Antonio García Martínez</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/334/1*HEY0IMujznQcY0BycjFoRw.png" /><figcaption>Antonia Martínez, “Chaos Monkeys”</figcaption></figure><blockquote>PM’s lone story<br>of startup, FB, valley<br>life. egos, aplomb</blockquote><p>Check out the book on <a href="http://amzn.to/2hlKezy">Amazon.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31be62a05eab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/book-haiku/book-review-haiku-chaos-monkeys-obscene-fortune-and-random-failure-in-silicon-valley-31be62a05eab">Book Review Haiku: Chaos Monkeys — Obscene Fortune and Random Failure in Silicon Valley</a> was originally published in <a href="https://medium.com/book-haiku">Book Haiku</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Ways Your Strategic Planning Process Could Fail]]></title>
            <link>https://medium.com/@HuangV/5-ways-your-strategic-planning-process-could-fail-113de0d93677?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/113de0d93677</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[goals]]></category>
            <category><![CDATA[strategy-execution]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Tue, 15 Nov 2016 17:00:17 GMT</pubDate>
            <atom:updated>2016-12-27T17:58:08.467Z</atom:updated>
            <content:encoded><![CDATA[<h4>Common reasons why companies can’t complete their strategies</h4><p>As a Product Manager for a product that helps companies bridge <a href="https://blog.betterworks.com/dear-strategy-meet-execution/">strategy and execution</a>, I’ve had multiple candid conversations with CEOs and COOs around their ability to execute against their strategies. While over <a href="https://www.cebglobal.com/innovation-strategy/strategy/strategic-planning.html/">50%</a> of the time companies spend on strategic planning is wasted, I’ve noticed 5 common pitfalls that ruin those perfect strategies:</p><h4><strong>1. You don’t reduce your strategy to 3–5 top priorities</strong></h4><p>Only <a href="https://hbr.org/2015/03/why-strategy-execution-unravelsand-what-to-do-about-it?utm_campaign=Socialflow&amp;utm_source=Socialflow&amp;utm_medium=Tweet">55%</a> of middle managers can name any of their company’s top priorities. When you have too many priorities, it becomes difficult for different employees and divisions to focus on what’s most important. In turn, this often causes misalignment and an unengaged workforce.</p><p>Narrowing your number of top company priorities to 3–5 ensures everyone in the company — from executives all the way down — is clear on what to focus on. Having a handful of priorities is useful in and of itself because it’s easier to communicate and easier for people to remember.</p><h4><strong>2. You don’t identify what success looks like (hint: it should be measurable).</strong></h4><p>Companies often set a strategy but don’t quantitatively define what success, or achieving that strategy, looks like. Yet, different department heads don’t always speak the same language. Defining what success means — for instance, increasing NPS by 10 points — and making it transparent across the company decreases the chance of misunderstanding and creates a clear and unambiguous battle cry.</p><p>Without these quantitative definitions of success, employees don’t want to commit to the company strategy because they don’t know what drives it. Success should be defined with measurable key results (think <a href="https://rework.withgoogle.com/guides/set-goals-with-okrs/steps/introduction/">OKRs</a>!) and progress metrics that employees can focus on.</p><h4><strong>3. There isn’t clear accountability and ownership of initiatives.</strong></h4><p>A lot of the time, employees don’t know which key results and initiatives they are responsible for working on. This happens when there is a lack of transparency across the company and no one can see what others are working on. In turn, employees become disengaged and unmotivated because they don’t feel accountable for their own goals. As a result, initiatives don’t get finished and progress can’t get measured.</p><p>Instead, what you need to do is get people committed to first step initiatives by the first quarter of the new year. We could all take a page from Apple’s book, where the secret to developing great products is having <a href="http://thenextweb.com/apple/2012/01/24/this-is-how-apples-top-secret-product-development-process-works/">clear owners for each step</a> of their new product development process.</p><h4><strong>4. You don’t resource your strategic priorities.</strong></h4><p>So, you’ve set your vision for 2017…now what? It’s great you’ve created your strategy, but don’t forget that if your priorities aren’t resourced, nothing really changes and you can’t make progress on activities that matter<strong>.</strong></p><p>While it’s obvious you want your strategy to be executed, you need to give it the opportunity to be executed by resourcing your priorities. That includes budgeting, staffing and monitoring progress on initiatives throughout the year. Additionally, before the new year and continually throughout, you should eliminate activities and behaviors that don’t support the new strategy.</p><h4><strong>5. You don’t spend the time to ensure that your groups are aligned.</strong></h4><p>According to an <a href="https://hbr.org/2015/03/why-strategy-execution-unravelsand-what-to-do-about-it">article in HBR</a>, when asked to identify the single greatest challenge to executing their company’s strategy, 30% of managers cite failure to coordinate across units, making that a close second to failure to align. Often, there’s misalignment because executives don’t involve the business unit early on, and there’s a lack of communication across the company.</p><p>For example, horizontal misalignment occurs when strategies come into conflict. Take a common objective of improving profitability. A supply chain executive might think to decrease the company’s COGS by employing a fast following strategy. On the flip side, the R&amp;D executive believing in first mover advantage might promote a more aggressive new product development schedule. There’s horizontal misalignment with two completely different, non-collaborative solutions to the top strategy.</p><p>Another common issue is vertical misalignment, when a company can end up either over indexing on one priority or having conflicting strategies. For example, a supply chain executive seeking to lower production costs may over emphasize on lowering inventory costs, which gets translated to having plants ship more, which translates to speed. Focusing only on speed may forget about quality. While the plans might improve speed at the cost of quality, it could ultimately lead to increased production costs to manage the lowering quality.</p><p>I hope these indicators help you as begin your strategic planning. While it’s great to create your vision for the new year, it’s important to understand — and avoid — these common pitfalls if you’re going to execute effectively.</p><p><em>Ping me if you’d like to discuss and share how your company approaches strategy and execution. Originally published at </em><a href="https://blog.betterworks.com/5-ways-2017-strategic-planning-process-fail/"><em>blog.betterworks.com</em></a><em> on November 15, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=113de0d93677" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons learned setting goals at a goal setting company]]></title>
            <link>https://medium.com/@HuangV/lessons-learned-setting-goals-at-a-goal-setting-company-7084e8c64365?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7084e8c64365</guid>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Wed, 08 Apr 2015 16:30:09 GMT</pubDate>
            <atom:updated>2016-12-29T22:33:57.479Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*wm2jvJFGHAYzx_5AXUEcrA.jpeg" /><figcaption>Francisco Antunes</figcaption></figure><p>I work at a company that helps companies set goals. As a company that <a href="http://blog.betterworks.com/champagne/">drinks our own champagne</a> (our term for dog fooding), goal setting is important to us and the entire company sets quarterly goals. However, nobody tells you before you start that setting goals is <strong><em>really, really hard</em></strong>.</p><p>I try to take a few minutes to reflect on their goals at the end of the quarter. Reflection is important because: 1) helps us learn, 2) helps us write better goals, and 3) helps us communicate to the rest of the team how we did.</p><blockquote>We do not learn from experience…we learn from reflecting on experience.</blockquote><blockquote>John Dewey</blockquote><p>This is what I’ve learned from reflecting on how I set goals.</p><h2>First Lesson: A is not OK</h2><p>I first joined betterWorks halfway through the second quarter of 2014. I jumped straight in working towards my goals. BetterWorks was a great way to show other people what I was working on. For lack of a better term,<em> I was crushing it.</em></p><p>By our team quarterly review, I was “recognized” for my work. Blood drained from my face, the moment I heard what I was recognized for. I was recognized for 100% completion and for completed 10 of my 10 goals. A.k.a. I had <strong>sandbagged my goals</strong>. I had not stretched enough the first few months.</p><h4>Lesson Learned: You’re sandbagging your goals if you can easily reach 100% by the end of the</h4><h3>Second Lesson: Being everything is being nothing</h3><p>Vowing not to repeat myself and to stretch myself, I rejiggered how I created goals. I created a series of objectives aimed at 4 pillars I thought I needed to work on: improve efficiency and effectiveness of our product development, achieve product adoption targets, improve product quality, and instill data driven decision. I had goals that touched project management, product management, quality, and data analytics.</p><p>However, in trying to do a bit of everything, I ended up not doing anything well. John Doerr talks about one of the key benefits of the OKR model is to “<a href="http://blog.betterworks.com/keys-okr-success-qa-john-doerr/">focus on a set of priorities</a>” <strong>My answer to developing focus was to focus on everything.</strong> Wrong Answer.</p><h4>Lesson Learned: You goals should reflect your core focus. Your goals shouldn’t represent everything that you do, but represent what you deem as most important.</h4><h2>Third Lesson: Do your goal push-ups</h2><p>They say that time waits for no one, and surely time didn’t wait for me in a few of my quarters. I got too busy and didn’t spend the necessary time thinking about my goals. My goals ended up being a collection of goals cascaded down from people in the organization. I blindly accepted goals assigned to me.</p><p>I hadn’t take the time to push up some goals<em> </em>that<em> I felt were important</em> to drive business results. My goals became a list of deliverables. Because they were items that needed to be done, my goals quickly devolved into a list of tasks. It became a rout <strong>check-the-box exercise; </strong>I simply tried to get through as my items as fast as possible. While I completed my tasks, I felt that I added no additional value to the org and felt like a robot. I realized that when I work and define goals with my peers, I<strong> acquire a sense of ownership in the goal.</strong></p><h4>Lesson Learned: Goals need to be both top-down and bottom-up. Be proactive with your goal setting conversations.</h4><h2>Lesson Four: Communicating progress</h2><p>Before the new quarter rolled around, I sat down to define the goals I thought were important. After picking up some goals that aligned with our top company goals, we used both lists to form my goals. I ended up with some big, audacious goals. As we are nearing the end of the quarter, I’m starting to review and reassess my goals and have come to the realization that while my goals have a lot of protein and weight, they weren’t chunked out into smaller pieces. Chunking wasn’t about breaking things into small tasks — every Monday I set a weekly goal for myself based on my quarterly goals, but it’s about communicating and updating my progress to the rest of the team. <strong>Often goals are owned by an individual, but work is completed by teams</strong>. Successfully completing a goal isn’t only about completing the goal, but enabling those who need to be consulted in informed of your progress.</p><h4>Lesson Learned: Break down your goals so you can be more agile. Frequently communicate any progress of your goals to your stakeholders</h4><h3>What have I learned?</h3><p>Good goal setting isn’t intuitive. It’s easier for us to think about what to do today as opposed to what’s the most important thing that needs to be done. This requires us to deliberately focus on what should be done, not casually do what is in front of us. Nobody is perfect, this requires constant iteration and practice. One needs to continually set, do, reflect.</p><p>Takeawys:</p><ol><li>You’re sandbagging your goals if you can easily reach 100%.</li><li>You goals should reflect your core focus. Your goals shouldn’t represent everything that you do, but be what you deem as most important.</li><li>Goals need to be both top-down and bottoms-up.</li><li>Goal setting should be a conversation with multiple stakeholders within the org.</li><li>Break down your goals so you can be more agile.</li><li>Frequently communicate progress of your goals to your stakeholders.</li></ol><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/lessons-learned-from-year-setting-goals-goal-company-vincent-huang?utm_content=buffer7d94a&amp;utm_medium=social&amp;utm_source=plus.google.com&amp;utm_campaign=buffer"><em>www.linkedin.com</em></a><em> on April 8, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7084e8c64365" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Everything We Know About Drucker’s Vision for MBOs May Be Wrong]]></title>
            <link>https://medium.com/@HuangV/why-everything-we-know-about-drucker-s-vision-for-mbos-may-be-wrong-f42770d39db6?source=rss-36a80bef138e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f42770d39db6</guid>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Vincent C. Huang]]></dc:creator>
            <pubDate>Tue, 24 Mar 2015 13:11:23 GMT</pubDate>
            <atom:updated>2016-08-08T15:01:07.614Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever sat through a management course, you probably remember the name <a href="http://www.druckerinstitute.com/">Peter Drucker</a>.</p><p>Credited as the father of Management by Objectives (MBOs), Drucker’s 1954 book, <a href="http://www.druckerinstitute.com/peter-druckers-life-and-legacy/books-by-drucker/"><em>The Practice of Management</em></a> was the first to consider management as a whole and being a manager as separate responsibilities. Harvard Business Review says, “His writings are landmarks of the managerial profession” while the Wall Street Journal calls him “The dean of this country’s business and management philosophers.”</p><p>In <em>The Practice of Management</em>, Drucker outlined a process in which both management and employees would agree upon the objectives of an organization. When this happened, he believed, organizations would become more effective.</p><h3>What Companies Rolled Out</h3><p>Companies took note and began instituting annual (or quarterly) MBOs in modern business settings that had executives creating objectives and sharing them with their departments or business units — giving everyone a shared target. Then the work employees did to reach the goals was monitored. If the target objectives were achieved, performance was rewarded and management set new objectives for the next cycle.</p><p>Across industries, executives adopted MBOs hoping to promote maximum productivity, expecting that if employees knew what goals they were trying to reach, they would work more diligently toward them. Yet what we’ve seen over time is that MBOs have become mainly top-down, executive instruments. Most are hierarchically driven to cascade goals down from top management with few, if any, factoring in individual employee input upward.</p><p>This isn’t exactly what Peter Drucker had in mind. While his vision of MBOs included objective setting, a significant and important element of his thinking was omitted in how businesses translated his process.</p><h3>The Part We’ve Been Missing All These Years</h3><p>Drucker’s vision for MBOs included a discussion of self-control, which he believed was critical to how employees accomplish tasks. The value of self-control in the MBO process is that employees get to control their own performances. For Drucker, self-control would lead to stronger motivation and better performance because individuals would have a desire to do their best rather than good enough.</p><p>It’s human nature to want to control our own destiny and Drucker understood this. When goals are given to employees from the top down, individuals aren’t as motivated to achieve them as they are when they’ve been involved in the process of deciding the goals from the start.</p><p>At <a href="http://www.betterworks.com/">BetterWorks</a>, we’ve taken Drucker’s missing organizational management tenet to heart. We recognize the value of applying goal management and self-control in one solution so organizations can empower individuals and in turn, gain a more motivated, autonomous workforce. One of the most obvious ways we are advancing this idea is in enabling employees to easily set, track and manage aspirational goals.</p><h3>Self Control Leads to Stretch Thinking</h3><p>Drucker believed managers must take risks and allow risk-taking decisions to take place at lower levels in the organization. This would require that employees at different levels of an organization have a say and some control over what objectives were being targeted and met. Drucker wanted employees to push one another and stretch to accomplish goals. We couldn’t agree more.</p><p><a href="http://blog.betterworks.com/okrs-stretch-or-not-to-stretch/">Stretch thinking</a> — among low and high performers — yields positive business rewards. It can uncover new ways of doing business (e.g., opening new markets) and drive types of disruption and innovation never thought possible. Aspirational (or stretch) goals even provide learning experiences in times of failure.</p><p>But stretching doesn’t just benefit a business; it also motivates employees and increases achievement and accountability. It fosters increased communication because more people work together — typically within and across departments — to make stretch goals a reality.</p><h3>BetterWorks Supports Aspirational Goals</h3><p>With the addition of self-control to MBOs, Drucker offered a powerful solution to align businesses. Our enterprise goals platform is <a href="http://blog.betterworks.com/aspirational-goal-setting-at-work/">helping companies make his vision for success a reality</a> by providing transparency and accountability. Within BetterWorks, everyone in the organization — bottoms-up, top-down, and across the organization — can set and manage goals. They can also support peers through social engagement (e.g., comments, nudges, and cheers) and self-assess performance against measured outcomes.</p><p>Organizations can set up goal scoring in our platform to work the way that makes the most sense for their employees — numbers or even smiley faces — keeping individuals inspired, up to date, and in sync toward objectives. Because we believe “a connected team is an engaged team,” BetterWorks helps organizations cut the time and effort it takes to do annual performance evaluations by providing real-time data about how work gets done.</p><p>If businesses had equally applied Drucker’s vision for goals with his vision about self-control, MBOs might still be the preferred management methodology. Because they haven’t, organizations are looking to evolve their current processes to achieve better alignment and accountability. We hope Drucker would be pleased with how our platform is steering them back toward his original vision.</p><p>Do you agree? We’d love to hear your thoughts below.</p><p><em>Originally published at </em><a href="http://blog.betterworks.com/druckers-vision-for-mbos/"><em>blog.betterworks.com</em></a><em> on March 23, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f42770d39db6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>