This weekend, I finally got Eric to start approaching this thing like a project at work. He is a programmer, as I may have mentioned (I don’t know, did I?), and he thinks in terms of bits and bytes and ones and zeros, and he has this uncanny and mystifying talent for storing hundreds, maybe thousands, of lines of code in his brain and can visualize outcomes before they happen. I can’t do that. Most normal people can’t. He has all these details stored in his brain and can see it for himself, but when he communicates it to others, they find themselves stupefied and mumbling, “What the hell is this guy trying to do here?” He can answer that question, but in terms that only he understands. It is not an answer that normal people can wrap their heads around.
So I put on my work hat, and told him I had to have easel paper and some markers. It was time for a meeting; a data dump of everything he has stored in his brain. Ultimately, it was a brainstorming session where all these ideas and plans and open issues would get documented, organized, and prioritized. As a normal person (not a programmer), I was growing frustrated with the knowledge that he has all this stuff in his head and seems to understand it all perfectly, but I was lost … completely overwhelmed with all these ideas and details and data. It didn’t feel like it was organized enough to really get a handle on it. Data was spilling out of his mouth and onto the floor like kaleidoscope shards dumped haphazardly out of the tube, and I could NOT see any pattern to it to save my life.
So once the objectives were identified, tasks could be identified, and from there, we could figure out what was most important and who was going to do what … so we got an action items list out of it that even I could understand. He knew we needed to do this, but programmers are not good at this sort of thing, and smart people know to relinquish what they are not good at to those who are good at it. He is smart. He is scary sometimes. If he took all that stuff he has in little head and put action plans to it all, he would be a millionaire … and I am not talking about just the land. His brain is just exploding with unrefined, raw data. He needs to channel it … focus it and put it into action. In programmer lingo, “He needs to compile it and move it into production.”
Granted there were only two of us, and we really needed some subject matter experts or SMEs (one from ODNR, one who knows how to write grant proposals, one who understands geological surveying and water testing processes, etc) but we did okay. At least, we identified the SMEs we need to involve at some point when the time is appropriate.
We now have a mission (from which we can develop a project objective that SMEs WILL be able to grasp): “Do No Harm” (which was later qualified to mean “Make the overall impact of our presence a positive one.”) We now have a “DAY ONE” actions items list (all the things that have to be addressed within 30 days of closing … getting answers to the most URGENT questions) and we have started a list of all things that have to be researched and the decisions that have to be made in the long term. Granted, we have a long way to go, but at least we have defined where we are headed on Day One. Some of these things could get done right now, if we wanted to.
Day One is (so far) a six point list on easel paper taped to the wall in the family room for us to chew on for a couple days. We will look at again and refine it, if need be, and then, I will get it documented. You can call it an “Infrastructure Development Plan.” Yes, we are a developing wildlife-conserving, but human-supportive infrastructure while being sure to maximize our SME resources and save money. (Yes, I know that “wildlife-conserving/human-supportive” might sound like a contraction in terms, but read on. It’s really not.) That is exactly what we are doing; we’re building an infrastructure. First things on the list? Getting water/sewer, electricity, and communication resources established and determining specific contact information on the SMEs we are going to need in the long haul (like ODNR and all their little databases that we don’t even know are there yet). That is going to be hard to do while supporting the mission statement. But it can be done.
We ended up going back and qualifying what we meant by “Do No Harm.” I suppose the radical tree-hugging environmentalists might have a valid argument that you cannot set up a human-supporting and sustainable infrastructure without causing some sort of harm. Well, we meant “Do no harm to the animals and do nothing to the landscape that cannot easily be undone or is not positive.” Whatever impact we have will be outweighed by the longer term goals of cleaning up the mess from the wells and strip mining and reclamating the damage done in past decades using modern technology for reforestation and erosion control, but we will do that with the most minimalistic approach possible. We did not mean “Make no changes and have no impact.” We just want to make sure that the overall impact is a positive one for nature. We will leave it better than we found it. But to do that, we will need to safely establish a “primitive residence” where the land’s custodians can function and have basic needs met (like eat and pee) because we cannot fix what we don’t understand. We have to stay there and study it to find out what all its’ problems are and how best to approach them. You can’t monitor the reclamation process if you are not THERE to watch it. Sure, we will have some impact. That is a given. The goal is to make sure that in the grand scheme of things, it is a GOOD THING for the environment. Even the tree-hugging environmentalist would have to find that noble enough.
Posted in Uncategorized



