# Team-Topologies, Developer-Productivity, Organizational-Design

Published articles for Team-Topologies, Developer-Productivity, Organizational-Design.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Interaction modes of a developer experience team

DevFeed: [Interaction modes of a developer experience team](<https://devfeed.tech/articles/interaction-modes-of-a-developer-experience-team-39898.md>)

Original publisher: [Read original article](<https://mende.io/blog/developer-experience-team-interaction-modes/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2022-03-26T13:10:00Z

Content type: opinion

Language: en

Sources: [Tobias Mende](<https://devfeed.tech/sources/tobias-mende.md>)

Topics: [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Development](<https://devfeed.tech/topics/development.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>)

Tags: [developer](<https://devfeed.tech/tags/developer.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [development](<https://devfeed.tech/tags/development.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [platform](<https://devfeed.tech/tags/platform.md>), [team-topologies-developer-productivity-organizational-design](<https://devfeed.tech/tags/team-topologies-developer-productivity-organizational-design.md>), [usability](<https://devfeed.tech/tags/usability.md>)

### AI overview

This article explains how a developer experience team interacts with other software development teams. It describes the team's platform role in providing tools, services, components, and documentation, while also emphasizing an enabling mode that works directly with teams to support technology adoption. It identifies usability, findability, and credibility as three pillars of the team's offering.

### Source excerpt

Interaction modes of a developer experience team In my last article, I wrote about how we shaped our developer experience team and why we decided for this team constellation. In this article, I will focus on how this team interacts with the other software development teams and which aspects are particularly important.

## Shaping developer experience teams for autonomy

DevFeed: [Shaping developer experience teams for autonomy](<https://devfeed.tech/articles/shaping-developer-experience-teams-for-autonomy-39899.md>)

Original publisher: [Read original article](<https://mende.io/blog/developer-experience-team-shape/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2022-03-19T13:08:00Z

Content type: article

Language: en

Sources: [Tobias Mende](<https://devfeed.tech/sources/tobias-mende.md>)

Topics: [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [code productivity](<https://devfeed.tech/topics/code-productivity.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>)

Tags: [autonomy](<https://devfeed.tech/tags/autonomy.md>), [backend](<https://devfeed.tech/tags/backend.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [team-topologies-developer-productivity-organizational-design](<https://devfeed.tech/tags/team-topologies-developer-productivity-organizational-design.md>), [teams](<https://devfeed.tech/tags/teams.md>), [tech-leadership](<https://devfeed.tech/tags/tech-leadership.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

This article discusses how to structure a developer experience team for autonomy and independence. Drawing on BRYTER's experience, it argues for a cross-functional team that can address frontend, backend, tooling, continuous integration, deployment, and monitoring concerns, with specialists covering different technical areas.

### Source excerpt

Shaping developer experience teams for autonomy Once you have decided, that a developer experience team would provide value to your organisation, the question is, how such a team should be set up, how it should be shaped, and how it should interact with other teams.