<?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 Oded Maimon on Medium]]></title>
        <description><![CDATA[Stories by Oded Maimon on Medium]]></description>
        <link>https://medium.com/@oded.maimon?source=rss-23f7b205e1dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*qDAXFdt9ZZOM6O0W.jpg</url>
            <title>Stories by Oded Maimon on Medium</title>
            <link>https://medium.com/@oded.maimon?source=rss-23f7b205e1dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:15:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oded.maimon/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 forgotten agile]]></title>
            <link>https://medium.com/@oded.maimon/the-forgotten-agile-2d304e9bea95?source=rss-23f7b205e1dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d304e9bea95</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Oded Maimon]]></dc:creator>
            <pubDate>Mon, 28 Sep 2020 13:22:33 GMT</pubDate>
            <atom:updated>2020-09-28T21:42:15.401Z</atom:updated>
            <content:encoded><![CDATA[<h4>Agile and what we’ve been taught to be agile are somewhat different from each other. One is simple to understand, and the other is full of books, practices, know-how, and complications</h4><p>Before I start, I want to write that one of the mistakes people usually make is to think that agile is for the R&amp;D &amp; Product to figure out. While, in fact, agile is a management style and should start from the top, another thing is that HR leads usually are not aware of what is agile and what its principles are. Agile is around team building. For that reason, I think HR should be a big part of implementing and maintaining it. I suggest to work with HR leads and make them your number one partner into the transformation. Now, let start.</p><p>If you’ve ever been in a Formula 1 race, you’ve seen the most functioning teams in the world. The best teamwork I’ve ever seen, the image below is on the pit when the driver brings the car for new tires and fuel during the race. (The image below, if I remember correctly, is from F2 race)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m12RvvLaKZk3AJAo" /><figcaption>Formula Pit</figcaption></figure><p>In the video, we see how it is being done in around 5 seconds (<a href="https://www.youtube.com/watch?v=wsCriICZ-nA">The fastest pit stop in the world so far is 1.82 seconds</a>).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2PmYOTMyIhs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2PmYOTMyIhs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2PmYOTMyIhs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6585bec797a6d36b902aa1ba5449b048/href">https://medium.com/media/6585bec797a6d36b902aa1ba5449b048/href</a></iframe><p>But that&#39;s not the only teamwork during the race. F1 racing is not a solo work by the car’s driver; the driver has a full team <a href="https://aws.amazon.com/f1/#:~:text=During%20a%20FORMULA%201%20Grand,unparalleled%20track%2Dside%20decision%20making.">overviewing around 120 sensors of the car, generating 1.1M telemetry data points per second, transmitted to the teams at the pit wall</a>. The image below is the pit wall with the team in constant communication with the driver.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CGYl1iuzCgxn7qkwekpbbQ.png" /><figcaption>Formula, Pitwall</figcaption></figure><p>I love learning new things, and I also love reading about what I already know to get other people’s views on the subject. When we had to improve our development process practices, I got back to the only way that I know how to learn. I looked for the best selling books around agile, and I searched for articles; I even searched for video content (I don’t like watching videos) around the subject, and guess what I found? The amount of content around agile is enormous, so that someone new to the subject will not know where to start.</p><p>When I searched for agile books on Amazon, I got more than 10,000 results (8,000 if filtering English only). If I filter for the 4+ stars rating, I got more than 2,000 books, which is an insane amount of books around one topic. Just for a comparison:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*S68-Cp0kF45NPgr4R7eLgg.png" /><figcaption>Amazon books comparison by topic</figcaption></figure><p>When someone doesn’t know where to start, the next step is to search for an expert, pay someone to give the digested information so we will be able to execute. I have to admit that I always had a problem letting others tell me what to do without fully understanding the logic around it, and that logic had to make sense to me.</p><h3>Noise cancellation</h3><p>I decided to go back and learn the foundations of agile from the places it all started. I needed to make sense out of it. That way of learning is not new to anyone. Understanding the foundations before I learn about what was built on top of it is something that tech people are doing every day (and probably also in other sectors). I decided to start from the beginning, and the next place I looked at was Wikipedia.</p><p>The first paragraph under “<a href="https://en.wikipedia.org/wiki/Agile_software_development">Agile software development</a>” in Wikipedia is</p><p><em>“In software development, agile (sometimes written Agile) practices approach discovering requirements and developing solutions through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end user(s). It advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages flexible responses to change.”</em></p><p>Well, that is simple enough to understand. We do not see all the big words like SCRUM, KANBAN, SCUMBAN, SCALING AGILE, etc. Not here, not in that basic definition.</p><p><em>*Spoiler: This single paragraph is indeed the foundation of Agile. Everything else is a lot of noise that we need to filter the things that fit our team, company &amp; product.</em></p><p>The next thing in Wikipedia talked about the “<a href="https://agilemanifesto.org/">Manifesto for Agile Software Development</a>”. I was very much aware of the manifesto at that time, but I always assumed that the manifesto is somewhat related to what I learned to be agile. I didn’t consider it is what I found to be the manifesto. It has 12 simple principles:</p><ol><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.</li><li>Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.</li><li>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</li><li>Business people and developers must work together daily throughout the project.</li><li>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.</li><li>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.</li><li>Working software is the primary measure of progress.</li><li>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.</li><li>Continuous attention to technical excellence and good design enhances agility.</li><li>Simplicity — the art of maximizing the amount of work not done — is essential.</li><li>The best architectures, requirements, and designs emerge from self-organizing teams.</li><li>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.</li></ol><h3>Principles behind the agile Manifesto</h3><h4>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software</h4><p>For me, it translates to working on small deliverables that are valuable to our users and deliver them for our users to start working with and gather feedback.</p><h4>Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage</h4><p>This one is super important, and I see how almost every engineer struggles to understand that building a product takes iterations. If changes are not embraced, we might find ourselves asking for a waterfall model, and it is not something anyone should ask. When one iteration is completed, it can impact the following iterations, and that is good because it means we are building the product our users need and love and not the product that we thought they would need and love.</p><h4>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale</h4><p>Fast iterations, to be able and deliver working software earlier. To achieve something like that, we would also need to make sure we have the right CI/CD process to deliver the software to production end-users. Otherwise, end-users can’t start using the new software; we won’t learn and build the right product. <br>Except for CI/CD, we will need to make sure to have the proper feature flagging mechanism to deliver the release to a small subset of users and gradually roll out the changes once we decide that it make sense (based on KPIs defined in advance).</p><h4>Business people and developers must work together daily throughout the project</h4><p>I would take the word developers in a more broadly manner these days. We need developers, QA, UI/UX, maybe 3D artists, Animators, and possibly other disciplines depending on the product we are trying to build.</p><p>My translation to that principle is that we need to build a multidisciplinary team around a product, and that team needs to have daily standups to sync and keep alignment.</p><h4>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done</h4><p>Let talk about these motivated individuals for a second. We can mistake that motivation will come once we build a team of talented people and give them a goal. That doesn’t stop there. Building a functioning team requires social engineering, ensuring that the team members have a social match and work well together. If we fail to make that team, break, and rebuild.</p><p>Trust is the foundation of any functional team, trust within the team, and trusting the team by management. Building trust is not easy, it is not easy to create trust inside the team, and it is for sure not easy for management to trust the teams because it means that if we trust the team, we are losing control, and that is hard for many of us to do.</p><h4>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation</h4><p>Let’s start with the word conversation, DO NOT mistake it with meetings… meetings are an organization disease, and everyone should think twice before scheduling a meeting and adding more people into it (I embrace <a href="https://www.businessinsider.com/elon-musk-3-rules-running-better-meetings-like-having-less-2019-8#1-no-large-meetings-1">Elon Musk’s three meeting rules</a>).</p><p>What it means is that we can have a decision faster when we talk f2f. Suppose we are a multidisciplinary team, and we are in the same co-location, or even better, in the same room. In that case, we probably can look to our sides and ask the question and close the issue in seconds, instead of sending a mail, open a ticket, slack, or worse, set a meeting to make a decision.</p><p>With COVID-19, these days are more challenging, and we find ourselves doing more async communication even within the team. Still, there is also great solution like zoom and others, I’ve seen a team creates a zoom room for the team that all team members are in that room during the day, all muted, and only speak when having a question for the team that is important enough not to be sent via Slack. Still, there are other methods people are using these days to keep the interaction faster and more personal. I do not want to get into that, because the web is full of ideas around that.</p><h4>Working software is the primary measure of progress</h4><p>The definition of done, a developed software, tested adequately, deployed to production &amp; released to users (users of our choice, gradually and safely) is the place we should strive to be. Even if we are not at this stage yet, we should deliver working software for our end-users to play on a staging environment, or (not as good) to internal stakeholders, but only until we build our way to deliver the software to our end-users.</p><h4>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely</h4><p>This part is art for me, it is so hard to accomplish, and it requires a lot of practice and discipline to make it happen. It requires every person in the team to be at his/her best to achieve that. We need to make sure the stories split in the right way, that they are small enough, testable, independent, and, hmmm, well, You can google for <a href="https://www.google.com/search?q=invest+story&amp;oq=INVEST+Story">INVEST Story</a> and read more about it, it stands for:</p><p>Independent, Negotiable, Valuable, Estimatable, Small &amp; Testable.</p><p>If we can continuously achieve that, we will have sustainable development at a constant pace.</p><h4>Continuous attention to technical excellence and good design enhances agility</h4><p>Everyone should hate the wording “technical debt”; the way to have less is to build the right tech for the problem. Have the time to make the correct designs for the system, but don’t take it to the other edge and spend a lot of time building the future system that no one will us in most cases. How to do that? Read the next principle.</p><h4>Simplicity — the art of maximizing the amount of work not done — is essential</h4><p>This principle is also art :)</p><p>Not doing things and still achieving our goals is pure art, delaying decisions to later stages, delivering the working software but still not doing the things that are not as important or are not at the core of the service. How to identify these things? It requires experience, attention to detail, and takes time for people to master. Always ask yourself, do I really need to do that? Can I make it without this part?</p><h4>The best architectures, requirements, and designs emerge from self-organizing teams</h4><p>Let talk about <a href="https://en.wikipedia.org/wiki/Conway%27s_law">Conway’s law</a>, introduced by Melvin E. Conway, at 1967, his wording was:</p><p><em>“Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.”</em></p><p>Suppose our teams will not be self-organized and have full autonomy. In that case, we will find that some teams will depend on other teams to deliver their product and achieve their own goals. At that point, we are losing many things, but we are also losing the option to build the best architecture for that team’s product.</p><h4>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly</h4><p>Retrospectives are essential for the team improvement process. There is never perfection in a team or a process. The team needs to keep on improving continuously and indefinitely. For that, they need to have retrospectives at regular intervals.</p><p>I found it effective for me to let the team raise the issues to cover, then let the team pick three that they think are the most important and then run a <a href="https://en.wikipedia.org/wiki/Five_whys">five whys</a> session on each of the problems.</p><p>I never try to improve all issues raised in one interval. It is super hard to fix everything in one interval and at the same time, keep the same consistent pace, so I start with three, and then on the next interval, the team can discuss if three is the right amount, or maybe we need to decrease/increase it.</p><h3>Almost done</h3><p>That was longer than I expected it would be. I wanted to cover more details on implementing each of the principles, but it got too long, so maybe next time.</p><p>Agile software development is an old concept that can be traced back to 1957, so it is pretty old, and we can understand why there is so much work done around that concept, not only in the software industry.</p><p>Everything I wrote is my interpretation of the principles. I might have interpreted it differently from what the seventeen signatories of the manifesto meant. Still, I think it is expected to interpret the principles based on your company, product, and teams and find what works for you best, as long as you follow the last principle and keep improving.</p><p>Every time I read about agile, it helps me tune my thinking a little bit more. Still, I genuinely think that you will find it simpler to implement agile practices and implement SCRUM or KANBAN or any other methodology if you follow the principles. I hope you will find this article helpful to you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d304e9bea95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Precious Diamonds (Part 1)]]></title>
            <link>https://medium.com/@oded.maimon/our-precious-diamonds-part-1-bb8941083e9f?source=rss-23f7b205e1dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb8941083e9f</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Oded Maimon]]></dc:creator>
            <pubDate>Tue, 15 Sep 2020 12:27:54 GMT</pubDate>
            <atom:updated>2023-01-25T16:18:31.085Z</atom:updated>
            <content:encoded><![CDATA[<h3>Our Precious Diamonds (Agile and Squads)</h3><h4>How we moved one of our gaming studios at Playstudios from 50~ people to 180~ with 12 autonomous teams building different features without dependencies (product or tech-wise) and actually achieved linear throughput growth.</h4><h4>Playstudios?</h4><p>Before that, I want to give a brief overview of <a href="https://www.playstudios.com/">Playstudios</a> and how the company operates at a high level. Playstudios is a successful gaming company with multiple successful games in the social casino genre, and now we are growing into new genres that will be published in early 2021.</p><p>Playstudios takes the approach that each studio needs to be fully independent, from the point when we start thinking about a game to the point when we publish it, A/B test it, iterate and improve on it, and layer new content into it. <br>This means that each studio can make product and technology decisions without a complicated approval process outside of that studio. Each studio creates and operates one game until the studio operations are working properly, then the studio can decide to ramp up building another game.</p><p>We have several teams that we decided to keep central or change them to be central across all studios because it made sense for us and how we operate as a company, which includes teams like User Acquisition or Customer Support and others. I’m don’t want to detail the reasons or how these teams are actually structured and operating, but it is important to understand that it made sense to keep/make them central for us.</p><p>This story revolves around our studio based in Tel-Aviv, Israel. The studio started as an independent startup called <a href="https://techcrunch.com/2011/09/14/and-the-winner-of-techcrunch-disrupt-is-shaker/?guccounter=1&amp;guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&amp;guce_referrer_sig=AQAAANaH_W5vHOPy3oPqg1xdDxa0ZfoGuUk8DrzPWHbxTdNmN-c443Zpygdisnjt24YISIKITCt-SYN3hLhPn--refKbRvm2pkY6ezhrAmdWwO6GJBGyyt7S9p8OyKVmeWbR5A5wzr7n9j8DuCzEKC0VjdEbUlDNtn3lFwHozR4nWboA">Shaker</a>. Shaker built a platform (on the web at that time) to provide people with a way to meet other people &amp; friends without leaving their home, and still have a real-life experience like they would had had if they’ve been in a similar place in real life, like a bar or a concert.</p><figure><img alt="Shaker Bar" src="https://cdn-images-1.medium.com/max/640/0*jz52nwXhvOIPyW0Z.jpg" /><figcaption>Shaker Bar</figcaption></figure><p>In the end, we shifted to building Real-Time, Multiplayer Social casino games. Based on the Shaker platform, It didn’t take long before Shaker was acquired by Playstudios and started building a new game together, based on the Shaker platform &amp; the Playstudios brand, and a partnership with MGM Resorts. The new game was called <a href="https://app.adjust.com/z4jr2bj_7vcswsu">POP! Slots</a>.</p><figure><img alt="POP! Slots Casino" src="https://cdn-images-1.medium.com/max/1024/0*8kGsBWIPT2qkT_TA.jpg" /><figcaption>POP! Slots Casino</figcaption></figure><h4>Our previous process</h4><p>At that time, we shifted from traditional project management practices into feature teams, and it was a big improvement for us. However, it didn’t take long for us to understand that it was not ideal. We kept improving the process for almost a year, but we still had complications/time wasted that we didn’t know how to solve with the current feature teams approach.</p><p>We weren’t satisfied, and we knew that there must be a better way to run our studio. We also knew that if we’d kept going in the same direction, our capability to scale our studio from 50 to 200 people wouldn’t actually mean that we would get 4x throughput or even 3x, and that just wasn’t acceptable to us. We needed a way to scale our studio linearly, both in capacity and in throughput. We had to change the way we did things, and we needed to do it immediately. Also, we were very concerned about what these changes will do to our culture, and we kept that in mind while working on finding the solution to our problems.</p><p>Here are some of the things we didn’t like in the existing process:</p><ul><li>Too much planning in terms of project and resources.</li><li>Moving resources between projects all the time.</li><li>Lack of real ownership.</li><li>Too much time wasted in meetings.</li><li>Lack of autonomy.</li><li>Slow onboarding to each product domain.</li><li>The complicated approval process with central people, who needed to be part of almost every decision, created a bottleneck for the company of 80+ people.</li></ul><p>In addition to the above issues, most of our codebase was a monolith, and we wanted to move into microservices. The purpose was to remove technical dependencies, decouple components, improve stability &amp; scalability, etc. That process was already in action, and we didn’t know at the time how much it was going to be connected to the way we would restructure our studio.</p><h4>Going back to the drawing board</h4><p>So we researched a few things about how to improve our existing process:</p><ul><li>We looked back on ourselves when we were a small startup and tried to understand why we could achieve so much with so few people.</li><li>We looked at other companies whose products we admire, such as Netflix, Spotify, Google, Supercell, Activision, Amazon, and more. By doing that, we encountered other companies, some that we wouldn’t even get into our list even if it had 100 companies on it, such as <a href="https://www.fastcompany.com/37815/engines-democracy">General Electric</a>.</li><li>We started reading more books related to team building, culture settings, different management approaches, and microservices.</li><li>We spoke with different people from different companies to learn how they operate: the pros and cons they encounter, and the challenges they must overcome.</li><li>We documented everything we liked and didn’t like.</li></ul><p>Basically, we started educating ourselves as a company.</p><h4>Small Startup</h4><p>The first question was: Why could we achieve things as a small startup that we couldn’t achieve today with 50 people?</p><ul><li>We were 20 people; no complicated project management procedures were needed.</li><li>We had one product in development and not much diversity in work on the product.</li><li>We had full ownership &amp; we felt 100% accountable for the failure or success of everything we did.</li><li>We didn’t have many meetings, and most of the conversations we had were while we worked next to each other &amp; during our daily standup meeting.</li><li>Everyone knew what the high-level goals were and what everyone else was doing to achieve our goals. We trusted each other to do the best job possible to ensure everyone succeeded (Trust is a big factor).</li><li>The decision process was a quick talk with your partners sitting next to you.</li><li>We cared about each other and formed tight work relationships in and out of work.</li><li>We rounded corners, both in tech and product, to get to our goal.</li><li>We worked 15–18 hours a day.</li><li>People were accountable. They even felt bad not working while being sick, went on long vacations, etc.</li></ul><p>Although the last three items are not optimal for a big company (or even sustainable for the long run), they are still part of why we were able to achieve so much with fewer people. Our past alone paved the road to the change we were looking for: a small, static team, focused on one mission.</p><p>A static team is one in which the team members stick together for a long time (at least a year) without moving around between different projects. <br>Feature teams were focused on assembling a team of people for a short-term mission and then shuffled them around when the project was done. Some of them were moved around different projects simultaneously because their part of the project was done, or they were blocked from moving forward with their current tasks. Feature teams were focused on resource optimization more than anything else.</p><h4>What others are doing?</h4><p>The next question was: what does the development process for other companies with great products look like? I’ll describe some of them here.</p><p>We started with the companies that published information about how they operate. We looked at Spotify’s great articles on how their development process worked with squads, tribes, etc. You can find the first article <a href="https://engineering.atspotify.com/2014/03/27/spotify-engineering-culture-part-1/">here</a>.</p><p>We liked Spotify’s concept, but it also looked too complicated for our case, a studio of 50 people that wanted to scale to 200, so we took a lot from the squad &amp; chapter concepts, but we pretty much stopped at that point. Squads are multidisciplinary teams working on one feature area (8–12 people), and Chapters are basically the traditional functional teams, like Mobile Frontend or QA Team that have a lead that is focused on employee growth, helping solve issues, share knowledge, build the discipline standards, etc.</p><p>We looked at Netflix’s culture deck (again). Everyone knew and probably still knows about that deck. You can find the original version of it <a href="https://www.slideshare.net/reed2001/culture-1798664">here</a>, and the new version <a href="https://jobs.netflix.com/culture">here</a>. It wasn’t directly related to the development process, but it was related to ownership, accountability &amp; trust. We also read the book <a href="https://read.amazon.com/kp/kshare?asin=B077Y4WVPT&amp;id=Rg062gZjQAe7Nt2o9CKtYw&amp;reshareId=2S1FEESGTVRTAHVJYKX2&amp;reshareChannel=system">“Powerful: Building a Culture of Freedom and Responsibility” by Patty McCord</a> and listened to Netflix’s podcasts to get additional info.</p><p>Supercell, a gaming company with a collection of very successful games that we love to play, spoke at different conferences on how Supercell is built and operates. They follow the belief that <a href="https://supercell.com/en/our-story/">“The Best Teams Make the Best Games”</a>. <a href="https://youtu.be/crbQgePq5CY">Here</a> is a talk by Ilkka Paananen, Supercell’s CEO, from GDC 2018 on how they turned the traditional org-chart upside down. We actually took a lot from how supercell operates.</p><figure><img alt="Supercell’s turned around org chart" src="https://cdn-images-1.medium.com/max/951/1*dkarWXDUMKjkYyG9ID7zIg.png" /><figcaption>Supercell’s turned around org chart</figcaption></figure><h4>Diamonds</h4><p>Diamonds are multidisciplinary autonomous teams, usually between 8 to 12 people, with one mission statement, business goals, and full independence. Diamonds are highly aligned with the company’s goals and strategy, and each Diamond is trusted to execute without complicated management approvals processes.</p><p>We even have Diamonds working on the same mission statement, without overstepping each other’s roadmap or tech.</p><p>Diamonds are built into our culture and are actually enablers for our cultural preservation while we experience company growth over time.</p><p>When moving to the Diamond structure, we looked at the company as a collection of teams (not a collection of individuals) and took the stand that teams are more important than individuals. Due to that, changes to the way we evaluate people were also made. We now appreciate a person who might not be an expert in her/his domain but dedicates themselves to the team’s success more than we appreciate a person who is the best in the domain but doesn’t act as a team player.</p><p>Soft skills became super important to us. For example, great communication skills, for example, are mandatory for everyone. I’ve worked with many people who are experts in their field but didn’t know how to communicate or express what they think so that other people would be able to take part in the thinking process. Other examples of important soft skills are the person’s ability to differentiate between what is important and what is not, prioritizing work properly, knowing when to ask for help, etc.</p><p>All the Diamonds team members participate in building the roadmap, thinking about the next features, and sharing their feedback and input. It was very easy to notice that we did not need super elaborate product specifications anymore when that happened. People became aware of the requirements while participating in the thinking process, so everyone was aligned on the same goals/concept. The time to build a spec was reduced, and therefore the time to read it and understand what the “product owner” actually meant disappeared altogether.</p><p>Moreover, we actually designed our new office to facilitate the Diamonds work: gave them a space to sit next to each other, provided a small meeting room to have sessions that might not be relevant for the entire team, made available a lounge to have standups/presentations or move out of the table to a less standard working area.</p><p>Like most processes, it is very easy to break the model. When that happens, it can also be due to some decision taken by someone in the management layer and not inside the Diamond. So, when a manager makes a decision that impacts the Diamond, it is good to put up a red flag, rethink the approach, and find a different way to circulate the decision. One approach is to go to the team with the reasons/thoughts/restrictions that got you to the decision first and then let the team come back with a proposed solution.</p><h3>Part II?</h3><p>There is a lot more to write on how the Diamonds operate and the platform around them that enables that operation. If you have questions, feel free to ask them so I can address them in Part II.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb8941083e9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>