As a programmer, I often end up trying to explain non-technical concepts to non-technical people using things that I’ve picked up as a programmer. Often it doesn’t pay off. “Don’t Repeat Yourself” or “Tell - don’t ask” is not always easy to explain or translate, even if they hold truths and wisdom.

Today I tried to explain Technical Debt to a director of a hospital. That didn’t really work - my mistake. However, the Technical Debt metaphor is based on something that most grown-up people understand: financial debt.

In this instance, we talked about how communication could be improved (as it always could be, I would think) in the hospital. In order to explain this, I drew this graph for her:

You know about debt, right? I asked her. The longer we wait to do down-payments, the more the debt increases, due to the interest...

At my current client we’re starting to work with improvements, as I wrote about before. The things I talk about in that post is small changes, but bigger things we handle on separate lines. For now. That might change.

Today I tried to introduce an idea of experimenting to the team. Let me walk you through it, because I found that by just changing the language a little bit, we got a much better understanding and reduced anxiety. Also I think they all like it.

We are trying to bring our profitability up and hence try to find new ways to serve more customers. In this case there was a suggestion to prolong the opening hours for one department to 1900 on weekdays and keep it open on Sundays too. It’s now closing at 1400 and is not open at all on Sundays.

(Ok, it’s a bit of...

We break for something different. This is not my normal IT/agile/lean post. It’s about God and his care for me

Happy that you continued to read.

I’ve been having some hard days at work. I was very angry and it affected not only me but also those around me. Also I was being affected physically with dizziness and head ache. For the first time in my life I found it better to go home and cool off a couple of days.

I felt so tired and was beginning to doubt if I’m really doing the right thing. In the right place.

So I did things that pick me up. Playing hymns on my euphonium is one of those things. My playing is closely related to my faith, since I’ve made most religious experiences with my instrument in hand, playing in the most cases.

What happened this time was Gods way...

One of the best and shortest explanations of what Lean is really about, I’ve found in the “This is Lean” book by Niclas Modig and Per Åhlström.

The thing that made it “click” for me was a diagram that contrasted Resource efficiency with Flow efficiency. I love it! Even though I might have talked about Efficiency versus Effectiveness… Well, it’s not my book—maybe that’s why it’s famous and I’m not.

Basically:

• Scoring high on Resource efficiency is, for example, a melting plant for steel. You want that running all the time. You keep a lot of material ready to be processed because the plant is so expensive to shut down.
• Scoring high on Flow efficiency is, for example, the fire department. Most of the time they have enormous overcapacity, just sitting around waiting until they are needed. We want much less work...

Goldfish by josullivan.59, used under Creative Commons

That’s a saying I’ve heard in a number of places. I have a terrible memory. Ah, it’s great and everything, but it’s sadly short. So I don’t lie. I’m too stupid I have too short a memory for that.

That’s such a relief! I know that going in. In everything I do. I don’t lie. I play it open. There - now you know too.

In fact, I would go so far as to say that it makes me better. Because since I’m playing it open it puts the pressure on me to be great and make sure that my work can withstand scrutiny and review by everyone that I share it with. It’s not scary - because that is how it is from the start.

This is the same kind of thinking that can...

I hate fights.

And arguments.

Hey, even discussions sometimes I find uncomfortable or at least boring.

Note that I try not to be a coward. I stand up for my beliefs and thoughts. But I don’t like to fight about them, that seems very common today. If you wanna pick a fight, just tweet any opinion under the #NoEstimates tag and you see what I don’t wanna.

From time to time I’ve withdrawn from blogging and social media. Just to get away. That might be cowardly, but I didn’t see the use continuing fighting about how to approach estimation, what JavaScript data access library is better etc. The world need you and me better elsewhere.

I’ve stopped being the guy at the computer in the cartoon to the right. But I’m still expressing my views.

In this blog post I’ll share how. I’ve...

The one talk that made the most impact of me have to be “Embrace Uncertainty” by Dan North. If you haven’t seen it… You’re dead to me Please view it now!

Dan North - Embracing Uncertainty from NDC Conferences on Vimeo.

The thing that stuck the most for me in there was the short, and depressing, sentence:

We are rather wrong than uncertain.

Meaning simply that we would rather run with something that we know for a fact to be wrong than to live with uncertainty. We are very uncomfortable with uncertainty. But for those that can embrace it there’s other type of control and “certainty” to be had.

Now… I’m beginning to think that this comes to us from an early age. I’ve done studies… the last one was this Saturday at the mall, with Albert (6).

Here’s the conversation we had at McDonald’s:

...

I talk a lot about effectiveness and how it differs from efficiency. This is probably due to two reasons: firstly, the difference between these two concepts is central to the lean mindset. Secondly, I’m Swedish.

Swedish is a very poor language compared to, for example, English, which is much richer. If I were to translate the first sentence of this blog post into Swedish, you’ll understand what I mean:

Jag pratar ofta om effektivitet och hur det skiljer sig från effektivitet

Ah, the poverty! It’s the same word. There’s no difference… in Swedish. I have yet to understand if that means that Swedes are focused on effectiveness or efficiency.

But this linguistic poverty has been a trigger for learning for me. I’ve really tried to deep dive into this.

To this date, this is the best and simplest way to describe the difference...

I’m working with vision statements and strategic planning right now. Man, this is an area that is really misunderstood and misused, I think. Also, and that’s what this post is about, I think it’s deliberately this way in order to get some wiggle room. I don’t understand that. We’ll get there.

Definitions

As always, I’ve learned a great deal while diving into this area again and here are the definitions that we are using and that I think are clarifying:

• Mission statement - Why are we here? What is our purpose? For example; Why does the Salvation Army exist in Indonesia?
• Vision - When we are doing the mission perfectly - what would that look like? This is a dream, a target and something to aspire to.
• Strategic plan - How will we get from where we are today to the vision?
...

We are working a lot with trust and transparency in my current team. Specifically on the transparency item one “trick” we have been using is to cc the entire team in as many conversations as possible.

I picked this practice up from the Stripe company and specifically this article, which is a great read if you haven’t seen it before.

Yes, they cc the whole company on everything. And I’ve seen this practice in action at Spotify to certain extent as well.

By now some of you need oxygen; MY GOD! My inbox will be flooded. And how could anyone be expected to read all of that?! Do these people do any real work?

There’s three comments that needs to be made here, that I have repeated a lot when trying to implement this in all kinds of teams;

First; you are not expected to...