Showing posts with label Strategy. Show all posts
Showing posts with label Strategy. Show all posts

Monday, December 10, 2012

The Case Against Incremental Improvements In A Business World Turn Upside Down

Media_httpinfosthetic_rlhuw

I hear this from executives and workers all the time: "I understand that we need to innovate, but why now? I'm just trying to make it to the next quarter. This is the time to get back to basics." In theory, I don't object to getting back to basics. Every company has to grow revenue, raise prices (if it can), and cut costs. That simple arithmetic never changes.

But here is the shared dilemma: Most companies today can't grow revenue by force feeding the same old stuff to the same old customers through the same old channels in the same old way. People may already be eating as many hamburgers as they are ever going to eat, drinking as much beer as they are ever going to drink, even buying as many plain vanilla personal computers as they are ever going to buy.

You just can't grow revenue significantly -- unless you bring jaw-dropping new products and services to customers. And surprise surprise….your customers are internal (employee partners) and external. Unless employee partners are working in a state of discovery and awe, rather than archaic feardoms, remarkable competitive products leaving competitors whimpering, “What the heck” on Monday mornings won’t occur.

The choice for business is really quite simple. Get busy doing the things you know to do.

 

Hire Jim

Jim Woods is principal and founder of InnoThink Group. Jim is a business turnaround expert and personal coach. His story is riveting. He has worked with government, U.S. Army, MITRE Corporation, Pitney Bowes, Whirlpool, and 3M. Jim W experiences, extensive research on competitive strategy and innovation have given him a fresh perspective on improving individual and organizational performance. Jim is a prolific speaker on strategic innovation, creative leadership, uncertainty and competitive strategy. Speak with us for consulting or speaking engagements call 719-266-6703 or click here for more information. Follow Jim on Twitter. Follow Jim on Facebook.  

 

Monday, April 16, 2012

This Matters: How Microsoft grew into a giant

The tech giant was a no-name startup when it launched its MSDOS operating system in the 1980s. But the open environment it created with developers fueled its explosive growth.

By John Hagel and John Seely Brown, contributors

Bill Gates, 1986

Microsoft chairman Bill Gates in 1986

FORTUNE -- Microsoft was still a no-name startup based in Redmond, Wash. when it launched its operating system, MSDOS in the early 1980s. From the beginning, however, the company believed that this was not your average product launch. MSDOS's design allowed it to adapt easily to different hardware, reducing entry costs for potential users. And Microsoft encouraged participants to tailor MSDOS for particular environments, meaning that the product could actually improve over time.

Like any good platform, however, MSDOS was only as valuable as its network. While it did not have a large user base in its early years, Microsoft (MSFT) soon negotiated relationships with tech giants like IBM (IBM) and Intel (INTC), fueling growth expectations and motivating more early adopters to sign on. In this way, the platform was able to quickly gain critical mass and achieve network effects -- that wonderful position when the value of the network increases for all participants as more members join. This growing value helped to attract even more participants. By relying on growing economic incentives to attract and engage participants, Microsoft significantly reduced the overhead costs that often slow, or even limit, the growth of more conventional business networks.

Perhaps even more important than its network size was how individuals interacted with and tailored the MSDOS platform. In some respects, the common platform leveled the playing field among participants, creating incentives for them to "protect their turf" by improving their own performance. As the number of participants continued to expand, both competitive pressures as well as the spoils of success increased, perpetuating a cycle of continuous innovation around the standard platform.

MORE: Games: A job recruiter's new best friend?

In many cases, different participants teamed up to make the network better, while others chose to work on their own. Without any intervention from Microsoft, these interactions among participants evolved into complex webs of collaboration, where the interactions were not just one-to-one, but among groups of different players. This resulted in an explosion of experimentation.  Many of these promising ideas were quickly adopted by other participants, and those that failed served as collective learning material.  In this way, each participant, and the ecosystem as a whole, learned much faster than they would have on their own. 

The first release of the Microsoft platform may seem like ancient history, but it illustrates the powerful potential of what we call "web ecosystems." In nature, the webs we discover can inspire awe and defy explanations. A well-constructed cobweb, for instance, can span a seemingly impossible distance from its central point and remain intact even in heavy rains and wind that send neighboring leaves and branches to the ground. It is no wonder, therefore, that this image of strength and subtlety has become an oft-referenced metaphor in so many other domains (yes, we're speaking of the World Wide Web, among others).

As we researched ecosystems (gatherings of business participants engaged in some form of collaboration), we found that the well-worn term perfectly characterized the nuances of MSDOS and other webs.  These ecosystems are particularly interesting because of their scalability -- webs have the potential to mobilize hundreds of thousands, even millions, of participants.  More than just scalability in numbers, webs also support a much broader range of innovation than other kinds of collaborative ecosystems. Just as intricate patterns emerge on the edges of spiders' webs, so too can distinct and exciting innovations emerge from different pockets of a given ecosystem.

MORE: New evidence that going green pays off

Web ecosystems often rely primarily on economic incentives to mobilize its participants. Platforms of some sort are usually involved in catalyzing and growing web ecosystems, but the platform developer often tries to expand participants' abilities to work with each other rather than tightly specifying what they can and cannot do.

Consider the differences between Apple's (AAPL) iOS app store to Google's (GOOG) Android marketplace. Apple's app platform, though highly profitable, does not constitute a web ecosystem. Apple's structured development regulations and rigorous screening process limit the scope for experimentation and require a significant level of interaction between the platform developer (Apple) and the participants. It offers the benefit of more reliability for its users and an adherence to certain quality standards.

By contrast, the largely open Android platform does represent a web ecosystem. Android offers more freedom for developers to experiment and test potential applications. The relaxed and flexible structure means that a greater number of "amateur" applications are available, but it also creates many opportunities for collaboration and innovation.

Though many of today's examples come from technology companies, the applicability of web ecosystems extends further than this domain. Consider the story of Malcolm McLean, a truck driver in the 1950s. After seeing the need for greater coordination between different groups working in shipping, McLean developed a standardized shipping container and made the standards available industry-wide.  By encouraging port authorities, shippers, and crane companies to invest in new equipment and practices to support this standard, McLean, much like Microsoft, was able to speed up adoption and quickly reshape the global industry.

We expect these web ecosystems to become more prevalent in the future. Big Data, for example, may become fertile ground for new web ecosystems. As certain companies accumulate richer and more detailed profiles of customer behavior, these bits of data can be used to create a "platform" that participants can use to develop innovative products and services. Government 2.0 projects, which make available data accumulated by various government agencies, represent another promising web ecosystem.

Web ecosystems have meaningful implications for many industries today. For starters, we would single out health care, financial services, media, and the energy industries ripe for disruption. But let's not stop there. Is your industry ripe for change at this scale? What would a web ecosystem need to look like in your field? Like stumbling across an ornate and resilient spider web, the results might surprise you.

Speaking 

As the CEO and founder of InnoThink Group, Jim can help your organization enhance the strategic innovation and competitiveness of your business policy and strategy, with an emphasis on increasing top line growth. 

 If you’re interested in having Jim speak at your next event, simply use this form to send us your details and speaking requirements, and we’ll be in touch shortly. Or you may call us at 719-649-4118. 

Thursday, April 5, 2012

The Long-Term Damage from Juggling Too Many Projects

Managers who try to meet important product development deadlines by shifting resources from other projects may succeed in the short term, this paper finds, but the continuous shuffling of resources and team members has a harmful ripple effect over time. Ultimately, the company’s ability to deliver projects reliably will suffer from this schedule-driven approach to project management.

The insight applies to any company that finds itself overextended in the rush to make good on multiple commitments. But it has particular relevance now, given the recent recession and the ongoing so-called jobless recovery, the authors write, because companies have few resources (for example, their highly skilled engineers are in short supply) and are reluctant or unable to hire and train new staff.

If product development and manufacturing firms are to survive in competitive markets, they must continuously tweak their offerings and create new products that feature emerging technologies and trends. As a result, these firms typically have many projects cooking at once, and have different teams sharing engineering and design resources, which can become overextended at peak times. They’re also under pressure to accelerate product development and reduce the time it takes to get their merchandise to market, especially for cutting-edge technology or in-demand goods.

Accordingly, top managers often try to allocate resources from concurrent jobs to ramp up an important project that has fallen behind because of a late start or insufficient support, both common scenarios when companies are juggling many assignments. And some projects are simply more critical to the business than others. For example, firms can lose significant anticipated revenues if their products don’t get to market before a certain predetermined date or if a competitor beats them to it. Many contracts also stipulate penalties for delays.

But what is the long-term effect of this schedule-driven project management approach? To find out, the authors studied the product development division of a manufacturer of high-performance trucks, which embodied the challenges faced by many companies that work on several projects and deadlines at once.

The firm’s target customers are mostly short- and long-haul logistics companies that pay more than US$150,000 per vehicle. Preserving customer loyalty is essential in the trucking industry, because customers rarely switch between competitors when renewing their fleet. Manufacturers must respond swiftly to their competitors’ new products, advances in technology — including ways to improve fuel efficiency and reduce emissions — and regulatory changes.

The company in the study builds about 100,000 trucks annually, mostly tractor units for semitrailers or rigs, but very few are identical. A top management team allocates the annual R&D budget to a number of initiatives to develop new business, and the approved projects share the same pool of specialized resources.

The authors conducted more than 80 one-on-one interviews, eight group presentations, a four-hour workshop, and an analysis of the firm’s archives, as well as making direct observations at the company from 2004 to 2009. Employees participating in the study had diverse job roles, including engineering designers and project and portfolio managers.

The resulting data was then fed into several computer-based models that probed the effects of schedule-driven pressure on long-term productivity. Specifically, the authors examined scenarios in which the time crunch resulted from a policy to complete business-critical projects by the deadline, regardless of whether they started late or initially lacked resources.

The simulations showed that as top management put pressure on a team to finish a project, the time lost on subsequent projects tended to snowball in several stages. First, as one project sacrificed resources, it also came under schedule pressure. Second, as the pressure ratcheted up on more projects, resources switched back and forth more frequently as managers struggled to prioritize. Third, productivity went down as the teams’ size increasingly fluctuated and employees logged long overtime hours.

Jim Woods is president and founder of InnoThink Group. A global management consulting firms specialized solely in helping organizations of all sizes in all industries catalyzing top line growth through strategic innovation and hypercompetition. Jim has over 25 years consulting experience in working with small, mid size and Fortune 1000 companies. He is a former U.S. Navy Seabee and grandfather of five. Jim is board president of a charter school located in Colorado Springs whose sole purpose is to prepare otherwise disadvantaged students more competitively for college. To arrange for Jim to speak at your next event or devise an effective hypercompetition strategy email or call us at 719-649-4118 for availability. Subscribe to our innovation and hypercompetition newsletter.   

Follow us on Twitter

Follow us on Linkedin

Follow us on Facebook