I ran across a great post by Dan Kindeborg that thought me a lot of about effect mapping (prequel to Impact mapping). “Sadly” it was in Swedish and I got to keep the material to myself… Or well no - that’s not how I roll. So asked Dan for permission to translate the original post here on my blog. He was totally fine with that so here it is. When you read stuff about UX and design below it’s Dan’s word. Don’t worry - i still know nothing about that. But I learned a lot by reading this I hope you do too. So, from the next paragraph when you read “I think” it’s actually Dan thinking. Just so you know. Over to Dan.

Lean UX with effect map

An IT-project is often started with an idea about how business impact can be...

I was asked to help a client to facilitate a Impact Mapping workshop. An initial map had already been created as a first try and we talked about around it to get a feel for where the discussion would head.

The main goal (refered to as the WHY on an impact map) was well-established and understood in the organization. Which was a big “phew” for me, since that is a hard case to crack in a single workshop, I reckon  I foresee lengthy discussions with political undertones, at least if it’s keept on a company-wide-level.

But in this case the goal was set, let’s say that it was “Get 100 000 active users by 2014”.

On the next level, WHO, the proposed map and reasoning confused me a bit. And I didn’t have an answers to explain why.

On the next level the map showed the different teams in...

Well the title really says it all, but there’s big changes coming for me and my family this autumn. We’re moving to Bandung, Indonesia to work at a hospital for the Salvation Army there. That statement may cause some questions to arise in your head. Let me see if I can foresee them?

Why?

There’s three big answers to that question and they come in chronological order. On my first date with Elin (8 years ago now, my wife since 6 years) she told me that she wanted to work abroad. In a “developing country”. That’s her life long dream and the reason she’s decided to become a nurse in the first place. Now the opportunity has come to fulfill that dream - and I get to be part of it!

Secondly: I have the Salvation Army to thank for so many things. Things that I use in my everyday life at...

I was at the hairdresser yesterday. I’m not very particular about my hair but it was starting to look a bit like this.

When I want it to be more like this guy to the left.

The conversations at most hair dressers in Sweden is not very interested, mostly due to the fact that I’m not interested in hair. Particularly mine. So while I was seated in the chair thoughts from some discussions on prioritization and flow for a team at a client.

Low WIP and flow are concepts that are well understood and often implemented as well at this particular client but the implications of such a strategy was interesting. And, oddly enough, I saw some...

I’m back from AgileSverige - the premier agile conference in Sweden (IMHO) and this year was no exception. Or rather it was - it was exceptionally great from where I sat.

One of the talks that really got me thinking was about Mobprogramming by Tobbe Andeberg and Ville Svärd. Not the technique itself but rather the implications of such a team…

Mobprogramming is easy to do; put your entire team in a room. Give them a single keyboard. Work together to solve the problem at hand. Then take the next. Then the next. And so on. It’s like pair programming but for an entire team.

I’m not sure that a team would benefit by doing mobprogramming all the time but the concept got me thinking, thanks to the great presentation by Tobbe and Ville. What if… In this post I’ll share some ideas and thoughts that...

In recent years the Lean Startup movement has really taken off. For a great reason as well. It’s a really appealing and excellent described framework for how to get validated learning of your startup idea fast.  For me as a Lean-dude it all sounds very nice and fits nicely into my current understanding and beliefs.

But as always ideas like the ones presented in Lean Startup will be stolen, then tweaked “a bit” and then finally declared unsuitable for the things that it didn’t was intended to solve in the first place. I’ve seen it again and again; agile, scrum, specification by example is just a couple of examples that comes out top of mind.

In this post I’ll share some things that I’ve been thinking about around this recently. If I’m wrong about these things I look forward to your comments and further education on the topic.

MVP

The thing...

I’m surrounded by brilliant minds at work. Both at my company (Aptitud), at my clients and in my community. They make me think a lot and quite clearly thinks a lot themselves too.

But sometimes I think we think too much (cannot wait for the reaction to that contradictive sentence :)) - and we should do things instead. It’s in doing we learn and see how stuff work out and how well our hypothesis stands up to the reality that we throw them into.

Let me give you a few … well examples and ideas that have formed my thinking around this.

Getting to know new people

| | |:————————————————————————————:| | | | From http://redstarresume.wordpress.com |

I have never been in a situation to hire someone - although I have done A LOT (50+) prospect...

In my last post I related two stories that I’ve been a part of and that got me thinking about what we (or me at least) code for: change or stability.

The post got attention (amazing attention for a small time blogger like me, actually almost afraid of writing now :S) and quite a lot of questions was posed. These of course got me thinking even more and I realized that I needed to follow up on the post. So here it is: some thoughts (and some answers) to questions and arguments I’ve had during the last week.

Mindset vs practice

What I bluntly failed to convey in the first post was the mindset aspect of it all. For me the difference in approaches was one of mindset in what we develop; do we write the code thinking that it will change or that this is the last time...

Let me tell you a story: when I was in university I took an “advanced” object oriented programming course. This was my first exposure to the topic and I was lost big time. The course was taught in SmallTalk had a very different format; the first day we got an assignment from the professor that ran throughout the 4 week course.

We were very excited since we were going to write a game. An old-school text-input adventure game a la Zork. We teamed up three people in groups and went to the professor smalled crammed room. Here we got the instructions on a single sheet of paper. We almost ran out of there.

Just as we reached the door of the room he called us back (I’m sure he had time that call to perfection):

“Oh yeah, almost forgot. Two weeks from now I will come by and change...

SpecFlow is a wonderful tool. With a lot of hidden gems inside of it. I have been using and coding on it now for about 4 years and still I often forget about features and extension points that Gaspar and the community has put in there.

For example: did you know that there’s an inversion of control framework built right into SpecFlow? Now you do and in this post I wanted to show you one way that you could use that feature to make your step definitions more maintainable.

I found this feature (again, i had heard about it before) when Gaspar mentioned it too me after my presentation at CukeUp 2013 and the usage is part of “Pushing the HOW down” which I wrote at length on before.

The Context injection feature (as it’s called in SpecFlow) is one of those “just works”-feature and...