On mount spokane, many years ago, I shared a road with one other family. It was written into the documentation for land ownership that the costs of maintaining the road should be divided 50/50. I talked to the neighbor and we struck a deal. I would buy a tractor, clear the snow, shape the road and keep it in good condition and he would buy some fresh gravel each year. I did my end. He never did his end. A few times a year I would try to check in with him about the gravel. This small thing turned into a poison for our relationship.
From his perspective, I suppose he thought I was some sort of dick. Each time I would call would be "harassment". He didn't want to see me and it got to the point that I really didn't want to see him.
I suspect that if there was ever a day that I was late in removing snow or a bit of a pothole problem, he would have justification for not holding up his end. But I was really good about doing my end.
I think that in the beginning, he had every intent to hold up his end. Then ... who knows. Maybe he just, simply, perpetually put it off. Anything else seemed more pleasant than buying and applying gravel.
- -
When trying to build anything, there needs to be a certain level of predictability. If you go to build a great thing and collaborate with five other people and one of the five ... um .... falls a bit short, then you have to fill in or one of the others has to fill in, in order to complete the "great thing." Of course, it has been my experience that the party that fell short still wants whatever they were going to get out of the arrangement.
What happens if three out of the five fall short. And some of those things that were to be done ... well, the whole reason you tried the bigger project is because it was a merging of three magic pieces that were hard to come by. And the people that did their part wanted the final product.
- -
When Ernie and Erica first started selling their plans, they set it up at a site that would, at the end of the month, say "paul sold 30, you now owe him $150". So I became a bill. An obligation. And it is my opinion that this was starting to poison our relationship. So I harassed E&E regularly until we got moved over to scubbly. And now I was no longer a bill - I was the guy that connected buyers to their plans and scubbly made sure all agreements were honored.
THIS is an example of working with nature. Working with human nature. My relationship with E&E gets more awesome with every passing month.
- -
For the last 20 months I took on the obligation of feeding gappers. I am not a cook, and I don't want to cook. But I had this theory that this would be the beginning of building community. To pay for food, cooking and cleaning ended up averaging about $6000 per month. For 20 months I did this. This was an enormous amount of money. I tried to find ways to reduce costs, which nearly always ended up in causing frustrations. My thinking was that this was "to prime the pump". In a few years, we would be growing a lot of the food and the property would have a collection of
income streams that would pay for somebody to cook and somebody to clean. I confess that this has been far too stressful for me and I need to find a different solution to forward velocity.
The problem with this is that each
gapper that eats the food then has an obligation to provide work. But the work they are tasked with might be outside of their comfort zone. They come to learn about natural building, but they might find themselves repairing the pickup that another gapper was less than kind to.
We have a big list of stuff and we collectively look at the list once a month. We talk about the projects. Some people take ownership and say that they will make sure it gets done (obligation).
I'm in the office working to pay for everything while everybody else is working to move the project forward. I know that some people have worked some really long hours and generated a lot of cool stuff. And some people have sorta phoned things in. I think some people get a few months down the road and start to think that this is a shitty job with shitty pay. Frankly, I agree with them. People that don't know how to fix things keep breaking things and the people that do know how to fix things get stuck trying to fix the broken things instead of working on cool stuff.
Then the person that is accomplishing a lot is working next to the person that is not accomplishing a lot and knowing that they both get "paid" the same. Resentments build.
When you come for a week, you don't really notice these things. But when you are here for months, this sort of thing starts to build in your head.
So we have a lot of artifacts that move a lot of things forward. These were built by the group to move the group forward. After all, I don't need four houses to live in - I can only live in one at a time. I don't need six showers - one is plenty for me.
When the work day starts at 9am, it is an obligation. When breakfast starts at 6:30, that is a type of obligation. If you come for a week, then it is no big deal. But as the months pass, it is too much. It's a job and the pay is too low.
At the same time, having people be here for years is of far greater value than having people here for just a week.
This system is turning out to be unsustainable. And I don't think I can keep bringing in this much money anymore.
- -
There was a gapper that needed a phone. We have pretty good cell service here. Plus, it would be good to be able to call/email/text for improved communication. So I struck a deal: I'll pay the $60 per month for the phone if he posts a picture a day to permies (I got him a phone with a really good camera). Since this guy was planning on being here "for life", I went ahead and agreed to the two year contract. This is gonna be awesome! People who are itching for pictures on permies will see more stuff! There is gobs of stuff that has not yet had a pic posted!
The result: One picture every few weeks. Often after a reminder from me.
Poison.
I think I became something of an ugliness in his life. I tried to limit my mentioning it because I knew how painful it was. And, at the same time, it was eating me up. After all, this is a thing I could clearly measure. All of the gapper responsibilities fell into a space that I could not (or did not) measure.
But there were so many people falling short on their obligations, commitments, etc. it was starting to become a bit overwhelming. Everybody needed me to be 100% all the time, but they also needed me to set my expectations of them to 0%. Over and over it kept happening. I finally got to the point where I just NEEDED more people to honor their commitments. To do the thing that they agreed to. For anything where there was a metric that could be measured, I needed those things to be honored.
I was poisoned. He was poisoned.
He left. I am paying the termination fee for the phone (hundreds of dollars).
In hindsight, there are lots of ways I could have handled this better. One way would be to say, in the beginning, if you don't meet the agreement for a month then you fork over $60. Of course, this becomes a hassle to measure. Thus indicating that it is a poor approach. Probably the best thing to do was to have this person solve their own phone needs and then come up with tasks where there could be some cash flow. Do the task get the cash. Let the task go, no problem - somebody else can do it. (although I am surprised that we didn't have more people posting pictures just for hoots)
- -
I was talking to somebody about making a DVD series. The deal didn't work out, but the thing that bothered me the most was that this other person wanted a royalty. I think that is a normal thing to want. And I'm sure all sorts of production companies want to go that route instead of money-up-front. (and let's skip past the fact that this guy wanted big money up front plus big royalties) But this would mean that for the funds that come in, you gotta make a report for that stuff and then calculate the royalty and send a check. I agree that is not a LOT of work, but it is some work. And sometimes I can get swamped. I am working to reduce my obligation load. So, for me, that was a deal breaker.
I like business deals that quickly come to an end and then we can all go on to make other business deals. Granted, there is still obligation, but it is possible to get to "done". As opposed to the concept of "there will always be more work to do."
- -
Time to own my shit: I failed in my obligation to Bart. We did the
world domination gardening kickstarter in january 2014. The idea was that we would start a new kickstarter every three months or so, so the next one should have started around mid april. This would give bart lots and lots of work so he could focus full time on these projects. We hit some big fiascos in march and april. Followed by more in the summer. And then more. I didn't hold up my end of the deal. I have some very serious pain around this. I hope that, in time, I can make this up to Bart.
- -
I remember as a software engineer, people would want to pay me by the job. There would be an eight page contract detailing what the software would do and at what points there would be payment. But with most of these, the needs would change as development happened. Then there would need to be all sorts of negotiation about a new contract with the new features. And most of the time they would ask for freebies just to avoid all the paperwork. It just led to a lot of painful discussions. So I ended up passing on anything but hourly gigs.
I liked "extreme programming". Every two weeks the team would meet and bid for tasks: "I can do that task in six hours", "I can do it in five" etc. Then when your dance card for the next two weeks is full, you stop bidding. I would generally outbid everybody and then get "my" tasks done early, then help others. I felt like it was a system that encouraged fairness and it was clear who was awesome (me!). Others .... didn't like this. And that manifested as .... human stuff .... less-than-noble-stuff.
- -
There were lots of places I worked as a software engineer and sat next to people that just seemed to accomplish about nothing. I remember once place I worked where a manager came in every day for a week and asked me "what time did he come in?" and "what time did he leave?" Other people were asked too, but their answer was "I don't want to get in the middle of anything - I have to work with the guy." I answered. When the person who signs my checks answers a legit business question, I'm going to answer. The guy was putting in less than 20 hours a week. He showed up late every day and talked about getting his kids to school. Then he left early because it was his day to pick up the kids - or to squeeze in an errand before picking up the kids. In the meantime, this company was in quite a pickle (which is why they hired me). Lots of people were working late. This guy had an obligation to be there 40 hours a week.
I suspect that when they fired him, they paid him his full salary up through the date of being fired.
This sort of thing was really common in some offices.
Another thing is that there often seemed to be engineers that would show up for work but they just didn't really seem to get much done. They seemed to spend a lot of the day visiting with others or surfing the internet. But software engineering is something that can be hard to measure. A manager would have to be really observant to catch on to what is really going on. And when the manger comes to talk to you about pissing away the day, does that qualify as "poison"? What an icky conversation.
Along these lines, when my grandad died, I was pretty out of it for a year. Fortunately, I had put in a few months with this company already and saved their bacon a couple of times. Even more fortunately, I had kept extremely careful track of the hours I put in. After my grandad died, I might spend ten hours at the office, but I just wrote down "2". I think I started 300 in the positive. After a year I was 400 in the negative. I got it back to even before I left the company. I guess I'm lucky that a manager didn't press the point. My point here is that I totally get there can be off days - or even an off year.
- -
When we design community the permaculture way, it has to account for people being "human" (as opposed to being "noble"). I have learned a very expensive and painful lesson.
We could reflect on every last thing and talk about how people should have honored their obligations. But that is contrary to the point. This mental exercise is: how could the system have been designed so that the project moves forward at a higher velocity, lower expense and happier people. What does a system with less obligation look like?
My first thought is: I withdraw feeding everybody and I withdraw the 35 hour per week obligation. More focus on the ant village. Gappers can still come and hope to build experiences, and they will be given simple tasks for which they will be paid. They handle their own food - whether that is growing it, wildcrafting or buying. They do their own cooking in their own space.