Where a Story Starts
Most people picture a sports story starting with an idea and ending with a publish button. In between, there’s a process that looks nothing like that straight line. A tip comes in about a youth academy changing its coaching staff, or a source mentions a college program quietly building a new scouting method. None of that is a story yet. It’s a thread, and threads can snap.
The work between the tip and the finished piece is where most of the actual reporting happens, even though readers never see it.
The First Call Isn’t to Confirm, It’s to Test
When a tip comes in, the instinct is to call the most obvious person and ask if it’s true. I’ve learned to resist that. The first call should test the tip, not confirm it. I ask questions that someone repeating a rumor couldn’t answer with specifics: dates, names of people in the room, what changed day to day.
If the answers are vague, I slow down. If they’re specific and checkable, I move to a second source who has no reason to say the same thing for the same motives. Two people confirming a detail for different reasons is worth more than five people confirming it for the same one.
Building the Spine Before the Details
Once a tip survives that first pass, I build what I think of as the spine of the story: one sentence that states what happened and why it matters to someone who follows the sport. Everything else gets tested against that sentence. If a quote or a stat doesn’t support the spine, it probably belongs in a different story, not this one.
Skipping this step is the fastest way to end up with a piece that has good information and no shape. I’ve turned in drafts like that early in my career, pieces stuffed with detail that never resolved into a point. The reader finishes and isn’t sure what they were supposed to take away.
Why the Order of Interviews Matters
I don’t interview people in whatever order they’re available. I try to talk to the person closest to the outer edge of the story first, someone who can describe the broader landscape without knowing all the specifics. That conversation hands me questions I wouldn’t have thought to ask the central figure.
The person at the center of the story goes last, not first. By then I know enough to ask something sharper than “how did this happen.” I can ask about a specific decision, a specific moment, because three other people have already described the outline around it.
Reverse that order, and the main interview tends to set the frame for everything after it. You end up reporting on their version of events instead of testing it.
The Draft That Never Gets Published
Every finished piece I write has an earlier version that never sees a reader. That draft exists to show me where the holes are. I write it fast, without worrying about sentence quality, just to see the shape of the argument on a page. Half the time, a section I thought was essential turns out to be filler once I see it next to everything else.
This is the step people skip when they’re on deadline, and it’s the one that costs the most later. A piece built on information is still reporting. A piece built on a clear spine, tested against real interviews, in the right order, is a story.
What Mechanics Can’t Fix
None of this process replaces judgment. I can follow every step correctly and still end up with a tip that doesn’t hold up, or a source who seemed reliable and wasn’t. The mechanics don’t guarantee a good story. They just make sure a bad one doesn’t get through because of a shortcut I could have avoided.
That’s really what the process is for. Not polish, and not speed. It’s a way of making sure that by the time something reaches a reader, I’ve already asked the hard questions so they don’t have to wonder if anyone did.