<?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 Robin Cannon on Medium]]></title>
        <description><![CDATA[Stories by Robin Cannon on Medium]]></description>
        <link>https://medium.com/@shinytoyrobots?source=rss-705013235ecb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7rjpj9CHj37kNqLk3jJjeQ.jpeg</url>
            <title>Stories by Robin Cannon on Medium</title>
            <link>https://medium.com/@shinytoyrobots?source=rss-705013235ecb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:38:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shinytoyrobots/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[Carbon v10 Release]]></title>
            <link>https://medium.com/carbondesign/carbon-v10-release-812eacb7da7f?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/812eacb7da7f</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ibm]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Thu, 04 Apr 2019 21:42:03 GMT</pubDate>
            <atom:updated>2019-04-04T23:20:32.413Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dv_27YAf-buFFo61kruotw.png" /></figure><p>We’re excited to announce the official release of <a href="https://www.carbondesignsystem.com/">Carbon Design System v10</a>.</p><p>IBM announced the new <a href="https://www.ibm.com/design/language/">IBM Design Language</a> at <a href="https://www.ibm.com/events/think/">THINK 2019</a>. The Carbon Design System is the practical application of the philosophy of the IBM Design Language. It’s the official design system for software and digital products at IBM.</p><h3><strong>Introducing Carbon v10</strong></h3><p>Carbon v10 represents a total visual overhaul of the design system. It refines the user experience and offers expanded theming and tokenization options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gv_5yXA8gvqBJo1cZFZN6g.gif" /></figure><p>Core functionality maintains parity with v9. The core components of the Carbon Design System have been updated to v10. We’ve worked to keep breaking changes to a minimum.</p><p>The <a href="https://www.carbondesignsystem.com/">Carbon website</a> provides expanded and more rigorous guidance and documentation. Users should have as much information as possible while exploring Carbon. That includes clear guidance on migrating from previous Carbon versions.</p><h3>Carbon v10 release summary</h3><ul><li>Carbon has a revamped look and feel.</li><li>Introduction of <a href="https://github.com/ibm/carbon-elements">Carbon Elements</a> and corresponding guidance. These are the building blocks that make up the Carbon Design System.</li><li>More guidance around <a href="https://www.carbondesignsystem.com/guidelines/color/overview">color</a>, <a href="https://www.carbondesignsystem.com/guidelines/typography/overview">type</a>, and <a href="https://www.carbondesignsystem.com/guidelines/layout">layout</a>.</li><li>A switch to an 8px base unit grid.</li><li>New themes with added token depth, new type tokens, and revised spacing tokens.</li><li>Updated perspective on motion. Guidance on micro-interactions and impactful animated moments.</li><li>Expanded and updated <a href="https://www.carbondesignsystem.com/guidelines/accessibility/overview">accessibility guidelines</a>.</li><li>Updated Carbon Design Kit functionality;<br>- Available on Sketch Cloud, with library syncing.<br>- More configurable symbols for building and theming.</li></ul><h3>Expanded tooling</h3><p>The best design systems help design workflows at scale. Carbon’s tooling tries to encourage best practices, while still embracing alternate workflows.</p><p>The Carbon Design Kit is now hosted on Sketch Cloud. Users can receive updates without leaving Sketch. Symbols in the kit are now more configurable for building and theming user interfaces.</p><p><a href="https://sketch.cloud/s/JaVzz">Sketch Cloud</a></p><h3>A design system everyone can own</h3><p>Carbon is IBM’s Design System. But it’s also an open source project. It’s available to anyone who wants to build with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7CDZ729T-YBCBch8o-0aQ.png" /></figure><p>Over the last few months we’ve reorganized our GitHub repositories. Carbon’s code and our issues and roadmap are public. We want the Carbon community to grow and become more involved. That’s the only way we can support Carbon components across <a href="https://github.com/ibm/carbon-components">vanilla javascript</a>, <a href="https://github.com/ibm/carbon-components-react">React</a>, <a href="https://github.com/ibm/carbon-components-angular">Angular</a>, and <a href="https://github.com/carbon-design-system/carbon-components-vue">Vue</a>.</p><p>For information on how to contribute as a <a href="https://www.carbondesignsystem.com/contributing/designers">designer</a> or as a <a href="https://www.carbondesignsystem.com/contributing/developers">developer</a>, check the <a href="https://www.carbondesignsystem.com/">Carbon website</a>.</p><h3>Start using Carbon</h3><p>If you’re new to Carbon, start with our <a href="https://www.carbondesignsystem.com/getting-started/about-carbon">getting started guide</a>. It has everything you need to design and develop with Carbon.</p><p>If you’re looking to migrate existing projects to v10, head over to our <a href="https://www.carbondesignsystem.com/updates/v10-migration/overview">migration guide</a>. It has tools, guidance, and resources for you to get started with v10 today.</p><h3>We want (and need) your help</h3><p>Building this system wouldn’t be possible without your contributions, suggestions, and critiques.</p><p>Run into any issues or have feedback for us? Please make an issue, or submit a pull request, on our project over on <a href="https://www.carbondesignsystem.com/resources#github-repos">GitHub</a>.</p><p><em>If you haven’t heard of the Carbon Design System before, </em><a href="https://www.carbondesignsystem.com/"><em>check us out</em></a><em>! We’re the design system for IBM, shipping open-source styles and components in </em><a href="https://github.com/ibm/carbon-components"><em>vanilla</em></a><em>, </em><a href="https://github.com/ibm/carbon-components-react"><em>React</em></a><em>, </em><a href="https://github.com/ibm/carbon-components-angular"><em>Angular</em></a><em>, and </em><a href="https://github.com/carbon-design-system/carbon-components-vue"><em>Vue</em></a><em> for anyone building on the web.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=812eacb7da7f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/carbondesign/carbon-v10-release-812eacb7da7f">Carbon v10 Release</a> was originally published in <a href="https://medium.com/carbondesign">_carbondesign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to Expect in Carbon 10]]></title>
            <link>https://medium.com/carbondesign/what-to-expect-in-carbon-10-5af1bd6e25f6?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/5af1bd6e25f6</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Mon, 10 Dec 2018 23:07:21 GMT</pubDate>
            <atom:updated>2019-04-25T20:05:46.625Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phjbcNJzTax4YiDxsmUcxA.png" /></figure><p>It’s coming up to the end of the year, when we’d usually schedule a major Carbon Design System release. The team is going to do things a little differently this time around.</p><p>Since October, we’ve had an “Experimental” section at <a href="http://carbondesignsystem.com/">carbondesignsystem.com</a>. These new components, elements and patterns build on the updated IBM Design Language, are the next step for the design system, and a major design evolution. In our next major release, these “experimental” resources will be production-ready.</p><p>This is a more significant change than usual, so we want to keep everyone informed of our plans.</p><h3>Carbon v10 Alpha Release</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/1*CoTS2qKCy-1aOk6G_-4AHQ.jpeg" /></figure><p>Before the end of the December, we’ll release an alpha version of Carbon v10 which will be available at <a href="http://next.carbondesignsystem.com/">next.carbondesignsystem.com</a>. It will include;</p><ul><li>Carbon Elements — icons, layout, grid, etc</li><li>New components</li><li>UI Shell</li></ul><p>This work isn’t ready for production use, but we want to give you an early preview of what’s coming. As always, we encourage feedback and contributions.</p><p>During the alpha availability, we’ll be making updates, adding documentation and guidance. The scope of the release is subject to change.</p><h3>Carbon v10 Beta Release</h3><p>In the second half of January, we’ll upgrade our alpha version into a beta release. Which will continue to be available at next.carbondesignsystem.com.</p><p>Designers and developers will be able to use these resources with more confidence. The beta version will confirm the scope of the production release. We’ll provide expanded guidance, and updated components, elements, and other resources.</p><p>If you’re using a previous version of Carbon, we’ll have more help on transitioning to v10.</p><p>You can also expect significant design changes to the Carbon Design System website.</p><h3>Carbon v10 Production Release</h3><p>In the early Spring we’ll announce the full production release of Carbon v10. We aim to do this by IBM Think 2019.</p><p>The updated website design and content will be live by Think (even if other resources are still in beta). This will coincide with updates to the IBM Design and IBM Design Language websites.</p><p>We’ll communicate the release, and offer sessions providing transition and adoption guidance.</p><p>Of course, we know people can’t update instantly, so you’ll still be able to access Carbon v9 at v9.carbondesignsystem.com</p><p>You might also see a change to the “Carbon” brand as we’ll be more closely integrated with other IBM Design guidance, and the updated IBM Design Language.</p><p>But even if we change our name, we’ll still be open-source and community-driven.</p><h3>Further in the Future</h3><p>After Carbon v10, we expect to move to a Spring/Fall release schedule. In Summer/Winter we’ll be providing developer and designer previews. So you’ll always know what’s coming down the line in the next release.</p><p>If you have any questions, we always want you to reach out. Submit issues in our repos (or contribute code). Email us at <a href="/service/mailto:carbon@us.ibm.com">carbon@us.ibm.com</a>, or contact us at the <a href="https://twitter.com/_carbondesign">@_carbondesign</a> Twitter handle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5af1bd6e25f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/carbondesign/what-to-expect-in-carbon-10-5af1bd6e25f6">What to Expect in Carbon 10</a> was originally published in <a href="https://medium.com/carbondesign">_carbondesign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Never Stop Asking “Why?”]]></title>
            <link>https://medium.com/@shinytoyrobots/never-stop-asking-why-714d2e92a2e7?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/714d2e92a2e7</guid>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Fri, 26 Jan 2018 15:26:33 GMT</pubDate>
            <atom:updated>2018-01-26T15:26:33.058Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WeZkJPHYfD27wwajqa-N3Q.jpeg" /></figure><p>Remember when you were a kid and the most interesting question in the world is “why?” It’s one of the ways children learn about the world, by being permanently curious. The conversations that go on and on until a parent finally gives up and says “because I said so.” Remember how frustrating that was as a child?</p><p>“Because I said so” is still a bad answer. But as adults we often don’t delve deeper in the same way we did as children.</p><p>It’s the start of the new year. In many companies that means there are new priorities coming down. New lists of features. New demands for work. And a lot of them lacking the deep dive into “why?” that they need.</p><p>Without delving deeper into answering “why?”, our ranking of work is going to be subjective at best.</p><p>I recently had a discussion about improving a dashboard in our UX. Several stakeholders wanted us to put effort into design and development. I asked why.</p><p><em>“Because we don’t think it’s good enough.”</em></p><p>OK…I don’t disagree. But that’s pretty nebulous. So, I asked why it isn’t good enough.</p><p><em>“People can’t manage their apps and services well enough”</em></p><p>Again, I don’t disagree. But, so what? I asked why that was important.</p><p><em>“If people can’t manage their apps and services easily, they don’t add extra functionality. They don’t create new services.”</em></p><p>Seems to make sense. But, again, why is that important?</p><p><em>“If users have more interconnected services, their lifespan as a customer increases.”</em></p><p>OK…now we’re getting somewhere. Our real aim is “we want to make creating and linking services something that users want to do more”. And we have a good business reason behind that, too. It reduces our user churn.</p><p>— -</p><p>If we didn’t delve deeper, our target would be “make the dashboard better”. And the only measurement would be a subjective one.</p><p>Now we have a more detailed aim, we can come up with more specific solutions. We want to make creating and linking services something that users want to do.</p><p>Let’s say that our analytics suggest a slow search function puts people off creating services. The biggest drop off in usage is when people wait more than 3 seconds for search results. Our average search result time is 4 seconds.</p><p>That’s the basis for a genuine hypothesis. We can expand that with more study of analytics. And we can make some educated guesses. We might end up with;</p><p><em>“Reducing our average search time by 25% will lead to a 10% increase in the number of services a user creates.”</em></p><p>And, with enough user data already stored, we could make a good guess the business impact.</p><p><em>“A 10% increase in the number of services a user creates will mean a users stay with us an average of 3% longer.”</em></p><p>Now we have a measurable piece of work (reduce search time by 25%). We have a hypothesis of the impact on users. And a hypothesis on the business impact.</p><p>(I’m making these specifics up to demonstrate the point, in case anyone is hoping to pick up any secrets!)</p><p>— -</p><p>Those specifics are the vital pieces of information we need to make business decisions. They help us rank the importance of work.</p><ul><li>We can scope the specific work. That will give us a good idea of the time / cost of making that change.</li><li>We can compare that time / cost with our predicted results and business benefits. Is there a return on investment?</li><li>Even if there is a return on investment, is it the best option? Is there something that takes less work, but with a similar impact? Or is there another piece of work that will have more impact? Do that work first.</li></ul><p>And, if we do this work, we can <strong>measure the results</strong>. We can tell whether it was successful in the way that we predicted. Or our hypothesis was wrong. If it is wrong, we’ve still learned something by disproving it.</p><p>None of that is possible unless we keep asking “why?”. If we don’t, then we’ve got a vague “make something better”. We don’t have any objective measures of success or failure. And no way to determine if this is more or less important than another piece of work. We won’t prioritize well. And we won’t learn how to get better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=714d2e92a2e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protecting your sprint]]></title>
            <link>https://medium.com/@shinytoyrobots/protecting-your-sprint-c45d0e25bd?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c45d0e25bd</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 18:38:10 GMT</pubDate>
            <atom:updated>2017-11-14T18:38:10.716Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JDgBXUJPsLW3VNSzZRdfAw.jpeg" /></figure><p>A sprint is the most common piece of the Agile process that companies adopt. Even if the rest of their <a href="https://medium.com/@shinytoyrobots/agile-principles-versus-reality-f2e3ffcba58">Agile understanding is imperfect</a>, they still have sprints. At worst, that’s arbitrary two-week time blocks towards a waterfall delivery. At best it’s an integral part of a Scrum process of iterative delivery.</p><p>And sprints are always under pressure from external factors. Even if you get buy in to allow the sprint team to estimate their work, something new comes up. There’s an emergency. There’s a last minute piece of work. All things which undermine not only that sprint, but the point of sprints at all.</p><p>The biggest benefit of sprints is that they create predictability and transparency. The team estimates how much work they can do, delivers an iteration, and has a retrospective. Over time, their estimation gets better, and the sprints become more predictable. With my teams, I can say with a very high degree of confidence that what we put in a sprint will finished in that sprint.</p><p>That only works if I can protect my sprint. And there is very often an “emergency” that puts pressure on the sprint. Something that comes up mid sprint, at short notice, and needs doing fast.</p><h4>The solution is not to work more hours.</h4><p>Not only does this have the problem of <a href="https://medium.com/@shinytoyrobots/crunch-time-even-if-you-succeed-you-fail-835af4305bad">“crunch time”</a>, it undermines the long-term benefit of sprints.</p><p>One of the biggest benefits of having sprints is having predictability. That means that the same number of people, in the same period of time, can do a certain amount of work. A team reaches that predictability over time, by learning and refining their processes. If extra work adds to a sprint, and adds to the work hours, I can’t reach predictability. A short-term emergency has long-term negative impacts on predictable delivery.</p><p>Doing that extra work also rewards bad behavior, or false expectations. Once you say “yes” to undermining your sprint once, it’ll get undermined again. You’ll lose all the benefits of predictability. A sprint becomes a variable, not consistent, period of work.</p><h4>The concept of a “silver bullet”</h4><p>The best way to defend the sprint is to define a standard for “silver bullets”. These are those emergencies that need work. But the solution is not to add more work, it’s to replace existing work.</p><p>Emergency work should be defined like any other work. And once it’s defined, it can be sized like any other work.</p><p>If the work is sized, then the next step is to go back to the stakeholder and ask what they want replaced. Say the emergency piece of work is five story points. If there are more than five story points worth of work in the sprint that hasn’t been started yet, swap it out.</p><p>This makes the decision about the emergency work a business decision. The stakeholder needs to choose which pieces of work are more important. The sprint stays predictable, the scope doesn’t change much. We can be confident the “silver bullet” can ship.</p><p>If there’s more than one stakeholder defining work, then they need to agree on the swap.</p><p>This protects the scope of the sprint. But it has an extra benefit. If you tell someone their “emergency issue” needs to replace something…very often it’s suddenly less of an emergency!</p><p>Sprints are not arbitrary blocks of time. They exist for a reason. Even if they’re the only part of Agile process you’ve adopted, work to protect them.</p><p>Well protected sprints bring transparency and predictability to work. By doing so, they provide a foundation for long-term efficiency and performance. Don’t let that be undermined by short-term demands.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c45d0e25bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There is no good time to take vacation]]></title>
            <link>https://medium.com/@shinytoyrobots/there-is-no-good-time-to-take-vacation-89acfe613035?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/89acfe613035</guid>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[vacation]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Wed, 27 Sep 2017 04:21:42 GMT</pubDate>
            <atom:updated>2017-09-27T04:21:42.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ak4KI3dk2hxFJvmXGh1vmg.jpeg" /></figure><p>A few years ago, I was managing a team during “<a href="https://medium.com/@shinytoyrobots/crunch-time-even-if-you-succeed-you-fail-835af4305bad">crunch time</a>”. There was lots of pressure from above, and unrealistic timelines. One of my developers had a vacation scheduled. I think he was going to Hawaii. It came up in a discussion with a VP of Engineering, who said I should ask him to postpone the vacation. I refused. I thought it was a completely unreasonable suggestion.</p><p>That VP was pissed that I refused to even consider the suggestion. I’m happy to take that as a measure of him, not of me.</p><p>Vacation policy often comes up in interviews. Or in 1–1 discussions with members of my team. People ask what are “good” times to take vacations. My response is pretty simple. There is no good time. There is no particularly convenient time. And that’s fine. Vacations aren’t for the company to define, they’re for the benefit of the employee.</p><p>Nobody knows better that they need or want a vacation than the person taking it. In the US in particular, vacation time is limited enough. Adding further restrictions on when someone can take that vacation is punitive.</p><p>Vacations are often presented as a favor from a company to an employee. That’s far from the truth. Vacations are a necessary part of ensuring people stay energized and enthusiastic. Feeling their work helps enable their life, rather than restricting it. Energized and enthusiastic employees are motivated and productive ones. Those are the kind of people I want on my team.</p><p>Refusing a vacation because it’s inconvenient is unproductive. The benefit I could get from having a team member available at a particular time is momentary. I want them to be feel invested in their work, and feel that they’re treated like adults. I trust them to make decisions that are right for them.</p><p>If someone is trying to find a “convenient” time to have a vacation, it’s impossible. In a busy company there’s always something more than needs doing. There’s always an upcoming release that needs work now. There’s no good time for me to have a member of my team unavailable for a week or two. Which means that any time is fine.</p><p>And it all works. People behave responsibly. If they’re booking a vacation far in advance then it’s easy to factor that into work planning. If there’s a big release next week, there aren’t many people who are going to ask for time off at the last minute. If they need to, chances are it’s an emergency.</p><p>Last week in a 1–1, a team member brought up a vacation request. The dates they want to go on vacation coincide with what I know will be a very busy week. We had a good discussion. I said that if they hadn’t booked it yet, and were flexible, it’d be great if they could push it back a week. I also made it clear that was only a request.</p><p>That’s the furthest I’ll ever go in suggesting any limitation to vacation. A week’s delay if it’s not time critical for the employee. The decision is still theirs. And no choice they make will make me look negatively at them.</p><p>People have lives outside work. They have other people whose lives interact with theirs. These don’t take second place to a short term need at work. Nor should they.</p><p>In building teams, in helping companies that I work for, I want sustainable success. Not reactive short term action at the expense of the long term good. Vacation planning is part of that. Of realizing that it’s something my team are entitled to.</p><p>Their vacations, taken at their convenience, will bring benefit to the company. Long term benefit. Benefit that outweighs any short term advantage to having them in the office that one extra-busy week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89acfe613035" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Positive Transparency]]></title>
            <link>https://medium.com/@shinytoyrobots/positive-transparency-9faa43058e53?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/9faa43058e53</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Mon, 25 Sep 2017 02:36:59 GMT</pubDate>
            <atom:updated>2017-09-25T02:36:59.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xxQXASDZYvIMTiPXvl8QSQ.png" /></figure><p>I’m very transparent with my team. I believe in openness. We talk about what we’re doing, what other people are doing, how things are going. We discuss the reasons behind our work. I try to communicate as much as possible what’s happening on a broader scale. We share hopes and fears, both as a team and in weekly 1–1 meetings.</p><p>And, in general, this is a great thing. A manager should trust their team. Trust them to do good work without interference. But also trust them with knowledge and information. Trust them to know the “why” of things. And be able to be honest and up front about the bad as well as the good.</p><p>This week I had some conversations that encouraged some self reflection. For the last couple of weeks I’d been frustrated. I had a few problems with the direction of some work.</p><p>Everyone has those issues, I’m sure. But I’d been too transparent about those frustrations. I let some of that negativity affect my interaction with my team. I made a couple of bad, or questionable, decisions on how I approached things. Vented a few times. Not been a positive influence.</p><p>Transparency should encourage a forward-looking attitude. Frank conversations are important. Identifying problems and concerns, and feeling free to raise them, is important. But in a way that encourages solutions and action. Not in a way which reinforces negativity.</p><p>My mistake wasn’t that I was open about my concerns. The mistake was that I focused on my frustration rather than talking about next steps. If a conversation is about how something is bad, then I’m not enabling my team. I’m only giving the option to agree that things are bad, or disagree and say that things are good!</p><p>Being open and transparent should encourage action. If I’m expressing a concern, it should be with a focus on how to mitigate the problem. About how to reduce its severity. If I’m talking about how something isn’t good enough, I should be prompting ideas to make it better.</p><p>I wasn’t running around all week crying that the sky was falling. But I definitely let myself be more negative than usual. I’m lucky that I have a great management chain. My 1–1s with them provoked that self reflection. They didn’t have to tell me what to do, but they helped coax that assessment from me.</p><p>I think it was in a <a href="https://www.manager-tools.com/">Manager Tools</a> podcast that I heard a great snippet. A direct manager is the most immediate representation of “the company” to any employee. That’s worth remembering.</p><p>I’m human, and imperfect. I’m not going to beat myself up about a mistake. I’m not going to stop being open with my team. But I’ll do so with a greater understanding of how I present myself, and how it affects them.</p><p>It’s important as that leader to encourage positivity. Not in a false “nothing is ever bad” kind of way. But in a way that makes people enthusiastic about pushing to make things better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9faa43058e53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crunch Time — Even if you Succeed, you Fail]]></title>
            <link>https://medium.com/@shinytoyrobots/crunch-time-even-if-you-succeed-you-fail-835af4305bad?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/835af4305bad</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Sat, 23 Sep 2017 22:11:15 GMT</pubDate>
            <atom:updated>2017-09-23T22:11:15.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B8UJ7vnjb_evkcVnKgwudg.png" /></figure><p>In every tech job I’ve ever worked there has been pressure to put in more hours close to delivery. The demand to work evenings and weekends to ship something by a deadline. More hours = more work remains an intuitive belief. It’s also disproven by pretty much every piece of research on the topic, going back over a century.</p><p>“Crunch time” isn’t pointless. It’s even worse than that. One of the most irritating parts of working in development is also counterproductive. It fails in the short term; it doesn’t deliver more work. It fails in the medium term; time is wasted fixing flaws caused by rushed work. It fails in the long term; it undermines enthusiasm and retention, which costs a company more.</p><p><a href="#cabd">The weight of evidence is clear.</a> Believing that long hours mean better delivery is the same as believing climate change doesn’t exist because it’s cold outside.</p><p><strong>The Short Term</strong></p><p>It’s the supposed short term gains that provoke crunch time. There’s pressure to deliver by a date. There are calls to work lots of extra hours. And something gets delivered, and everyone kind of celebrates.</p><blockquote>Crunch time punishes practitioners for planning failure. “Success” means leadership gets away with that failure. This process then repeats.</blockquote><p>More hours worked leads to diminishing returns per hour. Working more than 40–50 hours a week doesn’t only lead to reduced output per hour. It leads to such reduced output that people would have got more done if they’d worked fewer hours.</p><p>You can <em>maybe</em><strong><em> </em></strong>get away with it in the very short term. A couple of weeks of some extended hours can boost productivity. But that’s short term productivity only. It leads to negative impacts further down the line.</p><p><strong>The Medium Term</strong></p><p>Some of those diminishing returns only come to light after something ships. The reduced productivity becomes clear in the number of errors and flaws. More things need fixing. And in most cases, everyone’s already moved onto the next new thing. There isn’t enough scope to fix those problems.</p><p>And everyone is tired. The recovery period from crunch time is longer than the crunch time itself. People are less productive because they’re fatigued.</p><p>That compounds the issue. Fixing issues delays new work. Fatigue reduces productivity. So in a few weeks or months we’re into the same crunch time problem again.</p><p><strong>The Long Term</strong></p><p>I think two of the biggest costs from crunch time and long hours come in the long term. And they’re two of the most overlooked problems.</p><ul><li>A lack of predictability. In an Agile environment we want teams to get better at estimating their work, and their sprints. That requires consistency. If the hours are ever changing, the estimates become pointless.</li><li>Retention problems. People burn out. They leave. This means losing a subject matter expert. That delays new work. It also leads to the cost of recruiting someone new. And the time and costs of training them up to the same level.</li></ul><p>Those long term problems exacerbate the short term and medium term problems. They make them happen again. I see it as stumbling forward, over and over.</p><blockquote>Well done everyone, I know it took long hours and weekends, but we delivered.</blockquote><p>I’ve heard that many times. It’s a fundamental failure in the process.</p><p>Shipping something is a time when people celebrate. And because it’s a time of celebration, not enough people ask if it was worth the cost. Shipping something “proves” that crunch time works. Many of the problems don’t come to light until later. And then it’s too late, there’s already pressure to deliver something new.</p><p>I’d prefer crunch time to fail outright on a more consistent basis. Its “success” isn’t because of the long hours, but in spite of them.</p><p>I push back hard against crunch time. Not because I want to avoid hard work. It’s because I want to delivery high quality, sustainable work. I want to do so in the most productive way possible. And I trust the research data that tells me how that’s achieved.</p><p>I enforce, as far as possible, a standard on my team that nobody is obliged to work more than 40 hours a week. Given the authority, I’d even change that to “not allowed” to work more than 40 hours a week.</p><p>That can cause problems, but they’re problems of perception. One team is working longer hours than mine, and they think it’s unfair. But I’m not counting hours. I’m counting productivity. And I’m always happy to measure my team’s output and quality against another’s.</p><p>I don’t always succeed in keeping my and my team’s hours to the most productive level. But I’ll protect my team as much as I can. And I’ve been reasonably successful in maintaining that balance. I want me and my team to succeed in the short term and in the long term. It’s one of the most important principles in how I manage.</p><ul><li><a href="http://www.salon.com/2012/03/14/bring_back_the_40_hour_work_week/">Bring back the 40-hour work week</a> (Salon.com)</li><li><a href="http://www.alternet.org/story/154518/why_we_have_to_go_back_to_a_40-hour_work_week_to_keep_our_sanity">Why we have to go back to a 40-hour work week to keep our sanity</a> (AlterNet)</li><li><a href="https://blog.trello.com/swedens-six-hour-work-day">The science behind Sweden’s six-hour work day</a> (Trello)</li><li><a href="https://www.fastcompany.com/3048751/happy-employees-are-12-more-productive-at-work">Why happy employees are 12% more productive</a> (Fast Company)</li><li><a href="http://lunar.lostgarden.com/Rules%20of%20Productivity.pdf">The rules of productivity</a> (Lost Garden)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=835af4305bad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hire People Who Buy Into What You’re Doing]]></title>
            <link>https://medium.com/@shinytoyrobots/hire-people-who-buy-into-what-youre-doing-870fa8ae9369?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/870fa8ae9369</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Fri, 22 Sep 2017 21:36:04 GMT</pubDate>
            <atom:updated>2018-01-26T18:42:17.694Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BYP6zaqMEllyuMSoZp0wZQ.jpeg" /></figure><p>Five years ago I worked for a startup in Manhattan called <a href="http://get.viggle.com/">Viggle</a>. Viggle was a mobile app that was a rewards program for watching television.</p><p>Viggle’s business model was reliant on a user base that was passionate about TV. The whole app focused on engaging users with different shows and broadcasts.</p><p>I watch a lot of TV. I enjoy great shows. And working on a product related to something I like was a big draw. So it surprised me as a learned how many engineers who worked on Viggle didn’t own a TV. Not only didn’t own a TV, but many were almost proud of not owning a TV (in that New York hipster way).</p><p>It seemed strange to me how people could work on something when they had no real interest in the product. If you don’t watch television, how can you empathize with the users of a product for people who love television?</p><p>Viggle was also the first time I’ve been a hiring manager. I’ve hired a lot of people and built some great development teams since then. Most hiring processes make a big deal about skills fit and culture fit. But I think they miss an important third pillar of the hiring process; mission fit.</p><p>The first two of these pillars are simple.</p><p><strong>Skills fit</strong> — does the person you’re interviewing have the right skills for the job?</p><p><strong>Culture fit</strong> — does the person you’re interviewing seem like they’ll fit in well with the rest of the team? Will they be a good match for the office culture as a whole? (there’s a whole other article to write about the emphasis on culture fit and hiring diversity)</p><p>And mission fit is also simple, even though it’s more often overlooked.</p><p><strong>Mission fit </strong>— is the person you’re interviewing interested in what you’re making? Do they have a passion for your product or service, or some aspect of it?</p><p>It surprises me how often mission fit is overlooked.</p><p>Maybe it’s more important to me. Technical or management challenges are interesting. An engaging office environment is cool. But unless I care about the product or service itself, I’ll get bored. I’ve been told I get bored easily! I want to work on something I have some passion for.</p><p>When I first moved to Austin I worked for six months for a company called <a href="https://www.keyingredient.com/">Key Ingredient</a>. It has a website and mobile app built around cooking and recipes. I love cooking, so it seemed like a good mission fit. It was a product related to something I cared about.</p><p>But when I joined I discovered I wouldn’t be working on the main product at all. I’d be working on something called “My Family Vault.” A product based on storing and sharing digital “family assets”. Photos, legal documents, etc.</p><p>It’s not that it was a bad product idea. Amazon launched their own “<a href="https://www.amazon.com/Prime-Photos-Family-Vault/dp/B01MS4N6D3">Prime Family Vault</a>” service last year. But I wasn’t very interested in it. I don’t take lots of photographs. I don’t have a large family. I wasn’t the target audience. I had no passion for it.</p><p>Now, Key Ingredient had a lot of other problems. I didn’t stay for very long. But if I’d had a passion for the product they were building then I might have stayed longer. I might have been more productive. I’d have been more bought into the work I was doing. I was the right technical fit for the job. I was an OK culture fit for the people I worked with. But I didn’t fit the mission.</p><p>You don’t have to love everything about what you work on. But I don’t think the satisfaction of solving technical problems is enough in the long term. There needs to be something about the product that you care about.</p><p>I don’t have an abiding passion for Enterprise Cloud solutions. But I do care about making developers’ lives easier. So I care about the work that’s done on <a href="https://www.ibm.com/cloud-computing/bluemix/">IBM’s Cloud Platform</a>.</p><p>Mission fit is pretty simple. Do you care about the end product in some deeper way than having solved a technical problem. Is it more than an intellectual exercise? Mission fit creates a greater sense of ownership. It instils a greater passion for excellence. For me, that’s a vital factor when hiring new talent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=870fa8ae9369" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Principles versus Reality]]></title>
            <link>https://medium.com/@shinytoyrobots/agile-principles-versus-reality-f2e3ffcba58?source=rss-705013235ecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2e3ffcba58</guid>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Robin Cannon]]></dc:creator>
            <pubDate>Fri, 22 Sep 2017 04:37:41 GMT</pubDate>
            <atom:updated>2017-09-22T04:49:46.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*efPf_0xduIEbW2cgpxPerA.png" /></figure><p>Everywhere I’ve ever worked in the last few years has said they promote Agile workflow, or have one already. A common definition of Agile in reality is:</p><blockquote>“A process where teams work in arbitrary two-week periods (‘sprints’) toward a fixed scope and unrealistic deadline.”</blockquote><p>How do the <a href="https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/">12 Principles of Agile</a> manifest in many work environments? Even ones that say they’re Agile? Sometimes (often?) in some or all of these ways. Understanding this is an important first step to improving it.</p><p><strong>1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.</strong></p><p>The highest priority is to deliver something, valuable or otherwise, that we can sell.</p><p><strong>2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.</strong></p><p>Changes aren’t to the customer’s competitive advantage, but due to other demands. The lack of true Agile process means change isn’t for the customer’s competitive advantage.</p><p><strong>3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</strong></p><p>Rely on large deployments that kind of work with frequent fixes.</p><p><strong>4. Business people and developers must work together daily throughout the project.</strong></p><p>Business people will dictate to developers regularly throughout the project.</p><p><strong>5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.</strong></p><p>Build projects around motivated individuals. Ask too much, and fail to give them support they need. Don’t trust them to get the job done.</p><p><strong>6. The most efficient and effective method of conveying information to and within a development team is a face-to-face conversation.</strong></p><p>One of the principles that is most often adhered to.</p><p><strong>7. Working software is the primary measure of progress.</strong></p><p>Satisfying a date is the primary measure of progress.</p><p><strong>8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.</strong></p><p>Create an environment that forces regular “crunch” times. See point 7.</p><p><strong>9. Continuous attention to technical excellence and good design enhances agility.</strong></p><p>Don’t allow this. See point 7.</p><p><strong>10. Simplicity — the art of maximizing the amount of work not done — is essential.</strong></p><p>Create a large scope of work that isn’t simple, or containable. “Avoid” past failures in incremental development by adding everything and the kitchen sink from the start.</p><p><strong>11. The best architectures, requirements and designs emerge from self organizing teams.</strong></p><p>Don’t let teams self organize. Dictate architectures, requirements and designs.</p><p><strong>12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.</strong></p><p>Disempower teams so they find this difficult.</p><p>Process change is difficult. It’s even more difficult if it’s claimed that the process has already changed when it hasn’t. I’ve met few leaders or organizations that don’t pay lip service to Agile. But few leaders and organizations that trust, or are allowed to trust, the process.</p><p>Whether in small organizations or large, external pressures push back against Agile process. False predictability is often preferred to the perceived ambiguity of Agile. But Agile is more predictable in the long term.</p><p>I’ve had success in gaining benefits from Agile transformation. I’ve also had failure. It’s not organizational size. IBM has trusted me to push for change. Some of the smallest companies I’ve worked for have been the most resistant.</p><p>I’ve learned I’m more successful when I temper the ideal of Agile with the reality of circumstance. It helps to admit that we’re not Agile, and that we might never be. Then we can start to learn lessons from Agile methods which help us.</p><p>Agile is a philosophy, a way of thinking. It’s sometimes much harder to change the way people think, than to change some of the things they do. That can be a more productive first step.</p><p>I call this “How to be Agile-ish”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2e3ffcba58" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>