The merits of failing faster are integrated with taking risks. Successful innovations only come after many failed attempts. Marten Mickos, CEO of Eucalyptus Systems, explores the intersection of open source and innovation in a Technology Academy Finland (TAF) post "What is Innovation?"
"An innovation creates a new dimension of performance. It's not enough to improve performance. It’s not enough to create a new thought. A new thing is not an innovation unless it finds a new direction for performance." » Read more
This should come as no surprise: Open source principles are great guidelines for conducting successful collaboration sessions. What wasn’t as obvious to me was that the different principles are more important in different collaboration situations. Imagine the concepts of trust, openness, transparency, and release early, release often as ingredients in a mix, controlled by a row of dials. The environment determines how much you need to 'dial up' or 'dial down' each characteristic. » Read more
It's true. If you think about the characteristics of open source and the qualities of a successful relationship, you will find a lot of overlap.
OPEN: You have to be open and flexible to make a relationship work. Going back to my favorite analogy in regards to open source software and proprietary software--proprietary software is like buying a car with the hood welded shut. Oh, you need to change to oil? Too bad. Buy a new car. If we aren't flexible and open to change--if our hoods are welded shut--it makes it extremely difficult to keep the (love) engine running. » Read more
Usually when Facebook comes up at opensource.com, it's because they've done something that's very much the opposite of open. But a blog post on FrameThink this week showed Facebook's more open side. » Read more
I’m lucky enough to have the opportunity to spend much of my time these days doing something I love—helping clients position and manage their brands. My experience helping build the Red Hat brand over ten years had a profound impact on the approach I take to brand positioning. » Read more
As we've described before, we have a unique organizational model here at Red Hat in that we've combined the more traditional Human Resources and Corporate Marketing functions into a single department that we call People & Brand. Thanks to this structure, we are able to explore the places where our brand intersects with many different elements of our culture and associate programming, such as recruiting, interviewing, orientation, on-boarding, and training & development (among other things). » Read more
The open source community has a phrase for the principle of rapid prototyping: “Release early, release often.” The theory is sound: Don’t wait until a project is perfect to share it. Instead, keep producing work so more people can experience it, react to it, find bugs, and improve it.
But does the principle also work in a creative environment? Ideas are fragile. Their merit is judged not just on the idea, but the quality of the execution. Often they need to be protected just to get that far. All it takes is one naysayer to sweep the legs out from under your idea. » Read more
A few months ago, opensource.com ran a story on a textbook for college students learning programming (Can Professors Teach Open Source?, Greg DeKoenigsberg, Apr 6 2010). The textbook, "Practical Open Source Software Exploration," was created the open source way on the Teaching Open Source wiki. (Read Greg's article for more on what we mean by creating the textbook "the open source way".)
Although the textbook was written with students in mind, it turns out that professors are pretty important when it comes to teaching, too. » Read more
This is the third in a series exploring the things I have learned from the open source way during my journey with Red Hat.
One of the key tenets of the open source way is “release early, release often.” This means rather than keeping an idea or project "secret" until it is perfect, you go ahead and share it or make it available to others. You get it out there, let people play around with it, test it, expose its weaknesses, you allow peer review. » Read more
You may be familiar with the Thomas Edison quote: "I have not failed. I've just found 10,000 ways that won't work." In the open source way, the principle is sometimes referred to as rapid prototyping, or "release early, release often." The idea is that faster prototypes can lead to faster failures. And faster failures lead to faster solutions.
What do you think? Do you agree with the philosophy? And if so, how can we help organizations see small failures as steps toward big successes?
The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat.
opensource.com aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. Red Hat and the Shadowman logo are trademarks of Red Hat, Inc., registered in the United States and other countries.