Blog
Articles on information patterns, information modelling and comparisons between good and less good solutions.

Good solutions
When a flow becomes master data – a line of reasoning
Master data never appears out of nowhere – it is born in a transaction. Here we examine the moment when an ordinary information flow becomes a state the whole organisation depends on.
· 3 min read
Read more
Good solutions
Stop cleaning data in a hub – hold a mirror up to your source systems
Many organisations spend large sums on MDM hubs that quietly correct faulty details. But when the hub cleans the data, the source systems stay wrong and responsibility disappears. Quality only improves when the people entering the details see which business rules were broken and who should fix the error.
· 4 min read
Read more
Less good solutions
It is not technical debt – it is information debt
When integrations stall and automation fails due to constant exceptions, we almost always blame technical debt and legacy systems. But the real bottleneck is rarely the code. It is information debt – and brand-new, modern cloud applications become part of it the moment they launch with their own isolated data models.
· 3 min read
Read more
Less good solutions
When the key person leaves and nobody dares touch the code
When critical logic lives only in one person's head, that person becomes a Single Point of Failure. How to remove the dependency with open rules, standards and processes that work manually.
· 4 min read
Read more
Organisation
Occupations and occupation groups – a fragmented starting point
Three external lists group occupations in different ways, and support and governance lack common code lists. That makes statistics uncertain and automation hard.
· 2 min read
Read more
Organisation
AI doesn't fix flawed foundations – why automation and AI require the same structure
AI, automation and interoperability require the same orderly foundation. Language models guess when systems disagree.
· 2 min read
Read moreEmployee 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.
Good solutions
A consistent user interface starts in the data model – not in the CSS
Matching colours and buttons are not enough to make an interface consistent. Users also need to find the same terms, information and responsibilities across services.
· 3 min read
Read moreGood solutions
The right tool for the right person – How the application catalogue and the organisation tree together create secure, automated assignment
When the application catalogue and the organisation tree are linked through process roles, assigning tools, licences and access becomes automatic. Nobody needs to copy a colleague's access, the right manager approves and the assignment is removed when someone moves or leaves.
· 3 min read
Read more
Good solutions
The backbone of the IT landscape – why the organisation tree and VEP decide everything
When the digital organisation tree and management (VEP) work as authoritative master data, they solve problems in every IT system. But it also requires managers to have a reasonable span of control – otherwise digitalisation is eaten up by shadow roles and administration.
· 4 min read
Read more
Good solutions
When frameworks meet reality – why DMBOK needs blueprints
DAMA-DMBOK describes what data management needs to cover. To use it in everyday work, an organisation also needs to decide how information, responsibilities and systems fit together.
· 4 min read
Read moreEmployee 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.
Good solutions
The tool that couldn't create agreement
Why master data is fundamentally a conversation, not software – and why it is human to start at the wrong end.
· 2 min read
Read more
Good solutions
The price of autonomy
Different services sometimes need different rules. But old system requirements and local working practices can make it difficult to share information and automate work.
· 2 min read
Read moreEmployee 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.
Organisation
One organisation – one unit structure
Many public organisations assume the organisational structure lives either in the finance system or in the HR system. The result is two versions of reality that do not match.
· 6 min read
Read moreProduct
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.
· 3 min read
Read moreEmployee 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.
Organisation
When the unit hierarchy and management hierarchy follow the same structure
An organisational structure is more than a picture of who reports to whom. When the structure is used as information across multiple systems, it needs to be consistent, predictable and governed by clear business rules.
· 6 min read
Read moreEmployee 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.
Good solutions
One manager – one responsibility
Employment points to a unit or cost center. When that responsibility is shared, employer responsibility turns ambiguous – and IT support unusable.
· 2 min read
Read more