Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Businesses Books Media Book Reviews Technology

It's Not About The Technology 198

prostoalex writes "No one quite knows the exact point when high-tech marketing went wrong. When instead of selling distinct products and services, the company Web sites and brochures started pitching 'the next big thing.' When even software developers don't have a slightest idea about what's being sold to them. Raj Karamchedu from Silicon Image, however, feels that certain things in high-tech marketing should be straightened out, hence this book." Read on for Moskalyuk's review of Karamchedu's It's Not About the Technology .
It's not about the technology
author Raj Karamchedu
pages 230
publisher Springer
rating 4
reviewer Alex Moskalyuk
ISBN 0387233504
summary Developing the craft of thinking for a high-tech corporation

20 chapters are written from the point of view of tech marketing executive, as Karamchedu tries to answer the question of why some products gain a loyal audience and enjoy commercial success, while the others are simply additions to the dusty shelves of history. Everyone has their favorite comparison, where a technically advanced product does not gain acceptance on the market while a supposedly inferior competitor is rolling in cash. Hey, IBM built an entire theory on how it was safe to let Microsoft sell its not-so-great DOS with IBM PCs in order to push the hardware from the warehouse while the company was preparing the next revision of state-of-the-art OS/2 -- which, of course, everyone will buy on the day of release in order to replace Microsoft's software.

History occasionally teaches tech marketers some curious lessons, and the conclusion that the author comes up is summarized in the book title. The title might sound like an insult to a design engineer, but in most of the cases the success in the market is not guaranteed by superiority of technology. Karamchedu is on the mission to find out why.

The first chapters take us through a conflict inside a company. Seldom will you find a high-tech startup where marketing people do not clash with engineers. Marketers promise the features to the customers in order to adhere to the mantra of "we listen to our customers," only to see feature requests denied by the engineers, since the budgets and deadlines are fixed. Marketers then complain to the executives about lack of response from the engineering staff and their inability to deal with the new features, while engineers fight back, claiming that the product is about to miss the deadline even with existing feature set and overworked staff.

Later, Karamchedu focuses on a second problem, peculiar to high-tech marketers: after being immersed in the technology world for too long, they cannot relate to the customers. Hence grandmas in Best Buy staring at the computer described as "P4 3.0 GHz 256 DDR 40.0 GB DVD/CD-RW" when all she wants to know is whether she can check email and view photos of the grandkids. Marketers forget to empathize with the customers. They spend too much time with engineering, and like to tell customers how the new microprocessor has a much wider front-side bus, or how their new piece of software supports dual-core systems, without really telling the customer how that will improve business processes or increase efficiency.

The third part of the book takes a look at a typical semiconductor company and tries to draw the plan of attack for a starting marketing executive. At this point the book turns into a manual on high-tech marketing, which the author hopes the readers will find useful, as there are no set rules and algorithms for launching successful marketing campaigns in high-tech world.

The book is quite insightful, but one can't help but feel that it is missing something. It will probably prove to be a valuable read to anyone facing the daunting task of marketing a high-tech product, but even though I got to the last page of the book, I found the title to be too terse and dry, lacking concrete examples and not quite coherent as far as the chapter-by-chapter arrangement. The preface and the author's description of the book are available online. It's also strange that in an attempt to write a textbook on high-tech marketing, the author decided to provide no case studies whatsoever. In Search of Stupidity from Apress is a great book about high-tech marketing, since it tells the story of a failed marketing attempt and also tries to figure out the reasons, but in It's Not About the Technology, Karamchedu just tells years of his personal experience, without references to specific companies or projects, which makes the book a compilation of abstractions on high-tech marketing.


In his spare time Alex enjoys reading technology and business titles. He also keeps a collection of free books for readers on a budget." Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
This discussion has been archived. No new comments can be posted.

It's Not About The Technology

Comments Filter:
  • Bullsh** detector (Score:5, Insightful)

    by baggachipz ( 686602 ) on Monday January 03, 2005 @04:32PM (#11247662)
    When looking at a brochure-style website dealing with services or products, count how many times the word "solution" is used. The higher the number, the more full of crap they are. The all-time record is held by ibm.com.
  • Blame M$ (Score:5, Insightful)

    by superpulpsicle ( 533373 ) on Monday January 03, 2005 @04:33PM (#11247670)
    It went wrong when the biggest players in the market can sell lemon to the consumers and get away with it. Think of how many versions of M$ windows are unusable before a service pack 2 or 3.

    Imagine buying a car and it doesn't work until 6 months later when your manufacturer has a recall for you. Commercial hi-tech industry seriously need a good role model.

  • by rainmayun ( 842754 ) on Monday January 03, 2005 @04:35PM (#11247696)
    If the people making the purchase decisions aren't the software engineers, then why should the advertisements be tailored to them? of course I am speaking out of the side of my neck... in a more ideal environment, the purse-string-holder would consult the geeky-technician for an opinion before pulling the trigger on any tech purchases.
  • by Ckwop ( 707653 ) * on Monday January 03, 2005 @04:37PM (#11247712) Homepage
    I don't know about you but I think he has egg on his face.. ASP.Net was a revolution..

    For the first time rather than having three hundred asp/php pages with cut-and-copy disease we had a way to make structured code that could be developed very quickly and maintained easily.

    At work we've got loads of legacy ASP and lots of new .NET stuff. I'll probably never understand all the ASP. Cut-and-copy disease has made the thing a fucking pain to maintain. In contrast, the .NET stuff is readily understood.

    I don't think .NET was a tremendous revolution but it did improve things considerably from a web development point of view.

    Simon.
  • Word (Score:5, Insightful)

    by t_allardyce ( 48447 ) on Monday January 03, 2005 @04:40PM (#11247748) Journal
    It took me 3 years to have a basic understanding of what .NET was. 3 years just to figure out that it was basically Java.
  • Re:Blame M$ (Score:5, Insightful)

    by garcia ( 6573 ) * on Monday January 03, 2005 @04:40PM (#11247755)
    Think of how many versions of M$ windows are unusable before a service pack 2 or 3.

    Hmm, Windows2000 and XP ran just fine for me right out of the box without service packs. Yeah, you needed a good firewall (hardware and software) and you needed to make sure some services weren't running but I really don't consider that to make the "unusuable".

    Honestly, I wouldn't run ANY OS without the above mentioned changes being made to the configuration.

    Should we say that RedHat is bad because everyone knew that you shouldn't use a RH release before X.3?
  • by JeffTL ( 667728 ) on Monday January 03, 2005 @04:42PM (#11247763)
    I've noticed that myself. And also note how often there isn't an explicit price tag on a "solution" -- that's what makes it different from a product, which is when you can see what you're considering getting and for how much money without promising your firstborn and getting on a mailing list.
  • by micromoog ( 206608 ) on Monday January 03, 2005 @04:43PM (#11247776)
    That's funny, because IBM actually does drive a lot of the innovation, and definitely performs a lot of the work, in IT. "We intend to sell dog food on the Internet" is a much better bullshit signal.
  • by Anonymous Coward on Monday January 03, 2005 @04:44PM (#11247792)
    I remember when advertising would list the benefits of a product. Now all it has is a picture of the sky with a question "where do you want to go today?". Thanks a lot, that tells me nothing.

    I was reading some back issues of Pc Magazine from the 80's, the ads told me as much as the articles. Ads would say "The new microsoft compiler has these features... that are better than the last version" I miss those type of ads.
  • by Doc Ruby ( 173196 ) on Monday January 03, 2005 @04:46PM (#11247816) Homepage Journal
    The problem is that consumers believe marketers' lies, which are cheaper to produce than a working product. High-tech is no different from any other industry (what do you know of that really works, the way high-tech "doesn't"?), except the cost difference between marketing lies and good products is extremely high, matched only by the their obvious difference in performance. While that NP-complete problem is intractable, the breakdown occurs when consumers react to discovery of the lies, when the product sucks, by switching liars. High-tech offers greater possibility for changing that, as the degree to which products actually work is increasing consumers' ability to filter the lies, and report the reality, through mass P2P communications by people with mutual interest in consuming quality, rather than producing profit.
  • by czaby ( 93380 ) on Monday January 03, 2005 @04:47PM (#11247820) Homepage
    When I give lectures about highly technical topics like J2EE, half of my presentation is writing buzzwords to the whiteboard and explaining what it actually means. Most of the time I finish with: "See, this is really trivial. It was made to LOOK complicated, because the business needs it. But you are technical experts, you should know how simple it is."
  • by zymano ( 581466 ) on Monday January 03, 2005 @04:48PM (#11247832)
    Has got to be REAL superfast broadband.

    The cable companies CAN'T and WONT deliver it. I am talking about higher than 100 megabits/sec. .

    Imagine a billion HDTV channels and no more installing operating systems.

    No more needing to even buy a computer because of distributed networking. You will buy supercomputer time for tough projects.

    All this will never occur because municipal fiber to the curb has been killed by stupids in government and their cronies in the private markets.
  • by PaulBu ( 473180 ) on Monday January 03, 2005 @04:50PM (#11247850) Homepage
    Or something else... really...

    To say that the current version of the Company X product is so much better than the previous version of the _same company's_ product does not really endorse _either_ version.

    Paul B.

  • by That's Unpossible! ( 722232 ) * on Monday January 03, 2005 @04:50PM (#11247852)
    I don't know about you but I think he has egg on his face.. ASP.Net was a revolution..

    That is highly debatable, but Joel was talking about .NET. You're talking about one aspect and more easily defined part of .NET, called ASP.NET.

    Back in 2000, it *WAS* confusing as to what the fuck .NET actually was supposed to be. People would ask me what it was, being a developer they thought I knew, and I could usually muster was, "Well, it's a lot of things all under one umbrella."

    Now when people say ".NET" they are usually talking about ASP.NET or the .NET APIs. But back when Joe's article came out, .NET was being bandied about to talk about everything, from Windows .NET Server (aka Windows 2003 Server), to the new API/platform to replace COM, to a set of web services (like Passport), etc.
  • by Zebra_X ( 13249 ) on Monday January 03, 2005 @05:03PM (#11247950)
    ASP.NET doesn't introduce anything new, unless you've only used ASP and have since upgraded to (pre-existing) functionality that "new" in ASP.NET.

    Not true at all. Each "page" is a class and is treated as such in it's implementation from a functional perspective.

    A UI developer can make changes to the controls, with out wortying about breaking some server script. In addition it is possible to completely remove SQL code from the presentation tier, this is not possible with out a great deal of engineering and com components with traditional ASP.

    ASP.NET simplifies state management on three levels, application, session, and page as well. Page state is something that has traditionally needed to be built by the developer, but this is no longer the case in .NET. Each control on a page manages it's state via the view state.

    Also validation for all forms is simple and easy to implement, taking a fraction of the time to complete, and it's twice as robust (it runs client side, and server side depending on what your browser will support)

    At the moment, I'd be hard pressed to find another technology platform for web development that is as flexible as .NET.

    The revolution was really for the developer - not so much from a product perspective. Have a look at how easy it is to incorporate 3rd party components into web applications. Provided the 3rd party provided designed their component well, it usually "just works". That's more than I can say for similar development platforms.
  • by Mr. Slippery ( 47854 ) <.tms. .at. .infamous.net.> on Monday January 03, 2005 @05:06PM (#11247975) Homepage
    For the first time rather than having three hundred asp/php pages with cut-and-copy disease we had a way to make structured code that could be developed very quickly and maintained easily.

    I never touch ASP, but if your PHP suffers from "cut-and-copy" you need to take a cattle prod to the developers.

    This is a coding practices issue, not a language issue - the legacy code at my current employer is C++ CGI programs that suffer greatly from the use of cut-and-paste rather than code libraries. It's just about the worst C++ code I've ever seen, but that's not C++'s fault. PHP makes it easy to create reusable modules that you can just "require_once"; if developer's don't, that's not PHP's fault.

    "Our old code in Language X sucks, our new code in Language Y is better written" doesn't mean that X is better than Y.

  • PC specs (Score:5, Insightful)

    by HarveyBirdman ( 627248 ) on Monday January 03, 2005 @05:13PM (#11248036) Journal
    Hence grandmas in Best Buy staring at the computer described as "P4 3.0 GHz 256 DDR 40.0 GB DVD/CD-RW" when all she wants to know is whether she can check email and view photos of the grandkids.

    I hear that at work all day and it drives me nuts. Not that I don't look at specs when I buy a computer, but I have learned never to ask about anyone else's new computer because you get the five minute laundry list of numbers that have no real importance. Do I really need to know if your new Duh-ell PC has an 80G or 100G hard drive? PC specs have replaced dick size and engine displacement as bragging fodder or something.

    I overheard the guy in the office next to me last year spend hours on the phone shaving costs of his new PC. $10 here. $5 there. He must have spent 20 hours to save $100. He drives a $45,000 car. Nobody places value on their time. He finally bought the thing and announced it to the bay the next day. Absentmindedly, I asked what kind... D'oh! Nine hours later I could have reverse engineered a schematic of the motherboard based on what this guy told us.

  • by jdhutchins ( 559010 ) on Monday January 03, 2005 @05:20PM (#11248088)
    ASP.Net was not the first time you could use modular programming in web pages. You can do it in perl, you can do it in PHP, and you can do it in Java. If you had significant amounts of copy-and-paste code in every page, you probably had web designers instead of programmers write your website. ASP.Net was not a revolution.
  • by Lord_Dweomer ( 648696 ) on Monday January 03, 2005 @05:30PM (#11248186) Homepage
    As someone in marketing/advertising, I have to agree that I have seen few areas as hyped up as the tech industry in terms of their marketing.

    Frankly, its disgusting at times because they hurt the credibility of the entire industry (not that we had much with the /. crowd to begin with).

    I try to do my part by not misleading people with what I market as I understand that an informed customer that you treat with respect will be a repeat customer who will spread the good word about you. I also inform people of when deceptive marketing/advertising is used and explain why it is bad and meaningless.

    I think all of you are familiar with such lies as the "industry leader" claim or the "does more" claim. To those I have to ask "industry leader according to whom? The CEO fo the company? Because legally as long as you have the quote from someone, you are allowed to make that claim", and then I ask "does more? Does more WHAT?! Oh wait, legally that doesn't matter as long as you don't state it. It could ben "does more to line the CEOs wallets" and it would still be legal."

  • Actually, some do. (Score:4, Insightful)

    by khasim ( 1285 ) <brandioch.conner@gmail.com> on Monday January 03, 2005 @05:42PM (#11248274)
    The owner of the company that I work at buys whatever the latest and coolest toys are.

    He doesn't know how to work them or even why a cell phone that works in Europe won't always work in the US .... but he buys them. He buys them because they are cool and newer than what other people have so he can impress them. He is the type who will buy something because it is "superior".
    Techies like to say things like "Windows is unusable" (when most of the world uses it) or "corporations put profit above technology" (gee, do you think?). Just shows why a lot of them get along better with hardware than with people.
    I think the techies are pretty much like other people in that regard.

    They have their point of view based upon their requirements / values and have trouble recognizing that other people have different requirements / values which result in different points of view.
    People buy "stuff" that that we can use to do whatever it is that we want to, preferably without breaking a sweat or needing to read a book first.
    But part of "Marketing" is making the consumer believe they have a "need" that they weren't aware of before, that can only be supplied by your product.

    That "need" can be as esoteric as "I am a rebel against authority" to as mundane as "fast food you like".

    Marketing high tech is different from most other markets because newer stuff is constantly being released. The perception of obsolescence is a key factor both in pushing the new stuff (don't be a loser, everyone else is faster) and in resistance to purchasing (why buy now when tomorrow it will be faster and cheaper).

    I haven't read the book so I don't know if he covers that in depth.
  • by ednopantz ( 467288 ) on Monday January 03, 2005 @05:49PM (#11248343)
    By adding a dubious, four year old dig at MS to the post, they manage to get the reviewer's actual comments ignored in favor of yet another M$ sux thread.
    Good going guys!
  • by Anonymous Coward on Monday January 03, 2005 @05:52PM (#11248369)
    The fallacy of your post is one of the biggest problems I face in I.T.

    I.T. is not just an expense.

    Spending $10,000 on System XYZ to replace System ABC might can save my company $15,000 inside a relevant timeframe; the critical, most difficult, and most frustrating part of my job is quantifying the time of particular departments and employees when even the managers and owners cannot do so.
  • Re:Blame M$ (Score:4, Insightful)

    by Audacious ( 611811 ) on Monday January 03, 2005 @05:54PM (#11248394) Homepage
    I believe that the blurring of lines between what is being sold to someone and what is being leased has not helped things out at all.

    My take on the above is:

    Sold: An item is sold to you when you do not have to make any other payments to the manufacturer and you do not have to give it back after a specific period of time.

    Lease: An item is leased when you have to make payments based up a daily, weekly, monthly, or yearly time period and, after the lease has expired, the item has to be returned to the manufacturer.

    From the above, if you "buy" a copy of Windows and do not have to make any additional payments, then the copy has been sold to you - not leased. If this is true (ie: M$ sold the software to you and did not lease it) then all of the leasing agreements imposed by the EULA are null and void. Further, your rights as a purchaser of a product have just increased ten fold because there are a lot of rules and regulations about items which are sold which do not pertain to items which are leased.

    With the recent decision by a court in California that M$ et al must display the EULA on the outside of the box and/or have it readily available for viewing before a purchase is made - the distinction of whether a piece of software is sold to the end user or leased will become a greater issue in the near future.
  • Unplug 'N' Prey (Score:3, Insightful)

    by Ranger ( 1783 ) on Monday January 03, 2005 @06:07PM (#11248489) Homepage
    No one quite knows the exact point when high-tech marketing went wrong.

    I do. About two seconds after the words 'high-tech' and 'marketing' were merged in the acorn sized brain of a marketer. Due to their limited storage capacity any relevant technical information was squeezed out and replaced with marketing slogans. He/She/It thus completely divorced from reality was provided with the ability to create a marketing strategy unecumbered by facts.
  • Possibly. (Score:3, Insightful)

    by khasim ( 1285 ) <brandioch.conner@gmail.com> on Monday January 03, 2005 @06:57PM (#11249117)
    1. "New" doesn't mean "superior". Your boss may buy something because he thinks those two words are synonymous, but they aren't.
    True. But in most cases, "superior" is also "new". Faster proc's are usually the newer ones.
    2. Techies who argue "Windows is unusable" -- a palpable untruth --often do so simply to assert their own elitism. They just want us to know that they've defined themselves as too smart to use Windows. Conveniently, then, anyone who does use Windows is stupid. It's just a peacock display.
    Pretty much. But those people do form a market of their own that a good marketing exec can exploit. #1 & #2 are just different sides of the same coin. For something to be "superior", something else must be "inferior". For something to be "unusable", something else is "usable".
    3. Techies who whine that businesses put profit before technology forget that profit spreads technology. If someone doesn't make and sell the stuff for a profit, how is it going to exist? Are all those good little techies going to devote their lives to making and giving away "stuff"?
    That's what is happening with the Open Source market. It all comes down to the individual's requirements / values. Linus gave his work away. He focuses on the technology instead of the profit. But code is a very special market because no matter how often you give it away, you always have it.
    4. People aren't mindless lab rats at the mercy of marketeers. Just because someone's ads try convince me I need something, why should I pay attention?
    No one is saying that you should.

    But people do pay attention. Advertising works. Advertising is what gets people to pay $500 for a pair of sneakers.

    Yet if you ask a person who just paid that why he paid that, he won't ever say that it was because of the advertising. He will say it's about style or that they are the best sneakers or some other rationalisation. But the reality is that it is because of the marketing campaign.
  • by Infonaut ( 96956 ) <infonaut@gmail.com> on Monday January 03, 2005 @07:05PM (#11249196) Homepage Journal
    High-tech companies like the term "solution" because of the limitations of the terms "product" and "service". No single product can ever be right for every customer. So customers are rightly suspicious of a single product that purports to solve all problems. A service implies that you simply pay money to a company on a continual basis so they can brush off problems you'd rather be able to take care of yourself.

    But a solution is often a set or range of products, and in the case of vendors like IBM those products are paired with service. When you sell a product, the assumption is that once you sell it, you want nothing to do with the customer from thereon after. Tech support is offered only for problems. But if you are trying to impress upon customers the notion that the product and the sometimes rather involved, in-depth service associated with it are equally important, the term "solution" makes sense.

    While the term is applicable to IBM, it's not applicable to many products that simply bill themselves as a solution, when in fact the vendor would rather eat rat poison than provide integrated and thorough support.

  • Re:Word (Score:4, Insightful)

    by skrolle2 ( 844387 ) on Monday January 03, 2005 @07:32PM (#11249471)
    You list some neat pieces of syntactic sugar that generally makes C# a lot nicer to program than Java, but to call that "much more" is a gross overstatement. They're both reasonably high-level object-oriented compiled virtual machine-using languages with large class-libraries. The only large difference is that C# is very much geared towards XML in all forms (which didn't exist when Java was made), but other than that the differences are minor.
  • by gelfling ( 6534 ) on Monday January 03, 2005 @07:37PM (#11249514) Homepage Journal
    Products that don't work
    Service providers that can't make it work
    Customers that don't care if it does
    Executives that don't know IF it does
    Solutions in search of problem that doesn't exist

    Designed to fail, working as designed.
  • Two computers. (Score:3, Insightful)

    by jafac ( 1449 ) on Monday January 03, 2005 @07:39PM (#11249525) Homepage
    There are two kinds of people in the Computer Industry.

    1. People who see computers as neat and useful tools, which can be adapted for nearly any purpose. Software or Products which give people additional ways to use their computers - especially tools that improve productivity, either personal, or at work, are generally going to succeed in the market place. The way to sell such products is often referred to as "Pull" Marketing.

    2. People who see computers as neat and useful ways of getting consumers to spend money on stuff they wouldn't have otherwise spent it. This is accomplished by pushing crippleware that looks neat on the surface, but is essentially useless to a user until they pay more money to unlock the useful features, or basically, the software ends up being a complicated scam to get someone to sign up for some service with a monthly fee.
    These products ultimately fail. This kind of marketing is referred to as "PUSH" Marketing.

    At the end of the day, #1 is the correct way of looking at computers, and there are a couple of tennants of business and innovation that prove it:

    "Built it, and they will come."
    and
    "Invent a better mousetrap, and the world will beat a path to your door."

    Unfortunately, High Tech Marketing is full of people who want the world to beat a path to their door, without all that costly and complicated mousetrap-inventing stuff.
    They spend so much effort trying to find innovative ways to get people to spend more money, rather than innovated ways to make computers more useful tools for people to buy, because their lives are improved.
  • by bhadreshl ( 841411 ) on Monday January 03, 2005 @10:55PM (#11250884)
    There is a distinction between a 'product', 'service', and 'solution'.
    The service sector is being overpopulated with competition as outsourcing increases.
    So companies have no choice, but to innovate, and provide a *solution*. This "solution" does a lot more than just a simple service. This is what will drive the service sector in the future
    Wouldn't it be better if a software product provided a solution rather than just a service. Your statement is also valid because some companies nowadays say they are providing a "solution" to sound almighty, but in fact, it is just a service or a product.
  • by LaCosaNostradamus ( 630659 ) <[moc.liam] [ta] [sumadartsoNasoCaL]> on Tuesday January 04, 2005 @08:51AM (#11252669) Journal
    There isn't a price tag on "solution" since in the mind of the marketing twit, you'd pay anything for a "solution". Price is no object for things which solve your problems. And thence lay the heart of the high-tech scam: it will solve our problems. Instead, it has created many, many more problems.

    After all, what would you pay for a "problem"? That's exactly what IBM, Microsoft, Sun and all the rest are really selling you: PROBLEMS. High-tech infrastructure is plagued with problems. But no marketing drone is going to even go near the honesty in that.

    I've been busily replacing perfectly good Pentium IIs with expensive P4s. The price alone should have told the company execs that this is a PROBLEM. But they are sold on "solutions" ... for instance, on the myth that employees are a "problem", so replace them with machines. But machines introduce all kinds of other problems ... which marketing n00bz never seem to include in their presentations and shiny brochures.

    Don't get me wrong here. I approve of selling problems as "solutions". Those are giant IQ tests, and America's corporate execs are failing them left and right. What bothers me unduly is how long it's taking the American investor to realize this. After all, stupid people are simply a baaaaaad investment.

Make sure your code does nothing gracefully.

Working...