veryard projects - innovation for demanding change

thoughts 1998

veryard projects > news > thoughts 1998
thoughts on this page
> when things settle down
> customer call centre
> eclipse
> supply chains
> the power of networking
> different situation, same control
> customers going spare
> customer unknown
> long in shape, short in duration
> it takes two to tangle
> global recession
> man-made virus

please scroll down

thoughts moved elsewhere

> competition
> intelligence
> internet risk
> process invisible
> technology progress
> thinking the unthinkable
> Barry Palmer



When things settle down ...
"E-commerce is just a fad.  Lots of people are just throwing money at it, getting their fingers burned. When things settle down, it'll be back to basic business principles."

Imagine a Rugby schoolboy saying: "I'm not going to pick up the ball.  I'm just going to kick it, like my father and grandfather before me.  I'm sure this handling is just a fad, and then we'll settle back down to good old kicking."

If you want to stay in the game, you have to understand that the rules have changed, are changing, and will continue to change. If you have enough power, proximity and interest, you may try to change the rules of the game, or at least influence them.  (Changing the rules of the game is itself another game.)

The removal of exchange controls permanently changed the basis of investment and international trade, and led to a situation where the currency and options markets are swamped by speculation.  (For every businessman who wants to swap yen for euros to settle a debt, there are dozens if not hundreds of sharp kids playing the money markets.)

That's why e-commerce, e-business, and all the other e-stuff, are important - because the basis of competition has permanently changed.  Sure, there are more losers than winners - but that's competition.



Customer Call Centre
The thinking behind call centres was that customers would respond favourably to a friendly voice on the end of the phone.  Market research indicated a preference for Scottish accents, as conveying an impression of personal, friendly and efficient service.

This strategy has backfired - because the service isn't really personal, friendly or efficient - in other words, the strategy was an inauthentic one, based on an inauthentic relationship with the customer, and an inauthentic selection of staff by an attribute falsely connected to genuine friendliness or efficiency.  Nowadays, when I hear a Scottish voice on the other end of the phone, my heart sinks - another bloody call centre.

more


Eclipse

Supply Chains?

The Power of Networking
amazon.comamazon uk

Different Situation, Same Control

Customers Going Spare
My friend David, who is an expert on software components, recently complained about the maintenance on his expensive German automobile. He wanted the garage to fix a faulty rear light. It turned out that the light was part of a larger component and he needed to have the entire rear light cluster replaced, costing several hundred pounds.

He asked who made the decision to set the unit of replacement at the level of the rear light cluster. Was it a production engineering decision? Surely the marketing role would not have misrepresented customer requirements so badly?

Sadly for us consumers, the key question for many marketing departments is not

(A) which component architecture would be most convenient for most of our customers? but (B) does this component architecture make any difference to the likely volume of sales? In other words, does the car-maker care whether it costs you more to fix your rear light? How much money do they make from selling spare parts?

(Perhaps the most skilled marketing departments are those that manage to put an A-style presentational spin on a B-style decision. In other words, they can persuade the customers - and even the industry analysts - that they put the customers' interests above their own. And then there's Microsoft.)

Another industrial analogy is the mobile phone. Most of us have good-looking phones, with lots of features, but with an almost unusable menu structure, with strange interactions between the features of the phone and the features of the connection service (I have not succeeded in sending a fax from my phone yet) and no upgrade path (I cannot use some of the accessories that are available for my type of phone, because my phone has an earlier version of the software). As long as we consumers tolerate this, the manufacturers have no incentive to improve these aspects of the product design.

The relevance of this for software components should be obvious. Any software vendor (or consortium) that designs a component architecture that is not driven by their own business advantage is naive and therefore strategically vulnerable. One of the most important jobs for industry analysts is to highlight the potential advantages and disadvantages (for the purchaser) of various architectures.

When Jeremy Clarkson reviews expensive German cars on BBC2, does he mention the rear light assembly? Or does he concentrate on the sexy corners and go-faster stripes? If the Jeremy Clarksons of this world were genuinely concerned about insurance and maintenance costs, wouldn't the car manufacturers would start to take them more seriously too? What are the hard questions I should ask my car dealer, next time I buy a car? What are the hard questions I should ask my software component dealer?


Customer Unknown
I've just received some junk mail from a well-known vendor of OO modelling tools, inviting me to attend a presentation by some well-known OO gurus.

The envelope is addressed to: "Richard Veryard, Unknown". I take this to mean that the name of my company is unknown - to them.

As a technical expert, I can immediately jump to conclusions about the database structure and data processing system that have produced this result. And I might reasonably assume that the vendor's own tools were used to design and implement this system.

As a business adviser, I would be more concerned about the potential effect on customer relationships, and the apparent failure to regard this as worthy of anyone's attention.

Of course, such technical oversights are all-too-common. Usually I just smile and toss the envelope into the recycling bin. But when it comes from people who claim expertise in the area - who ought to know better - I am rather more critical.


Only Connect
It has become common for clubs and charities to dump a perfectly meaningful name in favour of something bland. I suppose it started with RELEASE. Then the Marriage Guidance Council became RELATE, and the Spastics Society became SCOPE. What's left? Perhaps the RNLI will become FLOAT and WaterAid will become SINK.

One can sympathize with their motives, of course.  The old names might have seemed restrictive, or potentially offensive. But at the same time, the loss of meaning may be regretted.


Long in Shape, Short in Duration
Old dictionary definitions were sometimes more clever than useful. In old editions of Chambers dictionary, you may be lucky enough to find a witty definition of eclair: a cake long in shape, short in duration.  (This has now been converted to a more prosaic definition, but one which retains a trace of the old definition: a cake long in shape, covered in chocolate. I think I also detect the same hand in the definition of shema: a Jewish prayer, with a long history ...)

Long in shape, short in duration. This could also be the definition of an ideal consultancy assignment. Large enough to get your teeth into, but intense enough to provide quick satisfaction.


It Takes Two to Tangle
Disease mutates and evolves: new flu viruses, more virulent forms of TB. As the human immune system and/or the drug companies develop resistance to one form, another form appears, which elegantly evades our best defences.

Once upon a time, computer programmers could easily recognize spaghetti code by the presence of one word: GOTO. It was considered harmful; programming languages were developed in which GOTO was unnecessary or impossible; generations of programmers were trained to resist anything that resembled a GOTO. But the pattern or meme mutates, and reappears in a new form, designed to bypass our programmed resistances. Large complex computer systems are now being developed; each software component may be impeccably designed and coded, but these software components are wired together (using some form of scripting language) into something that we can only regard as a new manifestation of spaghetti.

The use of good patterns, and the avoidance of negative patterns or anti-patterns, can easily become trite or obsessional. An interesting pattern mutates, evolves, morphs. We must be alert to every new manifestation.

more


Global Recession
A little while ago, some doom-mongers in the software industry were suggesting that the Year 2000 problem could cause a significant number of firms to fail, leading to a global recession.

The global economy now seems to be managing a recession quite nicely thank you very much, with no help from software at all. How humiliating - even when we think we've really screwed up now, the rest of the world has much more serious problems than software to worry about.


Man-Made Virus
A virus epidemic relies on the fact that there is a large number of similar individuals to be infected. Exploiting this fact, irresponsible or malicious software engineers have developed software viruses. Large communities of closely connected computers running the same operating system are particularly vulnerable to these software viruses.

more

As genetically modified plants become more widespread, it may not be long before disaffected or disengaged biotechnicians start producing plant viruses, specifically designed to attack the modified genetic material. Such viruses may cause much wider devastation than previous plant diseases, because of the wider circulation of the genetically modified organism.

Or then again, perhaps Nature will manage the job much better.

more



veryard projects - innovation for demanding change veryard projects > news
Technical update November 1st, 2003
Copyright © 1998, 1999 Veryard Projects Ltd
http://www.veryard.com/news/thoughts1998.htm