Where’s Adobe on blogosphere?

Jim Turner says about Adobe: “I can tell you what they are not doing, they are not having a conversation with the influential people in their industry.” and “Where is the Adobe blogger?”

I guess Jim missed that Adobe has tons of blogs.

And, I would expect that Adobe will increase the discussion over the next few months. I am telling them not to invite me next time, but to get a bunch of .NET developers in a room like Scott Hanselman. Those are the influentials that Adobe really needs to have a conversation with.

26 thoughts on “Where’s Adobe on blogosphere?

  1. I think John captured exactly my thoughts, it’s just too bad I was not better at presenting my own idea. John, when it comes time to find that authoritative voice, I hope you are standing in line for the job!

  2. I think John captured exactly my thoughts, it’s just too bad I was not better at presenting my own idea. John, when it comes time to find that authoritative voice, I hope you are standing in line for the job!

  3. Thanks John, but the more I think of it, it sounds like Jim was seeking the authoritative Adobe “voice” on a current issue related to Adobe.

    On this issue there was no authoritative group voice, but instead a series of individual narratives, because these Adobe and non-Adobe projects were in early development — we can’t wait for a formal group process to get its considered messages in consensus among stakeholders — the goal here was to get feedback early, to enable course-corrections *early*, before the company formed the final 1.0 message which would be amplified out to the world.

    I can understand why Jim would like to find Adobe’s side of the story, but in this case it’s not yet a story, not at least at the level at which Adobe Systems sets a 1.0 number. Does this sound reasonable to you…?

    jd/adbe

  4. Thanks John, but the more I think of it, it sounds like Jim was seeking the authoritative Adobe “voice” on a current issue related to Adobe.

    On this issue there was no authoritative group voice, but instead a series of individual narratives, because these Adobe and non-Adobe projects were in early development — we can’t wait for a formal group process to get its considered messages in consensus among stakeholders — the goal here was to get feedback early, to enable course-corrections *early*, before the company formed the final 1.0 message which would be amplified out to the world.

    I can understand why Jim would like to find Adobe’s side of the story, but in this case it’s not yet a story, not at least at the level at which Adobe Systems sets a 1.0 number. Does this sound reasonable to you…?

    jd/adbe

  5. Robert, I think Jim misses the point about blogging. There does not have to be one voice from Adobe. Isn’t that the whole point, Adode provides many, many voices by having or encouraging employees to write corporate blogs.

  6. Robert, I think Jim misses the point about blogging. There does not have to be one voice from Adobe. Isn’t that the whole point, Adode provides many, many voices by having or encouraging employees to write corporate blogs.

  7. Just who are these “influentials” that you (Robert) and Jim Turner are talking about? The so-called “a-list” bloggers, the self-appointed know-it-alls?

  8. Just who are these “influentials” that you (Robert) and Jim Turner are talking about? The so-called “a-list” bloggers, the self-appointed know-it-alls?

  9. … which is why the entrypoints on the Adobe website point to the aggregators.

    Desuetude’s a common problem for all blogs. (And of weblogs which are active, not all have content, or cost-effective content, but I ramble.)

    jd

  10. … which is why the entrypoints on the Adobe website point to the aggregators.

    Desuetude’s a common problem for all blogs. (And of weblogs which are active, not all have content, or cost-effective content, but I ramble.)

    jd

  11. Thanks, Jim. I agree that it can be hard to find a particular resource on large sites.

    Searching Google with “adobe weblogs” turns up many results before the main entry points, for instance.

    Navigating may be more straightforward… the “Communities” tab in the site’s main naviation bar leads directly to relevant weblog resources.

    jd/adobe

  12. Thanks, Jim. I agree that it can be hard to find a particular resource on large sites.

    Searching Google with “adobe weblogs” turns up many results before the main entry points, for instance.

    Navigating may be more straightforward… the “Communities” tab in the site’s main naviation bar leads directly to relevant weblog resources.

    jd/adobe

  13. Robert and John,

    I did a little mea culpa on my comments. I was actually looking to find a place on the adobe site where I could click to get the Ado0be side of the story. Yeah I could sort through the many enterprise type blogs, but I wanted to go to one stop shopping.

    Searching through all of the blogs I came up with only a recap of what I had already read on 10 other blogs, and had received in my RSS feeds. I got an echo. Where is the Adobe voice?

  14. Robert and John,

    I did a little mea culpa on my comments. I was actually looking to find a place on the adobe site where I could click to get the Ado0be side of the story. Yeah I could sort through the many enterprise type blogs, but I wanted to go to one stop shopping.

    Searching through all of the blogs I came up with only a recap of what I had already read on 10 other blogs, and had received in my RSS feeds. I got an echo. Where is the Adobe voice?

  15. I posted the following on Jim’s blog over an hour ago, but it still hasn’t made it out of the (unadvertised) moderation queue:

    – start –

    “Where is the Adobe blogger?”

    Hmm. You’re aware where the term “corporate blogging” came from, right?
    http://www.wired.com/news/culture/0,1284,52380,00.html

    The Macromedia weblog system has not yet been rolled into the Adobe staff weblog system, but both are quite active, informative and influential:
    http://weblogs.macromedia.com/
    http://blogs.adobe.com/

    The Engage event was not a public broadside — lots of the discussion revolved around the Apollo project, which is not yet even a beta public release. This was more an event to get a few dozen bright people from different disciplines together in a room, and to look at some of the early projects from different development groups, and discuss them together. Updated links to more resources here:
    http://weblogs.macromedia.com/jd/archives/2007/02/adobe_engage_li.cfm

    jd/adobe

    – end –

  16. I posted the following on Jim’s blog over an hour ago, but it still hasn’t made it out of the (unadvertised) moderation queue:

    – start –

    “Where is the Adobe blogger?”

    Hmm. You’re aware where the term “corporate blogging” came from, right?
    http://www.wired.com/news/culture/0,1284,52380,00.html

    The Macromedia weblog system has not yet been rolled into the Adobe staff weblog system, but both are quite active, informative and influential:
    http://weblogs.macromedia.com/
    http://blogs.adobe.com/

    The Engage event was not a public broadside — lots of the discussion revolved around the Apollo project, which is not yet even a beta public release. This was more an event to get a few dozen bright people from different disciplines together in a room, and to look at some of the early projects from different development groups, and discuss them together. Updated links to more resources here:
    http://weblogs.macromedia.com/jd/archives/2007/02/adobe_engage_li.cfm

    jd/adobe

    – end –

Comments are closed.