<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on CTOMultiplier</title><link>https://ctomultiplier.com/tags/productivity/</link><description>Recent content in Productivity on CTOMultiplier</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 23 Mar 2026 21:05:53 +0100</lastBuildDate><atom:link href="https://ctomultiplier.com/tags/productivity/feed.xml" rel="self" type="application/rss+xml"/><item><title>Systems Thinking</title><link>https://ctomultiplier.com/systems-thinking/</link><pubDate>Mon, 13 Nov 2023 18:11:56 +0000</pubDate><guid>https://ctomultiplier.com/systems-thinking/</guid><description>&lt;p&gt;Occasionally I work with clients who have a major problem in delivering on time and to the agreed quality. When I start to investigate the causes I find that when I talk to the product team they say the problem is that engineering is not fast enough and/or they produce too many defects, and when I talk to engineering they tell me that they get incomplete specifications from product, which means they have to spend more time developing, and sometimes they have to undo changes because they were not what the customer wanted. It is common for these organisations to see themselves as a set of silos, and to believe that the solution lies in &amp;ldquo;fixing&amp;rdquo; one of these silos (e.g. engineering). But this is a reductionist view of the problem, and rarely helps to solve it. To address the root of the problem, we need to rethink how we understand the organisation, and this is where systems thinking can help. As Einstein said: &amp;ldquo;We cannot solve problems by thinking in the same way as when we create them&amp;rdquo;.&lt;/p&gt;</description></item><item><title>The impact of culture on performance</title><link>https://ctomultiplier.com/the-impact-of-culture-on-performance/</link><pubDate>Mon, 13 Nov 2023 17:44:00 +0000</pubDate><guid>https://ctomultiplier.com/the-impact-of-culture-on-performance/</guid><description>&lt;p&gt;This week I want to talk about a podcast from techlead journal (link at the end), in which they interview the author of the book Wrong fit, right fit. In the podcast, the author (André Martin) talks about company culture as a determining factor for the performance and happiness of an employee. Quote &lt;strong&gt;a Gallup report that says $8.8 trillion is lost due to employees&amp;rsquo; lack of engagement with their companies&lt;/strong&gt;. André will equate working in a company with which you don&amp;rsquo;t have a cultural fit to writing with your left hand (or right if you are left-handed). You can do it, and you will produce&amp;hellip;but the quality will be much worse and you will feel unfulfilled.&lt;/p&gt;</description></item><item><title>How to conduct effective meetings</title><link>https://ctomultiplier.com/how-to-conduct-effective-meetings/</link><pubDate>Thu, 26 Oct 2023 10:53:18 +0000</pubDate><guid>https://ctomultiplier.com/how-to-conduct-effective-meetings/</guid><description>&lt;p&gt;There is often talk about whether meetings are worthwhile, and whether they should be abolished altogether because they are a waste of time. Personally I find this view somewhat extreme, but I understand that it responds to the fact that in many cases the way we conduct meetings is effectively a waste of time and money, and a source of frustration and demotivation. Throughout my career I have worked with quite a few companies, and in all of them I have participated in unproductive meetings, and this seems to be a constant no matter who you talk to. It&amp;rsquo;s hard to find someone who, when you ask them about how they do meetings in their company, doesn&amp;rsquo;t complain.&lt;/p&gt;</description></item><item><title>Do you know what DPE is?</title><link>https://ctomultiplier.com/do-you-know-what-dpe-is/</link><pubDate>Wed, 27 Sep 2023 07:23:39 +0000</pubDate><guid>https://ctomultiplier.com/do-you-know-what-dpe-is/</guid><description>&lt;p&gt;DPE stands for Developer Productivity Engineering and is the name of a new discipline that aims to improve developer productivity through automation, observability and tool enhancement.&lt;/p&gt;
&lt;p&gt;The work of a developer when programming has three phases: code -&amp;gt; build -&amp;gt; test, the developer repeats this sequence tens or even hundreds of times a day. And in many cases the build and test phases can take in the order of minutes. For example: if the build of an application takes 5 minutes and the developer does 10 builds per day, that&amp;rsquo;s 50 minutes that the developer has to wait per day. Similarly, the testing phase can increase the developer&amp;rsquo;s waiting time. Multiply that by the number of developers in a company and the cost is significant.&lt;/p&gt;</description></item><item><title>Guide to do Code Reviews in your team</title><link>https://ctomultiplier.com/guide-to-do-code-reviews-in-your-team/</link><pubDate>Tue, 25 Jul 2023 15:42:32 +0000</pubDate><guid>https://ctomultiplier.com/guide-to-do-code-reviews-in-your-team/</guid><description>&lt;p&gt;Code reviews are a practice that has become widespread in recent years, where one or more developers review the new code implemented by another colleague, with the aim of detecting code quality issues, bugs, vulnerabilities, bad practices, etc&amp;hellip; . This allows feedback loops to be shortened, which we know is very beneficial because the later a problem is discovered, the higher the cost of fixing it and the greater the potential business impact.&lt;/p&gt;</description></item><item><title>Is your Scrum suffering from low productivity? Your problem could be WIP</title><link>https://ctomultiplier.com/is-your-scrum-suffering-from-low-productivity-your-problem-could-be-wip/</link><pubDate>Thu, 20 Jul 2023 09:18:13 +0000</pubDate><guid>https://ctomultiplier.com/is-your-scrum-suffering-from-low-productivity-your-problem-could-be-wip/</guid><description>&lt;p&gt;It has been proven that the more work in progress a person or a team has, the more time it takes to close tasks. On the one hand, if we are doing several tasks at the same time and we deliver them at the same time, the delivery time will be the sum of the time of doing the two tasks. However, if we work on the tasks in sequential order, the first task will be delivered earlier, and the average delivery time will also be lower.&lt;/p&gt;</description></item><item><title>The cost of being reactive vs. being proactive</title><link>https://ctomultiplier.com/the-cost-of-being-reactive-vs-being-proactive/</link><pubDate>Sun, 04 Jun 2023 16:30:16 +0000</pubDate><guid>https://ctomultiplier.com/the-cost-of-being-reactive-vs-being-proactive/</guid><description>&lt;p&gt;On countless occasions we hear that we need to be more proactive. In other words, taking the initiative and anticipating problems. But being proactive almost always comes at a cost, which is paid in advance, at best a little time investment, at worst a lot of time and money. We often look at the cost of being proactive, but overlook the cost of not being proactive. Especially when we see that the cost of being proactive is high, we often dismiss it outright, without seeing the other side of the coin.&lt;/p&gt;</description></item></channel></rss>