Talk:Teamwork

Merge to Team building: yes or no?

The merge tag's been up there forever. Decide.

• No merge. Different concepts

* No merge - you build a team and get the staff to be team players. Building a team is using strategies and plans to convince people to work and gel together - but team player is a culture that staff are encouraged to be a part of and engage in so that they work as a team.

untitled (and odd) comments

Team player - a phrase or ethos that means you can get staff to do anything you want in return for a few very small concessions (like you or staff being able to leave 2 minutes before your shift in the office is finished because the computer clock is different from the phone clock and well...it's only 2 minutes right?).

Stop being a team player and...they point out that stuff, call the situation sad, say how upset and disappointed they are that you are not being a team player, not one of the group...

Whoever came up with team player needs to have their head examined.

It works in theory - but only in theory and only if all the people involved are of the same mind set or whatever.

I think you need to consider the effects of team building on a team? Does it even effect them? You can't merge them until you assess this! Coldelephant 0902 (GMT) 03 November 2006

Wiki Education assignment: Project Team Management

This article was the subject of a Wiki Education Foundation-supported course assignment, between 1 September 2024 and 5 December 2024. Further details are available on the course page. Student editor(s): Flerime (article contribs).

— Assignment last updated by JonKush (talk) 15:51, 12 November 2024 (UTC)

New subsection: Psychological barriers to teamwork

I have added a new subsection, "Psychological barriers to teamwork", summarizing several published models on psychological barriers to effective teamwork (Steiner 1972, Edmondson 1999, Lencioni 2005, Scouller 2024). The aim is to complement the existing "Effective teamwork characteristics" and "Basic team dynamics" subsections by explaining psychological factors that can hinder teamwork and team performance.

Comments and suggestions for improvement are welcome. — Preceding unsigned comment added by Tens49 (talk • contribs) 17:08, 24 March 2026 (UTC)

NicheSports Thanks for the edit and edit summary. I appreciate the concern about UNDUE coverage of corporate‑oriented frameworks in a broad article like this, and I am not planning to restore the full section as it stood.

Just to clarify one point: I wrote the removed text directly from the cited sources. I did not use a large language model to generate it. I am aware of the draft “Writing articles with large language models” guidance, which advises against using LLMs to generate article content and notes that similarity of style alone is not sufficient evidence of LLM use, and I am happy to work within that emerging norm.

On reflection, I agree that a long, model‑heavy section is too much for this article. As a more modest alternative, I propose adding a very short “Psychological barriers” paragraph that briefly mentions one or two well‑established ideas (Steiner’s process loss and Edmondson’s psychological safety).

Draft replacement wording:

“Researchers in social and organizational psychology have highlighted psychological factors that can limit teamwork. Steiner’s process loss theory suggests that group performance is often lower than the combined potential of individual members because of motivation losses (such as social loafing) and coordination difficulties. Edmondson’s work on psychological safety emphasises that teams function better when members feel able to speak up, admit mistakes and share ideas without fear of embarrassment or punishment.”

I’d welcome views on adding something along these lines, and I’m happy to adjust wording or scope to better fit the article’s coverage.Tens49 (talk) 19:22, 28 March 2026 (UTC)