Discussion about this post

User's avatar
John Hagan's avatar

We were recently rejected by Allen Philanthropies, a major U.S. climate funder, to test whether the carbon offset market could be used to conserve old-growth forest. Our proposal stated clear, testable hypotheses. In the proposal we explained that the idea might fail for a variety of technical and financial reasons, and that reporting failure would be as important as documenting success. Maybe there were other reasons we were rejected, but we very explicitly set out to test a potential climate solution with science. All we got for 80 hours of proposal writing was “we wish you the best in your endeavors.” Rejection is the nature of our business, but a thoughtful explanation would be respectful, given the time we put into thinking it through and writing it. We are on the front lines of climate change. We at least deserve a thoughtful couple of sentences in a rejection. (We had already successfully passed the Letter of Intent phase earlier in the year.) To the author’s point, this example is a disincentive for writing proposals that rigorously test hypotheses (ideas).

Jim Bignal's avatar

A fascinating piece, Beate. Your distinction between trying to persuade people to behave better and designing systems that produce better outcomes particularly resonated with me.

We’ve reached a similar conclusion in our work on Responsible Business 2.0.

Personal responsibility matters. Values matter. Leadership matters. But we cannot simply exhort people to behave responsibly if the systems, incentives, governance and culture around them encourage something different.

That is why we’ve increasingly focused on the organisational “operating system” that shapes everyday behaviour and decision-making.

Perhaps the challenge is not simply how do we encourage responsible behaviour?

It is how do we design organisations in which responsible behaviour becomes the natural outcome of how the system works?

Really thought-provoking article.

1 more comment...

Ready for more?