<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tobi(as Mende)</title><link>https://mende.io/</link><description>Recent content 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, 30 Jan 2026 05:00:00 +0000</lastBuildDate><atom:link href="https://mende.io/index.xml" rel="self" type="application/rss+xml"/><item><title>The 5 Processes Every Business Should Automate First</title><link>https://mende.io/blog/the-5-processes-every-business-should-automate-first/</link><pubDate>Fri, 30 Jan 2026 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-5-processes-every-business-should-automate-first/</guid><description>&lt;h1 id="the-5-processes-every-business-should-automate-first">The 5 Processes Every Business Should Automate First&lt;/h1>
&lt;p>Most businesses I work with know they should automate more. They have heard the promises. They might even have an n8n instance running somewhere with one or two small workflows that someone set up a while ago.&lt;/p></description></item><item><title>AI Made Me 10x More Productive – Now What?</title><link>https://mende.io/blog/ai-made-me-10x-more-productive-now-what/</link><pubDate>Fri, 05 Dec 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/ai-made-me-10x-more-productive-now-what/</guid><description>&lt;h2 id="thoughts-on-ai-productivity-and-what-we-should-do-differently">Thoughts on AI, Productivity, and What We Should Do Differently&lt;/h2>
&lt;p>In the last couple of months, I got to use Claude code a lot for software development, and I am at a point with it, where it gives me consistently high-quality results at incredible speed. In 99.5% of all cases, I get the results that I expect/desire. In other areas of my life, (other) AI tools have a drastic influence on my productivity and (sometimes) even my ability to do certain things, too.&lt;/p></description></item><item><title>Building Diving Nomads in Public Part 3</title><link>https://mende.io/blog/building-diving-nomads-in-public-part-3/</link><pubDate>Fri, 31 Oct 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/building-diving-nomads-in-public-part-3/</guid><description>&lt;h1 id="building-in-public--part-3-how-we-built-the-diving-nomads-partner-map">Building in Public – Part 3: How We built the Diving Nomads Partner Map&lt;/h1>
&lt;p>This is part three of the &lt;em>Building Diving Nomads in Public&lt;/em> series.&lt;/p>
&lt;p>After sharing &lt;a href="https://tidbits.mende.io/p/building-in-public-part-2">how we automated outreach for dive centers and coliving / coworking partners&lt;/a>, this chapter is about the thing people actually use – our &lt;strong>Partner Map&lt;/strong>.&lt;/p></description></item><item><title>Building in Public: How Diving Nomads Automates Coliving &amp; Coworking Partner Outreach</title><link>https://mende.io/blog/building-diving-nomads-in-public-part-2/</link><pubDate>Fri, 29 Aug 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/building-diving-nomads-in-public-part-2/</guid><description>&lt;p>At &lt;strong>Diving Nomads&lt;/strong>, we’re building something special for digital nomads who love scuba diving. Our mission is to make it easy for them to find great places to work, live, and dive — without having to choose between beautiful dive spots and solid remote work setups.&lt;/p></description></item><item><title>Building Diving Nomads in Public Part 1</title><link>https://mende.io/blog/building-diving-nomads-in-public-part-1/</link><pubDate>Fri, 25 Jul 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/building-diving-nomads-in-public-part-1/</guid><description>&lt;h1 id="building-diving-nomads-in-public-how-we-onboard-dive-centers-and-automate-memberships-with-almost-no-code">Building Diving Nomads in Public: How We Onboard Dive Centers and Automate Memberships with (Almost) No Code&lt;/h1>
&lt;blockquote>
&lt;p>&lt;strong>TL;DR&lt;/strong>&lt;br>
We&amp;rsquo;re building a platform for digital nomads with a passion for scuba diving. Our lean, automation-first tech stack allows us to move fast, deliver value early, and maybe inspire other early-stage founders to rethink how they build.&lt;/p></description></item><item><title>Transforming Developer Experience: Lessons from Building a Platform Team</title><link>https://mende.io/talks/transforming-developer-experience/</link><pubDate>Thu, 10 Jul 2025 00:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/talks/transforming-developer-experience/</guid><description>&lt;p>Creating a superior developer experience is key to motivating and streamlining engineering teams, serving as a strategic pillar for business success. Focus areas include optimizing workflow, reducing cognitive load, and establishing efficient feedback loops. As technology grows more complex, achieving these becomes increasingly challenging.&lt;/p></description></item><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>Making Better Decisions – How we can decide better together.</title><link>https://mende.io/talks/making-better-decisions/</link><pubDate>Thu, 19 Jun 2025 00:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/talks/making-better-decisions/</guid><description>&lt;p>With the number of daily decisions increasing significantly over the past ten years, effective decision-making is crucial. Decisions need to be made as fast and as good as possible. This talk focuses on the value of collaborative decision-making, highlighting benefits such as improved problem-solving through diverse perspectives and enhanced commitment from team members. We will explore various group decision-making methods supported by real-world examples.&lt;/p></description></item><item><title>Why Delegation Fails – and What to Do About It</title><link>https://mende.io/blog/why-delegation-fails/</link><pubDate>Fri, 30 May 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/why-delegation-fails/</guid><description>&lt;blockquote>
&lt;p>&amp;ldquo;You don’t have a delegation problem. You have a clarity and trust problem.&amp;rdquo;&lt;/p>
&lt;/blockquote>
&lt;p>I used to think I was helping my team by staying involved. Answering every question. Checking every detail. In reality, I was slowing everyone down – including myself.&lt;/p></description></item><item><title>From OK-ish to Outstanding – How any team can become a high-performing one.</title><link>https://mende.io/talks/from-ok-ish-to-outstanding/</link><pubDate>Wed, 21 May 2025 00:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/talks/from-ok-ish-to-outstanding/</guid><description>&lt;p>Most software engineering teams operate far below their capabilities. They perform okay, good enough, or average. But what if any team can reach higher productivity, joy, and excellence?&lt;/p>
&lt;p>In this session, we will discover why most teams do not use their full potential and what every one of us can do to lead our teams toward high performance and engineering excellence.&lt;/p></description></item><item><title>Being the Leader Your Team Actually Wants to Follow</title><link>https://mende.io/blog/leader-your-team-actually-follows/</link><pubDate>Sat, 26 Apr 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/leader-your-team-actually-follows/</guid><description>&lt;p>There’s no shortage of leadership advice out there. Everyone has a framework, a matrix, or a magic quadrant. And honestly? Most of it feels disconnected from the messy, real-world challenges of building a company – especially when your team is growing, priorities are shifting weekly, and you&amp;rsquo;re just trying to keep your calendar from eating you alive.&lt;/p></description></item><item><title>Deciding Better in Organizations</title><link>https://mende.io/blog/deciding-better-in-organizations/</link><pubDate>Sat, 29 Mar 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/deciding-better-in-organizations/</guid><description>&lt;h1 id="deciding-better-how-to-make-faster-smarter-and-more-effective-decisions-in-your-organization">Deciding Better: How to Make Faster, Smarter, and More Effective Decisions in Your Organization&lt;/h1>
&lt;p>The quality of your decisions influences the quality of your life. The quality of the decisions in your organization determines your company’s future.&lt;/p></description></item><item><title>The Leadership Dilemma – When Times Change and Generations Collide</title><link>https://mende.io/blog/the-leadership-dilemma/</link><pubDate>Sat, 01 Mar 2025 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-leadership-dilemma/</guid><description>&lt;h1 id="the-leadership-dilemma--when-times-change-and-generations-collide">The Leadership Dilemma – When Times Change and Generations Collide&lt;/h1>
&lt;p>Your leadership style is heavily influenced by the leadership you have experienced yourself. The way how you run and build a company is the result of the companies you have worked in, your experiences, and your considerations.&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>From Code to Customer – How Continuous Deployment can Accelerate Your Software Development Cycle</title><link>https://mende.io/talks/from-code-to-customer/</link><pubDate>Thu, 17 Oct 2024 00:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/talks/from-code-to-customer/</guid><description>&lt;p>Many organizations struggle with streamlining the software delivery process, resulting in slower delivery, lower quality, and decreased customer satisfaction. They also face challenges in establishing efficient CD pipelines and implementing cultural changes necessary for successful CD implementation.&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>Don’t motivate people</title><link>https://mende.io/blog/dont-motivate-people/</link><pubDate>Sat, 24 Aug 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/dont-motivate-people/</guid><description>&lt;h1 id="dont-motivate-people">Don’t motivate people&lt;/h1>
&lt;p>Now and then, when working with leaders, I get the question of how they could motivate their people. From their perspective, their people seem not motivated, not driven enough to bring the results they want to see.&lt;/p></description></item><item><title>How to give outstanding code reviews (if you have to)</title><link>https://mende.io/blog/how-to-give-outstanding-code-reviews-if-you-have-to/</link><pubDate>Sat, 20 Jul 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/how-to-give-outstanding-code-reviews-if-you-have-to/</guid><description>&lt;h1 id="how-to-give-outstanding-code-reviews-if-you-have-to">How to give outstanding code reviews (if you have to)&lt;/h1>
&lt;p>Most software companies use code reviews to ensure that at least two people check each part of the code base and maintain its quality. Although I prefer pair or team programming over asynchronous code reviews, I recognize that this isn’t always possible. In such cases, asynchronous code reviews are the next best option.&lt;/p></description></item><item><title>Increase Engineering Productivity by 50% Through Focus and Flow</title><link>https://mende.io/blog/increase-engineering-productivity-by-50-through-focus-and-flow/</link><pubDate>Sat, 01 Jun 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/increase-engineering-productivity-by-50-through-focus-and-flow/</guid><description>&lt;h1 id="increase-engineering-productivity-by-50-through-focus-and-flow">Increase Engineering Productivity by 50% Through Focus and Flow&lt;/h1>
&lt;p>Creating an environment where developers can maintain focus and achieve flow can lead to a 50% increase in productivity, &lt;a href="https://queue.acm.org/detail.cfm?id=3639443">as research suggests&lt;/a>. But how do we create such an environment?&lt;/p></description></item><item><title>Value-Stream-Oriented Kanban</title><link>https://mende.io/blog/value-stream-oriented-kanban/</link><pubDate>Sat, 20 Apr 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/value-stream-oriented-kanban/</guid><description>&lt;h1 id="value-stream-oriented-kanban">Value-Stream-Oriented Kanban&lt;/h1>
&lt;p>Many teams, especially in the startup environment, move away from Scrum and use a leaner Kanban-based approach. This is a good thing. I don’t think Scrum is a suitable framework for modern, fast, agile companies. – Especially not in the SaaS field (the reasoning behind this statement will become another article, eventually).&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>11 Aspects Most Startups Get Wrong About OKRs and How to Fix it</title><link>https://mende.io/blog/11-aspects-most-startups-get-wrong-about-okrs-and-how-to-fix-it/</link><pubDate>Sat, 24 Feb 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/11-aspects-most-startups-get-wrong-about-okrs-and-how-to-fix-it/</guid><description>&lt;h1 id="11-aspects-most-startups-get-wrong-about-okrs-and-how-to-fix-it">11 Aspects Most Startups Get Wrong About OKRs and How to Fix it&lt;/h1>
&lt;p>Objectives and key results (OKRs) can be a powerful tool. But as with any framework or methodology out there, just applying it as others do will likely not yield the best results. It can even harm your organization.&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>Cutting through the noise – becoming myself again</title><link>https://mende.io/blog/cutting-through-the-noise-becoming-myself-again/</link><pubDate>Sat, 13 Jan 2024 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/cutting-through-the-noise-becoming-myself-again/</guid><description>&lt;h1 id="cutting-through-the-noise--becoming-myself-again">Cutting through the noise – becoming myself again&lt;/h1>
&lt;p>In the last two years, I got tons of advice about how to start my own business, how to find clients, how to market myself, how much to charge, how to position myself, … you name it.&lt;/p></description></item><item><title>May the LLM be with You – On Planes and German Trains</title><link>https://mende.io/blog/may-the-llm-be-with-you-on-planes-and-german-trains/</link><pubDate>Sat, 30 Dec 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/may-the-llm-be-with-you-on-planes-and-german-trains/</guid><description>&lt;h1 id="may-the-llm-be-with-you--on-planes-and-german-trains">May the LLM be with You – On Planes and German Trains&lt;/h1>
&lt;p>This might be the unofficial seventh part of the “&lt;a href="https://mende.io/blog/tag/ai-for-devex/">AI for DevEx&lt;/a>” series. LLM tools are a great help during the entire software development process. But what if we are offline or if data privacy concerns disallow using ChatGPT and similar tools?&lt;/p></description></item><item><title>LLMs for General Productivity Improvements (AI for DevEx, Part 6)</title><link>https://mende.io/blog/llms-for-general-productivity-improvements-ai-for-devex-part-6/</link><pubDate>Sat, 23 Dec 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/llms-for-general-productivity-improvements-ai-for-devex-part-6/</guid><description>&lt;h1 id="llms-for-general-productivity-improvements-ai-for-devex-part-6">LLMs for General Productivity Improvements (AI for DevEx, Part 6)&lt;/h1>
&lt;p>Welcome to part 6 of &lt;a href="https://mende.io/blog/tag/ai-for-devex/">AI for DevEx&lt;/a>. In this last part of the series, I will give some inspiration on how AI, namely LLMs, can help engineers with their everyday tasks.&lt;/p></description></item><item><title>What AI Tools Mean for Deployment, Operations and Security (AI for DevEx, Part 5)</title><link>https://mende.io/blog/what-ai-tools-mean-for-deployment-operations-and-security-ai-for-devex-part-5/</link><pubDate>Sat, 16 Dec 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/what-ai-tools-mean-for-deployment-operations-and-security-ai-for-devex-part-5/</guid><description>&lt;h1 id="what-ai-tools-mean-for-deployment-operations-and-security-ai-for-devex-part-5">What AI Tools Mean for Deployment, Operations and Security (AI for DevEx, Part 5)&lt;/h1>
&lt;p>Welcome back to &lt;a href="https://mende.io/blog/tag/ai-for-devex/">AI for DevEx&lt;/a>, Part 5. In the last part, we explored how AI tools can &lt;a href="https://nudge.unblocked.engineering/p/how-ai-improves-collaboration-and">help us to improve our collaboration and communication&lt;/a>. Today, we’re focusing on an often ignored aspect of software engineering: the importance of deployment, operation, monitoring, and security for teams that manage their software from creation to running it in production. Terms like DevOps, DevSecOps, and Dev&lt;!-- raw HTML omitted -->Ops have been created to emphasize the need for teams to own their software completely.&lt;/p></description></item><item><title>How AI Improves Collaboration and Communication (AI for DevEx, Part 4)</title><link>https://mende.io/blog/how-ai-improves-collaboration-and-communication-ai-for-devex-part-4/</link><pubDate>Sat, 09 Dec 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/how-ai-improves-collaboration-and-communication-ai-for-devex-part-4/</guid><description>&lt;h1 id="how-ai-improves-collaboration-and-communication-ai-for-devex-part-4">How AI Improves Collaboration and Communication (AI for DevEx, Part 4)&lt;/h1>
&lt;p>Welcome to part 4 of &lt;a href="https://mende.io/blog/tag/ai-for-devex/">AI for DevEx&lt;/a>. In this article, we will explore how AI can help us improve how we communicate synchronously and asynchronously, how we collaborate, and how it can even increase the value of documentation.&lt;/p></description></item><item><title>How Testing and Quality Assurance Change Through AI (AI for DevEx, Part 3)</title><link>https://mende.io/blog/how-testing-and-quality-assurance-change-through-ai-ai-for-devex-part-3/</link><pubDate>Sat, 02 Dec 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/how-testing-and-quality-assurance-change-through-ai-ai-for-devex-part-3/</guid><description>&lt;h1 id="how-testing-and-quality-assurance-change-through-ai-ai-for-devex-part-3">How Testing and Quality Assurance Change Through AI (AI for DevEx, Part 3)&lt;/h1>
&lt;p>Part 3 of the &lt;a href="https://mende.io/blog/tag/ai-for-devex/">AI for DevEx series&lt;/a> examines testing and quality assurance. It builds on &lt;a href="https://nudge.unblocked.engineering/p/writing-and-improving-code-with-ai">Part 1&lt;/a>, where we saw how AI and Large Language Models can assist in coding. We focused on how AI can generate test cases for unit and integration tests there.&lt;/p></description></item><item><title>Custom GPTs as a Developer Companion (AI for DevEx, Part 2)</title><link>https://mende.io/blog/custom-gpts-as-a-developer-companion-ai-for-devex-part-2/</link><pubDate>Sat, 25 Nov 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/custom-gpts-as-a-developer-companion-ai-for-devex-part-2/</guid><description>&lt;h1 id="custom-gpts-as-a-developer-companion-ai-for-devex-part-2">Custom GPTs as a Developer Companion (AI for DevEx, Part 2)&lt;/h1>
&lt;p>Part 2 of “AI for DevEx” focuses on the new GPTs announced by OpenAI on November 6th and how they can enhance the experience for developers.&lt;/p></description></item><item><title>Writing and Improving Code with AI (AI for DevEx, Part 1)</title><link>https://mende.io/blog/writing-and-improving-code-with-ai-ai-for-devex-part-1/</link><pubDate>Sat, 18 Nov 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/writing-and-improving-code-with-ai-ai-for-devex-part-1/</guid><description>&lt;h1 id="writing-and-improving-code-with-ai-ai-for-devex-part-1">Writing and Improving Code with AI (AI for DevEx, Part 1)&lt;/h1>
&lt;p>Artificial intelligence (AI) is here to stay. It’s become a part of our daily lives through ChatGPT, Midjourney, or even the occasional frustrating chatbot. Despite their imperfections and the mix of risks and opportunities they present, AI tools are transforming the way we create, manage, and improve software.&lt;/p></description></item><item><title>Collaboration for Introverts: The Myth of the solo-working Introvert</title><link>https://mende.io/blog/collaboration-for-introverts-the-myth-of-the-solo-working-introvert/</link><pubDate>Sat, 11 Nov 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/collaboration-for-introverts-the-myth-of-the-solo-working-introvert/</guid><description>&lt;h1 id="collaboration-for-introverts-the-myth-of-the-solo-working-introvert">Collaboration for Introverts: The Myth of the solo-working Introvert&lt;/h1>
&lt;p>Almost all the teams I met throughout my career were collaborating too little. Productivity, quality, alignment, and the feeling of belonging rose in every team where we increased the amount of collaboration.&lt;/p></description></item><item><title>Benefits of Collaboration</title><link>https://mende.io/blog/benefits-of-collaboration/</link><pubDate>Sat, 04 Nov 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/benefits-of-collaboration/</guid><description>&lt;h1 id="benefits-of-collaboration">Benefits of Collaboration&lt;/h1>
&lt;p>In my career, I’ve seen many “teams” that mainly collaborate only when the work gets tough or if someone has been stuck for days. In these cases, teamwork is more of an exception than a regular practice. This approach is backward. Collaboration should be the standard way of working, and we should only choose to work independently for good reasons.&lt;/p></description></item><item><title>How outstanding teams form without team-building exercises</title><link>https://mende.io/blog/how-outstanding-teams-form-without-team-building-exercises/</link><pubDate>Sat, 28 Oct 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/how-outstanding-teams-form-without-team-building-exercises/</guid><description>&lt;h1 id="how-outstanding-teams-form-without-team-building-exercises">How outstanding teams form without team-building exercises&lt;/h1>
&lt;p>Building outstanding and high-performing teams is the dream of every engineering leader. But how do you do it? And how do you do it when people work remotely, and getting everybody to the same place is difficult and costly?&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>Why We Need to Stop Measuring (Developer) Productivity — Part 2</title><link>https://mende.io/blog/why-we-need-to-stop-measuring-developer-productivity-part-2/</link><pubDate>Sat, 23 Sep 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/why-we-need-to-stop-measuring-developer-productivity-part-2/</guid><description>&lt;h1 id="why-we-need-to-stop-measuring-developer-productivity--part-2">Why We Need to Stop Measuring (Developer) Productivity — Part 2&lt;/h1>
&lt;p>This is part two of my article on measuring developer productivity. In &lt;a href="https://devexnuggets.substack.com/p/why-we-need-to-stop-measuring-developer">part one&lt;/a>, we discussed the dangers of measuring productivity in general and why the need for productivity metrics for management and leadership is based on flawed assumptions.&lt;/p></description></item><item><title>How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments</title><link>https://mende.io/blog/how-bryter-achieved-increased-developer-experience-ownership-product-quality-and-engineering-effectiveness-through-continuous-deployments/</link><pubDate>Fri, 22 Sep 2023 08:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/how-bryter-achieved-increased-developer-experience-ownership-product-quality-and-engineering-effectiveness-through-continuous-deployments/</guid><description>&lt;h1 id="how-bryter-achieved-increased-developer-experience-ownership-product-quality-and-engineering-effectiveness-through-continuous-deployments">How BRYTER Achieved Increased Developer Experience, Ownership, Product Quality, and Engineering Effectiveness through Continuous Deployments&lt;/h1>
&lt;p>BRYTER, a German LegalTech scale-up, faced challenges with its monolithic deployment process and limited understanding of the deployment process within its engineering teams. Deployments occurred only twice a week and were managed by the QA team, leading to a lack of visibility and ownership among the other teams.&lt;/p></description></item><item><title>Why We Need to Stop Measuring (Developer) Productivity — Part 1</title><link>https://mende.io/blog/why-we-need-to-stop-measuring-developer-productivity-part-1/</link><pubDate>Sat, 16 Sep 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/why-we-need-to-stop-measuring-developer-productivity-part-1/</guid><description>&lt;h1 id="why-we-need-to-stop-measuring-developer-productivity--part-1">Why We Need to Stop Measuring (Developer) Productivity — Part 1&lt;/h1>
&lt;p>Leaders are obsessed with productivity metrics. This is at least true for leaders who learned to lead in the last century. The ones that follow a command-and-control or carrots-and-sticks leadership approach. They need to measure each department individually to make the right decisions top-down.&lt;/p></description></item><item><title>Company Culture determines Product Quality</title><link>https://mende.io/blog/company-culture-determines-product-quality/</link><pubDate>Sat, 09 Sep 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/company-culture-determines-product-quality/</guid><description>&lt;h1 id="company-culture-determines-product-quality">Company Culture determines Product Quality&lt;/h1>
&lt;p>You have probably heard the claim that improving developer experience and company culture will lead to higher product quality and satisfied customers.&lt;/p>
&lt;ul>
&lt;li>But is this true?&lt;/li>
&lt;li>How are company culture and product quality related?&lt;/li>
&lt;li>Are product quality and customer satisfaction side effects of a great company culture?&lt;/li>
&lt;/ul>
&lt;p>While it would most likely go too far to call customer satisfaction a side effect of great company culture, the connection between company culture and product quality is more substantial than you might expect.&lt;/p></description></item><item><title>Improving Developer Experience, Level 4: Optimizing Feedback Loops: Tools, Tests, and Teamwork</title><link>https://mende.io/blog/improving-developer-experience-level-4-optimizing-feedback-loops-tools-tests-and-teamwork/</link><pubDate>Sat, 02 Sep 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/improving-developer-experience-level-4-optimizing-feedback-loops-tools-tests-and-teamwork/</guid><description>&lt;h1 id="improving-developer-experience-level-4-optimizing-feedback-loops-tools-tests-and-teamwork">Improving Developer Experience, Level 4: Optimizing Feedback Loops: Tools, Tests, and Teamwork&lt;/h1>
&lt;p>&lt;a href="https://mende.io/blog/improving-developer-experience-level-3-the-triad-of-clarity-focus-and-flow/">Last week&lt;/a>, we dove into focus, clarity, and flow. Today, we will delve into the top layer of &lt;a href="https://mende.io/blog/maslows-hierarchy-of-needs-devex-edition/">Maslow’s Hierarchy of Needs (DevEx Edition)&lt;/a>. Here, it gets a bit technical. While the three bottom layers are mostly concerned with culture, structures, and processes, the top layer includes technical and cultural aspects. This shows how important and foundational non-technical aspects are for outstanding developer experience.&lt;/p></description></item><item><title>Improving Developer Experience, Level 3: The Triad of Clarity, Focus, and Flow</title><link>https://mende.io/blog/improving-developer-experience-level-3-the-triad-of-clarity-focus-and-flow/</link><pubDate>Sat, 26 Aug 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/improving-developer-experience-level-3-the-triad-of-clarity-focus-and-flow/</guid><description>&lt;h1 id="improving-developer-experience-level-3-the-triad-of-clarity-focus-and-flow">Improving Developer Experience, Level 3: The Triad of Clarity, Focus, and Flow&lt;/h1>
&lt;p>Last week, we delved deep into “&lt;a href="https://mende.io/blog/improving-developer-experience-level-2-belonging-collaboration-and-communication/">Belonging, Collaboration, and Communication&lt;/a>“. Further up in the &lt;a href="https://mende.io/blog/maslows-hierarchy-of-needs-devex-edition/">Maslow Pyramid of DevEx&lt;/a>, we have the factors that affect focus, clarity, and flow. This article will explore how we can improve those factors.&lt;/p></description></item><item><title>Improving Developer Experience, Level 2: Belonging, Collaboration, and Communication</title><link>https://mende.io/blog/improving-developer-experience-level-2-belonging-collaboration-and-communication/</link><pubDate>Sat, 19 Aug 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/improving-developer-experience-level-2-belonging-collaboration-and-communication/</guid><description>&lt;h1 id="improving-developer-experience-level-2--belonging-collaboration-and-communication">Improving Developer Experience, Level 2: Belonging, Collaboration, and Communication&lt;/h1>
&lt;p>As part of the ongoing series about improving Developer Experience (DevEx), the &lt;a href="https://mende.io/blog/improving-developer-experience-starting-with-psychological-safety-team-stability-and-work-life-balance/">last article&lt;/a> highlighted the significance of psychological safety, stability, and work-life balance.&lt;/p></description></item><item><title>Improving Developer Experience: Starting with Psychological Safety, Team Stability, and Work-Life Balance</title><link>https://mende.io/blog/improving-developer-experience-starting-with-psychological-safety-team-stability-and-work-life-balance/</link><pubDate>Sat, 12 Aug 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/improving-developer-experience-starting-with-psychological-safety-team-stability-and-work-life-balance/</guid><description>&lt;h1 id="improving-developer-experience-starting-with-psychological-safety-team-stability-and-work-life-balance">Improving Developer Experience: Starting with Psychological Safety, Team Stability, and Work-Life Balance&lt;/h1>
&lt;p>As companies strive to foster an environment that promotes creativity, motivation, and productivity, they increasingly recognize the role Developer Experience plays in these efforts.&lt;/p></description></item><item><title>Measuring Developer Experience &amp;#8211; A Balanced Approach</title><link>https://mende.io/blog/measuring-developer-experience-a-balanced-approach/</link><pubDate>Sat, 05 Aug 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/measuring-developer-experience-a-balanced-approach/</guid><description>&lt;h1 id="measuring-developer-experience-8211-a-balanced-approach">Measuring Developer Experience – A Balanced Approach&lt;/h1>
&lt;p>Developer Experience is one of the most essential factors for high-performing teams and organizations. Thus, the obvious question is how to measure, assess and understand the status quo within your organization and team.&lt;/p></description></item><item><title>11 Tips to Prevent Survey Fatigue in Your Organization</title><link>https://mende.io/blog/11-tips-to-prevent-survey-fatigue-in-your-organization/</link><pubDate>Sat, 29 Jul 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/11-tips-to-prevent-survey-fatigue-in-your-organization/</guid><description>&lt;h1 id="11-tips-to-prevent-survey-fatigue-in-your-organization">11 Tips to Prevent Survey Fatigue in Your Organization&lt;/h1>
&lt;p>Surveys are a vital tool to measure and understand the perceived developer experience within a team or organization. People who run surveys often face the challenge of decreasing responses. Survey fatigue can be a huge problem when trying to get meaningful data about the state of the developer experience within an organization.&lt;/p></description></item><item><title>Ways to Decrease Performance: Daily Standups</title><link>https://mende.io/blog/ways-to-decrease-performance-daily-standups/</link><pubDate>Sat, 22 Jul 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/ways-to-decrease-performance-daily-standups/</guid><description>&lt;h1 id="ways-to-decrease-performance-daily-standups">Ways to Decrease Performance: Daily Standups&lt;/h1>
&lt;p>In this second article of my series, “&lt;a href="https://mende.io/blog/tag/ways-to-decrease-performance/">Ways to Decrease Performance&lt;/a>”, I will dive into the exciting topic of “daily standups.” Daily standups are an important ritual of many agile teams, which makes them a worthy subject in this series.&lt;/p></description></item><item><title>Ways to Decrease Performance: Velocity Tracking</title><link>https://mende.io/blog/ways-to-decrease-performance-velocity-tracking/</link><pubDate>Sat, 15 Jul 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/ways-to-decrease-performance-velocity-tracking/</guid><description>&lt;h1 id="ways-to-decrease-performance-velocity-tracking">Ways to Decrease Performance: Velocity Tracking&lt;/h1>
&lt;p>This is the first article of my series, “&lt;a href="https://mende.io/blog/tag/ways-to-decrease-performance/">Ways to Decrease Performance&lt;/a>”, which intends to trigger critical reflection on common &lt;em>“Agile”&lt;/em> practices, that is, practices that I see many &lt;em>”agile”&lt;/em> teams doing.&lt;/p></description></item><item><title>Maslow’s Hierarchy of Needs — DevEx Edition</title><link>https://mende.io/blog/maslows-hierarchy-of-needs-devex-edition/</link><pubDate>Sat, 08 Jul 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/maslows-hierarchy-of-needs-devex-edition/</guid><description>&lt;h1 id="maslows-hierarchy-of-needs--devex-edition">Maslow’s Hierarchy of Needs — DevEx Edition&lt;/h1>
&lt;p>Do you know how to prioritize your developer experience investments? You might have read about the three dimensions and 25+ factors of developer experience (see below). But what to do about that? — Maslow’s hierarchy of needs gives the answer.&lt;/p></description></item><item><title>From Conflict to Collaboration in Engineering Teams</title><link>https://mende.io/blog/from-conflict-to-collaboration-in-engineering-teams/</link><pubDate>Sat, 01 Jul 2023 04:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/from-conflict-to-collaboration-in-engineering-teams/</guid><description>&lt;h1 id="from-conflict-to-collaboration-in-engineering-teams">From Conflict to Collaboration in Engineering Teams&lt;/h1>
&lt;p>In any team setting, conflicts are inevitable. They can arise from various sources, such as differences in perspectives, competing priorities, or communication gaps. Engineering teams are no exception.&lt;/p></description></item><item><title>How to Measure Developer Experience: The Danger of Metrics</title><link>https://mende.io/blog/how-to-measure-developer-experience-the-danger-of-metrics/</link><pubDate>Sat, 24 Jun 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/how-to-measure-developer-experience-the-danger-of-metrics/</guid><description>&lt;h1 id="how-to-measure-developer-experience-the-danger-of-metrics">How to Measure Developer Experience: The Danger of Metrics&lt;/h1>
&lt;p>Whenever I talk with people about developer experience or developer productivity, one question is never far: How do we measure it?&lt;/p></description></item><item><title>Developer Experience at Risk: Red Flags for Engineering Leaders</title><link>https://mende.io/blog/developer-experience-at-risk-red-flags-for-engineering-leaders/</link><pubDate>Sat, 17 Jun 2023 05:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/developer-experience-at-risk-red-flags-for-engineering-leaders/</guid><description>&lt;h1 id="developer-experience-at-risk-red-flags-for-engineering-leaders">Developer Experience at Risk: Red Flags for Engineering Leaders&lt;/h1>
&lt;p>Developer Experience is &lt;strong>the&lt;/strong> most important driver behind productivity, engagement, and job satisfaction. Therefore, improving the perceived experience of their engineers should be the top priority for engineering leaders at all levels.&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>Managing Technical Debt in Software Development</title><link>https://mende.io/blog/managing-technical-debt-in-software-development/</link><pubDate>Sat, 29 Apr 2023 07:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/managing-technical-debt-in-software-development/</guid><description>&lt;h1 id="managing-technical-debt-in-software-development">Managing Technical Debt in Software Development&lt;/h1>
&lt;p>Organizations often accumulate technical debt as the pressure to deliver customer value quickly increases, systems grow, and extending functionality the &lt;em>right&lt;/em> way becomes more difficult.&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>Weekly Kickoff: Reconnect and Kickstart as a Team</title><link>https://mende.io/blog/weekly-kickoff-reconnect-and-kickstart-as-a-team/</link><pubDate>Sat, 08 Apr 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/weekly-kickoff-reconnect-and-kickstart-as-a-team/</guid><description>&lt;h1 id="weekly-kickoff-reconnect-and-kickstart-as-a-team">Weekly Kickoff: Reconnect and Kickstart as a Team&lt;/h1>
&lt;blockquote>
&lt;p>It’s Monday! 🚀 Developer Experience Kickoff&lt;/p>
&lt;/blockquote>
&lt;p>This was the title of a blocker in the calendars of members of the DevEx team at BRYTER, spanning from 9:00 CET to 12:00 CET every Monday. Three hours. Quite some time for a meeting. Unless: This was not a meeting, as you may know it.&lt;/p></description></item><item><title>Deep Work and Collaboration in Platform- and Enabling-Teams</title><link>https://mende.io/blog/deep-work-and-collaboration-in-platform-and-enabling-teams/</link><pubDate>Sat, 01 Apr 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/deep-work-and-collaboration-in-platform-and-enabling-teams/</guid><description>&lt;h1 id="deep-work-and-collaboration-in-platform--and-enabling-teams">Deep Work and Collaboration in Platform- and Enabling-Teams&lt;/h1>
&lt;p>&lt;em>This is the fourth and last articles of my series about &lt;a href="https://mende.io/blog/tag/deep-work/">deep work&lt;/a>. The first article was about &lt;a href="https://mende.io/blog/the-value-of-deep-work-for-peak-performance/">the value of deep work for peak performance&lt;/a>. The second article was about &lt;a href="https://mende.io/blog/7-tips-for-more-deep-work-for-individuals/">seven tips for more deep work for individuals&lt;/a>. The third articles was about &lt;a href="https://mende.io/blog/deep-work-is-a-team-effort/">deep work for teams&lt;/a>.&lt;/em>&lt;/p></description></item><item><title>Deep Work is a Team Effort</title><link>https://mende.io/blog/deep-work-is-a-team-effort/</link><pubDate>Sat, 25 Mar 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/deep-work-is-a-team-effort/</guid><description>&lt;h1 id="deep-work-is-a-team-effort">Deep Work is a Team Effort&lt;/h1>
&lt;p>This is the third article in my series about &lt;a href="https://mende.io/blog/tag/deep-work/">deep work&lt;/a>. The first article was about the &lt;a href="https://mende.io/blog/the-value-of-deep-work-for-peak-performance/">value of deep work for peak performance&lt;/a>. In my last article, I gave &lt;a href="https://mende.io/blog/7-tips-for-more-deep-work-for-individuals/">seven tips on how to get more deep work time as an individual&lt;/a>.&lt;/p></description></item><item><title>7 Tips for more Deep Work for Individuals</title><link>https://mende.io/blog/7-tips-for-more-deep-work-for-individuals/</link><pubDate>Sat, 18 Mar 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/7-tips-for-more-deep-work-for-individuals/</guid><description>&lt;h1 id="7-tips-for-more-deep-work-for-individuals">7 Tips for more Deep Work for Individuals&lt;/h1>
&lt;p>In my &lt;a href="https://mende.io/blog/the-value-of-deep-work-for-peak-performance/">last article&lt;/a>, I highlighted the importance of &lt;a href="https://mende.io/blog/tag/deep-work/">deep work&lt;/a> to achieve high productivity and quality of work. Today, I will follow up with seven tips for more deep work as an individual.&lt;/p></description></item><item><title>The Value of Deep Work for Peak Performance</title><link>https://mende.io/blog/the-value-of-deep-work-for-peak-performance/</link><pubDate>Sat, 11 Mar 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-value-of-deep-work-for-peak-performance/</guid><description>&lt;h1 id="the-value-of-deep-work-for-peak-performance">The Value of Deep Work for Peak Performance&lt;/h1>
&lt;p>As somebody who juggled various roles and responsibilities as a software engineer, architect and tech lead, I certainly understand the importance of deep work and how difficult it can be to get it when working with other people.&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>Dysfunctional without knowing: 5 signs that your team might have a problem</title><link>https://mende.io/blog/dysfunctional-without-knowing-5-signs-that-your-team-might-have-a-problem/</link><pubDate>Sat, 25 Feb 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/dysfunctional-without-knowing-5-signs-that-your-team-might-have-a-problem/</guid><description>&lt;h1 id="dysfunctional-without-knowing-5-signs-that-your-team-might-have-a-problem">Dysfunctional without knowing: 5 signs that your team might have a problem&lt;/h1>
&lt;p>In the last 10+ years, I have worked in and with many teams. And I was fortunate to experience working in many fantastic teams. Teams where people cared for each other, trusted each other and were committed to deliver the best results together. People, where conflicts and disagreements were beneficial and important to achieve better results.&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>Make three friends with one gift: Why developer experience is key to productivity, engineering excellence and stakeholder satisfaction.</title><link>https://mende.io/blog/make-three-friends-with-one-gift-why-developer-experience-is-key-to-productivity-engineering-excellence-and-stakeholder-satisfaction/</link><pubDate>Sat, 11 Feb 2023 06:00:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/make-three-friends-with-one-gift-why-developer-experience-is-key-to-productivity-engineering-excellence-and-stakeholder-satisfaction/</guid><description>&lt;h1 id="make-three-friends-with-one-gift-why-developer-experience-is-key-to-productivity-engineering-excellence-and-stakeholder-satisfaction">Make three friends with one gift: Why developer experience is key to productivity, engineering excellence and stakeholder satisfaction.&lt;/h1>
&lt;p>In today’s fast-paced, technology-driven world, software development has become a critical aspect of many organisations. However, with increased demands on development teams, it’s easy to overlook the importance of developer experience.&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>How to do Architecture Mapping Workshops in a Remote Setup</title><link>https://mende.io/blog/remote-architecture-mapping-workshops/</link><pubDate>Sat, 23 Jul 2022 13:27:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/remote-architecture-mapping-workshops/</guid><description>&lt;h1 id="how-to-do-architecture-mapping-workshops-in-a-remote-setup">How to do Architecture Mapping Workshops in a Remote Setup&lt;/h1>
&lt;p>Mapping the architecture of the system that you are building in your company, is a worthwhile activity. The worth does not come so much from the end-result, the map, but much more from the activity itself, if done right.&lt;/p></description></item><item><title>Is &amp;#8220;Not deploying on Fridays&amp;#8221; an outdated practice?</title><link>https://mende.io/blog/not-deploying-on-fridays-outdated-practice/</link><pubDate>Sat, 09 Jul 2022 13:25:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/not-deploying-on-fridays-outdated-practice/</guid><description>&lt;h1 id="is-8220not-deploying-on-fridays8221-an-outdated-practice">Is “Not deploying on Fridays” an outdated practice?&lt;/h1>
&lt;p>Every person working in a field somehow related to software development probably has heard the term “Don’t deploy on Fridays”. For years, I considered this as a wise recommendation.&lt;/p></description></item><item><title>Scratch the Backlog – There is a better way to plan your work</title><link>https://mende.io/blog/scratch-the-backlog/</link><pubDate>Sat, 25 Jun 2022 13:22:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/scratch-the-backlog/</guid><description>&lt;h1 id="scratch-the-backlog--there-is-a-better-way-to-plan-your-work">Scratch the Backlog – There is a better way to plan your work&lt;/h1>
&lt;p>Every approach of making work visible has some kind of “Open Column”, “Backlog” or something similar with a more fancy name. This &lt;em>thing&lt;/em> tends to fill up over time, while more and more ideas and tasks get added. Eventually, this container turns into a graveyard for ideas, hopes, and promises.&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>What Developer Experience Engineers can learn from User Experience Engineers</title><link>https://mende.io/blog/user-experience-teachings-for-developer-experience-engineers/</link><pubDate>Sat, 28 May 2022 13:15:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/user-experience-teachings-for-developer-experience-engineers/</guid><description>&lt;h1 id="what-developer-experience-engineers-can-learn-from-user-experience-engineers">What Developer Experience Engineers can learn from User Experience Engineers&lt;/h1>
&lt;p>While developer experience is a relatively new term, user experience is not. In fact, the term &lt;em>user experience&lt;/em> was probably first coined in 1990 by Don Norman:&lt;/p></description></item><item><title>DRY – DO repeat yourself</title><link>https://mende.io/blog/dry-do-repeat-yourself/</link><pubDate>Sat, 30 Apr 2022 13:13:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/dry-do-repeat-yourself/</guid><description>&lt;h1 id="dry--do-repeat-yourself">DRY – DO repeat yourself&lt;/h1>
&lt;p>When I started my career as a software developer and already during university, almost no principle was mentioned as often as the DRY principle: “Do &lt;strong>not&lt;/strong> repeat yourself”&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>Why companies should care about great developer experience</title><link>https://mende.io/blog/care-about-developer-experience/</link><pubDate>Sat, 05 Mar 2022 13:02:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/care-about-developer-experience/</guid><description>&lt;h1 id="why-companies-should-care-about-great-developer-experience">Why companies should care about great developer experience&lt;/h1>
&lt;p>Companies might fall into the trap to believe that developer experience is a nice-to-have luxury rather than a necessity. However, this is not the case. As I argued in my &lt;a href="https://mende.io/blog/developer-experience-developer-productivity/">last article&lt;/a>, high developer productivity results from a great developer experience and thus, the companies’ success ultimately relies on this.&lt;/p></description></item><item><title>Should we focus on developer experience or developer productivity?</title><link>https://mende.io/blog/developer-experience-developer-productivity/</link><pubDate>Sat, 26 Feb 2022 12:57:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/developer-experience-developer-productivity/</guid><description>&lt;h1 id="should-we-focus-on-developer-experience-or-developer-productivity">Should we focus on developer experience or developer productivity?&lt;/h1>
&lt;p>When talking about developer experience, there are a couple of other names thrown into the conversation that all kind-of mean the same, but IMHO have a slightly different touch / focus and can be perceived quite differently.&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>Blameless Post-Mortems: Incidents are a learning opportunity</title><link>https://mende.io/blog/blameless-postmortems/</link><pubDate>Sat, 15 Jan 2022 12:42:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/blameless-postmortems/</guid><description>&lt;h1 id="blameless-post-mortems-incidents-are-a-learning-opportunity">Blameless Post-Mortems: Incidents are a learning opportunity&lt;/h1>
&lt;p>Blameless post-mortems are an effective tool to facilitate learning from failures, to share knowledge and to significantly improve the entire system, including software, infrastructure, and processes.&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>Focus Week Case Study: Bringing E2E Tests into the CI Pipeline</title><link>https://mende.io/blog/focus-week-case-study/</link><pubDate>Sat, 25 Dec 2021 12:34:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/focus-week-case-study/</guid><description>&lt;h1 id="focus-week-case-study-bringing-e2e-tests-into-the-ci-pipeline">Focus Week Case Study: Bringing E2E Tests into the CI Pipeline&lt;/h1>
&lt;p>In my &lt;a href="https://mende.io/blog/focus-weeks/">last article&lt;/a>, I wrote about focus weeks and how my team is currently doing them at BRYTER. Today, I want to share a case study of our latest focus week.&lt;/p></description></item><item><title>Focus Weeks: How to collaboratively crack difficult problems with joy</title><link>https://mende.io/blog/focus-weeks/</link><pubDate>Sat, 18 Dec 2021 12:32:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/focus-weeks/</guid><description>&lt;h1 id="focus-weeks-how-to-collaboratively-crack-difficult-problems-with-joy">Focus Weeks: How to collaboratively crack difficult problems with joy&lt;/h1>
&lt;p>Focus weeks are a tool for cracking difficult or complex topics as a team while fostering team collaboration and improving team culture.&lt;/p></description></item><item><title>There is no system like production: Why you should test in production</title><link>https://mende.io/blog/testing-in-production/</link><pubDate>Sat, 11 Dec 2021 12:27:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/testing-in-production/</guid><description>&lt;h1 id="there-is-no-system-like-production-why-you-should-test-in-production">There is no system like production: Why you should test in production&lt;/h1>
&lt;p>&lt;img src="https://mende.io/img/import/2021-10-testing-in-production.jpg" alt="">&lt;/p>
&lt;p>Shipping software without testing sounds scary. And this is also, what this article &lt;strong>is not&lt;/strong> about. Organisations spend a lot of time and money to make sure that code is as much error-free as possible, when it reaches production and affects users.&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>Crucial developer practices: Decoupling deployments and releases</title><link>https://mende.io/blog/decoupling-deployments-and-releases/</link><pubDate>Sat, 27 Nov 2021 12:02:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/decoupling-deployments-and-releases/</guid><description>&lt;h1 id="crucial-developer-practices-decoupling-deployments-and-releases">Crucial developer practices: Decoupling deployments and releases&lt;/h1>
&lt;p>When systems are small and the risk of introducing defects when changing its behaviour is low, these changes can happen during deployment. However, when systems grow, the behaviour becomes more complex and more people are working on the system, it is essential to decouple behaviour changes, the releases, from deployments.&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>The value of team programmings</title><link>https://mende.io/blog/the-value-of-team-programmings/</link><pubDate>Sat, 13 Nov 2021 11:35:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/the-value-of-team-programmings/</guid><description>&lt;h1 id="the-value-of-team-programmings">The value of team programmings&lt;/h1>
&lt;p>In this article, I want to explain, why team programmings across units with developers from many backgrounds and areas of the codebase are extremely valuable for companies and individuals, but often undervalued and deprioritized by developers. I will focus on this specific type of team programmings, not about team programmings within a cross-functional unit, even though most of the benefits apply there as well.&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><item><title>Increasing Deployment Efficiency at PAYONE: A Case Study</title><link>https://mende.io/blog/increasing-deployment-efficiency-at-payone-a-case-study/</link><pubDate>Wed, 01 May 2019 07:20:00 +0000</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/blog/increasing-deployment-efficiency-at-payone-a-case-study/</guid><description>&lt;h1 id="increasing-deployment-efficiency-at-payone-a-case-study">Increasing Deployment Efficiency at PAYONE: A Case Study&lt;/h1>
&lt;p>PAYONE, a leading payment service provider (PSP, FinTech) specializing in B2B SaaS solutions, offers merchants the ability to integrate various payment options seamlessly. Their services extend beyond mere transaction processing to include advanced fraud prevention and multichannel checkout systems.&lt;/p></description></item><item><title>Imprint</title><link>https://mende.io/imprint/</link><pubDate>Wed, 31 Oct 2018 09:47:56 +0100</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/imprint/</guid><description>&lt;h2 id="information-provided-according-to-sec-5-german-telemedia-act-tmg">Information provided according to Sec. 5 German Telemedia Act (TMG):&lt;/h2>
&lt;p>Tobias Mende
INOCEA LLC
Scanbox 16656
Ehrenbergstr. 16a
10245 Berlin
Germany
(Letters only)&lt;/p>
&lt;h2 id="contact">Contact:&lt;/h2>
&lt;p>Telephone: +49 451 7072134&lt;br>
Email: &lt;a href="mailto:web@mende.io">web@mende.io&lt;/a>&lt;/p>
&lt;h2 id="responsible-for-contents-acc-to-sec-55-para-2-german-federal-broadcasting-agreement-rstv">Responsible for contents acc. to Sec. 55, para. 2 German Federal Broadcasting Agreement (RstV):&lt;/h2>
&lt;p>Tobias Mende
INOCEA LLC
Scanbox 16656
Ehrenbergstr. 16a
10245 Berlin
Germany
(Letters only)&lt;/p></description></item><item><title>Privacy Policy</title><link>https://mende.io/privacy-policy/</link><pubDate>Wed, 31 Oct 2018 09:47:56 +0100</pubDate><author>tobi@techunicorn.builders (Tobias Mende)</author><guid>https://mende.io/privacy-policy/</guid><description>&lt;h2>1. An overview of data protection&lt;/h2>
&lt;h3>General&lt;/h3>
The following gives a simple overview of what happens to your personal information when you visit our website. Personal information is any data with which you could be personally identified. Detailed information on the subject of data protection can be found in our privacy policy found below.
&lt;h3>Data collection on our website&lt;/h3>
&lt;strong>Who is responsible for the data collection on this website?&lt;/strong>

The data collected on this website are processed by the website operator. The operator's contact details can be found in the website's required legal notice.

&lt;strong>How do we collect your data?&lt;/strong>

Some data are collected when you provide it to us. This could, for example, be data you enter on a contact form.

Other data are collected automatically by our IT systems when you visit the website. These data are primarily technical data such as the browser and operating system you are using or when you accessed the page. These data are collected automatically as soon as you enter our website.

&lt;strong>What do we use your data for?&lt;/strong>

Part of the data is collected to ensure the proper functioning of the website. Other data can be used to analyze how visitors use the site.

&lt;strong>What rights do you have regarding your data?&lt;/strong>

You always have the right to request information about your stored data, its origin, its recipients, and the purpose of its collection at no charge. You also have the right to request that it be corrected, blocked, or deleted. You can contact us at any time using the address given in the legal notice if you have further questions about the issue of privacy and data protection. You may also, of course, file a complaint with the competent regulatory authorities.
&lt;h3>Analytics and third-party tools&lt;/h3>
When visiting our website, statistical analyses may be made of your surfing behavior. This happens primarily using cookies and analytics. The analysis of your surfing behavior is usually anonymous, i.e. we will not be able to identify you from this data. You can object to this analysis or prevent it by not using certain tools. Detailed information can be found in the following privacy policy.

You can object to this analysis. We will inform you below about how to exercise your options in this regard.
&lt;h2>2. General information and mandatory information&lt;/h2>
&lt;h3>Data protection&lt;/h3>
The operators of this website take the protection of your personal data very seriously. We treat your personal data as confidential and in accordance with the statutory data protection regulations and this privacy policy.

If you use this website, various pieces of personal data will be collected. Personal information is any data with which you could be personally identified. This privacy policy explains what information we collect and what we use it for. It also explains how and for what purpose this happens.

Please note that data transmitted via the internet (e.g. via email communication) may be subject to security breaches. Complete protection of your data from third-party access is not possible.
&lt;h3>Notice concerning the party responsible for this website&lt;/h3>
The party responsible for processing data on this website is:

&lt;p>Tobias Mende&lt;br />
INOCEA LLC&lt;br />
Scanbox 16656
Ehrenbergstr. 16a &lt;br />
10245 Berlin &lt;br />
Germany&lt;/p></description></item></channel></rss>