It’s Thursday, and the team is running user acceptance testing (UAT) ahead of Monday’s ERP launch. Sales tries to confirm two orders at the same time. Both reserve the last unit, but the warehouse has only one to ship. The consultant who spotted the problem can’t reproduce it every time, and the project manager has just told the client the rollout is on track.
In this fictional case, I want to know whether the person who spotted the problem will raise it while some facts are still unclear. Then I want to see how quickly the team can turn the report into a decision. That tells me more about an ERP team’s performance than a count of the tasks it closed that week.
What Google found in its teams
Project Aristotle studied 180 teams inside Google, including 115 engineering project teams and 65 sales teams. Google assessed effectiveness from several perspectives, including executives, team leads, and team members, as well as sales against quota. Psychological safety stood out among the factors associated with effectiveness in its data. The others were dependability, clarity about goals and roles, a personal sense of meaning, and a sense that the work made a difference. The findings describe associations in the organization Google studied. Google re:Work on Project Aristotle
FlowHR offers a separate set of practices for managers. Talk with team members regularly, make it easier to raise hard issues, clarify goals and roles, recognize specific contributions, and keep workloads manageable. I’d try those practices in one ERP test cycle while keeping the acceptance criteria the client and project team agreed on. FlowHR’s five practices for a high-performing team
When someone reports a double reservation
If I were leading the team, I’d say, “Thanks for bringing this up now. Let’s pull up both orders. What do we know so far, and who can help check the rest?” Let the person who found the issue walk through what they saw, what they can reproduce, and what they’re still unsure about. The project lead can acknowledge having called the rollout ready too soon if the test results were incomplete. How the lead responds in that moment tells the team what happens when someone raises a problem.

Put the technical lead in charge of investigating and proposing a fix. Ask the consultant to set up the retest and the client’s sales and warehouse staff to confirm what should happen when two orders compete for the last unit. The project manager records the impact and brings the evidence to the person authorized to approve go-live. The team knows who fixes the issue, who tests it, and who makes the decision. Read more about decision rights on an ERP project
Agree in advance on the evidence needed to approve go-live. In this example, the second order must be unable to reserve the same unit, and sales must see a status that matches what the warehouse sees. If the result is still unverified at the decision deadline, the approver can consider delaying the affected workflow or limiting the rollout to a part that can be isolated safely with the client’s agreement.
Try a 20-minute review this week
Pick one client workflow, such as handling an order and reserving stock. Use the team’s existing board to record anything affecting delivery, with the evidence, an owner, and the date for the next check. I’d follow up privately on issues people hesitate to raise in front of the group. Anything that puts go-live at risk should go through the project’s agreed reporting channel right away.
| Time | Question to ask | What to leave with |
|---|---|---|
| 5 minutes | What does the client need to be able to do by the end of the week, and what evidence do we have? | A shared target and the current test status |
| 10 minutes | What’s still at risk, and who can help answer the open questions? | An owner, retest criteria, and a decision deadline |
| 5 minutes | What should move off the schedule to make room for testing, and who helped the team spot a problem earlier? | A workload the team can manage, plus recognition tied to a specific action and its effect. Reporting the double reservation gave the warehouse more time to investigate before launch. |
Measure delivery and how the team works
Try this on one project for two weeks and compare it with a similar work cycle. Look at critical tests passed out of those agreed, issues that had to be reopened, time from first observation to the team learning about an issue, and the team’s after-hours workload. If more issues are reported, look at their severity and when they were raised. The team may be finding problems faster, or more problems may actually be occurring.
Ask team members if there was anything they wished they’d brought up sooner and what held them back. Then choose one change. You might pair a developer and a consultant before sending a case to the warehouse for testing, or defer a report so the team can finish a critical test. Start the 10-part Building Teams series with Episode 1 on psychological safety