One year ago today I embarked on my current adventure, leaving Adobe after five years there and two years creating the startup they acquired, Fotiva. At the time I left Adobe, I had only the fuzziest idea of what I was going to do, but I knew it would be related to the web, and I was pretty sure it would be connected to Ruby on Rails. And that it has turned out to be.

I’m as busy as I’ve ever been, and my income in the past year is the lowest it has been in more than 25 years. But I’m having a great time, and I have a good feeling about where things are headed. I thought I’d take the excuse of this one-year anniversary to look back on my decision to leave Adobe, and catch my readers up on my business thinking.

Looking back on Adobe

I’ve not written much about my experiences at Adobe, in part because I want to avoid any possible appearance of breaking confidentiality agreements, and also because I wanted to gain some perspective first.

Looking back on my five years at Adobe, there’s a lot that I’m grateful for. I learned a tremendous amount about digital imaging and the PC software business, and about life inside a big company. I met a lot of great people, was able to immerse myself in digital photography, and had the opportunity to lead a research team and do technology licensing with the power of a big player behind me. The team I helped build for Fotiva continues on, in large part, as Adobe’s Santa Rosa office, and I’m pleased to have had some small role in growing the software business in the North Bay. And the product that started life at Fotiva has an enduring role as the organizer in Photoshop Elements.

In a strange way, though, I’m most grateful to Adobe for being so thoroughly dysfunctional when it comes to enabling innovation that it drove me out. As someone with a entrepreneurial heart, I found Adobe stifling. If I had been able to accomplish a bit more at Adobe, I might still be there, and then I would have missed out on so much.

To a large degree, the challenges I faced finding happiness at Adobe would be there in any businesses at that scale. But not entirely. Many of the other entrepreneurial folks I met at Adobe, who tried valiantly to build new products and services, have also left. They’re at an assortment of small companies, but also at Google, and Yahoo, and Apple.

One of Adobe’s biggest weaknesses, in my view, is the distance between top management and the people who have passion for innovative new product ideas. It is exhausting, and usually dispiriting in the end, pushing ideas up through a chain that, at it’s pinnacle, doesn’t seem very interested.

The difficulties I had getting new concepts to market at Adobe, especially when they were web-related, are symptomatic of top management’s resistance to exploring new concepts in the marketplace. Adobe doesn’t like to accept the risk of new markets in return for a role (and learning opportunity) as an early player. Perhaps at Adobe’s scale their approach of waiting until market opportunities are clear, and then buying their way in as needed, makes sense. But it did not make for a satisfying place for me to work.

My evolving Ruby on Rails business plan

When I left Adobe, I had done a little Rails development, and read a lot about it, and I felt strongly that it was going to be a big deal. I spent the majority of this year building custom Rails sites for small businesses, and set up Topaz Web Solutions LLC as the home for that work. I enjoyed it, and some of it is ongoing, but my focus has now shifted to Collective Knowledge Works, Inc., the company I cofounded this fall with my partner Christopher Haupt.

I spent quite a while looking for ways to build a business around delivering Rails-based solutions to other small businesses. I continue to believe there is a great opportunity in this domain, but the sales and support challenges are significant.

Collective Knowledge Works grew out of an idea I had to create a portal for Ruby on Rails developers. We’re now deep into doing just that: you can sign up for the beta list at BuildingWebApps.com. Within a couple weeks, we’ll be letting in beta testers, and early next year it will be public. I can’t wait to show it off, and I think it’s going to be a great resource for the Rails community. After eight years away from the editorial, publishing, and training business, I’m glad to be back in it.

Initially, we don’t expect BuildingWebApps.com to generate much revenue directly. Our first revenue stream will be from the Ruby on Rails QuickStart Seminar that we’ll be presenting in February in San Francisco. Later, we believe we can create revenue from the site itself in various ways.

Christopher and I have just launched the Learning Rails podcast, which has been an adventure of its own.

There’s a bigger plan in the background, too. All the technology we’re building for BuildingWebApps.com can be used for any knowledge domain. After we’ve had time to build out this first site, we’re going to develop additional knowledge domains, and enable others to host their own knowledge domains. That’s why we named the company Collective Knowledge Works.

It’s great to be back in this early business-building phase. And it’s wonderful not to have to try to sell new ideas up through multiple layers of management, but simply to decide what to do, and then do it.

Today was my last day at Adobe. It was an odd feeling walking out the door for the last time.

I had a great job at Adobe. There were a lot of exceptional people I had the pleasure of working with. I’ll miss working with many of them, but I’m sure the relationships will endure. I’ll miss being in the digital photography industry, though I think I’ll enjoy it even more as a hobby.

I won’t miss the shrink-wrapped software business model, the isolation from strategic decision making, the split between marketing and development silos, the financial tyranny of being in a public company, and, most of all, the too-small box I felt I was in.

Seven years ago (on Thanksgiving day, in fact) I had the idea for a photo appliance, and registered the PhotoTablet domain. A couple months later we raised a round of financing and started a company, which evolved to be a PC software company and was renamed Fotiva. Two years later we sold the company to Adobe, where I’ve been for five years.

I’m starting on my fourth career. First I was a hardware/firmware engineer; then a newsletter publisher and conference producer; then a manager of software development and research. Now it’s on to building a business based on web applications. I think it’s a bigger opportunity than anything I’ve done in the past.

One of the projects I led at Adobe during the past year was the development of a new generation of web photo galleries to replace the clunky old HTML galleries that have been in Photoshop and Photoshop Elements for years. We built what I think is a pretty cool Flash application, which has some really nice features compared to typical web galleries. Most notably, it:

• Scales to fill the browser window
• Uses multiple image renditions (sizes) and uses the one most appropriate to the window size
• Performs intelligent prefetching of images
• Can be extensively styled via an XMLfile
• Supports video clips (FLV format) in addition to still images

This gallery is used in Photoshop Elements 5.0 and in Photoshop Lightroom, with different styling.

Now, for the news: Adobe has released the source code for the gallery as open source. This is a pretty large ActionScript program, which was written for Adobe by Bluefire Productions. You can get the code now from the Adobe Open Source site.

If you’re a Flash developer, you can modify the gallery program, or learn from it to produce your own design, and then distribute it to users of Photoshop Elements or Lightroom. They can install your design in either application and create galleries using it just like they can with Adobe’s standard version. You can even specify, using XML, what customization controls you want presented in the application. There’s a tutorial on how it works on the Flash Developer Center (coauthored by yours truly).

Here’s some examples of what the gallery can do:

• Thumbnail grid plus preview image
• Vertical thumbnail strip plus preview image
• Horizontal scrolling thumbnail strip plus preview image
• Slideshow with background image
• Lots of slideshows produced by users of Lighroom beta