How to use Process Intelligence data your team trusts

How to use process intelligence data without losing your team's trust: 3 written rules to set before the first dashboard goes live. #ProcessIntelligence #Automation #GBS Years ago, in a BPO, one employee logged "stop" almost every afternoon in a simple work-logging tool. His manager called him in for a difficult conversation. The next week his afternoons were full of process clicks, and his output was exactly the same. He was one of the most efficient people on the team: he finished his work by lunch and simply logged the truth. After one 15-minute meeting, the company lost its most honest data. In this episode of the AI Automation Dojo, Andrzej Kinastowski explains why employees assume the worst when nobody has written down how data about their work will be used, and which three rules prevent it. What you'll learn in this episode: 🔸 Why the same measurement builds trust or fear, depending only on how it is used 🔸 Why training managers is not enough, and a written, signed rule is 🔸 The Never List: 4 things process data should never be used for 🔸 Why the first response to any bad reading should be a question: "What's blocking you?" 🔸 Who should act on a finding: the process owner, not the people manager 🔸 Why your first project should fix the oldest complaint on the floor, not chase the biggest ROI 🔸 How to bring your works council a draft they can test instead of a vendor brochure Write the rules before the first dashboard. Otherwise your employees will write them for you