16.12.2015 Views

the new hr

1NT8tPl

1NT8tPl

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>the</strong> only constant.” Connect <strong>the</strong> two statements<br />

and you realise that it is intelligence, and not<br />

knowledge, that helps us handle change.<br />

Why is it imperative to transform from<br />

a knowledge-based organisation to an<br />

intelligence-driven organisation?<br />

In <strong>the</strong> intelligences-framework, agile organisations<br />

have to discard <strong>the</strong> old model of knowledgebased<br />

organisation that evolved in <strong>the</strong> 1990s, and<br />

embrace <strong>the</strong> <strong>new</strong> paradigm of intelligence-driven<br />

organisations. I do not use <strong>the</strong> word paradigm<br />

lightly—we do indeed need a paradigm shift.<br />

When <strong>the</strong> organisation is driven by intelligence,<br />

<strong>the</strong>re are two advantages: first, it knows which<br />

knowledge-base to use under what circumstances,<br />

and second, even when <strong>the</strong> organisation does<br />

not have <strong>the</strong> ‘knowledge’ needed to handle <strong>the</strong><br />

situation at hand, it can use intelligence to find<br />

solutions. These two situations are repeated in<br />

different forms across every size of organisation in<br />

every part of <strong>the</strong> world. Thus, <strong>the</strong> <strong>new</strong> imperative<br />

is an intelligence-driven organisation, which<br />

operates in a business world where knowledge is<br />

necessary but not sufficient.<br />

Could you elaborate on <strong>the</strong> Vivékin<br />

Intelligences Framework, and its key<br />

aspects?<br />

The important mind shift is to recognise that<br />

agility is a blanket term—it signifies all kinds of<br />

flexibilities. We need to think of not one agility,<br />

but five different agilities. In Nimble, I argue that<br />

a company that wants to be agile should focus on<br />

developing five intelligences, each of which drives<br />

an agility—analytical, operational, inventive,<br />

communicative, and visionary. Fur<strong>the</strong>r, <strong>the</strong> use<br />

of <strong>the</strong>se five agilities should be sensitive to <strong>the</strong><br />

organisation’s current context. For instance,<br />

in one context, <strong>the</strong> organisation may need to<br />

use more analytical and communicative agility,<br />

and in ano<strong>the</strong>r, use more operational agility. To<br />

be an agile organisation, <strong>the</strong>refore, <strong>the</strong> senior<br />

management must pay attention to developing<br />

<strong>the</strong> different agilities and also enhancing <strong>the</strong><br />

context-sensitivity needed to best benefit from <strong>the</strong><br />

multiple agilities.<br />

Sometimes, companies in <strong>the</strong> midst of<br />

being ‘agile’ lose sight of <strong>the</strong> larger picture<br />

and miss <strong>the</strong>ir step. How can this be<br />

avoided?<br />

The key to avoid this is to develop visionary<br />

intelligence. Two central questions must be asked<br />

each time we make what we think is an ‘agile’<br />

response: (i) long-term—what do we think will<br />

be <strong>the</strong> effect of this response t<strong>hr</strong>ee or five or ten<br />

years from now? and (ii) width of impact—how<br />

many people or processes will be affected by<br />

this response, and in what ways? For personal<br />

leadership decisions, <strong>the</strong>se questions are asked<br />

and answered by an individual, and for team or<br />

organisational responses, a team needs to weigh in<br />

on <strong>the</strong>se questions.<br />

Given <strong>the</strong> need for agility across <strong>the</strong><br />

company, is culture sacrosanct or<br />

contextual?<br />

I would say that an agile culture, which is<br />

contextual, is sacrosanct. In a truly agile company,<br />

agility is not in some pockets, but as you rightly<br />

say, agilities should be developed and used across<br />

<strong>the</strong> organisation. The organisational culture<br />

should be open, inquisitive, and innovative, where<br />

people are allowed to take risks, but wisely. Since<br />

‘wisdom’ is subjective, an agile organisation’s<br />

culture will tolerate failure and constantly<br />

learn, not only from its own mistakes but also<br />

from those of o<strong>the</strong>rs. But above all, <strong>the</strong> most<br />

successful and long-lasting companies are those<br />

that truly use multiple agilities and are firmly<br />

guided by visionary intelligence. Such companies<br />

are tremendously nimble, but also think ‘beyond<br />

top- and bottom-lines’ and ‘beyond <strong>the</strong> company’.<br />

As a result, truly agile companies create benefits<br />

for <strong>the</strong>mselves, for <strong>the</strong>ir people, and most<br />

importantly, for <strong>the</strong> world at large.<br />

(As told to Poornima Subramanian.)<br />

48 INDIAN MANAGEMENT NOVEMBER 2015

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!