<?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 Gabriella Hachem on Medium]]></title>
        <description><![CDATA[Stories by Gabriella Hachem on Medium]]></description>
        <link>https://medium.com/@gabriella_46676?source=rss-f7335ce2e998------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Q1TvD_sVBgADRRU_</url>
            <title>Stories by Gabriella Hachem on Medium</title>
            <link>https://medium.com/@gabriella_46676?source=rss-f7335ce2e998------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:23:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gabriella_46676/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[Collapsing the talent stack]]></title>
            <link>https://medium.com/@gabriella_46676/collapsing-the-talent-stack-40eb849a2f97?source=rss-f7335ce2e998------2</link>
            <guid isPermaLink="false">https://medium.com/p/40eb849a2f97</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Gabriella Hachem]]></dc:creator>
            <pubDate>Mon, 24 Feb 2025 16:56:37 GMT</pubDate>
            <atom:updated>2025-02-24T16:56:37.462Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my favourite articles on the internet is <a href="https://www.implications.com/p/insights-on-collapsing-the-talent">collapsing the talent stack</a> by Scott Belsky. This piece is my take on collapsing the talent stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QffrqWEpsVjskJZwHdr80Q.png" /></figure><p>I’ll start with what it means to collapse the talent stack. My interpretation is that it’s about having the same person own multiple parts of a process, and therefore naturally, have the same person act as multiple “roles”. It’s when the designer owns copy across the product, and therefore, owns the responsibilities of what other companies might hire the specialized role of “copywriter” for. Or a product manager running and analyzing user interviews, owning traditional responsibilities of a “user researcher”. It’s about streamlining work so that a single person handles as much of the process as possible.</p><p><strong>What leads to an “uncollapsed” stack</strong></p><p>I believe that as an industry, we’ve become overspecialized. We’ve built walls between roles that inherently overlap. We’ve created separate titles unnecessarily. I think there are 3 main contributors:</p><ol><li>ZIRP era</li></ol><ul><li>People raised crazy rounds because of a flooding of capital in the industry.</li><li>One of the only ways to justify that much capital is to hire, so companies overhired (the mass layoffs we’re experiencing is another consequence of this). We hired too many people and therefore separated responsibilities that could have been owned by less people.</li></ul><p>2. Language</p><ul><li>Language is one of the most important and influential aspects of society. It’s the foundation of how we think and how we perceive, and therefore act. This extends from the jokes that we make and the news headlines we read to the job titles we give people.</li><li>When only one role in a team has the word “quality” in its title, we immediately (and usually, unintentionally) take accountability of “quality” away from other roles. In the same vain, when we give only one role’s title the word “design”, we take the accountability and <em>care of</em> design off of others. We tell our teams “someone else is specifically responsible for that, you don’t have to worry about it”. We put boxes around people with the language we use in their titles, giving them <em>only</em> specific parts of a process to own. These parts could have been shared rather than isolated.</li></ul><p>3. Incentive structures</p><ul><li>Incentives don’t just encourage behaviors; they discourage others.</li><li>When someone’s promotion is based on “closing tickets”, you’re limiting the scope of the role. Over time, people optimize for the metrics they are measured by, often at the cost of broader impact. Collapsing the stack is about removing limitations and allowing a single person to take as much effective space as possible, and incentive structures play a big role in dictating how much space a person should be taking.</li></ul><p><strong>Cons of overspecialization: loss of speed and quality</strong></p><ol><li>In any process, the more people between decision and execution, the lower the quality of the output and the slower you are. Every additional layer introduces more friction — misalignment, delays, and a dilution of the original intent.</li><li>An idea having to go from one person through 10 other people to finally be executed will include a heavy loss of information. Translating thoughts into words is already a lossy model, imagine how much information is lost when you have to communicate and translate ideas through tickets and documents. Every time information gets relayed, it’s interpreted and reinterpreted, often diluting or even distorting the original intent.</li><li>More stakeholders also means more opinions. Instead of optimizing for the best solution, teams start optimizing for what’s <em>agreeable. </em>It’s also easier for people to pass blame or avoid responsibility as the direct connection between decision and outcome is weakened. The further someone is from the decision-making, the less they understand the reasoning behind it. This leads to a lower quality of execution because they don’t have all the nuances of the context to make right trade-offs.</li><li>Each additional layer adds meetings, approvals, and check-ins. The more layers, the longer it takes to move forward. The more brains and hands a decision has to pass through, the more likely it is that execution won’t meet expectations, also often requiring do-overs.</li></ol><p><strong>Pros of collapsing</strong></p><ol><li>Increase in speed</li></ol><ul><li>You will be faster. I feel like I shouldn’t have to explain why having less people involved in a process makes you faster. We’ve all felt the inefficiencies of meetings, emails, and back-and-forth. I’m all for inclusivity but if one person can make the right decision fast, without needing other people’s opinions, this should not be punished. It should be rewarded.</li></ul><ol><li>Increase in quality</li></ol><ul><li>The thing that allows you to be able to make the right decision in the first place is that you’ve been involved in the process since step 1, so when you get to step 4, you have full context.</li><li>“Exercising good judgement” isn’t something that we’re just born with. We’re able to make the right decisions based on judgement because of a compounding intake of information. That being said, the ability to synthesize and analyze this information, quickly, to make the right decisions can be a differentiator between good and great talent.</li><li>When the stack is collapsed, more of the information is complete and accurate, vs. having to go through multiple heads for bits and pieces to get lost in translation. Decisions are based on what information you have available to you, so the more complete the information, the higher the quality of the decision. At the end of the day, quality is inherently holistic — it’s not just about isolated moments of excellence but about the integrity of the entire process. When one person owns multiple parts, they see the bigger picture, allowing for a more seamless coherence. Fragmentation dilutes quality, while continuity reinforces it.</li></ul><p>3. A less measurable positive outcome is that the work becomes more fulfilling because ownership is heightened and impact is more concrete. For control freaks, the important piece here is to balance authority to make decisions with accountability for making them.</p><p><strong>Actionable ways to collapse the stack</strong></p><ol><li>Leave titles more open ended. I know that some people like clarity and titles and scoped responsibilities give clarity, but what if the magic is in the chaos and open ended-ness? It’s not for everyone, but it can be magical. I’m increasingly seeing positions like “member of technical team” which leaves responsibility vague, and allows for impact and ownership wherever possible.</li><li>Align incentive structures with outcomes, not outputs. This incentives people to do whatever is necessary to get to the outcome, often executing beyond their normalized “scope”.</li><li>If incentive structure and culture are not there at the company level, as an individual contributor, problem selection becomes a very important skill. The best people don’t just take what they’re given — they question, refine, and shape the problems before solving them. In structured teams, not all problems are “yours” to solve, but that doesn’t mean you can’t have influence. You might end up changing the whole culture for the better.</li><li>Our tools define what we create and how we work. Seek out and push for the adoption of tools that collapse the stack.</li></ol><p><strong>What does collapsing the stack mean for collaboration</strong></p><p>Collapsing the talent stack doesn’t eliminate collaboration, but it does reshape it. Instead of collaboration being rigid handoffs between roles, it shifts toward fluid, high-context teamwork. Individuals own larger slices of the work and engage in collaboration <strong>only</strong> where it adds meaningful value. Work between individuals becomes more paralleled and intertwined.<strong> <br>A collapsed stack only works if there is trust</strong> — because people operate with autonomy and make decisions quickly. The future will be concentrated on polymathic people who bring multiple skill sets, highly enabled by tools &amp; software, making teams leaner but more powerful.</p><p>—</p><p>There’s a responsibility on technologists to redefine workflows by building better tools. Stop automating the existing shitty work. In this platform shift, there’s a real opportunity to <strong>redefine</strong> the work. The best teams are going to jump on this. <a href="https://www.dessn.ai/">Some</a> already have;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40eb849a2f97" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>