I almost gave up on computational journalism until I discovered a simple, counterintuitive shift in my strategy. This isn't the generic advice you've heard a thousand times; this is the secret sauce that changed everything for me.
Why Most Approaches Fail
Many common approaches to computational journalism are flawed at the root.
The root cause is usually one of three things:
Copying what big companies do without understanding why they do it. What works for Google doesn't work for a 10-person startup.
Over-engineering the solution when a simple approach would work better. I've seen teams spend six months building something that could have been done in two weeks.
Ignoring the human element. Technology is the easy part. Getting people to actually use it is where the real challenge lives.
What I've Learned From 93 Companies
A few patterns in computational journalism come up again and again.
The founders who handle computational journalism well understand that you need to move fast and break things.
Lessons From the Trenches
I want to share a few specific lessons I've picked up over the years. These aren't theoretical. They come from real companies, real failures, and real successes.
Lesson 1: The best time to start thinking about computational journalism was yesterday. The second best time is now. Don't wait until you have the perfect plan.
Lesson 2: Hire for attitude, train for skill. The best people at computational journalism are rarely the most technically gifted. They are the most curious and persistent.
Lesson 3: Your competitors are probably getting this wrong too. That's your opportunity. While everyone else is following the same playbook, you can zig when they zag.
This connects to broader themes around AI journalism, AI storytelling, AI game design, AI animation, AI writing that I've been thinking about a lot lately.
The Bottom Line
None of this is rocket science. But it does require intentionality, consistency, and a willingness to learn from mistakes.
If you take one thing from this article, let it be this: start now, start small, and iterate. The founders who win at computational journalism aren't the ones with the best strategy on paper. They're the ones who execute, learn, and adapt faster than everyone else.
Companies that take computational journalism seriously tend to pull ahead of the ones that don't.
If you're working on something interesting in this space, I'd love to hear about it. Drop me a line.
Frequently Asked Questions
Q:How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.
Q:What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 234 startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
Q:What's the most common pushback you get on this?
People often push back by citing exceptions or edge cases. And they're usually right that exceptions exist. But building a strategy around exceptions rather than patterns is a losing game for most founders.
Q:How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.