Reliability and validity: can this measure support your conclusion?
Reliability concerns the consistency or precision of measurement under relevant conditions.
Foundation guide
Make change workable for the people and systems it affects.
New to this subject? Start here
Reliability concerns the consistency or precision of measurement under relevant conditions.
Foundation guide
Before acting on a management claim, identify exactly what it says, trace it to its original evidence and ask whether the method supports that conclusion in a relevant setting.
Playbook
A useful management literature search starts with a decision question, records how evidence was found and selected, and brings findings together by concept.
Playbook
Continuous improvement is a repeatable way to examine a problem, try a bounded change, study what happens and decide what to keep or investigate next.
Playbook
A team handoff is complete when the receiving team can understand the work, accept the relevant responsibility and take the next action.
Playbook
A process workshop should produce a shared account of current work, a defensible improvement question and an owned next test.
Playbook
Organization design connects the work an organization must accomplish with its roles, decisions, coordination, capabilities and incentives.
Playbook
Improve employee experience by investigating a specific part of working life, changing the service behind it and checking whether people can complete their work more easily.
Playbook
Organizational ambidexterity means being able to improve an established business while exploring opportunities that need different assumptions, routines and measures.
Framework
Connect training to specific tasks, supported practice, feedback and working conditions, then check application over time without treating 70/20/10 as a rule.
Playbook
Plan an open Knowledge Café question, small-group conversations and a whole-group reflection, with clear boundaries and a useful route for follow-up.
Method
Map new tasks to observable behaviour, assess evidence with clear limits and choose development or workplace fixes that address the actual gap.
Method
Plan a software rollout around real tasks, handoffs, permissions, practice and support, then use a bounded pilot to make the expansion decision.
Playbook
Build a candid change story around the reason, consequences, uncertainty and next actions, then check it with the people whose work will change.
Playbook
Use insights, options and experiments to change a working routine, with clear participation, decision rights, feedback and criteria for the next step.
Playbook
Use Kotter's eight steps as questions, not a recipe: build urgency from checkable evidence, involve people who know the work, and see where the model differs from ADKAR.
Framework
Learn what psychological safety is and is not, what the research supports, and which leader and meeting habits help a team raise questions, mistakes and dissent early.
Foundation guide
Treat pushback as information: sort objections into flaws, losses, workload, history and practical obstacles, check each one, and choose a fair response.
Playbook
See a new idea from the adopter's side with Rogers' diffusion theory: perceived attributes, the decision process, peer networks, adopter categories and when saying no is rational.
Framework
Plan World Café questions, rounds, table hosts and a harvest, then use the results honestly: as the views of those present, with clear decision boundaries and follow-up.
Method
Use Schein's cultural levels to investigate routines, stated values and assumptions without labelling people or pretending one survey explains a company.
Playbook
Choose a focused collaboration, clarify what each partner contributes and plan how external knowledge will become usable work inside the business.
Playbook
Clarify a change assignment before promising a workshop or rollout. Agree outcomes, decision rights, responsibilities, boundaries and when to revisit the brief.
Playbook
Use a practical workplace example to distinguish correcting an action from reconsidering the goals, rules and assumptions that guide it.
Comparison
Plan around the questions people need answered, connect messages to real work, and give feedback an owner instead of just another inbox.
Playbook
Plan a useful handover by identifying critical know-how, choosing appropriate transfer methods and checking that the next person can actually use it.
Playbook
Explore the different questions behind innovation and organizational change, and connect early experiments with the work of putting an idea into use.
Comparison
Before introducing a new way of working, find out whether people share the commitment, confidence and practical conditions to make it happen.
Playbook
Why a widely repeated failure statistic is a weak planning assumption, and how to evaluate change with clearer questions.
Perspective
A careful guide to Awareness, Desire, Knowledge, Ability and Reinforcement, including where the model needs support.
Framework
Imagine a plan has failed, uncover plausible causes, and turn the most consequential risks into actions before launch.
Method
Identify who is affected, who can influence a change, and which conversations must happen before the next decision.
Method
Run a participant-led conversation with a visible topic queue, simple voting, time checks, and clear follow-ups.
Method
How to diagnose, support and sustain changes in everyday work without reducing adoption to communication.
Foundation guide
Try a different area, subtopic or format.
Begin with the work that will change for a particular role. Then identify affected people, investigate readiness and match support to the actual obstacle. Keep individual adoption, organizational conditions and evaluation connected without treating them as the same problem.