This is the best way I know to set up the last chunk of my comments and improvements-through-play for Tomb of the Iron God. Because in addition to making the dungeon's features more suitable for analog play, I also needed to thread a more coherent story through the adventure.
Like exploration or roleplaying, figuring out the dungeon's story doesn't need an explicit in-game reward, because it carries its own reward. All the same, story-delving can pass clues back to the adventure game. Insights from the dungeon's story help the players figure out where its treasure is, how to defeat a monster or bypass a hazard.
|Whose history is it?
Part of old-school revivalism among the more experimental games set has involved just such a focus on generating adventure backstory through play - whether How to Host a Dungeon or Microscope.
If not generated by play of its own, then a story is hard to improvise. It can be done - I'll show you how, next post in this series - but it won't click as well.
So if I would urge one thing on module designers, it's this: Give the adventure a story of its own. Lay some initial clues down, make the structure of it interesting. Everything else I can handle - the mixed dwarven and Imperial coins in the hoard, the doors of stone because they couldn't be bothered to haul wood so far, the way the kobolds fall down and worship the party when cornered because they believe that the Architects will come again.
Oh, and who's telling the party's story? Why the party, the dice, and the DM, in one big contested collaboration. But the dungeon's story rests on one pair of shoulders only.