Prepare a Focused Decision before Scheduling Thirty Minutes
A 30-minute meeting needs a defined decision and prepared information. Shortening the end time alone leaves missing evidence and an overloaded agenda untouched.
Thirty minutes is an option to test. Complex analysis or multi-party decisions may require a different duration and format.
Choose Work That Needs a Meeting
Reading an update may be handled through shared material and a question route. For live comparison or joint decisions, specify what requires the group’s time.
Atlassian’s meeting audit considers asynchronous alternatives. (Atlassian: Audit team meetings)
Reserve Time to Record the Outcome
One example allocates five minutes to context, fifteen to comparison, and ten to decisions and actions. Share substantial reading beforehand.
When discussion stalls, identify what is missing. Check the required decision and participants’ availability before extending.
Assess Outcomes alongside Duration
Record decisions, unresolved items, and any follow-up meeting needed. Repeated rework suggests the scope or preparation needs revision even if the meeting was short.
For a short public consultation, explain its purpose and preparation on the event page so visitors know what it covers.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To publish a website explaining the scope of your short consultation sessions, give SpreadSite a try!
Build a website with SpreadSite →