Jump to content
There are 4 item(s) tagged with the keyword "collaboration".
Just caught this great article in the Economist about when products flop (fail spectacularly) in the market. This is on the heels of the most recent flop courtesy of the good folks at Disney Films, John Carter. $300M in $30M out. Ouch! Even for a company as large as Disney that one hurts.
One point the article makes is that in business, occasional flops walk hand in hand with successful products. Nothing ventured, nothing gained as it were. It's true that sometimes it takes a big risk to make a big hit. Still I wouldn't want to be the producer of the John Carter movie right about now. He just blew $300M; let another guy make that mistake.
The other day I had the opportunity to spend some time with a team of world-class CIOs of Global 2000 companies in a private setting and hear what they had to say about innovation when "nobody" was listening. Their comments were shocking.
Risk is the most popular characteristic of innovation. We recently mentioned how our nation's leaders associated risk with some of the greatest moments in American invention and there's no shortage of academic resources pushing organizations to take greater risks in order to innovate.
But risk isn't always good for your career.
Join us for a discussion with ideation expert and industry leader, Luke Hohmann, Founder and CEO, of Innovation Games, Inc., on how Innovation Games can enhance the Product Portfolio and provide higher visibility and stakeholder alignment. Innovation Games helps companies improve business performance through collaborative and cooperative play. As the leading producer of online and in-person Serious Games, we invite you to explore our site to learn how we can help you solve complex problems in Sales, Corporate Strategy, Marketing Strategy and Product Development.
Our webinar on Wednesday October 6th at 10:00 a.m. PT / 1:00 p.m. ET will offer a fascinating look at an innovative way to have serious fun doing serious business.
In my past two posts in the Scaling Agile series, I've written about the triangle of traps and the challenges of developing complex systems when scaling Agile development. Today I would like to focus on the impact and challenges at the team level when developers and product owners are forced to operate in dispersed and distributed environments – a situation that could impose serious dependencies and may have an impact on other teams.
Three points of impact