Blog Detail

Please refer our previous blog, Blog No. 41, in which we promised to take up numerous details – starting with this blog. We need to look at these details in relation to the key ideas consolidated and listed in Blog No. 41 to ensure our success in our mission.

Yes, there are numerous details… We can’t take them up all at once. Let’s take a detail in every blog now onwards, including today’s blog.

As you must have taken a cognizance of in our earlier blogs, we have been re-emphasizing the supreme value of “expertise” in supporting an engineering requirement. The development of “expertise” requires a resource to stay – in a “climatic condition (–> Domain)” – preferably in the same “soil (–> Organization)”. How long? – As long as it may take…

Let’s review the above in sharp contrast to the prevalent situation in which a resource hops from domain to domain, and organization to organization for non-engineering reasons, like inability of a resource to hold a long-term career perspective, inability of an organization to hold a long-term business perspective, etc.

So there are three vertices of the expertise-development responsibility matrix – Resource, Domain, Organization. There is an absolute need for synergy among them to ensure the feasibility of the end coveted result.

Let’s review the reasons for the current “otherwise” state:

A business development structure without a foundation of expertise-based engineering

As a result of the above, a shaky organization with inherent inability to offer a much-needed prospect to a resource to “stay and stay in a particular domain”!

The future direction is obvious…Isn’t it? The so-called problem of attrition is largely due to the above, along with a few more reasons which we’ll discuss in our next blog.