Testing the practices we were all taught.
Proofweight is published by Aditya Rao. It draws on research, organizational accounts and practitioner experience across HR, organizational roles, consulting and coaching.
What we are for
Most people practices are inherited rather than tested. We put familiar practices under a stress test: what the research supports, where it conflicts, how far it travels, and what an organization can try on Monday.
What we want
Organizations that make better decisions about people, and through those decisions come closer to what they are capable of. Most never find out what they could have been, because the practices holding them back are never examined.
The cost of holding on
Every practice was a sensible answer to something once. The expensive part is rarely adopting one. It is keeping it after it has stopped working, and sometimes long after it has started working against the organization. A rating scale, a review cycle, a competency framework: each costs time, attention and trust that nobody ever totals up. We try to make that cost visible, so that keeping a practice is a decision rather than a habit.
We are curious people
Proofweight is more interested in the question than in being right about the answer. It reads the studies that disagree, says when the evidence is thin, and would rather change its mind in public than defend a position it has outgrown.
How we work
- We distinguish what research supports, what we infer, and what remains a proposition to test. Every article says which it is.
- We publish what the evidence does not support, including where that is inconvenient.
- Conclusions stay open to revision. When we get something wrong, we correct it in public.
- We use AI assistance in research and drafting, and we say so on every article.
Where our interests lie
We consult for a living. Proofweight sells nothing and takes no sponsorship, and no article here is written to support a service. If a conclusion ever lines up with work we do elsewhere, we will say so in the article itself.
Get in touch
Bring a practical question, a correction, or an example from your organization. Write to us.