WEBVTT

1
00:00:00.210 --> 00:00:02.010
<v ->When leaders are thinking about</v>

2
00:00:02.010 --> 00:00:04.740
IT cost optimization programs,

3
00:00:04.740 --> 00:00:09.740
they need to think of the whole set of levers

4
00:00:09.810 --> 00:00:11.610
in two dimensions.

5
00:00:11.610 --> 00:00:13.500
One is efficiency,

6
00:00:13.500 --> 00:00:16.140
and then the other is effectiveness,

7
00:00:16.140 --> 00:00:18.750
and both are very, very critical.

8
00:00:18.750 --> 00:00:21.960
Now, there are some levers that they will apply

9
00:00:21.960 --> 00:00:24.360
which improve both the efficiency

10
00:00:24.360 --> 00:00:26.190
as well as the effectiveness.

11
00:00:26.190 --> 00:00:29.370
For example, if you're implementing DevOps

12
00:00:29.370 --> 00:00:31.650
and CI/CD automation,

13
00:00:31.650 --> 00:00:34.920
that improves the efficiency of the software engineers

14
00:00:34.920 --> 00:00:36.720
but also improves the speed

15
00:00:36.720 --> 00:00:40.290
by which the products reach the business.

16
00:00:40.290 --> 00:00:43.980
However, there are some where there is a trade off.

17
00:00:43.980 --> 00:00:46.500
For example, when the CIOs look

18
00:00:46.500 --> 00:00:48.450
at their application landscape,

19
00:00:48.450 --> 00:00:50.250
and they are looking to rationalize

20
00:00:50.250 --> 00:00:52.860
some duplicative functionality,

21
00:00:52.860 --> 00:00:56.520
that has an impact on the business which is using those,

22
00:00:56.520 --> 00:00:59.550
and those are the right conversations to be had,

23
00:00:59.550 --> 00:01:02.790
and you need to have the deep analysis done

24
00:01:02.790 --> 00:01:07.410
as what is the impact on both the efficiency

25
00:01:07.410 --> 00:01:09.090
as well as the effectiveness,

26
00:01:09.090 --> 00:01:12.150
and is it worth, in your specific context,

27
00:01:12.150 --> 00:01:13.563
to make that trade off?