<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>JohnnyL’s Blogic</title>
      <link>http://blogs.adobe.com/johnnyl/</link>
      <description>John Loiacono is Adobe’s SVP of the Creative Solutions Business Unit</description>
      <language>en</language>
      <copyright>Copyright 2008</copyright>
      <lastBuildDate>Thu, 27 Mar 2008 11:53:38 -0800</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=3.2</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <item>
         <title>Look Mom, No Hands, er, I Mean, No CD</title>
         <description><![CDATA[<p>Wikipedia defines Software as a Service (SaaS) as a software application delivery model where a software vendor develops a web-native software application and hosts and operates the application for use by its customers over the Internet. <br />
 <br />
Dramatically reduced cost for computation and storage resources as well as plummeting network bandwidth costs are greatly increasing the ability to deliver software as a service. It is estimated that by 2011, 25% of all business software spending will be delivered via a SaaS model. That is up from 5% in 2005 (per our friends at Gartner). Clearly, SaaS is becoming an increasingly important part of the IT stack; helping organizations in a multitude of industries manage their day-to-day business. The benefits include reduced costs, bug count and IT resources, faster implementation and iterative development cycles, and always being up to date.<br />
 <br />
SaaS is already an integral part of Adobe’s strategy in the enterprise space with its products Acrobat Connect and Scene 7. And we will continue to increase our investments in SaaS for both the enterprise and our creative pro audiences.<br />
 <br />
But what about the consumer space? You’ve probably observed the broadband penetration into the home, consumer comfort with web-based applications and the explosion of sharing on the Internet through social networking sites like MySpace and Facebook. <br />
  <br />
People are taking more pictures than ever before – an estimated 49.5 billion images were captured on digital cameras and camera phones in 2006. Couple that with the number of people online growing at an ever-increasing rate, at all ages. In the US alone, it is estimated that 20% of the online population is represented by the 18 - 24 year old demographic.<br />
 <br />
But there has been something missing – a complete imaging solution that offers a broad set of functionality specifically geared to this emerging ‘connected generation’. To continue Adobe’s passion of enabling engaging experiences, we have announced Photoshop Express – a new service that will support this community of mass market consumers in the creation of engaging content in rich environments.  </p>

<p>Photoshop Express is fully web based. No CDs. No downloads. No updates or activation. Whenever you log in, you’re using the very latest version.  While we have leveraged Photoshop core technology to build this new solution, it is not Photoshop online. It is a targeted solution focused on this new generation of content creators that will extend the power of creativity to the consumer at large. For this audience, it is a complete solution. You can easily upload, organize/sort, edit, store and show off your images. And when you’re done, share them anywhere, including social sites such as MySpace and Facebook. <br />
 <br />
It’s easy. It’s fun. It’s free. All you need is a browser. To learn more about Photoshop Express, and to participate in our just released beta program, go to <a href="http://www.photoshop.com/express">www.photoshop.com/express</a>.</p>

<p>You take the pictures. We’ll help you make them look great as you share them with others.<br />
</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2008/03/look_mom_no_hands_er_i_mean_no_1.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2008/03/look_mom_no_hands_er_i_mean_no_1.html</guid>
         <category>General</category>
         <pubDate>Thu, 27 Mar 2008 11:53:38 -0800</pubDate>
      </item>
            <item>
         <title>See You At MAX 2007</title>
         <description><![CDATA[<p>Last year I attended my first <a href="http://www.adobemax2007.com/na/">MAX conference </a>just a few months after started working at Adobe.  MAX is our three-day, interactive event aimed at showcasing the latest technologies and strategies to developers, creative professionals and, generally, anyone interested in what we're up to.  The most positive response I get from attendees is the insight they get via the keynotes, the number of "sneak peeks” we use to showcase what's on the horizon, and most importantly, the opportunity to speak directly with our top evangelists and engineering experts. The most compelling reaction is a good "oooh or ahhh".  <br />
 <br />
We had great attendance at last year's event.  Shortly after, we announced <a href="http://www.adobe.com/creativelicense/?sdid=BDXEW">CS3</a> and began shipping to the kudos and applause of our customers, industry pundits, reviewers, bloggers... just about anyone who used them. The better news is that the momentum just keeps building - and this years' MAX is yet another example. More than two weeks before the start of the program, we passed the 4K registered attendees number for the first time in the history of the event. And I suspect we'll get to the maximum capacity for the show well before opening day and beat last years' crowd by a ton. We've been doing that at all our events this year.  The buzz and anticipation that is building for MAX is simply huge - and for good reasons. <br />
 <br />
MAX 2007 will feature more than <a href="http://www.adobemax2007.com/na/sessions/">200 sessions in five tracks </a>from which to choose. The group I run, the Creative Solutions Business Unit, developed two tracks this year. The first is Design Across Media - a key workflow for just about every media-based company I speak with of late. And the other is Web, Video and Interactive Design. There are a ton of strong sessions in each of those two tracks. <br />
 <br />
You shouldn't miss 'What is the New Publishing Workflow Anyway?' being led by Will Eisley. He'll be talking about how Adobe technologies enable you to create, manage and publish content across multiple channels. <br />
 <br />
And if you want a look into the future, Joan Bodensteiner, Rick Grefe – the AIGA Executive Director, and Darcey Merriam will be talking about Designer 2015 - a look at the trends and opportunities we see for the designer in the year 2015 and "visioning" what creative tools may look like to address the way they will be working. <br />
 <br />
And for those of you using the Master Collection - or aspiring to use it - some of our top evangelists will be running a session called Unlocking Cross Media Workflows. With Jason Levine, Greg Rewis, Rufus Deuchler and John Schuman leading the session - I can promise that you will not be bored!  (We have a strict Adobe policy that these individuals are not allowed to be exposed to caffeine during work hours.) Guaranteed to be both informative and entertaining.<br />
 <br />
For those of you who attend MAX - let me know what you think of the event. Be sure to attend the sneak peek sessions. And please "oooh" and "aaaah" and applaud when you see things you like. I'm never tired of those reactions! <br />
</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/09/see_you_at_max_2007_1.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/09/see_you_at_max_2007_1.html</guid>
         <category></category>
         <pubDate>Tue, 25 Sep 2007 13:10:06 -0800</pubDate>
      </item>
            <item>
         <title>Innovate or Integrate?</title>
         <description><![CDATA[<p>I sometimes hear about Creative Pros who - in an effort to save money - decide to use open source applications instead of <a href="mailto:http://www.adobe.com/creativelicense/">Adobe's Creative Solution products</a>. I come from a company that believes strongly in open source. I actually was the guy that helped open source the <a href="http://www.sun.com/software/solaris/get.jsp">Solaris operating system</a>, arguably the crown jewels of the <a href="http://www.sun.com/">Sun Microsystems </a>software product portfolio. Open sourcing Solaris allowed that community to do what they really loved - tinker with the code to their hearts content. It made sense to open source Solaris for that community and in the right circumstances, I absolutely believe in the model. </p>

<p>And obviously, I have thought about whether open source has a place in Adobe's creative products strategy. But what designers need is tightly-integrated workflows and high reliability right out of the box so the really important question to ask is what's the impact to the user. Yes, clearly it's cheaper, but does it really save money in the end? <br />
 <br />
I read a really interesting blog written by <a href="http://www.dangerousmeta.com/?p=14373">Eric Vreeland</a>, a creative professional who works across print, web and video - virtually all of the CS3 product line. His description of the time it took to manage the lack of interoperability between those products, reduced feature sets, differing interfaces of the various free products, inconvenient file formats, etc. really gave me some insight into his business. He used so much of his time "fixing" all that free software that the savings on the cost of the software evaporated incredibly quickly. Time he could use on new projects - and by the way, bill to a customer to help drive up his bottom line - was taken up being his own system administrator and software integrator. <br />
 <br />
In the end Eric decided that the open source products had too big a cost to him for this set of tasks, and he bought our <a href="http://www.adobe.com/products/creativesuite/mastercollection/?promoid=RVKI">Master Collection </a>-- an integrated suite of some 12 individual products like Photoshop, Illustrator, Dreamweaver and Flash software, all with a common user experience, interface, installation, etc. He found he could spend his time taking full advantage of not only rich feature sets but the incredible integration of the products. Less time on getting things to work meant he gets to spend more time on what he really loves. Being creative. <br />
 <br />
Don't get me wrong, open source software can be a perfect solution. It's just not right for everything. Or for everyone - like many creative professionals who are on deadline and prefer to innovate vs. integrate.</p>

<p>For people like Eric, it has become clear. Less time per project. More time spent on the work he loves. More dollars to the bottom line. Priceless. Just proves the old adage. Time is money.  <br />
</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/08/innovate_or_integrate_3.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/08/innovate_or_integrate_3.html</guid>
         <category></category>
         <pubDate>Thu, 16 Aug 2007 05:40:00 -0800</pubDate>
      </item>
            <item>
         <title>Adobe and FedEx Kinko&apos;s Update</title>
         <description><![CDATA[<p>As I said in my last blog, we promised to look into what we could do to address the concerns raised by the print industry regarding the deal we signed with FedEx Kinko's.  We’ve done that. <br />
  <br />
Adobe announced today that we will release an update of Adobe Reader and Acrobat Professional which will remove the "Send to FedEx Kinko's" button from those products. The update will be released in about 10 weeks. I know that there are a lot of folks who will be asking why we can't do it this afternoon. The answer is we can't just go back to the 8.0 release since the 8.1 release that contains the button included a lot of critical security and quality updates in addition to the new print option. We have determined the best way to move forward is with an 8.1.1 update. We have moved as many people as we can on to the project, but it takes time to do the standard testing that is required to ensure that we don't cause more problems by not performing sufficient testing. <br />
 <br />
We made a commitment to the print industry to address the concerns they raised about the FedEx deal. We made a commitment to all our customers to deliver the best, most secure product possible. We plan to deliver on both those commitments, and it takes time. <br />
 <br />
I'd like to acknowledge that FedEx Kinko's really went the extra mile to work with us to come to a resolution.  They could have taken a tough line, because we do have a formal contract, but they showed a lot of class and understanding about the concerns within the print community. I do want to say that FedEx Kinko's has a great vision for enabling worldwide remote printing to increase speed and convenience for their customers. So I'd like to give my personal thanks to the team at FedEx Kinko’s.<br />
 <br />
Thanks to those of you who have shared your ideas on how to resolve this issue and thanks to everyone for your patience as we addressed the concerns. </p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/08/adobe_and_fedex_kinkos_update.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/08/adobe_and_fedex_kinkos_update.html</guid>
         <category></category>
         <pubDate>Wed, 01 Aug 2007 16:00:00 -0800</pubDate>
      </item>
            <item>
         <title>Lessons Learned</title>
         <description><![CDATA[<p>The last several weeks have been weeks filled with a number of painful lessons learned. </p>

<p>Some of you might have seen the announcement we made with FedEx Kinko's regarding putting a "Send to FedEx Kinko's" button in the 8.1 version of Adobe Reader and Acrobat Professional. And you might have also seen the blogs and articles about the reaction of many members of the print community. The reaction was immediate, strong, and negative. That was our first lesson learned.  We met the objective of developing new business opportunities for our technology and addressing a customer's print workflow problem, but did not engage with print industry thought leaders and influencers early in the deal cycle to determine how to best implement the program. We have a long-standing, very supportive relationship with the print community, so getting their input should have been baked into the process.</p>

<p>Bruce Chizen, Adobe's CEO, immediately acknowledged that our process, and therefore the end result, was flawed.  We received a number of letters and emails letting us know just how problematic this is for print service providers, universities, government agencies, etc. We initially attempted to respond to each and every email.  But as the volume built, we had to resort to a standard letter and a posting on our website. Another lesson learned. Immediate response is great, but the community wants action -- and quickly.  What we really needed to do was sit down with them and have a conversation to see if we could find some common ground. </p>

<p>So Tuesday, Bruce and I met with a representative group of print industry leaders. They were tough on us. Big time tough. They told us exactly how they felt and the hard truths of what this deal means to them.  We heard them.  And they clearly told us what their expectations for next steps are. They had a lot to say, we had a lot to listen to. At the end of the discussion, we committed to coming back to them within two weeks with a decision on how we will move forward. We are going to do everything possible to find a way to deliver a win - win situation on all sides. It's the right thing to do. Another lesson learned. </p>

<p>In the meantime, some good has come out of all of this. We finally got many of the industry leaders in the same room and we spent the last 20 or so minutes of the meeting talking about what we could work on together once we resolve this big hairy issue that is on the table. And we will resolve it. That's the other lesson learned. At the core, we all want to work together, support each other, and ultimately, succeed together. <br />
</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/07/lessons_learned.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/07/lessons_learned.html</guid>
         <category>General</category>
         <pubDate>Wed, 18 Jul 2007 19:10:36 -0800</pubDate>
      </item>
            <item>
         <title>Amazing Voices</title>
         <description><![CDATA[<p>I've told you I love talking to customers to get the real scoop about what's happening in the industry. But what do I love even more? Seeing how Adobe's products, combined with people who really care about helping kids change their lives, can make a difference. So a few weeks ago, I went to San francisco to meet with some kids and their teachers who are participating in a project we are calling <a href="http://www.adobe.com/aboutadobe/philanthropy/youthvoices/"><strong>Adobe Youth Voices</strong></a>. It's a multi-year international initiative to empower youth in underserved communities. The high school aged kids I met with are using our <a href="http://www.adobe.com/creativelicense/?promoid=RVHW">Creative Pro products</a> to explore and comment on their world. </p>

<p>There are programs in several parts of the US, the UK and India - and the one I visited is called <a href="http://www.adobe.com/aboutadobe/philanthropy/youthvoices/worksinprogress/#work3"><strong>Build San Francisco</strong></a>. It's a program that mixes academics with internships in architecture and design. This year the participants are researching and documenting through photographs and interviews the impact of globalization on the people and places close to them, whether it's the world of fashion, food... or even martial arts. It was a fascinating day as we met with volunteers, the teachers, and the kids. They are all incredibly passionate about what they are doing and that passion is contagious.</p>

<p>What I really love is the program is run like a true design studio - with real tools, real projects, real deadlines, real end products. Unlike most school assignments, if the client doesn't like the output, the students have to re-do the project. They don't just get a C grade and move on. They re-work, iterate, and alter until the client is satisfied. So the kids are learning a ton about how the real world works - and how even though they live in a world that faces issues of war, racism, poverty, and crime... they can make an impact. </p>

<p>And their work is amazing. I saw some early photography samples that I'd love to hang on my wall! Really compelling work. I can't wait to see the final photo essays and the book from these kids and the kids in Noida, India working on a similar project. You can check out some of the <a href="http://www.adobe.com/aboutadobe/philanthropy/youthvoices/worksinprogress/#work3">practice photos from the BSFI students </a>and some of the <a href="http://www.whatkidscando.org/specialcollections/adobeyouthvoices/index.html">truly amazing and moving final products </a> from many of the groups of kids around the world and learn more about the program. I'd love to hear your comments on the work you see on the site. This is a project that really makes a difference and that I'm going to stay close to - so you'll be hearing more from me about Adobe Youth Voices and what the kids participating around the world are accomplishing. </p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/06/amazing_voices.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/06/amazing_voices.html</guid>
         <category></category>
         <pubDate>Tue, 26 Jun 2007 13:45:28 -0800</pubDate>
      </item>
            <item>
         <title>kuler talk confessional</title>
         <description><![CDATA[<p>One thing we are working really hard at is reaching out and being more open, interactive and relevant to our customers with things like the pre-release beta programs for <a href="http://www.adobe.com/products/photoshoplightroom/">Lightroom</a> and <a href="http://www.adobe.com/products/photoshop/photoshopextended/?xNav=MCPSX">Photoshop CS3</a>, and now for the most recent beta of <a href="http://www.adobe.com/products/soundbooth/">Soundbooth</a> - as well as open sourcing our technologies such as <a href="http://www.adobe.com/aboutadobe/pressroom/pressreleases/200611/110706Mozilla.html">Tamarin</a> and the <a href="http://www.adobe.com/products/flex/sdk/">Flex SDK</a>.  And we're getting far more community involvement, with a far broader audience than we have ever addressed. And nothing is cooler than, well, <a href="http://kuler.adobe.com/#">kuler</a>. </p>

<p>I was checking out some of the web forums the other day and came across <a href="http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid=72&catid=622">kuler talk</a>. This is the online forum for our new free online service to create your own color themes, browse color themes created by others, and share your creations with the kuler community, now over 150,000 strong!  What I read there absolutely stunned me—in a positive way.  I never thought I'd see the day when someone described themselves as being "addicted" to an Adobe product. But that's what has happened. </p>

<p><a href="http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=622&threadid=1262313&enterthread=y">Boyd Wiebe</a> , one kuler member said "I don't really consider myself an addict, <strong>yet</strong>", but acknowledged his immediate family was starting to wonder about his usage. Six hours straight on Kuler... Boyd, let me just say that admitting the problem is the first step in the 12 Step Program!</p>

<p><a href="http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=622&threadid=1262313&enterthread=y">CBuckley</a> calls herself a "kuler addict.” She's not into denial. I think that when she struggled to reduce her number of published themes from 63 to 36, she knew this was serious. And now she's building up her library again. To her, I say, “We've got plenty of storage space. Keep creating!” </p>

<p>And then there are the folks who are using kuler in interesting ways. <a href="http://lenkocambria.livejournal.com/91904.html">Lou*ser </a>is going to paint his house "using sweet color schemes from Adobe kuler.” My personal favorite is another kuler talk post by <a href="http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=622&threadid=1259159&messageid=4544811">jaynan.narayanan </a>who has been using kuler along with a few of his colleagues to make interesting rather than "traditional color combinations.” The good news is his wife likes the site too and has begun to spend time there with him —so I’m guessing it’s been good for his marriage. </p>

<p>kuler: Explore your colors, share your creativity, save your marriage. But do be careful as we are still searching for the antidote. </p>

<p>By the way, what you see in kuler, an online hosted service application, is just the beginning. Stay tuned for additional wildly successful web services that will augment the incredible foundation of the <a href="http://www.adobe.com/creativelicense/">CS3 Suites </a>and point products. <br />
</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/05/kuler_talk_confessional_5.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/05/kuler_talk_confessional_5.html</guid>
         <category></category>
         <pubDate>Wed, 09 May 2007 08:42:00 -0800</pubDate>
      </item>
            <item>
         <title>The Ecosystem: Turning a &quot;Wow&quot; Product Into A &quot;Wow&quot; Platform</title>
         <description><![CDATA[<p>When the daily challenges of running a business bog me down, the best pick-me-up is to go out and talk to (and hang out with) customers and partners. There's no better real-time feedback of how well, or poorly, you're doing. One great place I love to use for getting a finger on the pulse of our digital imaging busines is <a href="http://www.photoshopworld.com/">Photoshop World</a>. It's a well-attended, growing, and fun event that rotates coasts every six months. And it's run by a bunch of crazy, passionate, lunatic fringe folks. My kinda people.</p>

<p>I did the keynote at the most recent event in Boston. The enthusiasm for <a href="http://www.adobe.com/products/photoshop/photoshopextended/?xNav=MCPSX">Photoshop CS3</a>, and the newly announced <a href="http://www.adobe.com/creativelicense/">Creative Suite 3</a> was amazing. It was the FIRST time ever that they sold out the show. Every breakout for every track -- sold out. There were people lined up in the halls trying to get in to some of the most popular sessions.  And the first ever Birds of a Feather session for medical and scientific pros had more than 80 people show up for it!  </p>

<p>As proud as we are of Photoshop CS3, and the new Extended version, it was clear that just as important to our success is the ecosystem of complementary technologies that make Photoshop World a "world" and not an "island". Walking the show floor was a great reminder for me of how our partner offerings continue to grow and support new and innovative ideas for designers around the world. Many of our long term partners were there showing their newest products, which was great. But as we passed one booth, an employee handed me a flyer for their new product and said it was "brand new... just 2 hours old".  They were launching their company's first product right there on the show floor at Photoshop World.  Their press release went out as the show opened. At another booth, I got a demo for a new input device that was just a prototype, but is expected  to ship early next year.  Brand new company. Brand new product in development. Brand new ideas all adding to the value of our products to our customers.   </p>

<p>And the sudden flood of 3D companies that are coming out of the woodwork with products that support and expand the new 3D capabilities in Photoshop CS3 Extended is just mind blowing. <a href="http://blogs.adobe.com/jnack/2007/04/great_3d_addons.html#comments">John Nack </a>has already blogged about some of these. Check it out.  </p>

<p>We strive to build wow products. At the same time, we want to provide an open ecosystem that creates opportunities for new growth in the community that makes a wow product become a wow platform.  This open approach, including using techniques like the very successful open public beta of <a href="http://www.adobe.com/products/photoshoplightroom/">Lightroom</a> has proven incredibly valuable and we hope to do more along those lines. </p>

<p>Amazingly supportive customers. Incredibly innovative partners. Adding the zaniness of Scott Kelby, the president of the <a href="http://www.photoshopuser.com/">NAPP </a>(National Association of Photoshop Professionals) performing Motown's greatest hits -- backed up by the "Histograms" (a geek version of the "Pips") made my trip  to Boston  a worthwhile venture. I'm just thankful I was not asked to lip-sync with Scott and the Histograms. I only play one musical instrument. The stereo. </p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/04/the_ecosystem_turning_a_wow_pr.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/04/the_ecosystem_turning_a_wow_pr.html</guid>
         <category></category>
         <pubDate>Mon, 23 Apr 2007 10:55:06 -0800</pubDate>
      </item>
            <item>
         <title>The Glitch</title>
         <description><![CDATA[<p>I don't know about you, but no matter how many times I've spoken in front of large crowds, I still get nervous before walking on stage. I fear tripping while strolling away from the podium, or just tripping up on what I'm supposed to say. Haven't physically stumbled yet, but it's probably only a matter of time. If<u> I </u>wasn't going to be the problem, what was? There's an old adage in tech, if you're looking for something to go wrong, just include demos in your presentation.  And I had a ton of great demos. <br />
 <br />
So there I was. March 27, 2007. "The biggest launch in <a href="http://www.adobe.com">Adobe's</a> history", we kept saying. My first big launch here. I made it to the stage without tripping. OK, that's good.  We had a few hundred in the local audience, and another 17,000 - 20,000 viewing live on our <a href="http://www.adobe.com/go/cs3launch">webcast</a>. Everything was working the way it was supposed to - just like in all the rehearsals.  A bad sign. That never happens. We had the appropriate oooohs and ahhhhhs in all the right places. The demos were flawless. We were even right on time (another rare ocassion in a launch event). Life was good. <br />
 <br />
And then, the grim reaper of stage events raised his ugly head. When I first glanced up to see a light static snow storm on the screen, I just assumed we had a little signal interference. But it continued. I glanced at the guy directing the show. He was sweating and yelping into his headset mic. Not good. The static got worse to the point where almost the entire screen was static. No demo. Just static. Really not good.<br />
 <br />
Although we were demoing with Internet Explorer, this wasn't the "blue screen of death" at work. In fact, it wasn't anybody's software. It was a fried video router. Hardware!   After a bit of softshoe and stallling, we had no choice but to stop the show.  <br />
 <br />
For those in the room, it was a simple 20-minute intermission, complete with free refreshments. But for the people viewing online, I was really disappointed. Good news was the webcast traffic didn't drop off as much as I expected, maybe 20%. Amazing when all the web audience could see for 20 minutes was event participants wandering aimlessly around while the AV folks were madly (and I do mean madly) trying to find and fix the problem. But they got it up and running. And the rest of the event went flawlessly - if a bit longer than anticipated. <br />
 <br />
I look at it this way. In 10 years Greg (my demo partner) and I will look back and remember the famous glitch in the CS3 New York City launch event. If we'd had no issues, we would have claimed it was just another great stage event...no hiccups, no snafus, no failed routers... And no story to tell.      </p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/04/the_glitch.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/04/the_glitch.html</guid>
         <category></category>
         <pubDate>Fri, 06 Apr 2007 09:55:53 -0800</pubDate>
      </item>
            <item>
         <title>WHAT A DAY!</title>
         <description><![CDATA[<p>It's the culmination of some of the best work that I have seen in my entire career. <a href="http://www.adobe.com/go/creativelicense">Creative Suite 3</a> brings together what I can only say are  some of the most compelling and cool products on the planet. Former Macromedia products and Adobe  creative tools  that were  already best-in-breed point products have been enhanced with an incredible set of new features and now provide seamless workflow integration.  And not just <strong><u>within</u></strong> the individual <a href="http://www.adobe.com/products/creativesuite/design/">design</a>, <a href="http://www.adobe.com/products/creativesuite/web/">web</a>, <a href="http://www.adobe.com/products/creativesuite/production/">dynamic media</a> workflows - but <strong><strong><u>across</u></strong> </strong>those workflows as well.  Even more, we've added a number of all-new products and technologies, such as the new <a href="http://www.adobe.com/products/photoshop/photoshopextended/">Photoshop CS3 Extended</a> (which pushes image manipulation to new heights with the addition of video, 3D and measurement and analysis); <a href="http://www.adobe.com/products/soundbooth/">Soundbooth</a> (a new, intuitive audio tool specifically for video pros); and <a href="http://www.adobe.com/products/creativesuite/devicecentral/">Device Central </a>(which allows you to check how your image/web application/video will look and act on any number of mobile devices). Some 200+ profiles are included.<br />
 <br />
The work on all of this began just 15 months ago when the <a href="http://www.adobe.com/aboutadobe/pressroom/pressreleases/200512/120505AdobeAcquiresMacromedia.html">acquisition of Macromedia</a> happened. There was work going on in each company before that of course - but the real work to deliver on the promise of the  acquisition - the integration of not only the two companies and its employees, but the integration of great products into a greater whole - began just  over a year ago . <br />
 <br />
<strong>And now you have to just see it to believe it.</strong> Getting ready for todays' launch, I had 20 or 30 hours of demos to choose from. Cool, awe-inspiring, WOW demos. It was like being a kid in a candy shop trying to decide what to include in the event.  If you get a minute, log in and watch the launch today - it's being <a href="http://www.adobe.com/products/creativesuite/launchevent/webcast/">webcas</a>t live and will be available for re-broadcast a few hours later.  Rather than having me babble on, we'll let the products speak for themselves. They should take up 75-85 percent of my stage time. That's better for all of us. And while you're there, check out the rest of the website to see the demos and products I don't have time to show. <br />
 <br />
I've been heard to describe todays' announcements as the "biggest launch in the history of Adobe". That's true from the number of products: 13 point products, 6 suites, 9 key technologies, 2 services. It's true from the number of people working on it all. It's true from the number of lines of code, 80-90 million lines as best I can calculate .  I can best summarize it with three "I's". <strong>INTERACTIVE</strong> and engaging content design/development. <strong>INTEGRATED</strong> products within and across the key workflows, and <strong>INSANELY</strong> cool products.  <br />
 <br />
Take a look at the <a href="http://www.adobe.com/products/creativesuite/launchevent/webcast/">webcast</a>. You'll be impressed. I'm absolutely sure of it. I'll be blogging regularly on the products, what our customers are saying - and what's next. Stay tuned. <br />
</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2007/03/what_a_day_1.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2007/03/what_a_day_1.html</guid>
         <category>General</category>
         <pubDate>Tue, 27 Mar 2007 10:03:07 -0800</pubDate>
      </item>
            <item>
         <title>Anyone Care About CS Native on MacTel?</title>
         <description><![CDATA[<p>Apologize for the tardiness in my next entry. It's strategy planning season and I'm neck-deep in understanding and delivering what's next for Adobe's Creatives Business.</p>

<p><strong>Photoshop World</strong><br />
Just returned from my first <a href="http://www.photoshopworld.com">Photoshop World </a>and my first keynote in my new role. There is good news and bad news about standing in front of 3,000+ people who have deeper knowledge than you about your own products. Some of the interesting facts are that the show, put together by the NAPP (<a href="http://www.photoshopuser.com/">National Association of Photoshop Professionals</a>), is the largest in its 14-year history, even ahead of the numbers during the dot com boom. My new best friend Scott Kelby (NAPPs president) roasted me well in his introduction. I asked him not to use my corporate bio as a reference point since I find them to be ultimately boring. When Scott asked what I recommend as an alternative. I suggested that he just make something up. "Tell them I was an astronaut, then professional baseball player, then part-time open heart surgeon prior to coming to Adobe. See if anyone's awake at 9 a.m." He took that as a challenge and proceeded to introduce me, as best as I can describe it, in a style that was a cross between a presidential national convention and WWF (World Wide Wrestling Federation). I'm not usually at a loss for words, but this was one of those rare moments. It was great. I don't get mad, Scott, I get even. </p>

<p><strong>Lightroom</strong><br />
I polled the audience on a couple of subjects. Based on my guesstimates, it looked like about 70% were running Photoshop and/or the Creative Suite on the Mac platform. It was great to then see that about the same number were also running on Windows (many shops run both). I'd estimate about 60-65% of the attendees said they'd downloaded <a href="http://labs.adobe.com/technologies/lightroom/">Lightroom</a>. It's been astonishing to see the interest in Lightroom since we began making the Beta available early this year. Closing in on 350,000 unique visitors, half of those Windows, and we've only made the Windows version available for a couple of months now. </p>

<p><strong>Red Pill</strong><br />
I jokingly asked if anyone was interested in seeing us put Photoshop and CS natively on the <a href="http://www.apple.com/macpro/">MacTel</a> platform. Strangely, about 99% raised their hand and applauded. Hmmm. That prompted me to give folks a glimpse of "Red Pill", the code name for our universal binary version of Photoshop "next". This is a monumental effort within Adobe. Unfortunately (or fortunately depending on your view), we are not able to simply do a quick and dirty port of Photoshop to MacTel. Our customers have an expectation that we do an optimized, performant, killer implementation that takes full advantage of what the new hardware is capable. Therefore, we committed to, and are sticking with, our spring delivery. </p>

<p>All in all, a great couple of days in Vegas (a city I could easily do without). What was most enjoyable for me was the interaction with the passionate community that has made Photoshop what it is today. Meeting the Hall of Fame inductees, the NAPP staff, the trainers and guest speakers, the folks bending my ear on the show floor, the partners -- great stuff. You can build great products, but the real test of extensibility is how fast and broad an ecosystem forms to support and expand the product's success. There are few with more passion and who are more boisterous and opinionated than our Photoshop world.</p>

<p>Wouldn't have it any other way.</p>

<p>JohnnyL</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2006/09/anyone_care_about_cs_native_on.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2006/09/anyone_care_about_cs_native_on.html</guid>
         <category></category>
         <pubDate>Mon, 11 Sep 2006 12:13:38 -0800</pubDate>
      </item>
            <item>
         <title></title>
         <description><![CDATA[<p><em>I'm the new SVP of Creative Solutions. After 19 years at Sun Microsystems, I'm now a few weeks into what I hope to be a long run at my new digs. This is my initial blog entry.</em></p>

<p><strong>How Do You Eat an Elephant?</strong></p>

<p>I just sat through most of a 3-day internal marketing summit where our global corporate, field and product business unit marketing teams gather for strategy, motivation, skills development and time to interact (I heard there was also some evening parties and a few late night antics, but that can’t be confirmed just yet). As a former chief marketing officer, my experience is that no matter how good the speakers/content/breakouts are, most of the attendees find that just getting time to network with their brethren is the most valuable output. My second experience is that it can be very difficult to do breakouts for employees, who tend to be one or more of the following: pessimistic about anything you say; skeptical that anything will ever change; tired after flying in from Japan, India or the like; more excited about sampling the local drinking establishments than hearing about the best way to implement a direct mail campaign in Portugal. The breakout my VP of marketing and I hosted (“hosted” as in I just showed up), was a quick, hands-on and hopefully engaging exercise on the age-old common sense requirement: customer input. The outcome was in many ways just what was hoped for…people understood the value of why direct customer input is so important to how you create, build, market and sell your products. But the big epiphany for a lot of us what the comments that came when we asked about their thoughts on the exercise. The ah-ha was working on a problem that was narrow in scope, had a clear objective, was short in duration with a specific time limit, didn’t involve all the normal, tedious, pain-in-the-rear processes and approval cycles that usually kill momentum, and, had a result communicated right there in the room (award winners were named at the conclusion of the exercise). How we solve our internal issues is very similar to how any company addresses a huge, complex, seemingly overwhelming problem…carve it up into bite-sized pieces. You’ve heard the old adage, Q: “How do you eat an elephant?” A: One bite at a time. </p>

<p><em>So why did I come here?</em> The positive experience of our exercise, and the corresponding frustration that occurs when a similar process is carried out inside a company with real business issues is not unique to Adobe, or our industry, or any industry. In engineering if you want something to happen fast, task one individual to go away and come back when he or she has developed a solution. If you want to go even faster, isolate three people in a remote cabin (with power and a high speed internet connection) and turn them loose on the same problem. If you want to slow down the development, add 15 more people and double the budget. No magic in understanding that small, focused, motivated teams do better than huge monoliths. Both the challenge and opportunity with Adobe is 1+1=3. Adobe, by itself, is an interesting company with an incredible brand, really smart people and the ability to address the needs of the most creative people on the planet. But <a href="http://www.adobe.com/aboutadobe/pressroom/pressreleases/200512/120505AdobeAcquiresMacromedia.html">Adobe + Macromedia</a> is even far more compelling, with huge upside potential. If, of course, we are able to attack our new, bigger, more threatening challenges one bite at a time. That’s why I’m here, and welcome to my Blogic.</p>]]></description>
         <link>http://blogs.adobe.com/johnnyl/2006/06/post.html</link>
         <guid>http://blogs.adobe.com/johnnyl/2006/06/post.html</guid>
         <category>General</category>
         <pubDate>Tue, 13 Jun 2006 21:29:34 -0800</pubDate>
      </item>
      
   </channel>
</rss>
