/
All articles

Product

The unit is not a business service

When someone looks for a school, they meet a service at a place – not the headmaster's internal staffing unit. Keeping service, organisation and place apart makes things simpler for both residents and the organisation.

By Jens Fahlén · Published · 3 min read

A municipality running primary schools has two structures that are easily mixed up. One is the internal organisation: units, managers and cost centers that govern people, finances and the division of work. The other is what the resident encounters: a business service delivered at one or more physical places.

Problems start when the internal units are published directly as business services. The Unit building block then gets two roles that do not fit together: being the organisation's internal steering, and being what is shown to the citizen.

The school as an example

Take a municipal primary school with several hundred pupils and some eighty employees. To the resident, the school is a service: primary education at a specific address, with school choice, available places and contact details.

Internally it looks different. A school of that size has several work teams, student health services, after-school care and administration. Each part needs a manager with people responsibility, and each part needs to be followed up financially. That is a unit hierarchy – not a service catalogue.

How it usually looks: one unit, several managers

When business service and place are missing as concepts, the same pattern appears again and again: a single unit is created carrying the school's full name, because that is the name to be published to residents.

But a unit can only have one manager. To still make room for the school's actual leadership, several cost centers are attached to the unit – or several managers are attached to the associated cost center.

Both variants come from the same thing: a conceptual level is missing. And both break the chain of responsibility.

Several cost centers on the same unit make it unclear where people responsibility and financial responsibility meet. Several managers on the same cost center make it impossible to tell who the employer is – approval flows get two recipients and reporting either double-counts or leaves gaps.

The external publication also becomes fragile. Every internal reorganisation – a new work team, a new deputy headmaster – risks showing up in school choice or confusing residents, because the external name is the same object as the internal steering structure.

The sustainable model

Good solution

One unit, one cost center, one manager

1..*1Business serviceUnitCost centerManager

Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.

Explanation
Each unit has exactly one cost center and exactly one manager with people and financial responsibility. What gets published to residents is the business service, not the unit. A business service is delivered by one or more units.
Rationale
The chain of responsibility stays unambiguous: employment, responsible unit, one cost center, one manager. Approval flows, permissions and reporting always have exactly one recipient. See Pattern B.

The less good solutions

In both cases the business service is locked to the unit in a one-to-one relationship, because the unit name is what gets published.

Less good solution

Less good solution 1: several cost centers and managers under the same unit

11Business serviceUnitCost centerCost centerManagerManager

Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.

Explanation
The "Centralskolan" unit is published as the business service in a one-to-one relationship and is given two cost centers, each with its own manager, to fit the school's actual leadership under the published name.
Rationale
Splitting the finances under the same unit does not solve the underlying problem: the external face and the internal division of responsibility remain in the same unit object, and there is no way to tell who manages the unit.

Less good solution

Less good solution 2: several managers on the same cost center under the unit

11Business serviceUnitCost centerManagerManager

Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.

Explanation
The business service is still locked one-to-one to the unit. The unit has one cost center, but two managers are attached to that same cost center to make room for the school's leadership.
Rationale
Employer and approval responsibility becomes doubled: approval flows get two recipients, and reporting either double-counts or leaves gaps.

The principle

Units exist to lead and distribute work internally. Business services exist to deliver something outwards. Do not mix up who pays the salaries with what the organisation actually delivers.

Business rule VR-SRV-001 captures the same principle: a business service can be provided at zero, one or several places – but the place is linked to the service, never to the internal unit.

Tags

  • #business service
  • #unit
  • #place
  • #school

What did you think of this article?