Notes on building teams that last
Editorial timeline
Every piece in Dream Teammate follows the same working order, though the pace changes with each team. What follows is the sequence we actually run, from the first sit-down to the moment a draft is cleared for the issue.
Week 1
Reporting opens with a recorded conversation, usually two hours, sometimes more. We let people finish their own sentences, then condense the transcript without inventing dialogue or smoothing over the pauses.
Weeks 2 to 5
For diary pieces we follow a team across several weeks and publish dated entries instead of a single retrospective. Readers see the schedule slip, the argument on a Tuesday, and the fix that only made sense later.
Rolling
Columns alternate between people who hire and people looking for a first job, so both sides of the same hiring decision land in the same issue. Neither column gets the last word.
Per edition
The recurring section asks three professionals in the same trade to describe, separately, how they handled one concrete problem. Their answers run side by side, with no moderator's verdict at the end.
Final pass
Trade terms stay intact. Jargon gets trimmed only when it hides meaning. Disagreements stay visible instead of being resolved for the reader, even when that makes the piece harder to close.
Before publication
Every named person reads their own quotes before the issue goes out. We correct dates, job titles, and figures, but we do not soften a quote because it sounds uncomfortable in print.
Support desk
Pitches, corrections, and questions about how a story was reported all land in the same inbox. We read everything, but we answer in the order it arrives, and reporting weeks can slow that down.
Before you write, it helps to check the FAQ: most questions about deadlines, word counts, and how we handle trade terms are already answered there.
Best for story pitches, interview requests, and corrections with sources attached.
info@dreamteammate.comRP208, Santiago del Estero, Santiago del Estero, G4200, Argentina
Still unsure where your message belongs? Read the editorial policy or send a short note through the contact page.
Editorial method
Every piece on this site starts the same way: a long sit-down, a recorder on the table, and a team willing to talk about the parts that did not go well. Here is what that process produces for you as a reader.
We sit with people for around two hours and condense the recording afterward. Nobody gets to rewrite their own quotes into slogans, and we do not invent dialogue to fill a gap.
Project diaries follow a team across several weeks and publish entries as they happen. You see the wrong turn in week two, not a cleaned-up version written after everything worked out.
Columns alternate between people who hire and people looking for a first job. The same decision shows up twice in one issue, from two positions that rarely share a page.
In our recurring section, three professionals in the same trade describe how they handled one concrete problem. Their answers run side by side, and we leave the disagreement standing.
We trim jargon only when it hides meaning. If a press operator says "make-ready" or a cook says "mise en place," it stays, because that is how the work is actually described on the floor.
Curious how a specific format fits a story you have in mind? The use cases page walks through each one, and you can always reach the editors directly.