The Great Untasking (aka Truck Number ~1)

This update gives a little insight into a GTD fail and recovery.

Last November MassLandlords hired a key full-time employee. Before then, we were already heading into task-trouble. The graph below shows the terrible climax. On March 6, 2017, I had 617 items overdue. The oldest was 84 days late.

Task Queue Total and Days overdue as of 2017-07-26

Most of these items were MassLandlords tasks, but the graph shows everything on my plate. The data points were taken when I felt I had time or energy to take data, which sometimes meant when I was feeling particularly bad or good about the situation. (If it were possible to create the graph automatically, I might have been more regular or scientific about sampling.)

When MassLandlords hired in October, I didn’t anticipate what I later came to realize: we weren’t ready to hire for that role. That key hire was great, but they exposed some weaknesses in our processes and resulted in a lot of extra work for me. We survived the last nine months with most of our customers. Most significantly, it’s now fair to approximate our truck number as slightly greater than one. We may be still be in a tenuous situation, but we are nevertheless in the best situation to date.

What’s Different?

Certainly the primary improvement was the addition of our second full time equivalent, despite the surge in tasks their new role created.

Another improvement made during this period was to start migrating all customer service responsibilities out of asana, which has no customer-service features, and into groove. Groove has put up almost no adoption hurdles for the team. It has streamlined and created a sense of perspective that was lacking before. Many tickets ran through my inbox before. I intend to remain accessible to MassLandlords members, but for their sake as much as mine, we are slowly going to start directing their communications to me through Groove. Many routine items (most common complaints: password issues, message board access) can be triaged by team members while we work to eliminate root cause. The items that need my attention can still be forwarded to me.

Another improvement was when I started prioritizing emails from team members. I do not use gmail’s priority inbox. Instead, I have a Monday priority reminder to search my inbox for messages from each team member and provide what they need. I believe that expediting is the sign of a broken process — my process is broken — but this expediting has produced managerial leverage, in the Andrew Grove sense: each hour I spend expediting frees up many hours of team member time. There are currently ten people on my leverage list, putting out 50 to 90 hours each week in total. With team members in the US, Philippines, India, Africa, and Europe, a response one hour late can result in a calendar day’s worth of delay. A sticky note on my monitor reads, “When you manage people, it’s all about them.” This is a great quote from Jack Welch, and a reminder to work towards team dynamics that don’t require me in the loop at all.

Speaking of monitor stickies, another sticky reads, “hire every day.” There are three or four essential roles still needed at MassLandlords before we can declare victory on the bootstrapping challenge. This may take another year yet. When we originally set out in late 2013, early 2014, I estimated it would be about five years to stability. We can’t yet prove me wrong.

Two more factors just in the last 30 days have resulted in a general freeing.

First, one of our most demanding and harassing customers (not a landlord but an organization) finally cut the tether holding them to reality and set sail for the great political void. I bid them adieu, and bid welcome to the newly freed timeslots on my calendar.

Second, I have had a total break from the demanding cycle of MassLandlords events. We are attempting to hire for a major event role before the 2017-2018 season begins. We also hope to reduce my attendance at some events with video. Events took up more time than I realized, and since there are no events in July or August, I have been able to close out a wide variety of tasks. There are currently 102 projects and focus areas in various states of need. Many of the projects will be closed out, and we will continue to offload focus areas as we hire.

So that’s the GTD fail and recovery. This fall, when events resume, we shall see whether I have made a lasting improvement.

What should be humanity’s top priority?

I saw a quora article by this title back in February. In it, there were various suggestions split into two main camps: either social or technological. I think humanity’s top priority is probably the intersection of the two.

Specifically, humanity’s top priority is almost certainly is the predictive ability of economics, and thereby, the application of science to government.

Many ideas were suggested in the quora article, including space colonies. How can we know which is best? Economics should come to the rescue, but it’s the “dismal science.” We cannot predict with any repeatable certainty which actions will lead to “improvement.” To make matters worse, there is serious disagreement over what to improve. Should we minimize the maximum unhappiness? Should we maximize average happiness? Should we do whatever it takes to propagate our genome, our ideas, or our individual freedoms? Should we all just seek inner enlightenment, as one person suggested?

The truth is we have only a vague idea. Our limited history gives us incomplete empirical data, very little of which was designed for statistical analysis or recorded in adequate detail. Our theories can explain some concepts and some trends very well, but when it comes to Trump’s election or ISIS we are easily blind-sided. And unlike our endeavors in the similarly complex medical sciences, we have no economic “clinical trials.” There is almost no deliberate experimentation in government or society. There is little candor in evaluating the results of what little we try.

I suspect that we will be able to decide the next “top priority” — and eliminate political divisiveness in the process — if we can first beef up economics. There are two components to this: economic “clinical trials” and better predictive modeling.

Imagine you could take a proposed law and run it forward 100 years in a simulator. What does that do to the target objective? What externalities do we see? Does the simulation suggest a refinement or an altogether different approach?

Meanwhile, for things that are harder to predict, can we voluntarily enlist 100,000 people in an economic trial? One group is a control, the other group lives under slightly different circumstances.

With either approach, there are daunting implementation details to be worked out. Modeling is sharply limited by our understanding of human behavior and our computational inability to simulate anything as complex as a society. And economic trials are going to be befuddled by selection bias, and double-blind issues, and all the ethical questions delineating the degree to which we experiment on ourselves.

But in principle, this is the approach. We have used it with astonishing success in mechanical engineering, which is the application of science to solving hard physical problems. We should apply similar methods to social engineering. Politics as a method leaves me feeling misdirected, to say the least.

My hope is that we can — with modeling and economic trials — expand the scientific method to the work of government. Rallied around an objective reality, anything will be possible. Divided along untestable ideological lines, we can only hope to muddle our way forward.

So science in government first. Space colonies later, if that’s what makes sense.

Bootstrapped Startup Update: Leveraged Management vs Individual Contributions

Starting 18 months ago, I began more detailed timetracking for MassLandlords, which is a bootstrapped startup. I started noting the difference between what Andrew Grove called “high leverage” activities and what Pratt and Whitney called “individual contributor” activities. This is the first time I’ve made a graph of the results. It’s a prime example of “what you don’t measure doesn’t get better.” It shows that I haven’t been unburying myself the way I imagined.

Leveraged management time vs individual contributor time in a bootstrapped startup. Each point is a 4-day interval. Graph shows level of effort for the MassLandlords project.

Leveraged management time vs individual contributor time in a bootstrapped startup. Each point is a ten-period moving average of a 4-day interval. Graph shows level of effort for the MassLandlords project.

The graph shows percent “level of effort” (what percent of time I spend on just these two activities) vs time. Each point is four days’ worth of time data, averaged over the last 40 days so it looks smoother. I track my time in four-day intervals because I use a piece of paper on a clipboard that I keep with me at all times, because only four days fit on a sheet, and because weekends are not very relevant anyway =(. I quickly note what I’m doing on paper. I don’t need to use any company-specific information systems like harvest, where maybe I’m not logged in or I need to switch accounts or who knows what is going wrong. (I love harvest for team-level perspectives, but paper is like harvest just for me.)

The blue portion represents time spent doing “leveraged management.” The idea is that one or two hours spent with a direct report, employee, or contractor will enable them to do eight or more hours of work on their own. In the last 18 months, MassLandlords has brought on about 50 hours of work each week (one big and several smaller hires). So I somewhat expected that I would add about ten hours of high leveraged work each week and lose a lot of unleveraged work. The red portion of the graph is “individual contributor,” or things that an employee should be hired to do.

The new hires are definitely working out, but they are exposing weaknesses in customer service, event logistics, and financial controls. All of these areas are largely my “individual contributor” responsibility. On our bootstrapped trajectory, it has been undesirable to lose touch with our customers by hiring for service, and impossible to hire adequately for logistics or controls (these positions seem to require some degree of scale because of the physical nature of the logistics work, and great degree of trust required to hand over financial controls). The increased effort for event marketing, event planning, and advertising have certainly been helpful, but they are generating more customer interactions, more events, and more transactions.

Leveraged management time vs individual contributor time in a bootstrapped startup. Each point is a 4-day interval.

Leveraged management time vs individual contributor time in a bootstrapped startup. Each point is a ten-day moving average of 4-day intervals.

The graph showing total hours gives more insight. The red “individual contributor” line has been climbing as MassLandlords has grown. Our major hire started fall 2016. During their training, the blue “leveraged management” line spiked. It has been declining as they (and other team members) gain experience and ability. The blue line should have stayed high after that major hire. Except with the weaknesses in service, logistics, and controls, the red line shows a lot has landed back on my plate. This has distracted me from focusing on scaling and the next hire.

The trick here seems to be to make sure that some portion of the blue line includes time spent scaling and focusing on the next hire. If that’s the case, then we will eventually successfully pull ourselves up by the bootstraps. On the other hand, if the blue line is being spent just to keep the existing team going, then we must be caught in limbo. Not only will no one be working on scaling, but also, because I am just one person, the red line will eventually max out, customers will go unhappy, churn will increase, and the organization will rebound downward. Understanding this graph is of the first importance. And anyone with a bootstrapped startup probably should be making their own graph, because so much of starting up is “the grind” that produces so little value compared to high-leverage activities.

Random Grumbles and Advice

Service: Knowing what I know now, I would have implemented a customer service process much sooner, maybe at the outset. It would have been possible for me to maintain contact with customers even from inside a framework like zendesk. Now we have a situation where customers are emailing the last team email address they saw, which is pretty much not working out for anyone.

Controls: I also would have prioritized a relationship with a bank that gave granular access controls. Most small business banks — and even quickbooks online, which I otherwise much admire — have laughable separation of controls. The person who enters vendors must not be the person who pays them, and this must not be the person who records the debts in the first place. Most small business systems make all of this accessible to the same user. Thereby, any dishonest schmuck can enter a fake vendor bill, enter the fake vendor billpay, and pay the fake bill to themselves or to their cousin. Sure, they will eventually get caught, but only after much stress and financial loss on our side. I think Avidia Bank will be our partial salvation but until we implement it, I can’t say for sure. QuickBooks online is still not compliant, and I don’t see a way around that yet, so we’re waiting to hire an employee who can be paid enough to come with high “trust factor.”

Logistics: This is a problem particular to MassLandlords, where we basically need to have 23 physical locations one night a month. I don’t think I have any insight to share at this time.

So that’s the latest timetracking update on our bootstrapped startup. I see now why people take capital: just go hire all the people you need.

Prioritization Grid

I drew this on a screenshare today while talking to a MassLandlords manager.

priority grid, hard high impact, easy low impact etc.

I don’t remember where I learned it*. The basic gist is that lots of people will suggest lots of things for you to do.

 

Some things are going to be hard and have a low impact on your goals. Write them down, but don’t do them.

  • These might become more relevant or less difficult in the future.
  • Writing them down, as opposed to outright rejecting them, lets you return to them in the future. It also is more politically palatable to a requester to hear that it’s in your system, albeit lower priority, than “I have deleted your request.”

Others are going to be easy, low impact. Most administration falls into this category. Hire for it if you can. If you’re not able to hire, do these items when you’re tired.

  • Anna Dietrich described these items as “zombie tasks” or “shooting zombies” because they are repetitive and won’t ever die. I like that analogy.
  • When possible, try to eliminate the source of the zombies. Automation or process changes can eliminate a lot of the low impact work we take as given.

Some things are easy and will have a high impact on your goals. Do these asap.

  • This is the most difficult thing for someone detail-oriented like me to do. I like to have a clean desk and inbox zero. Much of my best work happens because I ignore the other pressures.

The final set are things that will have a high impact but are hard. These require project plans and a longer-term commitment.

  • It’s extremely important not to let a “high impact” item linger because you haven’t created the project plan. Oftentimes the first “action” is a brainstorm or research. Get these items into your task list. David Allen’s advice is invaluable on this front. Define the next action. The journey of a thousand miles begins with a single step.

I don’t like spending lots of time bucketing items into different categories. I don’t like systems that have nine or 16 squares. This four-square framework can be useful for communicating when you will or will not work on something. Otherwise, just get back to work.

*Covey’s Original Prioritization Framework

It turns out Stephen Covey popularized this, but he didn’t have “difficulty,” he had “urgency.” This switch hides any recognition that management or project planning might be needed. I might have learned to replace “urgency” with “difficulty” at Pratt & Whitney, I don’t know. Suffice it to say I think of the grid above when I think of priority frameworks.

Thinking of “urgency” works better in the “personal productivity” space, but less well in organizations. Everything is urgent to the requester.

Why is the law so hard to read?

If I could wave a magic wand, I would pass a law that read,

“Every law must be comprehensible by the people it is meant to govern.”

and then I would pass another law that read,

“For the purpose of the law, attorneys are presumed to have infinite intellect, and can punish themselves with whatever legalese in law or regulation they so desire to inflict upon their own profession, but may so punish no one else.”

That way, everyone’s in heaven.

How Should Cofounders Split Equity? A Cofounder Vesting Riddle

Here’s a cofounder riddle:

Cofounders A and B start a company around A’s idea. There are 10 million shares authorized. A gets 2 million unrestricted for the “idea.” A and B each get 4 million subject to vesting.

Due to unforeseen circumstances, A immediately quits. A’s unvested shares return to the company. B presses forward alone and vests all 4 million shares. The company succeeds without further investment.

At liquidation, A has 2 million of the 6 million outstanding. B has 4 million. A gets 2 million divided by 6 million = 33% of the proceeds. A’s idea premium was lofted from the 20% agreed-upon to 33%. B feels snookered.

What could A and B have agreed to on “day one” so that A would have ended up with just the 20% idea premium?

I posted this to the MIT Venture Mentoring Services forum. Here’s a summary of what was proposed by others:

  • A, the departing founder, could be
    • subjected to steeper vesting
    • given a contractual claim or special class of shares, instead of common, that convert to 20% of the liquidation proceeds
  • B, the remaining founder, could be
    • granted additional stock or options
    • signed onto a “bear hug” right of first refusal to purchase cofounder shares
    • given a loan from the company to purchase cofounder shares
  • Or we could do one of the following:
    • forget idea premiums;
    • accept ownership changes as a risk in starting up;
    • forget the whole “riddle” as an impossible problem.

The type of solution we’re looking for is:

  • Not predictive: we shouldn’t have to know whether A will actually quit;
  • Prescriptive: if A does quit, or participates less fully than B desired, there is no disagreement on how A or B should be penalized/compensated;
  • Smooth: the spectrum of A’s non-participation and B’s compensation, from “A quit” to “A is fully engaged,” should have no step changes;
  • Tax-free: founders can still declare an 83(b) election to pay relatively zero tax on their founder stock; and
  • Cash-free: founders should not have to come up with lots of money to maintain an agreement made early.

Many of the ideas above have either tax or cash consequences, or are not smooth, or are predictive.

The “bear hug” concept combined with an idea sent to me privately, issuing warrants that expire as the co-founder’s stock vests, seems to me to be an implementable solution with few tax or cashflow consequences. So that’s what I’ve been working on this week.

I will report back and/or blog about it if we produce anything interesting. Certainly the name of this scheme would be, “a completely warranted bear hug.” Stay tuned.

Pixaby "bear hug" graphic to accompany "cofounder riddle"

My Favorite Part of the Work Week is Saturday at 7:30am

Saturdays at 7:30 am (5:00 or 6:00 pm India time depending on daylight saving) I call the MassLandlords bookkeepers in India. I love it.

I actually get up at 6:30 to prepare for the call and to review our “treasury dashboard.” I love getting up early on a weekend. It feels so productive. Plus, this phone call represents two-and-a-half years of process development. We review income and expense reporting for MassLandlords and two MassLandlords partners. We use asana for linear processes, skype for the call and screen sharing, Google Drive for file transfer, and Google Docs for the dashboard itself.

MassLandlords Treasury Dashboard

 

The idea for the dashboard comes from my training in operations. You want to quickly see a visual status of the entire organization. One of these boxes updates via an API, most are manual and take 30 seconds to update, maybe five minutes for the whole week’s work. I can update them or the team in India can.

The other thing I really like about the team in India is their combination of hard working and good attitude. They have had no end of challenges, from power outages to dengue, and yet we have continually taken care of our people and our jobs. We’ve had language skills training to the point where we’re talking politics, technological innovation to automate a lot of our work, and a mindset of continuous improvement to leave us all feeling productive and headed in the right direction.

I’m lucky to work with their team leader, who is receptive to suggestions and candid with feedback. It’s a great team, almost three years in the making, and checking in on their progress is certainly my favorite part of the week.

Follow Doug via Email

You can say you knew him before he was famous:

The up-and-coming landlord association for Massachusetts.