Archive for April, 2008

Two Twitter Tales

In a great post last Friday, Marshall over at ReadWrite Web set forth a great set of examples of how they (RWW) use Twitter in their journalistic efforts. Head on over and read the whole thing - but in a nutshell, he tells how they use Twitter:

  • the discovery of breaking stories,
  • performing interviews,
  • quality assurance
  • and promotion of our work.

What was fun for me personally about this post is that I finally met Marshall (in person) the afternoon he was writing it - via Twitter. I was waiting for another networking meeting, and was watching my Twitter feed via iTweet:

@marshallk tweets

How many “Earthhippy” buildings in the Pearl are there? I surmised I was sitting in the exact spot (EcoTrust Building/World Cup) I’d find him. And I looked up toward the register, and le voila… an introduction eased by coincidence.

Fast forward to Monday. I went to meet Scott Kveton, also down in the Pearl. On autopilot, I had neglected to check where we were to meet, and went to World Cup again. I wondered whether I had crossed my wires, when, at 2:08, I hadn’t seen Scott walk through the door for our 2:00 yet. Knowing Scott is an avid Twitter advocate, I checked my feed only to see:

@kveton tweet

Ugh! wrong place… so I immediately DM’d Scott (sent him a direct message) letting him know I was in the wrong spot, and we quickly arranged to meet in the middle. He DM’d me back saying “meet in middle?” and the rest was captured here:

@janetleejohnson twitter

So: (and I know I’m on a rave about Twitter recently) the two events are linked in my mind forever as little examples of the beauty of “in the moment” speed, usefulness and connectedness that Twitter provides me.

It started with “Hi Friends…”

I got a note last week that I just have to take the time to expose to the air… from my friend Gillian. Her words struck so personally I feel moved to blog them:

::::

I hope you don’t mind me reaching out to each of you on a rather personal note…As most of you know, I lost my father to pancreatic cancer 9 months ago today. Although pancreatic cancer is one of the major cancer killers, it still receives little to no government funding or support.

Some of you may have heard of Dr. Randy Pausch, a 47 year old Carnegie Mellon professor who was diagnosed with pancreatic cancer, whom through his “last lecture” has gotten lots of media attention (Prime Time, Good Morning America, and yes, even Oprah). Well, here is his recent powerful appeal to Congress - it would mean a lot to me if you would take a moment to listen to it.

If you are so moved, here are a few additional ways to help:

  1. Write your local legislator
  2. Donate to the cause (be sure to earmark your contribution for RESEARCH) - through my mother’s efforts to raise awareness we have raised almost 30K in research funds in my father’s name, James J. Kennedy
  3. Continue to stay educated through http://www.pancan.org/ and http://www.lustgarten.org/

I appreciate your time with this and I can only hope that what we do today will make a difference.

::::

Apparently Gillian received a huge response to her note, and there were some further follow-on clarifications:

::::

I know there were some questions about donating to PanCan - it sounds like the only way to earmark the donation for research and/or make the donation in my father’s name (James J. Kennedy) is to either:

  • call PanCan at 1-877-272-6226 and make the donation over the phone or
  • mail in a check that has the information in the memo. The form for this and info about how to do it is here.

::::

Gillian and her mom are just trying to raise awareness. Apparently her mom is quite an expert on pancreatic cancer now. If anyone has questions, I’m happy to connect you with them.

Smart, Managed RSS Systems

I put up a slideshow on SlideShare last night that shows (rather than tells) screenshots of how easy and powerful a smart RSS reader (like my client Attensa’s) can be to setup and use. (View it in ‘full screen’ mode so you can see the screen shots easily.)

I’ve blogged before about how much my productivity has been enhanced by using it to keep up with news and information about clients.

Thought it might be useful to people to see how easy Attensa’s RSS reader for Mac is to use.

Of 2013, Enterprise 2.0 and Fear

Over on ReadWrite Web Sarah Perez wrote a compelling post summarizing Forrester’s predictions of Web 2.0 adoption in the enterprise. She gives a great synopsis of the report, and speaks about the barriers to adoption:

“….One of the main challenges of getting Web 2.0 into the enterprise will be getting past the gatekeepers of traditional I.T. Businesses have been showing interest in these new technologies, but, ironically, the interest comes from departments outside of I.T. Instead, it’s the marketing department, R&D, and corporate communications pushing for the adoption of more Web 2.0-like tools.

Unfortunately, as often is the case, the business owners themselves don’t have the knowledge or expertise to make technology purchasing decisions for their company. They rely on I.T. to do so - a department that currently spends 70% of their budget maintaining past investments.

Despite the absolute mission-critical nature of I.T. in today’s business, the department is often provided with slim budgets, which tends to only allow for maintaining current infrastructure, not experimenting with new, unproven technologies.”

And she goes on to say,

“By 2013 Web 2.0 will be a feature, not a product.”

And while I agree with the overall premise of that statement, I agree with Forrester:

By 2013 Web 2.0 will be a fabric, not a phase.

And I think it’s that vision - coupled with fear, not budget constraints - that is precisely what’s holding so many businesses back from Web 2.0 adoption today. Scott Niesen over at Attensa has blogged a leading indicator (to me) of the fear when he said,

We are working with forward thinking IT professionals [JLJ’s emphasis] who are partnering with business teams to integrate Web 2.0 technologies to enhance existing systems and business processes….”

I agree with Scott that finally enterprise RSS adoption is coming into fruition - but why has it taken us so many years to finally get here?

Why do the folks considering (what James Dellow has called “the DNA” of enterprise communication and collaboration) enterprise RSS today have to be the “forward thinking” ones? Because of fear.

And it’s not the IT folks who are to blame. Many business leaders (in all sizes of organizations) are fearful of Web 2.0.

Why the Fear? Because Web 2.0 Fundamentally Changes Business Rules

Many have written compelling visions of the future of the enterprise under the influence of Web 2.0 technologies. (I still enjoy Sam Lawrence’s “Enterprise Octopus” vision as a succinct roll-up of what happens to a business in a Web 2.0 environment.)

And I believe Hugh Mcleod, in writing his extremely insightful “The Hughtrain” post from 2005 was right:

“: There’s only one thing harder than starting a new business: Re-inventing an old one.”

Hugh’s “Porous Membrane” description (which could look a little like an octopus on it’s side) sums up “why the fear?” to me:

hugh mcleod porus membrane

“….So I drew the diagram above.

1. In Cluetrain parlance, we say “markets are conversations”. So the diagram above represents your market, or “The Conversation”. That is demarkated by the outer circle “y”.

2. There is a smaller, inner circle “x”.

3. So the entire market, the “conversation” is seperated into two distinct parts, the inner area “A” and the outer area “B”.

4. Area “A” represents your company, the people supplying the market. We call that “The Internal Conversation”.

5. Area “B” represents the people in the market who are not making, but buying. Otherwise know as the customers. We call that “The External Conversation”.

6. So each market from a corporate point of view has an internal and external conversation. What seperates the two is a membrane, otherwise known as “x”.

7. Every company’s membrane is different, and controlled by a host of different technical and cultural factors.

8. Ideally, you want A and B to be identical as possible, or at least, in sync. The things that A is passionate about, B should also be passionate about. This we call “alignment”. A good example would be Apple. The people at Apple think the iPod is cool, and so do their customers. They are aligned.

9. When A and B are no longer aligned is when the company starts getting into trouble. When A starts saying their gizmo is great and B is telling everybody it sucks, then you have serious misalignment.

10. So how do you keep misalignment from happening?

11. The answer lies in “x”, the membrane that seperates A from B. The more porous the membrane, the easier it is for conversations between A and B, the internal and external, to happen. The easier for the conversations on both side of membrane “x” to adjust to the other, to become like the other.

12. And nothing, and I do mean nothing, pokes holes in the membrane better than blogs. You want porous? You got porous. Blogs punch holes in membranes like like it was Swiss cheese.

13. The more porous your membrane (”x”), the easier it is for the internal conversation to inform and align with the external conversation, and vice versa.

14. Not to mention it makes misalignment, if it happens, a lot easier to repair.

15. Of course this begs the question, why have a membrane “x” at all? Why bother with such a hierarchy? But that’s another story.

[AFTERTHOUGHT:] And yes, this works with internal blogs as well, poking holes in the membranes that seperate people within a corporate culture; aligning “the conversation” internally etc. The other advantage of internal blogging is that it organises conversation into a long-term manageable form. Two people sharing ideas via blogs is a lot more permanent, viral and useful for the company than two people sharing the same information over by the watercooler.

[AFTERTHOUGHT:] Poking holes in membranes subverts hierarchies. Avast, ye scurvies etc.”

Avast ye scurvies it is! Let’s subvert the hierarchies, get over the fear of changing the way we do business and let the porous membranes dissolve. Our customers, employees and (I’ll bet money) shareholders will appreciate us for it.

Again, in a succinct summary statement, Martin Koser over on Frogpond said:

“Don’t spend hours pondering the details and splitting hairs - actually use this stuff and find out.”

Enterprise RSS Day Of Action - Memes are Bubbling

The Enterprise RSS Day of Action is coming up this Thursday, and it’s fun to see the conversations bubbling about it around the web. I especially liked Charlie Davidson’s matter-of-fact post about it the other day over on the Attensa blog.

In his very succinct post - “RSS is what RSS does” - he summed it up nicely…

“Ironically it is also the tool I am using daily to participate in this community of thought.”

Scott Niesen described a meme he’s been following that positions the technical and business points of view on collaboration and communications flow, where he succinctly describes how Attensa’s started talking in a very different way about “enterprise RSS” to enterprises who are struggling to get their arms around all the information they’re being asked to manage:

“When it comes to talking about getting your arms around the information you and Enterprise RSS, it all comes back to Andrew McAfee’s SLATES:

Search | Links | Authorship | Tags | Extensions | Signals

“SLATES describes the combined use of effective enterprise search and discovery, using links to connect information together into a meaningful information ecosystem using the model of the Web, providing low-barrier social tools for public authorship of enterprise content, tags to let users created emergent organizational structure, extensions to spontaneously provide intelligent content suggestions similar to Amazon’s recommendation system, and signals to let users know when enterprise information they care about has been published or updated, such as when a corporate RSS feed of interest changes.”

Replacing the abbreviation RSS with words like signals, alerts, delivery is far more descriptive and useful to customers. One of our customers has named their RSS initiative project: Communication & Collaboration Delivery. That’s got a much better ring to it than Enterprise RSS.”

As long as we don’t replace RSS with SAD, I’m cool with it, Scott.

James Dellow, over on the Enterprise RSS Day of Action WIKI, has envisioned this day and the WIKI space to set aside some time to review the following:

Enabling Communication and Collaboration To Do List:

  1. Develop a resource pack, containing slides, posters etc, that people can use to run their own day of action
  2. Create a list of Enterprise RSS solutions (servers, feed readers and other related tools)
  3. Develop an Enterprise RSS FAQ and Glossary
  4. Collect case studies of early adopters
  5. Enterprise RSS Company bios

I plan to spend the morning on Thursday talking communication and collaboration online. Care to join in?

-
Close
E-mail It