Selling the Business of Value of DID’s
Selling The Business Value of DIDs: How Do We Convey (And Quantify) The Commercial Value of: Portability(Mobility), Selective Disclosure/NKPs?
Thursday 15F
Convener: Karyl Fowler, CEO at Transmute
Notes-taker(s): Margo Johnson
Tags for the session - technology discussed/ideas considered:
Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:
Transmute: Starting with business process optimization
3 question framework
- Is selective disclosure or privacy a priority?
- Is there is high coordination burden?
- Defined as Large amount of friction between players of a network
- Is traceability or audibility important?
Focusing on cost and revenue centers of the company
Core features:
- Portability of DID
- Inter-operability: vendor proprietary lock-in is seen as a problem (Government)
- The word portability seems to resonate in some cases… attach to person or thing
- Relationship to mobile phone number portability
- Vendor: it is configurable (portability can be a bad word!)
- Consumer thinks of as ubiquitous acceptance - “freedom”
- Relationship to mobile phone number portability
What types of language work for clarification of the business proposition of DIDs? (group brainstorm)
Unlock potential of better work flow… further integration into the market value network that provides customer experiences
More APIs more integration of services
Identity layer unlocks potential for deeper service integrations
Get out of your silo
Parallel to microservice architecture value proposition
Telcom example
New company… if you don’t like my service you can always go back… and I can ingestst
“Insurgents” like idea of portability
Bigger companies don’t like ideas of portability
Future-proof, fear-based sales don’t work as well
Regulation in the mid-term
Defense logistics totally different
EU Governments
GDPR — privacy is a big selling point
Opportunity to leapfrog from paper to not a central silo… not having to be the sole carrier of risk
“Distributed responsibility”
Everyone can use the same SSI method… you can’t tell that I am using social benefits services
“Seamless”
High failure costs … “cryptographically verified” to save time and money
Don’t trust, verify
Avoiding correlation
“Protecting proprietary information”
“Protecting business secrets”
Who you are at work, at home, etc. Protecting personal privacy… own identity
Decentralized reputation
Open your network to opportunity, not risk
Carrier can take their reputation, not your IP
Using the word “blockchain” is the innovation sell
Compliance and ease of integration
Provability
Healthcare context - the “P” in HIPAA … portability is required
Governance: anti-surveillance is compelling
Ease of use
Federal government clearance process
Same with physician credentialing
Standardized way of doing this
Recognition between a company and customer
Stop treating you customer like strangers
What are you gaining from SSI?
What are you losing from not adopting it?
Legal challenge: How to port reputation without giving things away
Selective disclosure about prior confidential matters without over-disclosing
Congressional testimony: say the things you want to say without saying the things you don’t want to say
At same time, building community of belief of self-sovereign identity
Putting the customer in charge
What is the most compelling functionality of DIDs?
-Wallet in order to manage identity
-Mutual consent receipts
-Terms and conditions consent provably bilateral
-Open Source
-Password-less options
Next steps
Need for a business gathering?
Temporary working group for the DIF
Business glossary?
Common language
