Category Archives: Technology

Beyond the Beaker, A Book Review

Paul Patterson’s Beyond the Beaker, a book on How to Achieve Successful Market Adoption for Emerging Technologies, is a book that belongs on every innovator’s bookshelf. Whereas there are a lots of books on how to innovate, and even a fair number on how to take your product to market, there are very few that overview all of the relevant issues that need to be addressed and managed, fewer still that address both the innovator and corporate perspectives, even fewer still that illuminate the roadmap with real case studies, and next to none that uses successes and failures to help you understand the criticality of getting even the seemingly mundane choices right.

As Paul Patterson notes in the preface, the true, Real Life, events, which frequently go undocumented, are more often the critical events of success. For example, its 4 am and your phone rings. The person on the line is upset, screaming vulgarities because someone in the collaboration violated international trade laws. It’s your job to repair the situation.

For example, sometimes the most important aspect of the product is the seemingly mundane service guarantee. Here in North America, we expect our products to work and manufacturers to replace them if they don’t. We also reward companies who have faith in their products and provide satisfaction guarantees in addition to basic “works as advertised” guarantees. These companies do so knowing that, since we want to do the right thing, we won’t abuse the guarantee. However, do the right thing is culturally defined. Whereas some cultures will pride themselves on only using a guarantee if they are truly unsatisfied or the product doesn’t work, others will pride themselves on finding innovative ways to use the guarantee because their culture prizes cunning in business more than personal restraint. As Paul Patterson notes with this quote from Gan Chee Eng, Vice President of Amway China Company Limited, the Amway Guarantee almost put them out of business in China on the first day:

“I tried to explain to corporate that their guarantee will not work in China, but they insisted. People would have a wagon in the parking lot with a small barrel in it, come into the shop and purchase a 1 litter container of L.O.C.TM, walk out to their wagon, dump the container into the small barrel, walk back inside, and say, ‘I’m not satisfied, you replace’. Honouring the guarantee almost put us out of business on the first day. We closed for two weeks and re-opened with a new guarantee, which limited customer satisfaction to providing one replacement, which meant we effectively sold two for the price of one.”
– Gan Chee Eng

Sometimes the most important aspect of the product is the education around the importance of the product. For example, the success of Hindustan Lever Limited (HLL), the largest soap and detergent manufacturer in India, and its Lifebuoy soap (reformulation) came down to educating the populace on the importance of using soap. A market analysis by HLL found that many consumers were not using soap when washing because they believed that soap did not provide any additional value. So HLL developed an educational program that “visual clean is NOT safe clean” which included a germ-glow demonstration targeted at school children ages 5 to 13 and their parents. This program which did not advocate HLL or Lifebuoy but simply soap usage, ultimately led to a sales increase of 30%. The branding around the educational content was enough.

And sometimes the most important aspect of the product is the insight into potential usage. For example, consider the classic Post-It Note. In 1968, Spence Silver at 3M developed a super-weak glue that could stick to objects, and be easily peeled off, while searching for a new super-strong glue formula. For five years, he hyped the product internally, showing samples in spray-can and tack-less bulletin boards, but it never took off. Then he noticed Art Fry using pieces of the tack-less bulletin board tiles to mark pages in his hymnals and he came up with the idea for a better bookmark. Then he realized that the product wasn’t really a better bookmark at all, but a better note. And while there were technical challenges in perfecting the formula so the glue stayed on the note and not the object the note was stuck to when the note was removed and in developing appropriate coating equipment for paper (which was an imprecise substrate), the biggest hurdle was coming up with the right application for the technology. The second biggest was the right marketing campaign as the product, which was the company’s Outstanding New Product in 1981, did not take off with the first launch attempt in 1977, but the second in 1980.

The second thing I really like about the book is that it’s not your usual pop-culture business book that uses 200 pages to expound upon a simple (although usually very important) idea that could be summarized in 20 pages but is instead a jam-packed tome of information which would make a good textbook. As a result, this is a book that will end up on your bookshelf when you are done reading it and not the goodwill donation pile because you will want to read some parts of it more than once and keep it for reference.

Not only does it tackle strategic marketing, business development, financial concerns, legal considerations, organizational management, and corporate perspectives as well as the identification and evaluation of emerging technologies and technology development, but it addresses each from multiple viewpoints. For example, with respect to strategic marketing, it addresses SWOT (Strengths, Weaknesses, Opportunities, & Threats), macro and micro approaches, Porter’s Five Forces (Rivalry, Threat of Substitutes, Buyer Power, Supplier Power, and Barriers to Entry), Boston Consulting Group Market Evolution (Fragmented, Specialization, Volume, Stalemante), market and sector attractiveness, competitive advantage, value proposition, application and value chain analysis, other market drivers, and risk management. It addresses business development from a multitude of perspectives that include strategy, cultural, pitch, promotion, and communication. And it covers the five phase evaluation of emerging technologies (feasibility, value research, quick test market, action plan creation, and implementation) because the easiest thing about innovation is, well, innovation itself. The real challenges often lie in getting the innovation to market.

Finally, I really like the inclusion of a chapter on the corporate perspective. If you identify an emerging technology that you want to bring to market, you have to understand how your potential financiers think if you are going to be successful. Financiers typically invest in a portfolio of opportunities to mitigate their risks and increase the odds that they will see a return on their investment. As defined by Copper et. al in Portfolio Management for New Products:

Portfolio management for new products is a dynamic decision process wherein the list of active new products and R&D projects is constantly revised. In this process, new projects are evaluated, selected and prioritized. Existing projects may be accelerated, killed, or deprioritized and resources allocated and reallocated to the active projects. The portfolio decision process is characterized by uncertain and changing information, dynamic opportunities, multiple goals and strategic considerations, interdependence among projects, and multiple decision makers and locations.

This indicates that decisions about whether or not to invest in your product will not be made in a vacuum and will be made with respect to the rest of the portfolio. That means that you will need to insure that you continually address each of the critical success factors of portfolio management (strategic alignment, competitive advantage, market attractiveness, leverage of core competencies, technical feasibility, and financial rewards) if you wish to get funding and maintain it.

All in all, a great book and a great reference.

Share This on Linked In

Vinnie Mirchandani on “The Costs of Software Renewal”

Today’s guest post is from Vinnie Mirchandani of”Deal Architect” and “New Florence. New Renaissance”. Vinnie, a founding member of the Enterprise Advocates, is a tireless advocate of trends and technologies that can help buyers get more for less.

Ray Wang gives us a timely reminder that “Labor Day (US & Canadian Holiday) traditionally marks the end of summer BBQ’s, the beginning of the fall conference season, and yes, the time to begin a review of your software maintenance contacts that expire at the end of the year.” (Software Insider, Sep 1, 2009)

I would say start with that — and then keep going. Take a look at all of your contracts that renew through the end of 2010.

Several good reasons to this include:

  • Establishment of a savings target on the total maintenance spend for 2010.
    Have your staff focus on every software contract, especially those that have been “auto-renewed” for years now because they were “small” and fell under attention thresholds. If you make the overall target part of a compensation plan for key IT and procurement staff, you’ll quickly find that Thar’s gold in them yellowing software contract files.
  • Multi-year maintenance deals which looked good when signed may now be overpriced.
    Current market trends are driving the cost of maintenance down, especially through third party services. Don’t assume they cannot be re-opened. (See Marc Freeman’s tips for “renegotiating with integrity”.)
  • If you don’t start now, you might not finish the renegotiations in time.
    Don’t overestimate the ability of your team to get organized — or underestimate the ability of the vendor team to stall — beyond the end of the year. If maintenance expires, and something goes wrong, you could be at the vendor’s mercy in renegotiations. Formally document your new process and let the vendor know next year will be different. Furthermore, be sure to allow 6 months for the renewal negotiation next year.
  • Even if you are looking to migrate, you will still need incumbent vendor support until the cut-over occurs.
    This holds true whether you are looking to migrate away from the incumbent vendor to SaaS, or to third party maintenance, or to do-it-yourself support (and readers of Deal Architect will know I am a broken record on the subject of considering all of these options). This will likely push you into 2010 planning and funding.

So, use Ray’s call for intensity over the next 3 months and build momentum for another 12 months. The payback will be huge — software maintenance continues to be one of the items on the IT menu with the most “empty calories“.

Thanks, Vinnie!

Share This on Linked In

It’s Still All About the Pentiums, Baby!

It was exactly 3724 days ago today, or 10 years, 2 months, and 10 days ago today that Weird Al Yankovic proclaimed that It’s All About the Pentiums. I wonder if he knew that when he proclaimed:

 

My new computer’s got the clocks, it rocks

But it was obsolete before I opened the box

You say you’ve had your desktop for over a week?

Throw that junk away, man, it’s an antique

Your laptop is a month old? Well that’s great

If you could use a nice, heavy paperweight

 

that the trend was only just starting and that ten (10) years later it would still be about the latest generation of the Intel Processor (the Core 2 Duo), that your database would still be a disaster, that windows would still take a “day-and-a-half” to boot up, or that, regrettably, supply chain managers would still be king of the spreadsheets?

I’m wondering because 3724 happens to be the RFC on The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture. The end-to-end principle just happens to be the core architectural guideline of the internet. Addressing concerns of openness, reliability, robustness, user choice, and ease of new service development, the end-to-end principle, which was originally a question of where not to put functions in a communication system to insure that applications could survive partial network failures, is still as relevant as it ever was. While not a standards proposal, like most RFCs, it put forward some good questions as to how the internet should evolve, questions which are becoming increasingly important with the rapid proliferation of the internet across a wide range of wired and wireless devices on which you will want to seamlessly access your supply chain applications.

Simply put, you’re going to want to be able to run your apps whether you’re working on your server, working on your desktop, working on your laptop, or working on your mobile, and you’re going to want to be able to do it using an open architecture built on open standards. This is because you don’t want to be spending thousands upon thousands of dollars for proprietary products that use proprietary APIs on each platform that do nothing more than convert your data from proprietary format A to proprietary format B so your mobile can talk to the server. You just don’t.

So remember, it’s all about the pentiums, baby.

If Software Development Outsourcing is Too Agile, You’ll Be Kayaking Over the Waterfall

A recent article on “how agile methodologies help software development outsourcing” over on SourcingMag.com had some very good points on how agile software development can help you with your software development outsourcing. However, having lived through the Agile Craze in IT, I know that you can overdo it and actually hinder your development processes and development outsourcing.

 

Let’s start by review the positives put forward by the article:

  • Methodology Fit
    The ability to make continuous process changes and improvements is a boon to two organizations trying to synch their processes for the first time.
  • Bridge the Communication Gaps
    Frequent release-and-review cycles can help to bridge communication gaps.
  • Perfection is Iterative
    No one gets it right the first time. Only the lucky get it right the second time. Just about everything of significant technological complexity in this day and age takes at least three attempts to get right — and when you’re talking software, thirty attempts (behind the scenes) isn’t uncommon …
  • Building Expertise
    You can move your development to an organization that has built a number of similar systems in the past.
  • Responsiveness to Change
    Requirements and processes change continuously … more frequent iterations allow for faster revisions of requirements and code-bases.
  • Quality
    Faster feedback generally means that problems are identified – and solved – sooner in the development process.

Now we’ll look at the negatives that can result if you’re not careful:

  • Methodology Fractured
    While the ability to make rapid changes can be beneficial when trying to synch processes, they can also break processes that are working well.
  • Deepening the Communication Chasm
    Frequent release-and-review cycles that lead to constant improvements can give you the illusion that the communication gap is bridging when in fact the chasm underneath is deepening. The successive improvements could be due to trial-and-error and luck and not have anything to do with communication improvements. Plus, an over-focus on feature-function might cause you to ignore relationship building, which is critical if you are ever going to truly bridge the communication gap, especially with offshore development organizations in India, China, and Poland, for example.
  • Running-in-Place
    The faster you respond to change, the faster the change requests start coming in. If you’re not careful, you’ll start to cycle through changes until you’re back with what you started with — after months of wasted effort.
  • Lack of Robustness and Flexibility
    If you only measure quality by “how close the end-user design is to what you envisioned”, or “how many of your test cases run bug free”, you might miss the fact that the code is an unmaintainable mess of spaghetti that you’ll never be able to maintain, update, or modify again. Very Bad Code is a regular by-product of overly-aggressive agile development cycles with too many iterations. Building good code requires building a good, stable, underlying architecture that does not change. Just like you can’t use the frame of a three-story house for a 6 story office building, you can’t use an architecture for low-volume EDI message exchange for a high-volume real-time XML exchange. If you adopt a high-frequency agile development cycle and don’t take the time to get the right framework and software architecture up-front, the developers end up having to hack the code every iteration to make their changes and after five or six iterations you have a tangled mess that even a development guru won’t be able to make heads or tails of.

So while agile can be beneficial to your development outsourcing, it has to be used in moderation or the drawbacks will far outweigh the advantages.

 

 

Share This on Linked In

Sourcing Innovation Welcomes Vinimaya as New Lead Sponsor

Sourcing Innovation is pleased to welcome Vinimaya, an innovative provider of e-procurement catalog and marketplace solutions, as its newest lead sponsor. Vinimaya, which represents The Next Wave in Product Catalogue Management (PCM), has been adding new functions, new offerings, and new clients since I first blogged about them back in 2007 (shortly after they were named a Cool Vendor by Gartner).

Unlike other providers, who only support catalogs, marketplaces, punch-out, or punch-out 2.0 (where the vendor maintains a cached copy of the supplier catalogs to simulate simultaneous searching and comparison of supplier products), Vinimaya’s Virtual Internet Supplier Network solution (VISN, as in “vision”), supports simultaneous, or federated search directly from whatever catalog format your suppliers have in place — be it punch-out, on-line catalog, storefront, marketplace, database, or flat-file. Whereas most solutions force your supplier to adapt to the vendor’s format, Vinimaya’s agent-based architecture adapts to your suppliers, which is why it’s a low-cost solution for you and for them.

The proof that Vinimaya’s offering, which revolves around their SmartSearch Catalog software product, actually works is in the adoption level. Vinimaya’s client base, which includes mostly well-known, brand name, global companies from almost every vertical market, have executed over $1 Billion in online orders over the past 12 months alone. Delivered SaaS with the ability to “plug and play” with just about any e-Procurement system (e.g. SAP, Ariba, Oracle, Peoplesoft, etc.), once installed, the system not only allows you to find the product you need simply and efficiently, but also verifies that you’re paying at the contracted rates. Vinimaya’s clients sit back and watch their negotiated savings materialize with every purchase.

SmartSearch Catalog also comes with a number of unique features that enhance your efficiency and savings. The unique features include true side-by-side comparison shopping across suppliers, price audit (which will alert you whenever a price has changed or diverged from the contract price), supplier self-service catalog management (which allows your suppliers without any online capabilities to either maintain a catalog for you or create a punch-out site), and inventory checking (which checks that the item is in inventory before sending the order to the supplier). It even offers some capabilities specific to certain procurement systems (e.g. SAP Item Master Check). In the coming weeks, I plan to review the new version of the SmartSearch Catalog (a.k.a. the B2B Search Engine), as well as some of their new offerings, and if I can track down the Sourcing Maniacs, see if they have any insights from their last site visit.

Vinimaya’s bent toward innovation is no surprise when you look at the management team. CEO Gary Hare, who recently penned a piece on B2B e-Commerce right here on this blog, Orville Bailey and Richard Waugh have been thought leaders in the e-procurement space since its inception.

So please join me in welcoming Vinimaya. It’s innovative companies like them that keep this blog going.