Commentaries and insightful analyses on the world of finance, technology and IT.

« An Incentivized Anarchy | Main | The Time-Travel Hypothesis »

Products - A Business Perspective through Technology Coloured Glasses

As I was browsing through my news feeds for the day, I began to wonder how much a couple of my favourite ones drew stark parallels to the current state of existence of business software products. On one hand, my personal favourite, engadget, abuzz with new developments, innovation, product launches on the gadgets and allied areas (leaving me dazed on how often there is something similar happening on the business software front); while on the other hand, lifehacker, flooded as usual with tips on maximising productivity and making the most of various softwares (something where most organisations have paid limited attention to, leaving vendors with the lack of impetus to tread in that direction).  The traditional business software products have only accentuated these miseries, ending up as nothing more than an isolated block in the organisation's application portfolio.

How often have you crumpled under the social pressure (or a mad zest?!) of buying of a hot new gadget and leaving it lying un-used? The state of risk management softwares hasn't been much different with the coercive factor being 'compliance'.

All the recent financial happenings have only heightened the debate about the ab(g)ility of organisation to respond to changes. How to make the empowering technology, agile, is the real question? In the world of risk management in particular, the ability of the business to flex technology and its ability to respond make all the difference.

Imagine your house as a non-separable whole where you can't add anything new (say, furniture) as much as you can't remove any other. Well, that's today's products for you!

Do you think you can always get saas-y? (We'll put that in perspective in a later post)

ADM remains painful in these cases - While I may be in the market for a new pc, I don't wish to witness how the platters in a hard disk are put together; or the die on the processor...

From a technology perspective, most business needs, to a great extent, can be addressed by a cogent organisation of a set of configurable components. For instance in a business scenario pertinent to risk management, Basel business hierarchy, risk rating, issue remediation, LDAs and EVTs translate into the likes of simple tree builders, workflow, rules engines, analytics, reporting tools etc. Leaving the configuration of every element in its silo make upgradeability and portability a cinch. Loosely couple these together with the business logic, standardise data access layer (with say, hibernate) to make it database agnostic and factor in the flexibility of the UI layer, and you have a componentised product framework in your hand. Want only select functionalities - no problem, just toss out components that you don't need, retain only relevant configurations in the remaining - flex that 'modular' muscle.

'Shared Infrastructure' is an undeniable value proposition. Apart from saving tons of money in duplicate investments, it provides the much needed business (process & system) integration that product silos can't. To illustrate, If your organisation happens to purchase / upgrade, say the intelligence engine, you can squeeze out every penny by making it available to all applications, and also where needed, by sharing the intelligence across the board. Atleast with intelligence, that's how it's really meant to be, isn't it? And what's more, your products remain as recent as their newest updated component

Business software products have transcended being applications and become the 'platform'.

If ever, there is a lingering thought about if and how this would work, rest assured, at Infosys, these methodologies have been tried and tested.

The definite question is, what does all of this have to do with risk and compliance - Well, to sum up my previous blogs: a brave new world; changed paradigm; a new breed of approaches...and this is technology catching up.

Having planted the thought, I take a pause before examining its particular significance in the risk(y) business...


Vikram, this is definitely a refreshing way to look at striking a balance between ADM and products - the best of both worlds. I am quite fascinated, look forward to more insights on this in your later posts. Cheers.

You guys have provided a new perspective to componentisation and modularisation, something which, so far, has been used to refer to the organisation of the source code. One thing that I was clear all the way through was that only an IT vendor can provide such innovation, a product vendor cant imagine - My belief has been reinforced.

There's a point here if you observe the developments since FB n twitter. They built a common platform to do the "sharing and networking" stuff and now almost every site piggybacks (thru 'like'or 'Tweet me' options) on their infrastructure instead of creating their own - Simple, shared IT structures are the way of the future...

Manufacturing cos reuse production lines, even tech cos reuse codes but somehow ironically many other organisations fail to extract best of their IT investments. This is a right step in that direction.

Well said. Extrapolating your example, the 'usual' products we know of, are akin to, those branded PCs early in the day - But as the realisation on building to needs grew, the assembled PC market grew to mammoth proportions.

My personal belief on why this would be a better approach is

1. Given the rapid obsolescence and ofcourse, specific org needs, the user is bestowed choice to decide whether & what to upgrade
2. What the above does is also clearly delink business and technology portions of the S/W in the sense that technical needs which do not involve the need for a new functionality do not call for the vendor
3. Also, many orgs do have enterprise wide licenses, particularly for reporting and analytical tools which would be put to better use here. Anyways in traditional products, one cannot expect the vendor to be the best on building all the components
4. Most significantly for small enterprises, it allows the usage of freeware equivalent components

Good one...

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter