About CCG

CCG is a group of experts of the information support to manufacturing operations offering advice, support and products to assist:
  • company, supply chain, production, engineering and IT executives to set up their vision, strategy and tactics regarding industrial systems operations and information
  • functional and IT managers and teams in charge of industrial IT transformation: master planning, IT architecture, organization and governance 

CCG Associates

A. V. Rajabahadur's picture
INDIA
Business Consultant
Bill Bosler's picture
UNITED STATES
Texas Consultants, Inc.
SME Energy/Refining
Jean Vieille's picture
FRANCE
Industrial systems consultant
José Gramdi's picture
FRANCE
Associate Professor
Mark McGregor's picture
UNITED KINGDOM
Business Process & Enterprise Architecture
Michel Devos's picture
BELGIUM
Business consultant - MES
Yves Samson's picture
SWITZERLAND
Principal Consultant

Expertise

  • Identification of relevant business process that involve inter-system communication
  • Involving ERP / MES / SCADA / LIMS / WES / AMS... systems
  • Relevant to Production, Inventory, Quality, Maintenance operations
  • BPMN description of workflows
  • Specification of transactions and messages
  • Implementation of defined messages based on the appropriate ISA95 standard models
  • Definition of a lexique mapping Enterprise taxonomy to ISA95 terminology and concerned systems
  • Customization of B2MML schemas to incorporate enterprise specific data
  • Definition of XML schemas based on UML data structure or any data modelling definition
  • Help for mapping information to the different systems
  • Specific competency on SAP/R3

 

ISA88 changed the way of dealing with automation. Our expertise addresses:

  • Agile and flexible control
  • Flow integrity management
  • Process control knowledge management
  • Organisation of application projects in highly parallelized tracks
  • Organisation of the development of an enterprise automation object repository

This brings robust, modular, and hierarchical automation design based on the ISA88 standard, flow analysis method and CCM manufacturing architecture framework.

 

Business processes represent the company practices for achieving irts duty and goals.  They must be continuously assessed monitored and improved to sustain a high efficiency level. They need to be and redesigned to match strategy, organization and technology changes. GGC experts provide:

  • Support for improving of the enterprise organization and processes in order to achieve the best results in all relevant expertise domains
  • Help for designing of the processes, workflows and organization

Data cleansing or data scrubbing is the act of detecting and correcting (or removing) corrupt or inaccurate records from a record set, table, or database. Used mainly in databases, the term refers to identifying incomplete, incorrect, inaccurate, irrelevant etc. parts of the data and then replacing, modifying or deleting this dirty data. After cleansing, a data set will be consistent with other similar data sets in the system. The inconsistencies detected or removed may have been originally caused by different data dictionary definitions of similar entities in different stores, may have been caused by user entry errors, or may have been corrupted in transmission or storage. Data cleansing differs from data validation in that validation almost invariably means data is rejected from the system at entry and is performed at entry time, rather than on batches of data. The actual process of data cleansing may involve removing typographical errors or validating and correcting values against a known list of entities. The validation may be strict (such as rejecting any address that does not have a valid postal code) or fuzzy (such as correcting records that partially match existing, known records).

This domain of expertise addresses the challenge of assessing objectively the impact of information technologies on the efficient operation of the enterprise in general, and more specificaly of its production system. It then addresses the implementation of an operational and dynamic planning for continuously adjusting the industrial IT resources (MES) to environement and strategy evolution. It supports the following action types:
  • Consolidate enterprise strategy definition and rodmap
  • Evaluate IT contribution to Enteprise Critical Success Factors
  • Develop KPIs to assess the actual IT efficiency with regards to CSFs
  • Define and implement processes to monitor IT support to strategy
  • Maintain the IT project porfolio, justify project investment with regards to:
    • Effective support to strategy
    • Short and long term benefits
    • Social, environmental and economic
  • Animate a dynamic master planning to supervise IT construction and deployement
  • Articulate the planning on Manufacturing Architecture in its structural and functional dimensions

Tied to the specific environment of industrial facilities, in close relationship with engineering and business systems, industrial IT is associated with particular problems of management, urbanization, infrastructure choices, and responsibility boundaries. Technical and organisational conflicts are frequents and hardly solved internallly.
 
Our experience and expertise support the adjustments of organization and processes to leverage in house competencies and ensure an efficient governance of industrial IT:

  • Compenetencies assessment
  • Organization schemes
  • Process definition
  • Maturity level approach
  • Obective control
  • Service level definition

Definition and implementation of relevant and consistent metrics and dashbords for assessing industrial performance

Modelling is at the heart of complex system mastery. The modelling exercise is not a goal by itself, but rather a step - an ongoing process actually - mandatory to support any improvement approach.
Modelling is thus a prerequisite fot any IT development from planning to realization. A major aspect of manufacturing architecture, this expertise addresses the different dimensions of the production sytstem as defined by CCM:
  • Asset modelling: Products, People, Equipment assets
  • Equipment control
  • Manufacturing processes
  • Company wide transformations & facilities processing capabilities
  • Operation management processes

Manufacturing Intelligence facilitate the feedback of actual performance and deviation resulting from the execution of work to assist the decision making

  • in real time by the operator or automation
  • in deferred time by R&D, engineering and maintenance
  •  
It concerns the different aspects of the manufacturing architecture:
  • Usage and performance of resources (human, equipment, material...)
  • Product Quality
  • Performance of physical and operational processes

Support to implementation of operations management methods

  • Process and quality improvement
  • Resourece effectiveness monitoring
  • Business Process Reengineering
  • Enterprise and Supply Chain Metrics and Critical Success Factors

Manufacturing Execution Systems and Manufacturing Operation Management address the support to manufacturing related operational activities through methods, best practices, and IT support.

This expertise domain covers the 8 ISA95 part 3 activities:

  • Detailed Scheduling
  • Dispatching
  • Execution Management
  • Data collection
  • Analysis
  • Tracking
  • Defintion Management
  • Resource Management

applied to the 4 manufacturing operation categories

  • Production
  • Maintenance
  • Quality
  • Inventory

It concerns the following aspects:

  • Operations visibility, KPIs
  • Operations monitoring and supervision
  • Open loop resource and process optimization
  • Closed loop optimization with feedback to local operator, engineering et R&D (see Manufacturing intelligence)

Optimization of work scheduling and resource usage

  • Classical finite capacity scheduling
  • Drum-Buffer-Rope, theory of constraints based scheduling methodology
The information dimensions of the production system are particularly complexe. Managing master/basis and histortical data is a prerequisite for any effort to rationalize and improve physical and operational processes and activities.
Applying normative repositories facilitate the definition of requirements and the implemention of solutions for applications such as :
  • Master Data Management
  • Production Data Collection and historization
  • Traceability and Genealogy
  • Any Manufacturing Operation Management related IT development

This expertise domain relies manly on standards like ISA95 parts 1/2 and ISA88 part 4 addressing

  • Data structures
  • Electronic signature
The product is the critical aset of the industrial enterprise. The industiral dynamics depends directly on the efficient management of the product lifecycle, from the market perception to the ability to deliver the customer orders. The production system is involved at the industrialization time (implementation of the product on the industrial system) and for the R&D and engineering feedback (product, process and methods improvement). Some possible actions to improve the product lifecycle:
  • Formal definition of Product requirement by R&D
  • Formal definition of manufacturing capabilities by engineering
  • Industrialisation support, "on the fly" product manufacturing definition

This expertise is based on the ISA88 part 3 standard that defines the basis for consistent product and process knowledge management and relationships to allow translation of product physico-chemical transformation requirements to executable equipment oriented procedures.

  • Design to performance
  • Design to Compliance/Qualification
  • FDA PAT - Process Analytical Technology
  • Risk management
  • Economical justification

Support to project realization by defining an optimal task breakdown and scheduling for speeding up IIPS development

Helping the transition process from user requirement and functional specification to actual solution design by:

  • Identifying and mapping software functional capabilities to solution independent functional requirements
  • Providing gap analysis and support to design the technical response to functional requirements

Services

Taking appropriate action to induce knowledge and practices to handle efficiently a given part of the CCM Body of Knowledge and associated methods and standards.
This can include:

  • Self learning documentation,
  • In-house training courses,
  • Workshops,
  • Open courses
  • Teaching in schools and universities, 
  • Writing articles, developping papers and reports under specific directions for neutral articles in magazines, promotional report and white papers

CCG Management consultants have developed their own methodologies to enable them to identify problems and serve as the basis for recommendations for more effective or efficient ways of performing business tasks.

Our involvement enables organizations to gain an external advice (a second much needed impartial eye). The scope of our Management Consulting services includes:

  • Helping organizations to improve their performance, primarily through the analysis of existing business problems and development of plans for improvement.
  • Enable organizations to gain "Best Practices" and implement them within the organization
  • Organizational change management assistance
  • Coaching the Managers of the organization of all levels
  • Technology implementation
  • Strategy development
  • Operational improvement services

Projects allow enteprises to enable and  perfom their ongoing transfomation to adapt  themselves to their changing environment.

CCG experts support enterprises in the following:

 Project owner support

  • for scoping, planning, defining technical constraints, and monitor the project execution

Project Management

  • to ensure successful project execution by managing time, resources, budget, and quality. CCG experts apply proven and innovative managerial technics to address the ma,ny challenging conflicts and issues of complex projects.

Assistance to the project execution

  • to study, select and master the appropriate design options and solutions that will fulfil the owner requirement efficiently and cost effectively

Reviewing, evaluating and selected software products

  • Open publications
  • Software vendor internal usage or competition benchmark
  • Industrial company looking for project sourcing of technology roadmap

Helping software vendors to orient their developments by sharing ideas and long term vision based on ongoing technology awareness and highly structured manufacturing architecture framework

Assessing products, applications and people compliance to the standards such as B2MML, ISA88, ISA95, ISA84/IEC61508/61511...

Helping software editors to identify possible acquisitions or partnerships and to explore the technical aspects of a prospective deal.

User Requirement Collection:

  • Conduct interview with key users
  • Collect and align user requirements on manufacturing architecture
  • Standardize and translate user requirements into functionnal specifications
  • Ensure the independance between functional requirement / definition and technology
  • Develop user autonomy in submitting and updating their requirements and the corresponding specifications

Functional specification adds information support to the production system based on consistent industrial architecture.

Standards & practices

Six Sigma is a business management strategy, originally developed by Motorola, that today enjoys wide-spread application in many sectors of industry.

Six Sigma seeks to identify and remove the causes of defects and errors in manufacturing and business processes.

It uses a set of quality management methods, including statistical methods, and creates a special infrastructure of people within the organization ("Black Belts" etc.) who are experts in these methods. Each Six Sigma project carried out within an organization follows a defined sequence of steps and has quantified financial targets (cost reduction or profit increase).

ISA84 Scope
1. To define terminology that is peculiar to E/E/PES and high reliability.

2. Establish criteria for and means of assessing reliability and availability in practical applications.

3. Provide general specification guidelines that facilitate understanding.

4. Provide guidelines for process safety applications requiring high reliability.

5. Develop guidelines for specific hardware/software configurations that can meet varying levels of reliability/availability.

6. This work does not apply to nuclear power safety-related systems.
 

ISA88 Purpose

To provide standards and recommend practices as appropriate for the design and specification of batch control systems as used in the process control industries.

ISA95 Scope

  • Multi-part effort
  • Define in detail an abstract model of the enterprise, including manufacturing control functions and business functions, and its information exchange.
  • Establish common terminology for the description and understanding of enterprise, including manufacturing control functions and business process functions, and its information exchange.
  • Define electronic information exchange between the manufacturing control functions and other enterprise functions including data models and exchange definitions.

ISA99 Purpose

The ISA99 Committee will establish standards, recommended practices, technical reports, and related information that will define procedures for implementing electronically secure manufacturing and control systems and security practices and assessing electronic security performance.    Guidance is directed towards those responsible for designing, implementing, or managing manufacturing and control systems and shall also apply to users, system integrators, security practitioners, and control systems manufacturers and vendors. 

The Committee s focus is to improve the confidentiality, integrity, and availability of components or systems used for manufacturing or control and provide criteria for procuring and implementing secure control systems.  Compliance with the Committee s guidance will improve manufacturing and control system electronic security, and will help identify vulnerabilities and address them, thereby reducing the risk of compromising confidential information or causing Manufacturing Control Systems degradation or failure.

B2MML is an XML implementation of the ANSI/ISA 95 family of standards (ISA95), known internationally as IEC/ISO 62264. B2MML consists of a set of XML schemas written using the World Wide Web Consortium's XML Schema language (XSD) that implement the data models in the ISA95 standard.

 

Business Process Modeling Notation (BPMN) is a graphical representation for specifying business processes in a workflow. BPMN was developed by Business Process Management Initiative (BPMI), and is currently maintained by the Object Management Group since the two organizations merged in 2005.
The Business Process Modeling Notation (BPMN) specification provides a graphical notation for specifying business processes in a Business Process Diagram (BPD). The objective of BPMN is to support business process management for both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics. The BPMN specification also provides a mapping between the graphics of the notation to the underlying constructs of execution languages, particularly BPEL4WS.

The primary goal of BPMN is to provide a standard notation that is readily understandable by all business stakeholders. These business stakeholders include the business analysts who create and refine the processes, the technical developers responsible for implementing the processes, and the business managers who monitor and manage the processes. Consequently, BPMN is intended to serve as common language to bridge the communication gap that frequently occurs between business process design and implementation.

Currently there are several competing standards for business process modeling languages used by modeling tools and processes. Widespread adoption of the BPMN will help unify the expression of basic business process concepts (e.g., public and private processes, choreographies), as well as advanced process concepts (e.g., exception handling, transaction compensation).

(Wikipedia)

CCS

The Application of the Theory of Constraints for Project Management

CEA

The Coherent EA is a change oriented Enterprise Architecture approach base on the concept of continuous change. It taking the time dimension into consideration and suggest that an enterprise is changing continuously. The change oriented EA model is initiated to clarify major myth in the EA community as has evolved to emphasize on reference model and service oriented architecture to enable simplicity and agility, Segment Architecture to close the gap of business performance to address business change base empirical need. EA has not evolved as expected because there is a great confusion on What is EA, what is reference model, the role of service oriented architecture and the purpose of segment architecture due lack of a update EA model to keep up with the EA evolution. The community try to understand EA from the traditional application development oriented EA approach. CEA suggest a change oriented enterprise architecture approach which break the myth of target enterprise architecture and clearly explain what is reference model, the role of service oriented architecture and the purpose of segment architecture.

CIMOSA (Computer Integrated Manufacturing Open System Architecture) represents one of the most popular enterprise modeling architectures.
The aim of CIMOSA is to elaborate an open system architecture for CIM and to define concepts and rules to facilitate the building of future CIM systems. It was developed by the AMICE Consortium, in an EU project

Capability Maturity Model Integration (CMMI) is a process improvement approach that provides organizations with the essential elements of effective processes.[1] CMMI best practices are published in documents called models, which each address a different area of interest. There are now two areas of interest covered by CMMI models: Development and Acquisition.

From Wikipedia, the free encyclopedia

The Control Objectives for Information and related Technology (COBIT) is a set of best practices (framework) for information technology (IT) management created by the Information Systems Audit and Control Association (ISACA), and the IT Governance Institute (ITGI) in 1992. COBIT provides managers, auditors, and IT users with a set of generally accepted measures, indicators, processes and best practices to assist them in maximizing the benefits derived through the use of information technology and developing appropriate IT governance and control in a company.

 

Cynefin is used to designate a naturalising sense-making framework, developed by David Snowden and his collaborators. The Cynefin framework draws on research into complex adaptive systems theory, cognitive science, Anthropology and narrative patterns, as well as evolutionary psychology. It "explores the relationship between man, experience and context"[1] and proposes new approaches to communication, decision-making, policy-making and knowledge management in complex social environments.
(from Wikipedia)

DAV

Direct Value Added
Enterprise and Companies are different entities by their nature, roles and performance objectives.
Taking into account these differences reveals that the survival and the development of the enterprise is much better secured - the usually conflicting interests of shareholders and employees are better satisfied:
- The enterprise is no longer committed to generating profit, but to adding value, which feed wages and profit.
This fact lead to adopt specific KPIs and new decision processes and tools for driving the enterprise
...
Sales DAV = Turnover - Direct consomption

DBR

Scheduling Methodology based on the Theory of Constraints

CCG posts

Starting a New Business - the Systems Thinking Way

I am starting a new business. I am not giving up my work as a business advisor, but I do need a change of pace. Ten years of working to improve other people's businesses have taken a toll.

You might think "a change of pace" means I want to slow down. On the contrary, I want to speed up. The very, very slow, cumbersome, and obsolete systems and processes at most companies are very difficult to adapt to.

I need to do something challenging, and I need a test bed for ideas. I also happen to love photography, especially trick photography, so, I am setting up a photography business.

I am of course applying Maneuver Conflict and Systems Thinking ideas to the new business.

Here are some of the things I am doing differently from other photographers:

To succeed in business, you need to try a bit harder, and do things other people can't or won't do.
Finding a unique segment: Most photographers focus on weddings, portraiture or advertising. I focus on trick photography. It means I do something no other professional photographer in gothenburg does.
  • Lots of photographers shoot weddings. I am the only one that make the bride and groom fly, levitate, or be quite literally joined together. (You can do some amazing flesh manipulation techniques these days...)
  • Lots of photographers shoot children. I am the only one that can shrink a whole class of school children and put them in a lunch box.
  • Lots of photographers shoot products. I can make the products levitate, sparkle, etc., without an advertising agency.
  • Lots of photographers shoot portraits. Almost everyone does it using soft light and clamshell setups. I do that too, but I also offer soft light setups, hard light setups, night setups (in broad daylight)... and I can turn you into a zombie or cat creature.

Delivery: Most photographers deliver files on DVD, and framed prints. I deliver the files on USB sticks, because newer computers often do not have DVD players. I do deliver framed prints, but I also print on t-shirts, mugs, phone and tablet shells, and hundreds of other things. 

I bet people want to see, and show off, their pictures all the time, when they walk along a street, drink a cup of coffee, or pick up their phones.
My clients can order through a web form, and they can customize items themselves if they like, for example by adding or changing text, changing colors of items, and so on. I have set up a small public store to showcase 
what I can do.
Hadouken is a Japanese photo craze where you imitate Manga style fights, complete with Ki based energy attacks. Probably not what you would choose for a corporate group portrait. Then again, it might be...
Events and courses: I have started organizing photo events. The first one is a Hadouken photo event, on Saturday, 4 May. More will follow. If a special event is successful, elements from that event will be included in photography courses.
In short, I am constantly, and very consciously, looking for things I can do that will delight customers.
    Will I succeed? I will if what I do is interesting enough: Interesting to customers, and interesting enough so that people will want to spread the word.
    Here are links to my photography web site, and my photography blog.
    Check them out. You might like them! :-)

    Workshops: Values to Vision and Strategic Principles

    I am announcing four workshops in Stockholm and Gothenburg.

    Each workshop is limited to twelve people, and the first workshop is in just five weeks, so if you are interested in gaining an advantage over your competition, sign up now:

    Stockholm:

    Gothenburg:
    Why should you care about having a clear vision?
    A vision is a guiding light:
    The vision helps you establish a connection with your customers, it attracts the right people to your company, it sets a course to follow when developing strategy and tactics.
    And yet, most companies have vision statements that are bland, uninspiring, and to be frank, not very useful.
    In the workshop you will learn how to build a vision guided by your own values. You will learn how to use your values and your vision to shape your mission. And, you will learn how to create a Goal Map, a simple picture that explains your vision, and the intermediate goals necessary to achieve it.
    A Goal Map is a great tool for explaining your vision, and setting a course for your organization. More than that, you can use it to define the behaviors necessary for success.
    Why should you care about strategic principles?
    Strategy is about setting goals, and achieving them. There is a simple set of principles that are common to all kinds of strategy: In business, war, love, games.
    Unfortunately, a strategy developed without understanding the principles, will often cause more harm than good. Quite often, even large companies, confuse strategy and tactics. The result is often a gigantic  Powerpoint stack, full of lofty statements and wishful thinking, but of little practical use.
    The business strategy workshop will clearly define what strategy is, and give you:
    • A simple tool you can use to develop good strategies, and find the flaws in bad ones
    • Six strategic principles common to all strategy development
    • Cheng/Ch'i, a Chinese principle for developing strategies for business, war, and love

    And there is more of course. Check the links above for more information.

    The Reality Dysfunction Draws Closer

    The Reality Dysfunction is approaching. The picture above is the theme picture for my presentation at Lean Kanban Nordic on the 12th of Mars. I'm going for the jugular with this one...

    You can read more about the presentation itself here.

    Reality Dysfunction preview at Scrumbeers
    The audience was great - Knowledgeable, asked a lot of questions, and there was a very interesting discussion afterwards.

    I did a trial run for of Reality Dysfunction presentation at Scrumbeers yesterday. The presentation was very well received, though it was much too long. You can read the audience comments and reactions here.

    The Scrumbeers gatherings are always fun. This time, it was also very, very useful. The feedback I got will enable me to make the final presentation even more fun, and shorter. Lots shorter. My presentations tend to be about as long as a Hollywood movie. I need to cut this one down to 35 minutes or less before I present at the Lean Kanban Nordic conference on the 12th of Mars.

    I'd like to thank the audience not just for being very interested, kind, and fun to spend time with, but also for giving me lots of useful feedback.

    I am looking forward to the next Scrumbeer.

    The Reality Dysfunction - Presentation at Stop Starting, Start Finishing

    The nice people running the Stop Starting, Start Finishing conference in Stockholm the 12-13 of Mars 2013 asked me if I was interested in holding a presentation.

    Of course I am.

    I am hard at work on my presentation. Here is what I am going to talk about:

    Tempo!: The Reality Dysfunction
    Henrik Mårtensson


    Henrik Mårtensson
    How did we end up with so many dysfunctional companies? To fix the problems we face today, we must understand the causes. Tempo!: The Reality Dysfunction is a romp through the wild side of management history: It starts with a bang, a train crash the 5th of October 1841, with consequences that cause companies to fail in 2013.
    You will meet the unbeatable fighter pilot, who also figured out how to build an unbeatable organization. You will see what managers must know to lead an Agile development team. You will see how most companies are applying fundamental principles of strategy, psychology, and physics backwards, and hurt and disable themselves in the process. You will also find out what to do about it, and who has already succeeded.
    There will be a practical demonstration, with members of the audience, showing how a simple restructuring of work can reduce lead times by 60 percent or more, while increasing quality. And, you will have fun!
    Henrik Mårtensson is a business strategy coach, process developer, and project leader. He is also an author and presenter. Henrik began working with Extreme Programming, an agile software development method, in 2001. His interest in methodology quickly brought him to Lean, Theory Of Constraints, Statistical Process Control and Systems Thinking. Several years ago, Henrik got into contact with Strategic Navigation and a military strategic framework, Maneuver Conflict. Suddenly, all the pieces fit together.
    Tempo!, Henrik's first book on business strategy, was published in 2010. His second book, LESS!, published in 2012, is a collaboration between twelve thought leaders in Agile, Lean, Beyond Budgeting, Strategic Navigation, Systems Thinking, and Complexity Science. 

    Logical Thinking Process course by Bill Dettmer in Finland

    Bill Dettmer will hold a course in The Logical Thinking Process in Finland on the 3-5 of April, and the 8-10 of April. Here is a link.

    Bill is a well known management and leadership expert. He has written several very good books. I heartily recommend his book The Logical Thinking Process.

    Though I have never met Bill, we have corresponded via email. When I wrote my first book, Tempo!, Bill was very helpful and encouraging.

    In case you are wondering:

    The Logical Thinking Process is a method for solving problems. You can use it in business, or your private life. TLTP is great for facilitating communication and understanding. It beats long boring Word documents or bullet riddled Powerpoint presentations hands down.

    I often use it to visualize problems, to help my customers generate solutions, and to communicate and test solutions before implementing them. The tools are simple to use and very effective.

    Facebook vs. Google+ Communities - Is it talkers vs. doers?
    If you have a special interest, you may see a lot more action in a Google+ Community than on Facebook. After two days in Google's The Photo Community, my photos had garnered more interest than I have been able to build after years on Facebook.

    Google may have hit it off big with its newest product: Google+ Communities.

    Two days ago I joined The Photo Community at Google+. The community was created by Trey Ratcliff, a very well known HDR photographer. After two days in The Photo Community, I have gotten into contact with more photographers than I have during the past two years on Facebook. The reason for the different results: The design of the new Google+ Communities.

    I am an amateur photographer, and I have spent a couple of years building a photo library at Facebook. some time ago, I started doing the same thing at Google+, but initially it was a bit disappointing. I found other photographers, added them to my own photography circle, and posted photos, but there was little response. The design of Google+ made it easy to find people with shared interests, but it also made it difficult to get noticed.

    This changed in a big way two days ago. Google Communities aim to make it very easy to discover people with shared interests. Interested in photography? The Photo Community is very easy to find. (Though I admit, ironically, I found it on Facebook, because Trey Ratcliff posted an invitation.)

    A community can be divided into sub-communities. For example, I posted the Scaly Leaves photo in the Anything Goes subgroup, but the sunken boat in the Black & White Photos subgroup.

    Different social media sites have different characteristics:

    Twitter makes it extremely easy to connect with people who have similar interests, but you also need to use filters to get rid of lots of useless noise. You can't do much on Twitter, except post brief messages and links to interesting stuff.

    LinkedIn is great for building a network of business contacts, but sadly, doing things together with those contacts is very difficult. I know from experience, because The LESS Author Group used LinkedIn as the main network hub while writing LESS!. I set up a LESS! forum on LinkedIn because I knew everyone in the group had accounts there. Unfortunately, LinkedIn lacks the tools you need to do things: You can't upload files to other group members, you can't post pictures or other media, no face-to-face communication...

    Facebook is of course the largest community, but the noise to signal ratio is incredibly bad. You get advertised to death, people you barely know insist on telling you what they had for lunch (often with photos), you get invitations that are aimed at tricking you into opening up your contact data, and it is well difficult to find anyone who wants to do anything but smother you with their interests, or sell you something. The smothering, by the way, is not due to people on Facebook being especially boring. It is inherent in the design of Facebook. Facebook has affordances encouraging people to post everything in a general stream, even if there are special interest groups.

    The big thing about Google+ Communities is that the affordances drive people in the other direction: It is more attractive to post in a community than to post in a general stream. The effect of that shows in the  diagram at the top of this article.

    I strongly suspect that Google+ communities will turn out to bring something else into the game: The combination of communities, media upload, and video conferencing, makes Google+ communities very attractive for doers:

    If you want to start a company, make a movie, become a better surfer, produce an interactive eBook, become a top notch photographer or writer, start a rock band, or coordinate a political campaign, you can find people and coordinate activities using Google+ Communities much easier than you can using other social media web sites. It does not mean the other sites are useless, far from it, but a Google+ Community is likely to be the major activity hub.

    The Reality Dysfunction

    I was asked to submit a presentation proposal to Stop Starting, Start Finishing, the Lean Kanban Nordic conference, 12-13 Mars, 2013, so I did:

    If the proposal gets enough votes, I'll get to hold the presentation.

    Here is the proposal:

    Tempo!: The reality Dysfunction puts the fun back in dysFUNctional. 

    How did we end up with so many dysfunctional companies? To fix the problems we face today, we must understand the causes. 

    Tempo!: The Reality Dysfunction is a romp through the wild side of management history: It starts with a bang, a train crash the 5th of October 1841, with consequences that cause companies to fail in 2013. 

    You will meet the unbeatable fighter pilot, who also figured out how to build an unbeatable organization. You will see what managers must know to lead an Agile development team. 

    You will see how most companies are applying fundamental principles of strategy, psychology, and physics backwards, and hurt and disable themselves in the process. You will also find out what to do about it, and who has already succeeded. 

    There will be a practical demonstration, with members of the audience, showing how a simple restructuring of work can reduce lead times by 60% or more, while increasing quality. 

    And, you will have fun!

    Serious enough to get your vote? You should of course check out the other proposals before you vote, so you can pick the ones you are most interested in. (You get 10 votes, and you can put up to 3 votes on any one proposal.)
    2012 - ISA Doha - ISA95-B2MML use cases.ppt
    2012 - ISA Doha - ISA95-B2MML use cases.ppt
    LESS! is available on Amazon

    LESS!: Essays on Business Transformation is now available on Amazon Kindle.

    The hardcover version of LESS! is available from Lulu and quite expensive ($46.53). The Kindle and ePub versions are just $6.89. We do not use DRM protection, so when you buy the book, it is yours. You can put it on any device you want, and on as many devices you want. Please keep the copies in your family though.

    I am very proud of LESS!. I am particularly proud of the fact that I did not write most of it. LESS! is a collaborative work, and working with the other authors has been a privilege I cannot adequately describe. One of my best adventures ever.

    LESS! is about building better places to work:

    Have you ever had a great idea crushed by the words, "we can't do that, because it's not in the budget"? Then you really need to read up on Beyond Budgeting. Bjarte Bogsnes, VP of Performance Management at Statoil and Dr. Peter Bunce, Director of the Beyond Budgeting Round Table, have written two chapters helping you free yourself from the chains of budgeting.

    If you look around you at work, and see people with great potential, but somehow things never get together like they should. The sum of the work is always less than the sum of what the individuals can do. Then Making the Entire Organization Agile, the chapter by Steve Denning is for you. Steve is a former director of the World Bank. He is a deep thinker with unsurpassed practical experience. In November 2000 he was selected as one of the world's ten Most Admired Knowledge Leaders (Teleos).

    If you want to do Lean or Agile, what is you and your organization's position on Theory X and Theory Y? Why do you need to know about them? Because Agile and Lean are Theory Y based, and your organization is most likely Theory X based. X and Y ideas don't mix well. Not understanding the difference is a major cause of failure when implementing Lean or Agile. Dan Bergh Johnson's chapter Agile and Lean do not fit into Taylor's Glove will get you up to speed on the all important fundamentals.

    And that is just for starters. There is lots more, by authors like James Sutton, Karl Scotland, Håkan Forss, Ola Ellnestam, Brian Hawkes, Maarit Laanti, Ari-Pekka Skarp, and me. And you might want to check out the Foreword by John Hagel III. John is a great author in his own right, Director at Deloitte LLP, and co-chairman of the Deloitte Center for the Edge.

    I promised the Mexican photographer Herminia Dosal I would write an article about the story behind a picture she shot of me. At the time I made the promise, I did not realize how awkward I would feel putting myself on the cover of my own eMagazine, even though I love the photo. In the future, I will try to get Herminia's permission to publish some of her other work. Believe me, most of her models are far better looking than I am.

    By the way, if you read the Introduction, you will find a link to the LESS! resource page. That is where we put links to free material you might be interested in, such as the Tempo! newsletter. The issue you see above is in review at the iBookstore right now, but you will find four older issues on the resource page.

    If you do buy LESS!, please do write a review at Amazon, Lulu, or Goodreads. Honest reviews help me figure out how to make the next book even better.

    Why Cities Live and Companies Die
    When cities grow larger, productivity per person increases. When companies grow larger, productivity per person decreases. Cities can last thousands of years and survive plagues and nuclear blasts. Large companies have an average lifespan of fifteen years, and the lifespan is dropping.
    It is blindingly obvious, except almost nobody noticed until a couple of years ago: Companies have short lifespans. Cities live thousands of years; Cities can survive plagues and nuclear bombs. Companies croak when there is a slight downturn in the economy.; People want to live in large cities, but they want to work in small companies.
    Why? What is the difference, and does it matter? If we understand why cities are so resilient, can we use that knowledge to build better companies? Companies that are more resilient and better places to work?
    It turns out we can. Physicist Geoffrey West has studied cities and found a very simple mathematical relationship between city size and productivity: When a city doubles in size, each person in the city becomes about 15-20% more productive.

    The productivity increase in cities is in stark contrast to what happens in companies. According to an article in the CYBAEA Journal, when a company grows, productivity per employee drops.

    For comparison, I have plotted the power rules governing city and company productivity:

    When cities grow larger, productivity per person increases by about 15% each time the city population doubles. In a company, productivity per person drops when the company grows. The fundamental difference: Cities are networks, most companies are hierarchies. 

    What this graph shows is that a city is much better organized than the average company. But why?

    Cities are networks. They are to a large extent self-organizing. Nobody tells you where to live, where to shop, which friends to spend time with, or where to work, or whom to vote for. You figure all that out for yourself, based on the knowledge you have about the city.

    Companies are very different: You are told where to sit, what to work on, whom to work with, when to take a break, and who your boss is. You have comparatively little latitude to exercise your own judgement.

    What companies are missing is the power of self-organization. Here is another way to look at it:

    Donella Meadows's System Intervention Scale

    Company leaders usually focus on the low end of the Meadows scale: They set targets like "increase sales by 20%", or "reduce costs by 10%". They make budgets and set project deadlines, which is saying they allocate money and time buffers. Sometimes they make a reorganization, which means they mostly mess around with stock and flow structures.

    Cities leave most of that to its inhabitants. City planners are concerned with overall system structure, but they mostly let people make their own decisions, and that is what makes cities resilient, productive, and powerful.

    Value streams in functional hierarchies vs. value streams in networks. From my book Tempo!.

    Why are companies so much more vulnerable to damage than cities? There are several reasons, but most have to do with the way companies split in order to manage growth. Companies divide into functional departments. This causes problems when information or physical material is moved from one department to another. Hand-offs are difficult to manage, and you can have many value streams that interfere with each other. this problem becomes worse the more cost effective an organization is, because increasing cost effectiveness means reducing the capability to absorb variation in the value streams.

    Add to that, that if a single node in a functional organization is damaged in some way, it may affect all value streams running through that organization.

    For example, if the IT department suffers from work overload, you can't do anything but wait until they get to your request. I have worked at companies with waiting times of 9-18 months for simple requests like setting up a server.

    On the other hand, in a city, if you can't get the service you want when you want it, you go someplace else. If the grocery shop closest to where I live closes, I won't starve. I just shop my food somewhere else.

    The amazing thing is that we do have plenty of blueprints for building companies that are as resilient as cities, but with rare exceptions, we don't. There are signs that things are looking up though. We may have a phase shift, a rapid transition from the old hierarchies to network based organizations pretty soon.

    Sustainable Leadership seminar by The Hunger Project
     Julia Norinder, CEO of Preera, and the main speaker talked very passionately on the need for sustainable leadership.
    I've just been to a seminar on sustainable leadership. The seminar was arranged by The Hunger Project (The Swedish web site is here) and hosted by Ernst & Young.

    I am glad I went: Two good speakers, a great workshop, and an interesting panel discussion.
    The Hunger Project is a global organization fighting poverty by investing in human potential. In practice, The Hunger Project helps people in developing companies by means such as micro-loans and education.

    Sara Wettergren, CEO of the Hunger Project was the first speaker. She talked about the Hunger Project and how the organization works to eradicate poverty in the world.
    When Sara talked about how the organization has to change the mindsets of the people they want to help from "I am alone, there is nothing I can do" to "I am part of something larger. I can make a difference", it struck me that the problems she described, feelings of helplessness, isolation, is exactly the same problems I see in many business organizations.
    Helping others is a great way to help oneself. I bet that many companies around the world can learn a lot from The Hunger Project.
    Julia Norinder, CEO at Preera made a passionate presentation about the need for leadership adjusted to the world we live in. Julia advocates looking at organizations as living organisms, not machines. This is of course an argument that resonates with me. Organizations are made of people. People are living organisms, not machine parts.
    Moving from a machine view to an organic view means moving from control, instructions, and hierarchies to vision, values, understanding and dialog. This is not yet the mainstream view, but it is a view that is steadily gaining traction. (If you have read LESS!, you may recall that my co-author James Sutton wrote about organizations as organic entities.)

     Anastasia Nekrasova from Intelligent Mindsets ran an interesting workshop based on a real case:

    Josefine Lassbo, CEO of Reflective Circle, wanted help developing a vision and a growth strategy for her company. Turning to an outside group to get many different perspectives on what the business should be is a smart thing to do. Ultimately, it is of course up to Josefine to define why she is in business, but input helps. Developing a good vision statement is difficult.

     Getting multiple perspectives can speed up the process considerably.
    The audience was split into groups to discuss the vision and the strategy.

    It is worth noticing that much of the value from an exercise like this is due to most of the participants not being experts. We business strategists tend to think in similar patterns due to our sharing of a common body of knowledge. Put a more diverse group together, and you are much more likely to come up with a unique and valuable insight.

    My discussion group at the workshop, except...
    ...Carina Jonsson, who made our groups presentation after we were finished.

     The seminar finished off with a panel discussion about sustainable leadership.

    The panel: Caroline Trowald (Conferencier); Kristina Cohn Linde, CEO of Mig; Eva Hyllstam, Leadership Trainer; Liselott M Daun, Senior Consultant at Ernst & Young; Gustaf Josefsson, Innovation strategist

    The panel discussion was interesting and the panel members had a wide range of opinions about leadership and organization.

    I believe events like this are important: They are a sign that there is progress. Though management science has progressed enormously the past sixty years, we actually see very little of it in the way companies are organized and lead. Change is much overdue, and I am glad to see signs of it.

    Major change tends to happen like when you try to get ketchup out of a glass bottle: First you get nothing, then you get nothing, then you get everything at once. Scientists call this phase transition, but I'll save that for another blog post.

    Is Facebook corrupting us?

    When we discuss corruption, and we do, at least in the media, the focus is nearly always on some spectacularly greedy, dishonest, and stupid act. I believe it is a good thing that this kind of corruption is exposed, but there is another, more subtle kind that worries me.

    First, let's define the word "corruption":

    In philosophical, theological, or moral discussions, corruption is spiritual or moral impurity or deviation from an ideal.

    – Corruption, Wikipedia article 

    For example, in a contest, we are expected to abide by the rules of that contest. If the judge in a football match judges in favor of the team he likes the most, because he likes it, then the judge is corrupt.

    On the other hand, in a popularity contest, voting for the person you like the most is not corrupt. It is the expected behavior.

    We have always had a problem with very complex contests, like political elections. Most people do not like to grapple with complex issues, so they substitute something simpler, like:

    • Which politician do I like the most?
    • How do my friends vote?
    • Which policy do I like the most? (Without regard to the total effect of all the policies suggested by the party.)
    Politicians aren't exactly helping. They make a lot of speeches, but I haven't yet seen a politician use a Causal Loop, Stocks & Flow, or TLTP diagram, or anything similar. Instead, they rely on long-winded speeches, and documents so obtuse they obfuscate the issues rather than clarifying them.
    Of course, politicians are like most other people, they choose their position first, then look for arguments to support their point-of-view. This is much easier than actually figuring things out, experimenting, testing, working with scientists...
    There are of course exceptions to the rule among politicians, just as there are among other people. (I have actually met politicians which I judge to have integrity, honesty, a very high degree of intelligence, and who understand the issues they work on very well. It is just that they are a minority, regardless of which party they are from.)
    Robert Cialdini, a professor of Psychology and Marketing has constructed a highly useful model for how and when people substitute a simple problem when they are faced with a difficult one. The Cialdini decision model looks like this:
    The Wikipedia article on Cialdini contains more detailed information. 
    Right before writing this part of the post, I was in a discussion about the US presidential election. There was a newspaper with pictures of Obama and Romney on the front page.
    My interest was in the techniques Obama and Romney use to project a certain image. For example, both Romney and Obama had their shirt sleeves rolled up to indicate they are prepared to work hard. Romney had a a tie, indicating he is at home in board rooms. Obama had no tie and the top button of the shirt unbuttoned to indicate he has a strong working class connection.
    My discussion partner focused on the faces: "Obama looks a lot nicer than Romney." I also noticed she spent a lot more time looking at Obama's face than at Romney's.
    This is a very good example of the Cialdini rules kicking in. Instead of discussing the policies the candidates want to implement, a quite complex issue, we substitute things our brains are good at, like decoding facial expressions.
    This is not necessarily a bad thing. If you need to make a snap judgement, even a very brief look at a face can give you valuable information. However, when it comes to judging a complex issue, using a mechanism designed for snap judgements can easily lead to making the wrong decisions.
    BTW, she was right. Obama looked a lot friendlier than Romney. Then again, that impression could easily be reversed simply by comparing different photos.
    So, where does Facebook enter the picture? We'll, a lot of contests are run on Facebook. Since I am interested in photography, I get messages about photo contests. Of course, when my Facebook friends enter a contest of some sort, they post a message about it.
    What disturbs me is that with very few exceptions, the people who enter such contests send a message encouraging others to vote for themselves, not to look at the contest and vote for the best submission.
    This is, by definition, corruption. For example, in a photo contest, the idea is that the best photo should win. What actually happens is that the contest turns into a popularity contest. People are admonished to look only at a single photo, and then vote.
    A Facebook contest may be a trivial thing, but it teaches people to cast their vote for an alternative without even looking at the other alternatives. This bothers me.
    We need in a complex world, where the things we do can have very large consequences. To survive and thrive in such a world, we need more brainpower, not less. We need more decisions to be carefully thought through, not more snap judgements.
    We can't pay full attention to everything. For example, if I intend to vote in a photo contest with 10,000 submissions, I won't have time to compare all of them with each other. However, I can look at some of them, and pick the photo I think is best.
    Above all, I can be mindful of my own behavior, so that I can consciously choose when to think a choice through, and when to cruise on autopilot. This is something most people can learn, and I believe social media sites could be designed to encourage that kind of self-awareness.
    Imagine how the world would change if Facebook was designed to encourage people who use it to think, and to think about when they need to think. Maybe that would help us build a better future.
    Perspectives - To buy or not to buy a book?

    I am working on a new book, the working title is Perspectives. The purpose of the book is to show how the lofty ideas about management and leadership applies to everyday management decisions. I want to show how having more than one perspective can have a great impact on every day decision making.

    The following essay is an early sketch that may become a chapter in the book. I will publish more preview chapters in the newsletter supporting LESS!, the book I co-wrote with eleven other management experts not too long ago. By the way, the ePub version of LESS! is free, if you promise to write and publish an honest review.

    Here is the preview chapter for Perspectives:

    To buy or not to buy a book?
    Imagine you are running an IT department employing fifteen people. Anna, a young software developer asks you if the company will pay for a book she wants to read. The book is about XML Forms. You have no idea what XML Forms are. The book costs $17. Should you let her buy it?

    This is one of the countless every day decisions a manager has to deal with. You obviously can’t do a detailed Cost/Benefit analysis every time a decision like this is called for. Instead, you make a quick decision based on your gut feeling. However, depending on your perspective, your gut feeling will be very different. Let’s have a look at the implicit reasoning behind your gut feeling. We will use the following perspectives:
    • Cost Accounting
    • Theory X
    • Theory Y
    • Options thinking
    • Queueing Theory
    • Strategy
    Cost Accounting perspective
    The answer, straight from the gut, is no, no book!
    The reasons are simple and obvious: Spending money on a book incurs a cost, but there is no clear benefit for the company. No customer has asked for XML Forms. Anna does not currently work in a project where XML Forms would be needed. Even if she did work in such a project, it would probably be cheaper to use currently available technology instead of spending time and effort learning something new.
    Theory X perspective
    The quick answer is no, no book!
    Anna is not trusted to make a $17 decision, but you are. The reason is that you, as a manager, have a much better grasp of the big picture than Anna. If you cannot see how the book would benefit the company, then it probably won’t.
    Another reason is that the expenditure of buying the book would go on record. If you give Anna permission to buy the book, your own manager might hold you responsible for incurring a needless expense. If you deny Anna’s request, the matter ends right there. There will be no record of the request being denied, because no transaction has taken place. Thus you will not be held responsible for any opportunities that might be lost by Anna not reading the book. As we have already concluded, the probability of such an opportunity occurring is very low anyway.
    Options thinking perspective
    The gut answer is yes, Anna can buy the book!
    If Anna reads the book, the company will gain the ability to use more options in certain situations. Are those options likely to be worth more than $17? The average value of the options is:
    Probability of using the options x Value of options used - Cost of buying the options
    The cost of buying the options is $17. You have no clue what the other variables are for this particular book, but you can make an educated guess if you pose the question this way:
    If employees in your unit read 100 work related books, can they, and you, leverage the knowledge gained to make more than $1,700 for the company?
    If you are in a business where technology changes rapidly and customer requirements are varied, the answer will almost certainly be yes.
    Theory Y perspective
    Anna bought the book on her own initiative, without asking you.
    Anna is an intelligent, responsible adult. She works on software worth millions of dollars. Every day, a decision made by her can make a difference of many thousands of dollars on the bottom line of your company. That is part of the nature of knowledge work. Obviously, she can make a $17 decision on her own.
    If Anna had asked you before buying the book, that would have been a sign that you must help her gain confidence and rely more on her own ability to make decisions.
    Queueing Theory perspective
    Anna can buy the book on her own initiative, without asking.
    Let’s assume that Anna costs $100 per hour, or $1.67 per minute. You cost $130 per hour, or $2.17 per minute. If Anna makes the decision herself, she can make it in less than a minute. The cost of the decision is about $1.67. If Anna has to ask you, you will spend at least five minutes each. Anna has to explain the reason for her request before you can make a decision. Those 5 minutes will cost $19.2 (5x1.67+5x2.17).  The decision will cost $17.53 more (19.2-1.67) if you make the decision than if Anna does it. That is $0.53 more than the cost of the book itself.
    Even if you always made the right book buying decision and Anna always made the wrong one, it would still be cheaper to let Anna make her own decision. Thus, the simple rule is that Anna can make such minor decisions for herself.
    Strategy perspective (Maneuver Conflict)
    As a commander in Vietnam, I wanted to unleash my marines on the enemy, not control them.
    Thinking Like Marines, by Col. Mike Wyly USMC (Ret.)
    Anna bought the book on her own initiative, read it and liked it. She wrote a review for goodreads.com, made a video review for amazon.comamazon.co.uk, and your company’s book review channel on Youtube.com. She also made an entry about XML Forms in the company’s wiki based online encyclopedia. She added links to the PDF article, and updated the PDF article with a link to the XML Forms article. (As it turned out, the PDF 1.5 specification references the XML Forms specification, and your company has an interest in PDF technology.)
    Finally, Anna used the book as source material for the monthly Pecha Kucha[1] night at your company. When Anna was done with the book, she put it in the bookshelf in the company cafeteria. You saw the links to the reviews on the company Twitter list, which aggregates tweets from every tweeter in the company.
    You like Anna’s energy and initiative. Based on her presentation at Pecha Kucha night, you might give the book a quick read, just so you know what the developers are talking about when you have lunch with them. You make a note to ask Anna to show you how XML Forms can be integrated in the tactics of your unit.
    In this version, Anna did what you trained her to do: She took the initiative and made the most of the opportunity that presented itself. By reading the book she increased her own competence and created new options for your company and yourself. She then proceeded to spread an important message outside the company: “These people know their stuff! They are actively building their competence.” Note that every person who reads or watches one of her reviews, will also see your company name. Inside your company, Anna made sure that everyone who is interested in forms technology knows about the book, and also knows that she knows how to use XML forms.
    From a strategy perspective, Anna has strengthened interactions with potential allies outside your company, and also strengthened interactions between people inside the company. She has considerably reduced friction, in this case the startup cost of using a particular technology.
    Your role in this is as a leader and an enabler. You have trained Anna in IOHAI leadership[2]. You have participated in setting up the company Wiki, the book review channel on Youtube, and the accounts your unit has on Twitter and Goodreads. You are responsible for keeping your unit targeted on the overall Noble Vision of your company.
    In this version, your company is very likely to be organized as a network of small units, capable of independent action, responsible for their own value streams, but working to achieve a common goal, a Noble Vision. You are much more likely to be the leader of such a unit, than to be the manager of a functional department.
    Implications
    In 1995 I was co-owner of a small technical documentation company. One of my co-owners, who remains a close friend of mine, and I each bought a book about the Structured Generic Markup Language (SGML), Developing SGML DTDs: From Text to Model to Markup, by Eve Maler and Jeanne El Andaloussi. We quickly took to calling it “The Green Book”, because of the color of the cover. Buying The Green Book was the first step on our journey to become SGML experts. We did a lot more than just buying and reading a book of course: We bought and read many, many more SGML and XML books. We built SGML/XML document authoring systems just for the fun of it. I built a system for reading FrameMaker MIF documents and converting them to XML. I also built a system for managing XLinks in XML documents. XLink is a way of creating various types of links in XML documents.
    We adapted our company strategy to incorporate the things we were passionate about. As a result, we were in a perfect position when our largest customer decided to switch from using FrameMaker to using an SGML/XML based document authoring system in 1999. A couple of years later, the MIF to XML conversion system I built for practice became an integral part of a system for processing medical records. My friend integrated the XLink system I built into a commercially successfull XML document management system. Today, more than ten years later, not a single line of the original code remains, but the ideas about how to build a robust, user friendly XLink system live on.
    At least five different companies benefited from our original decision to buy and read The Green Book. The total profits accrued from that decision amounts to millions of dollars. I buy and read about twenty work related books a year. The cost is negligible compared to the total profits accrued from reading The Green Book. Even if my friend and I had never bought anything useful again, our reading habits would have paid off handsomely. Note that in monetary terms, other people benefited much more than we did. I think we got most of the fun and excitement though. However, had we not owned our own company, it is unlikely that any of this would have happened.
    The most common answer when an employee asks if their employer will spring for a book is “no!”. The employees learn quickly that knowledge is not valued in the organization. The people who are passionate about what they do will eventually leave, not because of the book buying decision, but because of the underlying mental models of the managers. Only the apathetic will remain, because apathy is the only alternative to going crazy.
    Without a steady flow of new knowledge, the company will be increasingly out of touch with the world around it. Customers and competitors will adopt new technologies faster than the company can. Strategy, tactics and organization will fall behind. When the customers leave, this is merely the result of a long process of erosion within the company.
    The problem is that the Cost Accounting and Theory X perspectives are so prevalent in our companies. Cost Accounting is based on the ideas of taylorism. Taylorism is based on Theory X premises about workers. If you work in a Theory X based hierarchical, functionally divided organization, and is evaluated on cost Accounting measures, you are unlikely to even know about other ways of thinking, and other ways of doing. Even the idea that there may be other ways is unlikely to occur. You, your co-workers, and your company, are trapped in a closed system.
    If you can break out of the closed loop, you will be able to see that there is great value in other ways of doing things. Reading a book might be the first step.
    Further thinking
    • How do the managers and leaders at your company value new knowledge and learning? What is the message they are sending to employees? If they do not actively support learning, what does that tell you? How often do you hear them speak about what they have learned themselves?
    • As a manager/leader, would you prefer the Theory X/Cost Accounting style of management, or the Theory Y/Maneuver Conflict style of leadership? If you prefer the Theory Y/Maneuver Conflict model, what are your fellow managers most likely to prefer? If most of you are likely to prefer the Theory Y/Maneuver Conflict style, what is stopping you from doing it? How can you remove or get around the obstacles?
    • The US Marine Corps has a reading list, providing a list of books that Marines must have read at each grade level. The list includes both fiction and science books, books about strategy, tactics, philosophy, and different cultures around the world. Higher ranking marines must read everything lower ranking marines read, plus the books graded at their own rank. What would a reading list for your company look like? If you find it difficult to put such a reading list together, why is that? If you find it easy, why?
    • Are there any other perspectives that might be important to a book buying decision? What are they? What insights do they add?

    • [1] Pecha Kucha is a presentation format where all presentations use 20 presentation slides. Each slide is hown exactly 20 seconds. Slide transitions are automatic. This forces presentations to be short and to the point. There is a Pecha Kucha organization that arranges Pecha Kucha presentation nights all over the world. See www.pecha-kucha.org.
      [2] IOHAI is a military leadership model. It is part of the Maneuver Conflict strategy framework. I have described IOHAI in more detail in my book Tempo!.

    2012-10 ISA106.docx
    2012-10 ISA106.docx
    Dave Snowden's Keynote at XP 2012, Part 2 of 2

    This is part two of Dave Snowden's keynote. Great stuff.

     Part 1 is here.

    Dave Snowden's Keynote at XP2012, Part 1 of 2

    Dave Snowden talks about complexity thinking and contrasts it with design thinking and systems thinking in his XP 2012 keynote.

    This is one keynote worth listening to. I was very fortunate to get it all on video.

    Part 2 is here.

    LESS! is released!

    Whew! After six months of hard work, LESS!: Essays on Business Transformation is released. I should write something brilliant about this, but I just feel tired and happy. I'll go play with my son instead. I have deserved it, and so has he.

    Just one thing: You may recall an earlier cover picture:

    You may notice that the cover has changed slightly compared to the earlier version:

    John Hagel III has written an excellent Foreword. Check him out. I am immensely proud that he wanted to do that for us. John is a great management writer. He is also Co-chairman of the Deloitte Center for the Edge, and Director Deloitte Consulting LLP. I am currently reading his latest book, The Power of Pull.

    Chances are you already do know about some of the LESS! authors, but I'll give you a list with links so you can have a look:

    Dan Bergh Johnsson - Technology evangelist and blogger

    Bjarte Bogsnes - Chairman of the Beyond Budgeting Roundtable Europe
    Peter Bunce - Co-Founder and Director of the Beyond Budgeting Roundtable

    Steve Denning - Consultant and former Director of the World Bank
    Ola Ellnestam - Co-founder of Agical. Organizer of the excellent Agical Geek Nights(!)
    Håkan Forss - Lean/Agile coach, creator of Visual WIP
    Brian Hawkes - Founder of Foresite SPA
    Maarit Laanti - Agile and Lean coach at Nokia
    Henrik Mårtensson - Happy and exhausted
    Karl Scotland - Advocate and pioneer of Kanban Software Development
    Ari-Pekka Skarp - Coach and organizational developer at Nokia

    James Sutton - 2007 Shingo prize winner, CEO of the Jubata Group, co-founder and president of the Lean Software and Systems Consortium

    We have a wide range of expertise spanning finance, management, Agile, Lean, strategy, systems thinking, and complexity theory.

    What can you, as a reader, do with it? You can start putting the pieces together. When laid out the way we have, it quickly becomes obvious that there are common themes, things we all need to do to make our companies work better. If we work together, we'll get better results. It is that simple.

    By the way, in his Foreword, John does speak very clearly about what happens if one does not change. The things we are writing about used to be nice to have competitive advantages. Now they are necessary for survival. On the up side, once you try, they are fun and exciting to do. :-)

    Now, I will go play with my son. Be seeing you!

    Agile Company Presentation at XP 2012

    It nearly did no happen because of my workload, but I will go to XP 2012. Here is a brief description of my presentation:

    Agile Company - Win by doing LESS!
    Over the past 50 years there have been many attempts to change how business organizations work: BPR, Deming's System of Profound Knowledge, McGregor's Human Enterprise, de Geus Living Company, Semler's Three Ring Model, Theory of Constraints... Despite great initial success, all these initiatives have failed.
    Now Lean and Agile show signs of failing, for the same reason their predecessors failed.
    The problem is that when a small system, like an Agile team, tries to change a large system, like a company and its customers, through long and continuous contact, the small system will change much more than the large system.
    This is also known as Prescott's Pickle Principle:
    Cucumbers get more pickled than brine gets cucumbered
    Can Agile and Lean avoid getting pickled the same way they predecessors have been? Yes, the solution is doing LESS!

    Writing LESS!
    The LESS! book cover and the first four chapters.

    The LESS! book is close to completion. All chapters are in, I have edited more than two thirds of the book. This has been my most enjoyable writing project in a very long time. Writing a book always requires a lot of hard work, but it is also incredibly fun. If you work with great people, which I do, the fun factor goes up...way, way, up!

    I have wanted to write a collaborative management book for a couple of years now, but when I got the opportunity, I was not the first to recognize it. Katherine Kirk did!

    Katherine and I were both speakers at the LESS 2011 management conference. The conference was a blast. Lots of great speakers: smart, experienced, deep thinkers, and very good at presenting their ideas. I decided to take the opportunity to interview a few of them for a book project that had been on the back burner for a year. I hadn't written much for awhile, and I was really itching to write and publish a new book.

    Katherine made a great presentation, so I asked her if I could interview her for a book. She said yes, so we got together, and I got a very interesting interview. One of my questions was "what topic would you really like to see a management book on?" "This conference," Katherine said.

    I just sat there for a few seconds. This was just too good an opportunity to miss. Katherine was right. A book written by the conference speakers was a fantastic idea. I mothballed the book I interviewed Katherine for (Sorry, Katherine!), and asked her if it was OK if I took her idea to the conference organizers. She was fine with it, so I contacted Vasco Duarte. He liked the idea too, so I got a list of speaker email addresses, and we were off.

    The LESS! project works like this:

    Each writer contributes a chapter. Writers are encouraged, but not required, to edit each other's chapters. We have set up a LESS Author group on LinkedIn to make it easy to discuss the book among all authors. I do the final edit, help with graphics, I do the book layout and the cover.

    We decided early on that profits from the book should go to a good cause. Some details left to finagle there. I'll tell you more about that when everything has been set up properly.

    So, not only were people willing to take on a large amount of work, they were all willing to give the profits away. Oh, and they have all put up with my rough-and-tumble approach to editing. I have been most fortunate to work with such a hardy bunch of management piooneers.

    Writing and editing LESS! has been, and still is, a great adventure by its own right. I learn a lot, about management, about writing, editing, layout, cover design, and about collaboration. I work with great people. I also learn a thing or two that will be useful in the future. I'll let you in on what they are, in the near future. You will not be disappointed.

    Now, it's back to editing LESS! for me. See you soon.

    iBook Author – Apple Changes the Game Again!

    The latest game changer from Apple is a bit sneaky. Apple recently launched iBooks Author, an eBook authoring tool. There were ads in the App Store of course, but overall, not much fanfare. Nevertheless, iBook Author is an important move. Amazon needs to watch out, or Apple will grab a sizable chunk of the eBook market.

    Why is iBooks author important? iBooks Author puts Apple in direct contact with authors, bypassing a traditional obstacle to publishing, publishing companies.

    A traditional publishing flow looks like this:

    Apple cuts out the people in the middle, like this:

    Publishing becomes easier, faster and cheaper than before. By itself, this would not be a decisive advantage. Amazon has 90% of the eBook market, and they aim to keep it.

    However, Apple has another little innovation up its sleeve: the iBooks Author workflow. It looks like this:

    An author can work directly in iBooks Author, write an eBook, integrating text, video, audio, presentations, even 3D objects, and publish a finished book by clicking a button. This is quite different from the publishing process most book publishers use. It is both faster and cheaper.

    Perhaps most important: the quality of the eBook itself is a lot better than most of the competition. At Amazon, eBooks are usually converted from print editions. At the iBook Store, an increasing number of eBooks will be designed to be eBooks from the start. This will make a big difference.

    iBooks Author is free, so the economic barrier to publishing high quality eBooks just disappeared. (The economic barrier to publishing really awful eBooks also disappeared. Too early to tell how that will work out.)

    Right now, compared to Amazon the iBook Store is a bit thin on books, but that only makes it easier for an iBook author to get noticed, and thus makes it easier to sell. Mainstream authors may not have much of an advantage, but niche authors will. Dominating a niche is the key to building mainstream sales.

    For about a year or two, authors writing for the iBook market have an excellent opportunity to break into literary niches and grow their readership.

    Whether the iBook Store will grab a sizable portion of the eBook market or not is by no means certain, but Apple is certainly making a credible attempt. Instead of slugging it out toe-to-toe with Amazon, they strike at the weak spots in the production chain.

    It is by no means certain Apple's strategy will succeed in the end, but as a writer, I am tempted to test the waters with an ibook or two.

    Viva la Pasta! - Spaghetti Management

    Bo Hagström is a well known chef, and hosts Sun Food (Swedish: Solens Mat), a Swedish TV show. I met Bo when he signed books in a bookstore. His latest book, Viva la Pasta! is about, you guessed it, pasta!

    Bo is on a mission: He wants to teach Swedes about pasta. As it turned out, with good reason. I got a short but interesting lesson.

    Bo handed me two strands of pasta and asked me to feel them. One strand was very straight, and felt completely smooth. The other strand was different, slightly crooked. The surface felt slightly rough.

    The straight, smooth strand is bad pasta, Bo told me. It is low on nutrients. It does not taste very good either. Because of the smooth surface, it does not absorb flavors from other ingredients.

    The slightly crooked strand with the rough surface is great pasta. Much more nutritious. Because it is porous, it can absorb flavors from sauce and other ingredients.

    The two kinds of pasta cost the same in the store. The bad pasta outsells the good pasta many times over. Pasta buyers lack the knowledge they need to distinguish between good and bad pasta.

    "The cost isn't important," Bo said. "What is important, is the value you get."

    I couldn't help laughing, because I realized it's exactly the same thing in my job. In your line of work to, I'm sure.

    Imagine that you are a pasta-consultant. You want to teach manufacturers how to make really good pasta, and buyers how to choose the best kind. How would you do it? How would you convince manufacturers to make better pasta when the consumers don't know the difference between good and bad? When the consumers have never tasted good pasta, don't even know there is good pasta.

    We can distinguish good from bad only when we have different things to compare with each other. With pasta, you can taste and feel the difference. And, it is no big deal if you buy a package of some brand you haven't tried before, and discover you don't like it.

    It is much more difficult to try something new if it is expensive, if the stakes are high, and if it is difficult to assess the result. Picking the right ideas about leadership, management, and process design would fall into that category.

    What I learned from Bo, besides choosing pasta, was this: I need to show potential customers something simple, like two strands of spaghetti. It must be something that can be felt, so the difference can be experienced.

    Something to think about.

    Of course I bought a copy of Bo's book. Pasta experiments await!

    Oh, there is one thing more:

    Suppose you have a pasta factory, and you want to make the very best pasta. For this, of course, you must have the very best process, so you start a Six Sigma program.

    Will that Six Sigma program give you straight, smooth pasta, or crooked, rough to the touch pasta?

    Beyond Budgeting

    The chief cause of problems is solutions.
    –Eric Sevareid

    At the LESS 2011 conference an entire track was dedicated to solving the problems caused by the annual budgeting systems most organizations use.

    Yes, caused! We have used annual budgeting for a long time. This means annual budgeting was created to solve problems in a world quite different from ours: The world moved slower, in more predictable cycles.

    Today, the world changes very quickly, and is a lot more unpredictable. This is not a bad thing per se. You can turn it to your advantage (which is what I talked about at the conference), but doing that while hanging on to an antiquated economic model is very difficult, to say the least.

    Does this sound familiar:

    • "Great idea, but we can't do it right now. Let's wait for next year's budget." The great idea will be delayed, which means your company will lose the money it could have earned during that delay. Even worse, delaying implementation means someone else may get there first, and take your market away. Or, the great idea may simply be forgotten. The employee who had the idea may get tired of waiting and move on to another company, or start up a business of her own.
    • "To ensure that we get the budget we need next year, we need to spend the money we have budgeted this year." Utter insanity from the point-of-view of the whole organization. And yet it makes sense from the point-of-view of a department or a project.
    • "Unfortunately cross-the-board budget cuts forced us to close down X. Without X, so much revenue was lost that we had to cut Y. We lost the company in the end, but there was really nothing else we could do." To put it very frankly: Bull! Truly hopeless situations are rare. Most of the time, the real problem is that the way we solve problems isn't very good. At the LESS conference, I demonstrated a Chinese problem solving method with the cut-the-budget method common here, and showed how the Chinese method can generate solutions simply not available to a person with a focus on the budget. (We also used the Chinese method, very informally, at a breakfast meeting to generate some nifty strategic moves for next year's LESS conference. That was fun!)
    There are of course upsides to budgeting, primarily the feeling that you are in control. If you control the numbers, you control the organization, right?
    No, you do not! Controlling the numbers is actually a very weak form of control. Look at this model of leverage points you can use to lead an organization (or change any system):
    The picture shows Donella Meadows model for changing organizations and other systems. This model has been used for many years now. Unlike budgeting systems, it has stood the test of time.
    Note that setting constants, parameters, and numbers, and setting buffer sizes, are the two weakest forms of controlling a system. In other words, relying on making a prognosis and setting a budget is like bringing a couple of knives to a gunfight. Moving Beyond Budgeting frees you to use more powerful means to lead the organization.
    The weakness inherent in how most organizations are managed and lead shows up in the statistics. I find this little piece of information more than a little worrying:
    The slide above is from my own presentation at LESS 2011: In 1937, an S&P Fortune 500 company had a life expectancy of 75 years. Today, the life expectancy is 15 years, and still dropping.
    If you just sit and wait, you will join the growing casualty list. Moving from a budget based system to a more flexible Beyond budgeting system is not the only thing you will have to do, but it is an essential part of it.
    When you do that, you will suddenly be able to deal with many other problems concerning organization, employee motivation (, and your own motivation, I might add. You'll be a lot happier,), strategy, customer satisfaction, profitability, innovation,... the pieces will begin to fit. This immensely increases your chances to survive and thrive.
    There are many organizations that have moved beyond budgeting, or are in the process of doing it right now.
    Bjarte Bogsnes, a keynote speaker at LESS 2011, is heading the Beyond Budgeting project at Statoil. He has also implemented Beyond Budgeting at the petrochemicals company Borealis. In his presentation he mentioned more than thirty companies using or currently moving to Beyond budgeting. These companies include:
    • Statoil
    • Handelsbanken (a very successful Swedish bank)
    • Google
    • Telenor
    • COOP
    • Arla
    • Southwest Airlines
    • Gore & Associates (makers of Gore-TEX)
    • Kongsberg Automotive
    • American Express
    • Sparebank
    • Jernia
    • Ahlsell
    ...and the list goes on.
    Leaders in these companies are facing reality, and have determined to break the bad habit of budgeting. After all, budgeting is not a necessity. There are proven alternatives. Budgeting is a bad habit, like smoking. Changing bad habits is difficult, but it can be done. Survivors do it all the time.
    You might want to read a bit more about Beyond Budgeting:
    Beyond Budgeting Round Table is a web site dedicated to Beyond Budgeting. There you will find more information, and links to books.
    Implementing Beyond Budgeting (link to Kindle edition) by Bjarte Bogsnes is a very good book on Beyond Budgeting. Bjarte heads the Beyond Budgeting project at Statoil. He also implemented Beyond Budgeting at Borealis.
    Beyond Budgeting: How Managers Can Break Free from the Annual Performance Trap (link to Kindle Edition), by Jeremy Hope and Robin Fraser is also a good book.
    Survival – The Reason I am going to LESS 2011

    There are plenty of good reasons to go to the LESS 2011 management conference. Most of them have to do with fun–not clowning around fun (which has its merits)–but with the doing-meaningful-work and living a life of purpose kind of fun.

    However, there is another reason: Survival!

    According to John Hagell III, in 1937 the average life expectancy of a Standards & Poor Fortune 500 company was 75 years. Today, it is about 15 years. Let's be a little bit simplistic about this, and draw a straight line between the two data points. Then let's be a bit adventurous, and extrapolate into the future.

    If this simple projection holds, by 2030, there won't be any S&P Fortune 500 companies.

    I am sure you can see the flaws in this simple model as well as I can:

    • There are only two data points. It is very easy to draw the wrong conclusions when using to few data points. (Though many companies are perfectly happy to use a single data point, which enables them to interpret it anyway they want. But I digress.)
    • The model is linear. Reality is rarely linear.
    • It'll never happen because something else will happen that changes the game.
    All true. Nevertheless, this simple projection does indicate that we are heading for some serious change, one way or another.
    The change may be good or bad, but it will happen. Shift happens!
    If you are in the water, and a great wave comes along, two things can happen: You are crushed by it, or you surf on it.
    Which would you rather do?
    I am going to LESS 2011 to meet with a gang of surfers, to talk about surfing the waves of change, and to have a blast while doing it.
    If you want to be a surfer to, join in at LESS 2011. If you can't be there, why not check out the people speaking there, and ask a couple of them to visit you and share what they know. About surfing the wave of change. About survival. About having fun and meaningful work.
    Tim Morrison at the Halmstad City Library
    Tim Morrison at the Halmstad City Library

    Tim Morrison played at the Halmstad City Library tonight. I had been sitting there working, most of the day. Luckily, I decided to stay a bit later than usual.

    I have no idea how to write about music, so I won't. Instead, I'll suggest you check out Tim's band, The Manglers. You'll find some sample songs at The Mangler MySpace page.

    Tim and I talked a bit after the gig. I bought a CD, which I am listening to as I write this. When Tim talked about writing lyrics, I recognized what I experience when writing a book or working on a presentation. It never ceases to amaze me how things that are very different on the surface, can be very similar on a deeper level.

    Some people can't help horsing around...

    As you can see above, there were other things happening at the event. In all, a very enjoyable evening.

    The Gothenburg Book Fair (A brief guide to mingling, Part 2)

    This post continues the networking story from A brief guide to mingling. I strongly recommend you read that post first, because in it, I describe why I network. Having that perspective is important. If you read  A brief guide to mingling, I think you will agree.

    I went to the Gothenburg Book Fair today. The book fair is a yearly event. I go to look for interesting books, and to meet interesting people. Let's dive right in and see what happened:

    Erik Lundh, a friend of mine, and I had agreed beforehand to meet at the fair. Anna Sigvardsson, the photographer I met at the mingle last week and I had also decided to meet and have a cup of coffee at the fair.

    When I arrived, I had plenty of time before meeting either Erik or Anna, so I did what everyone else at the fair does: I went looking for anything interesting that might catch my eye.

    Kersti Ingeborn works at the Mediapool's School Library Service

    Pretty soon I found myself talking to Kersti Ingeborn at the Mediapool  School Library Service. We found we had some interests in common. In addition to working at the School Library Service, Kersti is also engaged in health care. After talking briefly, I promised to email her a link to this blog post, and moved on.

    Stefan Olsson at Universe Imagine is an author, so we did what authors do when they meet: We swapped books.

    One of the nice thing with the book fair is that it is an opportunity for me, as a writer, to meet and speak with other writers. Thus, when I saw Stefan Olsson at Universe Imagine, I went over and talked to him.

    Stefan and I swapped writing and publishing experiences for a couple of minutes. Then Stefan suggested that we should swap books, so we did.

    It is not fair to hog the time of someone working at the fair, so I told Stefan I would email him a link to this blog post, and moved on.

    Astute readers may notice a pattern developing here. I follow up the connections I make, and I offer a reason to continue with some sort of contact. I only do this when I believe there really is some reason to keep in touch. The decision to continue the contact, or not rests entirely with the other person.

    As I wrote in  A brief guide to mingling, the purpose is not to sell or advertise anything, but to find and connect with interesting people.

    Anna Sigvardsson is a photographer. I wrote about meeting her in A brief guide to mingling.

    Of course, if you have agreed to meet two people at a book fair that lasts all day, they will arrive within a few seconds of each other. Erik beat Anna by about 30 seconds. Erik and I needed to talk about a few work related matters, so we did. Then I went to have a cup of coffee with Anna.

    You wouldn't believe the size and weight of the backpack I had lugged around all morning. Putting it down, having a cup of coffee, and talking photography and books was a relief you cannot imagine. Unless you to carry around a similar backpack, of course... Thanks Anna!

    After meeting with Anna, I hooked up with Eric again. Eric mentioned he wants to meet with a photographer, so I fired off an SMS to Anna to see if she would be interested in meeting Eric. She was, so I helped Eric and Anna set up a meeting. The cellular phone network was a bit overloaded, so we did everything by SMS. SMS wasn't altogether reliable either at the fair, but it worked out OK.

    Erik Lundh is a co-author of The System Anatomy, and Jens Fredholm at Studentlitteratur is the publisher.

    Eric had a meeting with Jens Fredholm at Studentlitteratur. Eric is a co-author of a recently published book, The System Anatomy. Jens is one of Eric's main contacts. Eric invited me to an after-the-fair for-people-in-the-publishing-business mingle, and off we went to see Jens.

    I have met Jens once before, but that was briefly a year ago, so Eric re-introduced us.

    It was nice meeting Jens again. Eric, Jens and I had an interesting talk. We decided to go and eat something, and that is when I suddenly saw Alf Fyhrlund and his wife Saga.

    From left: Alf Fyhrlund, Saga Fyhrlund, Jens Fredholm, and Erik Lundh.

    Alf is the statistician I wrote about in  A brief guide to mingling. Introductions were made all around, and business cards were exchanged. (Just so you know: Alf and I will go to a BNI meeting together on Tuesday.)

    After that, the only new connection I made the rest of the evening was with a humungous shrimp sandwich. (Thank you Jens.)

    Let's update the network diagram from  A brief guide to mingling:

    There are new connections, and some old ones have been maintained (Jens and me). One thing I like about having a diagram like this, is that the people in the diagram are likely to read this post and see it. That increases the probability that they will discover a reason to connect.

    If one is steeped in Command & Control culture, it is easy to believe that one should somehow be in control, or "own the network". That does not work. Nobody owns the network. I belong to the network. So does everyone else in the diagram.

    Thus, I am not at the center of the network, even though it may look like that in the diagram. It is just that the diagram is drawn from my perspective, and contains the connections I know about.

    Draw diagrams from the perspectives of Eric, Jens, or Anna, and they will look quite different, but they will be just as valid. (Try drawing a complete diagram, and you will end up with a mess and go bonkers in the process.)

    The network will change today, like it changed yesterday. I know Alf and Olle are likely to talk to each other, and I know Anna and Erik will too. I will ask them how it went, because these are people I like, and I have an interest in their connections working out for the best. Other things will happen too, lots of connections will be made I don't know about, and never will know about. That is as it should be.

    What is of interest to mingle event goers is that many of the things I described here, happened because of the mingle event, Göteborgsminglet, but they did not happen at the event. Mingle events are powerful because they generate sparks that may ignite something larger and longer lasting.

    Oh, perhaps I should mention: The fair itself was fun too. Lots of interesting books.

    A Brief Guide to Mingling
    Anna Sigvardsson is a photographer. Martin Richards is an English language coach. Martin I know from before. He brought me to my first BNI business meeting a couple of years ago. Anna I met for the first time at the mingle, but we have both been BNI members, and have acquaintances in common.

    I was at a mingling event, Göteborgsminglet a couple of days ago. Such events have become an increasingly important way of meeting people and developing business relationships.

    I left the event with one solid lead and more than half a dozen meetings booked. This is a marked difference from the first mingling event I went to about two years ago. When I left that first mingle, I had an enormous stack of business cards, but didn't really know what to do with them. Last Thursday, I had a much smaller stack of cards, but I knew what to do.

    What is the difference between now and then? Mainly, me: My own expectations, my understanding of what an event like this is, and its purpose, have changed. A lot!

    The first time I went to an event like this, I went to do business. In other words, I went there to sell my services.

    Of course that didn't work! There were no buyers. There were two main categories of people there: One category were greenhorns like me, who tried to sell stuff, or advertise stuff. The other category were networkers.

    Mingling events are not about selling or buying, they are about meeting interesting people. You don't sell them stuff, you talk to them. If they are interesting, and if they feel the same way about you, you set up a meeting.

    "Ok, and at that meeting, I get to sell!" No! You don't! You go to the meeting to figure out a few things:

    • Is this a person I want to spend time with? For example, if we go out and have lunch ten times, will we have more or less to talk about the tenth time than the first time? Will I enjoy listening to this person on a more or less regular basis?
    • Can I be of value to this person? One thing you can do, is to connect them with other people in your network. That is good, but don't rush it. Get to know the person first. You do have a responsibility to weed out the kooks (or make connections to compatible kooks). You can do other things. For example, if you meet me, and recommend a particularly interesting book about management, systems thinking, photography, or a good Fantasy book, you are of value to me. One of my favorite clients put me on to the Obiter Dictum podcasts. I walk two hours every day, and I often listen to Obiter Dictum while doing it. Now that is value... (When do I get to sell? When do I get to sell? Not yet!)
    • Does this person want to be of value to me? Not can, want. Does this person have a desire to play by the networking rules? If they do, they'll figure out how to help you with something, sometime. In the unlikely event they don't, they will still figure out how to help someone else. If you build connections with people like that, you will eventually end up with plenty of good business leads.
    Some people are just naturally good at this. I am not. I have to study and practice. There are lots of places where you can do that, but Business Network International is my favorite. It's ordinary people helping each other out in ordinary ways. They just happen to be very good at it.
    At the meeting last Thursday, I set two goals for myself:
    • Have good, interesting conversations with people. One would be enough. Not too long conversations though, because people have limited time to spend on a single conversation at these events. I got lucky and met several people I wanted to listen to.
    • Have dinner with someone well worth listening to after the mingle. I almost made it: I had a cup of coffee with someone very interesting to speak with and listen to. Very enjoyable. 
    In the beginning of this post, I told you I got one very solid lead. Here is a key point:
    I got the lead from someone I have known for the better part of two years. We met through Business Network International (BNI), we became friends, and we have dinner together on an irregular but fairly frequent basis. This person has a lot of integrity, and he is very careful about recommending people. He is a highly valued friend of mine.
    Most of the meetings I booked during the mingle were with people I have met before. Some are friends. Some are acquaintances. Only two were with people I haven't met before, and one of them know people I know.
    Good networkers often say networking is like gardening. Now you know why: It does take time, patience, and genuine interest. Some relationships grow, others wither.
    Alf Fyhrlund is a statistician.
    Speaking of growing relationships: Meet Alf Fyhrlund. I met Alf for the first time at the mingle. We had a brief chat, and I gave him my business card. Alf is a statistician. He does research, and he is also a consultant. I happen to know something most people don't: Statisticians can be very useful to companies and other organizations. Also, statisticians are well aware that the mere thought of statistics make most people's eyes glaze over. Thus, they are searching for, and developing, ways of making what they do easier to understand, more interesting, and easier to apply in practice.
    Alf and I decided to have a cup of coffee together. We did, and I had a very interesting afternoon. Alf and I connected on Twitter and Facebook.

    Another acquaintance of mine, Olle Ebbinghaus, posted a message on Facebook, saying that he wanted to talk to a statistician.

    I talked to both Olle and Alf to see if they would like me to connect them. I usually don't connect people like this unless everyone has said it is OK. Both said yes. In a couple of days, I will follow up by asking them how their meeting went.
    At the mingle I also talked with Anna Sigurdsson and Martin Richards, whom you can see in the first picture in this post. Martin invited me to a networking event, and I invited Anna to meet a Mystery Friend of mine. (A mystery to you, that is. Anna knows whom she is meeting, but I haven't obtained my friend's permission to use her name and picture in this post.) Anna, in return, offered to connect me with some people she knows.
    Let's look at a diagram. If you follow this blog, you know there will, sooner or later, be diagrams:
    During the mingle, our social networks began to reconfigure. That is, we made new acquaintances.

    Before the mingle, we had several disconnected networks, like this:

    This is the network before the mingle. The people in green circles attended the mingle. The people in blue circles did not attend the mingle, but their social connections are affected by it. Note that there are three disconnected network islands.

    During the mingle, the social networks we have begin to connect, but the really interesting stuff happens after the mingle itself. After couple of days, with some follow up work, the network looks like this:

    After the mingle, and a bit of follow-up, we have a new set of connections, and a world of new possibilities.

    Good networkers follow up. I have spent more time following up the mingle than I spent going to the mingle itself. So did Alf, Anna and Martin.

    For simplicity's sake I have left out a bunch of stuff. For example, I didn't mention how, when I checked out Alf on the Internet, quite a few recommendations popped up. Same thing with Anna. Plenty of recommendations.

    I haven't mentioned the other people I met either. A complete diagram describing the changes in my social network would take longer to draw than the two hours the event itself took. The changes are ongoing. At the time I am writing this, I haven't had all the follow-up meetings yet. I have some interesting people to meet next week.
    I have described only a part of how my social connections changed because of the mingle. Imagine the total number of new connections created or old ones strengthening during the event.
    There is a huge amount of change going on. Most of it is short-lived, to be sure, but some of it isn't. Some of the change will be permanent. Some of the change will open up great new opportunities.
    Here is a thing you might find interesting: There is an organization that organizes the mingle, sets the date, determine rules for the mingle (like: wear A4 size papers naming yourself, your company and describing your goal for the mingle), handles catering, etc.
    Within that framework, the mingle is self-organizing. Nobody tells people whom to speak to, what to say, or what to do. People figure it out, it works, and it is fun.
    Self-organization is interesting, because it may be the key, well, one of the keys, to building better business organizations in the future. Thus, mingling like this has an important social function that may not be obvious: It makes people more used to self-organization, which is a key to building competitive organizations today and in the future.

    When people who learn to mingle like this, take what they learn, and apply it to their own work, and their own private lives, that is when the really interesting stuff will happen.

    Happy mingling!

    There is a follow-up to this article, connecting what happened at the mingle event with things that happened at the Gothenburg Book Fair a week later.

    I promise to do LESS in 2011!

    The LESS 2011 conference in Stockholm, October 30th to November 2nd, looks set to be a lot of fun. A highly inspirational and useful kind of fun.

    If you go, you get to see and listen to keynote speakers like Steve Denning, former director of knowledge management at the World Bank, and Bjarte Bogsnaes who head's Statoils Beyond Budgeting project. You can hear systems thinker Peter Middleton, and Shingo Prize winner James Sutton.
    Check out the speaker lists and the topics, and you will understand why this is an event I do not want to miss. There is a long list of interesting speakers. I'll mention only a few, and I'll not even try to be unbiased about it. Instead, I'll pick those with whom I have had some contact, via social networks or otherwise, over the years:

    Jurgen Appelo has a talk titled Complexity Thinking? Or Systems
    Thinking++ ? Jurgen will talk about similarities and differences between Systems Thinking and Complexity Thinking, and he aims to connect them with Agile software Development, and the real world of business. Jurgen wrote the book Management 3.0: Leading Agile Developers, Developing Agile Leaders, and he is a very popular speaker.

    Ola Ellnestam will talk about Real Options. Ola is the CEO of Agical. I met Ola about half a year ago when I made a presentation at an Agical Geek Night. He is going to talk about how to keep options open in a project until the last responsible moment, without crossing the line and turning the project into a game of chicken.

    Torbjörn Gyllebring, is one of the most interesting people I have met on Twitter. Sharp, accurate, concise observations about software development and developers. His talk is titled Kanban is not your process (let me tell you why).

    Bob Marshall's talk is titled Keep it Light-Hearted. Bob is experienced, courageous, and has boundless energy. He is going to talk about Rightshifting and the Marshall model. I don't know much about what Bob will say, and I hope he doesn't tell me, because I want to hear it for the first time when I listen to his session.

    There are plenty of other speakers, and because my sample was 100% biased in favor of social connections and friendship, you can be assured there are many interesting speakers among the ones I did not mention too.

    Oh, perhaps I should tell you, I got a submission accepted too. You can read about it if you go to the Transforming Organizations page and scroll down a bit. I won't tell you about it in this post, because I would like you to scoot over to the LESS website.

    Customers

    A2I
    ACTEMIUM
    ADP
    AEI
    AGRANA
    AIR LIQUIDE
    AKTEHOM
    ALSTHOM
    APPLEXION
    APRISO
    APV-INVENSYS
    ARC-INFORMATIQUE
    AREVA TA, NC, FBFC
    ASPEN TECH
    ATOS ORIGIN
    AVIN OIL
    AXENS
    BAXTER
    BAYER
    BEAI
    BIC
    BNIC
    BP
    Bristol Myers Squibb
    BRITISH AIRWAYS
    BUHLER MIAG
    CEA
    CEGELEC
    CETIM
    CHEVRON
    Chipita International
    CIRA-CONCEPT
    COGESAL-MIKO
    COKA COLA
    COMATELEC
    CONCISE MANAGEMENT
    COURBON
    CRP Henri Tudor
    DUPONT
    EDF
    ELAN SOFTWARE
    EMKA
    ERELIA
    EURIWARE
    EVALI
    EXXON MOBIL
    FAGE
    FLEURY MICHON
    GDF
    GDF Suez
    GOODYEAR
    GROUPE LAFARGE
    GSKBio
    Haute Ecole Léonard de Vinci-ECAM
    HD TECHNOLOGY
    HEINEKEN
    Hellenic Petroleum
    HIMA
    HONEYWELL GERDS
    ICOTEM
    IDBS
    ILSYS
    INCOTEC
    INFOTEAM
    INFOVISION
    IPEDEX
    JOHNSON & JOHNSON
    KLM
    KNAUF SAS
    KNORR
    L'Oréal
    LACTALIS
    Le Gouessant
    LILLY
    LOGICACMG
    MASSELIN OCEANE
    MASTERFOOD-ISI
    MICHELIN
    MILLIPORE
    MSD
    NESTLE
    NEXANS
    OET
    ORDINAL
    PERTINENCE
    PETZETAKIS
    PFIZER
    PRINCEPS
    Public Power Corporation
    QUASAR SOLUTIONS
    REMINEX
    RENAULT
    RHODIA
    ROCKWELL AUTOMATION
    ROHM & HAAS
    SAINT LOUIS SUCRE
    SANOFI AVENTIS
    SCHNEIDER ELECTRIC
    SIEMENS
    SILICOMP MANAGEMENT
    SOFREGAZ
    SOLVAY
    SPC-CONSULTANT
    ST GOBAIN
    SUPELEC Rennes
    SYDEL
    TECHNIP
    TETRA PAK PROCESSING
    TEXACO
    TINEA
    TITAN CEMENT
    UCB-PHARMA
    UNILEVER
    UNILOG
    UNIV. DE TECHNOLOGIE Troyes
    VEOLIA
    WONDERWARE
    WRIGLEY
    YOKOGAWA
    YTONG