What alternative design did you have in mind, given that a Twitter-like data model of individual follows is likely a strict product requirement?
There are obviously other ways of doing it (doing the timeline propagation in a batch job, fanning out the reads rather than the writes), but they've got their own problems. Probably worse ones.
Wouldn't a hybrid approach makes sense?
Periodically classify users as hot/cold based on their activity, build hot-follower timelines on write, and build cold-follower timelines on read.