How To Set Up Weekly Performance Standups

Purpose:

To help manufacturers build a consistent rhythm around their data by implementing a short, weekly standup focused on key performance indicators (KPIs) captured in Caddis. This fosters a culture of accountability, visibility, and action on the shop floor.

Outcomes:

• Rapid visibility into what's improving or slipping
• Increased accountability across departments
• Quick action on performance issues
• Better use of Caddis insights in real time

Tools You’ll Use in Caddis:

• Downtime reports (especially excessive downtime)
• Cycle time trends
• Preventive Maintenance (PM) schedules and completion status
• Run vs. downtime breakdowns by equipment
• Tagged data (e.g., Operator, Part Number, Job Number)
• Notes entered during events

Caddis does not track idle time, but it does track run and downtime. Run time is triggered by cycles. Downtime is categorized as standard or excessive, with thresholds defined per equipment.

Notes and tagging are powerful but must be applied at the point of an active run. Common tag categories include Operator, Part Number, and Job Number—ideal for understanding how production variables influence performance trends.

Who Should Attend:

• Supervisor
  
  • Prioritization, team oversight
• Operator Rep
  
  • First-hand insight on issues
• Maintenance
  
  • Visibility on machine issues + PMs
• Caddis Champion
  
  • Drives meeting structure and data prep

When to Meet:

• Every Monday or Friday, 15-20 minutes
• Stand in front of a screen or printed dashboard
• Optional: hold additional 1-on-1 follow-ups afterward

Sample Weekly Agenda:

1. Downtime Recap

- Which machines had excessive downtime? - Any patterns by shift, operator, or part? - Were notes and tags entered?

2. PM Completion

- Which PMs were missed? - Do we need to adjust frequency or ownership?

3. Performance Trends

- Any change in average cycle time for high-volume parts?  - Any jobs running slower than expected?

4. Wins & Root Causes

- What did we fix or improve last week? - Were 5 Why’s done for any critical failures?

5. Quick Hits

- Any blockers we need to remove today?

ℹ️ Tip: Use the 5 Why’s Playbook as a follow-up process for any issue surfaced in this meeting.

🔄 How to Prepare for the Meeting:

1. Run Reports in Caddis:
   
    
   • Downtime summary by equipment
    
   • Cycle time report (tagged by part, if available)
    
   • PM status report

1. Highlight Exceptions:
   
    
   • Flag machines out of normal range
    
   • Spot gaps in tagging or note entries
2. Print or Display:
   
    
   • Bring dashboards or summaries visible to the team

Track Success Over Time:

Common Pitfalls (and Fixes):

• Meeting drifts off topic
  
  • Use agenda as script, assign facilitator
• No clear follow-up
  
  • Assign action items with owners before leaving
• People don’t take data seriously
  
  • Review trends visibly each week—let data tell the story
• Tags/notes are incomplete
  
  • Coach operators weekly, reinforce good habits

What Success Looks Like:

• The team anticipates standup and brings real input
• Data is trusted and guides priorities
• Wins are celebrated ("zero excessive downtime on Machine 3!")
• Small problems get addressed before they snowball

🔄 Combine with Playbook 1(Get the Facts) and Playbook 5 (5 Why's) to drive a strong continuous improvement rhythm.

📍 Pro Tip: Keep a whiteboard or shared doc of ongoing issues being tracked from standups. This helps with:

• Visibility
• Avoiding dropped tasks
• Accountability without micromanaging