1️⃣ Give the new hire a route to useful work Microsoft’s remote-onboarding research recommends a named buddy and, for developers, a simple first task to learn the workflow. Documents alone do not explain how the team gets work done.
💡 Why it matters Set an initial deliverable and name who can unblock it. Check role expectations with the manager, not just HR.
☕ Coffee talk Can your newest hire finish a small piece of work without having to discover the organisation first?
2️⃣ Write the failure story before kickoff Gary Klein’s premortem asks a team to assume the project has failed and explain why. McKinsey’s account then turns those vulnerabilities into changes to the plan.
💡 Why it matters Give the highest-priority risks an owner and a mitigation deadline before committing to the launch plan.
☕ Coffee talk Which launch dependency still has nobody responsible for checking that it will hold?
3️⃣ Keep the estimates made before everyone agreed In a 2011 experiment, seeing other people’s estimates narrowed the spread of answers and raised confidence without improving group accuracy. Agreement was a poor test of correctness.
💡 Why it matters Collect forecasts privately before discussion. Keep that baseline so later convergence has to be explained.
☕ Coffee talk Did the sales forecast improve after the meeting, or did everyone just move towards the same number?