Think about how many organisations you interact with every day.
- Your bank.
- Your mobile provider.
- Your supermarket.
- Your streaming service.
- Your airline.
- Your social platforms.
In the physical world, receiving a service does not always require the provider to understand everything about you.
Yet digitally, visibility has become almost synonymous with service.
- We track interactions.
- We analyse behaviour.
- We build profiles.
- We measure engagement.
And gradually, we have normalised a powerful assumption:
To serve someone effectively, an organisation needs to see them.
But does it?
What if visibility isn’t necessary?
Imagine separating two ideas we have allowed to become intertwined:
Providing a service.
and
Observing the person using it.
An organisation may need enough information to complete a transaction, establish an entitlement or deliver something requested.
That does not automatically mean the organisation needs continuing visibility into the person behind that interaction.
This distinction matters.
Because the moment an organisation can see information about someone, it inherits responsibility for what it can see.
- It must decide what to collect.
- What to retain.
- Who can access it.
- How to protect it.
- How long to keep it.
And increasingly, how to explain why it needed it in the first place.
For a greenfield organisation
Starting without the assumption of visibility creates an interesting opportunity.
Instead of designing a service and then adding privacy controls around the information it generates, leaders can ask a more fundamental question:
What would this business look like if seeing the customer were not a prerequisite for serving the customer?
That could change decisions about technology, customer journeys, governance, risk and even the business model itself.
Privacy becomes less about hiding information the organisation has already collected.
It becomes about questioning whether the organisation should be able to see that information at all.
For established organisations
The challenge is different.
Visibility is already embedded in many operating models.
Customer records, analytics, reporting, personalisation, marketing, security and performance measurement may all depend on it.
The adoption question therefore isn’t simply:
Can we become blind?
It is:
Where do we genuinely need visibility, and where have we inherited it as an assumption?
That distinction creates a practical starting point.
Not everything has to disappear.
Not every system has to be replaced.
But every point of visibility can be questioned.
From policy to structure
This is the important distinction behind ICCA Design Principles: Provider Blindness as a Structural Requirement.
Much of today’s approach to privacy depends upon organisations promising what they will and will not do with information they can access.
The alternative proposition is more fundamental:
What if, where visibility isn’t necessary, the system simply doesn’t provide it?
That changes the nature of trust.
Instead of asking customers to believe that an organisation will behave responsibly with information, leaders can begin asking whether the organisation needs access to that information at all.
That is not simply a privacy question.
It is a leadership question about responsibility.
A question for leaders
Look across your organisation and ask:
How much do we genuinely need to see to provide our service?
Then ask the harder question:
How much do we see simply because our existing systems allow us to?
The difference between those two answers could reveal something important about the organisation you operate today and the one you might choose to build tomorrow.
That is the adoption question behind ICCA Design Principles: Provider Blindness as a Structural Requirement.
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 principle. The article asks what adopting that principle could mean for leadership, organisations and the people they serve.
#ICCA #DigitalTrust #PrivacyByDesign #Leadership #DataGovernance #DigitalTransformation #CustomerTrust #RiskManagement #Privacy #CreativeCommons