Show Summary Details
Page of

(p. 263) Learning at work: Toward a learning stance in teams 

(p. 263) Learning at work: Toward a learning stance in teams
(p. 263) Learning at work: Toward a learning stance in teams

Dickon Bevington

, Peter Fuggle

, Liz Cracknell

, and Peter Fonagy

Page of

PRINTED FROM OXFORD CLINICAL PSYCHOLOGY ONLINE ( © Oxford University Press, 2021. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Clinical Psychology Online for personal use (for details see Privacy Policy and Legal Notice).

date: 17 April 2021

Team learning, the focus of the fourth quadrant of the AMBIT wheel, is justified by strong evidence about the weak translation of evidence-based trainings into practice fidelity, and weak clinical outcomes from even the most powerfully evidenced practices. The need for strong leadership (and what this entails) to support development of a learning organization is described. Research findings on quality improvements and outcomes in health and social care settings lead to a framework of AMBIT competencies. The notion of local team “manualization” is introduced; this is the systematic effort of a team over time to reflect upon and record (mentalize) how the team works, and why. Discussion of treatment manuals and (as the AMBIT stance presents it) the tension between “Respect for evidence” and “Respect for local practice and expertise” lead to notions of co-construction. Technical aspects of AMBIT’s wiki manual are described, along with how these aspects support a community of practice and mirror “open-source” IT developments.

Access to the complete content on Oxford Clinical Psychology requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.