Category Archives: Teamworking

Hirotaka Takeuchi & Ikujiro Nonaka: Scrum Development

Hirotaka Takeuchi and Ikujiro Nonaka have featured in an earlier Pocketblog, which was focused on Nonaka and the work  he led on how knowledge can transform organisations.

Arguably, it is how Nonaka and Takeuchi took some of their thinking forward that has led to a far bigger transformation. In 1985, they co-wrote an article for the January 1986 edition of Harvard Business Review. Called ‘The New New Product Development Game’, this article was instrumental in revolutionising the discipline of Project Management.

Takeuchi and Nonaka gave us a new way of thinking about how to develop products and deliver projects. And they coined an evocative sporting metaphor for their process, which has stuck: Scrum.

Hirotaka Takeuchi & Ikujiro Nonaka

Hirotaka Takeuchi & Ikujiro Nonaka

Ikujiro Nonaka

Born in 1935, Ikujiro Nonaka gained a BS in political science at Waseda University, then started work at Fuji Electric, where he created their management programme. Nonaka left Fuji in 1967, to study at the University of California, Berkeley. He was awarded his MBA in 1968, and his PhD in Business Administration, in 1972. He took posts at US universities, before returning to Japan, as a professor at the Graduate School of International Corporate Strategy, Hitotsubashi University.

Hirotaka Takeushi

Born in 1946, Hirotaka Takeuchi got his BA from the International Christian University, Tokyo. After a short spell working at McCann-Erickson, he went to the University of California, Berkeley, where he got his MBA in 1971, and his PhD in 1977. During his time at Berkeley, he also worked summers for McKinsey & Company in Tokyo and, more important, met Nonaka.

Takeushi took a lectureship at Harvard in 1976 until 1983, when he joined Hitotsubashi University School of Commerce, where he became a full professor and Dean of the Graduate School of International Corporate Strategy. He stayed until 2010, when he returned to Harvard, as Professor of Management Practice, where he is now.

The New New Product Development Game.

In January 1986, Harvard Business Review published ‘The New New Product Development Game‘ by Takeuchi and Nonaka. This was about a new way to do New Product Development, or NPD. They drew on the idea of ‘ba’ – a Japanese coinage of Nonaka’s, meaning a meeting place for minds and the energy that draws out knowledge and creates new ideas.

They also took a look at the Toyota idea of teams coming together to solve problems. They introduced a sporting metaphor from the game of Rugby; that of the scrum. They used scrum to denote the way teams work together intensively when the ball goes out of play. In a work environment that demands creativity and innovative problem solving, this is just what is needed.

They followed this article up with a 1995 book, ‘The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation‘. This looks at the way Japan became a major economic power, especially in the automotive and electronics industries. they argue that Japanese firms are successful because they create new knowledge to produce successful products and technologies.

Scrum Teams

The model they created for Scrum Teams is of a cross functional group that can work autonomously to resolve its own problems. Their organisation is ’emergent’ meaning there is no assigned leadership or structure; it just emerges from the effective collaboration of its members.

To work best, a Scrum Team needs to be co-located, and work together full-time. This allows a high level of cross-fertilisation of ideas, and a dedication to working on their shared problems, tasks, and initiatives.

Scrum as an Agile Project Management Methodology

Agile project management seeks to avoid the all-or-nothing approach to projects that used to characterise traditional approaches – especially when done in a way that slavishly follows a set of ‘rules’. Although good project managers have always incorporated a lot of plan-do-review (the Deming Cycle), the growth of software development projects demanded an increase focus on agility and incrementalism.

This was the basis of the Agile movement and today the single most widely used Agile methodology takes its name and guiding principles from Takeuchi and Nonaka’s metaphor: Scrum.

In Scrum projects, a Product Owner is responsible for detailing the business requirements and ensuring that the business gets a good return on its product development investment (RoI). The Scrum Team, led by a Scrum Master, selects one subset of functionality from a product backlog of undeveloped functions, divides it into tasks, and works intensively on developing the outputs for a fixed time, known as a Sprint, which is usually 30 days.

Each day, the team gets together for a daily Scrum Meeting to share learning, report progress, discuss challenges, and solve problems. At the end of the sprint, the team should produce a working product that is stable and useful. After a reflection and learning process, the team then works with the product owner to define the subset of functionality it will work on in the next sprint.

The team continues like this until the Product Owner concludes that the next sprint would not create enough additional value to justify the incremental cost.

The Scrum Project Management Lifecycle

The Scrum Project Management Lifecycle

 

Karol Adamiecki: Management Harmony

We tend to think of leading management theorists as coming from the United States. This seems especially so of Scientific Management. But when the privilege of naming things for the world’s largest audience goes to those who write in English, history creates a bias. And because that audience largely reads only one language, that bias gets amplified.

One of many losers from the Anglo-centric nature of management and business thinking was Karol Adamiecki. He was a Polish engineer, turned economist and management thinker, who can claim to have invented the Gantt Chart before Henry Gantt, PERT before the US Navy, the Theory of Constraints before Eliyahu Goldratt, and much of Scientific Management before FW Taylor.

Karol Adamiecki 1866-1933

Karol Adamiecki 1866-1933

Short Biography

Karol Adamiecki was born in southern Poland, in 1866. He studied engineering at the Institute of Technology in St Petersburg, graduating in 1891. He then returned to his home town, where he took charge of a steel mill. He stayed for nearly 30 years, during which time, he formed his ideas about management.

In 1919, he left the mill, and became a lecturer at the Warsaw Polytechnic, becoming a professor in 1922. There, he further codified and published his ideas. In 1925, he founded the Institute of Scientific Management in Warsaw, becoming its Director and remaining until his death in 1933.

Adamiecki’s  Law of Harmony in Management

While running the steel rolling mill, Karol Adamiecki developed sophisticated thinking around management that was, from our perspective, ahead of its time. The three principal components were:

  1. Harmony of Choice
    Management should select and supply production tools that are mutually compatible. He went on to argue that this should be especially so in terms of their output production speed. This anticipated the Theory of Constraints, and the ideas of Eliyahu Goldratt by 75 years or more.
  2. Harmony of Doing
    Sequencing and scheduling of activities need to be fully co-ordinated to optimise production efficiency. Here, he not only developed a tool that looks very similar to the Gantt Chart, well before Gantt published. His approach also anticipated the US Navy’s Program Evaluation and Review Technique (PERT) and du Pont’s Critical Path Method (CPM) by over 50 years.
  3. Harmony of Spirit
    I imagine the Pharaohs’ overseers were constantly emphasising the importance of creating a good team. But this is another theme that feels very modern – perhaps even more so than the other two. Let’s not forget that Taylor’s view of Scientific Management was mechanistic and process-oriented. It took Mayo to bring humanism to the fore, and ideas of team working in management only started to dominate from the 1970s.

Adamiecki started to publish in 1898, several years before Taylor did so.

Harmony of Doing:
The Harmonograph or Harmonogram (or Harmonograf)

In 1896, Adamiecki solved the problem of sequencing and scheduling in production and published, in1903, his solution. He called it a Harmonograf. And it looks very much like what we now call a Gantt Chart. However, Henry Gantt did not publish until 1910. There is no evidence to suggest Gantt copied Adamiecki’s idea.

In constructing the Harmonograf, however, Adamiecki describes a process that is pretty similar to the PERT and CPM methods. He certainly is able to include critical path and float. These are two concepts Gantt did not consider at all.

As Adamiecki described his methods, he was able to optimise production schedules by sliding paper tabs and arranging paper strips. In a very real sense, he developed an analog scheduling computer.

Assessment

Without a doubt, Adamiecki’s thinking was of its time, but way ahead of its rediscovery. He possibly failed to realise just how valuable it was. But more likely, he simply suffered from an Anglophone bias in scholarship and manufacturing. Publishing in Polish simply did not get him recognition far beyond the borders of his home country. Even now, it is only in the Karol Adamiecki University of Economics in Katowice, that his name is celebrated.

And I have to ask, could this happen again? Yes. I think it can, will and probably is happening now. Last week, we met Vlatka Hlupic. Arguably, her work is known despite her Croatian origin, because she lives and works in London. With the US and the UK increasingly looking to close their borders for differing but related reasons, the next Karol Adamiecki’s work could well lay undiscovered for just as long as that of the first.

Amy Edmondson: Teaming

Amy Edmondson is an Engineer turned Management and Leadership Professor, who has made a special study of how to create effective collaboration among small, disparate groups in informal circumstances. This, she believes, is the key to organisational success in a world where innovation is critical.

Amy Edmondson

Amy Edmondson

Very Short Biography

Amy Edmondson grew up in New York, and studied Visual and Environmental Studies and Engineering at Harvard University, graduating in 1981. For a short while, she was Chief Engineer at the Buckminster Fuller Institute. After she left, she published a book, ‘A Fuller Explanation: The Synergetic Geometry of R. Buckminster Fuller’ about Fuller’s ideas.

She then moved to the Pecos River Learning Centers, where she became Director of Research, until starting a PhD in Organisational Behaviour at Harvard in 1991. When she completed it, she joined the staff of Harvard Business School, where she is currently the Novartis Professor of Leadership and Management.

Failure

For many people, Amy Edmondson came to notice with her 2011 Harvard Business Review article ‘Strategies for Learning from Failure‘. In this, she argues the case for ‘intelligent failures’ setting out a neat model of how failure spans a spectrum from blameworthy to praiseworthy.

Reasons for Failure - Amy Edmondson

Reasons for Failure – Amy Edmondson

The abilities to face up to failure, discuss it candidly, and be curious about it lead nicely into the work for which Edmondson is best known…

Teaming

Edmondson distinguishes the concept of ‘Teaming’ from the more familiar idea of teamwork. Teaming is about bringing together a diverse group and rapidly creating the conditions for close collaboration. It bears a close relationship with the idea of Swift Trust, which we discussed in an earlier Pocketblog.

However, whilst swift trust focuses on creating a solid basis for long-term collaboration quickly, Edmondson is more interested in short-term, informal collaboration. For this to happen, she identifies ‘three pillars’.

  1. Curiosity – to learn from the people around you
  2. Passion – so that you care enough to work your hardest
  3. Empathy – so you can see things from other people’s points of view

The role of leadership becomes one of role modelling these three behaviours. You must be driven to achieve the goal, enquire deeply into the situation, and tune into the needs and emotions of the people around you.

Edmondson’s book, Teaming: How Organizations Learn, Innovate, and Compete in the Knowledge Economy is very highly regarded and features a foreword by Edgar Schein.

An important concept that Edmondson introduces in her work on teaming is…

Psychological Safety

Teaming works – and teams work – when participants collectively feel that members can take risks together safely. They can share feelings and disclose actions without fear of recrimination. This creates a climate of openness, which Edmondson calls ‘Psychological Safety’. Again, the leader needs to model appropriate behaviours, acknowledging your own fallibility, and being curious and empathic.

Crucially, when you achieve psychological safety for your team, work becomes a problem of learning, rather than of executing actions. In this, Edmondson’s work complements Schein’s exceptionally well.

Edmondson in her own Words

There are a number of excellent videos available. In this 12 minute TEDx video, Edmondson is talking about Psychological Safety.

Bruce Tuckman: Group Development

Bruce Tuckman developed a model of group development which is among the most viewed management models on The Management Pocketblog. We cannot wait any longer: we must take a look at his life and work with a wider perspective.

Bruce Tuckman

 

Brief Biography

Bruce Tuckman was born and grew up in New York, gaining his bachelor’s degree in psychology from the Renesselaer Polytechnic Institute in 1960, and his MA and PhD from Princeton, in 1962 and 1963 respectively.

From Princeton, he joined the Naval Medical Institute in Bethesda, Maryland, as a research psychologist. Here, he joined a group of researchers that was researching the the behaviours of small groups, thinking about getting the best team working on small crewed naval vessels. His supervisor gave him a stack of fifty research papers, telling him to see what he could make of them. His analysis resulted in the developmental sequence that was to make him famous:

  1. Forming – orientation, relationship building
  2. Storming – conflict
  3. Norming – developing cohesion and behavioural norms
  4. Performing – team inter-dependence and collaboration

Tuckman subsequently acknowledged that it was the choice of rhyming names for the stages that he used in his published paper (1965) ‘which probably account for the paper’s popularity’. The terms are certainly memorable and evocative.

From 1965, when he moved to his first academic post, at Rutgers, Tuckman started to focus on Educational Pyschology. In 1978, he moved to City University of New York and then to Florida State University in 1983. In 1998, he moved to Ohio State University, as Professor of Educational Psychology, where he remained until his retirement.

Developmental Sequence in Small Groups

The group development model for which Tuckman is best-known has been well covered in the Mangement Pocketblog already; so much so that we took the unusual step of creating a portal blog to guide readers to the various articles, at: Bruce Tuckman’s Group Development Model. You can also read Tuckman’s original paper, Developmental Sequence in Small Groups.

In 1977, Tuckman was invited to review his original work and, with Mary Ann Jensen (at the time a Doctoral student at Rutgers, with Tuckman, and now a psychologist in private practice in Princeton, New Jersey), produced a review paper (Stages of Small-Group Development Revisited) that validated the original work, and added a fifth stage, Adjourning, ‘for which a perfect rhyme could not be found’ said Tuckman. Many practitioners (this author included) prefer to use the term ‘mourning’ – not because it rhymes, but because it reminds us of the emotional impact of separation and therefore of the role of the team leader in ensuring the team acknowledges the loss.

Procrastination

Tuckman’s work on procrastination looks excellent. I was going to look it up but…

As an educational psychologist, most of Tuckman’s work is of limited interest to a management audience. But one topic stood out for me: the bane of many managers’ lives… procrastination. We all do it.

In 1991, while Professor of Educational Psychology at Florida State Univesity, Tuckman published a self evaluation tool to measure tendency to procrastinate. This was a core part of his research into students’ self-motivation in studying. This became a a key plank in much later research which he applied very directly at Ohio State University, where he founded the University’s Dennis Learning Center. They still teach workshops and courses based on Tuckman’s research. All the research related to the learning centre listed on its website is Tuckman’s.

Here’s the research paper that caught my eye: at the American Psychological Association meeting in 2002, Tuckman presented a paper that showed how procrastinators get significantly poorer grades in class. What I wonder is this: is it reasonable to generalise that result to the workplace? I suspect it is.

The message would be clear: ‘just get on with it!’

 


 

For more on Tuckman’s model of group development…

… and for more on teams in general:

 

Meredith Belbin: Team Roles

Meredith Belbin is the leading management thinker in developing our ideas about team roles. His research in the 1970s led him to develop the team-role theory that bears his name. This is now a widely used model, supported by a range of commercially available tools distrbuted and supported by the company he founded in 1988 with his wife, Eunice, and his son, Nigel Belbin.


Brief Biography

Meredith Belbin was born in 1926, and grew up in the English Home Counties during the Second World War. After the war, he went to Cambridge to read classics, but transferred to study psychology, where he met his wife, and went on to gain a PhD. His early work was focused on the needs of older workers, but it was when working with his wife at the Industrial training research Unit (ITRU) that he did his breakthrough research.

He was invited to conduct research at the Administrative Staff College (now Henley Management College) and set up a long-running programme of studies with co-researchers, Bill Hartston, Jeanne Fisher, and Roger Mottram. Year after year, they observed teams of managers competing in business games, recording the way team members contributed and cross referencing this with results of numerous psychometric tests.

Belbin documented the conclusions of this research in his now classic 1981 book, Management Teams: Why they Succeed and Fail, which is currently in its third edition. Since then, he has written a number of books, perhaps the most successful of which has been Team Roles at Work.

Belbin’s Ideas

We have covered much of the detail of Belbin’s Team Roles model in an earlier blog: Meredith Belbin’s Team Roles Model. The fundamental thesis is simple: management succeeds or fails, not on the strengths of individuals, but on the strengths of the team. Because individuals bring individual strengths, personalities, and thinking skills, the strength of a team depends upon the mix of people in it. The components Belbin particularly looked at were:

  • intelligence
  • extroversion/introversion
  • stability/neuroticism
  • dominance

What Belbin was able to do, was merge the many different psychological and aptitude factors into eight (later extended to nine) archetypes*, which he has carefully noted are not pure personality types. This means that one individual can fulfill more than one of the team roles and, indeed, this is often desirable. Belbin found that the most successful teams had a balance of all of the team roles, but also that teams of around five members are optimal.

Belbin’s later research and writings have been more anthropological and philosophical in nature and have failed to gain much traction. They seem neither as grounded in empirical research as team roles, nor as practical in their application. However, Belbin’s place as a leading thinker is assured. Whilst other models of team roles have emerged – most notably that of Charles Margerison and Dick McCann – Belbin’s core ideas have stood the test of time, and the nine team roles he identified and the tools his company supplies remain the most widely used by management teams.

 


* ‘archetypes’ is my word, not his – and I do not intend it to suggest any particular affinity between Belbin’s work and Jungian archetypes. In fact, the primary psychometric instrument Belbin used in his research was Cattell’s 16PF.

Howard Gardner’s Theory of Multiple Intelligences

The Management Pocketbooks Pocket Correspondence Course

This is part of an extended management course. You can dip into it, or follow the course from the start. If you do that, you may want a course notebook, for the exercises and any notes you want to make.


‘How intelligent are you?’

We like to measure each other and measuring intelligence seems particularly important to some. Its practice has a long and often unpleasant history. Harvard psychologist, Howard Gardner, has done more than anybody to challenge the ‘single measure’ approach to understanding intelligence, and has introduced a more comprehensive understanding of intelligence.

Instead, Gardner proposed that a better question is:

‘How are you intelligent?’

… in what ways? He proposed that we each have a range of intelligences, which we deploy in varying strengths. Our talents derive from combinations of these intelligences.

Gardner has worked hard to define ‘intelligence’ and set criteria for which capacities to consider as intelligences. Predictably, each of these has attracted much debate. Gardner himself has settled on eight intelligences – others propose more.

Howard Gradner's Theory of Multiple Intelligences

Verbal/Linguistic Intelligence

Our ability to read, write and communicate using language, used by authors, journalists, orators, debaters and people who speak several languages.

Logical/Mathematical Intelligence

This is shown by analytical thinkers who value reason and are good at calculation; people well suited to science and engineering, the law and accountancy, economics and even detective work.

Visual/Spatial Intelligence

This makes us highly aware of spatial relationships, shape, colour and form; strong in artists, architects and designers – also navigators and cartographers.

Musical and Rhythmic Intelligence

Do you listen to, make or compose music? This intelligence makes you sensitive to tone, melody, harmony and rhythm. The term virtuoso applies to people such as singers, performers, and composers who have and deploy this intelligence to a high degree.

Bodily/Kinaesthetic Intelligence

This intelligence manifests in two ways – both linked to a precise awareness of movement, and control of our bodies.

  1. Some excel at balance and co-ordination, using their whole body with grace and power – think about sportspeople, actors and dancers.
  2. Others exercise control, but through precise use of their hands or feet, excelling in areas like sculpture, surgery, craft.

Interpersonal (Social) Intelligence

This helps us socialise and collaborate, giving an understanding of people (empathy) and helping us to put them at their ease. It accounts for confidence in making small-talk, listening intently and leading naturally. Teachers, therapists, nurses and good salespeople excel interpersonally.

Intrapersonal Intelligence

This reflects both the ability to reflect and introspect (mindfulness), and our ability to manage our own motivation, feelings and behaviour.

* For more on Interpersonal and Intrapersonal Intelligences, take a look at this Pocketblog: There’s more to Emotional Intelligence than Daniel Goleman.

Naturalist Intelligence

Stamp collectors exhibit this intelligence in a world apart from nature: they love to collect. The naturalist has affinity for the natural world, understanding how it works and often having an uncanny knack for memorising hundreds of names. If they can, they collect – rocks, insects, photos – anything. Gardeners, pet-owners, environmentalists, and scientists exercise this intelligence. So too do the people who photograph bus, train or lorry numbers.

Critique

If we each have different strengths, then the power of a team comes from its diversity and therefore the abilities of its members to apply differences intelligences to the problems they must solve and the decisions they must take.

Gardner’s work has polarised debate in some quarters of education and psychology. Some love it; it fits with their world view, making intelligence more egalitarian and recognising that there is more to learning and knowledge than literacy and numeracy. Others challenge its lack of empirical support from either well-validated testing processes or neurology.

However, many educators find plenty of support in the educational results they attain, using it to guide their teaching. For managers, this offers a powerful model of learning styles which can be applied to developing people, and a valuable way to understand why a diverse team will outperform a homogeneous one. As Gardner notes:

These intelligences are fictions – at most, useful fictions
– for discussing processes and abilities that (like all of life)
are continuous with one another.’

 Further Reading

  1. The Learner’s Pocketbook
  2. The Accelerated Learning Pocketbook
  3. Frames of Mind: Theory of Multiple Intelligences, Howard Gardner, Basic Books, 4th Edition, 2011
  4. Howard Gardner and multiple intelligences, the encyclopedia of informal education, Smith, Mark K. (2002, 2008), www.infed.org/thinkers/gardner.htm
  5. Pocketblog: There’s more to Emotional Intelligence than Daniel Goleman

Meredith Belbin’s Team Roles Model

The Management Pocketbooks Pocket Correspondence Course

This is part of an extended management course. You can dip into it, or follow the course from the start. If you do that, you may want a course notebook, for the exercises and any notes you want to make.


‘What makes a good team and how can I construct one?’

…are questions every manager, supervisor and team leader asks themselves at some stage.

They are also questions that many researchers, thinkers and management commentators have tried to answer in their own way. Two sources of particularly valuable insights that you can read about on the Pocketblog are:

However, one of the most successful researchers into team dynamics was Meredith Belbin. His work has produced a widely used and very helpful set of diagnostic and training tools, that are also reasonably priced.

No interest to declare here; I have just been a user of Belbin tools for many years, since I first encountered them on a training course in the mid 1990s. I have used the tools in my own training and find that participants get a lot from them. Find out more at www.belbin.com

Belbin’s website and books tell the story well, but here it is in a nutshell.

The Origins of the Belbin model.

Belbin and his co-workers observed a great many management teams doing standardised tasks, to try to find what might predict success or failure. Their findings included:

  1. Teams that were too small or too large were less likely to succeed. Five was a good number.
  2. In teams, people seem to play a variety of different roles.
  3. Teams where all of the roles were represented were more likely to succeed than ones with noticeable gaps. (One person could play more than one role).
  4. Teams where two or more people competed to play certain roles were less likely to succeed.

The Team Roles Model

Out of this work came Belbin’s Team Roles Model – a set of identifiable roles that the researchers saw people playing. In the initial research, eight roles emerged. Later, Belbin added a ninth role and changed some of the titles he used.

Belbin observed that we each have preferences for one or more different roles and team success comes when members contribute the full range of roles, without clashes and competition to fulfil some of them. Here are the nine roles, with the names Belbin currently assigns.

Belbin Team Roles

In the illustration of the nine team roles, we can see three families of Roles:

Socially Adept Roles

The Co-ordinator, Team Worker and Resource Investigator roles are all favoured by people with strong social instincts and require good interpersonal skills to deliver effectively. The Co-ordinator seeks the best contributions from the team, while the Team Worker promotes good working relationships, and the Resource Investigator looks outwards to a network of contacts beyond the team.

Task-focused Roles

The Shaper, Implementer and Completer Finisher roles are all strongly focused on getting the job done: the Shaper on getting it started, the Implementer on making progress, and the Completer Finisher on tying up loose ends.

More Cerebral Roles

The Plant, Monitor Evaluator and Specialist all prize thinking carefully above doing. The Plant initiates ideas, the Monitor Evaluator reviews the team’s thinking and outputs, and the Specialist contributes deep expertise.

Some Comments about the Model

My experience, and Belbin’s guidance notes, highlight many factors about this excellent model, which you can use if you buy the materials from www.belbin.com. Here are some key points:

  1. The Belbin evaluation tools are not psychometrics. They are well calibrated and developed over a long time, but they tell you about a person’s preferences now – based on their situation, experiences and how they relate to other team members. Belbin profiles shift over time.
  2. The tool is not suitable for recruitment or advancement selection – it is designed to help understand and address team dynamics.
  3. Some people have one or two strong team role preferences, others have several and are more balanced. Every conceivable profile seems to appear over time.
  4. Team members can adapt their style and therefore active profile, in response to awareness, training and support.

Further Reading 

  1. The Teamworking Pocketbook
  2. Teambuilding Activities Pocketbook
  3. The Belbin Team Roles website