Design the tiered meeting system and its escalation

Decide which meeting each level holds, when and what for, so what happens below reaches the top in time and each problem goes up to whoever can solve it.

The task in figures

Gives you back
0.1 h a monthper team; today it takes 0.3 to 0.8 h a month
Elmira today
Helps
Frequency
Yearly
Who does it today
Lead
How it is done today

What hurts today.

  • Meetings overlap, and information reaches the top late.

  • Nobody knows which problem belongs to which level.

  • Each team runs its meeting its own way, and they cannot be compared.

A daily management system is a chain of meetings: the team in the morning, the supervisor after, management last, each with its agenda, its board and what goes up to the next. Designing it means deciding which meeting each level holds, ordering their calendar, setting what is escalated and when, and writing the standard of each one. Without that design, meetings overlap, information arrives late and problems stay where nobody can solve them.

Done today with

  • Expert
  • In-person meeting
  • Paper and whiteboard
  • Spreadsheet
  • Slides
  • Diagramming tool
With Elmira

Each step, today and with Elmira.

Obeyaka brings the method’s meetings, each team’s briefing and debriefing and each period’s planning, with their guide and their minutes. In the app you set the day and time of each; what is escalated is still yours.

StepTodayWith Elmira
Define which meeting each level holds, what for and who attendsIn-person meeting, Slides1 h – 3 hObeyaka (web)
Order the calendar, so what happens below reaches the top firstSpreadsheet, Expert30 min – 1 hObeyaka (web)
Set what goes up from one level to the next, and whenExpert, Diagramming tool30 min – 1.5 hStill by hand
Write the standard agenda and minutes of each meetingSlides, Paper and whiteboard1 h – 2 hAutomatic
Teach it to whoever facilitatesIn-person meeting, Slides1 h – 2 hStill by hand

The conversation

No example conversation: the Obeyaka web app does it, or it comes later.