diff --git a/examples/ecs/ecs_guide.rs b/examples/ecs/ecs_guide.rs
index 5acefd456e..05f5dd1a1b 100644
--- a/examples/ecs/ecs_guide.rs
+++ b/examples/ecs/ecs_guide.rs
@@ -1,6 +1,7 @@
 use bevy::{
     app::{AppExit, ScheduleRunnerPlugin, ScheduleRunnerSettings},
     ecs::schedule::ReportExecutionOrderAmbiguities,
+    log::LogPlugin,
     prelude::*,
     utils::Duration,
 };
@@ -338,9 +339,10 @@ fn main() {
             game_over_system.system().after(MyLabels::ScoreCheck),
         )
         // We can check our systems for execution order ambiguities by examining the output produced
-        // in the console by adding the following Resource to our App :)
+        // in the console by using the `LogPlugin` and adding the following Resource to our App :)
         // Be aware that not everything reported by this checker is a potential problem, you'll have
         // to make that judgement yourself.
+        .add_plugin(LogPlugin::default())
         .insert_resource(ReportExecutionOrderAmbiguities)
         // This call to run() starts the app we just built!
         .run();