<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Organizational Design on Tobi(as Mende)</title><link>https://mende.io/tags/organizational-design/</link><description>Recent content in Organizational Design on Tobi(as Mende)</description><generator>Hugo</generator><language>en-us</language><managingEditor>tobi@techunicorn.builders (Tobias Mende)</managingEditor><webMaster>tobi@techunicorn.builders (Tobias Mende)</webMaster><lastBuildDate>Fri, 27 Jun 2025 05:00:00 +0000</lastBuildDate><atom:link href="https://mende.io/tags/organizational-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations</title><link>https://mende.io/blog/rethinking-leadership-in-b2b-saas/</link><pubDate>Fri, 27 Jun 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/rethinking-leadership-in-b2b-saas/</guid><description>&lt;h1 id="rethinking-leadership-in-b2b-saas-lessons-from-self-managing-organizations">Rethinking Leadership in B2B SaaS: Lessons from Self-Managing Organizations&lt;/h1>
&lt;p>Two months ago, I joined the &lt;a href="https://www.corporate-rebels.com/masterclass">Corporate Rebels Masterclass&lt;/a> – a hands-on exploration of how pioneering companies like Buurtzorg, Haier, Viisi, and others approach leadership, structure, and collaboration. These aren’t companies tinkering at the edges. They’ve built entire systems that challenge our default assumptions about how work &lt;em>should&lt;/em> be organized.&lt;/p></description></item><item><title>Organizational Change Leadership</title><link>https://mende.io/blog/organizational-change-leadership/</link><pubDate>Sat, 01 Feb 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/organizational-change-leadership/</guid><description>&lt;h1 id="organizational-change-and-leadership--driving-change-effectively-within-organizations">Organizational Change and Leadership — Driving change effectively within organizations&lt;/h1>
&lt;p>Many people believe that you have to be in an official leadership position with official authority and power to lead change in organizations. This is far from the truth. I would even argue that it is easier to drive successful change if you do not have that formal authority.
This is because without formal authority, you have to lead the change right (we will get to that in a bit). With formal authority, on the other hand, you can force the change, which can lead to frustration, resignation, and damage to the organization overall. Even worse, people might not speak up against change that they do not understand or that does not make sense to them. Therefore, whenever being in a leadership position with formal power, be extra cautious about how you drive change.
In my article about &lt;a href="https://tidbits.mende.io/p/organizational-tension-processing">organizational tension processing&lt;/a>, I already tapped into an approach how we can initiate change in organizations without formal (hierarchical) authority. In today&amp;rsquo;s article, I explore the topic of how to drive the actual change and how to ensure that it becomes a success, in greater detail.&lt;/p></description></item><item><title>Better Alternatives to Performance Reviews</title><link>https://mende.io/blog/better-alternatives-to-performance-reviews/</link><pubDate>Sat, 07 Dec 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/better-alternatives-to-performance-reviews/</guid><description>&lt;h1 id="better-alternatives-to-performance-reviews">Better Alternatives to Performance Reviews&lt;/h1>
&lt;p>Traditional performance reviews often fall short of delivering the value they promise. Even worse: They can have disastrous effects on motivation, engagement, and performance of teams and individuals. I have explored the reasons for this in detail in &lt;a href="https://tidbits.mende.io/p/performance-reviews-considered-harmful">my last newsletter&lt;/a>.
In today’s article, I would like to explore what we can do instead to satisfy the actual needs companies and individuals might have.&lt;/p></description></item><item><title>Performance Reviews Considered Harmful</title><link>https://mende.io/blog/performance-reviews-considered-harmful/</link><pubDate>Sat, 02 Nov 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/performance-reviews-considered-harmful/</guid><description>&lt;h1 id="performance-reviews-considered-harmful">Performance Reviews Considered Harmful&lt;/h1>
&lt;p>Performance reviews are widely accepted in software companies to provide feedback, justify or object to promotions, and discuss compensation increases. Typically, they occur between an engineering manager and their reports, often cited as a necessary function of management within an organization. They are simply “how the world works.” Big companies do them, small companies do them, and highly paid consultants develop new and &lt;em>better&lt;/em> ways of conducting them.&lt;/p></description></item><item><title>Organizational Tension Processing – Driving Change in Self-Organizing Companies</title><link>https://mende.io/blog/organizational-tension-processing-driving-change-in-self-organizing-companies/</link><pubDate>Sat, 05 Oct 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/organizational-tension-processing-driving-change-in-self-organizing-companies/</guid><description>&lt;h1 id="organizational-tension-processing--driving-change-in-self-organizing-companies">Organizational Tension Processing – Driving Change in Self-Organizing Companies&lt;/h1>
&lt;p>Newcomers to self-organization often mistake the lack of a people-hierarchy for complete chaos. The term “flat” can be misleading, as it suggests that self-organizing companies lack any structure. In reality, this is far from the case.&lt;/p></description></item><item><title>Things I love and hate about the state of software companies in 2024</title><link>https://mende.io/blog/things-i-love-and-hate-about-the-state-of-software-companies-in-2024/</link><pubDate>Sat, 16 Mar 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/things-i-love-and-hate-about-the-state-of-software-companies-in-2024/</guid><description>&lt;h1 id="things-i-love-and-hate-about-the-state-of-software-companies-in-2024">Things I love and hate about the state of software companies in 2024&lt;/h1>
&lt;p>&lt;strong>Disclaimer:&lt;/strong> This started as a rant, not meant to be published. But sticking to my “&lt;a href="https://nudge.unblocked.engineering/p/cutting-through-the-noise-becoming">New Year’s resolution&lt;/a>” to write about what triggers me most, I decided to publish it anyway. I wanted to publish it as a LinkedIn post, but it got too long. So here is the unshortened, unpolished and authentic original version of this document, most of which I wrote on my phone after waking up on a Sunday at 5:45am. 😬&lt;/p></description></item><item><title>Self-organizing companies don&amp;#8217;t need managers but coaches</title><link>https://mende.io/blog/self-organizing-companies-dont-need-managers-but-coaches/</link><pubDate>Sat, 20 Jan 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/self-organizing-companies-dont-need-managers-but-coaches/</guid><description>&lt;h1 id="self-organizing-companies-don8217t-need-managers-but-coaches">Self-organizing companies don’t need managers but coaches&lt;/h1>
&lt;p>If you are a manager or consider managing teams and organizations a significant part of your profession, the title will likely cause a feeling of rejection or a strong disagreement. I invite you to read on anyway.&lt;/p></description></item><item><title>Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies</title><link>https://mende.io/blog/selling-devex-initiatives-in-purpose-vs-profit-oriented-companies/</link><pubDate>Sat, 21 Oct 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/selling-devex-initiatives-in-purpose-vs-profit-oriented-companies/</guid><description>&lt;h1 id="selling-devex-initiatives-in-purpose-vs-profit-oriented-companies">Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies&lt;/h1>
&lt;p>For years, a conversation has been ongoing on naming in the DevEx community (and within myself). Of course. Naming is hard, and why shouldn’t it be any different for this domain?&lt;/p></description></item><item><title>Engineering Strategy: Actionable and Specific Guidance for Growing Engineering Teams (High-Purpose Environments, Part 6)</title><link>https://mende.io/blog/engineering-strategy-actionable-and-specific-guidance-for-growing-engineering-teams-high-purpose-environments-part-6/</link><pubDate>Sat, 10 Jun 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/engineering-strategy-actionable-and-specific-guidance-for-growing-engineering-teams-high-purpose-environments-part-6/</guid><description>&lt;h1 id="engineering-strategy-actionable-and-specific-guidance-for-growing-engineering-teams-high-purpose-environments-part-6">Engineering Strategy: Actionable and Specific Guidance for Growing Engineering Teams (High-Purpose Environments, Part 6)&lt;/h1>
&lt;p>In the previous articles of my &lt;a href="https://mende.io/blog/tag/high-purpose-environments/">high-purpose environments series&lt;/a>, we have explored the importance of &lt;a href="https://mende.io/blog/the-importance-of-an-engineering-vision-high-purpose-environments-part-2/">vision&lt;/a>, &lt;a href="https://mende.io/blog/the-importance-of-values-and-guiding-principles-for-distributed-decision-making-high-purpose-environments-part-4/">values, guiding principles&lt;/a>, and &lt;a href="https://mende.io/blog/engineering-excellence-through-mission-driven-teams-high-purpose-environments-part-5/">engineering mission&lt;/a> in creating a thriving and purpose-driven engineering culture. In this final article, I will delve into engineering strategy — a crucial element that translates high-level objectives into actionable and specific guidance for growing engineering teams.&lt;/p></description></item><item><title>Engineering Excellence through Mission-Driven Teams (High-Purpose Environments, Part 5)</title><link>https://mende.io/blog/engineering-excellence-through-mission-driven-teams-high-purpose-environments-part-5/</link><pubDate>Sat, 03 Jun 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/engineering-excellence-through-mission-driven-teams-high-purpose-environments-part-5/</guid><description>&lt;h1 id="engineering-excellence-through-mission-driven-teams-high-purpose-environments-part-5">Engineering Excellence through Mission-Driven Teams (High-Purpose Environments, Part 5)&lt;/h1>
&lt;p>In software engineering and product development, high-purpose environments are vital for driving innovation, creativity, and collaboration. A strong sense of purpose, clear values, and a commitment to continuous growth and improvement characterize these environments.&lt;/p></description></item><item><title>The Importance of Values and Guiding Principles for Distributed Decision-Making (High-Purpose Environments, Part 4)</title><link>https://mende.io/blog/the-importance-of-values-and-guiding-principles-for-distributed-decision-making-high-purpose-environments-part-4/</link><pubDate>Sat, 27 May 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-importance-of-values-and-guiding-principles-for-distributed-decision-making-high-purpose-environments-part-4/</guid><description>&lt;h1 id="the-importance-of-values-and-guiding-principles-for-distributed-decision-making-high-purpose-environments-part-4">The Importance of Values and Guiding Principles for Distributed Decision-Making (High-Purpose Environments, Part 4)&lt;/h1>
&lt;p>Values and guiding principles are crucial in enabling distributed decision-making within an organization. They empower individuals to make decisions autonomously, without constant supervision or hierarchical approval. This leads to increased efficiency and agility and fosters a sense of ownership and responsibility among team members.&lt;/p></description></item><item><title>Crafting a Compelling Engineering Vision (High-Purpose Environments, Part 3)</title><link>https://mende.io/blog/crafting-a-compelling-engineering-vision-high-purpose-environments-part-3/</link><pubDate>Sat, 20 May 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/crafting-a-compelling-engineering-vision-high-purpose-environments-part-3/</guid><description>&lt;h1 id="crafting-a-compelling-engineering-vision-high-purpose-environments-part-3">Crafting a Compelling Engineering Vision (High-Purpose Environments, Part 3)&lt;/h1>
&lt;p>Creating a solid engineering vision is essential to building a high-purpose environment. A well-defined vision acts as a guiding star for your team and ensures that everyone is working towards the same goal.&lt;/p></description></item><item><title>The Importance of an Engineering Vision (High-Purpose Environments, Part 2)</title><link>https://mende.io/blog/the-importance-of-an-engineering-vision-high-purpose-environments-part-2/</link><pubDate>Sat, 13 May 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-importance-of-an-engineering-vision-high-purpose-environments-part-2/</guid><description>&lt;h1 id="the-importance-of-an-engineering-vision-high-purpose-environments-part-2">The Importance of an Engineering Vision (High-Purpose Environments, Part 2)&lt;/h1>
&lt;p>Have you ever seen organizations and teams spinning in circles, having endless discussions, and never seeming able to make progress? Have you witnessed environments where every decision was made by &lt;em>a leader&lt;/em> in the hierarchical sense? Or even worse, by someone able to exert a specific power and overrule others?&lt;/p></description></item><item><title>Creating High-Purpose Environments (High-Purpose Environments, Part 1)</title><link>https://mende.io/blog/creating-high-purpose-environments-high-purpose-environments-part-1/</link><pubDate>Sat, 06 May 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/creating-high-purpose-environments-high-purpose-environments-part-1/</guid><description>&lt;h1 id="creating-high-purpose-environments-high-purpose-environments-part-1">Creating High-Purpose Environments (High-Purpose Environments, Part 1)&lt;/h1>
&lt;p>High-purpose environments are cultural spaces that inspire, motivate, and empower individuals to work toward a common goal. A strong sense of purpose, clear values, and a commitment to continuous growth and improvement characterize these environments.&lt;/p></description></item><item><title>Default-to-Open: A Principle for High-Performance Organizations</title><link>https://mende.io/blog/default-to-open-a-principle-for-high-performance-organizations/</link><pubDate>Sat, 22 Apr 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/default-to-open-a-principle-for-high-performance-organizations/</guid><description>&lt;h1 id="default-to-open-a-principle-for-high-performance-organizations">Default-to-Open: A Principle for High-Performance Organizations&lt;/h1>
&lt;p>Sharing, communicating, and persisting knowledge, information, and decisions is a challenge that most companies have. This challenge may become even bigger in remote-first companies.&lt;/p></description></item><item><title>The Inverse Conway Manoeuvre in Existing Systems – It does not work!</title><link>https://mende.io/blog/the-inverse-conway-manoeuvre-in-existing-systems/</link><pubDate>Sat, 15 Apr 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-inverse-conway-manoeuvre-in-existing-systems/</guid><description>&lt;h1 id="the-inverse-conway-manoeuvre-in-existing-systems--it-does-not-work">The Inverse Conway Manoeuvre in Existing Systems – It does not work!&lt;/h1>
&lt;p>In 1968, Melvin E. Conway postulated a &lt;em>law&lt;/em> about a connection between organizational design and system structure, which got pretty famous. The paper has the title “&lt;a href="http://www.melconway.com/Home/Committees%5FPaper.html">How Do Committees Invent?&lt;/a>” and the &lt;em>law&lt;/em> goes as follows:&lt;/p></description></item><item><title>Happy without hierarchies: Who cares for employee happiness if there are no hierarchies?</title><link>https://mende.io/blog/happy-without-hierarchies/</link><pubDate>Sat, 04 Mar 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/happy-without-hierarchies/</guid><description>&lt;h1 id="happy-without-hierarchies-who-cares-for-employee-happiness-if-there-are-no-hierarchies">Happy without hierarchies: Who cares for employee happiness if there are no hierarchies?&lt;/h1>
&lt;p>Working with different clients has the benefit of discovering many contexts and with that, different perspectives, observations, and questions.&lt;/p></description></item><item><title>The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance</title><link>https://mende.io/blog/the-benefits-of-remote-work-for-developer-teams-increased-productivity-and-better-work-life-balance/</link><pubDate>Sat, 18 Feb 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-benefits-of-remote-work-for-developer-teams-increased-productivity-and-better-work-life-balance/</guid><description>&lt;h1 id="the-benefits-of-remote-work-for-developer-teams-increased-productivity-and-better-work-life-balance">The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance&lt;/h1>
&lt;p>In today’s fast-paced and constantly changing world, many organisations are rethinking traditional work arrangements and embracing the benefits of remote work.&lt;/p></description></item><item><title>The Importance of Developer Productivity in a Recession</title><link>https://mende.io/blog/importance-of-developer-productivity/</link><pubDate>Sat, 26 Nov 2022 13:30:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/importance-of-developer-productivity/</guid><description>&lt;h1 id="the-importance-of-developer-productivity-in-a-recession">The Importance of Developer Productivity in a Recession&lt;/h1>
&lt;p>When times get rough, companies and investors get more cautious with how they spend and invest their money. Many companies reduce their spending on employees and salaries by laying off large numbers of people.&lt;/p></description></item><item><title>From two manual monolithic deployments a week to 15+ automated deployments a day</title><link>https://mende.io/blog/continuous-deployment-for-the-entire-organisation/</link><pubDate>Sat, 11 Jun 2022 13:18:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/continuous-deployment-for-the-entire-organisation/</guid><description>&lt;h1 id="from-two-manual-monolithic-deployments-a-week-to-15-automated-deployments-a-day">From two manual monolithic deployments a week to 15+ automated deployments a day&lt;/h1>
&lt;p>We did it. Roughly two years after I joined BRYTER and one year after we started the developer experience team, we finally ended the era of manual deployments for roughly 15 teams.&lt;/p></description></item><item><title>Interaction modes of a developer experience team</title><link>https://mende.io/blog/developer-experience-team-interaction-modes/</link><pubDate>Sat, 26 Mar 2022 13:10:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/developer-experience-team-interaction-modes/</guid><description>&lt;h1 id="interaction-modes-of-a-developer-experience-team">Interaction modes of a developer experience team&lt;/h1>
&lt;p>In my &lt;a href="https://mende.io/blog/developer-experience-team-shape/">last article&lt;/a>, I wrote about how we shaped our developer experience team and why we decided for this team constellation. In this article, I will focus on how this team interacts with the other software development teams and which aspects are particularly important.&lt;/p></description></item><item><title>Shaping developer experience teams for autonomy</title><link>https://mende.io/blog/developer-experience-team-shape/</link><pubDate>Sat, 19 Mar 2022 13:08:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/developer-experience-team-shape/</guid><description>&lt;h1 id="shaping-developer-experience-teams-for-autonomy">Shaping developer experience teams for autonomy&lt;/h1>
&lt;p>Once you have decided, that a developer experience team would provide value to your organisation, the question is, how such a team should be set up, how it should be shaped, and how it should interact with other teams.&lt;/p></description></item><item><title>Why a developer experience team can help your company</title><link>https://mende.io/blog/why-a-devex-team-can-help/</link><pubDate>Sat, 12 Mar 2022 13:05:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/why-a-devex-team-can-help/</guid><description>&lt;h1 id="why-a-developer-experience-team-can-help-your-company">Why a developer experience team can help your company&lt;/h1>
&lt;p>Great developer experience is directly linked to great developer productivity and an important factor for company success. Therefore, as explained in my &lt;a href="https://mende.io/blog/care-about-developer-experience/">last articles&lt;/a>, companies should care and attempt to improve developer experience.&lt;/p></description></item><item><title>Code ownership conflicts as a signal for structural mismatch</title><link>https://mende.io/blog/code-ownership-conflicts/</link><pubDate>Sat, 19 Feb 2022 12:54:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/code-ownership-conflicts/</guid><description>&lt;h1 id="code-ownership-conflicts-as-a-signal-for-structural-mismatch">Code ownership conflicts as a signal for structural mismatch&lt;/h1>
&lt;p>In my &lt;a href="https://mende.io/blog/code-ownership/">last article&lt;/a>, I explained why I believe that individual code ownership is bad and why weak code ownership on a cross-team level can be highly beneficial.&lt;/p></description></item><item><title>Code Ownership: Keeping the balance between structure and agility</title><link>https://mende.io/blog/code-ownership/</link><pubDate>Sat, 12 Feb 2022 12:53:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/code-ownership/</guid><description>&lt;h1 id="code-ownership-keeping-the-balance-between-structure-and-agility">Code Ownership: Keeping the balance between structure and agility&lt;/h1>
&lt;p>Code ownership is an important topic when it comes to enabling your teams and allowing developers to improve the system while keeping the overhead of changes low.&lt;/p></description></item><item><title>A platform team for next-level developer experience</title><link>https://mende.io/blog/developer-experience-platform-team/</link><pubDate>Sat, 05 Feb 2022 12:49:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/developer-experience-platform-team/</guid><description>&lt;h1 id="a-platform-team-for-next-level-developer-experience">A platform team for next-level developer experience&lt;/h1>
&lt;p>In this article, I am sharing my experience (and opinions) of how a platform team should be set up to provide great developer experience for other development teams.&lt;/p></description></item><item><title>Remote can be synchronous, too!</title><link>https://mende.io/blog/remote-can-be-synchronous-too/</link><pubDate>Sat, 29 Jan 2022 12:47:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/remote-can-be-synchronous-too/</guid><description>&lt;h1 id="remote-can-be-synchronous-too">Remote can be synchronous, too!&lt;/h1>
&lt;p>When speaking with different people about their reasons for moving back to office-work or about their concerns about remote work, it often boils down to that they do not believe, that &lt;em>asynchronous&lt;/em> works.&lt;/p></description></item><item><title>OKRs are NOT guaranteed deliveries</title><link>https://mende.io/blog/okrs-are-not-guaranteed-deliveries/</link><pubDate>Sat, 22 Jan 2022 12:44:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/okrs-are-not-guaranteed-deliveries/</guid><description>&lt;h1 id="okrs-are-not-guaranteed-deliveries">OKRs are NOT guaranteed deliveries&lt;/h1>
&lt;p>Objectives and key results are a great tool for collaborative goal-setting and for aligned on a company-wide direction. While the key objectives or north-stars might be handed down from C-level management, the concrete objectives and key-results are discovered by the teams. Only they know best, how to achieve the bigger goals of the company. Thus, all teams needs to figure out, how they can best contribute to the company goals.&lt;/p></description></item><item><title>Bonuses are bad – change my mind</title><link>https://mende.io/blog/bonuses-are-bad/</link><pubDate>Sat, 08 Jan 2022 12:39:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/bonuses-are-bad/</guid><description>&lt;h1 id="bonuses-are-bad--change-my-mind">Bonuses are bad – change my mind&lt;/h1>
&lt;p>Compensation is a difficult topic. And depending on the domain and type of work, various models can make sense. Many companies rely on bonuses based on performance, ranking, or commission. Those bonuses usually revolve around clear goals or metrics that can be measured, such as finishing a project in time or closing deals with a certain total valuation.&lt;/p></description></item><item><title>Why teams need slack – not the tool</title><link>https://mende.io/blog/why-teams-need-slack/</link><pubDate>Sat, 01 Jan 2022 12:37:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/why-teams-need-slack/</guid><description>&lt;h1 id="why-teams-need-slack--not-the-tool">Why teams need slack – not the tool&lt;/h1>
&lt;p>At BRYTER, we were hiring a lot. Therefore, we were of course also discussing how many people of which profession we really need. While &lt;em>management&lt;/em> trusted us completely to make the right decisions here, sometimes I encountered that other people were afraid, that we hire people who are not 100% busy.&lt;/p></description></item><item><title>Adopting Continuous Delivery: More a culture change than automation of processes</title><link>https://mende.io/blog/adopting-continous-delivery-culture/</link><pubDate>Sat, 04 Dec 2021 12:07:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/adopting-continous-delivery-culture/</guid><description>&lt;h1 id="adopting-continuous-delivery-more-a-culture-change-than-automation-of-processes">Adopting Continuous Delivery: More a culture change than automation of processes&lt;/h1>
&lt;p>Continuous delivery, the process of automatically delivering changes of a system without human interaction, is one of the most beneficial practices that software teams can adopt. In &lt;a href="https://www.goodreads.com/en/book/show/35747076-accelerate">Accelerate&lt;/a>, the authors Nicole Forsgren, Jez Humble and Gene Kim, discovered a strong link between using continuous delivery and organisational performance: Teams that continuously deliver their changes have a stronger sense of ownership, get faster feedback and need to rework their code less. Furthermore, deployments are less stressful and the risk of burnout is reduced.&lt;/p></description></item><item><title>Do you have walls in your deployment process?</title><link>https://mende.io/blog/deployment-process-walls/</link><pubDate>Sat, 20 Nov 2021 11:59:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/deployment-process-walls/</guid><description>&lt;h1 id="do-you-have-walls-in-your-deployment-process">Do you have walls in your deployment process?&lt;/h1>
&lt;p>Enabling units to quickly deploy and release new features to their customers is one of the goals of &lt;a href="https://mende.io/blog/cross-functional-units-uni-functional-teams/">cross-functional units&lt;/a> and the “you build it, you run it” DevOps mentality.&lt;/p></description></item><item><title>Just care less about not being aligned</title><link>https://mende.io/blog/just-care-less-about-not-being-aligned/</link><pubDate>Sat, 06 Nov 2021 10:12:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/just-care-less-about-not-being-aligned/</guid><description>&lt;h1 id="just-care-less-about-not-being-aligned">Just care less about not being aligned&lt;/h1>
&lt;p>If you work in a company that is aiming for fast growth, being overly aligned will slow you down as the number of stakeholders increases. If every time I want to introduce a new linting rule I would need to agree with 55 other developers, I will likely not do it. Instead of forcing all units to use the same tech stack, the same code style, the same testing framework and so on, we need to learn to &lt;em>just care less&lt;/em>. Of course, the ability to care less depends on the architecture and the company structure. In a monolithic application, it is far more difficult to reduce the impact of units on each other, than in an environment of properly structured microservices. Thus, the goal is to identify and create structures that allow you to care less about alignment. The entire idea of cross-functional units is aiming for units to be independent. This is achieved by having units own vertical slices of the system completely, which reduces the need for alignment with other units to a minimum. However, sometimes even cross-functional units can influence each other because of technical dependencies or suboptimal structuring of these units.&lt;/p></description></item><item><title>Cross-functional units and uni-functional teams</title><link>https://mende.io/blog/cross-functional-units-uni-functional-teams/</link><pubDate>Fri, 29 Oct 2021 09:08:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/cross-functional-units-uni-functional-teams/</guid><description>&lt;h1 id="cross-functional-units-and-uni-functional-teams">Cross-functional units and uni-functional teams&lt;/h1>
&lt;p>Many modern companies put a high emphasis on having multiple functions within one unit or team. The goal: The unit should be able to function with a high degree of autonomy, working on its area and owning everything in this area from beginning to end.&lt;/p></description></item></channel></rss>