Skip to main content

Falling into the pit of success

Source: https://ricomariani.medium.com/pit-of-success-for-organizations-a046a0eae7b2


Imagine that systems of your organization are like a complicated piece of terrain. The people operating in the system are little balls rolling around. Victory is some sweet spot in the terrain somewhere. Depending on where Victory is it might be pretty tricky to get there. Maybe it’s up some big hill. Maybe there’s a lot of potholes. Maybe the path isn’t very direct.

If you had a Pit of Success organization, then Victory would literally be this GIANT hole in the middle that you just automatically fall into. You can’t help but win.

Anyone work at a place like that?

Me either.

Here’s the kicker. The terrain tends to get worse rather than better as things get complicated. For pretty simple reasons too. For instance, new parts of the system tend to be based on the old parts. So, say you have part of the terrain that’s full of potholes. Yup, naturally when adding to the system people are going to copy them, making EVEN MORE potholes for people to fall into.

Soon you get a situation where making any kind of progress requires complicated manuals and so forth. Step to the left. Avoid the spikes, don’t break your ankles on any of those holes, roll uphill over two hills, don’t crash into any obstacles, and maybe if you’re lucky you can claim victory.

Now you can either try to make your organization more effective by teaching everyone the rules, and I guess that doesn’t hurt, some rules are probably pretty good, or you can go about the business of making the terrain better. Change the shape of some of those hills so that people tend to roll in the right direction. Move the victory circle somewhere easy to get to. And OMG fill in those potholes so people stop cloning them!

If you do these things, then over time you will tend to get more people automatically going down good paths to success. They might not even know you did it, they just suddenly start winning doing the obvious “downhill” stuff.

I’ll leave you with my favorite Pit of Success metaphor. It’s an apocryphal story about the hamburger recipes of Dean Martin and Frank Sinatra.

It seems Mr. Martin was famous for his excellent burgers and had encoded a fabulous way to prepare them. There were many important instructions which I don’t remember but stuff like getting only the best meat, and getting the right spices, and cooking time, and of course the perfect wine.

Mr. Sinatra’s recipe on the other hand goes like this:

  1. Go to Deano’s house
  2. Ask Deano to make you a hamburger
  3. Drink Deono’s wine.

I’m liking that recipe 🙂

Now if you’re a framework author, or an organizational architect then maybe you’ve gotta be more like Dean but it’s be really nice if pretty much everyone else could be Frank.

Comments

Popular posts from this blog

On working remote

The last company I worked for, did have an office space, but the code was all on Github, infra on AWS, we tracked issues over Asana and more or less each person had at least one project they could call "their own" (I had a bunch of them ;-)). This worked pretty well. And it gave me a feeling that working remote would not be very different from this. So when we started working on our own startup, we started with working from our homes. It looked great at first. I could now spend more time with Mom and could work at leisure. However, it is not as good as it looks like. At times it just feels you are busy without business, that you had been working, yet didn't achieve much. If you are evaluating working from home and are not sure of how to start, or you already do (then please review and add your views in comments) and feel like you were better off in the office, do read on. Remote work is great. But a physical office is better. So if you can, find yourself a co-working s

Capture and compare stdout in python unit tests

A recent fan of TDD, I set out to write tests for whatever comes my way. And there was one feature where the code would print messages to the console. Now - I had tests written for the API but I could not get my head around ways to capture these messages in my unittests. After some searching and some stroke of genius, here's how I accomplished capturing stdout.

Todo lists are overrated

My tasks come from a variety of sources: 1) Tasks from emails  2) Meeting notes with details of people who participated  3) Project related tasks that can have a long format and can be tagged/ delegated  4) Scratchpad for unrefined ideas  5) Detailed documentation for completed technical tasks / ideas  6) FIFO list of high priority small daily tasks No one app has been able to map all the requirements above, and I have tried a lot of them! In my lifetime I’ve tried a dozen todo apps. In the beginning they all seem different, novel and special. Slick UI, shortcuts, tags, subtasks, the list goes on and on. But all our stories were the same: I start using the new app, then after awhile I stop using it. Up until the last week I thought the problem was in myself (you probably think so too). After all, David Allen seems to have figured this shit out. Also there are people leaving long 5 star reviews on every major todo list app, they discuss them on forums, recommend them to friends. But the