diff --git a/_pages/retrospective-playbook.md b/_pages/retrospective-playbook.md
index a0d7afe..b84d7c7 100644
--- a/_pages/retrospective-playbook.md
+++ b/_pages/retrospective-playbook.md
@@ -41,7 +41,7 @@ Retrospectives are a time for the team to come together and raise how they curre
 - **Regular & Scheduled**: Don’t get to the end of an iteration and go “well we should probably have a retro now” or be frantically trying to find a time in the calendar to discuss how we work. Get a regular slot in everyone’s calendars that everyone in the team can make.  
 - **Time-boxed**: Retros that run on for hour after hour can be a drag on everyone’s time and attention. Since we have the whole team in attendance we should be intentional with that time and use it appropriately. If a discussion about an issue is going on too long, consider setting up a specific follow-up session just to discuss that with the interested parties and move on to what affects the whole team.
 - **Looking inward on the Team, with only the team involved**: Identify who the team is (the people who are actively working together every day) and who should therefore be in retrospective. You should not have external observers or occasional stakeholders in the retro as they are not beholden to the actions of the retro.
-- **Structured and facilitated**: You don’t want to go into a retro and suddenly discover no one knows what you are going to do for a session. Plan out in advance who is facilitating and what activities they’ll run. In the early weeks of a team this should be someone experienced (e.g. the scrum master or team lead). As time goes on it’s great to share this around the team and get more people involved.
+- **Structured and facilitated**: You don’t want to go into a retro and suddenly discover no one knows what you are going to do for a session. Plan out in advance who is facilitating and what activities they’ll run. In the early weeks of a team this should be someone experienced (e.g. the scrum master or team lead). As time goes on it’s great to share this around the team and get more people involved. Also ensure that one member of the team, possibly the scrum master, is acting as a dedicated facilitator. It is their responsibility to ensure that the meeting stays on track and follows the structure. They should also ensure that all participants have a voice.
 - **A safe space**: It is incredibly important that every participant in the retro feels as if they can raise issues to the wider team. This is perhaps best expressed in the Retrospective Prime Directive:
 
 > **“Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.”** - Norm Kerth