PPaT Wiki
DokumentationPathwayWissensdatenbankForumBlogKontakt
Week streakFOUNDATION0 badges
Sprache: Deutsch
  • English
  • Nederlands
  • Karen (S'gaw)
  • Français
  • Deutsch
  • Lea faka-Tonga
  • Te reo Māori
Community fragen

Your PaT Pathway

0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User

Practitioner

  • ○Pop-Out Chat Feature (not passed yet)
  • ○Chat reminder (not passed yet)
  • ○Chat to SD (not passed yet)
  • ○Chat to email to chat (not passed yet)
  • ○Email to chat to email – non PaT users (not passed yet)
  • ○C2E Attachments (not passed yet)
  • ○Email to BFF (not passed yet)
  • ○How SD chats work with SD Members and External Users (not passed yet)
  • ○Docked Chats (not passed yet)
  • ○Inline chats (not passed yet)
  • ○Multi-Tasks (not passed yet)
  • ○Task Integrity: what it is and why it drops (not passed yet)
  • ○Chat to task to project (not passed yet)
  • ○SD Task wall view (not passed yet)
  • ○Using SDs as a report or meeting minutes app (not passed yet)
  • ●Running Meetings with SDs (this page)
  • ○Invite Attendees (not passed yet)
  • ○Recurring tasks: create and edit (not passed yet)
  • ○Info Icons (not passed yet)
  • ○Moving Section Headers (not passed yet)
  • ○SD Element Categorisation (not passed yet)
  • ○Add any Image as a Section Header Icon (not passed yet)
  • ○Embedding SDs in SDs (not passed yet)
  • ○Assigning an SD to a new parent (not passed yet)
  • ○Filing and retrieving SDs (not passed yet)
  • ○SD Owner Functions (not passed yet)
  • ○Docking SDs and Updating Images (not passed yet)
  • ○Embedding live data in an SD (graphs and spreadsheets) (not passed yet)
  • ○PaT AI (not passed yet)
  • ○Track Engagement (not passed yet)
  • ○Share and record your screen (not passed yet)
  • ○Different Form Uses (not passed yet)
  • ○Form Wall (not passed yet)
  • ○SD Form Responses: finding and exporting form responses (not passed yet)
  • ○Video rooms: guests joining and asking to record (not passed yet)
  • ○Comprehension Audits (not passed yet)
  • ○Evidential audits: completing one (not passed yet)
  • ○LMS Architecture (not passed yet)
  • ○Safe Walks (not passed yet)
  • ○Customer-specific training: how it works (not passed yet)
  • ○How PaT Manages Inactive Users (not passed yet)
  • ○How to unlock a module for a staff member (not passed yet)
  • ○Health and safety templates (not passed yet)
  • Company Structure: adding a new user
  • Company Structure: customer companies
  • Company Structure: departments, job titles and roles
  • Company Structure: modules for a site or a country
  • Company Structure: process categories
  • Connections: linking PaT to Microsoft 365
  • Forms - API Integration
  • How to create a campaign for the PaT Lite training portal
  • How to edit an existing Bulletin Board Post
  • How to set up your SD Map
  • LMS Feedback: learner ratings and comments
  • LMS Metrics - If you can't measure it, you can't manage it
  • Manage users
  • Pacing recertifications and escalations
  • PaT Business Unit Template Overview
  • SD Workflows - Multi Submit
  • SD Workflows - Workflow Settings
  • System Activity: escalations, logins, emails and more
  • System Config: company settings
  • The org chart
  • Add any Image as a Section Header Icon
  • Assigning an SD to a new parent
  • Aufgabenintegrität: Was sie ist und warum sie sinkt
  • C2E Attachments
  • Chat reminder
  • Chat to email to chat
  • Chat to SD
  • Chat to task to project
  • Comprehension Audits
  • Customer-specific training: how it works
  • Different Form Uses
  • Docked Chats
  • Docking SDs and Updating Images
  • Email to BFF
  • Email to chat to email – non PaT users
  • Embedding live data in an SD (graphs and spreadsheets)
  • Embedding SDs in SDs
  • Evidential audits: completing one
  • Filing and retrieving SDs
  • Form Wall
  • Health and safety templates
  • How PaT Manages Inactive Users
  • How SD chats work with SD Members and External Users
  • How to unlock a module for a staff member
  • Info Icons
  • Inline chats
  • Invite Attendees
  • LMS Architecture
  • Mehrfachaufgaben
  • Moving Section Headers
  • PaT AI
  • Pop-Out Chat Feature
  • Recurring tasks: create and edit
  • Running Meetings with SDs
  • Safe Walks
  • SD Element Categorisation
  • SD Form Responses: finding and exporting form responses
  • SD Owner Functions
  • SD Task wall view
  • Share and record your screen
  • Track Engagement
  • Using SDs as a report or meeting minutes app
  • Video rooms: guests joining and asking to record
  • Activity Notifications
  • Add members and set permissions
  • AI Summary: a quick summary of an SD
  • Aufgabe erstellen
  • Aufgabenübersicht
  • Aufgabenverwaltung
  • Aufgabenverwaltungssystem
  • Capture and Manage Accidents
  • Capture and Manage Hazards
  • Chat to task
  • Chat Wall
  • Contextual Communication
  • Convert a Note to a Task
  • Create a new SD
  • Critical Chrome Extensions
  • Document Store: shared links, your folders and favourites
  • Fast Notes
  • Getting help: the PaT Helpdesk
  • Global Search
  • Gruppenchats
  • How to embed Outlook onto your PaT
  • How to resize your browser to best view PaT
  • How to use the PaT Lite training portal
  • Insert links
  • Module Learning - Desktop
  • Module Learning - Mobile
  • My Profile
  • Newbie PaT Intro – Chats and SDs
  • Notes
  • Out Of Office: turning it on, and the calendar on your Task Wall
  • Outlook 2FA Issue
  • PaT Chat – Überblick
  • PaT Mobile App – Overview
  • Preview, download and share files
  • Publish a Bulletin Board Post
  • Reading an SD in another language
  • SD Elements
  • SD Main page useful features
  • SD Overview
  • Section Headers
  • Security measures for multiple users on a device
  • Share Feedback
  • Signing in to PaT and resetting your password
  • Traffic light progress
  • Upload file attachments
  • Video calls on the mobile app
  • Automatische Eskalation
  • Build a reporting system
  • Chat Management - Pro Tips
  • Conditional Formatting
  • Configuring a UDF: columns and calculated columns
  • Configuring a UDF: filters, grouping and endpoint details
  • Customer-specific training: setting it up
  • Endpoint Manager: finding endpoints and building your own UDF
  • Form builder: field types
  • Forms - Extract Data (the AI form builder)
  • Formular-Testmodus
  • How to build modules in the Module publisher
  • How to create module comprehension audits
  • How to create module evidential audits
  • How to create module quizzes
  • How to embed an SD into the LMS
  • How to make form templates live for everyone to use
  • How to upload form elements to an SD
  • How to use the PAR SD
  • Live H&S Reporting
  • Mastering the Business Strategy Template
  • Module Admin: finding and managing modules
  • Module Completion Notification Setup
  • Module Publisher Content Options
  • PaT SD Map Overview
  • PaT SD Map Presentation
  • PaT SD Templates Overview
  • Pure Forms
  • SD Dashboard: building a dashboard
  • SD Forms
  • SD Security Settings
  • SD Template Helper Functions
  • Strategy System
  • Throttling
  • Using Chat to SD to go from being a good manager to a great one
  • Using SDs as the LMS Document
  • Wie Manager für ihre Mitarbeitenden OOF aktivieren können
  • PaT Lite: Wichtige Aspekte von PaT, die Sie verstehen sollten
  • Was ist PaT und warum ist es wichtig
  • PaT Lite: Vom Chat zur Aufgabe
  • PaT Lite: Einführung von Strategy Documents
  • PaT Lite: Kernphilosophie – Standards und taktische Umsetzung
  • PaT Lite: Intelligente Tools, die mit Ihnen mitdenken
  • PaT Lite: Die Zukunft des Unternehmens ist Kultur
  • Willkommen im PaT-Wiki
  • Ihren Arbeitsbereich einrichten
  • Ihre erste Woche
  • Strategy Documents
  • Aufgaben und Zuweisungen
  • Berechtigungsmodell
  • Chat und Diskussion
  • Formulare und Einreichungen
  • Dashboards und Berichte
  • Benutzer verwalten
  • Workspace-Einstellungen
  • Buchhaltungssystem verbinden
  • Single Sign-on
  • API-Übersicht
  • Zugriffstoken
  • Webhooks
0/46
Foundation
0/43
Practitioner
0/37
Advanced
0/20
Super User
Practitioner quizzes: 0 of 43 passed
  • ○Pop-Out Chat Feature (not passed yet)
  • ○Chat reminder (not passed yet)
  • ○Chat to SD (not passed yet)
  • ○Chat to email to chat (not passed yet)
  • ○Email to chat to email – non PaT users (not passed yet)
  • ○C2E Attachments (not passed yet)
  • ○Email to BFF (not passed yet)
  • ○How SD chats work with SD Members and External Users (not passed yet)
  • ○Docked Chats (not passed yet)
  • ○Inline chats (not passed yet)
  • ○Multi-Tasks (not passed yet)
  • ○Task Integrity: what it is and why it drops (not passed yet)
  • ○Chat to task to project (not passed yet)
  • ○SD Task wall view (not passed yet)
  • ○Using SDs as a report or meeting minutes app (not passed yet)
  • ●Running Meetings with SDs (this page)
  • ○Invite Attendees (not passed yet)
  • ○Recurring tasks: create and edit (not passed yet)
  • ○Info Icons (not passed yet)
  • ○Moving Section Headers (not passed yet)
  • ○SD Element Categorisation (not passed yet)
  • ○Add any Image as a Section Header Icon (not passed yet)
  • ○Embedding SDs in SDs (not passed yet)
  • ○Assigning an SD to a new parent (not passed yet)
  • ○Filing and retrieving SDs (not passed yet)
  • ○SD Owner Functions (not passed yet)
  • ○Docking SDs and Updating Images (not passed yet)
  • ○Embedding live data in an SD (graphs and spreadsheets) (not passed yet)
  • ○PaT AI (not passed yet)
  • ○Track Engagement (not passed yet)
  • ○Share and record your screen (not passed yet)
  • ○Different Form Uses (not passed yet)
  • ○Form Wall (not passed yet)
  • ○SD Form Responses: finding and exporting form responses (not passed yet)
  • ○Video rooms: guests joining and asking to record (not passed yet)
  • ○Comprehension Audits (not passed yet)
  • ○Evidential audits: completing one (not passed yet)
  • ○LMS Architecture (not passed yet)
  • ○Safe Walks (not passed yet)
  • ○Customer-specific training: how it works (not passed yet)
  • ○How PaT Manages Inactive Users (not passed yet)
  • ○How to unlock a module for a staff member (not passed yet)
  • ○Health and safety templates (not passed yet)
  1. Dokumentation
  2. Practitioner
  3. Running Meetings with SDs

Diese Seite wurde noch nicht übersetzt und wird daher auf Englisch angezeigt.

Running Meetings with SDs

Summary Strategy Documents (SDs) have built-in functions for running meetings and taking minutes. This module explains the difference between a well-run meeting and a poorly run one, why…

Auf dieser Seite
  • Steps
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Taking professional minutes
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Step 9
  • Solving recurring problems for good
  • Step 10
  • The flow of a meeting
  • Step 11
  • Step 12
  • Step 13

Summary Strategy Documents (SDs) have built-in functions for running meetings and taking minutes. This module explains the difference between a well-run meeting and a poorly run one, why professional minute-taking matters, and how to tell Notes (for record-keeping) from Action Points (tasks with deadlines). It covers the CAPS method for keeping control of a meeting, and how to solve recurring problems permanently with problem-solving frameworks, training, inspections and audits, so the minutes become a living document with a clear historical timeline.

Steps

Introduction. The ability to run a meeting professionally is an incredibly valuable skill. SDs have built-in functions that enable advanced meeting management and minute-taking, and this module explains how to use SDs to run meetings effectively.

Step 1

First, understand the difference between a well-run meeting and a poorly run one. A great meeting looks like this: - It has a clear agenda, so new notes and action points are recorded logically and a detailed history of updates is kept. Anyone can review the minutes at any time and quickly understand the current status of discussions and decisions. - The Meeting Owner controls the session: sticking to the timeline, keeping discussions on track, and quickly halting any off-topic or branching conversations. - The minute taker makes sure every point is clearly put and understood before moving on, even pausing the meeting to clarify details if necessary. They tell notes (information for posterity) apart from action points (tasks assigned with deadlines). - A robust meeting management system makes it easy for anyone to review the history of discussions and agreements, which gives transparency and continuity.

Step 2

Most people run poor meetings. Companies that have studied the issue report these figures (the source is in brackets): - 72% of meetings are ineffective (Atlassian). - 47% of employees believe that meetings are the primary time-waster during their workday (Drexel Home). - 72% of meetings are deemed ineffective, making them a significant barrier to productivity (Fortune). - 67% of employees believe that spending too much time in meetings hinders their productivity (Flowtrace - Company Analytics). - Approximately 71% of all meetings are considered unproductive, leading to significant time wastage (Pumble). - 70% of meetings prevent employees from working and completing their tasks, a direct negative impact on productivity (Otter.ai).

Step 3

Poorly managed meetings display one or more of these traits: - Lack of a clear agenda: meetings start without a structured agenda or objectives, leading to aimless discussions and unclear goals. - Talk without action: meetings turn into talkfests, with lots of conversation but minimal, poor-quality or no note-taking. Attendees leave without clear takeaways or actionable steps. - Failure to progress work-in-progress (WIP) items: instead of existing WIP items being updated to build a history of discussions, issues are often deleted, or brought up again at the next meeting with no context of what was discussed before. This lack of continuity creates confusion and stalls progress. - Inconsistent or vague note-taking: notes are unclear or lack enough detail. When they are revisited, attendees struggle to recall the original intent, which leads to miscommunication and wasted time.

Step 4

Poorly managed meetings can also display these traits: - Inability to distinguish between notes and action points: general notes (for record-keeping) are not kept apart from action points (specific tasks assigned to individuals, with deadlines). - Ineffective action point management: action points are not assigned, not tracked or have no deadlines, resulting in incomplete tasks and a lack of accountability. - Lack of follow-through: there is no system to revisit past decisions, track ongoing issues or keep a history of discussions, so conversations repeat and initiatives stall. - Weak leadership during meetings: the meeting owner doesn't steer the conversation, so the meeting veers off-topic, branches into side conversations or loses focus. - No accountability: attendees are not held accountable for assigned tasks, and there is no system to make sure commitments made during the meeting are followed through.

Taking professional minutes

Step 5

Professional minute-taking is a vital skill, especially for Customer Service (CS) staff and leaders responsible for Business Units. The term "minutes" comes from the Latin minuta scriptura, meaning "small writing": the precise recording of key discussion points. Done well, it builds trust, clarity and accountability, and greatly improves how effective meetings are. Most staff lack formal training in running effective meetings, which results in "talkfest" sessions: lots of discussion but few meaningful outcomes. Without structured minute-taking, these meetings often waste time and only create an illusion of progress.

Step 6

Meetings are costly. With employee costs averaging $40-$60 per hour, a one-hour meeting with three people can easily cost $150. Most companies earn only a 5% net profit, so they need to sell $3,000 worth of products or services to pay for a one-hour meeting. Given these tight margins, meeting time must deliver real value. High-quality minutes support a clear agenda, record key decisions, set action points and make sure there is follow-up. They provide a reliable record that prevents misunderstandings and promotes accountability. Staff who apply these practices in their meetings raise their professionalism and build greater trust with customers and colleagues.

Step 7

Minutes record two types of items: - Notes record general information and context, with no follow-up. - Action Points assign tasks to individuals, with deadlines. The rule is simple: if a task with a deadline is required, record it as an Action Point; otherwise, record it as a Note. Tip: in minute-taking, "posterity" means creating a clear, permanent record of discussions and decisions for future reference. It preserves key information, prevents disputes and makes handovers smooth. You need to know this word to run meetings professionally.

Step 8

Control the meeting with the C-A-P-S method. It keeps control and clarity during meetings, so they have productive outcomes: - C - Control the flow: set clear expectations at the start, explain your role as the minute taker, and manage side conversations by bringing them back to the agenda. Don't hesitate to interrupt discussions if you need to catch up or clarify. - A - Apply the rule: record any tasks discussed with specific deadlines as Action Points. If there's no task or deadline, record it as a Note. - P - Pause: if you're falling behind on note-taking, pause the meeting briefly to catch up, so your records stay accurate. - S - Stop: stop the meeting whenever you're unclear about what's been said or recorded. Asking questions is essential for accuracy and mastery: confident professionals clarify uncertainties to avoid misunderstandings later.

Step 9

When a new issue comes up during a discussion, record it in a structured way: - As a Note: record it clearly. Document the issue factually and succinctly, and note who identified it and when. - As an Action Point: give it a meaningful title, and fill out the description if the title needs more context. Try to enter a realistic date, as this sets expectations. If it's difficult to judge, give it your best shot and rely on the deadline negotiation process in PaT.

Solving recurring problems for good

Step 10

When recurring problems arise, think strategically to address their root causes, not just the symptoms. Anyone can record issues: be the person who solves them. Go the extra step and use the tools PaT provides, such as problem-solving frameworks, training, audits and automated follow-up: \1. Problem solving: determine the root cause. If it is not obvious, use the 5 Whys template in PaT. \2. Design the corrective action(s): most issues come down to poor training or poor planning. If the training is there, decertify the people involved and make them retrain. If it isn't, task the Head of Department to build it. If it's a planning issue, task the supervisors to make sure the employee has a working knowledge of the BFF and Outlook blocking. \3. Inspection and follow-up: decide whether ongoing inspection is needed to ensure compliance. If it is, task the appropriate stakeholder to set up regular inspections and audits. Inspections verify that standards are consistently met, while audits review how effective those inspections are, from an independent perspective. Follow these steps and you will fix any human-dependent process issue permanently. This is the holy grail of management.

The flow of a meeting

Step 11

In the meeting, start at the top of the minutes and work your way down, with three key actions: \1. Close off completed tasks. If a task isn't complete, update it in its chat thread. \2. Review existing notes. Decide whether each note stays active or is archived. If you keep a note open, add chat comments to build its historical context. \3. Add new tasks and notes: a Note if you need to add something for posterity, or an Action Point if something needs to be done by someone by a certain date and time. This keeps everything clear, actionable and aligned with the strategy.

Step 12

The end goal is a living document that: - anyone can access at any time, to see exactly where everything stands; - builds a structured historical timeline through chat threads and notes. Learning this process takes time, but it leads to efficient, high-impact meetings.

Step 13

Best practice for professional minutes: use the CAPS method. Where Action Points are needed, step up and go the extra mile by asking whether any of these is needed: - problem solving (use the 5 Whys template); - tasking Department Heads to build LMS modules, where that is identified as the fix for a root cause; - tasking supervisors to upskill their staff in using the BFF and Outlook blocking, where that is identified as the fix for a root cause; - tasking Business Unit leaders to create inspections and audits, to fix a human-dependent process permanently.

Check yourself

Checking your PaT sign-in…

ZurückRecurring tasks: create and editWeiter Safe Walks

Auf dieser Seite

  • Steps
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Taking professional minutes
  • Step 5
  • Step 6
  • Step 7
  • Step 8
  • Step 9
  • Solving recurring problems for good
  • Step 10
  • The flow of a meeting
  • Step 11
  • Step 12
  • Step 13
PPaT Wiki

Dokumentation, Wissensdatenbank und Community-Support für People and Tasks.

Dokumentation

  • Erste Schritte
  • Grundkonzepte
  • Integrationen
  • API-Referenz

Support

  • Wissensdatenbank
  • Community-Forum
  • Kontakt
  • Dienststatus

Unternehmen

  • PaT
  • Blog
  • Nutzungsbedingungen
  • Datenschutz

© People and Tasks. Alle Rechte vorbehalten.