<?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 Jack Skeels on Medium]]></title>
        <description><![CDATA[Stories by Jack Skeels on Medium]]></description>
        <link>https://medium.com/@jackskeels?source=rss-235982f59e3e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YQerlV9KkOuSO1k70ePhnw.jpeg</url>
            <title>Stories by Jack Skeels on Medium</title>
            <link>https://medium.com/@jackskeels?source=rss-235982f59e3e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 12:23:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jackskeels/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Quiet Violence of Caring]]></title>
            <link>https://jackskeels.medium.com/the-quiet-violence-of-caring-d54d4879973a?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d54d4879973a</guid>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Tue, 22 Apr 2025 01:11:41 GMT</pubDate>
            <atom:updated>2025-04-22T01:11:41.410Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVyWIUvyeLO2yHIUcMWGOA.jpeg" /></figure><h4>(with apologies to Nietzsche)</h4><p>To speak is to steer.</p><p>Even the gentlest words are not free of force.</p><p>“I’m sorry you’re feeling that way” — meant as care, offered with softness — may land like shrapnel.</p><p>Because words don’t just move forward.</p><p>They ricochet through memory.</p><p>They awaken ghosts we didn’t summon, in places we’ve never been.</p><p>For the wounded, being seen can feel like being hunted.</p><p>For the unhealed, even kindness can be a trigger.</p><p>And if kindness can hurt, then what of judgment?</p><p>What of criticism, even when meant as help?</p><p>These land harder.</p><p>Sharper.</p><p>Because they ride the same path as the old harms — and the mind, always scanning, mistakes echoes for attacks.</p><p>This is the Illusion of Conversation:</p><p>— That we can mean well and be received well.</p><p>— That impact follows intention.</p><p>It doesn’t.</p><p>And yet, we speak.</p><p>Not to control, but to matter — and find ourselves tangled in the ancient machinery of cause and effect.</p><p>But peace is not found in perfecting the manipulation.</p><p>It’s not found in crafting words so precisely they leave no mark.</p><p>Peace lives deeper.</p><p>It comes from presence.</p><p>From confidence rooted in a truth:</p><p>— Our emotions, though powerful, are ours to hold.</p><p>— No one makes us feel — We feel.</p><p>And still… we keep trying.</p><p>Because conversation is not avoidable.</p><p>We are here to witness each other.</p><p>To hold space, even clumsily.</p><p>To offer light, even if it flickers.</p><p>This is what it means to be human:</p><p>— To reach for connection, knowing we might bruise each other.</p><p>— To disappoint, despite our best intentions.</p><p>And to show up anyway.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d54d4879973a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who Shattered My Workplace?]]></title>
            <link>https://jackskeels.medium.com/who-shattered-my-workplace-95665a073c54?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/95665a073c54</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[work-from-home]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Fri, 30 Aug 2024 19:15:02 GMT</pubDate>
            <atom:updated>2024-08-30T19:15:02.280Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m4S0Wuir00awzjVGqgti7w.jpeg" /></figure><h4>If the one-size-fits-all workplace is gone forever, what should yours look like?</h4><p>I remember a time when we all went into the office, had laughs in the break room, shared office gossip, and most weeks, went out for happy hour at least once with my co-workers. Lifelong friendships developed, relationships bloomed and faded, and we all generally liked the rhythm of the workweek. What the hell happened?</p><p>In my recent LinkedIn post (<a href="https://www.linkedin.com/posts/jackaskeels_exclusive-eric-schmidt-walks-back-claim-activity-7229612908748398593-Af2M?utm_source=share&amp;utm_medium=member_desktop">link</a>) featuring WSJ’s coverage of Eric Schmidt’s now-retracted comments regarding Google’s laggard AI efforts, blaming their work-from-home (WFH) policies, a wealth of people commented, revealing how complex it is to make even the most basic of generalizations, as I was trying to do:</p><p><em>For the type of work that benefits from working together, things go better when people are together working.</em></p><p>In the comments, someone disputed that there was research supporting my opinion (there is plenty), but others pointed out that the research as a whole is quite mixed. But that’s not a very useful answer if you’re trying to lead a company. Here are a few tips for navigating this complex topic.</p><p><strong>Whither the Workplace?</strong></p><p>As I note in Chapter 2 (The Origins of Bad Managing) of my recent book, <em>UNMANAGED</em> (<a href="https://a.co/d/5DyaClm">link</a>), our basic notions of what a workplace is date back a century or more to the Industrial Era, its factories, and the advent of a daily wage, which many employers took to mean that they “owned” the employee’s time, and anything that the employee did to avoid work (by taking a break for lunch) or god-forbid, leaving the property, was a form of “shirking” or stealing the employer’s money. In some ways, the workplace was a prison of contractual servitude, not something we should idolize.</p><p>In reality, my workplace memories of the 1980’s are flawed. Even then, pre-internet, our sales team was rarely in the office. Technically, they should have been there when not visiting the client or prospect, but results mattered more, so the best of them were more like Black Swan sightings than an office fixture. And yet, they still did meet in the office regularly in meetings I often attended — I was amazed how much I, a newbie, was learning from just hearing them talk, swapping stories and anecdotes. Presence, for those who did not need presence, did make a difference.</p><p>Most situations today also have this sort of nuance to them. In the software technology world, where offshoring, nearshoring, and subcontracting have long been prevalent and practical models, they always seemed to benefit from greater levels of connection and presence. In the 2000s, when I led Sapient’s Los Angeles office, we had 400+ people based in Gurgaon, India, working as part of our West Coast team. Frequent communications between the two regions were essential, of course. Still, physical presence seemed to make things go better, and so we flew people in both directions to increase the connections between the teams, also bolstering understanding. It seems presence, in obvious and subtle ways, matters.</p><p>But that was then. Today’s work-from-home workplace threatens to shatter this idea. Is the workplace a nostalgic relic? Do we need to get together?</p><p><strong>Key Question #1: What workplace presence versus autonomy does our work demand?</strong></p><p>For your kind of business and the type of work you do, what is the optimal mix of presence versus separateness? When do your people need to be together, and how do we make that a reality?</p><p>Famed organizational researcher Henry Mintzberg showed, over fifty years ago, that <em>optimal organizational form follows function</em>: that the highest-rated firms of any given “type” (business <em>function</em>) had many commonalities in terms of their <em>form </em>and key <em>functional</em> elements, including the types of systems, the nature of hierarchy, and the ways in which they actually managed and developed people.</p><p>Let’s add “workplace style” to that list — the shape of your work should be a factor in the shape of your workplace. At least what’s left of it.</p><p>We regularly conduct pod-design workshops for agencies and other high-innovation organizations. In their case, a key factor is the needed <em>level of interdependence</em>, the degree to which work is <em>optimally performed </em>with a lot of alignment (mutual awareness) and collaboration. These things don’t happen by accident and require at least some form of work process and key rituals…and presence. You can run your business without workplace presence, but innovation and collaboration will likely suffer. Our client’s teams are always surprised at how much more effective (and enjoyable) their work is with some added presence in their workflow and process.</p><p>The other side of interdependence is <em>autonomy</em>. WFH can enable greater autonomy (assuming you can limit interruptions), boosting the probability of <em>productive flow</em>. You can also do business without enabling autonomy, but other things like productivity and morale suffer.</p><p>Your company improves when you optimize the mix of interdependent and autonomous activity.</p><p>It also appears to be an imperative these days. Research that I did a few years ago on knowledge work and AI at RAND suggested that the last high ground of human knowledge work will be based on a mix of collaborative <em>alignment</em> and individual <em>autonomy</em>. This is the recipe for what humans can do that AIs cannot, at least in the near future. This is the work you need people for, where you can differentiate what you do.</p><p>And presence is powerful stuff, and a little bit, well placed, can go a long way. Toward the end of COVID, we ran a large Alignment Workshop for a pharma company’s 80-person diverse product marketing group for a recently approved drug that was a true game changer. They struggled to get everyone aligned in the chaotic remote and WFH environment. But with just a few days of presence, using exercises designed to create <em>intersubjective dialog</em>, the group gained massive alignment as to what they should collectively focus on, an alignment that likely would have taken months more to accomplish in a remote model.</p><p>How to decide? Leaders may just need to enable and guide rather than dictate. One of our favorite clients, <em>Starmark International </em>(<a href="https://app.box.com/s/oqgtcdmrh04kqt6yoblz91n5a2xuvh9u">case study here</a>) in Fort Lauderdale, developed a novel team-driven model: teams decide when they should meet (or not) <em>to best get the work done</em>. Starmark re-built its whole office space to enable these drop-in-drop-out meetings that would include remote participants. This is the same sort of awesome re-thinking of <em>un-managing</em> that one can find in CEO Ricardo Semler’s books, <em>Seven-day Weekend</em> and <em>Maverick</em>.</p><p><strong>Key question #2: How does presence affect our ability to attract and retain talent?</strong></p><p>Businesses also operate under constraints, and the availability of talent is among the biggest ones for knowledge work organizations. Knowledge workers, especially in technology and creative industries, have more choices than ever. Not only have the job markets been strong for a while now but are increasingly pervasive, even global, and high-quality internet access enables both a work-from-anywhere opportunity and a <em>work-for-anyone</em> choice of employers. Remote workers have been a reality for decades, but telepresence is increasingly seen as equivalent to actual presence, at least by employees.</p><p>Though some may argue with this point, there is a trade-off with remote workers, especially when the work is better performed with presence. We know of an agency whose top creative recently decided to move several hundred miles away. While the actual work of a creative might be performed as well (or even better in some cases) in the seclusion of separateness, the manager’s role needs consideration. In <em>UNMANAGED</em>, I argue that one of the most critical managerial responsibilities is mentoring and socialization in the workplace. I believe that we socialize and mentor better in person.</p><p>While companies can extend their reach further now, employees are also growing more distant. Some are de-prioritizing work as a central aspect of their life or increasing their emphasis on non-work life by moving to preferred climes, closer to nature or family. While it is increasingly common, it is not universal, and many others will still find value in having a workplace, a community of sorts, and even a place-based sense of belonging. We seem to forget the many people who were all too ready to leave the house and return to the office after COVID.</p><p>Dismissing the need for presence has long been a business guru <em>topic du jour</em>, yet we have natural forces that draw us together; we are communal creatures, highly pro-social, and, in most cases, enjoy the feeling of connection with each other. Why would we want to fight that arguably quite natural instinct? Even Jason Fried, the subversive management guru and author of <em>Remote: Office Not Required</em>, has a preference for having some level of in-office presence (<a href="https://future.com/jason-fried-basecamp-hey-interview/">link</a>)</p><p><strong>Key Question #3: Are you driving them out of the office?</strong></p><p>A sad and ugly reality emerged from the LinkedIn comments, which I can only paraphrase as “I hate your stupid workplace.” Yes, not all workplaces are good, fun, or even healthy. How is yours? Do you have people who make your workplace worse? Michael Lebowitz, CEO of SPCSHP (fka Big Spaceship), a company with a great culture, stated his policy as “Nobody is good enough to be an asshole.”</p><p>Indeed, toxic workplaces exist mainly due to genuinely toxic people, often in management or other positions of control or responsibility. Even more common are somewhat subtle effects of the wrong managerial style, usually due to a lack of skill and understanding rather than malice. These include:</p><p>• Use of dominance, usually vertical dominance of the more senior upon the more junior, including being overly directive, inappropriately critical, dismissive, or condescending.</p><p>• Over-managing, or micro-managing, is disempowering and productivity-killing, creating additional non-productive noise.</p><p>• Bias. Managers are almost always bad at assessing their people. An eye-opening study sponsored by Deloitte showed that the most significant factors in employee assessments were personal, not work or achievement-based.</p><p>• There are more.</p><p>It is probably also worthwhile to note that these workplaces also suffer from a form of innovation suicide — the combination of bias and dominance in a group setting can be toxic to genuinely innovative thinking. Diversity of thought and the power of different viewpoints are some of the first victims of mismanagement in the workplace. Some commenters noted that the slower pace of remote communications enabled them to both form and make their voice heard, something which felt more difficult for them in the workplace. RAND’s early, ground-breaking work in strategic decision-making showed that slowing the conversation down increased the beneficial effect of diverse thinking, creating better results.</p><p>One last note: don’t ask your managers how good your workplace is or isn’t. As revealed in the Deloitte study, the best test was to <em>ask your workers</em> to rate this statement: “At work, I have the opportunity to do what I do best every day.” I suggest you also ask them what could be better.</p><p><strong>Assemble Your New Workplace: Hybrid is likely the new normal.</strong></p><p>Start with hybrid. It gives you all of the options, and you can adjust from there. Extreme choices, like ditching an office entirely, are harder to undo. Make your office a great place to be hybrid, like Starmark did, optimized for the experience of being together when together is needed.</p><p>Make some basic rules. Your workplace rules need not be draconian or numerous and would likely fail if they were. Instead, set your sights on a few simple ideas:</p><p>1. <strong>Alignment and connection.</strong> When should we be together, in terms of teams, squads, and the whole organization? Defining productive and healthy togetherness is crucial in building whatever sense of community and belonging you want. Being together can also be virtual — and probably will always be for some — but not everyone will feel like they belong when they are always distant.</p><p>2. <strong>Autonomy.</strong> How do we ensure that people are as productive as possible when we are apart? The proliferation of tools like Slack means that even when hidden away in my Utah log cabin, the whole company can interrupt me at will. Set some rules for “Day Structure” to enable the productivity that WFH can unleash.</p><p>These are the cornerstones of the new “Way” in your workplace. You should re-align (or establish) <em>values</em> and a <em>vision</em> for your now-hybrid business that aligns with the above behaviors. This will form the core of your organization’s new culture.</p><p><em>Jack Skeels, CEO of AgencyAgile, is an award-winning author, entrepreneur, think-tank researcher, and leadership consultant. Jack’s work and company combine decades of business research, cognitive and behavioral science, and practical techniques learned from working with over 200 organizations into simple lessons on managing today’s complex, project-driven organizations more effectively. To learn more about how to make yours a better organization, visit </em><a href="https://agencyagile.com/"><em>AgencyAgile.com</em></a></p><p><em>Jack’s new book, UNMANAGED, a Gold Medal winner for “Independent Thought Leadership” at the 2024 Axiom Business Book Awards, is available now </em><a href="https://a.co/d/5DyaClm"><em>on Amazon</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95665a073c54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manage Less, Become Awesome.]]></title>
            <link>https://unmanaging.com/manage-less-become-awesome-22eaec46f01c?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/22eaec46f01c</guid>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Wed, 20 Mar 2024 18:57:09 GMT</pubDate>
            <atom:updated>2024-03-20T19:54:36.982Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L2ALRM1Lpym9XYF2LEsFqw.jpeg" /></figure><h4>A former RAND researcher shines light on the counter-intuitive yet proven path to being a great manager.</h4><p><strong>Welcome to the Unmanaging Revolution</strong></p><p>In the bustling landscape of contemporary workplaces, where knowledge work and talented teams reign supreme, the traditional management playbook appears as outdated as dial-up internet. Enter the groundbreaking concept: “unmanaging.” This innovative approach, as championed by industry visionary Jack Skeels, has become the anthem of high-performance organizations, orchestrating a symphony of increased productivity, elevated quality, and heightened engagement.</p><p><strong>The Symphony of Unmanaging</strong></p><p>At the heart of this revolution is the abandonment of the antiquated “manager-knows-all” model that harks back to the Industrial Era. Skeels’s call for “unmanaging” is a paradigm shift, a departure from rigid conformity toward an environment that values the insights and creativity of every team member. This departure from the old ways is not just a suggestion — it’s a necessity, a realization that the old managerial ways are like fax machines in a world of instant messaging.</p><p>The legacy of over a century of management practices is a paradox: the more we try to manage in the traditional sense, the less productive we become in the fast-paced, dynamic environments of today’s businesses.</p><p><strong>Overcoming the Over-Managing Dilemma</strong></p><p>Today’s workplaces grapple with an over-managing dilemma. Managers, with echoes of the factory floor still ringing in their ears, often believe they hold the reins to productivity. However, the reality is quite the opposite — productivity is inversely related to the level of managerial activity. It’s a revelation that echoes through the corridors of traditional management philosophies like a clap of thunder in a silent library.</p><p>The old factory model, with its empirically verified metrics and clear production lines, offered a framework for effective management. However, in the highly variable landscape of knowledge work, no such metrics exist. How do you guess the time it takes to write a groundbreaking report or develop something that’s never before been built? The answer is elusive, and managers are left relying on estimates that often fall short in busy knowledge work environments.</p><p>The lack of objective metrics eliminates a crucial constraint on managerial behavior. Over-managing becomes a slippery slope, intertwined with the errors in poor estimates and the occasional underperformance of workers. It’s a managerial dance where the steps are uncertain, and the consequences are often unforeseeable.</p><p><strong>The Agile Revelation: It Taught us that <em>Less is More</em></strong></p><p>Enter the Manifesto for Agile Software Development, a set of techniques initially designed for large-scale software projects but with broader implications for effective management. While the last decade hasn’t been the kindest to Agile methods, the overarching lesson stands strong: less managing equates to more productivity. Software Agile proved that projects and knowledgework organizations get (much) better when managers’ interaction with teams is <em>minimized</em>, emphasizing key moments for sharing understanding, providing feedback, and mentoring.</p><p>This core principle sets the stage for “unmanaging,” asserting that today’s workers are not just capable but tremendously so of self-management. Skeels introduces the “Four Key Managerial Moments” a framework that guides this approach:</p><ol><li><strong>The Why Moment:</strong> Often neglected but crucial, this moment invites a meeting of minds to address the human instinct to question “why.” It fosters ownership and requires managerial patience, enabling the subsequent “What Moment.”</li><li><strong>The What Moment:</strong> In contrast to legacy factory-managing notions, this moment focuses on scope and recognizes that managers need not know more than the workers. It encourages collaboration and understanding for successful delivery.</li><li><strong>The Go Moment:</strong> Productivity happens when managers lean back and unmanage during the windows of productivity that workers need. This shift of control to the worker is a powerful motivator, contingent on well-managed Why and What Moments.</li><li><strong>The Grow Moment:</strong> Directing actions toward opportunities, inclusion, learning, measurement, reflection, and mentoring, the Grow Moment is often neglected in favor of overmanaging the Go Moment. Balancing these moments is essential for sustained productivity.</li></ol><p><strong>The New Metrics of Unmanagement</strong></p><p>In the unmanaging revolution, workers become the ultimate barometer of managerial effectiveness. Their intrinsic desire to excel surpasses any managerial metrics. Deloitte’s internal research affirms this, identifying optimal worker enablement (as judged by themselves, not managers) as the strongest factor in success. Unmanaging becomes an art — a synchronization of managerial actions with the needs of workers, unleashing their natural capabilities while sidestepping productivity-killing behaviors.</p><p>In his new book, <em>UNMANAGED</em>, Jack Skeels, a former think-tank researcher, decodes the counter-intuitive magic of “Unmanaging”, offering practical and powerful techniques battle-tested in over 200 high-performance organizations. It’s a guide, a compass for leaders and managers navigating the complexities of today’s workplaces, offering a simpler and more powerful way of managing.</p><p><a href="https://read.amazon.com/kp/embed?asin=B0CPXDHMGH&amp;preview=newtab&amp;linkCode=kpe&amp;ref_=cm_sw_r_kb_dp_ZMFNC2AB3WGC5Y5XC0K0">Unmanaged: Master the Magic of Creating Empowered and Happy Organizations</a></p><p><strong>Embracing Unmanagement for a Better, Faster, Happier Tomorrow</strong></p><p>Unmanaging is more than a just a new management style — it’s a cultural shift. It’s an opportunity to drive massive improvements in quality and success rates, creating not just a productive workplace but a better, more inclusive, and engaged culture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22eaec46f01c" width="1" height="1" alt=""><hr><p><a href="https://unmanaging.com/manage-less-become-awesome-22eaec46f01c">Manage Less, Become Awesome.</a> was originally published in <a href="https://unmanaging.com/">UnManaging</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Entrepreneurs: You Can Never Elude the Shark]]></title>
            <link>https://unmanaging.com/entrepreneurs-you-can-never-elude-the-shark-6809bea3aa8a?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6809bea3aa8a</guid>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Sun, 11 Feb 2024 23:23:26 GMT</pubDate>
            <atom:updated>2024-02-11T23:23:26.903Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZyAyvuDH_fQCOONgA0Ofg.jpeg" /></figure><h4>But it can teach you to become a great swimmer.</h4><p><em>The hardest part of getting a young business to survive is out-swimming The Shark, the constant flow of cash out the door to support a growing mass of people, platform, facilities, inventory, marketing…you name it. In rare cases you can win by just selling more. Yet most businesses die or struggle because of how growth — literally success — comes with a dark side: The Shark gets bigger and faster as well. Mastering sales can feel like the most important skill for a business owner, but I believe that far more important and valuable is to know The Shark; how to live with and learn from it.</em></p><p><em>Here’s my post in Entrepreneur.com as published on the 29th of June 2016 on how </em><a href="https://www.entrepreneur.com/article/278146"><em>You Can Never Elude the Shark, But You Can Learn to Swim With It</em></a><em>. </em><strong><em>I’ve made a few tweaks as of Feb 2024, to update it to what I’ve learned since then.</em></strong></p><p>I’m unpacking my “desk box” in our first real office — an executive office space — and a vague anxiety grows stronger. It is 1991 and my company, Product Data Integration Technologies, was growing rapidly — within just a few short years we would make the Inc. 500 — and I felt like something big and ominous was stalking me. I told my partners, “I feel like there is a shark following us around, ready to eat us if we slow down!” They looked at me like I had three heads and laughed.</p><p>When it was just a few of us doing and teaching database design, all we needed was to pay the mortgage and have some money left for food and wine. With our fixed costs close to zero, we were like a small sailboat with a huge sail — the slightest breeze of revenue drove us forward like a speedboat. A classic bootstrap, we started in my partners’ guest house. Our puny 18” x 24” whiteboard represented a major purchase.</p><p>But we had just sailed into deeper waters. There were five of us to feed now — and two more on the way — plus a $2,500 per month rent payment, new computers and other expenses. That’s the shark. One of my many hats was CFO, and I lived in constant calculation of receivables needed by payday and the new biz pipeline that would keep the money flowing. From what I could tell, the shark was very happy that we moved to the new office because it was more likely that we would become its next meal.</p><p>Business went well for the next few years, but the shark grew as we did — from a tiny surf shark to a Great White. The ominous feeling really intensified as our staff reached 60 people. With 85 percent of revenues going to payroll, you could reach back and touch the shark’s teeth at times.</p><p>Ultimately, we survived, selling to a software company in 2000. Both I and the shark moved on. Today, in my new startup, we have about five people. So when the shark swam by — and I wasn’t surprised or all that scared — I realized that I had become a better entrepreneur through what he taught me.</p><h3>The shark never sleeps, nor will you.</h3><p>I had fantasized that having my own company would mean more time off, less pressure and a calmer lifestyle. That didn’t happen. Instead, I became the meanest, freakiest micromanager I could ever imagine. My new boss (me) would even wake me in the middle of the night, pretty much every night. Sharks don’t sleep — and you may not either.</p><h3>Big sharks do more damage than small sharks.</h3><p>Higher sales mean more delivery pressure and people. Missing a $25k payroll that’s mostly partner pay is <em>very</em> different from missing a $250k payroll where people’s mortgages, tuition payments, hospital bills and more depend on it.</p><p>It’s rare to leave the shark behind, let alone kill it; especially in a service business. But as in nature, the shark is a vital part of the entrepreneurial ecosystem. The shark actually made mine a stronger company. I learned to swim both faster and better. One of the key tenets that I share with other CEOs is that growing your sales often just grows the shark. You won’t widen the gap between you and him by just selling more, but you can by managing smarter.</p><h3>Grow your current customers.</h3><p>Many companies make the mistake of chasing the shiny metal object of “net-new” growth — new clients and/or new services. That can cost you current customers; and sharks smell that blood a mile away. Deepen the relationships you have; they are the best platform for growing your services.</p><h3>The shark likes managers best.</h3><p>Once you get to 30 people, it seems that the answer to every problem is to hire another manager. Even in creative businesses today, I often see one manager for every two or three employees. You’ll swim slower, dragging all those managers around. The shark smells all that high-paid meat and just swims faster.</p><h3>Minimize the Managing.</h3><p>(updated) As I now have documented thoroughly in my recent book, <strong><em>UNMANAGED</em></strong> (<a href="https://a.co/d/5DyaClm">available here</a>), relying upon traditional management is costly for project-driven organizations like mine was, and probably like yours is. How many managers do you have? Do you have account managers, department managers, AND project managers? Count the number of people that have a manager-like title and compare it to the number that don’t. If the ration is 1:3 or worse, don’t sleep. The shark is coming.</p><h3>Stop promoting your best.</h3><p>It’s easy to conflate reward with promotion, which will lead you to promoting your top performers into managers. That’s like turning the team’s best swimmer into a coach or cheerleader. It makes the team <em>slower</em>, as a body of business research has validated. The new coach has little time to help with swimming, and few skills in managing. Chaos erupts. The shark is drawn to that department thrashing in the water. You don’t need to create managers to reward people.</p><h3>Teach them all to swim like you.</h3><p>You’re a natural self-starter — motivated and reaching for challenge and responsibility. It’s a safe bet that all your people have that in them too. That’s why they’re working for your company. Channel their inner entrepreneurs. When you feel the need to hire a manager just to make sure that client status reports go out on time, ask if someone wouldn’t mind just owning that and making sure it gets done.</p><p>The laws of natural selection apply in business much as in nature. The shark rewards the focus that healthy companies demonstrate. Instead it takes the fat, slow companies out of the market. Those with lean, self-managing teams learn to swim faster, gaining on their own momentum. As long as you keep your team in shape and remain focused, you can swim with the shark forever. In the end, it will make you a better entrepreneur.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6809bea3aa8a" width="1" height="1" alt=""><hr><p><a href="https://unmanaging.com/entrepreneurs-you-can-never-elude-the-shark-6809bea3aa8a">Entrepreneurs: You Can Never Elude the Shark</a> was originally published in <a href="https://unmanaging.com/">UnManaging</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Million Dollar Margin Makeover]]></title>
            <link>https://unmanaging.com/the-million-dollar-murder-of-agency-margins-89b1f3681035?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/89b1f3681035</guid>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Mon, 05 Feb 2024 21:09:34 GMT</pubDate>
            <atom:updated>2024-05-30T17:39:24.894Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAzeZmkekr8e9yfJE4ju3A.jpeg" /></figure><h4>Burnt-out teams, lackluster deliverables, unhappy clients, and your margin is dying. It’s time to get your agency back into shape.</h4><p>Do you recognize this moment? You’re staring at your cash flow and revenue tracker and you can’t figure out what’s going on. Despite your agency having a really good month last month, hundreds of thousands in revenue, maybe more, your net profit was almost nothing. Where the fuck is our margin, you ask.</p><p>You are seeing plenty of other symptoms as well — your agency, a much happier place once upon a time, has grown, and at the same time strangely grown worse. It is a constant struggle to get work out the door, but it’s not a staffing problem; you have plenty of people to deliver the work you’ve sold. Maybe it’s efficiency, because it feels like work isn’t getting finished quickly enough, and yet everyone says they are busy. You ask managers what they think is going on and everyone has a different answer. You seem to be constantly “fixing” things, yet your organization still struggles. Can this be really that hard to fix?</p><p>It is.</p><p>Our team has worked with over 200 agencies to address exactly these questions, and the good news is that you’re not alone; almost every agency suffers from most if not all of these challenges. The challenges are solvable, though doing so requires a concentrated effort and technique. The problem is systemic, deeply rooted the many different stages of the agency’s sales and delivery model. At times, people call it s<em>cope creep, </em>which is not quite accurate, or <em>project overage</em>, or <em>a below-target effective billing rate</em>, but we use the term <em>rework, </em>because its net effect is one of requiring work that should have been done right the first time — and for whatever reason was not — to be done again, often late and unexpectedly. Most rework arrives as an unwelcome guest, late to the meal and somewhat demanding.</p><p>Calculate your rework using hours, the difference between the hours you thought (or hoped) you would need (as-sold), compared to the hours you actually used (as-delivered.) If a project was sold at 1,000 hours and delivered at 1,300 hours, then that’s a 30% rework rate. And those 300 hours are both lost revenue (because you can’t bill for them otherwise) and lost margin (because they increased your cost of the project, driving your <em>effective rate</em> down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MciK8a9xq2jJ4pdXAC_uZA.png" /></figure><p>Most agencies have a rework rate somewhere between 20–40%, depending upon their work types. Because the origins of rework myriad, complex, and misunderstood, most agency leaders believe that they can simply grow their way out of it; that growth (scaling of the business) will deliver the needed relief. This almost always fails, because it is based on a flawed understanding of what type of organization an agency really is.</p><p>As I describe in my book, <em>UNMANAGED</em>, agencies are not scale-driven organizations, but rather they what are known as <em>ad hoc project organizations</em>, the type of organization that is optimal for delivering creative, innovative and unique project work. Size is the enemy of <em>ad hoc organizations</em>, and as we’ve noted in our decade-plus of industry work, once your agency passes 20–30 people in size, growth slowly degrades the operational model, an effect amplified by an increasingly multi-client, multi-manager, multi-project and multi-allocated complexity.</p><h4><strong><em>It is very worth fixing.</em></strong></h4><p>Rework is quite costly. Here’s an example.</p><blockquote>A forty-person agency typically has annual services/project revenue around $5–7 million, maybe more. Drop the 25% rework rate down to 5% and recover 20% of those lost hours. It is easily a 7-figure number even in a small agency…if not in the first year, certainly by the second year. Larger agencies…well, it’s a no brainer. If you were able to claim even just half of that money and time back, then that’s still a pretty nice number. And you would get it back every day, and every year.</blockquote><p>Nothing else affects margin so profoundly. Twenty-five percent is a big number! Strangely, many agencies seem to treat it as an immutable part of business. I had one COO scoff, “25% is not all that that bad for us”, while also admitting that the numbers I suggested were true. When did he decide to stop caring about all that margin?</p><p>Earlier this year, I was speaking with a somewhat grumpy small agency CEO (<em>one of his operations leads had coerced him to take a call with me, and he assumed I was wasting his time.</em>) He was complaining that getting more sales (growing through scale) didn’t seem to help. Despite some recent wins, his teams weren’t generating enough margin to hire more people, and so he risked burning out his teams.</p><p>I asked him what his rework rate was, and he replied, “What’s that?” I explained it, and he said, “Well, it sounds like we should be tracking that.” Yes, I think so. When I explained where it comes from and why, he said, “That sounds like something we should fix.”</p><p>Will he? Many don’t because they have “other initiatives” they are focusing on. Every agency has those initiatives, but none of those initiatives move the needle on margin like fixing your rework rate. Agencies are filled with managers — aren’t they supposed to be fixing this? Or even preventing it? No single manager can fix it because it is a <em>broad and systemic problem</em>, and most of them, inadvertently, are part of the problem. Rework is born and nurtured in what we call the <em>broken scope-cycle</em> that spans the whole lifecycle of client engagement.</p><h4><strong><em>A failed chain of custody</em></strong></h4><p>The broken scope-cycle is a chain of scope management mishaps that create a self-reinforcing loop. (Note: when I refer to “scope” I mean everything that you should know about the project, the client, its intended results, etc. “Scope” is not just the tasks that people are being told to do.)</p><p>The data we have collected from our key diagnostic workshops (the 18-point Lifecycle Diagnostic, and the Productivity Diagnostic), performed with over 80 agencies, suggest there are <em>over a dozen key moments in the scope-cycle</em> in which the quality and understanding of scope is in near-constant decline. Here are some of the key ones:</p><ul><li><strong>You lost me at “Hello.” </strong>Agencies make a lot of promises when they’re pitching a new client or new piece of work. Almost universally, the agency itself knows they have very poor follow-through on those early conversations. Broken promises include how innovative they will be, how collaborative they will be, how deeply the teams will understand the client’s business, and how their work will create real business results.</li><li><strong>The absent and incomplete “Why.”</strong> In the rush to get going, often the tough questions are not asked of the client. Sometimes it is lack of skill in doing so, other times it is because one person expects that someone else, like a strategy person, will do it. But more often it is a “Three wise monkeys” problem: asking questions is curtailed by the very real fear that difficult questions may uncover complexities or uncertainties that blow up the sale, slow the project, or cause its scope to balloon. When we teach an agency our version of the “Why” technique using a new, real-life project, an agency will find 15 or more significant gaps in its understanding of the client context and the why behind the work, even after a signed contract.</li><li><strong>The ignorant handoff. </strong>When the work finally transitions from the sales or account people, much is still not known, and worse yet, the way the information is handed-off to the actual team is frighteningly ineffective, whether a briefing, a brief, a big PowerPoint deck, or even a specification. When we fix this through our trainings, you’ll hear account people say, “Wow, I wouldn’t have told them half of this.”</li><li><strong>The blindly optimistic and incomplete scope. </strong>Because so many details and potential risks have been (essentially) ignored, an agency has only an optimistic yet hazy idea of what the real work is. While much of what they<em> have spoken about</em> is fairly correct, <em>the most important scope is the scope that they haven’t spoken about</em>. Unexplored scope is a ticking time bomb of rework, guaranteed to go off at the worst possible moment. When we analyze this, <em>sales scope</em> versus the <em>more-correct delivery scope</em>, typically 30% of scope is hidden, unexplored, ticking away.</li></ul><p>The 30% should be terrifying to you, but it is just an average, and not that bad compared to the extremes, both of which can create even larger problems. Sometimes unexplored scope is near 0%, this is a scope that is simple and well-understood, and rework, as a result, is minimal. But the fact that this happens with some regularity can be very misleading to agency management, creating a belief that the agency’s “system” works. And then, when things go wrong on other projects, managers conclude that it was not the system (because it has been proven to work), but some specific cause, some person, some client, some mistake. An agency is always fortunate to get some simple and well-understood projects, but it often misleads them into thinking that their system works, that they really know how to handle more-challenging scopes.</p><p>The other extreme — when scope is horribly unexplored — can be quite profound. One small agency client thought they had landed a $600k project, but when we showed them how uncover the unexplored scope, they found the project was three times larger than they had thought. Were it not for a supportive client, they might have had a true disaster on their hands, or gone out of business. This happens to the big guys as well. One of our largest clients ever, part of one of the largest holding companies, had agreed to a $2MM project, which upon the deeper examination, turned out to be $8MM. Both agency and client agreed to walk away from the project; nobody wants a disaster.</p><ul><li><strong>The theft of the team’s scope. </strong>Most projects will go forward despite the incomplete and undiscovered scope. The “system” that worked so well for simple things now fails horribly, as <em>only the scope that is known</em> gets made into a plan. This does not fix things, and even tends to make them worse. This plan or schedule, ignorant of how much other work is really within this project, is inherently deceptive, missing 10–30% of its most important information. <strong><em>The plan is a lie, an inadvertent deception; because it suggests that everything is known when it is not. </em></strong>The teams are expected to deliver a project with missing scope following a schedule that for the same reasons lacks reality.</li></ul><p>Managers are often unwittingly part of the problem, as the common practice of having managers “own” the scope, either individually, (as in a PM, who cannot ask the tough questions to find the hidden scope) or collectively (as a group of leads who will then hand pieces of incomplete scope down into their respective department silos.), means that nobody ever really sees the whole picture, certainly not the team.</p><ul><li><strong>The fragmented, unaligned team. </strong>One of the other mistakes growing agencies make — believing themselves to be scale-based organizations — is fragmenting work into tasks, and workers into departments to “make things go better”. It doesn’t. The teams get spoon-fed only small pieces of scope, leaving them ignorant to the broader project and also their teammate’s work, which limits their ability deliver correct scope except through costly trial and error. These teams lack <em>alignment:</em> the ability to <em>understand each other’s understanding</em>. Alignment is the most important factor in successful teams’ execution in <em>ad hoc project organizations</em>.</li><li><strong>The stupid client. </strong>Clients are to blame for that scope creep, right? Nope. But they are the <em>easiest to blame since they know the least.</em> The fact that your agency did not fully-define scope, nor educate them to it, means that they are free to define (and re-define) it every time you try to deliver it. Agencies complain about client’s changing scope late in the project, but we’ve seen empirically that this is caused by <em>the discovery of undiscovered scope</em> late in the project. This is a direct result of the chain to failures to uncover and resolve missing scope, risks, and assumptions. The client is righteously stupid: if the agency did not ensure that all scope was understood and agreed to by the client, then the client has the right to change what wasn’t understood. In our Client Diagnostic workshop, the topic of “Clients don’t understand the project” is always in the top three types of agency-client challenges across their client base. Blame the client at your peril; it will keep you from ever fixing the real problem.</li><li><strong>The contagious Mt. Death March. </strong>And so, this project will be challenged to meet its schedule, quality, and margin goals. Your team is climbing Mt. Death March. But it gets worse when <em>The Grim Reworker</em> comes to visit. This wraith brings them the formerly undiscovered scope, now just a few, scant weeks before the delivery date, and they are going to need an extra 300 hours of work to get it done. Where do you find those people and hours? The only effective choice is to just keep the team together, but that means that the projects that they <em>were scheduled to work on</em> will now be delayed. This one bad project is making other, possibly good projects, go bad. It is the <em>Grim Reworker’s </em>plague of <em>project contagion</em>. Your other projects, including those which had simple and well-understood scope, will also suffer from staffing delays and other ills.</li></ul><h4><strong><em>Boost margin by a million dollars or more: the Scope-Cycle makeover</em></strong></h4><p>One of our clients, Kevin Hourigan, CEO of Bay Shore Solutions, told me that before they worked with us, he would routinely write off a “big, six-figure number” at the end of each year. He went on to say that once they had mastered the scope-cycle fixes we taught them, it became a “four-figure number.” I didn’t ask whether it was a big or small four-figure number because, well, who cares? At that point, he had at least three years of those results.</p><p>Less rework means less labor cost per dollar of sales. That means you can either deliver more work without hiring (by growing sales), or you can deliver the same work with fewer people. You could also use the extra time to do better quality work. Or stop burning everyone out.</p><p>Many other problems in agencies are symptoms of the broken scope-cycle. In analyzing six years of data from our keystone workshop, the <a href="https://agencyagile.com/productivity-diagnostic-workshop/">Agency Productivity Diagnostic</a>, we’ve found that approximately 50% of all “delivery chaos” is caused by attempts to recover from failed parts of the scope-cycle. This includes symptoms that managers think can be solved directly (they can’t), such as: excessive meetings, excessive number of managers, delivery “misses,” lack of innovation or creativity, and low team morale.</p><p>Fixing the broken scope cycle creates real results. To quote one of our clients, LaneTerralever, whose case study is on our site: “…we’re up about 20% more dollars per hour of delivery. A lot of that is due to less re-work and better planning.”</p><p><em>Jack Skeels, CEO of AgencyAgile, is an award-winning author, entrepreneur, think-tank researcher, and leadership consultant. Jack’s work and company brings together decades of business research, cognitive and behavioral science, as well as practical techniques learned from working with over 200 organizations, into a set of simple lessons on how to more effectively manage, today’s complex, project-driven organizations. To learn more about how to make yours a better organization, visit </em><a href="https://agencyagile.com/"><em>AgencyAgile.com</em></a></p><p><em>Jack’s new book, UNMANAGED, a Gold Medal winner for “Independent Thought Leadership” at the 2024 Axiom Business Book awards, is available now </em><a href="https://a.co/d/5DyaClm"><em>on Amazon</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zii70-hhBpVGo2KQdun9Ag.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89b1f3681035" width="1" height="1" alt=""><hr><p><a href="https://unmanaging.com/the-million-dollar-murder-of-agency-margins-89b1f3681035">Your Million Dollar Margin Makeover</a> was originally published in <a href="https://unmanaging.com/">UnManaging</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Way to Measure a Manager]]></title>
            <link>https://unmanaging.com/the-best-way-to-measure-a-manager-bfed5a6307b0?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfed5a6307b0</guid>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Tue, 05 Sep 2023 15:25:17 GMT</pubDate>
            <atom:updated>2023-12-01T15:45:57.607Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gB_QSKQ4roUpUENP" /><figcaption>Photo by <a href="https://unsplash.com/@graphicnode?utm_source=medium&amp;utm_medium=referral">Graphic Node</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>Excerpted with revisions from my upcoming book, </em>Unmanaged: Master the Magic of Creating Empowered and Happy Organizations.</p><p>How well are your managers doing? In our upcoming research brief on workers and team productivity, based on a sampling of the over 200 professional services organizations we have worked with, confirms that managers (and the way they manage) are likely your biggest impediment to productivity. This is a conundrum of sorts, as managers are often responsible for self-policing their own behaviors, yet research confirms that managers are not really good at assessing themselves, other managers, nor (especially) workers.</p><p>The complexity of this question (are we managing well, and if not, in what ways?) is why we offer to our clients a multi-point diagnostic survey (called the <a href="https://agencyagile.com/productivity-diagnostic-workshop/">productivity diagnostic</a> workshop) to help the organization clarify the impact of managerial actions upon productivity. How does it work? It works quote well, and we can now benchmark an agency’s productivity against a database created from using this survey with over 80 agencies. Our own <a href="https://medium.com/u/bc1a1bcc33e1">Lauren Dobkin</a> coded up that data and created categories that we can then measure comparatively.</p><p>But really how it works, how we best judge managers <em>in-context</em>, well that’s a very simple answer. And as I describe in Chapter 5 of my new book, <a href="https://a.co/d/9AQL3Lx"><em>UNMANAGED: Master the Magic of Creating Empowered and Happy Organizations</em></a><em> </em>, I had my eyes opened by an amazing agency CEO alomost a decade ago.</p><h3>Chapter 5: The Measure of the Manager</h3><p><em>I didn’t believe it when Ben, the CEO, described his organization. I assumed he was lying. Many of the </em>[project-driven] <em>organizations we work with have 30–40 managers for 120 people: a 1:3 or 1:4 ratio. Ben had just told me he had 8 managers overseeing 120 people. That is a 1:15 managerial span of control, which is pretty rare and pretty cool.</em></p><p><em>You’re probably expecting me to talk about the transformation that we did for them. But this was my first meeting with Ben. He had unmanaged his organization on his own. It was one of those wonderful moments when I got to be the student rather than the teacher. I dug in.</em></p><p><em>“So, how did you end up with so few managers?” I asked.</em></p><p><em>Ben looked around the beautifully renovated SOHO office space — it was nicely modernized while retaining the original midcentury charm — and with a dramatic gesture he said, “I never wanted ours to be like other companies, and so I vowed I would make my decisions differently. Every time I had to make a business decision, I would say to myself, ‘What would they do?’ and then I would do the opposite or something different.”</em></p><p><em>I smiled and nodded. Amazing. He was a contrarian, and that’s useful if you want to manage well.</em></p><p><em>“I noticed how often they would have chosen to hire a manager, and I just didn’t do that. Sometimes I had to, of course, but most of the time we could just find another way to do it or let people self-manage — do it themselves.”</em></p><p><em>Ben had called me there because, while he did know how he got to this point, he was not sure how to sustain it. His biggest fear was that as the organization grew, he would need to bring in more managers — ones who might not share his belief in their limited usefulness.</em></p><p><em>After some more discussion, I asked him how he judged the quality of the managing going on. His answer was simple.</em></p><p><em>“We do a performance survey for each manager. The workers get to vote on any manager that they have interacted with. It is a simple score and just one question: Thumbs-up or thumbs-down, how well did this manager do in helping to make you successful?”</em></p><p><em>Wow, brilliant. “How do you use the results?” That’s where the magic must lie, I thought.</em></p><p><em>“If a manager gets one thumbs-down, then we just have a conversation,” Ben said confidently, pausing afterward, as if to let the idea sink in. But the silence dragged on — he was actually baiting me, I think.</em></p><p><em>I took it. “And what happens if they get a second one?” There had to be a challenge to solve here — like what if a worker was just being mean or whatever.</em></p><p><em>“Nobody gets a second one.” Ben grinned wide.</em></p><p>Ben had turned the notion of managerial exceptionalism on its head. In effect, he said, if you, as a manager, fail at making our workers and teams better, then you have no managerial value to our organization.</p><h3>The Futility of Managerial Responsibilities</h3><p>Ben succeeded where many of us have failed: succinctly defining what managers provide an organization. He was focused on outcomes. When most managers are asked about their role, instinctively they rattle off a long list of activities that they do or responsibilities that they have:</p><p>· I make sure the project schedules are updated.</p><p>· I keep track of project status by holding the weekly status meeting.</p><p>· I conduct one-on-ones and write the annual performance reviews.</p><p>· I make sure we have enough resources for the work.</p><p>· I make sure that everyone remembers the due dates for the work.</p><p>· I approve everything before it gets launched, sent, or whatever.</p><p>This list certainly looks managerial from a traditional perspective, right? But does this mean that I should measure the manager by whether they do these things? Granted, these activities may sometimes be useful, but it depends upon how they are done and what the outcomes are. Consider that the team could still fail in their work while the manager “succeeded” at these tasks. What if a weekly status meeting turned into an hourly “What are you doing now?” interruption of the worker? Obviously, that would be highly detrimental to their productivity and morale. But the manager was merely executing their “responsibilities.”</p><p>Responsibility lists really don’t get to the core of what a manager is needed for. Instead, let’s ask, What is the measure of the manager? Lacking that answer, how could we judge any choice of action by a manager?</p><p>My conversation with Ben taught me a lesson about the importance of clarity in how we measure managers in a project-driven organization. If we prioritize our teams’ success because of their profound impact upon productivity, we can only judge managers by a few measures:</p><p>· Are your people growing, building new skills, and overcoming their gaps and limitations?</p><p>· Do they feel acknowledged, supported, informed, and central to the organization’s success?</p><p>· Are they happy, and do they feel engaged and appropriately challenged?</p><p>· Are they achieving their highest productivity while maintaining work quality and personal satisfaction?</p><p>Behind these questions is the most fundamental truth about workers and managers, what I have dubbed the First (and only) Law of Unmanagement.</p><h3>The First Law of Unmanagement</h3><p>Workers are the most precious source of productivity and capability in a project-driven organization. In their actions and design, managers and the organizational context can enable their workers productivity — or they can define the workers’ limits. The strongest organizations, from their structure to their preferred styles of managing, enable workers to the maximum productivity.</p><p>The productive speed of an organization is the speed of its workers and teams, not the speed of management. In fact, as you already understand to some level, an increase to the speed of management — that is, the frequency and intensity of managerial activity — is more likely to detract from the productivity of the organization. Enter the <strong><em>First Law of Unmanagement</em></strong><em>:</em></p><blockquote>The singular role of the manager is to be in full support of the workers and teams, enabling and unleashing their natural capability and energy upon the work and opportunities faced by the organization. In performing those duties, the manager shall not detract from productivity through any other actions or inaction.</blockquote><p>This law shifts the burden of scrutiny — as Ben did with his thumbs-up survey model — onto managers. Are their actions making things better for workers and teams? This question provides a North Star for measuring managers, but it certainly is subjective. Any manager can claim their intent is to support the team, hence the genius of Ben’s survey: workers get to report on how supported they feel.</p><h3>Post-script to this book snippet:</h3><p>At some point you need to stop writing and re-writing the book, which I have now, but of course new pieces of research pop up that scream to be included. Here’s a new one for me, a paper published in 2000, “Leadership role effectiveness as a mediator of team performance in new product development virtual teams.” (by Han, Soo Jeoung, Mirim Kim, Michael Beyerlein, and Darleen DeRosa, in <em>Journal of Leadership Studies</em> 13, no. 4 (2020): 20–36.)</p><p>The paper is on factors that influence performance in virtual (distributed) teams. I’ll write another article about their primary findings, but the cool tidbit in all of this is when they highlight that “factor models” (is the manager more of one thing or another, like <em>mentoring </em>versus <em>directive</em>?) that aim to assess managers’ behavior don’t really work because they give <strong><em>different answers in different contexts</em></strong>. For example, Company X’s distributed team will need different managerial factors to become optmially productive than Company Y’s team, because they are different companies with different business contexts (type of work, shape of team, industry, project design, etc.)</p><p>This is significant because most things written about managing are written in a generic way that assumes that any given managerial action is intrisically good or bad, regardless of the context. And the meta-analysis in the paper confirms that is not true, and as I wrote in <em>Unmanaged</em>, <strong><em>correct managing is contextual</em></strong>.</p><p>To my delight, the paper also concludes (with a lot of supporting citations) that the best measure is what Ben had chosen: team members are the best judgers of how optimal the manager’s behavior is <strong><em>for the given business context.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfed5a6307b0" width="1" height="1" alt=""><hr><p><a href="https://unmanaging.com/the-best-way-to-measure-a-manager-bfed5a6307b0">The Best Way to Measure a Manager</a> was originally published in <a href="https://unmanaging.com/">UnManaging</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How an Old Management Technique is Perfect for the New Normal]]></title>
            <link>https://jackskeels.medium.com/how-an-old-management-technique-is-perfect-for-the-new-normal-b77512644a74?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b77512644a74</guid>
            <category><![CDATA[new-normal]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Tue, 09 Nov 2021 00:10:27 GMT</pubDate>
            <atom:updated>2021-11-09T00:10:27.745Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9hicchVQ7Otyy_UeUtK5A.jpeg" /></figure><p><em>Leaders, executives, and managers can face the new normal with confidence knowing that there’s a new way for teams to work more productively. It’s called “pods” and it has been proven to deliver improvements of 30% or more in factors like productivity, quality, and employee satisfaction.</em></p><h3>Managing Just Got Easier</h3><p>We humans evolved an efficient way of working together centuries ago — an organizational model that may be our best approach to today’s fragmented and uncertain new normal. It’s called the “pod” model, and it describes a small, established team of people who are adaptive and largely self-managing.</p><p>The pod model helped propel us all the way from the Stone Age to modern abundance until it was cast aside a little over 100 years ago to make way for the machine-driven hierarchical mindset of the Industrial Revolution. But recently, thanks to the writings of systems scientists like Peter Senge, a new wave of collaboration and productivity has started to rediscover the ancient successes of pods, freeing up managers to achieve more with their teams by actually doing less.</p><h3>What Was Wrong With the Old Model?</h3><p>Today’s predominant model for managing comes from machine-based organizations (factories) that used an “assembly line” method of manufacture. Departments were born out of the need to train people to keep up with the machines, and managing consisted largely of setting the standards for how fast people should work in order to maximize company profits, or to avoid being fired. Managers were enforcers of a strict process in a rigid production system.</p><p>If that feels dehumanizing, you’re right — the factory methods did little to embrace the best in human skills and behaviors. But in today’s world of complex knowledge work performed by skilled workers, departments have become less essential. Since the 1990s pod-based ways of working have become more common, the most prevalent being <em>Agile</em> software development, a small teams (pods) method for running big projects. Pods are also in favor because they are a more flexible structure, enabling greater organizational agility and inclusion to meet the quickly changing demands of a more-digital marketplace.</p><h3>What is a Pod?</h3><p>A pod is a self-managing, cross-skilled group of people that can adapt and flex to tackle a wide range of simultaneous projects, often serving a range of internal stakeholders or clients. But how big or small this group is, has a significant impact on how successful a pod will be. Researcher Robin Dunbar first coined the idea of natural group sizes in the 1990s, having studied effective group populations throughout human history. His conclusions suggested that humans have evolved to work in groups but that certain sizes are optimal to certain types of activity.</p><p>In our experience, self-managing pods require a level of trust and communication efficiency that is difficult to maintain past fifty people in size. And on the other end, small groups of five or fewer people (or even ten) are <em>naturally</em> self-managing, but they lack the ability to scale into larger work or have significant parallel activities. We’ve discovered that pods of between 25 and 40 people deliver the optimal diversity of talent along with the ability to handle multiple streams of work.</p><p>These optimal self-managing pods of 25–40 people outperform the more traditional hierarchical approach by about 30% across a range of factors, including innovation, quality, productivity, employee satisfaction, and speed of delivery.</p><h3>Our Work</h3><p>Over the past decade, our company, AgencyAgile, has worked with almost two hundred knowledge-based organizations to implement sophisticated pod-based organization models. Initially we focused on advertising and marketing agencies because they are organizations that run on disruptive innovation — the work they do is different every time, and often the way they do it (process) changes as well; the traditional departmental-machine model is entirely unsuited for them. In our early days of working with them, we used <em>Agile</em> — a way of running very simple pods for software development. But very quickly we learned that ideas like Dunbar’s natural group sizes really do make a difference — we developed a richer model for these very complex agencies, but the result was a framework that works for other types of organizations too.</p><p>We continue to be amazed at how much better pods work than departments, and how quickly. From early on in the transformation process, teams started to observe measurable improvements in productivity, quality, and employee happiness, and they ran far better. But what we didn’t anticipate was the degree to which, during the work-from-home chaos of the pandemic, these companies resoundingly agreed that the disruption of their business would have been far worse had they not already shifted to pods. Its natural way of interaction clearly surpassed the department-machine models, and this will be a lesson that will carry over quite naturally into the atmosphere of the new normal.</p><h3>But What Does This Mean for Managers?</h3><p>Embracing the pods model means shifting from this hierarchical, department mindset and eliminating the concept of managing through power, replacing it with management through consensus. This is an enormous opportunity for managers, giving them greater opportunity to understand and truly lead their teams in ways that are far more in tune with the expectations of today’s workplace. Managers who embrace the pods model will be surprised how much easier managing gets. This is very similar to the benefits of work delegation, in which learning the skill of handing off work to another person frees you up to do better, higher value tasks.</p><p>Less managing is a good thing, especially in this era of Covid-shifted workplace models. If anything, traditional managing got harder to do with work-from-home and certainly hybrid work-home situations will be only marginally easier. Workers that can coordinate <em>without hierarchy</em> go faster than those who must work through it — research has shown that the frequency and speed of hierarchical decision-making are major factors in organizational productivity.</p><h3>A Model for the New Normal</h3><p>We believe pods are an ideal model across a range of workplace models. They clearly outperformed hierarchies before Covid, as well as during the work-from-home period. We also believe that the old machine-driven model will be increasingly more difficult to manage with distributed and hybrid workforces and virtualized activities. Regardless of whether team members remain co-located in the same building, are distributed across the country, or a hybrid of both, pods offer a model that improves performance and creates cohesive, productive groups, precisely what is needed for the evolving challenges of managing organizations.</p><p><em>Jack Skeels is an award-winning entrepreneur, think-tank researcher, leadership coach, and consultant, and brings together decades of business research, cognitive and behavioral science, as well as practical lessons learned from agile management, into a set of simple lessons on how to understand managing, and manage, in a whole new way. Visit </em><a href="https://agencyagile.com/"><em>AgencyAgile.com</em></a></p><p>Photo courtesy Darren Nunis (@dnunis) via <a href="https://unsplash.com/photos/aKRaaHnlTMI">Unsplash</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b77512644a74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What your DEI strategy is missing: the hard part]]></title>
            <link>https://jackskeels.medium.com/what-your-dei-strategy-is-missing-the-hard-part-9b7f90a02584?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b7f90a02584</guid>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[blm]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 16:34:29 GMT</pubDate>
            <atom:updated>2020-10-01T15:57:00.934Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vq1FdRmadFN2GnRILm5OUw.jpeg" /></figure><h4>Achieving our much-needed Diversity and Equity goals require that Inclusion is truly structural</h4><p><strong><em>Inclusion</em></strong> is the most important part of DEI: without inclusion, all your work <em>hiring into </em><strong><em>diversity</em></strong> and <em>assuring </em><strong><em>equitable</em></strong><em> compensation</em> will be noble gestures whose impact is never realized. All three are important, for sure, but <em>making your organization more inclusive</em> is the hard part…Inclusion has to happen all day, every day, and requires significant systemic change to how your organization currently operates.</p><p>I say this from the perspective of 20+ years of management sciences research, and most recently, a decade training and coaching well over 100 organizations in worker and team empowerment, essentially inclusion by another name.</p><p>Our current BLM-aware zeitgeist has brought inclusion into the spotlight, but inclusion has always been a huge problem, especially in the type of knowledge work organizations that are common these days, the Meritocracy. In a meritocracy, <em>deep specialists</em> are progressively promoted into <em>leadership in the hierarchy </em>through “merit”. But as I’ll discuss, these organizations have massive amounts of non-inclusion embedded in their processes due to two forces. The first is that of I<em>n-Group, Out-Group bias</em>, of which racism is but one of many different “<em>-ism</em>” variants.</p><p>The second force is a combination of <em>confirmation bias</em> that is amplified by a <em>pecking order</em> effect. These two forces are so strong in meritocracies that their impact is evident even when gender or race differences are not present. And, because they are driven by largely unconscious biases, they can be very difficult to see from the inside or from the top of the hierarchy.</p><p>The many costs of non-inclusion become visible once it is remedied. An organization that has increased its inclusion is unmistakable — its people are more engaged, work products are done better and faster, and a generally happier culture provides strong evidence.</p><p>The importance of inclusion is not only the focus of my work, but it, along with the rest of DEI, is personal for me, going back to <a href="https://medium.com/@jackskeels/what-my-father-taught-me-about-dei-fd34088a779c">the lessons I learned from my father</a>.</p><p>And I am concerned.</p><p>I am concerned with what I see companies doing: well-intentioned <em>compensatory gestures</em> rather than substantive, structural change.</p><p>I’m referring to acts like: sending out emails with carefully-crafted BLM-supportive statements, changing the wording on a website, forming committees, sensitivity/awareness sessions, and trying to re-model conversational techniques, like using “I think” statements instead of “It is” declaratory statements. I’ve seen similar gestures in the “adoption of an Agile mindset” which results in lackluster/worthless or even failed implementations of Agile.</p><p>A fifty-plus year body of workplace research and the evidence of a decade of successful transformations clearly show one key thing: better inclusion requires systemic change, a type of change requires planning and scripting of processes and behaviors in a way that steers the organization away from its biases.</p><h3>Let’s Fix the DEI Terminology</h3><p>You can say DEI stands for whatever you want — certainly the definitions out there are all over the place. I prefer a clean and simple structure, because then we can make concrete actions and decisions from there:</p><ul><li><strong><em>Diversity</em></strong> is about the richness of the mix of people you have; essentially giving people a chance to be on the team. Diversity is also influenced by population and talent demographics — you can only hire people that actually exist.</li><li><strong><em>Equity</em></strong> is about providing fairness in compensation, rewards and resources; essentially treating them like they are the team. Equity is assessed at hiring point, but also on an ongoing basis, and in that way is influenced by Inclusion.</li><li><strong><em>Inclusion</em></strong> is about letting and even making them play; getting people suited-up and on to the field, game-time. Often “diversity of thought” is put under diversity, but as I’ll illustrate in a moment, inclusion is the true driver of new and different perspectives that we associate with that idea.</li></ul><p>So using this model, Diversity is a “point event” that happens somewhat rarely, when a candidate is made an offer to join the team. In a purely technical sense, as long as they stay, you have succeeded in altering the diversity of your organization. Letting people go also has a similar impact. But these happen rarely in the scale of things.</p><p>Equity in a meritocracy is something that is assessed at hire but also on an ongoing basis. The <em>assessment at hire</em> is fraught with challenges and inequities that influence later assessments. The <em>ongoing assessment </em>is really more like a set of work “tests” or “trials”, where the person’s performance over time shapes the perceived need for improved equity. Both the opportunity to participate in trials and the assessment of the performance are challenges.</p><h3><strong>The First Force: In-Group-Out-Group Bias</strong></h3><p><em>In-Group-Out-Group bias</em> is something that we all have and it is largely innate and automatic: we are good at categorizing, making distinctions and assigning meaning and value…regardless of whether we are right or wrong in those matters. People whom you perceive to be <strong><em>favorably</em> <em>similar to you</em></strong> are your <em>de facto</em> In-Group…and you consider them (and yourself) superior to those who are not in that group, <em>the Out-Group</em>.</p><p>So I ask you, “Since this bias is automatic and invisible, how well do you think managers assess people in terms of their skills and talents?” Most managers in meritocracies are horrible at it. Research shows that the single greatest factor in a hiring assessment or performance review is not the quality of the work done nor qualifications of the applicant, but the appraiser’s (personal) opinion of the person.</p><p>People who have higher skills, but are in perceived to be in the <em>out-group</em> will tend to be appraised as less-capable than those within the <em>in-group</em> that have lower skills. Here are a few examples both old and recent:</p><p>A business partner of mine a few decades ago would tell a story of how he needed 200 people ASAP to staff his technology program at an aerospace company. After a few months he had only hired about 20 people and his boss called him in. He asked Bill what the problem was, and Bill quickly pointed out that, “…there just aren’t enough good people out there.” Bill’s boss asked to see the resumes, and Bill brought a big stack of them in as proof that he was looking at a lot of candidates. Bill’s boss peeled the top 100 resumes off that stack, handed them to Bill and said, “Hire ’em, give’em a chance, and fire the ones who don’t work out.”</p><p>Bill’s boss knew on some level that he didn’t need 200 people from Bill’s in-group. The punchline is, of course, that almost all of those people in Bill’s out-group worked out just fine.</p><h3>Our Persistent Under-estimation Bias</h3><p>Here’s the subtle idea inside the Bill story: we’re even worse at judging <em>how great a candidate </em><strong><em>won’t be.</em></strong> We underestimate people way worse than over-estimate them. Your lower expectation of the person translates into lower performance on their part, and once that happens, you will feel validated in your judgement. But your judgement was wrong, and you will never see that.</p><p>I’ll illustrate with an agency client story from a few years ago. Our new client was eager to do our team empowerment trainings, but there was one hold-up according to him: half of his 50 people were “the wrong people,” under-skilled and likely headed out the door. He asked, “Should we wait until we replace them all [this would take forever, of course], or what?”</p><p>You can see where this is going, right? So I kind of lied to him: I told him that he would <em>be able to see better which people to let go </em>after the training was done. I know he thought we were going to be providing him with rationale for why he could get rid of the “bad” half of his team. In reality, we were going to teach him that he had never been able to see how good they could be.</p><p>One year after our trainings, and following a big meeting with one of their clients, he wrote us, excited about “how awesome our team is now.” We shot back a note asking how many people had left or been exited. Only one person left, and that was because the person and their spouse decided to relocate because of the spouse’s new job.</p><p>So, 20–30 people who would have been let go for being sub-par, were actually pretty solid. But if that manager had let them go, he would have only “proven” that his (bad) judgement was correct.</p><p>This sort of carnage manifests in at least of 50% of the organizations we work with, and it often is accompanied by a blithe ignorance of the fact that <em>the managers job is to actually elevate people, not denigrate them.</em></p><p>By the way, this was pretty much a racially homogeneous group. We’re just amazingly good at having very severe biases. Because gender and race create a stronger perceptual difference between the observer and observed, I’m pretty sure they amplify these already strong biases as well.</p><h3>Equity: Paying Less is Forever</h3><p>In the hiring process, the decision on compensation will have all these same bias problems of course. One of the biggest mistakes — and this is somewhat counter-intuitive — is to pay people as little as possible upon hire, to negotiate them down on their compensation. I can hear some of you saying, “…okay, but shouldn’t some people get paid more, after all, if they are more talented, and others less, because they are not as in-demand?” To which I would reply, “Um, yeah, but you’re probably a horrible judge of them…and re-read that section above.”</p><p>And yet an even better rationale exists. A fine body of research on women’s inequity in compensation has shown that the starting wage has an outsize effect on ongoing inequity. When women (and others) often start with a lower hiring wage, we delude ourselves with a <strong><em>meritorious equity myth:</em></strong> “If they really deserved more, they’ll close the gap with promotions.”</p><p>But what the research shows is that the person that was paid less at hiring rarely recovers to wage parity, even when skills and experience are equal. Think about it: because of that lower starting wage, that person has to be <em>more spectacular than average </em>to actually <em>achieve average wage parity.</em> The lower wage puts them on a path to always having lower wages.</p><p>But wait, it gets worse.</p><p>There is an ugly, secondary effect of <em>In-Group bias</em> that happens when someone perceives themselves to be part of an <em>out-group</em>: they then rate themselves as less capable than someone of equivalent skills in the <em>in-group</em>. In this way, the more we create (group) distinctions, the more opportunities for negative <em>out-group</em> bias effects <em>from all participants</em>.</p><p>Organizations like the management consultancies — which are also meritocracies — work hard to do a great job of measuring, because they know that it ensures that high-performers get seen, even when, and because, they are hard to see. Sadly, most organizations don’t have that sort of discipline.</p><h3>Equity: Meritocracies are not fair</h3><p>When I say meritocracy, I mean any organization that promotes the best (most meritorious) specialists into management. This often impacts compensation inequity because of the mistaken idea that managers should get paid more then deep specialists. It is in the nature of a meritocracy to make quite clear the <em>in-group</em> (managers), and more important, the <em>out-group</em> (everyone else).</p><p>Because the largest increases in equity/pay come from winning, and winning requires that get a chance to play, to lead, and show your stuff, the third driver for inequity is <strong><em>lack of opportunity or lack of inclusion</em></strong>.</p><p>Meritocracies can be thought of as a large team that chooses small squads on a project-by-project basis; to be chosen to be on a squad is to be given opportunity through inclusion. The selection of people to be in these squads is subject to massive <em>in-group bias</em> — we see it in agencies especially — where the same people, over and over, get chosen for the most challenging problems and opportunities. Sales pitches or new types of work are both good examples of this.</p><p>This creates a <em>pecking order</em> <em>effect</em>: those people chosen into the squads get better faster, because they have more opportunity, and they learn on harder problems. Their heightened skills then reinforce the initial perceptual bias with a genuine experience-level difference, <strong><em>increasing their chance of getting chosen next time.</em></strong></p><p>These first team “starters” become the perennial squad members that will climb in the meritocratic hierarchy together, cementing their <em>in-group tribe</em> as only we humans can do — winners get the raises and the promotions while other just stand on the sidelines, wait and watch.</p><p>In many organizations we’ve worked with, this innate bias shows up as a large gap between how good the senior people are versus everyone else — it is an actual gap, perceptual, for sure, but also real. That gap finds has its roots in the effect of this assessment bias, repeated over and over. The agency example I gave above was just that. When we diminish the effect of bias upon inclusion, the other people got better faster…they became “awesome.”</p><p>Meritocracies typically possess a fire-fighter managerial class, one whose members are focused on being the smartest or best in the room. That class systematically neglects its true job of growing everyone else’s capabilities by excluding them, essentially <em>non-inclusion.</em> This has been a major subject of our coaching practice over the last several years. There are many subtle signals that one can use to diagnose this, but the most obvious one is when managers complain about the lack of capability in their teams. It is a difficult mindset shift for the former firefighter to realize that despite their success in climbing to the top, their job is to actually pull everyone else up with them, and lacking that, the model is broken for everyone else that got left behind.</p><p>In the winner-take-all meritocracy, that underpaid person whom nobody expects to become amazing, is locked in a spiral of non-inclusion, and lives down to what little is expected of them.</p><h3>Inclusion: The keystone to DEI</h3><p><em>Diversity</em> gets you a fair mix of people onto the team. <em>Equity</em> requires that you structure and assess compensation and rewards methodically and quantitatively, avoiding appraisal biases. But these events happen rarely, at most a few times during the year. <em>Inclusion</em> is how you make diversity and equity work.</p><p>Inclusion is how everyone gets a chance to win and learn the hard stuff. It is about what we do every day, and the key mechanism for disabling the day-to day effects of innate biases, In-Group dynamics, and the pecking order effect. But how do you be inclusive? You need to make structural change.</p><p>Breaking the <em>In-Group and pecking order spiral</em> requires that we fight the <em>manager’s blindness to people’s greatness</em> by removing the method that implements their bias: the choosing. We require managers to assign squads with a methodical randomness, not by choosing based upon perception or preference.</p><p>Assigning squads without the safety of our biases can be frightening to a manager who feels that this project or pitch must go perfectly, or else. But it is rarely true that the team is the major factor — projects always have challenges, and pitches get lost for many reasons — but more important, the fairly-shared chance to play on the squad means that we are building a broader base of talent inside the organization, and more important, giving everyone a change to play, fail, learn and grow. Building a business with the shoulders of many, rather than on the backs of a few, makes for a stronger organization, and happier people.</p><p>Increased inclusion happens when we counter unconscious bias with <em>an explicit and well-described model of behavior</em>, in this case, a set of behaviors that empower everyone at the worker-level, and decrease (but not remove) the influence of the managerial class and its biases in selection.</p><h3>Inclusion: Platitudes Don’t Work</h3><p>Hopefully now, you have a better understanding of my opening paragraphs: I complained about people saying things but not defining the hard stuff, the specific changes in behaviors that will create different outcomes. Here’s a simplified example from my keynote presentations at the 4A’s Talent 2030 conference last year (slightly modified but you can see the original <a href="https://app.box.com/s/u6jbsx6to2r9cur2s0b29njomn8b15q7">here</a>.</p><p>Company A and Company B are both concerned with Inclusion. They both make posters with their message on it, send out an email to everyone, hold a somber 9a.m. town hall meeting, and form an Inclusion committee to advance their message, and then everyone else goes back to work.</p><ul><li><em>Company A’s slogan: “We are inclusive,” and, “I always include my fellow workers”</em></li><li><em>Company B’ slogan: “Take turns and don’t be a jerk”</em></li></ul><p>Which one actually changes behavior and creates more inclusion…and why?</p><p>I can tell you empirically that Company B’s slogan, the second one, works better, and in fact, Company A’s slogan does nothing more than make a few people in leadership feel like they “did something” and leaves most other people confused about what to do.</p><p>Taking turns and someone not being a jerk, though, are both “scripts” that we humans know well. We can tell if they are happening — that means we can measure them — and actually we all know how to do them. People follow scripts.</p><p>It turns out that unscripted behavior change doesn’t work. Just doesn’t.</p><h3>Empowerment Requires Some Serious Attitude</h3><p>Building a culture of empowerment and inclusion is a matter of re-shaping hundreds of behaviors through several key process moments, like the choosing of squad members example above. The behaviors are necessarily simple, like how to take turns, mentor, and, well, not be a jerk. It also requires re-engineering of how to work more side-by-side than over-and-under — which is a more structural change.</p><p>Most important, though, is the needed attitude of leadership. New processes and behaviors must be rooted so deeply in the greatness that we all possess, and the organization must stay so methodologically committed that it won’t drift back to its old and very human biases.</p><p><em>Jack Skeels is a former management sciences analyst at the think tank, RAND, and the founder and CEO of </em><a href="https://agencyagile.com/"><em>AgencyAgile</em></a><em>, a productivity training and coaching firm that helps agencies, marketers, and other complex service organizations transform using empowered processes. His most recent project is a podcast, </em><a href="https://theartof.management/"><em>The Art of Management</em></a><em>, launching July 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b7f90a02584" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What my father taught me about DEI]]></title>
            <link>https://jackskeels.medium.com/what-my-father-taught-me-about-dei-fd34088a779c?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd34088a779c</guid>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[diveristy-and-inclusion]]></category>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 15:36:48 GMT</pubDate>
            <atom:updated>2020-07-02T15:46:16.952Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phEOTCMiinj6RT6DeRIQSg.jpeg" /></figure><h4>It was the 1960’s and 70’s, when race and gender lines were still being tested</h4><p>My father taught me a lot about Diversity, Equity and Inclusion (DEI) almost fifty years ago, though I certainly didn’t realize it at the time.</p><p>He was the chairman of the economics department at Northern Illinois University, a 20,000 student campus an hour away from Chicago. In the 1960’s and 1970’s it was his job to build a legit PhD program despite being surrounded by top-flight econ programs at far-more prestgious schools like the University of Chicago, Northwestern, University of Wisconsin-Madison and several others.</p><p>He succeeded in getting the PhD program accredited — which required that he find great talent and also that they publish great work — by taking advantage of <em>in-group, out-group bias.</em> Really good candidates were available if you weren’t trying to hire US-born white males. The best schools were bad at choosing, skipping over candidates that were otherwise awesome.</p><p>The team that he built was like the United Nations, and even had several women, an historic rarity in econ departments. The diversity of the staff was something that he was really proud of. The annual Econ Department picnic, its tables laden with dishes strange to a small midwest farming community, like kimchee, massaman curry, and strange round flatbreads stuffed with meat, to name a few, is clearly to blame for my lifelong addiction to strange and spicy foods. Many of those professors were great talents and moved on within five years, but they got their first shot at greatness because of his willingness, even desire, to be inclusive.</p><p>He taught me that you can only assess people by what they do, not what they look like, what they identify with, or how they speak. That’s because we are hopelessly bad at predicting that from appearance or presentment. In reality, all of us humans are actually ridiculously capable and motivated when given the chance to succeed…but that can be hard to see.</p><p>My dad would pay as much as he could for the talent he hired. And I’m pretty sure he never paid less than he could. That is, just because someone had been passed over by a more-prestigious employer, or didn’t have the best interviews, he didn’t try to hire them for less. It was principle on his part, but it turns out, a pretty smart one.</p><p>My dad also set up a scoring system for promotions, largely quantitative, it relied upon measureable stuff like ratings from students and the strength of the professors publications (this is measured by the number of citations and the quality of the journals.) When people delivered, they got paid. The long-tenured white gentry in the department, men that had been there long before he opened the door to minorities of all sorts, compained mightily when an Afghani got the next full professorship instead of they who had been waiting longer. Equity must be earned in a measureable way.</p><p>He never spoke of any of this directly, and maybe that’s why it has always seemed natural to me, the ideas that we teach of everyone getting to take a turn and play.</p><p><em>Jack Skeels is a former management sciences analyst at the think tank, RAND, and the founder and CEO of </em><a href="https://agencyagile.com/"><em>AgencyAgile</em></a><em>, a productivity training and coaching firm that helps agencies, marketers, and other complex service organizations transform using empowered processes. His most recent project is a podcast, </em><a href="https://theartof.management/"><em>The Art of Management</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd34088a779c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should probably never say “Agile”]]></title>
            <link>https://medium.com/swlh/why-you-should-probably-never-say-agile-df001a5bc22c?source=rss-235982f59e3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/df001a5bc22c</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[agile-management]]></category>
            <dc:creator><![CDATA[Jack Skeels]]></dc:creator>
            <pubDate>Thu, 07 May 2020 17:36:24 GMT</pubDate>
            <atom:updated>2020-05-14T13:37:15.631Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2dddVdSUGYXLl5apyqtwA.jpeg" /></figure><h4>The Agile Toolkit wasn’t made for you.</h4><p>In the world of business, the word “agile” has been over-used into virtual meaninglessness. It had a very specific meaning almost 20 years ago, and decayed rapidly under the distorting forces of rampant commercialization like I described in my <em>How Marketing is Destroying Agile</em> (<a href="http://bit.ly/AA-Destroying-Agile"><em>link</em></a>) article.</p><p>In 2014, Dave Thomas, one of the founders of agile, posted his own screed, titled <em>It’s Time to Kill Agile</em> (<a href="https://pragdave.me/blog/2014/03/04/time-to-kill-agile.html"><em>link</em></a>), calling for “agility” over “agile”. I would agree with Dave were it not for one thing: agility is even more poorly understood — really more of an attitude than anything — than Agile is; what do we possibly improve by making it more vague?</p><p>Having been around Agile for way longer than I would like to admit, and having had literally hundreds of conversations with copmpanies, well over 100 of which hired me and my team of neo-post-agile coaches to help them do something that creates results like you would expect from Agile, I can tell you most people think they know a lot but they don’t know shit.</p><p>I sometimes do an Agile IQ quiz with a new client, where there are a total of 100 points available for correct answers. I ask everyone how high they think they will score. People who rate themselves a 4 or 5 (out of 5) on an experience scale will predict that they will score 80 or more.</p><p>It is not a difficult quiz — if you know Agile pretty well, or even just understand how basic empowerment-in-action works, you’ll score 100 or close. Almost everyone scores less than 50.</p><p>The funny thing is, if they really understood what Agile is, or what it was designed to do, they would realize it is not for them, was not built for them. And in not doing so, they create and cling to the fad that is agile today for many, Random Agile.</p><p>In reality, Agile is a very specific thing built for a very specific situation. It is not easy to do, it is not “flexible” in the way that most people think of flexible…it requires a level of rigor and effort at customization that goes far beyond what people know.</p><h4>What is Agile?</h4><p>I’m sure you know the basic idea: it is a way to run a software development project. So here’s my question: does your work look like a software development project? Maybe, I guess it can at times, but let me explain more about what type of project these techniques were designed for.</p><p>Software Agile was designed over a 20 year period as a <em>set of techniques</em> that would help solve the problem of how to build <em>very large software systems</em>. You can read more about that here, in a book published in the 1970’s called <em>The Mythical Man-Month </em>(<a href="https://www.amazon.com/Mythical-Man-Month-Anniversary-Software-Engineering-ebook/dp/B00B8USS14/ref=sr_1_1?crid=3MCUNMC5XAJ80&amp;dchild=1&amp;keywords=mythical+man+month&amp;qid=1589305403&amp;sprefix=mythical%2Caps%2C203&amp;sr=8-1">link</a>). How large of a project? We’re talking 200 staff years worth of work, maybe 50 people all working on the same (one) thing for four years. Does your work look like that?</p><p>You’re probably familiar with some of the Agile techniques, like the stand-up meeting, or the lightweight planning (sticky-notes-on-a-wall) technique, but do you know what the fundamental problem was that Agile solved? Was it that software developer teams were not “agile” enough? No.</p><p>The problem was that very large projects are very hard to describe, define and understand. In fact, the size of the written specification for a 200 staff year project is so large that nobody could really understand it, and fewer people could even say whether it is right. Does your work include a lot of things that are so hard to understand that you can’t write them all down? No, nor does 99.9% of all other work in this world.</p><p>Agile was built for 0.01% of all projects in the world.</p><p>A key concept in Agile is the team. But Agile teams aren’t like your teams. These teams are dedicated to work <em>on a single project</em> for several years. Not your teams. Another important part of Agile is that the team should not be bothered by managers, or changing needs, or other projects. Agile dictated to managers: “Stay the f**k away from the team.” That is hard for anyone to honor, but much easier if you know they are only working on one thing and it will take a long while as was the case with Agile. Would your business function if you had to leave teams in isolation for two weeks before you could ask them to work on something different? Probably not.</p><p>Here’s what Agile is:</p><ul><li>a detailed set of processes designed for a very specific and rare business situation</li><li>a method by which dedicated teams can “chip away” at the project, choosing which part to work on next (this is the “agile” part), in order to more quickly build the right parts</li><li>a framework in which teams work in isolation on a singular project for an extended period of time</li><li>A framework, method and processes which requires months of tuning of by expert facilitator and coach in order to optimize how all the pieces work for a specific team</li></ul><h4>Unless it is purpose-built for you, it’s just Random Agile</h4><p>Even way back when it all started, Software Agile was always hand-crafted for each team and project. This is the part that people seem to not understand. Software Agile was a one-off that required the coach to work full-time with the team for months. Each and every team.</p><p>Every truly effective implementation of agile is a one-off that has been highly tuned for the specific situation. We’ve worked with over one hundred clients and all of them thought they knew Agile, and none, really none of them were even close to getting any of it right.</p><p>For those of you that geek out on this, here is a more modern example of how a (really good) purpose-built Agile works only where intended. There is a specific set of Agile practices, called <em>SAFe</em>, designed for production software work. Note, this is different than the original Agile (big, unknowable software) problem I described above. Rather, SAFe is designed for environments that have <em>multiple software projects</em> going on, and often have shared resources, and better-defined specifications, etc. SAFe is a different <em>purpose-built version </em>of Agile (read: non-random), and from what I hear, it works pretty well in that situation.</p><p>A few years back a client called us to coach them on Agile — what that really means is, “Can you make it work for us?”— and they were already using SAFe, and they said it was working really well. Huh? Why call us?</p><p>Turns out that this company was really two companies in one: they did sweepstake and promotional marketing, so half of the company wrote software for a massive “sweepstakes engine” which was big, complex and always evolving software platform, and the other half of the company actually did the marketing .</p><p>Guess what, SAFe didn’t work in a marketing environment. <em>Becuase it wasn’t made for that purpose.</em> We showed them how to craft their own agile toolkit for marketing , and viola, they were Agile with some amazing results. <a href="http://bit.ly/HW-Case"><em>You can read more about it here.</em></a> I offer it as evidence that every form of Agile, in fact pretty much every instance of Agile needs to be purpose-built.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ioj9eRAXQVbq3qg6xqkJyg.jpeg" /></figure><h4>The Agile toolkit is just a random box of tools some dudes named “Agile”</h4><p>The biggest misconception is that somehow these “agile techniques” are actually a general purpose toolkit. (Yet another way that the commercialization of Agile has destroyed it.) And for the most part, there are no “Agile” tools at all — every single item in that toolkit existed prior to the word Agile. Let me explain.</p><p>Imagine two real-world toolkits, one for an iPhone repair technician, and one for a plumber. Would the iPhone toolkit be useful for the plumber or vice versa? No, because they are such different applications. Could a watch repair person benefit from the iPhone toolkit? Possibly there might overlap that means that some of the tools can be applied, <em>but they would likely not be optimal without significant additions or modifications</em>.</p><p>Software agile plucked the “iteration” tool created at least twenty-years prior from a thing called Iterative Enhanced Project Management (IEPM), and renamed it a “sprint.” It lifted the Kanban tool, created in the 1940’s by Taiichi Ohno for the Toyota Production System, a manufacturing management method, and tweaked it for software. They also added the stand-up meeting, which probably has its origins in <em>homo sapiens</em> standing around the morning fire to talk about who will do what that day.</p><p>Enter the dudes. In 2001, after 10+ years of experimenting with a whole bunch of tools, 17 middle-aged programmers held a conclave in Snowbird, UT, and named the collection of tools that they preferred to use, “Agile.”</p><p>You want to use Agile? You need to make your own toolkit. Those dudes in Snowbird had no idea how your business operates or what it needs.</p><h4>Why being agile, as in “agility,” doesn’t count</h4><p>I cover this in more detail in another article called, <em>The Elusive Search for Organizational Agile</em> (<a href="http://bit.ly/elusive-agile"><em>link</em></a>), in which I try to enumerate all the ways people say they are doing agile, but are not. At the far end of the spectrum are things like, “Hey, let’s all agree to just be more Agile.”</p><p>My favorite one from years ago was when I was asking which people we could count on to be part of the team that we would coach, and the executive replied that he wasn’t sure, but they would make sure that we always had someone. He said, “Hey, we don’t really need to be specific on this, do we? I mean, can’t we just be Agile?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4OxBrLNdNlb1vnFDjsyGA.jpeg" /></figure><p>He had correctly identified that an aspect of Agile is dealing with uncertainty and then decided to co-opt it to mean that he didn’t need to make a commitment on anything. Nimble and deft in his handling of my question, yes, but he was not being Agile.</p><p>In order for us to change behaviors, change the way we work, we need to be specific about what the change is. Change doesn’t happen by platitude, but rather by well-explained and practiced behaviors. Tell people how to do a stand-up meeting, and they will fail. Make them do a stand-up, coaching them into a set of self-managed behaviors, repeat that 4–10 times and they’ll actually be good at it.</p><p>Random Agile, the type of Agile that exists in name only, is the result of platitudinous Agile behavior, using the word without any idea (or commitment) to do the hard parts. It makes Agile look like another management fad. I believe it has become that in the minds of many.</p><h4>When its okay to say Agile</h4><p>Here’s my short of situations in which you can say you’re doing or being Agile and actually be real about it:</p><ul><li>You are running a software project and authentically using a well-coached and tuned set of Agile tools. This includes something like SAFe if implemented authentically, and it is a fit for how you operate, the types of work and teams you have</li><li>You took the time and did the hard work of crafting your own purpose-built Agile toolkit, and as evidence, the nature of your organization has changed, especially the way managers yeild to teams and the whole organization becomes much more “flat” in style</li><li>You implemented your purpose-built Agile toolkit, and as evidence, the 20–50% of those people whom you had thought of as marginal performers, are actually really solid performers. You realize that the biggest obstacle that they faced was being poorly- or over-managed</li></ul><p>I hope for you and many others to be able to authentically make the claim of being Agile. In reality, we both know people can say whatever they want. But now you know that I’ll be watching.</p><p><em>Jack is a recovering client services executive, former senior analyst at RAND, and the founder and CEO of </em><a href="http://www.agencyagile.com/"><em>AgencyAgile</em></a><em>, a productivity training and coaching firm that helps agencies, marketers, and other complex service organizations transform using Agile and empowered processes</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df001a5bc22c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/why-you-should-probably-never-say-agile-df001a5bc22c">Why you should probably never say “Agile”</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>