Along the lines of my previous post, and discovered through the same source (ServerSide.net), Jon “stole” an idea I had on how to use WF in an ASP.NET app to manage page flow. I say “stole” because he had no idea that I've had the same thoughts, let alone an idea of who I am! Anyway, it looks like a great starting point to implement a workflow to manage page flow. The main key to the solution is that the workflow and ASP.NET app have no idea about each other. I like that.
When I get some time I'll see if I can build on his solution to do things like have alternate storage areas (other than Session) and optional integration with a security model, like the Microsoft Application Blocks, to route the workflow based on permissions.