Archive for February, 2011

“Like sands through the hourglass….”

Big Techmeme cluster today, prompting headlines of “What’s Going On, Adobe?”… seem to be triggered by this Engadget blurb: “Verizon’s webpage dedicated to the Xoom has just gone up and one of our eagle-eyed readers has already spotted a disquieting bit of small print: ‘Adobe Flash expected Spring 2011.'”

I don’t know Motorola’s schedule myself, but it’s usually better to wait for actual news than to get all excited about a partner’s little snippet.

The important thing is that humanity is now on the verge of universal connectivity through personal displays. The trend is for common high-performance among them — with hardware, OS, engines, distribution, and business models all evolving simultaneously to attain this. Hot “Brand X vs Brand Y’ debating may bring in click-revenue from early adopters, but is less important in the long run than how we’ll end up using these new communication abilities. That’s the real priority for attention now.

Update: Matt Rozen has more on how the early Honeycomb releases will go: “Adobe will offer Flash Player 10.2 pre-installed on some tablets and as an OTA download on others within a few weeks of Android 3 (Honeycomb) devices becoming available, the first of which is expected to be the Motorola Xoom.” Estimates for 2011 total shipments have risen recently, too.


Doing the usual news searches, came across a headline with above title, but kept on being redirected to various reprints… Google Websearch shows many hits, all low-value.

Going to what appears to be the canonical link, the story in whole seems to be the headline: “FLASH IS OFFICIALLY DEAD: This super interactive Nissan Leaf site is all HTML5.” The whole is linked to this Nissan USA site, which in my current FF/Win comes up as Flash, baby.

Takeaways? Flash doesn’t seem as “dead” as do for-pay bloggers and the whole weblog news culture. Look at the noise they generated, on how little thought! Look at how few costs they pay in return for increasing all readers’ costs! Look at what has been done to search engine results! And look at how the bloated Business Insider sites so frequently fail to complete loading, as they make unnecessary third-party calls to,,,,,,,,,,, and many many more cross-site tracking web beacons.

Hot headline, startlingly poor observation, no real argument, no feedback mechanism, but lots of slammin’ the SEO and social media channels with self-serving, public-penalizing bloviation… the writer makes a good case that it’s the web which he’s actually killing.

Blends of native and global

It’s not as simple today as it was when applications were developed for Windows, sometimes considering a Mac port, and wondering how Linux could recoup development costs. Now we have not only different form-factors (big multiscreen desktops, little pocket phones, in-between tablets and looming TVs) but we’re split on mobile between Apple OS, Google OS, Microsoft OS and other options. Fragmentation is big.

Some say the choices are “web apps vs native apps”. Some of the more enlightened also mention bridging technologies (AIR or other cross-device frameworks/compilers/runtimes). I don’t think it’s so cut-and-dried as “completely global” versus “completely native”.

For direct OS coding, unless you’re planning to deliver to only one brand of device, you’re going to divide up the work with both portable and native aspects… you’re going to make it easy to port to other environments later. You’ve got your core data structure, media assets and business logic, and then will handle specific devices in a separate layer.

Same when using the browser as your runtime, although inverted… here the instructions are mostly portable, but you’ll still have to build switches for slightly different runtime behaviors, or very different permitted services. The great variance in mobile HTML/JS/CSS performance pushes its promise of full-functioned cross-device compatibility off into the hazy future… you’ll have to handle the edge-cases.

That’s what I think it’s not “all native” or “all universal”. There’s always a blend between portable aspects and idiosyncratic aspects. People who argue polarities may not provide the best investment in listening time.

(Adobe’s role? To make it easier for creators to reach their audiences, however they choose to do so. Adobe tooling is used in even Microsoft-only development or Apple-only native-code development… used in most every webpage in the world… and Adobe also creates great runtimes for those seeking a more portable codebase with lower testing and support costs. Adobe supports varying blends of native and global — your choice.)

Adobe Culture, Geschke, 1998

In 1998, Quark sought to acquire Adobe, and the company underwent a massive reorganization. Adobe co-founder Charles Geschke sent out the following memo about what type of business culture he wanted to create. He also included “Adobe’s Core Values and Beliefs” from 1988 beneath it. I still hear these driving principles regularly discussed inside Adobe today.

This essay is already in the public record, a PDF hosted at Knowledge@Wharton, which I reformatted to HTML.


Adobe Culture

The principles that define us as an organization

Charles M. Geschke
September, 1998

The word culture is defined as the “refinement of thought, emotion, manners, taste, etc.” I’ve written this short essay to describe Adobe’s culture and to capture some of the characteristics that should guide us as we represent this corporation. The last section of the piece is a document first published nearly ten years ago describing the core values of Adobe. I think it applies as well today as it did a decade ago.

Many fine books have been written about how organizations can grow and operate effectively. This essay makes no pretense of replacing those excellent materials, nor does it attempt to define all the principles and attributes that should underlie Adobe’s business culture. The topics discussed herein are primarily those that are most important for us to focus on today.

A business built with intellectual capital

The raw materials from which our business is formed are the inventive ideas and creative talent of our employees. Adobe’s strong financial balance sheet is not based on assets such as factories, warehouses, storefronts, or mining and mineral rights. The capital assets of our corporation are our people who are skilled in sales, marketing, engineering, and administration. Therefore, the way we behave and operate our culture directly affects the financial success of our business.

The following paragraphs discuss specific activities as well as some of business characteristics that critically affect our ability to perform well as an organization.


The person who calls a meeting should clearly understand the necessity for convening it and be able to clearly articulate the purpose of the meeting to all those invited. Meetings generally fall into two classes: communication meetings and decision-making meetings. Meetings can easily be nonproductive when it is not clear to the convener and attendees exactly in which kind of meeting they are participating. Whenever possible, presentation materials should be distributed to attendees 24 hours before the meeting is held.

Decision-making meetings: These meetings should typically have no more than ten participants (preferably fewer). Someone should be appointed to take summary notes of the meeting and clearly record the decisions made and the follow-up actions that result from the meeting. These notes should be distributed to all attendees as soon after the meeting as possible. The convener (or a designee) is responsible for (1) communicating all decisions to those who need to know them (and did not attend), and (2) ensuring that follow-up actions are assigned to individuals and checking that those actions are completed.

Communication meetings: These meetings should be convened only when written communication cannot effectively convey the required information or when the opportunity to provide a forum for interactive communication and discussion of ideas is the primary purpose of the meeting.

As a global company, we constantly need to make and communicate decisions that involve participants from several locations around the world. Clearly, travel expenses for face-to-face meetings contribute significantly to our expense budget. But there are other hidden costs, including absence of the traveling participants from their local offices as well the negative impact on the quality of home and family life that result from extensive travel. Conveners should consider these factors carefully before deciding that face-to-face interaction is critical. We will continue to invest in infrastructure (broad-band networks, teleconferencing, etc.) to provide alternatives to face-to-face meetings.


If we clearly define who has the authority for making a decision after gathering input, then that decision should not be reopened for consideration except in extraordinary circumstances. As an organization, we have a habit of frequently reconsidering decisions. This creates confusion and delays effective implementation of decisions that many members of the organization believe have already been made. The Pathfinder project provided a framework (the RAID matrix) for eliminating this indecisiveness. If this framework does not work, then let’s work to find an alternative. However, the habit of continuously re-evaluating decisions, makes us an inefficient organization.


Going forward, we must adjust our spending levels to match our expectations for revenue growth. While the current economic crisis in Asia accentuates the issue, it is not the sole cause of our drop in profitability. Effective control of spending requires constant vigilance. Failure to control expenses has a direct impact on our earnings, growth, stock price, and profit sharing. Each employee has a role to pay in controlling our costs. We must apply the same careful thought to each dollar we spend from Adobe’s budget as we do to our personal finances.


A successful business organization must operate as a team, not as a loosely knit federation of individuals. Our corporate goal is to attract and hire the highest-quality employees. While each employee’s individual expertise and experience are critical criteria in the hiring decision, the overall effectiveness of Adobe can be maximized only when these individuals come together as a cohesive unit. This can occur only when each individual contributes to the overall objectives of the company by (1) understanding his/her role, (2) applying maximum effort to excel in performing his/her job functions, and (3) believing that each of his/her colleagues is performing at the same effort. Managers must (1) set clear direction and define each individual’s role, (2) monitor team performance, and (3) provide constructive feedback when individuals do not perform up to expected levels.


A successful manager must first be a leader. Leadership requires communicating a compelling vision, engaging the group in pursing that vision, and providing the resources and support necessary for success. Our goal should be to hire employees who are energetic, independent, and highly motivated. A manager should focus primarily on leading and not directing. A manager should work with his/her employees to set goals and objectives, measure progress, and evaluate performance. A manager is responsible for ensuring that his/her group operates in synch with the rest of the organization. The manager is therefore responsible for communicating the group’s direction and progress both horizontally and vertically within the organization. I ran across a quote from Ralph Nader: “The function of leadership is to produce more leaders, not more followers.” This quote parallels an Adobe principle often stated but not always followed that each manager hire his/her replacement. The implication is that to succeed in management, you should mentor your employees so that they can do your job as well as you can. Effectively replacing yourself is the most direct career path to a more senior management position in the company.

Global Markets

Adobe is a global company with an expectation that the majority of its revenue comes from outside the United States. While we operate locally, we must think globally. Business decisions that make sense in one geography may be completely inappropriate in another region of the world. Each functional unit in the company must understand its relationship with these global markets and take care to keep a worldwide perspective while pursuing its specific responsibilities. The global nature of our business places an even higher premium on effective horizontal communication throughout the organization.


Without trust, teamwork and leadership are worthless. To trust someone, you must know them. I have observed an insidious habit recently where groups or individuals are criticized by others who have not taken the care to investigate the underlying facts. This behavior erodes trust, which in turn disables teamwork. Unless we improve company-wide communication to provide the necessary information upon which accurate assessments can be made, we will not be able to build the level of trust required to effectively operate our business.


The most important virtue of Adobe’s corporate culture is honesty. The only sure-fire way to be asked to leave this organization is to knowingly fail to tell the truth.

On more than one occasion, an Adobe employee has remarked to me that our company stands out from the ordinary because its culture transcends the purely economic engines that characterize many other businesses. But, let us be perfectly clear — Adobe is a business. Maintaining a warm, supportive, caring culture is not the primary mission of this organization. To maintain the important components of our culture, we must commit to excellent, predictable financial performance. Over the past sixteen years, we have demonstrated a unique ability to achieve both goals. Although our financial performance has weakened in recent quarters, with your help and commitment, we can and will correct our course while maintaining the cultural heritage that defines Adobe.


Adobe Core Values and Beliefs

Adobe was founded on a set of core beliefs and values. As we grow, maintaining these values is critical to our continued success. When we were a small company, it was possible to communicate these values in person. The time has come to write them down for all of us to share.

  • Thrive on innovation — invent new technologies, define new markets, and build products that dominate.

  • Treat each individual with whom you interact as you would like to be treated. This fundamental principle applies to customers, vendors, and fellow employees.

  • For our customers: Deliver the best and most innovative products. License technology fairly and impartially. Maintain total confidentiality about each customer’s business. Provide the highest possible level of service.

  • For our employees: Hire the best. Treat them well. Provide a first class environment in which to work. Offer the opportunity to participate in the ownership and economic success of the company.

  • For our shareholders: Provide a fair return through predictable growth and careful husbanding of our resources.

  • For our community: Support charitable causes and public-benefit programs. Provide a good example of progressive employment and business practices.

The following pages illustrate these core beliefs as they apply to Adobe’s customers, vendors, managers, and employees. I encourage you to discuss them with one another and give me your thoughts on how to better communicate these ideals in the future.


  • Treat the customer as you would like to be treated.

  • Make the customer an ally, not an adversary.

  • Evaluate issues from the customer’s point of view.

  • Remember: your performance may have a major impact on the survival of the customer’s business.

  • Make the customer feel that we need his or her business.

  • Thank the customer frequently for his or her business.

  • “Reserve the right to be reasonable.”


  • Treat the vendor as you would like to be treated.
  • Make the vendor an ally, not an adversary.
  • Evaluate issues from the vendor’s point of view.
  • Do not exploit Adobe’s power to force the vendor into an untenable position.
  • Thank the vendor frequently for his or her support.


  • Treat your reports, as you would like to be treated.
  • Criticize in private; praise in public.
  • Hire people smarter than you.
  • Facilitate effective, efficient communication.
  • Decision-making meetings should be small.
  • Devote time to mentoring your employees.
  • Answer your phone in person whenever possible.
  • Keep your door and your mind open.
  • It is better to “coordinate” than to “direct.”
  • “A manager is responsible for working herself out of her job.”


  • Treat your fellow employees as you would like to be treated.
  • Remember that the major barrier to your career growth is you, not your colleagues.
  • Be a self-starter.
  • Whenever possible, work smart, not long.
  • Answer your phone in person whenever possible.
  • “At Adobe, everyone sweeps the floor.”
  • Keep your door open.
  • “People need to be reminded more frequently than informed.”