#Organizational Design

As a developer experience team, we are often working in a platform mode but are constantly shifting into enabling mode for better results.

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.

Great developer experience is directly linked to great developer productivity and an important factor for company success. This article starts to answer the question how great developer experience can be achieved.

Code ownership on a team-level can not only help to identify the team that has knowledge in a certain area, it also can serve as a signal for a mismatch between architecture and team structures.

Code ownership is an important topic when it comes to enabling your teams and allowing developers to improve the system while keeping the overhead of changes low. While today, most companies would (hopefully) agree, that individual code ownership is bad because it creates knowledge silos and makes the organisation dependent on individuals, code ownership still is essential on a larger scale.

Developer experience is a crucial topic which affects all development teams of a company. Therefore, it can be beneficial to introduce a team that has as their only mission to improve developer experience and productivity as these improvements multiply the impact of the other teams.

Whether a team works synchronous or asynchronous is not determined by whether it is co-located or not. Both teams have to make an effort, if they want their work to be synchronous.

Objectives and key results are a great tool for collaborative goal-setting and for aligned on a company-wide direction. Problems start, when teams start to rely on other teams OKRs to be finished in time.

Bonuses shift an employee's interest from the long-term success of the company to the achievement of a short-term goal. By introducing bonuses, you are incentivising the achievement of goals, that should not need any incentives, if they were the right goals to begin with.

Keeping people 100% busy will prevent them from innovating and improving. Therefore, teams should have slack that enables the to learn, adapt and improve.