The Follow the Journey Framework Applied to a Water-Based Expedition
Documenting a five-day paddleboard circumnavigation of Lake Tahoe with no reliable cell service, no easy way to upload content mid-trip, and constant physical demands, tested my Follow The Journey distribution framework in a way that a typical land-based expedition never has. Here's how the framework actually worked when applied to a project happening almost entirely disconnected from the internet, and what changed about the approach as a result.
What Follow The Journey Normally Looks Like
My Follow The Journey framework phases content release across four stages rather than dumping everything at once around a single launch date. On most projects, that means capturing material throughout, then structuring the release calendar afterward with enough real-time flexibility to adjust based on what's resonating as it goes out. That real-time flexibility is usually part of what makes the framework work well, letting early engagement inform how later phases get shaped.
Why a Water-Based Expedition Breaks That Model
72 Miles of Blue removed the real-time piece almost entirely. My best friend Michael Whalen and I had no reliable connectivity for most of the five days, meaning nothing could be posted, tested, or adjusted while the expedition was actually happening. The entire framework had to shift from a live, responsive process into something planned almost completely in advance, with execution happening only after we were back on land with the full body of material in hand.
How I Adapted the Framework for This Trip
Rather than releasing content live, I treated the entire five days as a single capture window, then applied the phased release structure afterward once I was back home and could actually review everything we'd gathered. That meant being more deliberate during the trip itself about what I was capturing, since I couldn't test in real time which moments were landing with an audience. I had to trust the instinct that certain moments, the packing day chaos, the near miss near Sand Harbor, the finish line, would carry weight on their own merits rather than relying on live audience feedback to confirm it.
What Still Worked About the Framework Despite the Disconnection
The core principle held up even without real-time execution. Different pieces of the story still needed different release windows to avoid overwhelming an audience with everything at once. The packing day chaos went out as its own piece, distinct from the day-by-day paddling content, distinct again from the brand-facing case study material. That structural discipline mattered just as much in a delayed, planned release as it would have in a live one.
What I'd Change About Documentation for the Next Disconnected Project
Knowing now how much the framework depends on eventually having real material to work with, I'd be even more deliberate next time about capturing redundant footage of key moments, since there's no opportunity to go back and reshoot something once a five-day expedition on open water has ended. I'd also keep more detailed notes during the trip itself about context and specific details, since memory fades faster than you expect once you're back in normal life and trying to reconstruct the exact sequence of a headwind delay or a conversation from three weeks earlier.
Why This Approach Still Produced Strong Results
Despite the lack of real-time adjustment, the phased release from this trip has continued to produce results consistent with what the Follow The Journey framework generates on more connected projects, over a million organic views across the full distribution cycle. That consistency suggests the framework's core value isn't really about live responsiveness. It's about structural discipline in how a single body of material gets spread across time and platforms, which holds up whether you're adjusting in real time or planning the entire sequence in advance.
What Other Brands Should Understand About This Kind of Documentation
Brands considering sponsorship of a disconnected expedition should understand this tradeoff clearly going in. You're not going to see live updates or real-time proof of engagement the way you might with a more connected campaign. What you get instead is a body of material that, once released, tends to have more staying power precisely because it wasn't optimized in real time to chase immediate engagement metrics. The delayed nature of the release actually protects the storytelling from the kind of short-term thinking that live, responsive content sometimes falls into.
How I Explain This Tradeoff in Brand Conversations
When I'm talking with a potential sponsor about a project like this, I'm upfront that they won't see anything until the trip is complete and I've had time to actually process and structure the material. That's a harder sell than promising live updates throughout an expedition, but it's an honest one, and the brands who understand the tradeoff tend to be the ones who end up happiest with the final result, since they're not disappointed by a lack of real-time content they were never going to get in the first place. Setting that expectation clearly at the start of the relationship has done more to protect both sides of the partnership than any amount of technical planning around the framework itself.
Why This Approach Might Actually Be More Sustainable
There's an argument that disconnected documentation, forced by circumstance rather than chosen deliberately, produces a healthier creative process than constantly checking engagement metrics throughout a project. Without the ability to see how something is landing in real time, I found myself making decisions based purely on instinct about what mattered, rather than being pulled toward whatever format or framing had performed well recently. That distance from the feedback loop, uncomfortable as it was in the moment, may have actually protected the storytelling from some of the short-term thinking that constant connectivity tends to encourage. I've started wondering whether some future projects might benefit from a similar deliberate disconnection, even when the technology to stay connected is actually available, simply to protect the work from the pull of chasing whatever performs best in the moment, a discipline that's much harder to maintain voluntarily than it was when the lake made the choice for us, which may be the strongest argument yet for building a little more genuine disconnection into future projects on purpose.
Before You Close This Tab
What does phased content distribution look like for a project you've worked on that happened somewhere disconnected from easy uploads?
How would you capture material differently if you knew you couldn't test what was resonating until well after the fact?
What structural discipline from a framework like this would still hold up even without real-time feedback?
How do you currently handle documentation for projects where memory is the only record you'll have afterward?
Dalton Johnson is a photographer, filmmaker, and brand storyteller based in South Lake Tahoe, California. Over the past decade he has worked with brands including Patagonia, GoPro, Arc'teryx, Four Seasons, Nike, Rivian, and Ford Bronco across all seven continents. He is the creator of the Follow The Journey distribution framework, which has produced over one million organic views per 30-day cycle without paid media. His work includes two published books, an award-winning documentary that aired on PBS, and more than fifty commercial spots directed. He runs Stories by Dalton on Substack, read by more than 34,000 subscribers.