The third category of technical debt

Tim Bull posted a fantastic comment on my last post about Technical Debt and I thought it would be good to share it again broadly here. 

—

“There’s a third category of technical debt which is subtly different.  Decisions that are made knowing that there is a better solution, but that the business stage or problem doesn’t validate that level of effort yet.

I think this is increasingly common in Lean Startups, where you do the minimum to validate the idea, but you are often left you with Technical Debt (we know this won’t work when we get to 100,000 users, but it’s fine for 1,000).  You know there is a better solution, but you trade speed and validation for future benefit.

You’re spot on when you say that it’s the ability to pay it down that matters – like with all debt really.  Technical debt isn’t inherently bad, but if you take on more than you’re ability to repay it in the future you’re in trouble!”

—

Yesterday, Alex talked about a government that was continuing to use a traffic model created in the 70’s to plan their roads and new infrastructure build. Besides the point that it’s not really very lean to be still using a template from 40 years ago to define today’s new roads (!) but I also feel comfortable saying that’s a direction that should have been pivoted a long time ago. However, the government had sunk a significant cost into creating said new roads.

Has anyone heard of any organizations out there, not working with code, that have been working in a more agile way to pay back their debt/sunk costs?

Technical Debt

The idea of technical debt is a fairly old one in engineering circles and it has enormous relevance to the way we solve business problems in organizations today. This came up over a coffee discussion today with Alex Steffens and Ross Hill. We discussed the problem of getting people to change a decision, or create a new solution, when there was already a sunk cost that had been invested in said solution. The idea of sunk cost, seemed to overlap heavily to the idea of technical debt.

Pete Yandell once walked me through how he defined technical debt, and I’d like to share that here today.

Technical debt is essentially the idea that once you release a piece of work, it has a number of flaws in it which require maintenance. This is true of everything in an organisation, regardless of whether what they are doing is code based or not. The key is not how you eradicate technical debt, but how you actively maintain it and pay it down..

There are two main types of technical debt:

1) Debt is accrued through poor work and/or poor decisions made in the present day, given the best present data.

The debt is accrued through poor decisions and poor execution at the time of deployment. This might be someone producing work that’s not up to scratch, or just a group of people making a decision which is not ideal even in the current time.

2) Debt is accrued over time, as a decision that was correctly made years ago becomes less correct as new solutions and opportunities appear.

Pete explained that, as an engineer, he had the chance to pay down some debt and make his code better each time he produced some new code. In an agile world, organizations produce new work in a consistent pattern. If that’s the paradigm that an organisation runs by, then whenever new work is created there is also a new chance to pay down some of the old debt that exists – be that type 1 or 2 above.

And so, we are seeing many organizations moving closer towards a more agile way of practicing business. This will have great ramifications when the world is faced with making decisions where sunk costs are present, which need to be reversed because it gives people a guided way to pay the dent down gradually – rather than in one big, expensive hit

Have you read Switch, by Chris and Dan Heath?

I’m about to read the book Switch, by Chris and Dan Heath and wanted to get your opinions on it. Call it a pre-read book review. I was in at Inspire9 yesterday and saw the beautiful #i9bookshelf in the ‘flesh.’ I love bookselves. I believe they provide a window in to the expertise, thoughts and mind of the people that own them. I’ve even put up a digital version of my bookshelf on this blog, which you can access through the books link on the navigation bar in the top right corner.

I noticed Switch, and grabbed it. I read a few passages on the train on the way home and thought I would share this lovely analogy which resonated with me.

“Haidt says that our emotional side is an Elephant and our rational side is its Rider. Perched atop the Elephant, the Rider holds the reins and seems to be the leader. But the Ride’s control is precarious because the Rider is so small relative to the Elephant. Anytime the six-ton Elephant and the Rider disagree about which direction to go, the Rider is going to lose. He’s completely overmatched.”

What were you’re favourite passages of the book? How did it compare, for you, to Chip and Dan’s first book, Made to Stick? I think it’s going to be interesting, because of it’s application to our work. If we work hard to change the Rider, then we end up simply setting ourselves up for failure. If we look to entice the Elephant in our efforts, then we will stand a chance of creating more sustainable and lasting change. I’m looking forward to the book. Let me know your thoughts below in the comments.

What's your craft?

I wrote yesterday about how beautiful the new Path was. Behind that statement, though, is the belief that the people working on the application have honed their craft to such a point that what they are producing vergers on being art. I’d like to offer that up for discussion today, with a beautiful clip from the Made By Hand series being produced at the moment.

I love that in the video above, Joel walks us through the progression of how his craft came about. He talks about familiar ideas, like the need to invest 10,000 hours or more to get to the point where maybe, just maybe what you do could become art. Xavier Shay and Col Duthie have both written great blog posts I often reflect upon where they discuss what drives them in the pursuit of their crafts. My favorite passage from Col’s post is this one:

“There is something that moves deep inside when I come to the end of a complex or challenging facilitation assignment and have delivered over and above. I love the look in people’s eyes when they reflect back on what we have accomplished. Inside I say to myself, “It’s what I do.”

I recommend reading Col’s post, Nice Work and Xaviers “Quitting A Six Figure Job: One Year Later” to get the full stories.

In my world, even though I’m very rarely making things by hand I’m constantly trying to understand what my craft may be. What am I, or have I, spent 10,000 hours working towards perfecting in my life and what do I want to continue investing my time in? It’s not clear to me yet, but I believe I have a great skill in helping groups come together to solve new problems they’re facing in their organisations. It’s a theme I’m going to continue to invest in and see what comes.

The new Path is beautiful

Path launched a new version of their app recently, and I’ve been using it a fair bit the last few days. It’s beautiful. Download it. Why?

I was a Path user about a year ago and loved it then but was very disappointed when the team launched a new version of the app which forced me to completely integrated with Facebook. I’m not a huge Facebook user, so this caused me to drop the app like a bad smell. It made me sad because one of the main reasons I loved the first iteration of Path was that it provided me the feeling of being with my best friends, whenever I was having a ‘moment.’

Path

When Path launched originally, Ross introduced it to me and explained that it was built around sharing moments. I was hooked instantly. I share a lot of stuff on Twitter, but I’d dare say most of that is either talking with others about news or stuff that’s relevant to location. I also use Twitter to connect with new people and my community at large – it’s an amazing service for bring more amazing people into my life. Path provided me something new. It provided the chance to share intimate moments and happenings that were special to me, with people that were very special to me. Semantics, maybe, but that’s why the tighter integration with Facebook killed the first version of the app for me. It made it feel less intimate and just another place to speak. When I posted something to Path, it meant something to me.

And so, when Justine told me that the new version was beautiful, I nearly didn’t believe her but went and updated the app. And it’s beautiful.

Yesterday I caught up with Jason, Nathan and Ross for breakfast; followed by a walk along St Kilda and Port Melbourne beach before dinner on Acland St. Whilst we we’re together, we chatted about a whole host of things, but also posted a few special moments to Path. In that time, we shared what Eddie was doing and also reminded Justine (a fellow Yammerati) that it’s the weekend in Australia at the moment and so it was okay that we weren’t working hard! It was a lovely day, which we finished by comparing Christmas parties with James, Luke and Rez.

I’m excited by the new Path, because it offers a new type of stream in the social media landscape. When Facebook and Twitter launched years ago, they offered us something new. The chance to connect with people without needing to know them. It provided this because it became easier for people to share what was happening in their lives. People had always been able to blog, but it’s a hard habit to keep up and takes an investment most people don’t want to make. I’ve been blogging for 4 years now, but have only posted 140 times. I’ve been using Twitter for about the same time, and have posted more than 10,000 times.

Twitter and Facebook changed the investment required to post something, but because it was so new most people added people to their stream and ended up with hundreds, if not thousands of connections. Some of us learned to deal with the stream but a host of people I know have continued to follow people and instead use various apps like Tweetdeck and Hootsuite to segment their follow lists, always battling to keep the tools relevant.

This is why Path is important to me and why I’m excited to see where Dave Morin and the team take it. We now have multiple streams in our lives, which brings more complexity into how we decide to spend our attention. Path provides a place where I can give attention to the people that are closest to me, in the same way that Twitter gave me the ability to give attention to the people that I didn’t know yet and Yammer provided me the ability to provide attention to the work my colleagues are doing.