{"id":1431,"date":"2025-12-16T08:45:04","date_gmt":"2025-12-16T08:45:04","guid":{"rendered":"https:\/\/dbvp.nl\/?page_id=1431"},"modified":"2026-03-18T10:49:42","modified_gmt":"2026-03-18T10:49:42","slug":"teamsamenwerken","status":"publish","type":"page","link":"https:\/\/dbvp.nl\/en\/expertise\/teamsamenwerken\/","title":{"rendered":"Team en samenwerken"},"content":{"rendered":"
\n
\"\"<\/span>
\n

Team Ontwikkeling<\/h2>\n<\/div><\/div>\n\n\n\n
<\/div>\n\n\n\n

Team development is about how a group of professionals learns to truly work together \u2014 not only in terms of tasks, but also relationally and reflectively.\nIn this theme, we approach teams and teaming as a psychodynamic and digital phenomenon: what is visible in meetings, decision-making, and results is always connected to what is happening in the undercurrent and to the ways AI systems co-organise the work.<\/p>\n\n\n\n

A psychodynamic perspective means recognising how unconscious patterns co-determine decisions.\nWho automatically steps into the role of rescuer, critic, or mediator?\nWho withdraws as soon as things become tense?\nWhich topics remain neatly out of view?\nBehind such patterns often lie earlier experiences with leadership, organisations, or failure, which are replayed within the team.\nConflicts, silences, or subtle power games are then not disturbances, but information: here the team touches something it does not (yet) dare to feel or discuss.<\/p>\n\n\n\n

At the same time, teams increasingly operate in a field where AI co-determines information, rhythms, and choices.\nAccess to data and tools becomes influence.\nDashboards steer attention.\nAI suggests solutions and priorities, and may even appear to offer judgements or scores.\nTeaming thus also becomes learning to collaborate with technology \u2014 and to remain critical of the assumptions embedded within it.<\/p>\n\n\n\n

Team development in a HUMAN\u2013AI context therefore requires teams to build sufficient safety to tolerate and discuss tension, uncertainty, and difference.\nTo make their unspoken rules explicit \u2014 including the rules around data and tools (\u201chere we trust the system, here we don\u2019t\u201d).\nAnd to consciously design how team and AI complement each other: what belongs to human judgement, what can be delegated to systems, and who ultimately remains responsible.<\/p>\n\n\n\n

This theme invites teams to see themselves and their digital environment as a single whole.\nTeam development then becomes transformation from the inside out: recognising patterns, creating role clarity, and using AI in ways that strengthen craftsmanship, responsibility, and trust.<\/p>\n\n\n\n

Intervention<\/strong><\/p>\n\n\n\n

DBVP views team development as more than \u201cbetter collaboration\u201d or \u201cclear agreements.\u201d\nA team is a living system in which task, relationships, history, power, and technology continuously influence one another.\nTeam development is therefore, for us, simultaneously a psychodynamic, systemic, and HUMAN\u2013AI challenge.<\/p>\n\n\n\n

Psychodynamically, we work with the undercurrent present in every team: who naturally becomes the spokesperson, who takes care, who explains everything away, who disengages, who subtly sabotages?\nBehind these movements often lie earlier experiences of rejection, success, failure, or lack of safety.\nWe do not see cynicism, jokes \u201cabout nothing,\u201d sluggishness, or conflict as disturbances, but as signals.\nWe work with the tension rather than around it, because that is precisely where the learning potential lies.<\/p>\n\n\n\n

Systemically, we never consider the team in isolation from its context.\nIts position in the organisation, the task, the mandate, and the dependencies shape the dynamics.\nWe therefore look at role clarity and decision-making, at the connection with other teams, and at the relationship with leadership and governance.\nWe intervene not only on behaviour, but on coherence: is the task right, does the composition fit, are boundaries clear, and is it evident who is truly responsible for what?<\/p>\n\n\n\n

We add HUMAN\u2013AI as a socio-technical reality.\nMuch team work is driven by data, systems, and AI tools: planning, dashboards, analyses, risk models.\nThose who have access to which information effectively gain more influence \u2014 and the system often determines the pace and focus.\nWe examine how technology shapes role distribution and attention.\nWe use AI both as a tool to clarify patterns and scenarios and as a mirror: what do your tools say about what is considered important in this team?<\/p>\n\n\n\n

How we intervene is consistent.\nWe start from the team\u2019s task: what are you here for, within the larger whole?\nWe then work with concrete cases where tension is present \u2014 real decisions, real mistakes, real friction \u2014 so that development does not become abstract.\nWe connect work and learning moments: the practice field is the daily work itself.\nWe create a holding environment that is safe enough for honesty and sharp enough not to stay away from what is painful.\nAnd we continually place ownership back where it belongs: with the team; DBVP is a guide, mirror, and challenger.\nIn this way, team development becomes not \u201ca nice day together,\u201d but a process of transformation from the inside out, visible in task maturity, mutual honesty, and mature engagement with AI and systems.<\/p>\n\n\n\n

Methodological considerations<\/strong><\/p>\n\n\n\n

At DBVP, we see team development as working with a living system of task, relationships, history, and technology.\nThe starting point is always the task: without a shared purpose, \u201ccollaboration\u201d quickly becomes an empty container.\nWe work from transformation from the inside out: patterns only change sustainably when emotions, loyalties, roles, and structure are all brought into view.\nPsychodynamically, we look at the undercurrent \u2014 who carries tension, who rescues, who fights, who freezes \u2014 and treat conflict and silence as information.\nSystemically, we examine position and context: task, mandate, boundaries, dependencies, and the relationship with leadership and other teams.\nAnd we explicitly include AI and systems as part of the team field: dashboards and tools partly determine who has influence, what appears to be \u201ctrue,\u201d and which pace becomes leading.<\/p>\n\n\n\n

Typical methods and techniques<\/strong><\/p>\n\n\n\n

We begin where the team already is: in the work.\nWe observe regular meetings and reflect back what happens, including what is not being said.\nWe work with concrete cases \u2014 decisions, mistakes, complaints, successes \u2014 and make visible how role patterns form in real time: who speaks, who remains silent, who names the unnameable, who diverts attention away from tension.<\/p>\n\n\n\n

We then make the undercurrent explicit and workable.\nWe normalise themes such as trust, shame, guilt, rivalry, and loyalty as part of team dynamics, and explore recurring reflexes: avoiding, rescuing, fighting, escalating complaints upward, becoming cynical.\nTeams practise \u201clistening beneath the words\u201d: what is being avoided, and what price does the team pay for that?<\/p>\n\n\n\n

We then bring in systemic ordering and role clarity.\nWe clarify the team\u2019s task, mandate, and boundaries within the organisation, and work out who is truly responsible for what \u2014 making implicit expectations explicit.\nOften, the biggest breakthroughs lie in small structural interventions: who attends which meetings, how decisions are made, which escalation routes are legitimate, and where the real dependencies lie.<\/p>\n\n\n\n

In parallel, we carry out HUMAN\u2013AI\u2013specific interventions.\nWe facilitate team conversations about systems: which data steer us, what are we missing, who sees which information, and what does that do to influence and recognition?\nWe examine situations in which AI or system outputs clash with professional or moral judgement, and make explicit how the team wants to shape the human\u2013system division of tasks: what do we consciously keep with ourselves, and how do we safeguard responsibility?<\/p>\n\n\n\n

Finally, we embed learning in the line through short learning loops.\nAfter significant moments \u2014 crisis, escalation, success \u2014 we facilitate immediate reflection, so insights do not evaporate.\nWe practise tension-filled conversations in the real work, not only in role play.\nAnd we involve the leader as part of the team field: not as an external \u201cboss,\u201d but as an actor who co-shapes the system.<\/p>\n\n\n\n

Throughout, the principle holds: DBVP brings framework, sharpness, and safety; the team brings itself, with all its friction and potential.\nTeam development thus becomes an ongoing process of looking together, choosing together, and practising together \u2014 visible in task maturity, mutual honesty, and mature engagement with AI.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

Teamontwikkeling gaat over hoe een groep professionals leert om werkelijk samen te werken\u2014niet alleen taakmatig, maar ook relationeel en reflectief. In dit thema benaderen we teams en teaming als een psychodynamisch \u00e9n digitaal fenomeen: wat zichtbaar gebeurt in overleg, besluitvorming en resultaat, staat altijd in verbinding met wat er in de onderstroom speelt \u00e9n met […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":772,"menu_order":4,"comment_status":"closed","ping_status":"closed","template":"page-full-width","meta":{"footnotes":""},"class_list":["post-1431","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/pages\/1431","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/comments?post=1431"}],"version-history":[{"count":2,"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/pages\/1431\/revisions"}],"predecessor-version":[{"id":2077,"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/pages\/1431\/revisions\/2077"}],"up":[{"embeddable":true,"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/pages\/772"}],"wp:attachment":[{"href":"https:\/\/dbvp.nl\/en\/wp-json\/wp\/v2\/media?parent=1431"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}