Peer Development Group Guide

Gather three to six peers who do not manage each other, agree a short written contract, and meet on a fixed format where questions come before advice. The group becomes the place where you think out loud about work, that is neither your team nor your manager.

Practice, not research: the format comes from the small-group tradition used in leadership programs at Stanford GSB (Interpersonal Dynamics), HBS (Authentic Leader Development), Wharton (P3) and INSEAD (PLDP). None of these schools publishes outcome data, so this page claims no measured effect. The group size and timings are rules of thumb.

Use it when:

• You want development that lasts beyond a course and survives daily pressure.
• You want feedback from people who see you over months, not once.
• You lead alone, run your own business or are changing direction, and have nobody outside your team or manager to think with.

Skip it when:

• You need a broad view of how many people see you, once: use 1.3 Feedback & Psychometric Summary.
• You are in an acute personal, legal or health crisis: talk to a professional (occupational health, a doctor, a lawyer). A peer group cannot carry that responsibly.

Small groups where participants work on each other's real leadership questions are a fixture of top business school programs. Stanford runs much of its Interpersonal Dynamics course in small facilitated groups with feedback in the moment; Wharton's P3 meets weekly in small groups; INSEAD pairs dialogue groups with coaching. The schools describe the format and its aims, but none publishes measured outcomes. Treat it as practice with a good rationale and judge it by what it does for you.

The rationale is a simple mechanism. Advice from a friend usually answers the problem the friend would have, while questions from peers who have no stake in your answer make your own thinking sharper. That is why this page runs on three rules: confidentiality agreed in writing, members who are not each other's managers, and a fixed format where questions come before advice. The format carries the quality on evenings when energy is low. The limit: demand and satisfaction are not proof of effect, and the quality depends on who is in the room.

Pick peers, not people above or below you, ideally from other organizations or units so no one has a stake in anyone's answer. Write roles, not names.

Strong answer: "Head of quality at a dairy cooperative, met on a course; leads about the same size team as me, works in another industry, has no stake in my decisions. Asked on 3 March."

Illustrative example: the people and organizations are made up.

Four mid-career leaders from different organizations in Norway form a group after a leadership course: an operations manager at a ferry company, an HR lead at a hospital trust, the founder of a small engineering firm and the head of a municipal unit.

Sections 1 and 2: the contract takes one evening. The founder wants quick advice rounds and accepts the questions-first rule reluctantly. They agree six dates and a rotating facilitator.

Section 3: meeting four is the turning point. The unit head brings a case she has told no one: "Should I leave the public sector?" She has tried a pros and cons list and is afraid of losing her pension rights. Forty minutes of questions, with no advice, let her hear her own answer: she wants to test consulting part-time before deciding. Her commitment, logged: talk to two former colleagues who made the move.

Section 4: at the autumn review, one member has canceled three times running. The group asks him in person whether he wants to stay; he leaves on good terms. They invite a fifth member and reread the contract with her. The founder says the rule he resisted is why he stays.