Secret of Pixar’s Success [Link]

Secret of Pixar's Success
A friend of mine sent me this link to an article called The Secret Of Pixar’s Success (How to make great movies and billions of dollars) by Helen O'Hara.
Lessons learned
Besides being an interesting and worthwhile read I'd like to share my lessons learned and how they can apply to web design:
- Innovate (basically: use new technology when the time is right and only when it’s absolutely necessary but continuously try solving real problems, not inventing fictitious ones)
- Genius (have a great team)
- Keep learning (Field studies
- Fail early and often (Prototyping)
- Advice (Heuristic evaluation, expert reviews)
- Don’t be afraid of failure (should be part of the company culture to be successfully applied)
- Share (should also be part of company culture, but mostly isn’t)
Esri listens to their Users and changes Pronunciation of its Name
This is big!
Background
And here is why: ESRI, a privately held company with more than 2700 employees, was founded in 1969, over 40 years ago. The company name is an abbreviation for Environmental Systems Research Institute and therefore
not pronounced as a word but as distinct letters similar to IBM, SAP and other software companies with an acronym based name. It is thought within the GIS (Geographical Information Systems) circles, and even joked that 'old' users prefer E-S-R-I, while novice users use the 'ez-ree' pronunciation.
(from wikipedia, March 2010, which has its own section called "Pronunciation of company name").
Insides and Myths
Over time a divide elapsed, employees were proud to pronounce their company name E-S-R-I and by doing so showing they are insiders and distinguishing themselves from the 'newbies'. It became part of company culture and identity.
Rumor has it that the first week of orientation for new employees is to train them to say "E - S - R - I" spelled out instead of trying to pronounce it as a word (ez-ree), though I cannot personally confirm this. There's also been a rumor of Jack Dangermond [the presiding of ESRI] having a version of the "swear jar" on his desk, and anytime someone says "ez-ree" they have to put a dollar in.
Confusion
Around the world users were confused. While it seemed to be natural to pronounce the company name ez-ree, users found themselves being corrected and lectured: "It's not ez-ree, it's E-S-R-I". Hearing "It hurts me to say "ezree". =)" from employees were not uncommon.
Forum threads tried to shed light on the ongoing discussion and various sides were quick to elaborate about the correct pronunciation in (mostly humorous) detail, e.g.
- Here in San Antonio, my new home, it is pronounced "ess-ray y'all".
- In austria we say: äsri
- When I'm in a hurry- I say 'eS-ree', and when I'm trying to sound sophisticated and smart I say 'E-S-R-I'. Isn't that the way it always works?
- As for ESRI or esree I have always called it EE ESS ARE EYE.
- Lately I've noticed that people, who aren't sure of what they are talking about, pronouce it 'Uhh, [pause] Ezree' or '[PAUSE] Eszree'. The pause before gives it away...
- Canadian pronunciation: ez-ree-eh?, or ee-ess-arr-eye-eh?
- One thing I've noticed, though, is that the tendency to elide sounds has some people pronouncing E-S-R-I rather like yes-are-eye (without the y). Will the next step in this evolution be yes-rye? (Then the only question will be Do you want that with mustard?)
- Down Under we say 'Bloody ezree' when things go ferral.
Change and Resistance
To the surprise of many employees an internal notice from 3/19/2010 read:
[...] we will be transitioning the pronunciation of ESRI to “ezree.” This effort will ensure a consistent name recognition around the world.
What followed was a big uproar from the employees side. Many of us felt robbed of our identity and culture. What seemed to work well for over 40 years should not be changed and trashed that easily!
Success
As it turned out, after merrily 4 months and a hugely successful User Conference with almost 14.000 people (the biggest gathering of GIS professionals ever) the name change was perceived as a relief by the user community. A sense of unity was felt, finally we speak the same language, the confusion was lifted, no more lecturing, no more division between insiders and outsiders, everybody became part of the family.
Esri stepped into icy waters and in risk of p***ing some of its own employees off it opened a new world of opportunities by Speaking the Language of Its Users - I'm loving it!!
What do you think?
Have you ever heard of a comparable change / step taken? Could you imaging IBM spelled Ei-bm?
Designing a Stop Sign [Video]
aka 'Welcome to my life'
Disclaimer: Any similarity to projects and designs living or dead is purely coincidental.
PS.: My absolute favorite is the dude swallowing his snack "...and a web address, in case people want more info".
Job Posting: User Interface (UI) Engineer at ESRI
We are actively looking for a full-time User Interface (UI) Engineer here in Professional Services (Applications Development Services) at ESRI.
If you feel qualified and are interested please send me your resume to mgaigg at esri dot com. I'm also happy to answer any kind of question (except payment) you might have.
My job here
A little bit about what you can expect here: In my daily job I consult, design and help implementing customized web applications that are for the most part based on our core mapping products and API's for JavaScript, Flex and Silverlight. Clients range from local and federal government to vertical markets like energy, water, environmental, etc. and reach local, domestic and international audiences - the challenges are never-ending, I promise
You can become part of this group!
Job Description
Use your technical background and innovative visual design skills to simplify complex business processes through the creation of intuitive and visually engaging user interfaces.
Responsibilities
- Create sophisticated, imaginative, efficient, and visually striking interfaces for front-end solutions
- Design reusable UI components by utilizing or building UI framework components
- Develop storyboards, mock-ups, and prototypes to communicate ideas for navigation and interaction models
- Evaluate requirements and initial mock-ups; make technology recommendations that support optimal construction, maintenance, and performance
- Translate complex functional and technical requirements into detailed architecture and design prototypes
- Ensure cross-browser/platform integrity of Web designs
- Work closely with software developers and software testers to create a working end-to-end solution
- Define, maintain, implement, and enforce style guides, standards, reusable templates, and best practices for client-side software development
- Leverage the latest developments in Internet technologies
- Serve as a technical resource and mentor
Requirements
- Bachelor’s or master’s in computer science, graphic design, visual design, human factors engineering, interaction design, information architecture, or other relevant field
- A minimum of five years of experience in user interface design, information architecture, user-centered design methodology, and implementation in complex enterprise environments
- Significant and proven experience demonstrating innovative UI visual design skills
- Ability to balance designs with the understanding of technical constraints within a software development environment
- Highly proficient with cross-browser/platform CSS, HTML, XHTML, and JavaScript; knowledge of browser compatibility issues and their workarounds
- Extensive experience using JavaScript libraries such as Dojo and jQuery
- Good understanding of user experience (UX) and user-centered design (UCD)
- Ability to take a concept from sketch to final implementation
- Ability and willingness to take ownership of projects and help drive them to effective implementation
- Exceptional attention to detail, organizational, communication, and presentation skills
- Passionate about novel user interface design and software development
Recommended Qualifications
- Experience with GIS/ESRI products and solutions
- Experience with .NET, C#, Silverlight, and Expression Blend
- Experience with JSP, Java Web frameworks, Flash, and ActionScript
- Experience with Linux, PHP, and MySQL
- Proficiency with Adobe Creative Suite including InDesign, Photoshop, and Illustrator
- Ability to interface with customers, gather requirements, and implement new solutions
Employment Fraction
Full-time
Work Location
ESRI Headquarters, Redlands, CA
HTML5 and the Future of Adobe Flash [and Silverlight]
Really interesting research note by Gartner.
Key findings:
- HTML5 will become the mainstream of the Web during the next decade.
- HTML5 is a potential threat to the continued adoption of plug-in based RIA approaches (including Flash/Silverlight).
Recommendations:
- Enterprises should try avoid becoming dependent on any one browser or client-side technology.
- Enterprise developers should “design for standards” and not browsers or runtimes.
- Developers should favor the lightest-weight technology that will meet their requirements.
- Architects should consider hybrid approaches […]
- Before purchasing or committing to a new UI technology or platform, enterprises should first invest in a user-centered design process based on objective data about user behavior.
Complete Analysis: http://www.adobe.com/enterprise/pdfs/html5_flash.pdf
On a personal note I especially like the following part (btw: brilliantly written):
Help creating the Ultimate (midnight coders) Music Compilation!
Help creating the Ultimate Music Compilation
I need your help! What is your ultimate "Get-on-track-song"?
Working late hours, dealing with brutal clients, blacking out over an impossible bug or passing out on the keyboard, sounds familiar? Ever since music cheered me up, changed my mood, told me to look on the bright side or just lifted my spirits and carried me away for a moment so I could successfully continue or start over again.
Yes, I do have playlists for every mood and task, and sure enough I have my favorites. But I figured, I would love to create the ultimate compilation and I for that I need your help!
Suggest a song that cannot be missed
Tell me, what is your favorite song and why? Add it to the comments section and I will consider it for the final selection.
Compilation so far
Towers of London - F**k it up!
As really mellow version of the original hard rock it helps you easing the pain after a co-worker has f**ked up something (usually breaking the code that you've finally finished after days of hard work) and freeing you of wishing this person a slow and painful death.
Twisted Sisters - Were Not Gonna Take It
Enough is enough. Man, do those feature requests drive me nuts. A button here, a label change there, one user couldn't see that image - no, we're not gonna take it... anymore!
Chumbawamba - Tubthumping
"I get knocked down, but I get up again." What else could serve as a better psycho-hygiene. Sing along, well, shout along and feel the air ventilating your brain again. Yes, it's not that bad, you will get up again.
UIE Web App Masters Tour
I've been fortunate enough to visit the UIE Web App Masters Tour in San Diego yesterday and today. It's great to see outstanding speakers like Luke Wroblewski (Yahoo!), Stephen Anderson, Julie Zhuo (Facebook), Bill Scott (Netflix), Mark Trammell (Twitter) and others. This is the first of 4 events on the tour with Minneapolis, Philadelphia and Seattle coming up.
Besides meeting fascinating people and hearing lots of good stuff one of my take-aways so far is that web design is shifting. It's been shifting from UI (interface design) and UX (the overall user experience) to social design. It's about the community and not only the individual anymore. It's about communication between many and not presentation of the single per se.
Interesting stuff. Hope I get the time soon to detail out some more.
15 Outstanding Examples of Braille in our World

Braille can be found everywhere. Some findings are real gems, love the McDonalds braille lunch menu which is even advertised on drive-through windows in corporate locations - yes, exactly, didn't know they had driving test in braille yet. I'd actually opt for scratch and smell menus at McDonalds - ok, that's just me
Love the braille bikini as well. Enjoy!
Presentation: Wiki – the right tool for my organization?
Finally I got my head around posting a presentation I gave last March. The title is "Wiki - the right tool for my organization?" and had the purpose of introducing the concept of a wiki to a group that was about to install a wiki within their department.
Background: About three years ago I went through the effort of evaluating existing wiki platforms, installing/hosting it for our department and keeping it alive for the next two years before it got sacked. I'm here to tell you why it didn't work out in the end.
Characteristics
I jump right into the characteristics (the slide "Characteristics" is duplicated in the presentation on purpose) because I found understanding them key to a successful implementation. That's why once more I want to emphasize on the issues that need to be met in order to successfully implement a wiki, for example if your company has no culture of sharing content or employees are reluctant to give up ownership of their code, a wiki is most likely not the ideal collaboration tool.
These are the characteristics of a wiki:
- Perpetual work in progress
- No one owns the content
- No specific organization (hyperlinks)
- Anyone can edit other people’s work
- Discussion area for each page
- Version control: list of all changes made to a page
Critical Success Factors (aka truth about a wiki)
Only implement a wiki if you feel comfortable you can meet the following critical success factors:
- Only 10% contribute; only 1% on a regular basis.
- Obey the characteristics of a wiki
- Power to the people
- Trust the user
- Authority to change something
- Refuse defined structures
My previous experience taught me that implementing a wiki into your organization is doomed to fail if one is not aware of their importance and therefore
- overestimates the reach and participation,
- neglects the characteristics of a wiki,
- or doesn't want or cannot give power to the people.
The truth is, only 10% of users contribute to a wiki and only 1% on a regular basis. If you have 100 employees you can expect between 1 to 10 of them to contribute and the rest to consume - which in turn will lead to lesser contribution and lesser consumption over time. Wikipedia works well because there are millions of users where 1% is still significant number to keep up quality content.
The argument of mandatory (or even monitored) participation runs directly against the characteristics of a wiki, is counter-productive and will result in your wiki failing.
Choosing a wiki: What to consider
Obviously there are many criteria and features that will directly affect your choice. I recommend Comparison of wiki software as a starting point for finding the right software but I wouldn't be surprised if you ended up with MediaWiki which is the used by wikipedia for one simple reason (besides its free usage under the GPL license and its huge community): the MediaWiki syntax is widely used and makes actually sense to learn - because it is wikipedia
Criteria
- Cost (open source license)
- Programming language (PHP, C#, Java)
- Data backend (File system or DB)
- Extensibility & user community
Features
- WYSIWYG editing & Syntax
- Version control & Discussions
- Permissions & Security
Keys to get a wiki going
Once you've decided to go ahead and install a wiki, what can be done to make it successful?
- Find dedicated helpers
- Partner with groups/people related to your mission
- Offer structural templates for new pages
- Add some content to major categories
- Do lots of marketing
- If possible, offer training
Do you work with wikis?
What are your experiences? Do you use a wiki in your company? How do you use it?



















