{"id":6433,"date":"2025-02-13T16:23:39","date_gmt":"2025-02-13T21:23:39","guid":{"rendered":"https:\/\/treize.pro\/?p=6433"},"modified":"2025-02-13T16:23:53","modified_gmt":"2025-02-13T21:23:53","slug":"eos-our-experience-with-level-10-meeting","status":"publish","type":"post","link":"https:\/\/treize.pro\/en\/management\/eos-our-experience-with-level-10-meeting\/","title":{"rendered":"EOS: Our experience with Level 10 Meetings (2\/5)"},"content":{"rendered":"<p>When we decided to implement the <a href=\"https:\/\/treize.pro\/en\/management\/how-we-discovered-and-implemented-eos-at-treize\/\">Entrepreneurial Operating System (EOS) at TREIZE<\/a>, we really wanted to test all the components to measure their impact. In this system, Level 10 Meetings (L10) immediately stand out as a powerful lever to break down silos, solve problems faster, and keep us on track with our goals.<\/p>\n<p>Before that, some departments at TREIZE were already holding weekly meetings focused on their own issues and projects. It worked\u2026 up to a point. Information was circulating slowly, if at all, from one team to another. We didn\u2019t necessarily see the challenges facing other teams, and vice versa. We therefore knew that the L10, by bringing everyone around the same table, would represent a sizeable challenge.<\/p>\n<h2>FIRST OF ALL, WHAT IS A LEVEL 10 MEETING?<\/h2>\n<p>Level 10 Meetings are mandatory weekly meetings of 90 minutes, always at the same time during the week. They follow a fixed agenda to maximize efficiency, and the majority of the time is dedicated to solving priority problems using the \u201cIDS\u201d method (Identify, Discuss, Solve). Each participant must respect the allotted time, stay focused on critical points, and avoid distractions. Every decision made must have a person in charge and a delivery date.<\/p>\n<p>The term \u201cLevel 10\u201d refers to the rating you aim for: a meeting considered perfect by everyone, rated 10 out of 10. At the end of each meeting, each person gives a rating from 1 to 10 to evaluate the meeting\u2019s efficiency, productivity, and value. <strong>The idea is to strive for meetings that are so well organized and focused that they deserve this perfect score<\/strong>.<\/p>\n<p>The L10 agenda is always the same:<\/p>\n<ul>\n<li>Check-in (5 minutes): A quick roundtable where each person shares a standout event (personal or professional).<\/li>\n<li>People Headlines (5 minutes): The good and bad news affecting the team (hirings, departures, successes, etc.).<\/li>\n<li>Scorecard (5 minutes): A review of the agency\u2019s KPIs (key performance indicators).<\/li>\n<li>To-do List (5 minutes): Following up on the tasks assigned the previous week.<\/li>\n<li>Rocks (5 minutes): A status update on the progress of quarterly priorities.<\/li>\n<li>Issues (up to 60 minutes): The heart of the meeting: identify problems, discuss them, then solve them using the famous IDS process (Identify, Discuss, Solve).<\/li>\n<\/ul>\n<p>The most important thing is to take a moment, right from the start, to <strong>step away from the daily grind and adopt a \u201cworking on the agency\u201d rather than \u201cworking in the agency\u201d mindset<\/strong>.<\/p>\n<h2>WHO TAKES PART IN THESE MEETINGS?<\/h2>\n<p>According to EOS, the ideal is to bring together the \u201cleadership team.\u201d At TREIZE, we don\u2019t have an officially appointed director for each department, so we had to adapt by creating two L10 meetings:<\/p>\n<ul>\n<li>Main L10<strong>:<\/strong> One key person per department, responsible for representing their team\u2019s issues.<\/li>\n<li>\u201cDev\u201d L10<strong>:<\/strong> Since we\u2019re a web development agency, we have enough developers to justify a second meeting focused on more specialized technical problems.<\/li>\n<\/ul>\n<p>This structure keeps us connected to the agency\u2019s major priorities while allowing deeper discussion of more technical questions in a dedicated setting.<\/p>\n<h2>ON THE EVE OF OUR FIRST L10S: APPREHENSIONS AND THE UNKNOWN<\/h2>\n<p>Just before our first L10s, we had two major concerns:<\/p>\n<ol>\n<li>The risk of confusion<strong>:<\/strong> by mixing all the teams, we could end up with too many issues and not know where to start.<\/li>\n<li>Friction<strong>:<\/strong> by bringing up friction points that affected multiple teams, we feared creating even more tension, hurting morale and cohesion rather than improving the situation.<\/li>\n<\/ol>\n<p>Up until then, we solved problems \u201cone by one,\u201d only with the people directly involved. The idea of putting everything on the table each week, with several departments in the same room, was entirely new to us.<\/p>\n<p>The IDS method was what worried us the most. Going from small-group discussions to a big collective brainstorming session where everyone gives their opinion\u2026 we were venturing into unknown territory.<\/p>\n<p>In short, the team was torn between excitement and nervousness. We decided to run a test for a full quarter, without altering the agenda or the basic rules, to really put the concept to the test.<\/p>\n<h2>THE EARLY DAYS: MEETINGS THAT GO IN ALL KINDS OF DIRECTIONS<\/h2>\n<p>During our first L10s, we often went in a thousand directions during the Issues section. We thought we were solving a specific problem, but then discovered a whole bunch of underlying sub-problems. This \u201cput everything on the table\u201d mindset threw us off at first because:<\/p>\n<ul>\n<li>We frequently went over the 90-minute mark, going in circles on several topics.<\/li>\n<li>We were dealing with very concrete, day-to-day issues rather than the big strategic challenges we\u2019d initially imagined.<\/li>\n<\/ul>\n<p>At first, we wondered if we were \u201cwasting\u201d our L10 on details. But we quickly realized these day-to-day problems were our real issues at the time and that it was better to solve them in order to move forward more calmly afterward.<\/p>\n<h2>FRICTIONS THAT LEAD TO PROGRESS<\/h2>\n<p>With several departments together, tensions were not lacking. Each department had its own issues, and these different points of view came head-to-head during the L10. We won\u2019t lie: yes, it led to some intense exchanges. But <strong>it\u2019s precisely from these sometimes heated debates that our biggest improvements emerged<\/strong>. Even if that friction can be scary, it\u2019s welcome. After all, like in a car, you can\u2019t have traction without friction.<\/p>\n<p>This helped us realize that some problems that seemed minor for one department were actually major blockers for another. By talking them through, we found improvements that worked for everyone. Plus, having multiple complementary minds around the table helped us find solutions to issues that seemed unsolvable. <strong>We left those meetings with new perspectives<\/strong>.<\/p>\n<p>Gradually, we learned to address sensitive topics without anyone shutting down. The first few weeks were a bit rough, but we gained humility and mutual trust.<\/p>\n<p>At TREIZE, kindness is one of our values. The L10s let us see it from another angle. Everyone understood how their work could affect others. Sometimes the discussions were difficult, but they ultimately brought the team closer together. We all realized <strong>our common goal is to improve our work environment and align the agency with its vision<\/strong>.<\/p>\n<p>It took us a few months to really get comfortable with Level 10 Meetings, but the results are clear:<\/p>\n<ul>\n<li>Faster flow of information<strong>:<\/strong> instead of waiting for a major problem, we tackle topics before they even arise.<\/li>\n<li>Fewer silos, more collaboration<strong>:<\/strong> each department has a better understanding of the others\u2019 reality, and we\u2019re rowing together, in sync.<\/li>\n<li>Better responsiveness<strong>:<\/strong> issues are dealt with as a team, often permanently, rather than coming back over and over.<\/li>\n<\/ul>\n<h2>L10S: A TURNING POINT FOR TREIZE<\/h2>\n<p>Level 10 Meetings changed a lot of things at TREIZE. They prompted us to communicate differently, include every department in a shared vision, and resolve our issues collectively. In the end, we move faster, more calmly, and we\u2019re all aiming for the same objective.<\/p>\n<p>Now, we wouldn\u2019t go without them. <strong>The initial frictions have turned into real traction that brings us closer, week after week, to our shared vision<\/strong>.<\/p>\n<h2>OUR FINAL ADVICE: DIVE IN HEADFIRST<\/h2>\n<p>For any organization interested in the Entrepreneurial Operating System and worried about setting up Level 10 Meetings, our advice is simple: follow the agenda and the rules to the letter at first, be disciplined, and trust the process.<\/p>\n<p>Yes, it can feel a little strict, and some meetings will be more \u201cproductive\u201d than others. But after one or two quarters, you\u2019ll see your team making progress. People will learn to name problems at the right time, come back the following week with concrete solutions, and <strong>friction will become a true driver of improvement<\/strong>.<\/p>\n<p><em>This series of articles is about EOS, the Entrepreneurial Operating System. We invite you to dive into our journey of implementing EOS at TREIZE. Throughout these articles, we\u2019ll share not only EOS\u2019s key concepts, but especially our concrete experience, our standout successes, and the challenges we encountered along the way.<\/em><\/p>\n<p>If you\u2019d like to discuss or learn more about why we chose to implement EOS or how we went about it, we encourage you to reach out by writing to <a href=\"&#x6d;&#x61;&#x69;&#x6c;&#x74;&#x6f;&#x3a;&#x6a;&#x66;&#x73;&#x61;&#x75;&#x72;&#x69;&#x6f;&#x6c;&#x40;&#x74;&#x72;&#x65;&#x69;&#x7a;&#101;&#46;&#112;&#114;&#111;\">&#x6a;&#102;&#115;&#x61;&#x75;&#114;&#105;&#x6f;&#x6c;&#64;&#116;&#x72;&#x65;&#105;&#122;&#x65;&#x2e;&#112;&#114;&#x6f;<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When we decided to implement the Entrepreneurial Operating System (EOS) at TREIZE, we really wanted to test all the components to measure their impact. In this system, Level 10 Meetings (L10) immediately stand out as a powerful lever to break down silos, solve problems faster, and keep us on track with our goals. Before that, [&hellip;]<\/p>\n","protected":false},"author":9,"featured_media":6438,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"wds_primary_category":0,"footnotes":""},"categories":[107],"class_list":["post-6433","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-management"],"acf":[],"_links":{"self":[{"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/posts\/6433","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/comments?post=6433"}],"version-history":[{"count":2,"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/posts\/6433\/revisions"}],"predecessor-version":[{"id":6435,"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/posts\/6433\/revisions\/6435"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/media\/6438"}],"wp:attachment":[{"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/media?parent=6433"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/treize.pro\/en\/wp-json\/wp\/v2\/categories?post=6433"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}