One Editor, Not a Committee

A family book made by consensus does not get made.

This is the least popular thing to say about shared memory projects, and it is the most reliably true. Two people can make a book together. Five people deciding together will produce a group chat that runs for four months and a book that never reaches a printer. The problem is not that families disagree. It is that nothing in the arrangement gives anyone the authority to end an argument.

Books need someone who can say no.

Why the group chat fails

Watch what happens when a family tries to choose together.

Someone shares forty photos. Someone else adds twelve, three of which are versions of one already there. A third person says they like the second one better, without saying which second one. Two weeks pass. Someone asks whether we are still doing the book. Everyone says yes, warmly and sincerely, and nothing moves.

Each of those exchanges is reasonable. The failure is structural. A book requires a long series of small refusals (this frame and not that one, six photos in this chapter and not eleven), and a group has no mechanism for refusing. Groups are good at adding. Every member can propose an inclusion; none feels entitled to propose a removal, because removing someone’s photo feels like removing them.

So the selection grows and never shrinks. And a selection that never shrinks is not a book.

Split the two jobs

The fix is not less collaboration, but collaboration on the correct half.

Gathering genuinely improves with more people. Different phones hold genuinely different moments: your brother has the only photo of the whole table, your mother has the one of the kids asleep in the car. Nobody’s archive is complete on its own, and a book built from one phone quietly becomes a book about one person’s vantage point.

Choosing degrades with more people, for the reasons above.

So: gather wide, decide narrow. Everyone contributes. One person holds the edit. Say this out loud at the start, in plain words, because the failure mode is that it goes unsaid and the editor discovers halfway through that four other people believed they had a vote.

Naming an editor sounds officious for a family project. It is much less awkward than the alternative, which is a book that stays unmade while everyone stays polite about it.

How to ask for photos

An open request produces nothing useful. “Send me any photos you have from the summer” reliably returns either a 900-photo dump or silence, and both leave the editor with the same workload.

Ask narrow. Their ten favourites. Everything from the Saturday. The ones with Grandma in them. A bounded request gets answered, usually within a day, and it hands you their judgment as well as their photos, which is the part you actually wanted and the part a bulk export throws away.

Give a deadline that is sooner than feels necessary, and start without the stragglers. A book waiting on one person’s contribution is a book waiting indefinitely.

A worked example

A grandmother’s eightieth. Four households, one 40-page book.

The open version of this project: a shared album, everyone dropping in whatever they have, a running conversation about what should go in. Six weeks later the album holds 1,400 photos and there is no book, because there is no first draft to react to and no one whose job it is to make one.

The structured version: one person is the editor, agreed in a two-line message. Each household is asked for their fifteen best from the day, plus any older photo of her they love. That returns about 90 photos rather than 1,400, most already filtered by someone who was there.

The editor cuts to 55, shapes six chapters, and shares a proof, not a poll. Two real corrections come back: a cousin’s name is misspelled, and one household’s only photo together was missed. Both get fixed. The book is ordered eleven days after the first message.

Ninety photos, one decider, two rounds. The difference is not effort. It is that somebody was allowed to choose.

The conversation actually worth having

There is one question the group should answer together, and it is not about photos.

Who is this book about?

A book about a grandmother is a different book from a book about the party for her, which is different again from a book about the family as it stands in this particular year. All three are legitimate. They select differently at every step, and a group that has not agreed on which one they are making will disagree about photos forever without knowing why.

Settle that in five minutes at the start and most later disputes dissolve. When someone asks why a photo is missing, the answer is usually available: it is a lovely photo, and this book is about her, and that one is about the room.

Software helps here more than people expect, but not by mediating. What it does is remove the arguments that were never really arguments: near-identical frames, blinks, the same moment from three phones. Enchanta collapses those before anyone sees them, so the conversation starts at the decisions that actually need a person.

Two people is a different problem

Everything above is about groups. Couples making a book together are a separate case, and the advice mostly inverts.

Two people can genuinely share an edit, because two people can actually converse. There is no diffusion of responsibility, no waiting to see what the others think, no silence that has to be interpreted. What goes wrong instead is a slow deadlock over a small number of photos, usually the same ones, revisited across several evenings.

The fix is to split by chapter rather than by decision. One of you takes the first half of the year, the other takes the second, and each holds full authority within their part. Then you read each other’s and may object once, with a reason. Not a negotiation: a single note, answered or declined.

This works because it removes the thing that makes joint editing exhausting, which is that every photo requires agreement. Most photos require nothing of the kind. They are obviously in or obviously out, and the only ones worth two people’s attention are the handful where taste genuinely differs.

It also produces a better book than either of you would make alone. You photograph different things and notice different things, and a book that alternates between two vantage points across the year has a texture a single editor cannot fake.

The one rule worth keeping: whoever holds a chapter holds it completely. Shared authority over the same page is where the evenings go.

When someone is hurt

Occasionally, despite all this, someone is genuinely upset. Usually it is about a photo of them, or a photo of someone they miss.

Answer it directly rather than defensively. Say why it was cut, in real terms: the chapter had four from that afternoon already, or it would not print well at any size the page could give it. Then offer something concrete: a copy of their own, a small album of the photos that did not fit, a print of the one they wanted.

Most of the hurt is about wondering whether they were considered, not about the photograph itself. Being able to answer that specifically, because someone actually made a decision rather than a photo quietly falling off a list, is usually the whole repair.

A committee cannot give that answer. Only an editor can.