<?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 Bill Morein on Medium]]></title>
        <description><![CDATA[Stories by Bill Morein on Medium]]></description>
        <link>https://medium.com/@wmorein?source=rss-359b43780e9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QND0GZidvXyv9qSbUIBC_g.jpeg</url>
            <title>Stories by Bill Morein on Medium</title>
            <link>https://medium.com/@wmorein?source=rss-359b43780e9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:46:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wmorein/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[Management for Humans]]></title>
            <link>https://medium.com/@wmorein/management-for-humans-6e0ce5b12cfc?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e0ce5b12cfc</guid>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[manager]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Thu, 27 Feb 2020 22:26:01 GMT</pubDate>
            <atom:updated>2020-02-27T22:26:01.996Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Photo by Dan Roizer on Unsplash" src="https://cdn-images-1.medium.com/max/1024/1*Ufz6vHn-2xs-Owpxus6aAA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@danny159?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dan Roizer</a> on <a href="https://unsplash.com/s/photos/river?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Before you’re first promoted into management, you don’t tend to hear about the crying. People give you tactical suggestions, they tell you about books to read, and give you a lot of good and bad advice about how to get things done. But the first time you have someone in your office who is dealing with the end of a personal relationship at the at the same time a work project is going off the rails, you really get a broader view of the job. How do you make sure that they’re okay? How do you make sure that they can stay motivated? How do you help them get back to a place where they can continue to grow and improve?</p><p>Even when things are going well, those questions still matter. The human part of the work is essential. As someone’s manager you might spend nearly as much time with them as they spend with their immediate family. They’re probably seeking fulfillment in their work, and as a manager you play a significant role in whether they find it. And, if they don’t find it they are likely to quit or become less effective over time.</p><p>Being a manager is a role that has outsized impact on both companies and individuals. When you manage you know that it’s very easy to go home every day feeling like you’ve let your team down. Every manager feels that way, at least sometimes.</p><p>I’ve spent over ten years managing teams. In companies small and large. In software companies that ship continuously and in software and hardware companies that build complex products that take two years to deliver. In teams going through hyper-growth and teams in the middle of painful layoffs. In functional and divisional organization structures. In teams full of eager recent college graduates and teams full of experienced industry veterans. In vision driven companies and in metrics driven companies. In bottoms-up companies and top-down companies. Companies with rigid performance management systems and companies that wing it. Companies using granular OKRs and companies using informal goals.</p><p>So much of what managers need to be effective depends on all of these variables; it’s enough to make a person despair about whether there are any general approaches to follow.</p><p>Two early managers helped me see the parts of managment that are immutable — and that each individual manager can do regardless of the environment. By thinking of people management independently (related to but distinct from executive management and project management, which are much more company-dependent), managers can make sure that they are truly supporting their teams.</p><p>The conceptual framework that has been most helpful to me originally came from <a href="https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884"><em>High Output Management</em></a><em>.</em> It starts with the idea that in people management, you have only two ways to make your team better: increasing their motivation and increasing their capabilities. As a manager you have a huge amount of direct influence on these two dimensions — to the point that you should feel wholly accountable for each of them.</p><p>For motivation, you should be asking questions like: Am I touching base with my team enough? Am I striking the right tone? Am I responsive enough to make them feel I care?</p><p>For capability, you should be asking yourself questions like: Am I giving them specific high quality feedback to help them get better? Is that feedback coming frequently enough to be useful and non-threatening?</p><p>Over the years I cobbled together a series of macros, email filters, and simple processes that helped me every day as a people manager. Tools that let me go home knowing I hadn’t left a message from a team member sitting unacknowledged in my overwhelmed inbox. Prompts that ensured that I was giving deep feedback on people’s real work, rather than on status reports or glimpses in a meeting.</p><p>That isn’t to say I’ve been perfect. More than once I’ve sent off a quick note that was unduly harsh or given someone feedback that was unnecessarily vague.</p><p>But having even rudimentary tools has been incredibly helpful, and I’ve long felt that having a real product focused specifically on people management would make a meaningful difference in how effective and happy people are at work.</p><p>With the rise of remote teams and squads the challenges that managers face are greater than ever. Your team might ask you a question in Slack, in Email, in Google Docs, or anyplace else where collaborative work gets done. How do you make sure that you are connected and responsive?</p><p>We started Riverin to deliver the first real tool for people managers. We integrate with all the places where work gets done so you never let your team down.</p><p>We’re in private beta now and starting to share the product with more managers. You can sign up for the waitlist <a href="https://riverin.typeform.com/to/ztWUKj">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e0ce5b12cfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Canonical Startup Org Structure]]></title>
            <link>https://medium.com/@wmorein/the-canonical-startup-org-structure-4e320d462864?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e320d462864</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hr]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Thu, 18 Oct 2018 14:58:44 GMT</pubDate>
            <atom:updated>2019-07-14T20:46:30.230Z</atom:updated>
            <content:encoded><![CDATA[<p>When startups are just getting started, no organization is necessary for the most part. The team is so small and everyone is so connected. But, as they grow the question of how to organize quickly becomes important. Once that happens, <strong>there is a right way for almost all startups to organize: a functional organization with cross-functional teams focused on particular areas.</strong> This doesn’t mean that absolutely every startup needs to be organized this way but it should be the starting point and organizations should have good reasons for going with a different approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z1dhtUTH1SWKgisewLNgeQ.png" /></figure><p><a href="https://a16z.com/2010/08/02/taking-the-mystery-out-of-scaling-a-company/">As Ben Horowitz says</a>,“the first rule of organizational design is that all organizational designs are bad.” So by no means is this a perfect structure that solves all problems. No matter what approach you choose as you structure your company you are inherently optimizing on some dimension. The other dimensions will suffer and you must consciously take steps to mitigate that effect. The structure suggested here makes a choice appropriate for a single-product company and provides good mitigations for the limitations of that choice.</p><h4>What’s the Problem?</h4><p>The right way to design an organization is to try to figure out what you are trying to accomplish and then build an organization around those goals. Although there are many different goals for many different kinds of startups, there are a few that are central to think about for organizational design in startups, particularly once they have acheived some level of product/market fit.</p><p><strong>Ship or improve a single product. </strong>Startups generally have a single product (or a very tightly aligned set of products with a single go-to-market approach) stemming from a clear vision that they are delivering to customers. There needs to be a level of coherence in the product in terms of design, architecture, and go-to-market.</p><p><strong>Ship and iterate quickly. </strong>Startups thrive on speed. Any org structure needs to support extremely rapid iteration, which means clarity, great decision making, and autonomy for people working on a problem to let them deliver quickly. There are many different and difficult problems that need to be solved within a startup and getting groups of people working on them effectively is essential. Further, because startups don’t have the degree of specialization that a larger company does, people need to step up and fill roles to make sure that the right things happen.</p><p><strong>Develop and build the team. </strong>As startups scale they need to retain and grow their people (both into managers and as individual contributors). A lot of this growth happens through people tackling interesting problems, but effective coaching and management play an essential part. In particular gaining mastery within their specific discipline is essential.</p><h4>The Answer: Functional Organization</h4><p>Two of the above goals (single product, developing team) argue more strongly for a functional organization while one (shipping quickly) argues a bit more for an organization built around the problems being solved. But, the additional issue that tips the balance towards having a functional organization is the fact that the problems that the team faces change quickly within a startup. If you try to organize formally around the problems chances are you’ll be re-organizing all the time, which is incredibly disruptive.</p><p>So, when you draw the org chart for your startup it should have leaders for each individual for each discipline and individual contributors working for those leaders. This means that designers work for designers, engineers work for engineers, marketers work for marketers, and data scientists work for data scientists. This is incredibly useful for evaluating performance, providing feedback, and reducing technical debt (and similar company cruft) over time.</p><p>Along with satisfying the core goals above, there are a few other key advantages that this model provides:</p><p><strong>Executive team makeup.</strong> By structuring the organization in this way, the executive team is straightforward. It should have the manager from each discipline on it, which leads to a very balanced executive team with all of the elements that are critical to the company represented.</p><p><strong>Hiring. </strong>Finding, attracting, interviewing, and closing candidates is essential and is greatly simplified by having people who know how to recruit in their field.</p><p>Depending on the nature and size of the company, there may be different ways of breaking down disciplines. For example, marketing teams include PR specialists and highly quantitative online ad specialists. There can also be “one-off” groups that need to find a home. As with everything in a startup there is a significant degree of flexibility that is needed to make this work, but no more so than any other model.</p><h4>Mitigating the Shortcomings: Strong Cross-functional Teams</h4><p>Having set up your organization functionally, you can now generally ignore that structure and should run most of your product efforts using cross-functional teams slicing across your org chart. People will naturally bias towards their function and manager, so the company rhythm should orient as much as possible around the cross-functional teams (often referred to as squads, pods, or cells) that are solving key problems of the company. So, for example, this means that squads should be the ones demoing progress at every company all-hands and celebrating success as features ship.</p><p>Squads focused on product improvements usually consist of 3-10 people for some finite period of time. The squads get everyone needed to make the right changes to solve a problem together on a full-time (or close to full-time) basis. They also need to have a clear definition of what they are trying to accomplish. But, once they have that definition they should be fundamentally autonomous and the individuals on the team should be empowered as much as possible to make decisions and progress. Squads that have the core cross-discipline team members together can move quickly and accurately with minimal dependencies and context switching.</p><p>This doesn’t mean that there is no oversight — designers will still show work related to the problem at the design team’s crits and engineers will still work with the rest of the engineering team to ensure that the architecture is right and the code is properly reviewed. The natural pull of the org chart and reporting responsibilities will ensure that the teams work within the context of the larger product and vision. But in the end the team is given a lot of latitude to get things done.</p><p>This squad model maps most cleanly to the part of the organization delivering product—clearly it makes less sense for groups like customer support and sales. Those organizations are served well by the main functional organization in their day to day work, and they also can and should be pulled in to squads as necessary and useful. Individuals in those functions will rarely be completely dedicated to a particular squad but often have a lot to contribute to a project.</p><h4>Considerations and Caveats</h4><p>Even though this is very likely the best structure for your company, it is worthwhile to understand the set of tradeoffs you are making as you think about structure. Two of the best posts on this topic are from <a href="https://medium.learningbyshipping.com/functional-versus-unit-organizations-6b82bfbaa57">Steven Sinofsky</a> and <a href="https://a16z.com/2010/08/02/taking-the-mystery-out-of-scaling-a-company/">Ben Horowitz</a>. Each is well worth reading.</p><p>One major caveat, as noted above, is that this model works best for product-centric operations. Operations-heavy startups may need to operate differently in some ways (e.g. if they are very location-specific the idea of general managers for regions might be important) but the basic principles apply.</p><p><em>While I’ve got you…</em></p><p><em>Interested in becoming a better manager? We’re working on a tool to help managers build and maintain better relationships with their teams and would love to talk with you and get your feedback. If you are interested (or just interested in signing up to try the product when it is ready) please fill out this form: </em><a href="https://riverin.typeform.com/to/ztWUKj"><em>https://riverin.typeform.com/to/ztWUKj</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e320d462864" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reading for Renaissance Software Teams]]></title>
            <link>https://medium.com/@wmorein/reading-for-renaissance-software-teams-70de0968562e?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/70de0968562e</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Wed, 25 Apr 2018 00:03:33 GMT</pubDate>
            <atom:updated>2018-04-25T00:03:33.792Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Renaissance man and woman have not been viable for the past 300–400 years. The world has simply become too complex. On the other hand, the notion of renaissance team is entirely viable: a social network of specialists from different disciplines working as a team with a common language. But while viable, the systemic biases of language, funding and institutional barriers make this type of team the exception, rather than the norm. — Bill Buxton</blockquote><p>Building modern software of any significant scope is a significant undertaking and requires a real team. The most creative and effective software and service teams I’ve been a part of have been composed of sets of individuals who each have incredibly deep expertise in a particular specialty. Along with their own area of expertise, however, members of these teams have enough knowledge of the other specialties to be conversant so that effective collaboration can happen. Teams of experts who don’t have empathy for the other disciplines and requirements are teams that don’t make good tradeoffs and can’t effectively push the envelope. They produce bland products.</p><p>People talk about “designers who code” but that is just a small part of the picture. Further, people don’t need to actually be able to do the jobs of the rest of the team to effectively empathize and get the real benefits of the team’s breadth. Success is about the engineer who understands the importance of and animation and is willing to come up with the creative solution to make it fast enough to ship. The designer who adapts the interaction model to ensure that it is accessible to those with motor skill limitations. The PM who ensures that the support team gets the information they need to solve problems. The tester who understands the value of the research that went into the initial design.</p><p>Everyone who wants to be a part of an exceptional team should figure out how to gain the knowledge to participate in deep discussions around what the team should be building. This kind of back and forth is what makes product development fun and results in the very best products.</p><p>A lot of this knowledge is gained by experience, but there is so much great content out there that can help you get started. Here is a set of links that I’ve either personally found useful for understanding other disciplines and/or have been recommended to me by experts in those domains.</p><p><strong>General Design</strong>: <a href="https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654">The Design of Everyday Things</a>, Don Norman</p><p><strong>Interaction Design:</strong> <a href="https://www.amazon.com/About-Face-Essentials-Interaction-Design/dp/1118766571/ref=sr_1_3?s=books&amp;ie=UTF8&amp;qid=1524607260&amp;sr=1-3&amp;keywords=about+face">About Face</a>, Alan Cooper</p><p><strong>Web/Interaction Design:</strong> <a href="https://www.amazon.com/Dont-Make-Think-Revisited-Usability/dp/0321965515/ref=pd_lpo_sbs_14_t_0?_encoding=UTF8&amp;psc=1&amp;refRID=71R94A5RH41C9ZZNC0SF">Don’t Make Me Think</a>, Steve Krug</p><p><strong>Data Visualization: </strong><a href="https://www.amazon.com/Visual-Display-Quantitative-Information/dp/1930824130">The Visual Display of Quantitative Information</a>, Edward Tufte</p><p><strong>User Research (Qualitative): </strong><a href="http://amzn.to/1TAoGNf">Interviewing Users</a>, Steve Portigal</p><p><strong>User Research (Quantitative): </strong><a href="http://amzn.to/1TAF2Wd">Designing with Data</a><strong>, </strong>Rochelle King, Elizabeth Churchill (Bonus article: <a href="https://medium.com/@InVisionApp/a-b-and-see-a-beginner-s-guide-to-a-b-testing-a16406f1a239#.78tyxmbrv">A/B and see</a>)</p><p><strong>Visual Design: </strong><a href="http://amzn.to/1RbwggS">Meggs’ History of Graphic Design</a>, Phillip Meggs, Austin Purvis</p><p><strong>Brand: </strong><a href="http://amzn.to/1RE16sU">Designing Brand Identity</a>, Alina Wheeler</p><p><strong>Typography</strong>: <a href="http://amzn.to/1RbxYPn">Thinking With Type</a>, Ellen Lupton</p><p><strong>Legacy and Change:</strong> <a href="http://blog.learningbyshipping.com/2016/02/08/why-the-heck-cant-we-change-our-product/">Why the Heck Can’t We Change Our Product</a> (article)</p><p><strong>Localization and Internationalization: </strong><a href="https://www.smashingmagazine.com/2012/07/12-commandments-software-localization/">12 Commandments of Software Localization</a> (article)</p><p><strong>Testing: </strong><a href="http://amzn.to/24V0OHX">Testing Computer Software</a>, Cem Kaner, Jack Falk, Hung Nguyen</p><p><strong>Pre-release Programs: </strong><a href="http://www.slideshare.net/centercode/sucessful-beta-testing-2034042">Successful Beta Testing</a> (slides)</p><p><strong>Statistics</strong>: <a href="http://amzn.to/1RV0ZvA">Statistics in Plain English</a>, Timothy Urdan</p><p><strong>Analytics and Data Science: </strong><a href="http://amzn.to/24V9vSo">Data Smart</a>, John Foreman</p><p><strong>Service Operations:</strong> <a href="http://amzn.to/1McmIe6">Web Operations</a>, John Allspaw, Jesse Robbins</p><p><strong>Service Deployment: </strong><a href="https://zachholman.com/posts/deploying-software">How to Deploy Software</a> (article)</p><p><strong>Marketing</strong>: <a href="http://www.amazon.com/Crossing-Chasm-3rd-Edition-Disruptive/dp/0062292986/ref=pd_sim_14_9?ie=UTF8&amp;dpID=51sUsyutXjL&amp;dpSrc=sims&amp;preST=_AC_UL160_SR106%2C160_&amp;refRID=1ENQJ137JHD32M56M6GY">Crossing the Chasm</a>, Geoffrey Moore</p><p><strong>Growth</strong>: <a href="http://amzn.to/1TB5tLd">Viral Loop</a>, Adam Penenberg</p><p><strong>Building a Business</strong>: <a href="http://a16z.com/2015/01/09/pmarca-blog-ebook/">Pmarca Blog Archives</a></p><p><strong>Teams: </strong><a href="http://amzn.to/1XiR3O2">Peopleware</a>. Tom DeMarco, Tim Lister</p><p><strong>Managing People</strong>: <a href="http://amzn.to/1pdliei">High Output Management</a>, Andy Grove</p><p><strong>Writing</strong>: <a href="http://amzn.to/1QS41yh">On Writing Well</a>, William Zinsser</p><p><strong>Basic Programming</strong>: <a href="http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/">What is Code</a></p><p><strong>Software Engineering</strong>: <a href="http://amzn.to/1RbXW5u">Mythical Man-Month</a>, Frederick Brooks</p><p><strong>Quality Code: </strong><a href="http://amzn.to/1XiQYde">The Pragmatic Programmer</a>, Andrew Hunt, David Thomas</p><p><strong>Performance:</strong> <a href="http://amzn.to/1RVlqc1">Software Performance and Scalability: A Quantitative Approach</a>, Henry Liu</p><p><strong>Artificial Intelligence:</strong> <a href="http://amzn.to/1RVlEjo">Artificial Intelligence: A Modern Approach</a>, Stuart Russell, Peter Norvig</p><p><strong>Networks:</strong> <a href="http://amzn.to/1UZ04Nt">Introduction to Networking: How the Internet Works</a>, Charles Severance</p><p><strong>Security and Privacy:</strong> <a href="http://amzn.to/1UZ1uYj">The Hacker Playbook: Practical Guide to Penetration Testing</a>, Peter Kim</p><p><strong>Community:</strong> <a href="https://www.amazon.com/Building-Successful-Online-Communities-Evidence-Based/dp/0262016575/ref=pd_sim_14_2?_encoding=UTF8&amp;pd_rd_i=0262016575&amp;pd_rd_r=20064B48GTGEWFQCAAAB&amp;pd_rd_w=lUcVB&amp;pd_rd_wg=iC468&amp;psc=1&amp;refRID=20064B48GTGEWFQCAAAB">Building Successful Online Communities: Evidence-Based Social Design</a></p><p>I’d love to hear about any suggestions for better alternatives for any of the content in these categories. Also, there are a few areas where I haven’t found great books (support, design prototyping) so if anyone has any suggestions I’d love to hear about them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70de0968562e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we Slack at FiftyThree]]></title>
            <link>https://medium.com/@wmorein/how-we-slack-at-fiftythree-5f6f8c4dcb1b?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f6f8c4dcb1b</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Thu, 02 Jul 2015 12:34:19 GMT</pubDate>
            <atom:updated>2019-06-18T20:48:51.916Z</atom:updated>
            <content:encoded><![CDATA[<p>As a growing company with over 50 people, the days of being able to hear just about everything going on just by sitting around our CEO’s apartment are long gone. When we added Slack to our communications mix, <a href="https://twitter.com/julianwa">@julianwa</a> and I spent a little time up front trying to come up with a set of pretty simple channel conventions as a way to bring a little clarity into our Slack world (we had been using Hipchat and it was pretty disorganized). Before doing this we tried to ask around about how others do this, but we didn’t find much. Since what we have seems to be working reasonably well for us so far, we figured it would be worth sharing to help others getting starting or trying to get more organized.</p><p>When we first set up Slack, we set up our channels using these conventions and then put together a Quip doc outlining them so that as new channels come online they fit the basic model. How and when we use Quip vs. Slack is a subject for a whole different post.</p><p>Below is the basic doc that we use internally, redacted a bit to hide some of the future projects we are working on. The examples obviously aren’t comprehensive but are intended to give people an idea of the types of channels that fall under each category.</p><h3>team-</h3><p>Teams are effectively the various groups on our org chart, although as a startup we still have a decent amount of overlap in roles so people sit in multiple teams. <strong>Examples:</strong></p><ul><li>team-app</li><li>team-web</li><li>team-web-backend</li><li>team-web-ui</li><li>team-product</li><li>team-design</li><li>team-operations</li><li>team-marketing</li><li>team-sales</li></ul><p><strong>Who should join:</strong> Team channels are mostly for the people in that specific organization. In cases where there are tight relationships others can and should join as well.</p><h3>product-</h3><p>Product- is for our general discussion on the progress of products in the market, how the product is being received, feature ideas, etc. <strong>Examples</strong>:</p><ul><li>product-paper</li><li>product-pencil</li><li>product-mix</li></ul><p><strong>Who should join:</strong> Anyone interested.</p><h3>ft-</h3><p>Feature teams are specific groups of people working on a particular feature. Features often have a specific end date as they get completed, and then the channel can get archived. The scale of feature teams can range from small to very large. Examples:</p><ul><li>ft-activitycenter</li><li>ft-thinkkit</li><li>ft-backup</li></ul><p><strong>Who should join:</strong> Generally these are more tactical so they are most appropriate for the team working directly on the feature.</p><h3>x-</h3><p>All general and social groups. Examples:</p><ul><li>x-random</li><li>x-general-nyc</li><li>x-general-seattle</li><li>x-jams</li><li>x-company-roadmap</li><li>x-app-notifications (commits and automated build completions via integrations)</li><li>x-children (cute photos of fiftythree kids)</li><li>x-moving-pictures</li><li>x-coffee-nyc</li></ul><p><strong>Who should join: </strong>Anyone interested.<br><strong>Why the x-? </strong>Slack displays channels alphabetically. This keeps general-purpose, non-core channels from jumbling up all the others.</p><h3>53-</h3><p>Any channel that includes external participants (see <a href="https://slack.zendesk.com/hc/en-us/articles/202518103-Restricted-account-and-single-channel-guest-FAQ">Restricted-account-and-single-channel-guest-FAQ</a>). Examples:</p><ul><li>53-firmware</li><li>53-remixer-discussions</li></ul><p><strong>Who should join: </strong>Only those who need to be in contact with the external people or communities in a given channel. Please be careful with these channels as they represent communication with partners, contractors, and customers.<br><strong>Why the 53-? </strong>Since these are visible to people outside of FiftyThree we want a clear qualifier that this channel allows communication with our company.<br><strong>Who can create these channels?</strong> Only Slack administrators. Generally these channels are temporary meeting rooms setup to collaborate for a fixed period of time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f6f8c4dcb1b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Ode to the Design-focused Engineer]]></title>
            <link>https://medium.com/@wmorein/an-ode-to-the-design-focused-engineer-f6d9157503a4?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6d9157503a4</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Tue, 30 Jun 2015 03:08:18 GMT</pubDate>
            <atom:updated>2015-06-30T03:08:18.922Z</atom:updated>
            <content:encoded><![CDATA[<p>As the tech industry has made its recent turn towards embracing design, the designer has (rightly) been celebrated and embraced. But, as we enjoy our newfound delightful yet meaningful animations and properly spaced and kerned text, let’s make sure to appreciate everyone who is responsible.</p><p>Mostly, I want to honor the design-focused engineer. The person who has to suffer the unholy hack in the codebase that sits where a purely logical algorithm would have let them sleep soundly at night. The person who could have built a functional feature in five minutes using a native control but instead spent two weeks building an entirely new transition model that really lets the user understand where their content is going. The person who took the tuning tweak late on the night before pushing to the App Store that makes the experience 3% better.</p><p>That is a pretty great person. We should all be appreciative.</p><p>If you are looking to personally thank one of them, I have it on good authority that high quality Belgian beer is rarely declined. If you are one of them, let me know. We appreciate them and we’re always hiring.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6d9157503a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creativity at Work]]></title>
            <link>https://medium.com/life-tips/creativity-at-work-a4f47caebb2?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4f47caebb2</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Tue, 12 May 2015 17:05:05 GMT</pubDate>
            <atom:updated>2015-05-19T16:10:22.157Z</atom:updated>
            <content:encoded><![CDATA[<p>When you say the word creativity, people’s minds usually go first to artistic endeavours. But it turns out that when you look at what makes companies and other organizations special, the ability to create something new is what matters.</p><p>Creativity in the work world (as everywhere else) is about people. New ideas and the evolution of those ideas into something real is a fundamentally human endeavour. It requires doing things like creating connections between ostensibly unrelated domains and jumping from a locally optimum method to a completely different way of approaching the problem. Those ideas are then relentlessly iterated on until they become tangible. These activities are all part of the process of bringing something new into existence. New products and processes mean differentiation and that means better performance as a company.</p><p>Inside a company, creativity that has an impact isn’t just about people who have “creative” backgrounds. In other words, not just designers, architects, and copywriters. Senior managers, business analysts, sales leaders, and product teams all need to generate, explain, and sell ideas to make real progress happen within a company. Making companies more creative means making all of these people more effective and creative.</p><p>Although most companies today hire for creativity and leadership teams spend a lot of time communicating to their organizations about the urgency of creation, investment in tools for creativity at work are usually limited to whiteboards and Post-it notes. While those analog tools are pretty powerful in their own way, it seems amazing that all of the digital tools are focused on <em>productivity</em> and <em>compliance,</em> rather than <em>creativity</em>. Companies invest massive amounts of money in CRM, ERP, and HR management services, but basically nothing in making their people more effective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Tij8ub3e6HQhX2Chjrnqnw.png" /><figcaption>The Squiggle</figcaption></figure><p>The very nature of creativity and the historical limitations of technology have made it hard to build great tools to augment people’s abilities in this area. A lot of these limitations have been more about the platforms:</p><ul><li><em>Creativity demands fluidity and adaptation</em> — input devices like mice and keyboards are designed instead for precision</li><li><em>Creation happens anywhere and anytime</em> — PCs and laptops are not always there when they are needed</li><li><em>Creativity is visual</em> — the tools for generating visual explanations are clunky and slow</li></ul><p>The advent of mobile devices like iPads and smartphones has the potential to ease those constraints through richer multi-touch input, and by being much more intensely personal and always available. The platform is ready for some incredible tools in this area. Now we as developers just have to deliver experiences that match that potential.</p><p><a href="http://fiftythree.com/">FiftyThree</a> is focused on helping people be as creative as they can be, regardless of field. Within FiftyThree we always talk about the “squiggle”, which represents the overall creative process — going from the nascent and tangled stages of ideation, to a focused and concrete idea ready to be shared with the world. With the introduction of <a href="http://fiftythree.com/think">Think Kit</a>, we are focusing on the business and educational worlds, and the specific creative needs within them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4f47caebb2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/life-tips/creativity-at-work-a4f47caebb2">Creativity at Work</a> was originally published in <a href="https://medium.com/life-tips">Be Yourself</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The First Principle in Software Projects]]></title>
            <link>https://medium.com/@wmorein/the-first-principle-in-software-projects-ae1003c8e9ce?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae1003c8e9ce</guid>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Sun, 12 Apr 2015 04:01:33 GMT</pubDate>
            <atom:updated>2015-04-12T04:01:33.339Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When you build software (at least if you intend to ever ship it), at the core you are trading off </em><strong><em>time</em></strong><em>, </em><strong><em>people</em></strong><em>, </em><strong><em>features</em></strong><em>, and </em><strong><em>quality</em></strong><em>.</em></p><p>Add more time and you can usually ship a higher quality product. Lose a person and you have to cut features or ship later. Of course there is a lot of subtlety behind that — features can refer to both breadth and depth, people may be specialized, and so on. But, fundamentally making sure that you keep that principle in mind regardless of what you are building will only help you as go down the incredibly hard path of getting things right.</p><p>Most methodologies end up implicitly or explicitly addressing the core tradeoffs. Whether it is timeboxing sprints and releases to lock down the time dimension, setting a minimum viable feature set for shipping, or insisting on a particular quality bar through a test-first approach, even if you think you are simply following a particular methodology you are really making these kinds of tradeoffs behind the seems.</p><p>Just as <a href="http://www.joelonsoftware.com/articles/LeakyAbstractions.html">you can get into big trouble</a> if you write code at a high level of abstraction without understanding what is going on behind the covers, you can get into a lot of trouble following a methodology without knowing what levers it is pulling. So, regardless of what methodology or approach you use, keeping the main set of tradeoffs in mind is a really good idea.</p><p>There are a few basic patterns and mistakes you should recognize:</p><h4>Change one at a time</h4><p>When you are starting your career or working in a larger company, in most cases you have three of the dimensions fixed for you— a release date is set, you have a team you are working with, and there is an explicit or explicit company bar for quality. You just have to figure out which features you can fit into those constraints. Or, a rough product scope has been pre-determined and your job is to come up with a schedule given a particular team.</p><p>Solving for those single dimensions can be hard enough, but where I’ve seen teams struggle even more is when they are trying to figure out two or three at once. For instance, if a team has to figure out the scope of the product but also ask for a team to build the product, the discussions can rapidly get circular.</p><p>If you are on a team that feels like it is churning and not making progress towards the goal, I’ve always found it is worth asking whether you are dealing with too many moving parts in this dynamic. If you feel like you are, force yourself to constrain all but one, even if you have to do so artificially.</p><h4>The bigger the dimensions, the bigger the problems</h4><p>The recent trend has been towards trying to simplify the whole thing — if you stick completely to small teams and very short release cycles, it still makes sense to think about the tradeoffs, but it becomes a lot easier to keep everything in your head and the cost of screwing things up becomes smaller. The world of services in particular has really made this possible, and if it fits in with your business it is a great idea to take advantage of that.</p><p>I’m a strong believer, though, that there are a lot of businesses and projects that can’t work that way. Perhaps because having a meaningful product launch is important, perhaps because the technology is complex and deep, or perhaps because there are dependencies that constrain you. Those are real and valuable cases, so being able to manage at scale is still important. Just think about how you can simplify one or more aspects so you can manage the dimensions.</p><h4>What are your meaningless rituals?</h4><p>There are a lot of standard practices that you follow because of the implicit or explicit approach that you use. In the context of the dimensions, it is worth asking whether you really need to be doing them. For example, if the project scope and team size are immutable, exactly what return are you getting for the time you just spent on the highly detailed schedule and timeline? There may be a very clear answer (e.g. you need it to coordinate your go-to-market plan) but do you need it right now? Every bit of simplicity and lack of busywork pays big divideds in team happiness and productivity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae1003c8e9ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[General Rules Won’t Help]]></title>
            <link>https://medium.com/@wmorein/general-rules-won-t-help-22259d0fccd0?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/22259d0fccd0</guid>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Wed, 08 Apr 2015 03:15:59 GMT</pubDate>
            <atom:updated>2015-04-12T14:05:31.785Z</atom:updated>
            <content:encoded><![CDATA[<p>There are two different stories that I’ve been told as analogies for the right way to develop products. This note is about how, even though they seem to the in opposition and are often told that way, you have to keep both in mind when making decisions.</p><p>Both stories are about civil engineering projects, just because software people apparently like large scale projects for comparisons.</p><h4>The Ramps to Nowhere</h4><p>When the 520 bridge in Seattle was built, the builders carefully planned ahead by building ramps to a future highway. As the project was underway, community unease with the planned routes killed the bridges, and the unfinished ramps have <a href="http://www.seattlepi.com/local/article/520-ramps-to-nowhere-to-be-demolished-4221870.php">stood ever since as a warning</a> to engineers crossing the bridge from Seattle to software companies on the east side of the lake (they are also favored by students as a great launching pad to jump into the lake).</p><p>When someone tells you about the ramps, the message is that you shouldn’t over-architect for the future, since you don’t know what that future will actually look like when you hit the market.</p><h4>The Train to Idlewild</h4><p>The other story is about when <a href="http://www.amazon.com/The-Power-Broker-Robert-Moses/dp/0394720245">Robert Moses</a> was building the Van Wyck Expressway to Idlewild Airport (now JFK) it would have been very easy to build a train at the same time (or at least to leave aside the land for a future train). Moses nixed the idea — ultimately the Van Wyck ended up as one of the most congested roads anywhere and the elevated AirTrain had to be built many years later on pylons over the road.</p><p>When you hear about the train, the message is that if you just think carefully about the future, the right small to medium investments now can pay off hugely.</p><p>We make our biggest mistakes when we only consider one side of this and try to use a shortcut in making the decisions. The reality is that you sometimes have to be pragmatic and take on the debt but sometimes you really need to make the investment. Your job is to reason through the particular case — general rules won’t really help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22259d0fccd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design and differentiation in startups]]></title>
            <link>https://medium.com/@wmorein/design-and-differentiation-in-startups-af0e2cc62fcc?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/af0e2cc62fcc</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[vc]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Fri, 03 Apr 2015 15:45:30 GMT</pubDate>
            <atom:updated>2015-04-03T15:45:30.205Z</atom:updated>
            <content:encoded><![CDATA[<p>The last few years have seen a lot of <a href="http://www.kpcb.com/blog/design-in-tech-report-2015">presentations</a>, <a href="http://www.fastcodesign.com/1665795/silicon-valleys-new-secret-weapon-designers-who-found-startups">articles</a>, <a href="http://ireneau.com/2014/04/22/im-joining-khosla-ventures/">hires</a>, and <a href="http://designerfund.com/">entire funds</a> that speak to the increasing prominence of design in the startup world. But why — how does design specifically make an impact on the things that matter in the startup world?</p><p>If you are looking to create a venture backed business, it is pretty much understood that you need to be able to create some sort of sustainable competitive advantage to be successful over time. Call it a moat or a monopoly, but somehow you need to have a significant aspect of your business that your competitors can’t replicate.</p><p>In the earliest days of VC, that was usually a deep technical advantage protected either as a trade secret or via patents. Over time other routes have emerged (e.g. network effects, unique distribution channels, scale) and in many cases have come to take the dominant role for most software and services investments.</p><p>Design can play two main roles in getting a company to a sustainable advantage.</p><p>The first is as an <strong>accelerator for other differentiation channels </strong>(network effects and brand in particular). Products that are clearly well designed have a significant advantage in many of the places that kickstart distribution (App Store features, press coverage, word of mouth) and also lead to better long term usage patterns and better sustain the network effect. The design of a product is also a key part of the company’s brand, and that is becoming more important over time.</p><p>The second (and perhaps more speculative over the long term) is as an <strong>independent differentiator </strong>in the same way that deep technical advantages are — something that is just flat out hard for others to replicate. Since the design of a product is something that you can inspect (unlike say the internals of a very complex piece of software) it would initially seem to be replicable. But, the reality is that great, complete, design is very hard and copycat programs have struggled to reach the polish and clarity of the original even when the copying is pretty blatant.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af0e2cc62fcc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Becoming a Manager of Managers]]></title>
            <link>https://medium.com/@wmorein/becoming-a-manager-of-managers-b4ffb9a8dcab?source=rss-359b43780e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4ffb9a8dcab</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Bill Morein]]></dc:creator>
            <pubDate>Wed, 25 Mar 2015 09:18:42 GMT</pubDate>
            <atom:updated>2015-03-25T09:18:42.245Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or: Things I Screwed Up When I Made the Move</h4><p>Everyone first steps into management by leading a small team of 3–5 people. Making that transition is really hard and there are a <a href="http://www.quora.com/Management/What-are-common-mistakes-that-new-or-inexperienced-managers-make?share=1">plenty</a> of <a href="https://medium.com/on-startups/understanding-people-747a1c08ecf0">interesting</a> <a href="http://firstround.com/article/My-Management-Lessons-from-Three-Failed-Startups-Google-Apple-Dropbox-Twitter-and-Square">articles</a> out there about how to do it, but it is still very hard work.</p><p>I haven&#39;t seen much written about the even more difficult move from <em>manager</em> to becoming a <em>manager of managers</em>. Making that jump is very deceptive — for me everything changed in terms of how working relationships worked, but it took me a while to figure that out. I’ve seen many others struggle mightily with this problem, so it seems worth sharing places where I botched things pretty miserably when I made the switch.</p><p>First, though, there are a few basics that I don’t think that I messed up (at least not too badly), but are still really important to remember:</p><ol><li>You have to genuinely care — about your people, about your company, about what you are building. If you don’t your team will know and you will fail.</li><li>You have to have a clear and straightforward vision for what you want to create. If the team doesn’t have vision no amount of effectiveness in execution can save it.</li><li>You have to sent the tone in terms of culture and values and live them straightforwardly and obviously yourself. If you ask your team for something that they don’t see as matching your actions, it will be a problem.</li><li>It is important to have frequent 1:1s with everyone who works on your team.</li><li>If you don’t give frequent and clear positive and negative feedback your team won’t know where they stand and will likely struggle.</li></ol><p>Those are mostly carried over from the basics of being any kind of a manager and hopefully you are doing them. If not, figure those out first and don’t take on a bigger team before your do.</p><p>If you decide to take the leap, here are some things to think about:</p><h4><strong>Embarrassing over-communication</strong></h4><p>I think that I was always pretty decent at articulating a pretty clear vision and strategy, both in writing and in speaking. However, once I took on a big team I was continuously surprised by how frequently people didn’t receive the messages, and how many times things had to be repeated in order to be confident that they had sunk in. The key difference is that when you have a smaller team of direct reports, you deliver messages 1:1 to your team. When you have a much bigger team, that is impractical for most situations (even though you should be doing skip-level 1:1s). What that means is that messages are either delivered in a bigger meeting/email (where people don’t always give 100% attention no matter how compelling you are) or they travel through a manager. In either case the messages are diluted significantly.</p><p>To be effective you have to make sure that you have repeated things to the point where you feel almost dumb — preferably through multiple channels (team meetings, email, Slack, hallway conversations, etc). Some people will feel like they have heard things too many times but that is better than having people not aligned to the mission or goals. If you don’t feel embarrassed about how many times you’ve said something important, you haven’t said it frequently enough.</p><h4><strong>You will make mistakes</strong></h4><p>Effectively everyone who gets to a point where they lead a big team has been really successful — and for many people that means that they are not all that used to making mistakes (or at least not making mistakes that they can’t quickly fix). When you lead a big team, you <strong>will</strong> make many mistakes and accepting that is essential. You can’t beat yourself up about them too much or it will be paralyzing.</p><p>The hardest part about this at such a large scope is that some of the mistakes you make will really impact people’s lives. You have to acknowledge that, make sure that you respect it and them, but be able to move on (with some good lessons learned).</p><p>You should also be willing to admit your mistakes to the team. They will know anyway and you will get a lot more respect if you acknowledge them. Don’t dwell on them and relive them over and over, but let people know that you are aware and you won’t make the same mistake again (you’ll make different ones).</p><h4><strong>Delegate delegate delegate</strong></h4><p>If you’ve hired the right people, they <strong>want</strong> to step up. It is easy to try to take on too much yourself (you think that you will be best at it, your team doesn’t have the broader context, you don’t want to burden people). But ultimately you have have a great team and you need to make sure that you trust them. This is true even as a team lead, but totally non-negotiable as a manager of managers. You should always be thinking about how to take yourself off the critical path on everything. Weigh in frequently, make sure that you keep standards, but try to make sure that the team is very rarely blocked on your input or tasks.</p><p>The one note here is that you do have to make sure that you and your team are clear about when this delegation has happened and who the newly responsible person is (and how you expect to have input). Crisp communication on delegation will save much pain later for everyone.</p><p>A special case within this is that you have to be really careful about skipping over your directs and going straight to people on their team. It is inevitable and it can and should happen, but make sure you are thoughtful about why you do it, when you do it, and how you follow up with your direct so they aren’t blindsided and frustrated.</p><h4><strong>Let people make mistakes</strong></h4><p>A related idea is that you have to be willing to let people make mistakes themselves. There will be times when you see someone making what seems like a mistake to you, and you will have the very strong temptation to step in and fix it. While in some cases this is absolutely the right call, there are a lot of times that this makes the team feel disempowered and it prevents them from learning effectively. It also has the side effect of leading the team to feel like they need you to weigh in on everything, which isn’t practical and can lead to gridlock. Also never forget that the people doing the work often have data, domain expertise, or history that may mean that they are right and you are wrong.</p><h4><strong>Learn the power of your words and reactions</strong></h4><p>Even if you still think that you are a part of the team, there are some set of people who will see you as apart and give your opinions outsized importance. In other words, they see you as an “exec” rather than as a team member. If you don’t recognize and internalize that it can lead to lots of unintended consequences. At some point you’ll make an offhand comment you didn’t think much about and someone will completely change a plan based on the comment. Even things like body language in a meeting and degree of interest you show in a topic can make people feel demoralized, excited, or change their plans in unexpected ways. People will also use your feedback as a way to wage battles — “The VP said…” becomes a tool and that is unhealthy.</p><p>This doesn’t mean that you shouldn’t give feedback — that is a big part of your job. Just make sure that you are very cognizant of the outsized (and sometimes unexpected) impact that it has on the team. This only becomes larger the larger the team is. If someone doesn’t get to interact with you every day, that one bit of input you give them has a lot of effect on them even if it is just one of hundreds of comments you make in the course of a week. Jeff Weiner wrote <a href="https://www.linkedin.com/pulse/20140602024642-22330283-avoiding-the-unintended-consequences-of-casual-feedback">a good article on how he deals with this problem</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4ffb9a8dcab" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>