Planning To Not Plan: The Route
How do you plan for a journey that isn’t supposed to be planned? Quite the dilemma, isn’t it?
It’s absolutely the case that when I finally hit the road I want freedom. I want freedom to roam about as I please, when I please. I long for the ability to stay in once place for weeks at a time and to decide other stays only warrant a night or two. I crave the experience of where I live being a completely open ended endeavor.
That said, this is going to be a wildly profound change of lifestyle for me. A transition that will take a significant amount of adjustment.
Yes, I want freedom. But I also have some realities I can’t ignore. For instance, I must be within range of data/internet Monday – Friday. At the very least Tuesday – Thursday. I have a fairly sizable budget for all the devices and plans I’ll need to ensure as much connectivity as possible at all times. But I know a lot of boondocking options are going to have to be kept for weekends at best.
Additionally, there is a long list of places I want to see my first year. I’ll talk more about that list in a later post, but for this one I’ll just hit on an overview.
With all of this in mind I’m not planning an extreme route that has to be totally adhered to, but I am planning a basic path to find peace with during year one. It’s probably a route that will feel traditional to a lot of peeps already doing this. And there is a reason for that… logic.
My general plan is fairly simple and follows the path a lot of others take. Hit northern states making the way across westbound to Washington during the summer months (2018), landing in AZ in January and working across to Florida during March/April/May. From there I want to head up the east coast landing in New England for the following summer (2019).
This is all very fluid, as it should be, and will likely often change a bit. As the journey gets closer I’ll integrate real time maps with information on each stop I make.
Any thoughts? Suggestions on must see stops?