Organisations need accountability.
- Someone needs to make decisions.
- Someone needs the authority to act.
- Someone needs to own the outcome when something goes wrong.
But as organisations and their technologies have become more complex, accountability has often become intertwined with visibility.
More people are copied into decisions.
- More information is shared.
- More systems are connected.
- More stakeholders are given access, just in case they need it.
The intention is usually sensible:
If everyone who might be accountable can see what is happening, the organisation should be better controlled.
But there is another possibility.
What if clearer boundaries, rather than greater visibility, created stronger accountability?
When access becomes a substitute for clarity
Consider how easily responsibility can spread across an organisation.
- A process crosses several teams.
- Data passes between systems.
- Multiple people have access.
- Several functions provide oversight.
Eventually, everyone can see something, yet determining precisely who has the authority to do what can become increasingly complicated.
That raises a leadership question:
Are we giving people information because they genuinely need it to fulfil their responsibility, or because our responsibilities are not sufficiently well defined?
Those are very different problems.
Accountability needs boundaries
Imagine an organisational model where responsibility is explicitly connected to the thing for which someone is accountable.
A person does not need unlimited visibility merely because that person performs a particular role.
The role requires the appropriate authority for a defined purpose.
The principle becomes:
Enough authority to fulfil the responsibility.
Enough information to establish what matters.
Clear boundaries around everything else.
Accountability becomes more precise because responsibility and permission remain aligned.
For a greenfield organisation
A new organisation can establish these boundaries before broad access becomes normal.
Instead of starting with:
Who needs access to this system?
leadership can ask:
What is this role responsible for, and what authority is actually required to fulfil that responsibility?
That reverses the design problem.
Access stops being something granted broadly and subsequently controlled.
It becomes a consequence of responsibility.
This could produce very different approaches to governance, decision rights, organisational design and technology.
For existing organisations
Established enterprises inevitably have more complexity.
- Roles evolve.
- Responsibilities overlap.
- Systems accumulate.
- Permissions expand.
- Temporary access can become permanent access.
The practical adoption question is therefore not about removing access indiscriminately.
It is about examining alignment.
Does the information someone can see correspond to the responsibility that person actually holds?
And:
Does the authority someone possesses end where that responsibility ends?
If the answer is unclear, the problem may not simply be access management.
It may reveal something about the organisational design itself.
From shared visibility to defined responsibility
This is where ICCA: Accountability and Role Boundaries in Identity-Constructed Systems becomes interesting from a leadership perspective.
Accountability does not necessarily become stronger simply because more people can see more information.
It becomes stronger when there is clarity about:
- What someone is responsible for.
- What authority accompanies that responsibility.
- Where that authority begins.
- Where it ends.
Clear boundaries can make accountability more explicit rather than less.
Privacy and accountability are not opposites
There is a tendency to frame privacy and accountability as competing objectives.
Either we restrict visibility or we maintain oversight.
But that may be a false choice.
An organisation may not need broad visibility into people to establish who possesses a right, who holds an obligation, whether something has been authorised, or whether a responsibility has been fulfilled.
The more interesting challenge is therefore:
Can we prove accountability without unnecessarily expanding visibility?
If we can, privacy and accountability stop pulling in opposite directions.
They can become products of the same organisational design.
A question for leaders
Look at an important decision or process in your organisation and ask:
Who is actually accountable?
Then ask:
What does that person genuinely need to know to exercise that accountability?
And finally:
Who else can see the information simply because the system allows it?
The difference between those answers may reveal an opportunity to create stronger boundaries, clearer responsibilities and less unnecessary organisational exposure.
That is the adoption question behind ICCA: Accountability and Role Boundaries in Identity-Constructed Systems.
The principle does not remove accountability.
It asks whether accountability becomes stronger when responsibility, authority and visibility have clear boundaries.
The underlying ICCA work is openly shared under a Creative Commons Attribution-ShareAlike 4.0 licence, encouraging discussion, challenge, adaptation and further development.
The paper describes the architectural and organisational model. This article asks what adopting that model could mean for leadership, accountability and organisational design.
#ICCA #Accountability #Leadership #OrganisationalDesign #Governance #EnterpriseRisk #DigitalTrust #DataGovernance #DigitalTransformation #CreativeCommons
