An excellent advice from Anthony Bradley of Gartner on Piloting Social Media:
“The most successful implementations I’ve seen don’t “pilot,” they execute on a planned increment. When you go to the community with a social media solution, go for real. So how do you mitigate risk? Mitigate risk with a carefully scoped purpose. Minimize the initial business purpose pursued but pursue that purpose with all the execution discipline it requires.”
Enterprise 2.0 conference is in progress this week in SF. Most of the speeches are available on [E2 TV]. Here are some tweets from the Conference attendees:
- trust, collaboration, network, engagement, task-driven, productivity-enhancement, defined-roles & responsibilities = 2.0 world (@ekolsky)
- Content is no longer enough, context of persona is key to E20.
- You can subscribe not only to a person feed, but also on tags.
- people want to work in an org where what they do matters, aligns with their principles and beliefs, be part of something (@ekolsky)
- The ethos has shifted from "need to know" to "responsibility to share" - Andrew McAfee
- Forrester reports that 1 in 2 businesses will use E2.0 software.
- Transparency does not eliminate the need for identity, security, etc
- More features are not what people are looking for in #E20. Focus 80% of your efforts on the 20% that really make people socially productive
- Use e2.0 for what you can't do with email, like journaling your work.
- 3 challenges to successful E2.0 deployment are Risk, Control, and Trust. deal with up front. - Dion Hinchcliffe
- Collaboration works best when it's in the flow of work- encourage interactions and multitiered adoption.
- you're never going to get people to that happy sharing place unless its in their flow of work.
- Key challenge with dedicated (standalone) enterprise microblogging platform is that it's not part of the workflow.
- collaboration needs to move from a doc-centric solution to a conversation-centric solution
- manage knowledge mostly by connecting people. Brains are just so much better than databases.
- The point is not to teach people how to use computer, but facilitating Human-to-Human interaction through a computer.
- "Business is conducted by people, not users" - @eugenelee
Source: Tweets from the Enterprise 2.0 2009 Conference (#E2Conf)
I n t e r e s t i n g r e a d
(a technology forecast by PricewaterhouseCoopers)
Modified on by Saqib Ali
… well at least about the proper translation of the term "Cloud Computing" to French:
A group of French experts had spent 18 months coming up with "informatique en nuage," which literally means "computing in cloud."
"What? This means nothing to me. I put a 'cloud' of milk in my tea!" exclaimed Jean Saint-Geours, a French writer and member of the Terminology Commission.
"Send it back and start again," ordered Etienne Guyon, a physics professor on the commission.
The problem was the word "cloud." In French, to be "dans les nuages" – or in the clouds – is a common expression meaning to be distracted.
"I think we can survive without the term 'cloud computing,'" said physics expert Mr. Guyon, slamming his hand on the table.
Why does terminology matter? Larry Downes explains:
| || |
No one’s “identity” is being stolen, but the use of the term to describe every financial fraud involving a computer amps up the terror level of consumers who largely have nothing to fear. The vast majority of “real” identity theft has nothing to do with computers at all, but rather begins with a stolen or lost wallet, stolen or simply discarded mail, or inside jobs pulled by clerks and others with legitimate access to the data.
The real problems are on the back-end, where credit card systems are left insufficiently secured, or where laptops with sensitive data are left in the back seats of cars where they are stolen not for the data but for the hardware. We keep hearing horror stories of government employees, university officials, and private sector employees who can’t even be bothered to put password protection on their logins, let alone encrypt their data. And the continued use of social security numbers by private enterprises both as a customer ID and an authentication field is probably the most dangerous practice of all.
[A]s long as consumers are being misdirected to think it’s their behavior that needs to be controlled, the financial services industry can avoid solving their largely self-made problems.
“Culture is an indirect variable, culture can’t be generated!”
Patent Application Abstract
A method, system and computer program product for enlivening conference calls. Noise detectors are placed on the telephone lines for the participants to a conference call. These noise detectors are used to monitor for noise on the telephone lines. A pre-selected stored sound (e.g., an interjection such as a laugh) may be generated if there is a period of silence on one of the telephone lines that exceeds a threshold, if noise is detected on a telephone line associated with a pre-selected individual, or if noise is detected on a pre-selected telephone line. Further, a request may be received from one of the participants of the conference call to play a provided interjection. The received interjection is later generated during the conference call. By including interjections during the conference call at appropriate times, the conference call may be enlivened and more interesting to the participants.
Read more .. ..
Lot of information scientist use the term "ontology" without really having a clear understanding of what it means. The following blogpost by Dr. Marshall X Ma of Rensselaer Polytechnic Institute gives a holistic definition of "ontology":
in short, ontology is:
For fun: the invisible hand behind anything;
In philosophy: (uncountable) the science or study of being; that branch of metaphysics concerned with the nature or essence of being or existence; (countable) a theory or conception relating to the nature of being;
In computer science: shared conceptualization of domain knowledge.
The professional life of the independent knowledge worker occurs in four different modes: insanity, give-back, work, and fun.
- If you are serving people you don't like to be with and are not getting paid, that is insanity.
- If you are serving people you enjoy being with but are not getting paid, that is give-back.
- If you are serving people you don't like to be with but are getting paid, that is work.
- If you are serving people you enjoy being with and are getting paid, that is fun.
First, find people you enjoy serving. Read more
Next, find problems you enjoy solving. Read more
… is Now available
This layer, developed by Sunlight Labs, allows people to visualize stimulus package contributions through an augmented reality application on any iPhone and Android.
David Navetta, Esq. CIPP, has published an interesting blog post on the topic of Legal Implications of Cloud Computing.
Mr. Navetta emphasize the need to understand the increasingly complex and interlocking relationships in the Cloud:
The party with whom a company is dealing will often not be the party actually processing data or providing computing services. This poses compliance challenges (e.g. how to perform/show due diligence) and contracting challenges (e.g. how to obtain/enforce contractual rights / remedies when one or two layers removed from the company actually doing the processing).
The blog post also highlights the need for proper data retention and destruction policies.
What if the SaaS provider is working on a Cloud Platform that creates residual copies of data that the Cloud User has a legal obligation to delete? What if the SaaS provider works with a Cloud Platform that does not have the technology or capability to properly wipe data? Even if the Cloud Platform has these capabilities, what if the SaaS provider has not negotiated for the right to obtain these services?
My thoughts on Legal Obligation to Delete:
Internet has created a world where "absolute destruction" of data is not easy to achieve. Even when the services are hosted in-house, this type of data destruction is not possible. There could be replicas, backups, off-site backups, DR backups, user created offline replicas, user archives and even printed copies.
I think what is a more achievable is delete in context. Data that loses its context, loses its meaning and is not of much use. So going back to Cloud Services, when I delete an email from my SaaS powered Inbox, the SaaS provider may still have some residual "Sharded" copies of the data. But these residual copies have completely lost their context. And as you traverse down the layers of Cloud Service aggregators (Saas –> PaaS –> IaaS), this residual data becomes more and more meaningless. Re-animating an email from this sharded residual data would be like trying to re-construct a needle by searching for its pieces in a haystack! :-)
You must love your [SaaS] vendor. You must trust your [SaaS] vendor. You must have your [SaaS] vendor's cell, home and wife's cell phone number. Your [SaaS] vendor is your lifeline. Do your research, make sure your cloud computing vendor has been in business for a long time, and with reasonable certainty, will continue to be in business for a long time. If a bank can go under, so can a cloud computing company. Maybe the answer is to use several different clouds. Don't put all of your documents into one cloud. Diversify. It's a tough economy out there, and at any given time, any company could be trudging up the bankruptcy court steps. The best you can do is to protect yourself as best you can.