Applied Human Conduct Review — Monthly Newsletter No. 0002

Editor's Note

After a naming ceremony at the community hall on our street last Saturday, the older women began stacking the plastic chairs, as they always do. A girl of about seven wanted to help, but the chairs were taller than she was. One of the women did not send her away. She gave her a job instead: "You count. Tell us when we reach one hundred and twenty." So the girl stood by the wall and counted every chair out loud as it went onto the pile, and the women, who could have finished faster without her, slowed down a little so that she would not lose her place.

I have spent much of my working life with numbers, and I notice how often we judge a group by its average. The average walker, the average employee, the average new hire. Averages are useful. But the health of a community is usually decided somewhere else: at its edges, by what happens to the person who is slowest, newest, or least like everyone else. A group that only works for its middle is not quite a group yet.

This month's three picks all look at those edges. One follows neighborhood walking groups and asks what keeps the least active members walking. One follows a person stepping back from a difficult teammate and asks how the teammate on the other side feels. One follows hiring panels that welcome candidates unlike the existing team, and asks what those new people change, and what they need in order to stay. In each case, making room for the person at the edge cost something, and the cost was often carried by someone other than the person who gained. What I find hopeful is that nobody had to be a hero. Somebody only had to make a small arrangement and keep to it.

At the end, the girl announced, "One hundred and nineteen." There was a short silence while everyone looked at the pile. Then one of the women found the last chair behind the door, carried it over, and set it down slowly enough for the girl to say, "One hundred and twenty." They all clapped, and she went home, I am sure, convinced that the chairs could not have been stacked without her. I think she was right.

— I.A.

This Month's Picks

1. Nobody Walks Alone

Shared Quests, Not Individual Points or No Game Layer: Group Goal Pools in AI-Coached Community Walking and the Members Who Fall Behind (Issue No. 0010)

Many fitness apps give you points for your own steps. That may suit some people. It does little for the neighbor who is just getting started and is already behind everyone else. This study asks what happens when an AI coach counts a walking group's progress together instead of each person's.

Community centers in four towns formed 48 walking groups of five or six adults, 276 people in all, for a 16-week program. All groups used the same AI coach, and each group was randomly given one of three designs. In "shared-quest" groups, the coach set one weekly distance target for the whole group, showed only the group's combined progress, and suggested that members walking ahead of their usual pace invite another member along. In "individual-points" groups, each person earned points for their own distance, visible only to them. A third set of groups had no points or targets. In weeks 13 to 16, 62 percent of shared-quest members were still walking at least three times every week for 20 minutes or more, against 51 percent with individual points and 49 percent with no game. Among members who had started in the least active third, the figures were 48, 39, and 40 percent. Among members who agreed to have joint walks tracked, shared-quest members took 1.9 walks a month together with another member, against 1.5 and 1.6.

I spoke with one of the authors, P. Kowalska-Tan.

Editor: The headline numbers are good, but what I wanted to ask about was the least active members. Why look at them separately?

P. Kowalska-Tan: Because an average can rise while the people at the bottom quietly stop coming, and in a walking program those may be the members with the most to gain, so we ranked members within each design by how much they walked in the first two weeks and followed the least active third on its own. The benefit appeared to reach them about as much as it reached the group as a whole.

Editor: What do you think was happening?

P. Kowalska-Tan: We expected the invitation to matter, since a walk with a slower neighbor counted for the group just as much as a fast walk alone, so a strong walker lost nothing in the group's score by bringing someone along, only some of their own pace. The joint-walk figures fit that, though we did not record who invited whom.

Editor: Someone must have paid for this.

P. Kowalska-Tan: The most active members did, because in shared-quest groups they walked about 6 percent less than the most active members of individual-points groups, 24.1 kilometers a week against 25.7, and 8 of 31 said that at least once they had felt they were carrying the group. That deserves to be taken seriously.

Editor: And the limits?

P. Kowalska-Tan: The least active thirds had only about 30 people in each design, so the differences between them rest on roughly three people each, which makes them imprecise. We asked only shared-quest members about "carrying," so we do not know how often active members elsewhere felt the same, and a step counter records distance, not effort, so a slower member's walk may have been harder than it looks. Members also knew which design their group had.

Editor: What would you say to someone who organizes a walking group, or any group?

P. Kowalska-Tan: Count the group's progress, not only each person's, and give your strongest members an easy way to bring someone with them. Then check in with those strong members too.

I like this study because it does not ask for heroics. It changes what counts, and more people kept walking. A good arrangement can make kindness the easy choice, and it can also notice the people who carry a little more.

— I.A.

2. Stepping Back Without Shutting Out

Phased Disengagement, Not an Abrupt Cut or Sustained Engagement: Stepping Back from a Difficult Teammate and Short-Term Team Throughput (Issue No. 0008)

Most of us have worked with someone we simply could not work well with. Common advice says either keep trying for the team's sake, or cut contact to protect yourself. This study looks at a third path, and at two parties the usual advice forgets: the rest of the team, and the colleague on the other side.

Researchers followed 188 teams in ten organizations where one member reported a persistently difficult relationship with a teammate. They compared three approaches. "Phased" members reduced optional contact over six weeks or more and formally handed at least one shared task or channel to someone else, on record. "Abrupt" members cut contact to the minimum within two weeks, with no handover. "Sustained" members kept full engagement. In the first eight weeks, teams whose member phased out kept 97 percent of their usual output. Teams after an abrupt cut ran at 80 percent, and teams where the member kept full engagement at 95 percent. The abrupt teams also had more reopened work (6.2 items per 100 completed, against 4.9). Of the 142 teammates on the other side who answered a survey, those whose colleague had stepped back abruptly felt more shut out of the team's work (4.5 out of 7) than those whose colleague had phased out (3.5). Where nothing changed, the figure was 3.2.

I spoke with one of the authors, K. Adeyemi-Voss.

Editor: The person stepping back is usually the one we worry about. How did they do?

K. Adeyemi-Voss: At six months, phased and abrupt members reported about the same exhaustion, 3.6 and 3.5 out of 7. Members who kept full engagement reported 4.4. So both ways of stepping back went with less exhaustion. The difference was in what happened to everyone else.

Editor: Why do you think the teams did so differently?

K. Adeyemi-Voss: The handover is the likely reason. Work that ran between the two people has to go somewhere. In abrupt cases nobody took it on. In phased cases someone took it over. We cannot separate the slow pace from the handover, because every phased member did both.

Editor: What did the phased path cost?

K. Adeyemi-Voss: Six weeks or more in contact they had already decided to reduce. At week four they reported more strain than abrupt members, 4.6 against 4.1. They paid that. The team and the other teammate got the return. By months four to six, phased teams were at 103 percent of their usual output, against 98 after an abrupt cut and 96 with full engagement.

Editor: What should readers keep in mind?

K. Adeyemi-Voss: People chose their own approach. Those who phased out may have had more cooperative teammates or more slack in their teams. We also classified the approach during the same eight weeks we measured output, so in some teams falling output may have led to an abrupt cut, not the other way round. And the teammates who answered our survey were volunteers, about three in four of those invited.

Editor: One practical step?

K. Adeyemi-Voss: Before you step back, write down what runs between you and that person. Hand each item to someone, on record. Then reduce contact gradually, over six weeks or more.

What stays with me is the teammate on the other side. A working relationship can stop working without anyone being pushed out of the team, and a handover written down in a task tracker can be a kind of courtesy. It can tell the whole team, including the colleague you are stepping away from, that the work and the people still matter.

— I.A.

3. Hiring the Person Who Sees It Differently

Values-Floor Hiring, Not Similarity Fit or Unstructured Judgment: Hiring for Difference Above a Conduct Floor and the Renewal of Team Practices (Issue No. 0009)

"Will they fit in?" is one of the most common questions in a hiring meeting. It sounds harmless, and it is usually meant well. This study asks what teams gain and lose when they set fit aside, above a firm floor of good conduct, and welcome people who see the work differently.

Researchers followed 154 teams in nine organizations for two years, classifying them by the score sheets their hiring panels actually filled in. "Values-floor" panels first rated candidates pass or fail on a short list of conduct standards, such as honesty with customers or respect toward colleagues regardless of role, and then scored differences in background or working approach as a plus. "Similarity-fit" panels scored how closely a candidate resembled the team, and a third group used no written rubric. Over 24 months, values-floor teams formally changed 3.1 long-standing practices per team after someone questioned them, against 2.4 and 2.5. A smaller share of their complaint types kept coming back quarter after quarter (18 percent of complaint categories, against 23 and 22). Misconduct cases were about as rare as in similarity-fit teams: 1.7 per 100 employees a year, against 1.6, and 2.1 with no rubric.

I spoke with one of the authors, H. Moreau-Asante.

Editor: Many managers would say that hiring for fit protects a good team. Is that wrong?

H. Moreau-Asante: It deserves a fair hearing. A team's way of working holds things that took years to build: how people treat customers, how they disagree, what corners they will not cut. Someone who rejects that can do real harm. So the question for us was whether a short, firm conduct floor could protect those things as well as hiring for resemblance does. On misconduct, it seemed to do about as well.

Editor: And above the floor?

H. Moreau-Asante: A team's habits also include things nobody chose. Some practices outlive their reasons, and people who share the team's background tend not to notice them. In values-floor teams, more of the changes started with a question from someone recently hired: 38 percent, against about 30 percent elsewhere.

Editor: Was it easy for the new people?

H. Moreau-Asante: No, and I want to be clear about that. Values-floor teams had more disagreements in their first six months, 4.6 disagreements per team escalated to the team lead, against 3.7 in similarity-fit teams, though this evened out later. And their new hires left more often in the first year, 14 percent against 11. That cost fell mostly on the hires themselves. In values-floor teams where every new hire was paired with a peer for six months, departures were 13 percent. Where not every hire was paired, 16 percent.

Editor: So the pairing mattered.

H. Moreau-Asante: It may have helped, but the pairing was not randomly assigned, and teams that arranged peers may have been more welcoming in other ways. Panels also chose their own approach, so teams already open to change may have been the ones that scored for difference. Conduct cases were few in every group, so that comparison is imprecise. What I am comfortable saying is this: a team that recruits people for seeing things differently should not then leave them to manage the friction alone.

Editor: What would you suggest to a hiring panel?

H. Moreau-Asante: Write down the few conduct standards you will not compromise on, and screen for those firmly. Above that line, give credit for difference. Then give each new person a named colleague to check in with.

"Fit" can feel like the safe choice in a hiring meeting. This study offers something steadier than that feeling: a way to protect what matters about a team while still letting new people change it, and a hint that someone walking beside them in their first months may help them stay.

— I.A.

Also Noted: October 2026 in the Journal

October 2026 carried four issues, published on October 5, 12, 19, and 26, with fifteen papers in all. Beyond this month's three picks, here is what else caught my eye, one line each.

Issue No. 0007 (October 5)

• A few shared scenarios: team leads who sketched several plausible futures and talked them through with their team re-planned faster after a disruption than those who shared one firm forecast, though the advantage largely disappeared in a small group whose scenario sets were very large and detailed.
• Deliberate delay: social media users randomly given a 30-minute hold on quick replies understood heated topics better and drew less escalation, at the cost of fewer reactions.
• Measured appeal: footballers who answered an uncalled foul with a brief gesture or a single query were given the foul more often the next season than players who protested at length or stayed silent.

Issue No. 0008 (October 12)

• Reinvested effort: employees who stepped back from a difficult colleague and put the time into new working contacts were less exhausted six months later than those who kept trying to repair the relationship or simply pulled back, after two months of being more tired, not less.
• Broadened contacts: employees who spread freed time across colleagues in other departments had more improvement ideas reach a pilot, and most of that edge tracked how many departments they were in touch with.
• Help from a mediator: in cases where a manager or senior colleague helped rearrange shared tasks, the colleague on the other side rated the change as fairer, at about six hours of the helper's time per case.

Issue No. 0009 (October 19)

• Situation-matched value notes: short staff-written notes on what a community expects in specific situations made AI-drafted replies feel more like "how we treat each other here" to members.
• Wider reach, thinner judgment: an AI interviewer gathered frontline know-how from more staff than workshops did, but its playbooks said less about when to set the usual practice aside.
• A reviewed observation log: newcomers whose questions about team habits were logged and reviewed with their lead felt more valued, even when the answer was an explanation rather than a change.

Issue No. 0010 (October 26)

• Repairable streaks: a practice streak that forgave one missed day a week and could be repaired with a short catch-up brought more language learners back after a break than one that reset to zero.
• Mastery-gated levels: points for passing applied checks, instead of for time spent, made a spreadsheet course more frustrating, and learners scored higher on an applied task three months later.
• A game layer that steps back: music learners whose points and badges were phased out early kept practicing more often once the program's rewards ended for everyone.

For the full papers and complete issue listings, see Issue No. 0007 through Issue No. 0010.