<?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 James Birchler on Medium]]></title>
        <description><![CDATA[Stories by James Birchler on Medium]]></description>
        <link>https://medium.com/@jamesbirchler?source=rss-f18ae1eed2bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tLgEehJW-SXkPIu09ZTXgA.jpeg</url>
            <title>Stories by James Birchler on Medium</title>
            <link>https://medium.com/@jamesbirchler?source=rss-f18ae1eed2bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:54:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jamesbirchler/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[Protect Your Engineering Culture As You Scale: Write Down Your Team’s Cultural Manifesto]]></title>
            <link>https://medium.com/@jamesbirchler/protect-your-engineering-culture-as-you-scale-write-down-your-teams-cultural-manifesto-2f17b41c2b45?source=rss-f18ae1eed2bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f17b41c2b45</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[James Birchler]]></dc:creator>
            <pubDate>Fri, 23 Mar 2018 22:47:53 GMT</pubDate>
            <atom:updated>2018-03-29T04:25:26.205Z</atom:updated>
            <content:encoded><![CDATA[<p>“Culture eats strategy for breakfast.” — Peter Drucker</p><p>I frequently speak with startup founders and leaders who are growing and scaling their teams, and among the most common questions I hear focus on building and maintaining engineering team culture. Establishing your culture is hard, maintaining it as you scale is harder. I’d like to share a few of the lessons I’ve learned about team culture, some of them the hard way, during my last 15 years working with engineering teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*0L41RdHh_Xs57z36rDB2Pw.png" /></figure><p>Scaling your team can wreak havoc on your established culture, overwhelming it with surprising speed as new hires bring fresh ideas and expectations about how your teams function and collaborate — but only if you let it.</p><p>In other words, the real threat to your culture is not your newcomers, it is the challenge of being mindful and selective about what you decide to incorporate into your culture.</p><p>A written manifesto is a simple and effective tool to manage the evolution of your culture to maintain its core attributes.</p><p>Your culture is the manifestation of the customs, institutions, attitudes, behaviors, and achievements of a group, regarded collectively. In other words, culture is both a product <em>and</em> a process. Your culture evolves — either maintaining or changing — every day in the myriad ways you and your team interact, converse, and collaborate, literally manifesting your culture and making it obvious to all. Your culture is a living archive of all your team has done together.</p><p>By writing down your team’s manifesto — a public declaration of your culture and the standards by which you agree to practice, operate, and be held accountable — you are creating a concrete artifact. By informing everyday words and deeds, a manifesto can be a powerful reinforcer of your company culture.</p><p>I recommend a basic process framework for creating written artifacts which allows for input from all quarters to ensure buy in, while avoiding the paralysis of “design by committee.” Start with ideas, build to a proposal, and finally present a recommendation for adoption.</p><p>It is important to communicate this overall process to your team to set expectations and ensure everyone understands when and how they will have input. The goal here is to have your team bought in, and it is important that people feel like they have a voice in the process.</p><p>When you’re ready to write your manifesto, start with a core group of leaders and ask them to author the manifesto with you. Begin with an idea brainstorm, and ask them to begin drafting a proposal. As they share versions of the manifesto, ask them to incorporate feedback from others in a way that authentically captures the feedback. This is challenging work, as they will need to balance a variety of perspectives. Do not rush this process, and expect this may take several weeks from start to finish.</p><p>Make your first shares to a small but diverse set of individuals who can quickly provide feedback to ensure your proposal is directionally correct. From there, share it with your entire team, inviting input, comments, and feedback. Share new versions of the revised manifesto periodically rather than in real time to allow for the team drafting the document to think through, discuss, and carefully craft their revisions.</p><p>Here are some sample statements from my own teams’ engineering manifestos over the years. You’ll see they cover a wide range of issues around how my teams have chosen to work together, from the practice of software engineering to mindset and communication. I think some of the strongest statements are ones that define how you make tradeoffs.</p><p><em>“We develop and test our code in a safe and controlled manner using modern tools and processes. We are careful to isolate potential instability in shared environments, services, and data. We consider and plan for potential areas of risk, mitigating them whenever possible.”</em></p><p><em>“For any project, we always determine how we will measure its success or failure, and how we will respond to either of these outcomes, and we commit to that follow-up work.”</em></p><p><em>“We work iteratively, shipping products quickly to test our riskiest assumptions first to validate our ideas and learn quickly. We practice the 80/20 rule, and believe that rapid iteration, “Launch and Learn,” is a better strategy to deliver value to our customers than seeking perfection before shipping.”</em></p><p><em>“We mix modern best practices with pragmatic choices to craft software we are proud of.”</em></p><p><em>“Every bug we fix or new feature we build has automated test coverage. If it’s hard to write tests for something, we figure out why and fix it so that it won’t be hard in the future. Code without tests is our “nuclear option” — a last resort and a decision that we make reluctantly and rarely.”</em></p><p><em>“We leave each piece of code we touch better than we found it. We refactor and clean up code, but we’re careful to prioritize that work based on the value it delivers to customers, or whether it makes it easier to change the code in the future.”</em></p><p><em>“We actively support one another. We create safe spaces for communication so we can feel safe being vulnerable to speak candidly, and ask for help when we need it. We want it to feel comfortable to both seek and offer help.”</em></p><p><em>“We take the time to reflect on, learn from, and talk candidly about both our successes and our mistakes. We practice retrospectives and debriefs to capture learnings so we can repeat the good and discontinue the bad. We assume positive intent, and seek understanding not blame.”</em></p><p><em>“We use processes as guides, but do not follow them blindly. We expect our processes to change as our context and awareness changes, and as we learn and grow.”</em></p><p>Once your team has a version of the manifesto they feel represents your culture and the standards by which the team agrees to practice, operate by, and be held accountable to, ask them to present it as a formal recommendation to the approver (usually the VPE or CTO for an engineering team).</p><p>At this point, everyone on the team ought to be familiar with the manifesto, and when you ask they should tell you that it resonates strongly with them. If this is not the case, send the recommendation back for more revisions.</p><p>If it is ready, it’s time to roll it out. Plan to communicate your manifesto in multiple venues and using every possible medium. Add a copy to your engineering department wiki or documentation, and provide pointers everywhere your team hangs out online: pin it to your team Slack channel, email to your team list, post in IRC — and in all cases make sure it’s archived and searchable. Make posters and print copies of your manifesto and display them prominently.</p><p>Next, hold a ceremony at your next engineering team allhands to announce your manifesto and celebrate it — make it real. Announce it at the company allhands, too, ensure that everyone knows how your team plans to hold itself accountable to delivering for customers and the business. Ensure your managers know to revisit your manifesto regularly, until it too is part of your team’s regular practice of engineering and its culture.</p><p><em>Learn more about </em><a href="https://jamesbirchler.com/about/"><em>what I do</em></a><em> and </em><a href="https://jamesbirchler.com/about/"><em>why I do</em></a><em> it at </em><a href="https://www.jamesbirchler.com/"><em>jamesbirchler.com</em></a><em>.</em></p><p><em>Image Credit: Image cropped from “</em><a href="https://www.flickr.com/photos/29233640@N07/5652406766/in/photolist-9Bu4B5-d7G1Tb-8bjr3J-bpNyoj-7GxjAW-9fA8fD-6T31Pg-DepTBW-c1b9m9-8bjrpd-EnwMvC-XxaNry-9fAdZr-9fAH9T-BXMPUw-Chq8go-9fBbSF-bpFvHw-55oNJq-55jBtc-bCHusH-dgE9xV-EeF9fJ-73ZtyT-55oP93-c1b8E1-rGCJ7z-ch5Dsy-bneymr-7zY4BL-e4eYxE-odhtg2-hMz3gL-9fEjcE-jiRKUV-kEKCKG-c1bhbo-c1bgSY-55oPi5-c1bfjh-21ixQhp-c1bgyU-c1b8eN-owW1oK-kEKKeJ-55jBnp-mwvXjc-c1b8Vy-55jBVk-c1beU7"><em>science</em></a><em>” by Robert Couse-Barker, </em><a href="https://creativecommons.org/licenses/by/2.0/"><em>Creative Commons License</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f17b41c2b45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lean Startup Best Practices: Build a culture that supports learning.]]></title>
            <link>https://medium.com/@jamesbirchler/lean-startup-best-practices-build-a-culture-that-supports-learning-d4002b057c27?source=rss-f18ae1eed2bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4002b057c27</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[James Birchler]]></dc:creator>
            <pubDate>Fri, 14 Oct 2016 18:50:37 GMT</pubDate>
            <atom:updated>2016-10-14T23:00:01.877Z</atom:updated>
            <content:encoded><![CDATA[<p>Building valuable products for customers is challenging, and <a href="http://www.startuplessonslearned.com/2008/09/lean-startup.html">Lean Startup</a> methodologies can help. The very act of learning itself is fundamental to these principles, and it’s worth attending to: one of the core tenets of Lean Startup practice is the <a href="http://theleanstartup.com/principles">Build-Measure-Learn</a> loop, an <a href="http://jamesbirchler.com/2011/10/26/sf-lean-startup-circle-the-new-science-of-product-development/">application of the scientific method</a>. But how do you maximize your learning with every pass through the loop, in the face of both success and inevitable failure? A healthy culture that supports learning can help ensure that you gain maximum value from every experiment you run.</p><p>It’s easy when your data comes back validating your hypotheses about your customer and business, but what happens when you upset your beliefs about your customer or business? I’ve seen too many teams ignore hard data and learnings only to maintaining a course toward product development failure. And even science-based Lean Startup methods will fail without a culture that supports learning. To illustrate why, I’ll briefly draw your attention to an example from the history of science.</p><p>Copernicus, Giordano Bruno, and even Galileo, widely known as a founder of modern science, were persecuted, arrested, and even burned at the stake, in part because the prevailing culture didn’t support their scientific methods of learning and the data and findings they presented.</p><p>The Catholic Church began the Inquisition in 12th-century France to combat heresy — but it took its toll on science throughout the 16th and 17th centuries before it was finally abolished in the early 19th century.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/0*3orR5Jo7PulhQ7lC.png" /><figcaption><em>A product manager presenting customer data to the executive team, or two priests showing the application of torture under the supervision of the Inquisition?</em></figcaption></figure><p>Nicolaus Copernicus formulated the heliocentric model of cosmology, placing the Sun at the center of the universe rather than the Earth. This was literally Earth shattering news at the time for the Catholic Church, which saw this as a threat to their authority based in their belief system — which included the Earth being at the center of things.</p><p>Instead of dealing with the facts of the situation, they attacked the messengers. Copernicus so feared the Inquisition that he delayed publishing his findings until he was on his deathbed in 1543. Giordano Bruno followed Copernicus and was burned at the stake. Galileo was placed under house arrest until his death.</p><p>Why was is so hard for these scientists to share their data and findings? The answer is complicated, but many product development professionals know the answer all too well. Suffice it to say that the prevailing culture espoused by the leadership at the time did not support their findings, particularly when that learning contradicted the prevailing belief system.</p><p>The parallels with modern product development teams, even or perhaps especially those practicing Lean Startup principles, are stark.</p><p>What is the culture like in your company? Is it hard to speak up when you have learnings to share and the news seems to contradict your quarterly goals or yearly plan? Does the <a href="http://www.exp-platform.com/documents/guidecontrolledexperiments.pdf">highest-paid person’s opinion</a> matter more than your customer data? Do teams and leaders prefer to stay the course, even when data is signaling a change might be warranted? I’m aware of too many companies that suffer from a combination of hubris, denial of reality, and delusions that everything is going according to plan — even as the projects, teams, and in the worst case, the entire company, is headed toward failure.</p><p>So what can we do?</p><p>The point I’m making is that culture matters. Creating a culture that supports continuous learning can help protect you in the face of visionary leaders with compelling reality distortion fields or your own subconscious desire to believe that your project is on track, even when it’s not.</p><p>Creating a safe space to learn within your company — a culture that supports learning in the face of both success <em>and</em> failure — while challenging, is worth the effort. Even with the world’s best product team building, experimenting, and measuring results, Lean Startup methodologies won’t work without a culture that supports learning from your data.</p><p>I’ve <a href="http://jamesbirchler.com/2016/10/06/lean-startup-practices-write-hypotheses-you-can-learn-from/">discussed previously</a> why it’s often better to reorder the Build-Measure-Learn loop to start with learning rather than building, as building without an understanding of your customer is superstition, not science. Learning literally comes first, beginning with what you already know about your customers and your business. <a href="http://jamesbirchler.com/2016/10/06/lean-startup-practices-write-hypotheses-you-can-learn-from/">Good hypotheses are also required</a>, as they drive experiments that you truly can learn from.</p><p>But what of culture? Culture is at once a process and a product. This means we have the power to change culture, but it requires conscious, meaningful effort. Think about how you want your culture to be, then take action. Everyone on your team contributes in minute ways to building, changing, and refreshing your culture with every interaction and every word spoken.</p><blockquote>Culture is at once both a process and a product; we can make change with conscious, meaningful effort. — <a href="http://ctt.ec/EKXe2">Tweet This</a>.</blockquote><p>Leaders have a responsibility here, of course. Culture starts at the top and permeates your organization. Your leadership team must be aligned and supportive — but that is not enough.</p><p>Leaders must make conscious efforts to build and maintain a culture of learning. Candor, based in vulnerability and accountability, is required. Clear communication about how the culture is meant to be will help — it should be written down, easily accessible, and referenced often in your practice.</p><p>Leaders, like everyone else, need to make an ongoing, conscious effort to build and maintain a culture that supports learning. Practice is key, and leading by example works. Executives can and should conduct root cause analysis when things don’t go as expected, and discuss the learnings and action items openly within the company.</p><p>It’s won’t be enough that one of your executive, engineering, product, or other teams practices a learning culture in isolation, so plan ways to ensure everyone practices together. Most teams are multidisciplinary, so ensure that everyone participates in learning moments through reporting on experiments, and during project retrospectives and postmortems. Learnings and action items should be communicated widely, and used as inputs to your product development and planning processes.</p><p>Building and maintaining a healthy culture that supports learning will help you maximize value from every turn through the Learn-Build-Measure loop, and help you make good on the promise of the Lean Startup.</p><p><em>I’m a product development leader, advisor, and coach. Learn more about </em><a href="https://jamesbirchler.com/about/"><em>what I do</em></a><em> and </em><a href="https://jamesbirchler.com/about/"><em>why I do it</em></a><em> at </em><a href="https://www.jamesbirchler.com/"><em>jamesbirchler.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4002b057c27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lean Startup Best Practices: Write hypotheses you can learn from.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@jamesbirchler/lean-startup-best-practices-write-hypotheses-you-can-learn-from-7e119afa0080?source=rss-f18ae1eed2bf------2"><img src="https://cdn-images-1.medium.com/max/2232/1*58IDq6v9567-UCeCzbKJsg.png" width="2232"></a></p><p class="medium-feed-snippet">If you practice Lean Startup methodologies, you&#x2019;re likely familiar with Build-Measure-Learn. It seems like the directive here is to first&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@jamesbirchler/lean-startup-best-practices-write-hypotheses-you-can-learn-from-7e119afa0080?source=rss-f18ae1eed2bf------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@jamesbirchler/lean-startup-best-practices-write-hypotheses-you-can-learn-from-7e119afa0080?source=rss-f18ae1eed2bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e119afa0080</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[scientific-method]]></category>
            <dc:creator><![CDATA[James Birchler]]></dc:creator>
            <pubDate>Fri, 07 Oct 2016 16:44:36 GMT</pubDate>
            <atom:updated>2024-11-15T16:39:32.064Z</atom:updated>
        </item>
    </channel>
</rss>