<?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[Growing OpenNest - Medium]]></title>
        <description><![CDATA[Stories about our organization growing itself. - Medium]]></description>
        <link>https://medium.com/growing-opennest?source=rss----117c888cfb7f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Growing OpenNest - Medium</title>
            <link>https://medium.com/growing-opennest?source=rss----117c888cfb7f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:52:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/growing-opennest" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Will It Blend?]]></title>
            <link>https://medium.com/growing-opennest/designing-communities-vs-designing-companies-342160afebe3?source=rss----117c888cfb7f---4</link>
            <guid isPermaLink="false">https://medium.com/p/342160afebe3</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[organizational-design]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Spencer Pitman]]></dc:creator>
            <pubDate>Wed, 03 Feb 2016 18:43:44 GMT</pubDate>
            <atom:updated>2016-02-10T02:39:46.418Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Community/Company Spectrum</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R76ZkG-mmc5nKCuv39WDQQ.jpeg" /></figure><h4><em>Part 1 in a Series Exploring Designs of Different Kinds of Organizations</em></h4><p>This morning, I was sitting in an airport bar having an airport breakfast doing some airport reading when my phone buzzed. It was my friend <a href="https://medium.com/u/8f3b79a92eb4">Carl Smith</a> and he had a simple question:</p><blockquote>“Do you think designing a community is the same as designing an organization?”</blockquote><p>My instant reaction was to try to frame community as a <em>sort</em> or organization, but I then I thought better of this pedantic trickery. I realized that what he really meant was, <em>“what do I need to pay attention to if I’m setting out to build a community vs. what I know from building companies?”</em> I think this is a really fantastic topic. In my consulting career I have helped produce both sorts of organizations. I think I have developed enough sensitivity to intuit the differences, but I have never set out to describe them. Over the next few weeks, I’m going to spend some time exploring different sorts of organizations, organizational designs, and my thoughts regarding them. This post explores some of the top level ideas that emerged when I thought about Carl’s question.</p><h4>On the Terms “<em>Community”</em> &amp; “<em>Company”</em></h4><p>In org design circles, it has become increasingly common to talk about building <em>companies as communities</em>, or to try to foster <em>community</em> within organizations. I’ve even <a href="https://medium.com/growing-opennest/building-communities-not-companies-part-1-e6532eb675b8#.uzlow1kvk">written about</a> this topic <a href="https://medium.com/growing-opennest/building-communities-not-companies-part-2-f1a0307ca431#.wo6dcynw6">myself</a>. However, for the purposes of this article, we’re going to make a distinction between <em>community</em> and <em>company</em>, wherein a community is an <strong>informal organization of people gathered around a common <em>theme(s)</em></strong> (intentionally vague: could be a set of ideas, interests, geography, problems, beliefs, etc.), and a company is a <strong>formal organization designed to offer a clear solution to market problem</strong>. You’ll notice that each of these terms are defined somewhat unconstrictively, so “community” could be an HOA or a Slack group, and “company” could be AMEX or a community nonprofit — they aren’t necessarily distinct. These definitions are not perfect, and aren’t exactly what I would use in <em>general</em> discussions on this topic, but they are suitable for the discussion we’ll have in this context.</p><h4><strong>Membership, Interrelationships, and Tooling</strong></h4><p>As I considered the differences that matter between designed communities and designed companies, one of the most basal distinctions is the what and how of membership. In a company, membership is relatively binary. Glossing over some in-between or exceptional cases like contract work and freelancing, you are either part of a company (in the US this means you’ll get an annual tax form from them) or you are not. Your relationship is transactional. You contribute, they pay. Communities are much more fluid. In some cases, one is part of a community by merit of simply being in a place (think of a neighborhood or communities of common experience). That is to say, it isn’t necessarily <em>joined</em>. They don’t always require active participation, and <strong>the relationship <em>between</em> community members is often more important than the relationship <em>to</em> the community organization itself.</strong></p><h4><em>So What Does This Mean As We Consider Design</em></h4><p>When we’re designing companies, we’re building and/or using pretty hard systems and are able to bet on consistency across platforms (theoretically). Things like IM tools, email, physical office spaces, intranets, budgeting, etc. tend to be bound together by merit of the imminence of the company’s organizational structure. When we think about communities, these things are less consistent between members. Some community members might be Facebook power users. Some of them might want to get on Slack. Some are intimidated by or incapable of using technology-oriented systems. Membership in a community doesn’t necessarily mean platform regularity or consistency.</p><p>When we began working on <a href="http://livewithstoke.net/">Stoke.</a>, we rapidly realized that the tools we were using to be more effective as org designers could actually be disenfranchising to the community we were desperate to support. Recognizing that we were designing a community vs. a company meant emphasizing the group actions we wanted to facilitate even over the tools by which we intended to facilitate them. The lesson? What we design must be responsive to the values and constraints of the community’s constituents, and must allow them to choose their own ways of organizing and the tools to supports them.</p><h4><em>Will it blend? Thinking about edge cases</em></h4><p>Given the distinctions pointed out here, I have to wonder about the increasingly common refrain of building communities out of our companies. Is this possible or realistic? Is there a blended state?</p><p>From what I have seen, I think that the blended state isn’t only possible, it is imminent. We’re starting to realize that, for a lot of industries, the notion of a compartmentalized “work-life balance” <a href="https://hbr.org/2014/10/what-successful-work-and-life-integration-looks-like">isn’t realistic</a> (the way that we often conceive of it), so it becomes ethically and functionally proper that we make work a place where people can find community. If we want to harness the dynamism of the human community to operate effectively in an <a href="http://www.organizeforcomplexity.com/book/">increasingly complex world</a> (and complexity is a good thing!), then we should be examining how to make workplaces and organizations spaces of wholeness. This means letting people show up fully, with the support to develop their greater purpose and the <a href="http://www.undercurrent.com/read/read/2014/06/responsive-bill-of-employee-rights">agency to pursue it every day</a>.</p><p>Thanks for reading! My name is spencer pitman. I <a href="http://opennest.io/">design organizations</a>, ski in the backcountry, ride my bike a lot, and <a href="https://www.instagram.com/alcesbull/">cook food</a> on snapchat every night @alcescow. If you want, follow me on <a href="https://twitter.com/AlcesBull">twitter</a> or just generally reach out and say hello. I like talking to people about almost anything.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=342160afebe3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growing-opennest/designing-communities-vs-designing-companies-342160afebe3">Will It Blend?</a> was originally published in <a href="https://medium.com/growing-opennest">Growing OpenNest</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ideas and Strategy at OpenNest]]></title>
            <link>https://medium.com/growing-opennest/ideas-and-strategy-at-opennest-15de34287f61?source=rss----117c888cfb7f---4</link>
            <guid isPermaLink="false">https://medium.com/p/15de34287f61</guid>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Spencer Pitman]]></dc:creator>
            <pubDate>Wed, 21 Oct 2015 20:53:03 GMT</pubDate>
            <atom:updated>2015-10-30T14:14:26.685Z</atom:updated>
            <content:encoded><![CDATA[<h4>Some Frameworks and Approaches</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t8n_xHnBTAuimdEOscDmyA.jpeg" /></figure><blockquote><em>note: This is an internal document that can be found in our </em><a href="https://drive.google.com/folderview?id=0B6V-uZEAqbfTfnBUWlVpLW5EN0tpcXZIYk1NVU4wRVdpMFN0bEoyR0NlVFpycjJlNnVsbmc&amp;usp=sharing"><em>Warpcore</em></a><em>, a growing collection of our internal tools turned public. It’s presented unvarnished, so some of the language is specific to its original format.</em></blockquote><p><strong>I N T R O D U C T I O N</strong></p><h4>DOCUMENT PURPOSE:</h4><p>I’m writing this document to support our organizational emphasis on novel, effective solutions. At <a href="http://opennest.io/">OpenNest</a>, we recognize that innovation is not an abstract value, but is <a href="http://www.oecd.org/site/innovationstrategy/45392693.pdf">measurable</a> and underpinned by intentional methodology. There are systems that give rise to increasingly creative and effective solutions, but we must understand the <em>how</em> and <em>why</em> of these systems if we are going to employ them (for ourselves and for our clients). Herein we’ll explore some of these systems, but it is most important to understand the <em>values</em> that guide them. When we understand what values we’re working toward, we can understand how to improve the systems themselves.</p><p><em>-spencer</em></p><h4>MAKING EDITS:</h4><p>Much like a wiki, this document should be community-supported and evolve as we become more advanced practitioners of the art and science of creativity. Feel free to make changes as you feel necessary. No need to ask for permission. Google Drive’s versioning system allows us to back out of any serious mistake, so charge onward.</p><p><strong>O N P R O D U C I N G I D E A S A N D C O N C E P T S</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*LVHl6Lf0MOmFdNiL." /><figcaption>Source: The Noun Project</figcaption></figure><h4>WTF EVEN IS “IDEATION”</h4><p>“Ideation sessions” are a common part of most creative-productive environments. Often times they look like getting a bunch of people in a room, talking for a few minutes about a problem or a customer or a campaign, and then people start “ideating.” This usually consists of a few hours of unstructured conversation, some sticky notes being put on whiteboards, and ad nauseam discussion of the good or bad of a given idea. This is, for the most part, a colossal waste of time as has been shown by numerous cognitive studies. Not the <em>principles</em> that drive us to ideation, but the process that winds up taking shape lead us astray.</p><h4>WORKING PRINCIPLES of IDEATION</h4><p>So if the process is flawed, but the principles are good, what are the principles most ideation processes are trying to capture? What are the values the ideal process generates?</p><ul><li><strong>COLLABORATION | </strong>Pooling together different expertise and perspectives in order to stimulate cross-fertilization of ideas. Combines different pieces of knowledge to generate <strong>novelty</strong>. Harnesses the collective knowledge of a group.</li><li><strong>NOVELTY | </strong>The uniqueness of ideas generated. Measured against the general set of ideas in the relevant field, novelty is a product of 1) unique combinations of existing knowledge or 2) unique deployments of well-developed ideas.</li><li><strong>IMPACT | </strong>The usefulness or reach of ideas generated. Should be a major component evaluated when considering which ideas to prioritize. Note: predictions of impact are impossible to make well (especially with truly novel ideas) so it is important to continuously monitor and measure.</li><li><strong>RECOGNITION | </strong>The ability of the group to <em>sense </em>the quality of an idea and generate a reasonable, safe path for trying it.</li></ul><p>If those four principles are present and acting when we do strategy and ideas right, then I think we are forced to recognize the failings of the sit-around-and-talk-about-it method. In our go to, cognitive biases and social dynamics lead to the loudest and most confidently presented ideas being discussed, and interrupt the ability for group knowledge to be harnessed in the synthesis of novel, impactful new ideas.</p><p>So what can we do? At OpenNest, we’re always excited at the opportunities offered by technology, and there exists a really wonderful tool that is changing the way we do early stage strategy and idea generation. It is called <a href="http://usecandor.com/">Candor</a>.</p><h4>WHY USE CANDOR?</h4><p>One of the largest pitfalls of the <em>group meeting</em> is that it only celebrates certain personalities–those that feel comfortable and confident speaking to a group. Further, in group meetings we typically don’t start crafting ideas until <em>after</em> we’ve heard the opinions of the rest of the group, so we’re under tremendous pressure to offer ideas that fit the narrow construct and values stated or implied. We’re using Candor to allow ideas to be generated privately and outside of these constructs, then evaluating them together. This allows generation and evaluation to be separate, unique processes.</p><h4>HOW TO RUN IDEATION MEETINGS at OPENNEST</h4><p>STEP 1 <strong>Elect a facilitator</strong> (most easily done via <a href="https://docs.google.com/a/opennest.io/document/d/1jExVnPCTizTFcp4sDtMCJwDPnTCgCU678w6MjSAOawI/edit?usp=sharing">Slack</a>). Ideally this person is <strong><em>not </em></strong>the team lead, but someone who can organize the meeting before hand, make sure that team members are participating, and move the meeting through each subsequent step.</p><p>STEP 2 <strong>Focus the team</strong>. Send out the core question or problem to be solved to the team members by sending a link via Candor.</p><p>STEP 3 <strong>Generate ideas in private</strong>, <em>before any discussion</em>. Submit through candor (either web-based or smartphone app). We’ve found this is most effective if the first 5–20 minutes of the allotted meeting time are dedicated to this. Silence is critical. Often times team members disburse through the office to spaces where they feel the most creative. Facilitator calls for time.</p><p>STEP 4 <strong>Put ideas on display.</strong> Use large screens or screenshare and the Candor web app to show ideas to the community. Round table, and allow everyone to clarify the ideas they submitted. No discussion on value yet.</p><p>STEP 5 <strong>Begin to evaluate.</strong> Open up the floor to discussion and critique of ideas. Remember the core principles: we’re selecting for novelty and impact, as well as trying to understand the risk of trying a given activity.</p><p>STEP 6 <strong>Clarify and simplify. </strong>Eliminate ideas the group feels would not be safe to try or do not address the core question. Modify and combine ideas that merit it. Add new ideas if they emerge.</p><p>STEP 7 <strong>Vote! </strong>Use Candor to vote on ideas. If a clear winner stands out, move forward to planning and execution. If a few ideas are close, then return to step five.</p><p><em>Credit where it’s due! This is a process that was built from the core process described by the Candor team, not something we invented out of thin air.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15de34287f61" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growing-opennest/ideas-and-strategy-at-opennest-15de34287f61">Ideas and Strategy at OpenNest</a> was originally published in <a href="https://medium.com/growing-opennest">Growing OpenNest</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tinker With Those Meeting Notes!]]></title>
            <link>https://medium.com/growing-opennest/tinker-with-those-meeting-notes-bf2155efeb73?source=rss----117c888cfb7f---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf2155efeb73</guid>
            <category><![CDATA[organization-design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Spencer Pitman]]></dc:creator>
            <pubDate>Thu, 01 Oct 2015 21:46:39 GMT</pubDate>
            <atom:updated>2015-10-05T18:14:47.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F8RVf3r3A5lJzJw4qDbPQA.jpeg" /></figure><h4>A Small Case Study in Evolving Tools for Teams</h4><p>Something I’ve found over the past few years is that the <em>best</em> meeting structures emerge when we give teams clear working principles and empower them to choose their own ways of achieving those. Instead of top-down mandated systems that disregard the huge variety of ways that people work, this approach allows teams to operate in ways that are sensitive to their individuals’ needs and styles. Importantly though, it does so while ensuring that product and insights remain transferable across the organization.</p><p>Recently I supported a team that evolved a pretty unremarkable artifact — its note-taking and meeting style — to great effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2s8dwsBkTNGG8VvrKlJlsg.png" /></figure><p>I n an effort to expand our capacity to deliver innovative product consulting, we recently brought in a new creative director, <a href="https://dribbble.com/katygarrison">Katy Garrison</a>. When new people come on, and especially if they are expected to lead teams, we find an internal project for them to direct with minimal up-front guidance. By starting off with trust in their ability to lead, we can begin to understand how they work, tap into their background (believe it or not people who have worked other places can sometimes teach us things 👻), and provide the opportunity to expose and resolve weaknesses in our current approach. Our sister company <a href="http://pcragency.com/">PCR</a> needed a website refresh, and this seemed an appropriate initial project for Katy to lead. We determined that the core team would be her as the product manager, a PCR employee as a representative from the client brand, a current OpenNester as a junior strategist, and me as a facilitator.</p><p>Any project that OpenNest delivers must be guided by good Purpose (Derrick Bradley provides a nice working definition <a href="http://derrickbradley.github.io/2015/03/06/making-purpose-applicable/">here</a>). For this website, the team generated the following: <em>To make explicit and accessible the PCR brand to clients, prospects, and seekers online.</em></p><p>Working principles for teams deserve their own post, but some of the common ones at OpenNest across all teams are:</p><ul><li><strong>Default to Open, Connected Systems- </strong>Documents are stored in shared, searchable places set to org-accessible. Conversations should be open and searchable vs. single-tenant. Anyone should be able to status check without having to ask for access.</li><li><strong>Move Small and Revise Frequently</strong>- Complex proposals should be pared down to work that can be safely tried quickly. Reflect at regular intervals on effectiveness of work, and tune outputs accordingly.</li><li><strong>Consumability is the Metric that Matters</strong>- The user is a key stakeholder. [Usually] we are working for our clients’ customers, not just our clients. Measurable improvements in usability and experience always trump vanity quotas.</li><li><strong>Always Collect Data- </strong>Record the essentials. Use systems that track in the background (no work around the work!). Remember that seemingly nonessential data often becomes powerful later. Track changes.</li><li><strong>Slow is Smooth, Smooth is Fast</strong>- “Continuous attention to technical excellence, good design, [and proper tooling] enhances agility.”</li><li><strong>Roles, Not Jobs</strong>- Define clear roles (both static and emergent) required by your project’s success conditions. Be ready to fill multiple roles, and roles that might seem out of your area of expertise. If a role needs to be filled and the present team doesn’t have capacity, tap someone from the organization.</li></ul><p>These were the tools with which Katy was equipped when she launched her first OpenNest project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LR4Bqy8j40LKQejv8IApGg.png" /></figure><p>K aty began with a planning meeting to clarify product management approach, jobs to be done, roles to be filled, and the conditions for success that would allow the team to resolve the period of the project.</p><p>In these meetings, especially when supporting someone leading their first OpenNest project, I try to stay silent and play the role of facilitator, only helping move the team forward through blocks or slowness, and avoiding exerting influence on either the specific ways of working or the design of the project itself (note: this is a growth area for me).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EOQKcVBH9GumhF7noc2wOA.png" /></figure><p>To the left are the notes from that first meeting. I felt that the general frame of the project was accurately captured, and the notes were sufficiently thorough, and I was interested to see how the daily work of the project would connect to the planning document. The team decided that it wanted to use Trello and Slack for task management. The first stand would be two days after the planning meeting, and someone from the team committed all the outcomes from the meeting to Trello.</p><p>A few insights emerged at our first stand. One, while our planning notes may have been thorough in some ways, they provided minimal guidance for how Trello/Slack was going to be used. So if a person needed to get up to speed on the project, they would look at our planning notes and have zero documentation on how to status check the progress of the project in real time. Additionally, we held the meeting in person, so had not recorded it or linked to the notes in the #pcrwebsite Slack channel. We had successfully selected open systems, but insufficiently connected them — a failure to achieve our first working principle.</p><p>Finally, the notes are ugly, kind of hard to read, and have an inconsistent formatting scheme. The taxonomy doesn’t make a ton of sense. Instead of sitting with Katy before the meeting and talking about what we were going to accomplish, I’d built the notes from a standard template I’ve used with other teams. This is a failure against “slow is smooth, smooth is fast” (good design <em>and</em> proper tooling). Citing ugly, uninspiring meeting notes as an early failure might seem overly pedantic, but the devil is in the details. Pleasant, clear visuals should underpin our internal systems as much as they need to guide our work for clients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cp_BfYWOGtVTOsGM-MsEMw.png" /></figure><p>K aty realized that we had the opportunity to record insights and make changes to the ways of working immediately, before starting the project off on the wrong foot. This meant delaying an extra day, but that was alright (<em>slow is smooth, smooth is fast</em>). Prior the second stand, Katy and the team made immediate corrections to the tooling. She pointed all the various productivity tools in play (Trello, Pivotal, Google Drive, etc.) to the central brain of the project, Slack, so that changes would update automatically. This provides two advantages: <strong>1)</strong> it allows progress to be recorded without requiring manual entry into a system (we’re smarter than that) and <strong>2)</strong> it stores all activity and output in a central, searchable location (the quality of search and notifications in Slack are a huge reason we’ve largely moved away from HipChat).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*WxYrPlKbQRZ1DTmIeI4FyA.png" /></figure><p>Katy also noted the problems with the visual taxonomy of the notes themselves, and tasked me (the original note taker) with arriving at a better format. It is worth pointing out here that her willingness to trust me (a non-designer) to generate this document demonstrated <a href="https://medium.com/@AlcesBull/what-i-stole-from-undercurrent-1f9ab3d79ecf">maturity</a> that we think is essential to success in any organization, and was a huge substantiation of our beliefs about the importance of having her join our team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tp4HeImhXjlVBiP39EbGCg.png" /></figure><p>In the left image, you can see the notes from the second stand. Despite the fact that the meeting happened in person, we posted in Slack and tagged @channel with a link to the notes. This makes them infinitely easier to find later, and lets anyone not physically easily jump into the document to follow along.</p><p>Note the evolved visual design for recording information. It’s a simplified scheme with smaller, sans-serif headers, a monospace body font, and information architecture that relies more heavily on indentation and color than rich formatting. This is a pretty obvious reference to information taxa in true plain-text systems like the terminal or SublimeText. Also, note the <em>types</em> of information included in the notes. Content like when the next meeting is, who is helping unblock, and each person’s role in the current meeting is available without any addtional searching.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ohma3BxcEXp4dxaZbQCQjA.png" /></figure><p>T hese small adjustments produced an immediate result. Katy’s team has been working with clarity and speed, and easily manages to address changing requirements. We’ve seen work being shipped in smaller units and within a week we feel like the team is effectively touching each of the working principles it often takes months to grasp. She’s able to fork people in and out of her delivery group and get them up to speed in minutes, rather than</p><p>The lesson? Never overlook the tooling and the small, foundational details if you want projects to move with clarity and agility.</p><p><em>I kind of snuck it in the piece, but we’re really stoked to welcome our new creative director Katy Garrison to OpenNest. Check her out on </em><a href="https://instagram.com/katygarrison/"><em>instagram</em></a><em>, </em><a href="https://dribbble.com/katygarrison"><em>dribbble</em></a><em>, or </em><a href="http://www.katygarrison.com/"><em>online</em></a><em>.</em></p><p><a href="http://opennest.io/"><strong>OpenNest</strong></a><strong> is an team design consultancy founded this earlier this year. We are helping organizations large and small navigate a business climate that is changing faster than it has before.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf2155efeb73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growing-opennest/tinker-with-those-meeting-notes-bf2155efeb73">Tinker With Those Meeting Notes!</a> was originally published in <a href="https://medium.com/growing-opennest">Growing OpenNest</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Platforms for the World to Build Upon]]></title>
            <link>https://medium.com/growing-opennest/platforms-for-the-world-to-build-upon-e946821a8f51?source=rss----117c888cfb7f---4</link>
            <guid isPermaLink="false">https://medium.com/p/e946821a8f51</guid>
            <category><![CDATA[responsive-organisation]]></category>
            <category><![CDATA[acquisition]]></category>
            <category><![CDATA[consulting]]></category>
            <dc:creator><![CDATA[Spencer Pitman]]></dc:creator>
            <pubDate>Thu, 16 Jul 2015 14:29:14 GMT</pubDate>
            <atom:updated>2015-04-15T02:56:31.781Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVyPunVRPTTqM_lYsInbwA.jpeg" /></figure><h4>Why Quirky’s Undercurrent Acquisition Makes So Much Sense</h4><p>As a strategist and organizational designer sometimes located in New York, I’ve remained impressed at the work Undercurrent has done over the last few years. Hell, I’ve even <a href="https://medium.com/@AlcesBull/what-i-stole-from-undercurrent-1f9ab3d79ecf">ripped them off</a> a time or two. I’ve gotten to become friends with several members and alumni of the organization, so I was excited to hear of their <a href="https://medium.com/undercurrents-greatest-hits/a-quirky-er-undercurrent-3f1bf2c9ea17">acquisition by Quirky</a> this week. Understanding the alignment of purpose of both, the move made a lot of sense to me prima facie. However, several people have asked me to explain why a product company would ever acquire a consultancy, so I’m going to attempt to offer my point of view. <em>Please Note: This is based on my own perspective and work, not direct insight into the UC/Quirky deal.</em></p><h3>Some Notes on Modern Consultancy</h3><p>I’m not going to spend a great deal of time explaining what it is organizational designers do, as <a href="http://voidlive.com/art/pretty-pictures-design-approach-activity-output/">I have done so before</a>, and Undercurrent has practically a <a href="https://medium.com/undercurrents-greatest-hits">library of information</a> on the topic. I will point out that, among other things, we specialize in developing business models that emerge from what often constitutes a very different way of thinking about work than many people are used to. The way that companies generate products and render services <a href="http://agilemethodology.org/">has changed a lot</a> over the years, and necessarily the way that we structure work and relationships in <a href="http://holacracy.org/">organizations has had to change</a>–equally, we should expect to mark evolution in how we sell and model our businesses. In a world where complexity is the null condition, everything we do should be about harnessing change for our customer’s advantage.</p><h3>Why Custom Product Companies Have Consultants</h3><p>Recently I cofounded a <a href="http://apellix.com/">product company</a> with a few other folks. We’re working on deploying robots into pretty complex use cases in a few different verticals. We sell to commercial businesses, and every product we deploy is custom-tailored to solve specific hazardous exposure problems that are part of these very inflexible workflows. However, by being flexible in <em>our</em> deployments, we can offer significant improvements to worker safety without the expense to our customers that comes from rebuilding processes from the ground up. Similar to Quirky’s “Powered by Quirky,” we operate on what we sort of blandly call Platform-as-a-Service.</p><p>I love robots, and I love tinkering, but ultimately I’m a systems consultant, not an engineer. I’m not the person who builds and tests and iterates on these things (though I put my time in when I’m needed!). My core function with Apellix is to walk alongside customers in the journey of developing the practices, ways of working, and purpose orientation that allow them to adapt quickly–not only to the immediate change that we are bringing by deploying new technology, but to the continuous change that our platform empowers. This is one part sales in generating custom business models, and many parts service, but it is a necessary function for building disruption <em>into</em> the system itself. Apellix doesn’t sell robots that automate work, we sell a sophisticated platform for continuously and increasingly moving people out of harm’s way…even in processes that seem designed to keep people in it.</p><h3>Delivery of Value vs. Pushing Product</h3><p>From my view, Quirky is deploying at least this level of customization across a much wider variety of customers, and a much more diverse set of use cases than Apellix. Bringing on a shop both as advanced in practice and aligned in purpose as Undercurrent dramatically expands Quirky’s capacity to ensure continuous delivery of value to their customers, which directly improves the <em>quality</em> of the sales that they make.</p><blockquote>“As the pattern gets more intricate and subtle, being swept along is no longer enough.”</blockquote><p>This is our job now. If we expect <a href="http://www.reinventingorganizations.com/">soulfulness</a> from organizations, which we increasingly do, then fire-and-forget sales can no longer be part of our operational paradigm. Our task is to make sure that the value-delivery lifecycle of what we offer extends, and that our customers know how to best use what we’re selling. As conditions change, specific best practices may evolve, but if we have built adaptiveness into our offering then our customers shouldn’t be exposed by this. Pairing responsive consultancy with hard product development allows something that once had a limited and deterministic value lifecycle to become increasingly plastic.</p><h3>A Trend?</h3><p>If the advent of X-as-a-Service models is any indication, the way that people connect with brands is changing. We increasingly want ongoing connection to solutions, and decreasingly look to simply have a widget in our pocket. As the use cases for these solutions see mounting complexity (such as with companies like ours or Quirky that are selling to other businesses) expect to hear about acquisition strategies like Quirky-Undercurrent more often.</p><p>I’m not really one for forecasting with any certainty, but I think this deal represents an exciting possibility for the future of both product development partnerships and consultancy.</p><p>The future is dead, long live the future.</p><p><em>I’m spencer. lately</em>: <a href="https://medium.com/@AlcesBull">medium</a> | <a href="https://twitter.com/AlcesBull">twitter</a> | <a href="http://pcragency.com/">pcr</a> | <a href="http://apellix.com/">apellix</a> | <a href="http://caracal.io/">caracal</a><br><em>into cities, mountains, wilderness, ocean and trying to figure out how to make things better for everyone.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e946821a8f51" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growing-opennest/platforms-for-the-world-to-build-upon-e946821a8f51">Platforms for the World to Build Upon</a> was originally published in <a href="https://medium.com/growing-opennest">Growing OpenNest</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No Tablets from the Mountain]]></title>
            <link>https://medium.com/growing-opennest/no-tablets-from-the-mountain-718e457fe1a7?source=rss----117c888cfb7f---4</link>
            <guid isPermaLink="false">https://medium.com/p/718e457fe1a7</guid>
            <dc:creator><![CDATA[Spencer Pitman]]></dc:creator>
            <pubDate>Wed, 15 Jul 2015 21:34:47 GMT</pubDate>
            <atom:updated>2015-07-16T15:18:45.431Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ul_CM66VeAULEw0haWaEHw.jpeg" /></figure><h4>On Embracing the Responsibility of Opportunity</h4><p>“No tablets are going to come down from the mountain,” <a href="http://www.artofclientservice.com/">Robert Solomon</a> chuckles to me over the phone.</p><p>Robert is a mentor, and we’re discussing the increasingly fluid nature of how OpenNest is developing its business, having recently shipped a rebranded and significantly pivoted model. Of course, the idea that not only do we embrace change, but we harness it is part of the whole deal–we’re a planning and strategy group that specializes in the type of projects that require long-term vision and comfort with chaotic conditions.</p><p>I had been musing about how important it was for us to have easily changeable <em>everything–</em>for instance, teams choose their own ways of working and billing according to the needs of a client or project–and Robert deployed grand mythological examples accompanied by his knowing, cosmically sardonic commentary: “Oh, if only the Lord worked in <em>those</em> mysterious ways.”</p><p>Indeed, it might be convenient if the god of consultancy would present to us the plan to end all plans, the model to fit all models. The 10 Commandments of Strategy, as it were. But we know better than to believe that anything is fit for writing in stone.</p><p>A few weeks ago, one of us read the <a href="http://www.amazon.com/Elon-Musk-SpaceX-Fantastic-Future/dp/0062301233">Elon Musk biography</a>. That person came in gushing about how amazing the vision (and dedication to that vision) of this modern titan of industry was.</p><p>I don’t entirely disagree, which is to say I do not entirely agree. Musk’s <a href="http://www.teslamotors.com/">com</a>p<a href="http://www.spacex.com/">anies</a> and <a href="http://www.spacex.com/hyperloop">ideas</a> are certainly outstanding, especially when compared to what many billionaires choose to do with their wealth. But I am not amazed by them.</p><p>Elon Musk’s personal history is interesting, and I don’t want to get too mired in the details of his upbringing, but suffice it to say he came from a position of significant opportunity (<a href="https://en.wikipedia.org/wiki/Elon_Musk">Wikipedia overview here</a>). What is inspiring about his story is his ardent dedication to taking advantage of that opportunity in service of a transformative vision: <em>to extend the life expectancy of our species</em>. Note: I do not mention his opportunity in an attempt to diminish or discredit him in any way, only to point out that he, like many of us, started off with a set of advantages, and those advantages (because of both intrinsic and extrinsic factors) continued to grow over the course of his life. When I see the work he is doing now I am not amazed by it because my response is so much more pragmatic. S<em>omeone is actually doing with opportunity what they should</em>. They are leveraging it to write history, not just for themselves, but for the good of our entire species.</p><p>I actually think that it is our <em>responsibility</em> to use any advantages and privileges afforded us to lift up others. To extend the opportunity we have to others who don’t. This is the greatest privilege of well…privilege…to be able to reinvest it in our human community. To make things better for everyone.</p><p>The inspiring part of Elon Musk’s story is not where he has arrived today, it is how he has <strong>consistently taken action</strong> in order to get there. There is a lesson in this for many Westerners: take what you have and grow it in favor of a massive, transformative purpose. This should be standard practice, especially among us with access to significant opportunity.</p><p>When our partner came in a few weeks ago and we began discussing Elon Musk’s astounding story, our conversation was not about how much he was worth, or how many companies he had sold, or even really where he had gotten to at this point. <strong>It was about how we could harness our own set of advantages</strong> (an established sustainable business, educated and growing perspectives, a beautiful office, access to transportation, minimal technical or organizational debt, and more) <strong>to service a similarly grand vision.</strong></p><p>This played well what we had already begun working on–launching a consultancy that harnesses our team’s diverse backgrounds to aid organizations in reconfiguring for the world as it is today and will be tomorrow. The post-internet, post-app, post-information age. Where volatility is the standard.</p><p>Over the the course of our careers (and the last two years of working together) we have converged upon a few shared observations. Some of these are intuitive, some of them are more researched, but for the most part:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NvaIoZ0S2WRnw-I4fJjpw.png" /></figure><ul><li><a href="http://www.slideshare.net/SpencerPitman/responding-to-change-how-social-technology-should-empower-better-faster-organizations">People interact differently</a> and less predictably with brands than they have historically.</li><li>Most organizations are built on an archaic model that is designed to render predictable outcomes given predictable inputs.</li><li>The inputs for most of our organizations are<a href="http://www.nber.org/papers/w7590"> increasingly volatile</a>.</li><li>Human organizations are complex, and trend toward increasing complexity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fnBuR2rWtBCO8IIlYQSaOA.png" /></figure><ul><li>Scientific philosophy gives us the <a href="http://www.itl.nist.gov/div898/handbook/pri/section1/pri11.htm">best tools and methods</a> for consistent &amp; repeatable evaluation.</li><li>Scientific history provides more <a href="http://palaeos.com/phylogeny/cladistics/index.html">proven organizational models</a> than human history.</li><li>Over time, organizational <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3399200/">plasticity</a> is a more advantageous trait than organizational robustness.</li><li><a href="http://www.ucmp.berkeley.edu/clad/clad1.html">Cladistics</a> provides a useful (if sometimes imperfect) model both for organizing information produced by a system and for organizing a complex system itself.</li><li>Harnessing change means combining nimbleness, purposefulness, and available tools.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYnLDSauU37NArjOxCKAoQ.png" /></figure><ul><li>Work should be meaningful, and if possible, enjoyable.</li><li>The workplace should be a space of humanity, even at the occasional expense of “professionalism.”</li><li>Culture emerges from the rhythms of the team; it is not mandated by leaders.</li><li>It is our responsibility to use what we have to make things better–for everyone.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*auLoO1GQJvVbpUv_Nuw0ug.png" /><figcaption>These observations have culminated in a broad (but still incomplete) set of principles that inform our work.</figcaption></figure><ol><li><em>Anti-entropy:</em> Open systems often seem chaotic early on, but with good Purpose alignment and guidance, they organize and become more effective over time.</li><li><em>Proximity: </em>Best solutions emerge from the work and insight of teams closest to the problem; they are not mandated from above.</li><li><em>Reductive Simplicity</em>: A bias toward actionable solutions requires the willingness to be lossy (simple action over delaying for perfection).</li><li><em>Group OODA (Observe-Orient-Decide-Act):</em> The best work we do is made better by collaboration, and continuous iteration aligned to clear <a href="http://derrickbradley.github.io/2015/03/06/making-purpose-applicable/">purpose</a>.</li><li><em>Bias toward Adaptivity:</em> Seeking predictable outcomes is less important than being able to adapt on the fly and harness changing conditions.</li><li><em>Collective Intelligence:</em> Human systems require human context–our organization should not exist in a bubble and should seek to both educate and be continually educated.</li><li><em>Move toward Equilibrium:</em> Default to what’s best for the least empowered group in a system. If we are capacitated to make change, then we must use our power to the benefit of elements marginalized by old versions of the systems we’re rewriting.</li></ol><p>If you’re thinking, <em>what the hell is this guy talking about and what does it have to do with consulting?</em> then I don’t blame you. When we began this, I’m not sure we understood exactly what we were getting into (but that’s completely fine with us: <em>responding to change over following a plan</em>). My point in discussing Musk was simply that doing big, transformative, visionary things with <em>whatever</em> we’re given is our responsibility, and reflexively, <strong>we’ve been given a lot.</strong></p><p>So with all that being said, and in light of the observations and principles above, I’d like to introduce you to our new brand, our new vision, our new business. We are <a href="http://opennest.io/">OpenNest</a>, a strategy and planning firm committed to partnering with organizations interested in solving seemingly impossible problems through purposeful experimentation to make things better for people. We’re inspired by the commitment of Musk, the mission of <a href="http://nobl.io/">NOBL</a>, the function of <a href="http://undercurrent/">Undercurrent</a>, the ingenuity of <a href="http://www.akqa.com/">AKQA</a>, the ethic of <a href="http://tostan.org/about-us/mission-history">Tostan</a>, and the reality that we have a tremendous opportunity to help organizations evolve to being critical engines in the extension of humanity.</p><p>No tablets will come down from the mountain, but if we can develop technologies and models that make things better for everyone, we may be able to lead ourselves out of the desert.</p><p><em>OpenNest is a strategy firm that works with innovation programs, startups, marketing teams, and product teams to create ideas, products, campaigns and organizational systems built to adapt and improve over time. </em><a href="http://www.slideshare.net/SpencerPitman/responding-to-change-how-social-technology-should-empower-better-faster-organizations"><em>Organizational models are archaic</em></a><em>, but we’re helping them evolve for a better future.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=718e457fe1a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growing-opennest/no-tablets-from-the-mountain-718e457fe1a7">No Tablets from the Mountain</a> was originally published in <a href="https://medium.com/growing-opennest">Growing OpenNest</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>