Skip to content
Lab651 Process

EOS with Engineers

Once a week the Head of Engineering meets with the employee engineers in an L10-style meeting. The meeting format has been slightly adjusted to facilitate conversations and support the way the team works. The goal is to bring the team together even though they generally work on separate projects. There is a meeting in ninety.io named “Engineering.” All items regarding the engineering team should be placed in this meeting.

L10

Section titled “L10”

The timings of most sections have been adjusted from the standard EOS format. The number of minutes in parentheses after the section name.

  1. Segue (20) — This is the biggest change in terms of time and structure. Instead of going around the table and people stating what they did, one engineer (different each week) asks the “question of the week.” The questions can be about anything (besides politics). The engineer who asks the question for one week will choose the next engineer to ask the question the following week. No one is immune to being picked.
  2. Data (5) — This contains the weekly percentage of billable hours for each engineer. The number is based on billable hours divided by 40.
  3. Rocks (15) — This section contains at least 2 rocks for each engineer. One rock is always “84%” (the billable goal). The other rock(s) is as normal for the quarter.
  4. Headlines (5) — This will contain meeting announcements and conference dates.
  5. To Dos (5) — As normal.
  6. Issues (20) — As normal.
  7. Conclude (5) — As normal.

Rocks

Section titled “Rocks”

Engineering leadership works with the engineers to define rocks that help their career and personal goals. The rocks should be a topic about which the engineer is passionate. A common suggestion is a rock that involves learning and/or presenting technologies/methods to the company. For new technologies/methods, a learning rock can be in one quarter and the presentation rock can be in the next quarter. For presenting known technologies/methods this should fall into just one quarter. Personal rocks are also encouraged, with the suggestion that they define a way to share it with the company as an end goal. For example, if an engineer wants to complete their IFR training (a personal goal which is fully supported), at the end they would give a lunch-and-learn about what an IFR actually is. The goal is to facilitate the core values.

Section titled “Related”
  • EOS Best Practice — EOS books, ninety.io, and offsite cadence
  • EOS — EOS introduction and accountability chart