Decision Mechanics

Insight. Applied.

  • Services
    • Decision analysis
    • Big data analysis
    • Software development
  • Articles
  • Blog
  • Privacy
  • Hire us

1st International Workshop on Complexity and Real World Applications—first call for interest

January 11, 2010 By editor

Title: 1st International Workshop on Complexity and Real World Applications: Using the Tools and Concepts from the Complexity Sciences to Support Real World Decision-making Activities

Date: July 21–23, 2010

Location: Southampton, England

Hosted by: ISCE Publishing (US) and Decision Mechanics (UK)

Contact: Kurt Richardson, ISCE Publishing (kurt@isce.edu)

Alice Munro, the Canadian writer, once said, “The complexity of things—the things within things—just seems to be endless. I mean nothing is easy, nothing is simple.” The more time we spend studying complexity, the more her sentiments are shared.

Of course, the very pervasiveness of this complexity is the reason we gravitate towards it—like basin-dwelling moths to the attractor flame. The increasing number of “complexity”-focused journals stands as a testament to the progress that is being made in this young discipline.

Our passion, however, lies in the possibility of releasing all these ideas into the wider ecosystem. While many of the more beguiling concepts have embedded themselves in everyday language, complexity thinking, as a formal discipline, is clearly much less widespread. There are islands of success, but the intellectual tectonic shifts required to make them continents have not been forthcoming.

Why is this? Maybe it’s partially down to the packaging. Complexity thinking is hard. Much of the research draws on sophisticated philosophy. This hinders the broad adoption of the ideas in the professional mainstream. The fact that the amount of research in the area of tools is dwarfed by that in the areas or philosophy and theory serves to compound the problem. A rough analysis of the papers published in the journal Emergence: Complexity & Organization, for example, in 2007 shows that less than 10% of them were primarily concerned with the development of tools for practitioners.

There is no doubt that the packaging of complexity into a neat, user-friendly shrink-wrapped “box” is a tall order. It’s difficult enough to just describe the damn thing! Maybe this is because we’ve been gradually increasing the complexity of complexity. As we’ve experienced the failures of the systems engineering paradigm, and seen the limitations of “new reductionism”, our definition of complexity has become increasingly elaborate. Naturally, this has trickled down the pipeline to challenge the tool developers.

But, maybe we can best approach tools from another theoretical direction—and use our understanding of complexity to evaluate and enhance them. Richardson (2008) has discussed the notion of a “modeling culture” where a practitioner uses linear tools in a nonlinear manner. This results in a kind of “cyborg” tool where man is responsible for providing the complex context. However, as complexity researchers, surely we’d like to provide man with more assistance in this area.

The motivation for this workshop is to further this endeavor. The organizers want to receive submissions that focus on real world applications of complexity thinking. Theory will certainly not be discouraged, but it must be followed by at least one case in which the theory-informed tool that was developed was used (successfully or not) to aid a real world decision-maker. By this we do not mean the application of a complexity framework to reinterpret a past event. Furthermore, we are very keen to attract those from outside the “traditional” complexity community—such as software developers, for example. The development of tools sensitive to complexity requires a multi-/cross-disciplinary effort, and the “complexity” community does not hold any particular claims to having the best language and concepts to confront and manage complexity. For example, much of the development in the complexity community over the past 15-20 years had already occurred within the soft systems community, and from both communities, simultaneous efforts have unfolded that, although approach matters from different directions, share similar aims, philosophies, and methods.

Suggested topics

In order to provide at least some basic topical guidelines for the boundaries of the event, a number of characteristics of “complexity-sensitive” tools are listed below. These are presented purely for guidance—please feel free to ignore our “arbitrary” framework if you have better ideas.

Boundary critique

The process of boundary critique is arguably the key feature of complexity thinking. We view this as the central element, with the remaining elements we will define being corollaries of the commitment to it.

Life is defined by where we draw the lines. The fact that defining these boundaries is so difficult is part of what makes life interesting. All boundaries are no more than temporary patterns resulting from a filtering process (e.g., based on personal values). As such, they are to some degree arbitrary (at the same time both quasi-objective and inter-subjective) and require ongoing review to understand how they shape our context of interest—and how our context of interest shapes them.

Pluralism

Given the non-reality of all boundaries (…very Buddhist…) we cannot rely completely on any one perspective. All perspectives are ideals and the real world is not idealistic. Mono-paradigmatic approaches are risky as they only tell part of the story.

Perspective is being used here in the broadest possible sense. It refers to individual opinions as well as particular methodologies. In a sense, these perspectives can be equated with stakeholders as they all have a vested interest in being recognized as relevant and important in the war of ideas—a kind of evolutionary memetics.

Being aware of multiple perspectives equips you for more effective boundary critique, of course. This is one of the processes that helps provide crowds with their wisdom.

Synthesis

Synthesis is closely related to pluralism. It relates to the attempt, through the use of boundary critique and pluralism, to tailor descriptions (models) to the context of interest, rather than have the model shape the context. Or, to put it another way, have the dog wag the model tail, rather than vice versa.

Of course, it is never this simple. By definition, the context of interest must pay some lip service to the model. If not, the model would have to be as complex as the reality it seeks to explain. It is quite reasonable to take a particular context and evolve it so that it can be more easily understood through a model. The key is that the “evolution” is reflected in the real world and is not just something that happens in the mind of the analyst. So, through boundary critique, an incoherent plurality is beaten and brutalized into a context specific and provisionally synthetic whole.

This synthetic whole can still only be a bastardization of the real world. It can only, therefore, be a tool for thought, rather than a proxy for reality. We need to maintain some ontological distance from our constructions. The commitment to “boundary critique” and “pluralism”—and maybe “improvement”, as in Critical Systems Thinking—is more important than the final model itself.

Emergence

The starting point of an analysis should not completely predetermine the end point of the analysis. This should lead us to be wary of purely systematic approaches. We need the flexibility and confidence to wander through “analysis space” (evolving as a consequence of our boundary critiques) in a way that acknowledges the emerging view of the real world, rather than the favored method/methodology. In addition, we need to recognize that the real world will collectively conspire to respond to our design interventions in a variety of ways—some of them not considered by the “designers”.

This requires us to engage in a tricky balancing act. Being overly prescriptive leads to narrow-minded analysis, while “anything goes” analysis can lead nowhere. Emergence requires some kind of container to filter out the cacophonous noise of reality. The structure of that container, however, should not remain fixed or overly restrictive.

Timeliness

Although the allocation of boundaries (in both space and time) is essential to “doing stuff”, control/design in complex systems is a never ending process. Most models used in support of decisions will, at best, only have short-term applicability. To guide any complex system in a particular direction requires ongoing analysis and intervention. And, of course, with the analyst being part of the complex system he seeks to affect, the notion of a “particular direction” will itself evolve. No room for long-term dogmatism here!

Event format

The event is deliberately called a “workshop” as number will be limited to no more than 20 participants. It is planned that the presentations given will be used as much as a source for further discussion as they are platforms for individual speakers to present their tools. As such, the bulk of the time will be set aside for structured discussion of the tools presented—and ideas for future tools.

An ISBN-referenced proceedings will be available in print shortly after the event (and available to non-participants on order—complementary copies will be provided for each workshop participant). A special issue of the journal Emergence: Complexity & Organization may also be produced depending on the number of submissions received. Paper submission is not a prerequisite for attendance, but authors of accepted papers will be given priority.

Provisional Timetable

Please let us know of your interest in attending this event as soon as possible. Attendance at the event will be strictly limited to 20 so as to encourage genuine dialogue amongst participants – selection of attendees will be determined simply on a first-come first-served basis (with the additional consideration of paper relevance, of course).

A block of rooms will be reserved at the workshop hotel as soon as final arrangements are made, and a special rate negotiated. Specific location details will be provided shortly.

Extended abstracts of around 1000 words to be submitted to Dr. Kurt Richardson (kurt@isce.edu) by end of March, 2010—but please notify us of your interest as soon as possible.

The decision by the review board (comprised of members of the hosting organizations) invite submission of a full paper—to be no longer than 5000 words—will occur by end of April, 9, 2010. Please note that paper submission is not a pre-requisite for attendance, but that priority will be given to paper contributors.

Full papers to be submitted by end of June, 2010, to give enough time to prepare them for distribution to all participants before the event itself.

The cost of registration will be US $595 and must be paid in full at the time of final paper submission – a registration form will sent to participants after the decision regarding paper acceptance has been made. As well as administrative and location costs, fees will also cover lunch and coffee/tea breaks during the event as well as a dinner event at the close of the first day. Participants will be responsible for their own hotel costs.

If you would like to attend the workshop please send an email to Kurt Richardson (kurt@isce.edu) with the following information: name, affiliation and position (if any), address, phone, fax, and email. Kurt will contact you with further information regarding hotel confirmation and payment of workshop fees.

If you have any questions please do not hesitate to contact Kurt.

Filed Under: News

Making better decisions by “Getting Things Done”

January 8, 2010 By editor

Important decisions require concentrated attention.

One obstacle to effective decision-making is the inability of decision-makers to carve out the time required to give the decision due consideration. It is far too easy to get caught up in the day-to-day minutiae of running your organization (and life).

If you are constantly distracted by your “to do” list, you will never find the time for the analysis and reflection your major decisions deserve. A clear head is an essential prerequisite for effective decision-making. If you don’t have your basic workload under control, the quality of your decisions will suffer.

If you find that you need some help in getting your day-to-day responsibilities under control, there are numerous “personal productivity” solutions in the marketplace. At Decision Mechanics we’ve adopted David Allen’s “Getting Things Done”. It’s comprehensive and pragmatic.

The basic premise of “Getting Things Done” is that you need “de-clutter” your mind. If you’re relying on your memory to manage your “to do” list you’re keeping it occupied with information you’re not ready to act on. Our minds have a limited capacity to keep information in the foreground, so you’re wasting valuable mental resources that could be used on your major decisions.

To allow your mind to let go of things you must convince it that they will be dealt with, appropriately, at some point in the future. And to convince your mind of this you need repositories (e.g. folders, lists) that you store all your stuff in and review on a regular basis.

As stuff (e.g. letters, emails, ideas, appointments, tasks) enters your field of attention, it is placed in an “in basket”. This may actually be an in basket on your desk…or it may be a box file containing scraps of paper…or the inbox of your email client… In fact, you are likely to have more than one of these “in baskets”. For example, you may have an in tray at the office, a box file at home and your email inbox. The idea is to collect all your stuff in as few places as possible.

The next stage of the process is periodically (e.g. once a day) reviewing the stuff in your “in baskets”. You go through the items in strict order of when they were placed in the repository (no cherry-picking) and decide whether something is actionable. If not, you file it (as a reference, or as something to be prompted about in the future).

If an item is actionable—i.e. you need to do something about it (beyond throwing it away or filing it)—and that action can be completed in less than two minutes, complete it and discard the item. Completing one action may result in another task. In this case, add the new task to one of your “in baskets” (e.g. as a scribbled note).

An actionable item that takes longer than two minutes to complete will either:

  • need to be done by a set date (implied by the action), in which case you put it on your calendar;
  • need to be done as soon as possible, in which case you put it on your “next actions” list; or
  • need to be delegated, in which case you make a note on your “waiting for” list.

Some tasks, such as projects, may require multiple actions to complete. In which case, you place the overall task on a “projects” list and add the next thing to be done on that project to your “next actions” list.

Your calendar, “next actions” list and “waiting for” list then contain your main tasks. When you find yourself with time available, you can return to one of these lists and choose an item to work on. The item you choose will depend on the time available, your frame of mind, etc.

The key to making the “Getting Things Done” process work for you is being disciplined in your review process. You must review all your repositories/lists religiously. If not, your mind will start holding onto things again. The one person you can’t fool is yourself.

This has been a necessarily brief introduction to Allen’s ideas, but we unreservedly recommend his book and website to those looking to organize their professional (or personal) lives so that they can place more focus on the decisions that really matter.

Filed Under: General Tagged With: process

Decision-making versus decision-aiding

December 9, 2009 By editor

The very idea of using software to assist decision-making often prompts a negative, knee-jerk reaction. Surely decision-making is a creative endeavor requiring judgement and insight? How can we replace experienced leaders with technology?

First, it is important to recognize that assisting decision-makers does not equate to replacing them. Have you closed your finance department since you purchased Excel? No? I thought not.

Software can aid decision-makers (primarily) by:

  1. managing data
  2. providing structure
  3. encoding best practices

Managing data is the most obvious benefit that software can provide. Data analysis tools can summarize large volumes of data, allowing decision-makers to separate the wood from the trees. However, software can also assist decision-makers by managing their assumptions. We’ve all had the experience of constantly revisiting the same issues when involved in making complex decisions. If we use software to model each stage of the process, we can return to previously considered issues without having to recreate everything for the umpteenth time.

The provision of structure is something that is often overlooked. Without a formal decision-making model, it’s too easy to avoid facing important facts. Models ensure that we don’t get caught up in the excitement of a major decision and become blind to inconvenient data that doesn’t support the “sexy” option. Models don’t have to be encapsulated in software, but doing so helps promote disciplined behavior—you can’t “hand-wave” at a computer program.

Finally, good decision-aiding software supports the spread of best practices throughout your organization. Many powerful decision-making techniques take time to learn—and we all know that time is becoming increasingly precious. Decision-aiding software can guide decision-makers through the mechanics of a process, providing all decision-makers with access to the latest decision science techniques.

So, the next time you have to make a decision, consider letting software onto the team. It’s there to help…

Filed Under: General Tagged With: decision-aiding

  • « Previous Page
  • 1
  • …
  • 57
  • 58
  • 59

Copyright © 2026 · Decision Mechanics Limited · info@decisionmechanics.com