Breaking a consensus?
Balancing divergent interests is one of the key things to do in a project: between business people defending the functional requirements and technologists pushing for non-functional, between the project manager guarding his time and budget constrains and the project member wanting to figure out the details of a problem, etc…
Lacking a brilliant visionary that can nail the silver bullet (the number of Steve Jobs in this world equals “limited - 1” these days), most project teams settle around a consensus. This decision approach does not always lead to an optimal solution (referring to the Belgian situation would be too easy), but allows building a shared discourse that is broadly supported and accepted (http://en.wikipedia.org/wiki/Consensus_decision-making).
Once such a consensus is found, introducing a divergent idea (e.g. to accommodate new insights or other requirements) is hard. Lacking the in depth elaboration, the required maturity and the broad understanding of the consensus idea, it is rather easy to shatter it to pieces and dispose of it - no matter if it may have a potential or not. Furthermore, most projects do not have the luxury to return on decisions taken or bet on several horses. Unfortunately, it may take a long time to validate the assumptions behind any large decision and assess the impact (market fit, technical feasibility, …), so doing an a posteriori evaluation of the original decisions is an exercise rarely doable.
My suggestion: make sure that you are part of the initial consensus building team. Breaking a consensus later on may seem a worthy cause, but chances for success are small & will in any case require lots of effort. And for the shortcomings of the/any consensus… I guess creativity will bring the right answers :)
Feel free to share your own experiences!
Personal Identity Management
A couple of weeks ago, I ran across a blog post “Thoughts on Data Privacy and the Penny Gap” [link], which took me to the website of www.personal.com. A couple of days ago, their blog featured a Forrester report titled “Personal Identity Management” [link].
The idea behind personal identity management is that the control over data shifts from the (large) operator of a service one wants to use, to the individual data owner, i.e. yourself. Each of these data owners will have one or more lockers on which they have the control and expose the relevant data when they see fit. Personal takes it a step further: they let you manage your data, not only for you own use, but also allow you to sell your data, withholding a transaction fee. This way, your data becomes an asset you can capitalize upon.
My first thought is that the consequences are huge.
The promise of being able to control who uses your data for which purpose is great. After all, it is private and yours. But in exchange for a real value in return, you’d want to share it (temporarily). Or perhaps I may even win the lotto by just being me?
But I guess there are some challenges that are similar to what we’ve known for a while… Rather than functionality provider, we need to select (and trust) an identity management service provider. What happens if they get compromised? How well will the business model work? Do we want to hand over a key asset to a governmental service? What is a reasonable price for my data?
My second thought was simpler.
Read more on the topic :)
I’ll keep you posted if I get some more insights!
While I am keeping my promise of reading more on the Personal Identity Management, I gladly take any opportunity to exchange ideas with open but critical minds. This morning one of these opportunities took place… and one of the questions was: