March 12, 2011

Tools for deciding, or confusing?

The last few days have been spent clarifying the problem and then trying to understand the tools best suited to solving it. We used a little bit of a methodological approach even in deciding which tools to try (!), and then each person volunteered to try to implement the ones that interested them. Upon meeting again, we attempted to present the results of our findings to each other, most of us thinking that our work had got us to the point where the group might be able to finalise decisions.

How wrong we were!!! Our internal biases had once again led us astray, and into thinking that our work could be without fault, and that each of the others would automatically understand what we had worked on, making the assumption that they had the same tacit knowledge that we did! It's becoming clear to me that managing all kinds of bias is certainly the biggest and most important challenge when making any judgement or decision.

What actually happened was that we found our work either littered with mistakes we hadn't previously seen, or in some cases, the rest of the group held wildly different views when presented with the work we had each done. This meant that much of what we had done turned out to be work in progress rather than the finished article, as so much rework was required! For example, I had largely focused on the decision trees, both for deciding what our options were and working through the possible results of around 8 different resultant scenarios. But, I'd failed to take into account that we might need another tree entirely for choosing the best location, or that sunk costs shouldn't have been included in the expected value calculations...

Once again, that means that after much confusing of our teammates, who might not have known the tools we worked with as well as we did, and realising that even we might not have used them correctly and entirely, or done requisite research, we find ourselves unable to make a decision still! Monday will be an important day for this.

Reflecting back, and thinking about future applications, I think that this will always be a problem. We will often have to present to colleagues entirely unfamiliar with our methods, so it will be crucial to learn how to translate our resuls in a transparent way, making sure to avoid the curse of knowledge. Of course there will be times when we fail to see errors in our work, so it is also very helpful to have colleagues who also know the methods and can check our work. This is quite a common approach in most engineering situations already, but perhaps as managers or leaders, we are not quite so used to this.


- 3 comments by 1 or more people Not publicly viewable

  1. It is like that Yanik and perhaps the whole idea of discussion teams before the start of a project is to find different approaches even with the same tools. The way that you see a problem differs from the perception of other co workers, classmates, etc. The understanding of the use of a tool is not exempt of this same issue, so remember one of the points of taking the best decision is analysing “all” the alternatives and in this case is “all” the different points of view and agree in the “optimal” one for the group.

    12 Mar 2011, 16:55

  2. I think also, it will be really interesting to see the different decisions that all the teams make, which will be based on the way they have each interpreted the same data. There are so many ways you could approach this, and as you say, even all the tools have the potential for very different use.

    12 Mar 2011, 17:32

  3. I so agree with you. Had the same issue. Working on the decision tree and presenting it to my group turned out to be more difficult as I thought. As you will maybe see in our presentation I started the whole tree different than others expected. So it was really hard to explain it and convince the others. I liked discussing about it, but I noticed how hard it is to convey your way of thinking and your logic to others. For me it was totally clear but some others did not see it in the first place. So yes it really can lead to confusion within a team but on the other hand the outcome is a lot better than just doing it by your own. Furthermore these discussion within the team makes your decision really robust because you can defend your idea and your way after long-winded discussions. So even if it takes its time i think especially with regard to your last paragraph it is totally worth.

    13 Mar 2011, 11:18


Add a comment

You are not allowed to comment on this entry as it has restricted commenting permissions.

March 2011

Mo Tu We Th Fr Sa Su
Feb |  Today  | Apr
   1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31         

Search this blog

Tags

Galleries

Most recent comments

  • Nice examples Yanik, especially the second one from OPP that shows that the redundancy of knowledge … by on this entry
  • It was interesting to consider Nonaka's view of human resource redundancy as an knowledge asset and … by on this entry
  • Hi, Surya. I agree with you that human being get extremely paranoid now. It is extremely unfair to u… by on this entry
  • I really like the way you have coined the term knowledge economy and stuffs with its relative approa… by on this entry
  • Hi, Yanik. Great post here! When I saw the movies 'Lord of the rings' once again tonight, I was thin… by on this entry

Blog archive

Loading…
Not signed in
Sign in

Powered by BlogBuilder
© MMXXIII