Borrowing "Is anyone better off?" Means Answering It First
Is anyone better off?
Ask that question after a summary of activities, and it does something specific. It moves the conversation from effort to effect. A count of what got done, however accurate (fidelity), doesn't answer it. Neither does a description of how well it was done. The question isn't about the work itself. It's about whether anything changed for the people the work was supposed to reach. That's a structural difference: doing more of something and something actually working are not the same claim, even when they get treated as if they were.
"Is anyone better off?" is a question As-I-Am Consulting Group borrows from Mark Friedman's Results-Based Accountability framework. It's one of three questions the framework asks about any piece of work: "How much did we do?", "How well did we do it?", "Is anyone better off?" The first two measure effort. The third measures effect. The framework's own materials call this the most important distinction: between what an organization does and whether anyone is better off, the difference between effort and effect. I first encountered this framework during my postdoc, and that distinction, effort against effect, stated plainly, is what stayed with me. It was an affirmation of the experiences that drove me towards community psychology. AsIAm didn't invent this question and doesn't need to. Some frameworks are worth adopting whole, distinction included, rather than rebuilt from scratch.
Borrowing a question isn't the same as citing it. If you adopt someone else's standard, you don't get to apply it only outward. Asking a client whether anyone is better off, while exempting your own work from the same standard, isn't accountability. It's theater with better vocabulary. A firm can say the right things about other people's programs and still flinch at applying the same measure to itself, and that gap is exactly where the theater lives. Once the question is loose in a conversation, it measures the person asking it before it measures anyone else in the room. That includes the shape of the work AsIAm takes on, and which engagements get accepted.
The harder version costs something. It means deciding in advance what happens when your own answer is no, before the meeting where that answer might matter, not inside it. It also means the standard has to survive an engagement you already want, not just one you were inclined to decline anyway. A standard improvised under the pressure of a proposal already half written doesn't hold. That's the difference between a standard and a sentiment: a standard survives contact with an inconvenient answer. One of my mentors in undergrad told me, "not all money is good money." Not every engagement is worth taking, and knowing that ahead of time is what makes the standard mean something later. None of this requires knowing in advance which engagement the standard will apply to. It only requires knowing, ahead of time, that it will apply to some of them.
This isn't abstract for me. Here it is in my own words, unedited:
"It hasn't happened on a real call but if something isn't a fit I'd rather be honest about it than try to make it work. Also given this endeavor is born out of frustration, I wouldn't entertain any engagement that seeks to maintain the status quo or simply isn't willing to go the distance to answer the question 'Is anyone better off?'"
A policy that hasn't been tested is worth less than a track record. Publishing it anyway is what makes it checkable later.
I think something similar is true of how research gets shared: the work that reaches people is disproportionately the work that came out "significant," while the rest goes quiet. I'd rather ours didn't. Publishing an untested policy anyway is a bet that someone can hold it up against what actually happens later, instead of it quietly disappearing.
Some of this is written down independent of that admitted policy. AsIAm's approach page lists "Structural over symbolic" as a public commitment, one anyone can check against what actually happens. The discovery process ends, before any proposal is written, by naming what has stood in the way before. That standard matters more for a firm whose job is building someone else's capability than for one selling a static report, because the promise is capability transferred, applied by the client after AsIAm leaves. Underneath all of it is one promise meant to hold across every engagement: we leave behind capability, not dependence. A commitment that isn't written down publicly isn't a commitment. It's a preference.
If you want to find out what "Is anyone better off?" would turn up in your own work, start with the Symbolic-to-Structural Assessment, one of AsIAm's three Diagnose-tier offerings. It's an assessment: no outcome promised in advance, because none should be.
