Argh! I tried to figure out what mine would say and it came out something like this: "I'm on my team's Sharepoint site. Your team doesn't have one and you aren't authorized to view mine. Have a nice day!"
- Daniel J. Pritchett
This makes a good point for me to press in-house though: Viral adoption of Sharepoint is not possible when teams have disconnected silos and no one has access to the other silos.
- Daniel J. Pritchett
I'm resharing this to the #e2adoption LinkedIn group - until we get some centralized micromessaging going on we'll lose these tasty bites of conversation.
- Daniel J. Pritchett
from IM
I've been experimenting with socialcast... do you want to try it? it's pretty cool. better than Yammer, imo. Also, let's put this note from Steve Radick in the thread too. http://twitter.com/sradick...
- Susan Scrupski
Done. I'd be happy to help with socialcast testing. Can you give me an account on a 2-person E2adoption community or should I start my own trial sandbox?
- Daniel J. Pritchett
from IM
They too are using the Yammer/Signals model of "your email domain determines your community access". Yet another sign that we oughta get some member emails created. I know you said you'd bought a domain and that you were testing Google Apps but I never figured out whether or not those were related stories.
- Daniel J. Pritchett
I've got a glimmer of an idea on how to push this argument and I'm going to use endless corporate restructuring as the foundation: "How long has your current team existed? Does it have its own knowledge silo? What is to be done with this silo when the team ramps down and is eventually decommissioned? What will you do with your silo if the team is split up or absorbed by another team?" I feel like "stop making KM silos" is the obvious answer, but maybe I'm prejudiced.
- Daniel J. Pritchett
from IM
Bridges To Knowledge: A Blog by Barry Camson: Six Important Conversations To Have To Bridge The Enterprise 2.0 Cultural Gap - http://www.barrycamson.com/2009...