<?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 Scott Brady Drummonds on Medium]]></title>
        <description><![CDATA[Stories by Scott Brady Drummonds on Medium]]></description>
        <link>https://medium.com/@drummonds?source=rss-f3b4de0c2acf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s2WvUeTM89C49hyk8xjRDA.jpeg</url>
            <title>Stories by Scott Brady Drummonds on Medium</title>
            <link>https://medium.com/@drummonds?source=rss-f3b4de0c2acf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:22:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drummonds/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[CIOs: is there a gorilla in your midst?]]></title>
            <link>https://drummonds.medium.com/cios-is-there-a-gorilla-in-your-midst-83b4b7fcec6f?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/83b4b7fcec6f</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Thu, 14 Jan 2021 02:19:45 GMT</pubDate>
            <atom:updated>2021-01-14T02:20:41.394Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally </em><a href="https://www.linkedin.com/pulse/cios-gorilla-your-midst-scott-drummonds"><em>posted on LinkedIn</em></a><em> in mid-December.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eo1csjZVhOH-2sN4EFPNhw.jpeg" /></figure><h3>Enterprises are amassing truckloads of data every day — are you realizing its full value?</h3><p>Question: do you recall <a href="https://www.open.edu/openlearn/ocw/mod/oucontent/view.php?id=88410&amp;section=_unit4.1.1">‘The Invisible Gorilla’</a> video doing the rounds a few years back? Six people are passing basketballs to each other and your job — the viewer — is to keep count of the number of passes made by those wearing white shirts. At the 0.26 mark, a person dressed in a gorilla costume strolls on screen, beats their chest and wanders off nine seconds later.</p><p>A Harvard study found that 50% of viewers didn’t notice the gorilla.</p><p>The point? 1. We’re missing a lot of what goes on around us and 2. We have no idea that we’re missing so much.</p><p>It reminds me of Google’s origin story: in the late ’90s Larry Page and Sergey Brin figured out they could conquer the internet’s sprawling sea of information by ranking search results according to popularity and selling ads associated with search keywords. But the major success came in 2003 from one simple insight that had, until the acquisition of Pyra Labs, been ignored: capturing and analyzing the data it collects from you and me as we browse, fueling its advertising dominance.</p><p>They were sitting on mind-boggling amounts of data for <em>quite some time</em> before the financial light bulb went off.</p><p>What would you do if you suddenly realized there’s been a guy in a gorilla suit hiding in plain sight in your company? If you’re anything like ServiceNow’s brilliant Advisory Solution Consultant <a href="https://www.linkedin.com/in/luke-miller-b7486123/">Luke Miller</a>, you tame it. Then you unleash it on your customers.</p><p>About six months ago I heard of Luke’s awesome experiment. He’d partnered with a customer to run ServiceNow’s machine learning (ML) technology against their own data. This capability is embedded in many ServiceNow products, but it’s exposed through the UI for clever customers’ experimentation. Luke had found it a side hustle: running ML on all customer incidents to dive deeper into what was going on.</p><h3>Is your data earning its keep?</h3><p>Enterprises amass significant amounts of meaningful (and useless) data daily, as employees and customers interact with systems and processes. I’m not talking about personal details — rather, the repetitive queries and actions individuals and teams undertake to get their job done. Massive swaths of information, captured and stored.</p><p>For example, in a single day, an employee might raise multiple cases across different departments: IT requests (“please order me a new hard drive”); IT incidents (“I can’t log in”); Human Resources (“my new starter needs to sign a contract”); Customer Service (“I’m at home and my internet has gone down”).</p><p>It’s seriously rich data and, frankly, most enterprises do nothing with it.</p><p>Luke had devised a sort of ‘test’ that would use ML to look for patterns in the data. Those patterns would represent automation the organization was inadvertently overlooking in its operations and spotlight unnecessary duplication. Here was the convergence of an untapped challenge that could be solved by applying existing technology in a new way. Luke saw the potential, so Solution Consulting management, and a major airline, did too.</p><p>The result was a list of insights revealing huge wastes of employee time and effort: manual, people-run processes that could have easily been automated — like password resets; repeat queries that could have been solved for the customer on the first interaction; common employee requests absorbing huge amounts of the Service Team’s, which could have been addressed with virtual agent support; IT issues bouncing from one person to the next, without prioritization or use of knowledge management.</p><p>It was a revelation for three reasons:</p><ol><li>These findings represented a raft of ‘quick wins’ just sitting there, waiting to be realized.</li><li>The airline already had the ability to automate most of these requests with minimal investment.</li><li>This translated into an immediate US$3m bottom line saving in productivity!</li></ol><h3>Get your gorilla: turn idle info into bottom line savings</h3><p>Technology teams have played a pivotal role in the global pandemic response, supporting employees to migrate work from the office to home almost overnight. While workplace debate continues about the post-COVID ‘new normal’, 87%* of APJ executives have flagged cost savings as a result of changes to company operations. With market conditions set to tighten into 2021, executives are looking to find efficiencies at every corner.</p><p>We’ve since applied Luke’s program with upwards of 60 customers, including a major Australian energy company, large telco player and retail giant, and delivered similarly impressive results and savings. As organizations move into planning and strategy season, now is an ideal time for CIOs to lead conversations and education around how intelligent technology can extract much greater value from the idle information at your company’s fingertips.</p><p>Referring to a powerful automation and AIOps tool as “running a simple test” may sound like it’s trivializing a complex operation, but Luke’s innovation has proven otherwise — in a matter of hours. You’re simply mining your own data for competitive edge. Just like Google.</p><p>Is your company ramping up digitization efforts to support an increasingly distributed workforce? What are the odds there’s a gorilla or two lurking in your data vault?</p><p><em>* Source: </em><a href="https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/other-document/the-work-survey-by-servicenow-research-summary.pdf"><em>The Work Survey by ServiceNow</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83b4b7fcec6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Four Judges of the Platform of Platforms]]></title>
            <link>https://drummonds.medium.com/the-four-judges-of-the-platform-of-platforms-37856e42b225?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/37856e42b225</guid>
            <category><![CDATA[it]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[platform]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 08:26:56 GMT</pubDate>
            <atom:updated>2020-08-11T08:33:17.644Z</atom:updated>
            <content:encoded><![CDATA[<p>ServiceNow aspires to become the defining software company of the 21st century. To do this, we are deploying in our customers <em>the platform of platforms</em>. Our platform, the <a href="https://www.servicenow.com/now-platform.html">Now Platform</a>, will unite many systems of record, the best of breed solutions, the worst of merger products, and every employee with a single, elegant, system of action.</p><p>But many vendors provide platforms that deliver value to their customers. How will this be different?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*03xfKuBtj8W0E-eA" /><figcaption>Photo by <a href="https://unsplash.com/@safesolvent?utm_source=medium&amp;utm_medium=referral">Martin Reisch</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We will use a model to measure our success at earning the “platform of platforms” title. In this model, four judges will each vote on whether ServiceNow has met their needs. Customers do enjoy a solution with only partial agreement from the four judges. But the “platform of platforms” accolade comes only by way of unanimous consent.</p><p>Let’s introduce the four judges:</p><ul><li>The <em>judge representing the company leader</em> (the CEO, COO, or delegate). This person speaks for the general state of the business.</li><li>The <em>judge of the functional leader</em> decides on behalf all department leads: CHRO, CIO, CFO, etc. This person can measure software capability against business requirements.</li><li>The <em>judge of the IT practitioner</em> represents enterprise architects, platform owners, and other IT experts.</li><li>The <em>judge of the user</em>. This judge will decide if user experience is satisfactory.</li></ul><p>As with any judge, these four will use clear criteria. We know today the people these judges represent and we succeed in varying degrees to win their trust. To focus our effort to win the platform of platform designation, I’ve documented the success criteria and measurements we’ve seen these personas use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFoEvArCQlwydJTSMqmcFw.png" /><figcaption>Judges: who they are, what they want, and how to engage them</figcaption></figure><p>In my experience, winning the vote of the judge of the company leader is fairly straightforward. Our Value Management team without fail are able to demonstrate the platform’s value. ServiceNow’s sales teams are excellent at winning the vote of the judge of the functional leads. The platform’s capabilities are incredible and our sales teams excellent. But it is the two judges of the IT practitioner and user, I believe, that require more attention.</p><p>When solving IT problems for IT people, ServiceNow is a recognized leader. But to be the platform of platforms, we need to help IT people solve enterprise-wide problems. ServiceNow’s solution consulting team are leading a project (Popiah, denoted with an asterisk above) to improve the way we collaborate with our customers on cross-functional, multi-department solutions. We’re building reference architectures that work for industry verticals. And we’re designing solution patterns to simplify the interconnection of systems. We lead free innovation workshops to help the customer see the potential of the platform.</p><p>For the user, to truly make the world of work work better for people, we have invested in a design-thinking presales team. This group collaborates with customers on design workshops to ensure the experience meets expectations. I’ve come to believe the user experience is arguably the most important part of the platform of platforms. An unused platform has zero value. And people will avoid an experience they dislike.</p><p>This is our evolving framework to earn the title platform of platforms. If we can get this right, if we can deliver enough value to these four judges representing entire companies, I believe we can become the defining software company of the 21st century.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37856e42b225" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Value of Value Discussions]]></title>
            <link>https://drummonds.medium.com/the-value-of-value-discussions-4ba78e71813e?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ba78e71813e</guid>
            <category><![CDATA[it]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[value-management]]></category>
            <category><![CDATA[servicenow]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Sun, 16 Jun 2019 09:18:36 GMT</pubDate>
            <atom:updated>2019-06-16T09:34:23.928Z</atom:updated>
            <content:encoded><![CDATA[<p>One behavior common to successful sales and presales professionals is comfort discussing their solution’s economic value with relevancy to the customer. Discussing value early helps the customer and vendor align on the budgetary scope of the project. It helps the customer disqualify overly ambitious vendor proposals. And it helps the vendor disqualify projects that cannot justify the cost of sale.</p><p>I have developed in my roles in sales and presales a three-tier system for discussing value with customers. I’ve discussed this with the more senior solution consultants and value management engineers at ServiceNow and want to share here.</p><h3>Tier 1: Throw a Pebble</h3><p>One of the easiest ways to start a value discussion is to throw a number out. I liken this to the old movie trope of throwing a pebble at a window. It will get your customer’s attention. It may surprise them a little. And rarely it will provoke the wrong kind of reaction. But in my experience all outcomes can be handled to move forward with the engagement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JQ7aXrXL0XIzUhH_rOb5tw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@hannahdickens?utm_medium=referral&amp;utm_campaign=photographer-credit&amp;utm_content=creditBadge">Hannah Dickens</a>.</figcaption></figure><p>On the value front, my pebble is simply a number. A provocative but reasonable estimate to gauge the size of the project from the customer’s perspective. I would throw this pebble by saying something like, “this sounds like a $2m problem to you. Do you agree?” A similar approach would be: “Last customer I worked with on this took $5m of cost out of their business. Are you expecting the same?”</p><p>Sales and presales professionals early in their career are often afraid of this topic. But believe me it is liberating for both parties to put a number into play early. There is nothing more frustrating to customers and vendors alike than to discover after months of discussions that the vendor’s solution is 10x more expensive than the customer’s budget.</p><h3>Tier 2: Create a BVA on a Napkin</h3><p>Business Value Assessments (BVAs) offer detail to the value claim. And, when meeting a customer for coffee, a simple BVA on a napkin is the right amount of detail for early discussions. When the pebble grabs the customer’s attention, the napkin BVA frames the proposal in very rough numbers. It can show the customer exactly how the solution could save them money without fussing over too many details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g1puaC4v8NxTfUtLUXlkeA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@readysetfreddy?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Freddy Castro</a>.</figcaption></figure><p>By far the two easiest inputs to a napkin BVA for software licenses are the current license, support, and subscription costs and expected productivity gains. Here is an example using only those numbers:</p><ol><li>“You’re currently using vendor A for this problem and spending $100k per year.”</li><li>“In addition to replacing vendor A, we think our solution will allow you to retire vendor B, who costs you $200k per year.”</li><li>“The four people using your current solution will be twice as productive with our solution. We estimate each person is paid $100k per year so this means another $200k savings for you.”</li></ol><p>Ergo, this solution should provide $500k worth of value to the customer.</p><p>The napkin BVA is much more consultative than the pebble. It helps the customer understand the vendor’s view of their software. It documents real numbers. And it gives the customer a chance to object or correct vendor misunderstandings.</p><p>From the side of the sales team, the customer’s reaction can provide great insight into how the customer views the vendor. Customers that entertain these discussions trust their vendor and value their insights. Customers that refuse to parley consider the vendor nothing more than a commodity broker. Difficulties will follow.</p><h3>Tier 3: Build a BVA</h3><p>Every vendor has BVA tools to help customers and sales teams estimate the value delivered by a solution. These tools are so prevalent I won’t explain more about them here.</p><p>But I will say that BVAs are only valuable with a customer that has opened up through the napkin BVA and is willing to co-own the full document. A BVA “thrown over the wall” to a disinterested customer will easily be torn apart. First because the assumed outcomes (50% productivity improvement, 20% improved time to value, etc.) will be subject to intense scrutiny. And second because unique customer characteristics and perspectives confound a straightforward analysis. For instance a customer may have a special relationship with another vendor resulting in “free” (or cost neutral) IT equipment. A BVA prepared in isolation won’t reflect this and will therefore lack credibility.</p><p>And, if we vendors are to be honest with each other, half of our BVA tools produce unbelievable, biased, self-aggrandizing claptrap. Sending one of these to a customer is worse than sending nothing at all.</p><p>However, a BVA developed with a customer advocate means the advocate can help validate the BVA and justify outcomes and assumptions. Furthermore, that advocate will be present to defend the document at internal customer meetings when the vendor is not present. BVAs do wonders for customer-vendor alignment as well as fostering alignment inside a large customer.</p><h3>Optional: Build a Business Case</h3><p>Some customers require a business case to justify investments. Business cases serve a similar purpose as the BVA. But they are scoped to match the project from the customer’s viewpoint. A BVA tends to scope the economic impact from the vendor’s viewpoint. Sometimes these two things are aligned but each could include components not in the other.</p><p>Since the business case creation is initiated by the customer and unique to the customer’s business, I’ll not generalize a recommendation here. ServiceNow is like many vendors these days in employing value management engineers that can help customers with this. Whether you work for ServiceNow or not, I recommend you use value engineers when helping customer business cases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZdObUWz8GtrK9xD1Y1X_cw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@martenbjork?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marten Bjork</a>.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ba78e71813e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being Strategic and Delivering Promises]]></title>
            <link>https://drummonds.medium.com/being-strategic-and-delivering-promises-431c53a81786?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/431c53a81786</guid>
            <category><![CDATA[it]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[presales]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Wed, 20 Mar 2019 13:20:35 GMT</pubDate>
            <atom:updated>2019-03-25T00:24:35.254Z</atom:updated>
            <content:encoded><![CDATA[<p>A presales engineer’s success is realized when delivering solutions that allow customers to achieve business outcomes. Doing this requires four steps:</p><ol><li>Understand the customer’s business initiatives and expected outcomes.</li><li>Provide a technology roadmap that will deliver those outcomes.</li><li>Agree to a business case that justifies the investment.</li><li>Document a plan to success.</li></ol><p>Good sales and presales professionals complete these by design or intuition. But let’s reflect on them for a moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_hEDASII5u7vgqJ9NH4mYA.jpeg" /></figure><h3>Business Initiatives and Outcomes</h3><p>Business initiatives are recognizable as a C-level manager’s commitments to his stakeholders and management. “Replacing outdated software” is not a business issue. “Improving employee satisfaction” can be. When an initiative’s results are quantified with KPIs I call them outcomes. As an example, a concise KPI-based outcome would be, “reduce IT outages by 10% annually”.</p><p>I met a customer last week that had not formalized KPIs for a business initiative that would use a ServiceNow solution. Luckily the ServiceNow solution consulting team have worked with dozens of customers using this solution and knew achievable KPIs associated with successful deployments. By documenting those KPIs the ServiceNow team can hold itself accountable for customer success. And the customer can show progress to his stakeholders.</p><h3>Technology Roadmap</h3><p>Business initiatives by definition cannot be addressed with a single product. They require multi-product solutions including hardware, software, services, people, and processes. Since senior executives are measured by the quarter initiatives rarely complete in less than 13 weeks. A technology roadmap must be provided to hold the owners of each component accountable for successful delivery of the entire solution.</p><p>It is a good test of a presales engineer’s status as a trusted advisor if she is invited to build that roadmap with the customer. The statement’s more powerful contrapositive is “presales engineers not invited to build a technology roadmap are not the customer’s trusted advisor.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5n8tevsZPhFAnWnJTzO3lA.jpeg" /></figure><h3>Business Case</h3><p>No business initiative is funded without a clear expectation of return on investment. Executives require this. Boards require it. Procurement teams review it. And vendors that do not see it are commodities in the eyes of the customer. Not only is it beneficial to the vendor to help build the business case, but vendors providing honest, verifiable business value assessments (BVAs) provide great value to their customers.</p><p>The key to business cases (or BVAs) it transparency and verifiability. Nothing undercuts a BVAs currency more than line items no one believes or can explain. Because claims of value rest on complex products we ask ServiceNow solution consultants to be responsible for the creation of a BVA and its defense under scrutiny.</p><h3>A Plan to Success</h3><p>I reviewed this week with one of ServiceNow’s presales engineers a joint deal plan constructed with a customer. The plan ended with “customer delivers ServiceNow an order form”. The solution consultant immediately recognized this was sales team “plan to close” and not a joint plan to deliver business outcomes.</p><p>The problem with plans to close, from the customer’s perspective, is they ignore the majority of the work. After the purchase, an enterprise IT customer may employ implementation teams, train administrators, communicate with users, build governance teams, and more. A vendor that ignores these activities is selfish and misaligned to its customer’s needs. We ask all ServiceNow sales teams to discuss and document these “post-sales” activities to ensure the customer is ready and willing to complete the steps needed to deliver the initiative’s business outcomes.</p><p>These four steps taken together will grow deal sizes for vendors, minimize customers’ project times, and maximize the chance of delivering successful outcomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xO-sVlzp7TA5AUH92ZMB8A.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=431c53a81786" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Presales Manager]]></title>
            <link>https://drummonds.medium.com/the-presales-manager-dad8d043183e?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/dad8d043183e</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[presales]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[it]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 23:07:54 GMT</pubDate>
            <atom:updated>2019-02-12T23:07:54.946Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve wanted to write this story for a while. A short talk with my manager inspired me to start. While I usually write about presales engineers, this one is for their managers. It is a challenge to every one of them to be the most they can be. To be viewed as a strategic thinker and influencer in their sales organization. And to capitalize on a unique opportunity unavailable to other employees of an IT vendor.</p><p>Presales teams are incredibly positioned within technology vendors. Part of the sales team, they are jointly accountable for sales success. As technical representatives of the company, the are the long arm of product teams wanting to understand how products serve customers. As relatively independently-minded technical professionals, they are trusted by customers with information making them the voice of the customer within the vendor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bJAfxV4qB-R6ajA8GdSKQA.jpeg" /></figure><p>Acting these parts, presales professionals are at the nexus of communication channels within the customer and between the customer and the vendor. Although we are privy to this flow of business-critical information, we sometimes fail to capitalize on its use. The opportunity cost of that failure is highest for managers. If we don’t represent the customer to our employer’s strategy owners, if we don’t explain product deficiencies to our employer’s product owners, if we don’t guide customers to make decisions in their long-term interests, everyone suffers.</p><p>Every presales manager should meet key customers at least once a year and ask the following questions:</p><ul><li>What do you like about our products?</li><li>What do you dislike?</li><li>What products/features are you using regularly? How are you using them?</li><li>Which products/features have you not adopted? Why?</li><li>How do your users describe the experience of using our products?</li><li>How do you quantify the value our products provide you?</li><li>What other vendors are providing great products that deliver great value and are capturing more of your time and money?</li></ul><p>The answers to these questions will open avenues for discussion during the client engagement and after. Let’s look at these separately from the perspective of the presales manager.</p><p><strong>During Client Meeting</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rdlnTgmSIxDx-yMrC6ivrQ.jpeg" /></figure><p>As a representative of his or her employer’s business, a the manager can immediately delegate vendor resources to address problems. At <a href="https://www.servicenow.com/">ServiceNow</a> we have a solution innovation team that can run workshops to help improve employee experience. We have business value consultants to help quantify the economic value of our solutions. We have a strategic sales team named <em>Inspire</em> that can realign ServiceNow around changing customer initiatives and ensure our products are used to the full expectation of our customer.</p><p>Managers have an authority to marshal these resources to the immediate support of the client. Their decisiveness and effectiveness will raise their worth in the eyes of the customer. The end result is a happier customer, an improved relationship between the customer and the vendor, and a plan to speed the customer in delivering its business outcomes.</p><p><strong>After Client Meeting</strong></p><p>Having delivered value to the customer during the meeting, the attending manager has the opportunity to deliver extraordinary value to the vendor after the meeting. Straight from the mouth of the customer, and at the advice of this knowledgeable manager, the vendor may now:</p><ul><li>Improve its product roadmap as a result of customer feedback.</li><li>Redesign professional services offerings to speed the customer’s deployment time.</li><li>Enhance documentation or training to assist customers in solving their own problems.</li><li>Design customer success offerings that raise adoption and deliver economic value to the customer.</li><li>Evaluate strategic partnerships to improve go-to-market plans.</li><li>Consider acquisitions to bolster solutions.</li></ul><p>IT vendors are servants to their customers’ business needs. In the realm of the vendor the voice of the customer is the king. Meetings like these make kings and queens of presales managers.</p><p><strong>But Wait, There’s More</strong></p><p>There is also personal reward for fulfilling this important need between customer and vendor. The manager will, by virtue of helping both sides, develop enduring relationships. The manager will be seen as a thought leader by the vendor. The manager will be seen as a trusted advisor to the customer. The person doing this will open for themselves a future of many career paths. The paths will be founded on a history of continuous improvement for the customer, the vendor, and themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atEsHK44oe_AWQhJKIy_KA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dad8d043183e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[High Performance Presales]]></title>
            <link>https://drummonds.medium.com/high-performance-presales-9753b424abbf?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/9753b424abbf</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[presales]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Mon, 21 May 2018 07:20:05 GMT</pubDate>
            <atom:updated>2018-05-30T05:33:29.997Z</atom:updated>
            <content:encoded><![CDATA[<ul><li>Measuring efficiency is a challenge for large sales and presales teams.</li><li>The right metrics as leading indicators can help to optimize team performance in a tight feedback loop.</li><li>I’m experimenting with this quantifiable sales process to measure effectiveness on a weekly basis.</li></ul><p>Its been one year since I returned to presales. Since joining ServiceNow I’ve learned much about our customers, our products, my teammates, and our industry. And I find myself this weekend returning to thoughts I had the week before I started. How can we quantify and optimize SE team performance? What follows is applicable to both the sales and presales teams I’ve led in the last decade.</p><p>Before we can measure a team’s effectiveness, we need to understand how to measure an individual. In the sales organization the ultimate outcome is a closed deal. And the single best metric total revenue captured. But these outcomes present two problems when managing people. First, they are lagging indicators. In long sales cycles we may not know for quarters if a team is doing the right things. Second, they are shared objectives. Shared not just by sales and presales, but also by professional services, specialty sales teams, and possibly a whole host of other professionals inside and outside the vendor.</p><p>So as managers we turn to activities: sales calls, demos, proofs-of-concept or -value, and more. Activities usually have a single person responsible for their execution. And they are realtime, measurable daily. But activities are weak predictors of outcomes. Using activities an SE delivering street corner demos will be measured as more successful than SCs that close deals without demos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UOrJMF5yBB7zBsStKCfZnw.jpeg" /><figcaption>Activities and outcomes are both important. We need a bridge from the first to the second.</figcaption></figure><p>So we need a process to accurately predict outcomes using activities. Luckily such processes are common in sales organizations. In fact sales processes are created precisely to help teams increase and accurately predict success. Furthermore, some sales systems can help quantify project health, which makes management at scale easy.</p><p>At ServiceNow we use ValueSelling from <a href="https://visualize.com/">Visualize</a>. I find much to recommend in it. Its Qualified Prospect Formula® measures a salesman’s understanding of his customer’s needs. And sales people should be building many of these formulas for various people working inside their customers. The formula instructs sales teams to:</p><ol><li>VM(D): Produce a differentiated vision match between the customer’s problems and the vendor’s solution.</li><li>V: Agree with the customer on a quantified value of the solution to business and people.</li><li>P(O): Understand people and power among the customer’s team and the roles they play during the evaluation.</li><li>P(L): Document a mutually agreed plan with the customer on how to run the project to completion.</li></ol><p>Each of these activities is measured in binary. Either it’s done (1) or its not (0). ValueSelling says the prospect is qualified only when all four activities are marked done (1). Any missing part of this formula informs a salesperson that his or her deal is at risk.</p><p>Sales managers could track the sum of the numbers to see deal progression. Engagements that stall will have an unchanged sum for a long period. And high velocity deals will quickly go from zero to four. For instance the following figure shows salesperson S1 effectively driving the deal forward in just a few weeks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4e1quhTMN-bySNvdjOKcSg.jpeg" /><figcaption>Sales person one was highly effective at qualifying the prospect in just four weeks.</figcaption></figure><p>This measurement tool works well for individuals. But I believe it can also measure team effectiveness. As each sales rep or SC completes one of these four items he “ticks the box” in that formula. A manager of of a team of four will know his individuals’ performance roughly by their tick sum for the week. And a team’s aggregate progression of all deals can be compared with other teams. In this case, a sales team generating 10 ticks a week is driving deals faster than a team with five ticks a week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIRuxPy6zaxLR_rDRQ1lKw.jpeg" /><figcaption>Salesperson two (S2) is highly effective and driving many opportunities forward. Is S3 on holiday?</figcaption></figure><p>Not all customer meetings can drive the qualified prospect formula forward. But certainly a team that drives more formulas to completion is more successful than a team that does not. Indeed, a team scoring lower against its peers in the organization almost certainly has problems with time management and activity prioritization.</p><p>As I look through the ServiceNow solution consulting (presales) team, I can use this metric to compare productivity of manufacturing in Japan to finance in Singapore. Should they have the same progression rate per person? Probably not. But if there is great discrepancy it merits investigation.</p><p>If this all sounds a bit “salesy” for an SE manager, let me assure you the same principles apply to the technical sale. An SE is more effective if customer visits flip one part of that qualified prospect formula from zero to one. A presentation should help get access to influential people (P=1). A demo should help with a vision match or to uncover value (VM=1 or V=1). SE activities can and should be viewed through the same prism as sales: time spent should be productive for both the customer and the vendor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9753b424abbf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“What Keeps You Up At Night?”]]></title>
            <link>https://drummonds.medium.com/what-keeps-you-up-at-night-49349a660b31?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/49349a660b31</guid>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[relevance]]></category>
            <category><![CDATA[presales]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Tue, 26 Dec 2017 03:53:59 GMT</pubDate>
            <atom:updated>2017-12-28T02:46:07.148Z</atom:updated>
            <content:encoded><![CDATA[<p>Last month I was listening to my colleague, ServiceNow’s solution consulting (presales) lead for EMEA. He was discussing the structure of a good consultative meeting with a customer. And laughing at bad ones. He brought up the trite sales opener, “What keeps you up at night?”</p><p>I blushed a bit because I’m sure I’ve used this in my career. The EMEA team joked about this dated, hackneyed question. Maybe it worked a decade ago. But it fails to incite a meaningful, consultative discussion.</p><p>Its not just that this question is too direct. It is also subtly demanding. Asking a customer to open a vein and pour out challenges and frustrations is a huge request. And there is no reason any human would open up completely on any issue with a sales professional. But customers do eventually share this information with their trusted advisors. Why is this?</p><p>Customers will share the kind of deep, painful fears and desires with sales people that demonstrate three characteristics:</p><ol><li>Likability.</li><li>Possession of value.</li><li>Consistent relevance.</li></ol><p>As far as being liked, some people have it and some don’t. If you have it life is probably easy for you. If you don’t have it, don’t fret. Sales managers know that some people just don’t like each other. Through underperformance or deliberate realignment you’ll find your managers will move you away from customers that dislike you to those that don’t.</p><p>Showing value is the true mark of a master. And the acquisition of knowledge, connections, and influence deemed valuable to customers is not easy. But this is why great sales people make so much money. They’ve spent decades accruing seemingly boundless resources to bring to their customers.</p><p>But it was in the demonstration of relevance that my EMEA colleagues spent so much time. In fact, we believe that account executives and solution consultants can be easily equipped to demonstrate relevance. And in doing so, may more quickly progress the vendor-customer relationship to a level that allows deep sharing.</p><p>Customers won’t appreciate the uber-direct “up at night question” any more than they’d enjoy a piece of cake smashed in their face. Customers — and all people — want to work up to that point. They will share a little but expect to gain a little. And if the sales team hasn’t had time to show value or likability, at least the team can show relevance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xDJOCpEpYCG08GuYzQleKg.png" /><figcaption>Great image from a teaching website: <a href="https://thebetterplan.org/tag/the-important-of-relevance-in-teaching/">https://thebetterplan.org/tag/the-important-of-relevance-in-teaching/</a></figcaption></figure><p>At ServiceNow we’re honing our systems to help the demonstration of relevance. This is best done by equipping every sales team with information meaningful to the customer. This can include background on the customer to show we’ve come prepared. And it can include industry-specific challenges and pains to show we understand. And it can come with insights that can actually benefit the customer. We need to build this material and train everyone to sift through it quickly.</p><p>These documents are not unique to ServiceNow. Every vendor has case studies and solution wins. Some have more than others. But I’d like to think at our still nimble size we’re working on equipping our sales teams to be more effective, more helpful, and more relevant than companies much larger than us. And I’m hopeful that our efforts will simplify the sales and delivery of ServiceNow for the years to follow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49349a660b31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“What is the difference between machine learning and automation?”]]></title>
            <link>https://drummonds.medium.com/what-is-the-difference-between-machine-learning-and-automation-68a2bdb1b279?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/68a2bdb1b279</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[it]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Tue, 21 Nov 2017 13:12:46 GMT</pubDate>
            <atom:updated>2017-11-21T13:12:46.648Z</atom:updated>
            <content:encoded><![CDATA[<p>Seemed like a simple question when it was asked. The customer sitting in front of me was earnest. In response I almost instantly launched into a treatise on machine learning. But I’ve learned that a quick answer to a simple question may miss the point. So I paused before I responded when this was asked to me this morning. I’m still not 100% sure that my answer is complete.</p><p>Machine learning (ML) is the technology <em>du jour</em> in enterprise IT. And for practitioners of AI, ML, or data science the nuance of their trade is obvious. But for hardened IT executives, courted by vendors that for decades promised rehashed technologies wrapped in new vocabulary, a straight answer from a vendor may be hard to come by.</p><p>So I provided a thoughtful response to this question. And I documented my answer when I returned to my desk. Its published here not as a statement of fact. But rather the beginning of a discussion.</p><p>Let’s start with a technology pyramid, capped by artificial intelligence, with higher tech levels built upon the capabilities provided by the techs on lower levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0-0ese4n9DTxDtM_SY_HA.jpeg" /><figcaption>Scott’s hierarchy of technologies capped by artificial intelligence.</figcaption></figure><p>Starting from the bottom:</p><p><strong>Digitization</strong></p><p>This is the conversion of non-digital, possibly analog data to digital storage. Examples are scanned images, Excel workbooks, and email.</p><p><strong>Instrumentation</strong></p><p>At this level technology is surrounding the data to observe, measure, and authenticate the flow of that information between people or systems. But no new insights, no derivatives, are created. This routing and control of data is foundational to the ServiceNow proposition. As a workflow automation platform, our product ensures previously digitized data is routed and transformed using custom business rules (heuristics).</p><p><strong>Analytics</strong></p><p>Here I mean the collection of tools developed by mathematicians and statisticians to derive meaningful insights from large quantities of data. These can include techniques like linear regression, decision trees, clustering analysis, and much more. Clever reporting and data presentation can justifiably be included in this level.</p><p><strong>Machine Learning</strong></p><p>ML will frequently include models based on well-know data analytics. Indeed those techniques have been understood for decades or centuries. But what makes ML unique beyond this is the ability to improve results from experience without explicit programming. This is usually done through supervised or unsupervised learning. The difference between these two is that supervised learning starts with data with known, “golden” results that can be used to test the accuracy of a model.</p><p><strong>Artificial Intelligence</strong></p><p>Measuring and defining AI is a slightly tougher exercise. The field of AI is dedicated to making computers capable of performing tasks formerly relegated to humans. This includes learning but also key human capabilities such as visual perception, language comprehension, and voice recognition.</p><p><em>So, what’s the difference between machine learning and automation?</em> ML is one part of operational automation. Each pyramid level provides automation capabilities of higher value than the ones below it. All levels except digitization provide some automation. But the automation provided at the instrumentation level (heuristics) are now so ingrained in our operations that we take them for granted.</p><p>Instrumentation includes business rules that can automate the flow of approvals. Analytics can consume vast quantities of data to produce insights. Machine learning can allow computers to act for humans when a problem can be fit to a model. And there is no limit to the possibilities of artificial intelligence.</p><p>But we are today a long way from AI rising to the standard set by our imaginations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68a2bdb1b279" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Culture]]></title>
            <link>https://drummonds.medium.com/good-culture-ad1af16b04ae?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad1af16b04ae</guid>
            <category><![CDATA[it]]></category>
            <category><![CDATA[tribes]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[servicenow]]></category>
            <category><![CDATA[asia-pacific]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 11:32:34 GMT</pubDate>
            <atom:updated>2017-11-14T11:32:34.341Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is the second half of my culture story spanning years in IT. </em><a href="https://medium.com/@drummonds/bad-culture-cd1764e76c66"><em>Part one was published last weekend</em></a><em>.</em></p><p>In recent years I’ve become a believer in the power of culture to shape business. I’m currently working for my fifth employer in 20 years and only in retrospect do I see the great differences and effects of corporate culture.</p><p>In my first months at ServiceNow I interviewed dozens of our solution consultants (presales technologists) about their perception of ServiceNow’s culture. I collected hundreds of comments and searched for themes. And then our APJ solution consulting leadership team expanded this search, synthesized the results, and documented a summary.</p><p>Nearly as important as the cultural definition of what we are, are the omissions of what we are not. It was important to me that our culture statement was not generic flattery. And also that we had understood our culture enough to disqualify cultural descriptions from other employers.</p><p>In identifying corporate culture I feel many corporations run afoul in several areas:</p><ul><li>Confusing values and culture.</li><li>Recognizing the presence of distinct cultures within a company</li><li>Being overly vague or flattering (“we love to win”, “we have fun”, “we work hard and play hard”)</li></ul><p><strong>Values versus culture</strong></p><p>Values describe what is important to an organization. Culture describes how people act in the environment. Companies strive to keep culture consistent with values in a competitive environment that occasionally rewards bad behaviors. In our culture document we wanted to tie ServcieNow values to a culture we recognized and are proud of.</p><p><strong>Recognizing sub-cultures</strong></p><p><a href="https://www.amazon.com/Tribes-We-Need-You-Lead-ebook/dp/B001FA0LAI">Seth Godin’s</a> <a href="https://www.amazon.com/Tribes-We-Need-You-Lead-ebook/dp/B001FA0LAI"><em>Tribes</em></a> explains how one person can fill roles in different and distinct groups of people (tribes). She can be a leader in one tribe, a participant in another, and an observer in a third. She will will see, work among, and be influenced by three groups’ district cultures. Similarly, an IT vendor may have different cultures between marketing, sales, and engineering. What is important to leaders is that we make sure the common corporate values are honored in the teams we build. And the culture is consistent with them.</p><p>ServiceNow’s published values are Respect, Performance, Customer Centricity, and Integrity. I was pleased to see that our bottom-up culture investigation yielded the same themes, with minor variations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*9iQlvsPVTE3gf6q29Qv3mQ.png" /><figcaption>Culture from ServiceNow’s <a href="https://www.servicenow.com/company/careers/join-servicenow.html"><em>careers page</em></a>.</figcaption></figure><p><strong>Avoiding vagueness</strong></p><p>A question I asked myself as we identified cultural themes was, “could this description match most or all of my previous employers?” Anything that produced an affirmation was rethought.</p><p>Vague value statements seem much more appropriate to me. Common to nearly every vendor is something about how important customers are. Although it should be painfully obvious, I understand how people buried deep in an organizational hierarchy can benefit from reminders to focus on the customer.</p><p>But vague culture statements have no value. Again if they aren’t likely to differentiate one company from another and they are not instructive when describing behaviors. To that end we organized in our document culture pillars and placed clear examples of the behaviors that demonstrate this culture.</p><p><strong>Conclusion</strong></p><p>So why did we do this? ServiceNow has succeeded with the culture it created. And we are rapidly growing such that new managers such as myself are quickly invited to grow their teams. A clear culture definition (with examples) helps us recognize the behaviors that got us here. It assists with interviews to ensure candidates will succeed in the organization. It suggests measurements of what good looks like when recognizing our colleagues. And it will guide us in times of uncertainty.</p><p>But its important to know that culture is not static. <a href="https://www.linkedin.com/in/larsschmidt/">Lars Schmidt on LinkedIn</a> recently wrote of <a href="https://www.linkedin.com/pulse/end-culture-fit-lars-schmidt/">The End of Culture Fit</a>. He wrote that hiring for culture is the enemy of inclusion. Companies cannot afford to hire to match the team of their last decade. But instead we must look for candidates that match our values and are “culture adds”. That way every addition to the team gets us closer to an objective <em>good culture</em>. And we can improve diversity, inclusion, and belonging to boot.</p><p>With hopes of growing our team along that vein, I present today’s culture definition of ServiceNow’s Solution Consulting team in Asia Pacific and Japan.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJF5Og9QvNVQG3XBftdZQg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad1af16b04ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bad Culture]]></title>
            <link>https://drummonds.medium.com/bad-culture-cd1764e76c66?source=rss-f3b4de0c2acf------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd1764e76c66</guid>
            <category><![CDATA[it]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Scott Brady Drummonds]]></dc:creator>
            <pubDate>Tue, 07 Nov 2017 14:01:05 GMT</pubDate>
            <atom:updated>2017-11-09T03:08:17.823Z</atom:updated>
            <content:encoded><![CDATA[<p>Do you like your job? Do you look forward to work in the morning? Are you eager to see what new problems present themselves to you each day? Think of a time you were not happy. Unhappy people’s reasons are varied and unique. But today think of what may invisibly bind them together: bad culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*TlmAaGpxi8gozJFimnue4w.png" /></figure><p>It is said that people leave managers, not companies. Perhaps obvious when corporations are viewed as the abstract entities they are. They share lofty values agreeable to most. Managers, on the other hand, are the living, breathing, acting face of the company. They represent and greatly influence their organization’s culture. And is culture, <em>values manifested in action</em>, that attracts and drives talent away.</p><p>The difference between belief (values) and action can be substantial. All companies want culture to reflect values. But we’ve all seen environments where that is not the case.</p><p>Ben Horowitz <a href="https://a16z.com/2017/03/04/culture-and-revolution-ben-horowitz-toussaint-louverture/">released last year a presentation on culture</a> where he said culture as what people do when no one is looking. Implicit here is that (1) culture describes actions born from values, not rules and (2) culture includes those actions and values common to a group. He poses thought-provoking questions to help the identify an organization’s culture:</p><ul><li>Does job title impact who is right and who is wrong?</li><li>Do you show up on time?</li><li>Do you use your own products?</li><li>Is watching what you spend important?</li><li>Do you tell the truth?</li></ul><p>No set of questions can clearly or completely identify organizational culture. But good questions shed light on the culture’s shape. Like viewing an object’s shadow instead of the thing itself. I’ll add to Horowitz’s list a few questions from my experience:</p><ul><li>Do your actions match your words?</li><li>Do you pay and promote based on merit versus experience?</li><li>How do you treat employees that are failing in their job?</li><li>Do you share information freely?</li></ul><p>But culture isn’t just corporate. National cultures infuse regional organizations to produce a strange, wonderful, or unpredictable melange. The great variety of the world’s natural cultures was investigated in a <a href="https://en.wikipedia.org/wiki/Hofstede%27s_cultural_dimensions_theory">series by Geert Hofstede</a>. He identified six dimensions of national culture that could support or conflict with corporate values and culture. For instance, what role does tradition play in decision making? How is institutional inequality tolerated? And what is the role of gender in work?</p><p>You can consider the surprising effects of culture on your own happiness with a thought experiment. Ask yourself your own commitment to honesty, punctuality, and transparency. Layer on your beliefs about tradition, authority, and individuality. Now imagine yourself in an organization where everyone’s answers were polar opposites. How could you <em>not</em> be miserable in that job?</p><p>A few years ago I was discussing with a young professional the rejection he had received for employment. The employer told him he wasn’t a cultural fit. He struggled to understand what that meant. And he didn’t understand exactly why culture mattered if he was capable of performing the job.</p><p>I think his rejection was a blessing in disguise. When I review my least favorite employers, I today know my unhappiness was a product of cultural mismatch. I was quick to label this <em>bad culture</em>. But let’s be honest: “bad” is subjective a pejorative. A better word would be different. Bad may exist but different needs to be respected.</p><p>Culture is a dynamic thing born of the actions of a collection of individuals. And while it behooves each of us to prefer organizations that match our own culture, there are great benefits for organizations to strive to stretch and shift their own culture.</p><p>More on this another day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd1764e76c66" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>