This organizational design for a technology department aims to optimally blend the need for the technology team to be an engine of innovation, a customer-service organization and technically excellent.
It views the staff, roles and responsibilities in three dimensions: products, partnerships, and professions.
- Products and projects the technology teams work on
- Partners, customers, and stakeholders of the technology department
- Professions of the various technology staff members
Organization by products focuses on providing great user experiences via small, agile and nimble teams that have ownership of their work.
Organization by partners focuses on being an effective client-service organization to other parts of the company.
Organization by professions provides for learning, best practices and career development of the tech employees.
This article first describes the three models and then suggests ways to bring them together into one integrated organization design.
Organizing by small product focused teams
A product is defined as something that customers use and experience. A product consists of features and functionality.
It refers to a digital entity, a physical good or a combination of the physical and virtual. For example, it could be a communication app that people use via their smartphones and computers. It could be a health device that people wear and access via their smartphones and computers.
The goal of a product is to meet customer’s needs & desires, to solve problems for customers including ones they didn’t know of, and to delight them. Many products aim to help make the world a better place, be it in small or big ways.
One way to think of a product team is as a mini-company within the larger organization. A product team has customers, which could be external, internal or both.
A product team develops the product, makes it available to customers (“ships” it), and maintains the product. Maintenance of the product includes new features, major upgrades and innovations.
Roles in a product team
A product team has several roles which are filled by professionals with certain skills, knowledge and interest.
People and Roles
These roles are not necessarily each held by different people. There is no prescribed restriction on who can hold which role or how many roles. Depending on the team’s needs, people’s skills & interests, and budget & resource situation, any permutation of the roles can be held by the people in the team.
A team should make the best decisions in allocation of the roles. The roles held by people are expected to change as the team scales up or down. The team should give importance to checks and balances via separation of duties where required for compliance of regulations.
As a minimum requirement, at least three people are required for it to be a product team that encompasses a sufficient set of the roles required. In a few rare cases, the team might be able to start with just two people.
For a product team to be successfully implemented, it needs to consider and address evidence-based management science related to human collaboration.
An important recommendation is that the team “resides” together, i.e. works together on a weekly if not daily basis. If the team works out of the same office, then they should work in close proximity. If the team is geographically separated, like the teams at Auttomatic/WordPress, then they should have “virtual proximity”, i.e. be in close contact using video conferencing and other online collaboration tools.
Organizing by Partners, Customers, and Stakeholders
Aligning the technology department with business departments
In this model, each line of business, department and product/service at the company is assigned a technology partner in the technology organization.
Examples of stakeholders in a media company include the heads of advertising, marketing, finance, customer service and editorial.
The technology partner is a senior, widely-respected and influential member of the technology management team who serves as the primary technology leader for that business, department or product/service. Excellent client-relationship skills are a requirement.
The technology partner may also serve as the solutions architect for the client, or may have solutions architects assigned to them.
Technology Partner Role Description
The technology partner is the go-to person for all technology matters for the client department, including for engineering, project, and technology, areas that the technology partner does not directly manage. For example, a large department like Advertising will have projects that could span multiple tech departments.
The responsibilities of the partner include:
- Assess Current Capability: Evaluate the current technical capabilities of all the technology systems.
- Define Future Capability: Understand strategic industry trends to plan future technology roadmaps.
- Technical Lead for product development: Responsible for technology execution, bringing new products to market and optimization of existing offerings.
- Plan Capacity: Translate roadmaps into future year capacity plans.
- Collaborate with other tech teams: Work with other product teams to service the needs of the business needs / departments / products where other teams in the technology organization are the owners of systems.
- Subject Matter Expert: As the primary contact for a business / department / product act as the SME for all technology.
Organizing by Professions
In this model, the technical people are organized by the professions they choose to belong to.
Professions and Roles
This is a sample list of professions and roles gleaned from companies that have products in the digital media space. This list can be easily adapted to other industries, for example, by including the relevant subject matter expert roles. This was compiled between the years of 2007 to 2014 and reflects some prominent roles from then.
Each profession/role is grouped under one of five major categories:
- Subject Matter Expert/Analyst
List of professions/roles
Software Development Engineer, Server-side “backend” Software Engineer, Client-side “frontend” Software Engineer, Mobile iPhone and Tablet Software Engineer, iOS Software Engineer, Android Software Engineer, Content Management (CMS) Engineer, Testing Engineer, App Release Engineer, App Operations Engineer, DevOps Engineer, Systems Administrator, Database Administrator, Security/Privacy & Compliance Analyst
User Experience Designer, Visual Designer
Subject Matter Expert/Analyst
Product Manager, Business Analyst, Journalist, Reporter/Content Author, Editor
Salesperson, Marketer, Customer Service Representative, Internal Advocate, Documentation Writer
Project Manager, Finances & Budget Manager, Team & People Manager
Integrating the three dimensions
Now that we have described the three dimensions, let us discuss ways to make it all work together.
Some people believe that “reporting relationships are irrelevant in today’s world”, but social science research has repeatedly proven this to be false*. Reporting structures and hierarchies are an essential and integral part of any organization of humans.
So rather than pretend that reporting relationships in a team don’t matter, it is important to address them in setting up these teams.
Let us start by acknowledging that human relationships are complex, nuanced and changing, so there is no one formula to organize your teams. Every approach to organizing reporting relationships has its advantages and drawbacks. Here, we present a reasonable but imperfect model.
This model applies to medium to large size organizations, but not to small companies or very-large companies. In a small company of less than 10 people, there are unlikely to be departments by profession where people report into. In very large companies’ each business unit may operate as an independent company with its own departments by profession (e.g. their own finance, HR and engineering).
We also make some assumptions. For example, that it is preferable that each team member has exactly one primary boss who they formally report to*.
Departments by Profession
It is important to define what is expected of a primary boss in your organization so you can best determine how to structure reporting relationships. For example:
- Does a boss’ role include the long-term development of the employee’s career, existing skills and new skills?
- Does a boss need to be a subject matter expert in the chosen profession of the employee? Or, is the employee best served by being part of a team of others with the same or similar professions?
- Does a boss need to objectively and independently look at the employee’s work as serve as a checks and balances relative to the product/project team the employee is presently doing day to day work in?
If your answer to the above questions is yes, then it is likely that setting up the primary reporting relationships by profession is a good solution for you.
What does reporting relationships by profession mean? It means that primary (and formal) reporting relationships are organized by departments of people in similar professions. For example, HR professionals report into the HR department, finance professionals report into the finance department and software engineering professionals report into the software engineering department.
In medium to large sized companies, having the primary reporting relationship by professional departments often has advantages over having direct reporting into the product/project team. In fact, most consulting firms use this model. Some of the benefits include:
- As new products are created, old products decommissioned and projects start and end, employees don’t need to switch from boss to boss. By having a boss who has seen an employee’s work over multiple products, services and projects, the employee can receive better coaching and development support.
- A boss who manages a team of employees of the same profession helps share best practices, standards and development opportunities across the organization.
- Such a boss can also serve as a check and balance for a product/project team’s short-term needs vs. the best long-term interests of the company. The employee has a primary person higher up to consult with outside their current product/project team.
Most medium to large size companies have departments by profession. For example, they have departments for finance, HR, sales, marketing, software engineering, design, etc. This makes good sense for reasons like the above.
Such departments often assign (or even embed) their professionals within other departments and product/project teams. For example, finance (or HR) may assign a finance person or team (or HR person or team) to work with the technology department. This person would likely be assigned full time to the technology department and work in close proximity to a part of it.
The organizational model recommended here views technology as a collection of departments by technical professions. For example, software development, quality assurance and testing, infrastructure engineering, and project management. Each of these technology departments embeds their staff into product/project teams.
The overall technology department also assigns a technology partner to every other department by profession. That’s how these three dimensions come together.
Balancing Professional Departments with Product/Project Teams
In setting up direct reporting relationships by professional departments, it is critically important to not let the departments become siloed. Each employee should be focused on, deeply care about and feel accountable to the product/project they are working on.
When the person’s primary boss is a functional head outside the team they are currently doing day to day work in, both the employee and the boss must ensure the employee is highly committed to their product/project team whether it is in their department or outside it. One way to accomplish this: Each employee can also be accountable to a lead within the product/project team via a dotted line if needed. In some cases, the employee’s boss and their lead within the team can be the same person.
The goal of the functional department is to both support product/project teams and serve as checks and balances, but never to work against them.
While this article was written for organizing technology departments at companies where a substantial amount of work involves software engineering, the thinking here might be adaptable to other types of departments. If you have thoughts on how to do that or have other approaches to organizing teams in organizations, please do share them.