<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by David Jared on Medium]]></title>
        <description><![CDATA[Stories by David Jared on Medium]]></description>
        <link>https://medium.com/@djared_44982?source=rss-832e7b09f2f6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*rjqhtJgCBsMRz037.jpeg</url>
            <title>Stories by David Jared on Medium</title>
            <link>https://medium.com/@djared_44982?source=rss-832e7b09f2f6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:42:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@djared_44982/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Engineering Manager’s Dilemma]]></title>
            <link>https://medium.com/adobetech/the-engineering-managers-dilemma-be708ecce8ea?source=rss-832e7b09f2f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/be708ecce8ea</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[David Jared]]></dc:creator>
            <pubDate>Thu, 11 May 2017 15:01:02 GMT</pubDate>
            <atom:updated>2017-05-11T15:01:02.333Z</atom:updated>
            <content:encoded><![CDATA[<p>In my previous blog post, I wrote about how <a href="https://medium.com/adobe-io/why-do-organizations-need-a-platform-team-910d79893e0a">software organizations grow to need a platform team</a>. I love how <a href="https://medium.com/u/859d560dd4c2">Peter Seibel</a>’s model yields information about the growing need for a platform team as organization get bigger. However, his model is a static analysis.</p><p><strong>One of the pieces missing from Peter’s model is the effect of time.</strong> The increased effectiveness of a single platform project doesn’t occur overnight. If a 1000 person organization creates a 250 person platform team, it will take months (if not years) to see the organization’s effectiveness increase by ~46%.</p><p>Let’s add time to Peter’s model. Ideally, most platform projects will follow a sigmoidal curve (growth is slow first, then fast, and then slow again) in their increase in effectiveness:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*psjZLZ0nJOGTZrEJvkbjQA.png" /></figure><p>In this example, the platform project takes ~6 months to complete and ~12 months to roll out and be adopted by the organization. Of course this is an average number. Some projects will be completed and adopted in a few months, while some other projects will take over a year to complete. From what I’ve seen at Adobe, 6 months to complete a project followed by a 12 month roll out seems about right for most projects.</p><p>So let’s take the case of the 1000 person engineering organization. Let’s say an engineering manager buys into the idea of engineering effectiveness and reallocates 256 people to a platform team, as the model suggests. As the projects being worked on by the 256 engineers mature and become adopted, the total effectiveness of the organization will rise — over time. The organization’s total effectiveness as a function of time would look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*1bda2-Bx7Xc3UdetDlNxTg.png" /></figure><p>The organization’s total effectiveness will drop in the first several months. The drop is equal to 256 engineers. After 18 months, the organization’s total effective will rise to ~1400 (as suggested by the model). The advantages of the reallocation of resources to platform are realized, but the organization had to go through a painful year of significantly (~25%) reduced effectiveness. <em>That is not a year any engineering manager would want to live through</em>. Around month 9, the executives of the company would revolt and fire the engineering manager in an attempt to save the company from chaos caused by losing 25% of engineering effectiveness.</p><p>Thus, the <strong>Engineering Manager’s Dilemma</strong>. The shaded region represents the total loss in effectiveness cause by staff reallocation. This deficit in effectiveness will not be made up until around month 18. So, something that was suppose to deliver greater effectiveness, has instead created a tough 18 month transition problem for the organization. This creates hard choices for the engineering manager.</p><p>Is there a way to phase in a platform team without destroying the company?We want the effectiveness curve to look more like the green curve rather than the blue:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F5jscsgPUAg3VbL214cDlQ.png" /></figure><p>Unfortunately, for a large organization, there is no easy way to avoid the Engineering Manager’s Dilemma. The most common way to build a platform team is to reallocate engineers from existing product teams. As we saw above, this will result in an immediate drop in the organizations effectiveness. What if the organization hires new people to create the platform team? Again, the organizations total effectiveness would initially drop. The organization total effectiveness will increase once the new hires begin to complete projects. But this will take time. Again, the organization will face the same “Engineering Manager’s Dilemma” as above.</p><p>What if the organization slowly reallocates engineers to the platform team? Rather than moving 256 engineers all at once, perhaps we start with 10 engineers. Once the increased effectiveness of these 10 engineers are realized, we move over 10 more engineers, and so on. Can we mitigate the pain by slowly creating the platform team? On the surface, this sounds like a prudent strategy. Why suffer a 25% lose in effectiveness, when we can manage through a series of 1% loses in effectiveness? This strategy will result in the slow creation of a platform team.<strong> It will also result in a perpetual state of ineffectiveness. </strong>Each time effectiveness increases, we move more engineers over to the platform team. So every time we see an increase, we reduce the effectiveness by moving more engineers to the platform team. By stretching out the reallocation time frame, it will take about 25 years before the organization will finally see a true increase in effectiveness.</p><p>Once a organization finds itself in the state of needing to move 25% of its engineers to a platform team, the engineering manager’s dilemma becomes difficult to avoid. The total lose in effectiveness (the shaded region) will remain the same no matter how you incrementally grow your platform team.</p><blockquote><strong>The best way to avoid the Engineering Manager’s Dilemma is to incrementally grow your platform team as your organization grows.</strong></blockquote><p>The best strategy is to plan ahead. Start growing the platform team when the organization is around 100 engineers. As the company grows, grow the platform team. Follow the optimal curve from “<a href="https://medium.com/adobe-io/why-do-organizations-need-a-platform-team-910d79893e0a">Why Do Organizations Need a Platform Team?</a>”. The organization will still experience the initial reduced effectiveness of each new platform team, but the pain will distributed over time.</p><p><strong>Mitigating the Engineering Manager’s Dilemma:</strong> Avoiding the Engineering Manager’s Dilemma takes a tremendous amount of forethought for company leaders. Most companies find themselves in the problem of creating a platform team once they are big. The only solution is strong leadership to ride through the time period of reduced effectiveness. For companies that have the fortitude to push forward, they will be rewarded with a huge effectiveness boost.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be708ecce8ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/the-engineering-managers-dilemma-be708ecce8ea">The Engineering Manager’s Dilemma</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Do Organizations Need a Platform Team?]]></title>
            <link>https://medium.com/adobetech/why-do-organizations-need-a-platform-team-910d79893e0a?source=rss-832e7b09f2f6------2</link>
            <guid isPermaLink="false">https://medium.com/p/910d79893e0a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organization-design]]></category>
            <category><![CDATA[organizational-change]]></category>
            <dc:creator><![CDATA[David Jared]]></dc:creator>
            <pubDate>Tue, 09 May 2017 15:01:01 GMT</pubDate>
            <atom:updated>2017-05-09T15:01:01.966Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BMh9gsoApUGmJnhiRYvQpg.jpeg" /></figure><p>In September 2015, <a href="https://medium.com/u/859d560dd4c2">Peter Seibel</a> of Twitter wrote one of my favorite blog posts:</p><p><a href="http://gigamonkeys.com/flowers/">Let a 1,000 flowers bloom. Then rip 999 of them out by the roots.</a></p><p>Peter was a technical lead on the Twitter Engineering Effective Group. His role at Twitter is not dissimilar to what I do at Adobe. The article talks about how Twitter handled technical debt (or didn’t) as the company grew. Many of the problems that Twitter encountered are similar to what Adobe is dealing with today. The Adobe Marketing Cloud is a conglomeration of many acquisitions; each of which came to us with its own data platform, data collection and data processing, plus their own style, culture and technical bias. We have a 1,000 flowers blooming.</p><p>We need a platform.</p><p>One of the many things I like about Peter’s blog, was his model for <em>effectiveness</em>. Engineering organizations have a common problem: how many people should be working directly on “the product” versus how many engineers should be working on “the platform”. The idea is that the platform will make product engineers more effective.</p><p>The model that Peter used was:</p><blockquote>E = (Nt — Np)(1 + bNp^s)</blockquote><p>where <em>E</em> is the total effectiveness, <em>Nt</em> is the total number of people, <em>Np</em> is the number of people working on platform projects, <em>b</em> is the effectiveness boost for the first platform member, and <em>s</em> is the scaling of the boost. The units for effectiveness are people. One person has an effectiveness of 1; 2 people have an effectiveness of 2 people, and so on.</p><p>It’s a good idea to get a feel for this equation. If no one is working on the platform (<em>Np</em> = 0), the effectiveness is <em>Nt</em>. This is exactly what you would expect: if you have <em>Nt</em> people working on the product, their effectiveness would be <em>Nt</em>. If no one is working on the product (<em>Nt</em> — <em>Np</em>) = 0, then the effectiveness is zero, which also makes sense. The (<em>Nt</em> — <em>Np</em>) term reflects the fact for every person working on the platform, the product effectiveness is reduced by that amount. The <em>bNp^s</em> term reflects the boost in effectiveness caused by the platform team. <em>b</em> is the percentage increase that a platform member increases the effectiveness of a product member. <em>b</em> = 0.02 means a single platform member will increase the effectiveness of a product member by 2%. A 2% improvement is modest, but <strong>small improvements in effectiveness add up</strong>. The <em>Np^s</em> reflect diminishing returns on adding more people to the platform team: every time you add someone to the platform team, the effectiveness boost is reduced. Peter argues for using <em>s</em> = 0.7, which seems reasonable.</p><p>This model is not complete, but it is helpful in understanding the dynamics of an organization. <strong>The results are heavily depended upon the values selected for b and s. </strong>If your platform team works on the wrong projects (<em>b</em> is small) or if your platform team has its own dysfunctions (<em>s</em> is small), then you are not going to see much effectiveness in having a platform team — and the model predicts this. If this is the state of your organization, then everyone should be working on the product and forget the platform.</p><p>Let’s take a look at how the model behaves for different organization sizes. For an organization of 10 people (<em>Nt</em> = 10, <em>b</em> = 0.02, <em>s</em> = 0.7), the effectiveness is</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*iXIw-60JKxo_SZiT-R4Qyg.png" /></figure><p>For an engineering group of ten people, moving engineers to a platform team makes little sense. Individual engineers will work on improving their own effectiveness. The product team is the platform team.</p><p>For an organization of 100 people (<em>Nt</em> =100, <em>b</em> = 0.02, <em>s</em> =0.7), things start to look different:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jw-L9_aouNfyVJf4adNYiA.png" /></figure><p>In this organization, having 3 people working on the platform team will increase the overall effectiveness of organization. This is very consist with what I’ve seen at Adobe. When teams get to about 100 people, a small group of engineers will start to work on infra-structure projects and small exploratory projects to improve identified problems. Again, there is no need for an official platform team.</p><p>For an organization of 1000 people (<em>Nt</em> =1000, <em>b</em> = 0.02, <em>s</em> = 0.7), the story is different:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*VEQrNQhoA6YCNWiochTtVA.png" /></figure><p><strong>By creating a platform team with 259 people, we can have an organization of 1,000 work with the effectiveness of 1,465 people.</strong></p><blockquote>By creating a platform team with 259 people, we can have an organization of 1,000 work with the effectiveness of 1,465 people.</blockquote><p>In other words, for a larger organization, by having 25% of your engineers working on the platform, you will increase total organization effectiveness.</p><p>Note that the model is only a model. For a given organization, the values of <em>b</em> and <em>s</em> can be ambiguous, which makes it difficult to determine the optimal number of engineers that should be working on a platform team. Thus, the specific result of 259 engineers should be taken with some fuzziness.</p><p>As a company with engineering teams dedicated to multiple different products, Adobe tended to think of itself more as multiple 100 person developer teams. Each 100 person organization was happy to devote 3% of there engineers to common-good projects — as the model suggests. But, this approach only increased the total organization effectiveness by a modest 1% — also as the model suggests. This falls short of the optimal number for such a large organization.</p><p>You can also see why the creation of a platform team is so hard. Reassigning 25% of your engineers seems crazy from the perspective of a 100 person organization. The simple linear model suggests that reassigning 25% of your engineers would result in a ~17% DECREASE (100–25 + 25/3) in effectiveness. Plus, platform teams are more often than not created by reassigning headcount from existing teams, not hiring new engineers. No manager wants to give up productive engineers.</p><p>Here is a graph of the optimal platform team size as a function of the organization size:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*3OB5fKmZBi0d2TidrhktWQ.png" /></figure><p>As you can see, for large organizations, the optimal platform team becomes a simple ratio</p><p><em>Np optimal = (1 — s) Nt</em></p><p>It’s interesting that <em>Np</em> stops being dependent on <em>b</em>, the boost. But, this makes sense, because the effective boost of the first platform engineer becomes irrelevant when the organization gets large.</p><p>It’s also interesting to note that for very large organizations (Nt &gt; 5000), the platform team itself will most likely need to be reorganized: the platform team will need its own platform team.</p><blockquote>For organizations with more than 5000 engineers, the platform team needs its own platform team.</blockquote><p>My next blog post will take Peter’s model a step further. Peter’s model is a static analysis: it looks at organization effectiveness once product and platform teams are working well together. In reality, it takes time to develop a platform team and realize the boost in effective. In my next post, I will add a temporal component to Peter’s model, and we will see the “<a href="https://medium.com/adobe-io/the-engineering-managers-dilemma-be708ecce8ea">Engineering Manager’s Dilemma</a>”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=910d79893e0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/why-do-organizations-need-a-platform-team-910d79893e0a">Why Do Organizations Need a Platform Team?</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>