90mmeeting.com · Questions & Answers

Our operations team uses Lean and our developers use Agile. Would adopting EOS mean giving those up?

Do not discard useful specialist methods simply to make every part of the company use identical language. First distinguish the operating system for the business from the methods teams use to deliver their work.

Lean practices can support process improvement. Agile practices can guide how development teams organize and deliver work. EOS addresses the shared leadership structure around direction, accountability, priorities, measurement, and issue resolution. These approaches are not automatically competing at the same level.

The recommendation to choose one business operating system is about avoiding conflicting management structures. It does not mean every department must abandon effective technical practices.

Use the EOS 90-Minute Meeting to explore the boundary. Ask where company priorities would be established, who would own them, and how departmental work would connect to those commitments. Also ask how an issue that crosses departments would reach the leadership team rather than circulating indefinitely within separate team routines.

Keep specialist methods when they support the company's shared priorities. Reconsider them when they create competing commitments or obscure accountability.

For example, a departmental delivery plan should not silently override a company priority. Equally, adopting EOS should not require the leadership team to manage every development task. The goal is one clear management backbone with appropriate methods underneath it, not one methodology forced onto every kind of work.

Category: EOS vs. Other Operating Systems

← All questions