Home About Contact Podcasts Writer River WordPress Consulting Advertising

Jeter Interviews Mike Hamilton at Former Blue Sky Software Office in La Jolla, Calif.

December 29th, 2007 | Posted in Recom. Podcasts, Technical Writing |

Madpak authoring suiteCharles Jeter recorded an excellent podcast with Mike Hamilton, V.P. of product management at Madcap Software, and posted it on his blog yesterday. Jeter is a technical writer in the California area who has been carefully analyzing the online help tool market.

The following are some of my takeaways from the podcast:

  • In an interesting real estate twist, Madcap moved back into 7777 Fay Avenue, which is where the former Blue Sky Software headquarters were. (Blue Sky produced eHelp, which later became RoboHelp.) This move back into the Blue Sky’s offices wasn’t intentional, but it seems fitting for Madcap, whose staff consists of many former RoboHelp employees. Apparently when the real estate agent unexpectedly announced the address of the new-found property, everyone listening on the phone fell silent.
  • You can sense Mike’s enthusiasm in the podcast. As a former technical writer, he and others at Madcap say they understand the technical writing community and its pain points. They’re trying to solve all problems technical writers face, and they’re approaching solutions for the entire workflow.
  • One can hardly ignore the impressive innovation Madcap has put forth over the past two years. They’ve produced a vast product line in a short amount of time. Some have even accused Madcap of having a “secret sweatshop of developers.”
  • In talking about innovation, Mike says they aren’t “just taking a handful of existing tools, throwing them in a box, and doing some marketing” (which he refers to as shovelware — obviously referring to Adobe’s Technical Communication Suite). All of Madcap’s apps were built from the ground up to support the concept of single sourcing. The products share integration of variables, visual elements, and even code.
  • Madcap Analyzer, one of their recent innovations, is a new product that Jeter says is “so good it’s scary.” Madcap Analyzer allows you to see problems in the help, such as inline formatting applied instead of styles. Hamilton says they “will continue to innovate tools into this space.”
  • Madcap has an open roadmap of development. They talk about what they’re working on, what’s coming in future releases of their products. Nothing is secret at Madcap, and they even solicit their roadmap ideas from customers.
  • Madcap actually uses their own tools to produce their documentation (what Jeter refers to as “eating their own dogfood”). This is also a point Rob Houser raised in his review of RoboHelp 7.
  • A recent San Francisco chronicle article reported that Adobe is laying off employees, while Madcap is rapidly expanding its staff and offices.
  • If you’ve downloaded Flare and Blaze, you know that the two look very similar. Mike says that when developers update the Blaze code base, it also updates Flare too, so that any hooks and other development foundations are available in the other products. This blending of code is how they share variables and other interactive features (and how they’re able to quickly produce so many products).
  • Madcap’s centralization of employees gives it an advantage when it comes to communication. If you need to talk to a developer, you can walk over to his or her desk with questions (as opposed to Adobe’s distributed model, which has developers in India and offices in the U.S. and other countries.)
  • Blaze promises to be a heavy-hitter — more impressive than first imagined, apparently. The formidable Sharon Burton has joined the Madcap team as product manager and is heading up Blaze.
  • Madcap now has 25% of the market growth. This is a trend that has a sharp curve upward.

Personal Reactions

The rivalry between Madcap and Adobe isn’t World War III, Mike says. But there is a strong tension between the two companies. The rivalry between Adobe and Madcap is good in an economic sense, in that it keeps consumer costs down, encourages innovation, and removes the ability for either company to sit back on their laurels.

During the podcast, Hamilton talks a lot about Madcap Capture (the integrated screen capture tool). He highlights this as an example of the integration of the Madpak authoring suite. Hamilton clarifies the purpose of the suite: Madcap is trying to provide single sourcing solutions that fit the software development workflow which technical writers live in. All the products function together to enable total single sourcing of your content.

Despite the logic behind the complete product line, the emphasis on integrated screen capture tools seems hard to buy. I almost invariably tweak my screen shots using SnagIt and Photoshop before inserting them into online help. I love both of these image capturing and editing tools. Why ask me to abandon them for something else? Every product has strengths and weaknesses and customers may want to pick and choose selectively. For example, I’d choose Captivate over Mimic, and Flare over RoboHelp, and Snagit/Photoshop over other screen capture tools, and Audacity over Echo (if they’re even competitors), and Visio over some other tool they might create. In my opinion, the concept of the suite is similar to a Swiss Army knife: lots of tools in there, but all kind of mediocre.

Mike points out that content created by a variety of tools may look inconsistent. If I were to use the Madcap suite of tools, the screenshots and screen demos and online help would all have the same look and feel. And you can share variables and content more easily between a suite of tools rather than a miscellany of products.

Maybe he’s right. I haven’t tried the Madpak suite of tools — only Flare and Mimic separately. Maybe the concept of the suite will grow on me with use.

Where Are the Blogs?

Finally, where are the blogs? With all the war going on between Adobe and Madcap, you’d think that each product champion would be hitting it hard on the blog scene. Nope, they’re both blog shy. If either were to start blogging in a whole-hearted, authentic way, they’d surely win over some of the audience.

Adobe has basically outsourced its blog to the development team in India, and Madcap sticks to its forums. Neither of these puts a personable face on for customers.

Based on some insightful comments, I decided to strike out the above. Adobe does have a good blog, and it looks like Madcap is getting ready to enter the blog scene.

RSS Subscribe


Related Posts

Tags: , , , , , , , , , , , , , , ,


Comments

You can leave a response, or trackback from your own site.

17 Responses to “Jeter Interviews Mike Hamilton at Former Blue Sky Software Office in La Jolla, Calif.”

  1. Wow! Great post. Thanks for listening to my podcast.

    You know, it’s funny you mention the blogs. Offline, Mike Hamilton told me he’s working in the little time he has to himself in putting out his mikehamilton.com blog. We were talking about technology, and next thing you know, we’re whipping out our phones and showing applications off, etc. etc.

    I’ve got to post a picture of his favorite cell phone application - reminder to myself.

  2. [...] bookmarks tagged tools Jeter Interviews Mike Hamilton at Former Blue Sky … saved by 11 others     thesunpilots bookmarked on 12/29/07 | [...]

  3. You say that Adobe and MadCap are “both blog shy,” and that “Adobe has basically outsourced its blog to the development team in India.”

    IMO, the Adobe Tech Comm product team has one of the better blogs among tools vendors (http://blogs.adobe.com/techcomm). Plus forums on the Adobe Web site, and user-contributed content in the Adobe Developer Center (http://www.adobe.com/devnet).

    Is a blog any less valid or useful if the blogger is in India? Is a product any less viable because the product team is in India? These are perhaps uncomfortable questions for writers based in North America, but we must address them in today’s global economy.

    Note that the contributors to the Adobe Tech Comm blog are Adobe product managers for the Tech Comm Suite, FrameMaker, and RoboHelp. They normally staff the Adobe booth at major tech comm conferences (e.g., STC and WritersUA). I encourage you to make an effort to meet them and share your ideas in person.

  4. Alan, you’re right. Adobe does have a good blog for their product, and they do have exceptional forums. I didn’t realize that the bloggers are product managers that attend conferences. I thought they were just the outsourced dev team.

    Whether the blog comes from India or elsewhere doesn’t matter to me — I just think the product champion should swing the bat on the blog scene. But I guess that actually, it might be better for the dev team to head up the blog — they know the product, the roadmap, and most importantly, they won’t be full of marketing speak.

    I’ll update the post a bit with some strikethrough font.

    Whether perceived product leaders like Mike Hamilton, RJ Jacquez, JoAnn Hackos, and others blog or not reminds me of a post Holly Harkness wrote a while ago called “Why aren’t more tech comm leaders blogging?”

    Although I’d like to see more leaders jump into the blog scene, I’d only like to read blogs that are appealing. If someone doesn’t want to blog, but is forced into blogging by social pressure, most likely the blog will be lackluster. Any thoughts on that?

  5. Tom — I’m grateful for your balanced response. I think there are some erroneous assumptions commonly made by writers in North America: for example, that any India-based operations are “outsourced” and (assumed to be) under the direction of U.S.-based management. I’m seeing more India-based operations with nearly complete responsibility for all aspects of product development and marketing. I’m planning a session at the STC Summit in Philadelphia to address the changing global business environment and (hopefully) to dispel some of the common misconceptions about global teams.

    As for getting more tech comm leaders into the blogging scene — there are lots of ways that these leaders contribute to the profession. Participation in standards bodies (like OASIS and W3C) comes to mind. Publishing books and newsletters is another positive contribution, as is volunteer leadership of organizations like the STC. Academic research is important, and often overlooked. All of these activities are time-consuming, and many don’t necessarily provide publicity or exposure. But all are important for the continued growth and evolution of our profession.

    I think it’s great when established leaders blog, but I understand why many choose not to. I also think much of the really appealing blog content is being generated by former “non-leaders” — those who have valid, insightful opinions, and who have become recognized in our profession through their blogs.

  6. Blogging is a double edged sword. As far as Adobe’s team is concerned, I’ve been highly critical of their blogging for what I feel is good reason.

    If you’re going to say one thing and do another, best not to put it into print where it can come back and rip you a new one.

    Item: Quality is innovation post by Vivek Jain where he states in March 2007, “I believe it is time to return to fundamental principle of software delivery- Quality. ”
    http://blogs.adobe.com/techcomm/2007/03/quality_is_innovation.html

    … yet RoboHelp 6 and particularly RoboHelp 7 were both soundly criticized for having an uncomfortable amount of bugginess.

  7. Alan,

    You raised an interesting point. Exactly where does that outsourced concept drop off into international business is a good thing to speak of, and sounds like it would bring clarity into a fuzzy world.

    My concept of outsourcing is where a (typically) stateside employee’s tasks are handed over to an employee or group hosted outside the (typically) United States.

    Yet in a clinical viewpoint this would be a simple cost cutting measure to a global company. So why would it not be transparent and spoken towards?

    In reviewing the Adobe acquisition of Macromedia through the SEC filed documents it was interesting to note that Adobe does not list the quantity of stateside employees like Macromedia did. Therefore, discovery or comparison of actual outsourcing that occurred after the merger versus previously held overseas positions is rendered opaque.

    It’s also interesting that the Adobe RoboHelp technical support team formerly located in San Diego was, by my terminology, outsourced in the summer of 2007. The only indicators of this however, are local print media (San Diego Union-Tribune) articles and blogs such as mine.

    Sounds like another thread is needed here unless you have one on your site. I’ll add it to my feed reader.

    My conclusion is that although none of us wants to discriminate against other nationals or seem to prefer stateside business versus a better (or perceived better) global product, the facts remain that there are trade deficits in knowledge and skills. These are measurable, and this concerns all of us in technology trades where our data is easily transported.

    After all, what makes any of us think that our innovation is competitive if, at the end of the day, our knowledge is commoditized from let’s say a $90/hour rate to a $10/hour rate. The market does correct itself because unerringly clients are burned and realize that they do get what they pay for, however it’s still a bitter pill and guess what?

    We tend to vote with our pocketbooks. Tech Support jobs previously held stateside farmed out to India? Ok, it’s definitely going to be factored into my decision making process as an American consumer.

    There’s a backlash going on about outsourcing and it’s not about ethnicity. It’s about clear and concise communication across several fronts - a marketplace being heard, products staying competitive, and that good old corporate value of Corporate Authenticity.

    It’s also a cultural backlash. Nobody likes to fear for their job right before Christmas and New Year’s yet the Adobe office in San Diego just laid off an undetermined number of people. I bet it wasn’t just one person either. Culturally, that seems insensitive.

  8. Alan,

    You wrote something that caught my attention: “… there are lots of ways that these leaders contribute to the profession.”

    This point made me reflect a lot. I often tend to see things myopically: if I’m actively participating in my local STC chapter and see other technical writers staying at home, I think, hey, you guys should participate more in the chapter.

    If I’m blogging and see other tech writers shrug their shoulders at the medium, I say, hey, you should be blogging.

    If I’m participating on a listserv and see others not subscribe, I think hey, everyone should be subscribed to this listserv.

    Or writing articles — if I write for the Intercom, I think hey, a lot of other writers should be submitting articles to this magazine.

    Or with podcasts, I think everyone should be listening to podcasts.

    And so on.

    I haven’t given any attention to a lot of other, equally important ways to contribute. I almost never view or comment in the STC Forums, I haven’t even looked at the new Learning Resource Center, and the last issue of Tieline I glanced at was about 6 months ago. I don’t participate on any standards committees, nor in other organizations (like the IEEE), and I often only glance at the cover of the Tech Comm Journal, much less think about ways to contribute to it.

    You’re right — we all participate in the profession in different ways. Not more than 5% of people blog. The medium simply does not appeal to many people.

    You’ve made me think differently about non-bloggers now — everyone chooses to contribute in their own way, according to the mediums that appeal to their learning styles, interests, and strengths. Thanks for helping me see this.

    Blogging does require a lot of time and thought. The main reason I blog is because I like to write and think — the blog gives me space and opportunity to do it, and interactions from readers like you always enrich me.

    I also like the “level-playing field” that blogging provides. As you say, you don’t have to be a big name or thought leader to reach people.

  9. The thread that’s developing about outsourcing and a global economy is interesting, but now I’m confused. How do you see Adobe’s development of RoboHelp? Is the work not outsourced to a development team in India, or is Adobe simply a global company with locations that include India? What are your views on this move by Adobe?

    By the way, in case you missed it, a while back I interviewed an Indian writer in Bangalore, India.

  10. Tom,

    My question exactly. Which is it, and how would we determine it? If we can’t see how many stateside jobs were lost when Macromedia was absorbed, it’s nearly impossible to determine.

  11. Here’s an interesting article about Adobe’s expansion in India and their focus on technical documentation.

    Adobe to invest $200m in five years

    NEW DELHI: Having established itself as one of the most important R&D centres for Adobe Systems worldwide, Adobe India is now drawing up plans to expand its capacity in India. The company’s business plans include expansion of capacity, increasing sales force, doing more R&D out of India and focusing on e-learning, online gaming and technical communication.

    Already, 25-30% of Adobe’ worldwide R&D is being done from India. The company now plans to increase that share substantially. “We have already said we plan to invest $200 million in India in the next five years,” says Naresh Gupta, MD Adobe India.

    The company is in the process of expanding capacity in its Noida facility from 900 to 1,500 in the next four months and to 2,000 in the next two years. Similarly, capacity at the Bangalore campus will go up from 400 to 800. “We also plan to increase our salesforce by 50% in the next three years,” says Gupta.

    In fact, the India operations is very critical for Adobe’s overall growth. So far the company has filed more than 50 patents from here. Nearly all global Adobe products have a contribution from India. While some have been completely done out of the India R&D centre.

    The company now plans to focus on three key areas of growth. These include: E-learning, technical documentation and online gaming. “E-learning is poised to grow at 45% worldwide,” says Gupta.

    I think it’s great that the focus is on technical documentation and e-learning.

  12. Wow. eLearning, technical documentation, and online gaming.

    Three areas I’ve been researching for quite some time. Add to that Wireless and I’m just going to start working in the construction field.

    Anyone need an energy efficient home??

    ;-)

  13. Actually I think it’s great in a global sense that we have a competitive market. It starts getting political when we’re looking at constantly having to push the edge in innovation yet we are under many more constraints (or could easily be under those constraints with a stroke of the pen).

    I’ll be looking forward to my time reviewing the Annual Report for Adobe to see where this focus fits. It is exciting, however I am cautious in my praise because it does represent a change in the knowledge management market that I’m not sure will help users at the end of the day.

    Sounds like a great topic for a blog post though!

  14. [...] but this was just too current to pass up. I’ve been hacking away at some research ever since Tom and Alan had a great off-topic discussion that began in the comments of Tom’s review of my [...]

  15. Alan, Tom,

    Feel free to comment on my blogpost/thesis paper! I’d love to have you crunch the numbers I found and see what results.

    There’s more than a passing probability that I made a math mistake. I haven’t done ratios in five or eight years…

  16. [...] insightful opinions, and who have become recognized in our profession through their blogs. (see comment | see Alan’s [...]

  17. …Much of the really appealing blog content is being generated by former “non-leaders” — those who have valid, insightful opinions, and who have become recognized in our profession through their blogs. (seecomment| see Alan’s blog) In other words, people who don’t hold high-up leadership positions are often the ones with more interesting blogs. At first this seems a contradiction: one would think people in high-up positions would have more interesting

Leave a Reply