/
← Back to the Academy

Module 2

The organisation tree and the manager's VEP responsibility

The organisation tree as backbone, and how the manager's operational, financial and personnel responsibility is affected by one or several trees.

Lessons

1. One tree as the backbone

The organisation tree describes how the organisation is divided into units. It is the structure that permissions, approval flows, reporting and communication rely on. Organisation and manager are created in exactly one process and one system.

Management is a relationship between employee and unit, expressed by a manager code – not a title. Deputies are not managers; budget responsibility follows the manager and can be delegated as a process role.

2. VEP – the manager's three responsibilities

A manager holds operational (V), financial (E) and personnel (P) responsibility for their unit. All three assume that operational, finance and HR systems see the same unit and the same manager.

  • One shared tree: approval, budget and personnel responsibility point to the same unit. Follow-up matches and automated flows work.
  • Several parallel trees: the HR unit and cost centre differ. The manager approves costs for staff they have no personnel responsibility for.
  • Shadow trees cause reconciliation work, broken approval chains and employees invisible to the right manager.

3. When several trees are needed

There may be reasons to view the organisation from several perspectives, such as financial follow-up. They should then be derived from the same foundation through rules – not maintained manually in each system.

A derived perspective updates automatically when the base tree changes. A manually maintained tree starts drifting at the very first reorganisation.

Example

Finance wants to follow up three wards as one result area. Instead of a separate tree in the finance system, the units are tagged with result area in the base tree, and reporting groups by that attribute.

4. Reorganisation and history

Organisations change constantly. Units merge, split and change managers. Every change needs an effective date so systems can prepare and history is preserved.

When the change is made in one place and propagated to all subscribing systems, employees, permissions and approval chains move together. When made system by system, gaps arise where nobody – or two people – are manager.

  • Plan the change ahead with a future effective date.
  • Let units be closed rather than deleted.
  • Check that every active unit has exactly one manager.

Key takeaway: One change, one source, one date – all systems follow.

Knowledge check

1. What does VEP stand for?
2. The HR and finance systems have different unit structures. Which effect is most likely?
3. How is management expressed in the library?
4. In how many processes and systems are organisation and manager created?
5. Finance needs its own follow-up perspective. What is right?