Posts about teams

Management Improvement Carnival #137

photo of Petronas Towers in Kuala Lumpur, Malaysia.

Petronas Towers, Kuala Lumpur, Malaysia by John Hunter. View from my hotel room.

The Curious Cat management blog carnival is published 3 times a month with select recent management blog posts. I also collect management improvement articles through Curious Cat Management Articles, you can subscribe via RSS to new article additions. Photo is the view I see as I post this issue of the carnival.

  • The importance of understanding variation or how to avoid treating all contractors as thieves by Benjamin Mitchell – “The fix for common cause variation (and most variation is common cause) is to go and study the situation, experiment and try and look for patterns or trends in the data before making a change to the system.”
  • Deming’s 14 Points by David Joyce – “The 14 points are not a menu you can pick and choose from. Deming intended you use all 14. They are one philosophy.”
  • Misconceptions about Self-Organizing Teams by Esther Derby – “Like all teams, they need a compelling goal, skills, information, and enough time to form and perform. And they still need managers to create a supportive context, set appropriate boundaries and constraints and connect the team to the organization.”
  • New York City Halts Teacher Bonus Program: Another Blow to Evidence-Resistant Ideology by Bob Sutton – “The decision was made in light of a study that found the bonuses had no positive effect on either student performance or teachers’ attitudes toward their jobs.”
  • Agile Prioritisation by Mike Griffiths – “There is no single best way to always prioritise; instead, try to diagnose issues arising in the prioritisation process, be it “lack of involvement” or “too many priority 1’s”, and then try approaches such as Monopoly money, MoSCoW or a pure list to assist if the problems cannot be resolved via dialogue. The goal is to understand where features lie in relation to others as opposed to assigning a category label.”
  • Continue reading

Why Lean is Different


Why Lean is different by Operae_Partners

Short webcast by Michael Ballé discusses what makes lean manufacturing different: going to where the work is done, standardize processes (from the gemba view), practice respect for people and continually improve. Lean thinking focuses on achieving better results and through that process improves trust and teamwork internally, as well as better supplier and customer relationships.

Related: Non-technical Control Chart WebcastMihaly Csikszentmihalyi: Creativity, Fulfillment and Flowlean management, books, articles…

Stop Starting and Start Finishing – Jason Yip

Jason Yip explores the value of reducing work in process and reducing context switching costs to optimize throughput. By designing processes to work on projects serially instead of in parallel we reduce context switching, and other costs, of multitasking.

Related: Multi-Tasking: Why Projects Take so LongThe Importance of Making Problems VisibleOne piece flow (continuous flow)Kanban

The Power of Small Teams

The power of small teams by Avi Muchnick

Choose a project that is simple to implement. Don’t try to create a complex suite of applications… Focus on solving a single problem. Philip Kaplan made email more efficient to use by stalling it instead of managing it. Dead simple approach and a great idea.Take the easier approach when possible.

Choose people that can wear multiple hats. Can your designer code? Can your programmer manage a community? Can your marketing guru fund raise? Can one guy do it all?

All documentation should be available via a central location. A wiki can work really well for this purpose. Good documentation lessens the loss from communication failures.

Arrange your workspace in common areas. Segregating your team in different offices is a recipe for lost communication data and with it, a need for additional people. You’d be surprised at how many roles can be shared by multiple people, so long as they have the ability to communicate instantly and unimpeded with each other. Put people between walls, and those shared tasks will need to be managed by additional team members.

Amazon and Google do a lot with small teams and I think they have it right. I have worked on small IT teams for several years now and find it great. Combine with agile management methods small teams allow for great focus (you are naturally guided toward appropriate project sizes instead of huge monster projects), great results and joy in work. I have no desire to work in large teams.

Related: Team HandbookMeasuring and Managing Performance in OrganizationsKeeping Track of Improvement OpportunitiesCurious Cat Management Articles

The Power of Teams

The Power of Teams, by Lynn Witten (broken link removed):

>Train team leaders and members. It is critical to provide training and guidance to people on how to function as effective team members and leaders. In addition, problem-solving training can give teams and team leaders a structured approach to finding solutions. It can help teams overcome members’ natural defensiveness and finger-pointing.

Evaluate incentive systems. Many incentive systems have been established to reward individual effort or effort from one functional area. In team-based systems, rewards need to recognize the impact of a team’s performance on the whole system.

  • Recent Trackbacks

  • Comments