Back to resources

Introduction of a Matrix-Based Organizational Model in a Software House

Innovation / Experiment
Motivation
Performance

9 December, 2021

Jan Pieczykolan
Jan Pieczykolan

Head of IT Development at Santander Bank Polska

Jan Pieczykolan, Software Engineering Director, shares his experience changing the organizational model to matrix-based resource pool one.

Problem

Companies use multiple organizational models. One of them is a silo-based organization in which each department is a sort of a silo that manages its projects and sometimes uses some of the services offered by the company – for instance, HR, IT, etc. Usually, such a department has its P&L, and its autonomy is relatively high. As long as profits are higher than costs and margin is on the expected level, everything is fine.

The division of a company lost several contracts simultaneously; therefore, several departments grouped within this division started to lose their profitability. The situation was specific as none of the departments lost all warranties, but all were impacted. None of them could survive on its own, therefore merging was an option to recover profitability on a macro scale, on the division level.

Actions taken

We reviewed our profits and costs – to understand expected revenues and determine how much FTE we could afford.

We went through our employee list to identify those we had to keep and those we had to let go of.

We understood that we would have to prepare a flexible, matrix-based organization in the short time horizon. Our solution grouped all engineers and project managers in a single cost center while projects were grouped in programs, and programs were aggregated in separate organizational units. Those organizational units were super lean – they consisted only of a Program Director, who was responsible for a profit from a specific contract or a specific customer.

Program Directors could hire project managers and engineers only for a specific project ordered by a customer. As soon as the engagement was finished, those people were available for other initiatives. Sometimes a person could be shared by more than one project – especially in the case of small projects or maintenance contracts (maintenance contract was a project as well). We were allowing overbooking, at least to a certain level.

After some time, when Program Directors stabilized their profit centers, they started to build their own organizations as they had guaranteed income. Therefore, they were able to afford permanent hiring of employees.

Lessons learned

  • Silo organizations are often non-transparent ones.
  • Engineers can be shared by more than a project only for a limited amount of time – focus switching is usually too difficult to handle for a longer time.
  • In matrix organizations, people usually have a problem identifying who their manager is and who influences their salary and bonus.
  • Performance review in a matrix organization is complex and requires unambiguous criteria to be conducted fairly.
  • It is challenging to build innovation in matrix-based organizations.
  • It is essential to define clear responsibilities between a line manager and a project manager who engages an engineer in a project. Lack of this clear distinction will lead to conflicts and demotivation of the staff.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

From Big Tech to Startup: Adding Value From Day 1

19 January

Angel Jamie, Chief Product Officer at Yayzy, recalls his transition from a well-established tech company to a sustainability startup, and the major differences he experienced.

Dev Processes
Company Culture
Impact
Team Processes
Cross-Functional Collaboration
Changing Company
Career Path
Performance
Angel Jaime

Angel Jaime

CPO at yayzy

Should You Stay Up to Date with Technical Skills As a Product Manager?

19 January

Nani Nitinavakorn, the Sr Product Owner at Revolut, describes how she keeps learning hard skills to increase motivation and respect her team.

Alignment
Innovation / Experiment
Different Skillsets
Personal Growth
Ownership
Coaching / Training / Mentorship
New PM
New Manager
Nani Nitinavakorn

Nani Nitinavakorn

Sr Product Owner at Revolut

How to Spark Sales-Driven Change

19 January

Nani Nitinavakorn, Sr Product Owner at Revolut, recalls her experience initiating a structural change to optimize her entire company.

Customers
Innovation / Experiment
Leadership
Meetings
Impact
Users
Nani Nitinavakorn

Nani Nitinavakorn

Sr Product Owner at Revolut

Strategies to Deliver Effective Employee Feedback

18 January

Rachit Lohani, Head of Engineering at Atlassian, shares all his ideas and principles on providing feedback and avoiding discomfort while doing so.

Leadership
Internal Communication
Feedback
Motivation
Strategy
Team Processes
Rachit Lohani

Rachit Lohani

Head of Engineering at Atlassian

Understanding Career Growth: Promotion and Sideways Career Changes

19 January

Mike Bassett, Senior Director of Engineering at Electronic Arts, shares his journey through the career ladder, highlighting evaluation steps to ensure high motivation.

Personal Growth
Leadership
Motivation
Career Path
Mike Bassett

Mike Bassett

Senior Director of Engineering at Electronic Arts (EA)

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.