Gaining buy-in for software modernization

00:00 → 00:02

The success of software modernization depends on

00:02 → 00:05

winning the support of the key stakeholder groups.

00:05 → 00:08

First, you need to know them inside out, and second,

00:08 → 00:11

adjust your actions and communication for their needs.

00:11 → 00:12

How to do it?

00:12 → 00:15

I'm Magda, senior business analyst in Merixstudio.

00:15 → 00:19

In this video, I'll introduce you to three main modernization

00:19 → 00:21

process affected parties.

00:21 → 00:24

I will show you the potential objections and concerns along

00:24 → 00:26

with the ways to address them.

00:26 → 00:27

Let's go.

00:31 → 00:34

Getting the board on board is the first step in gaining

00:34 → 00:36

support for software modernization.

00:36 → 00:39

Achieving the buy in is necessary for securing funds

00:39 → 00:41

and making system a priority.

00:41 → 00:44

The problem is that the board might not perceive it as a

00:44 → 00:46

business oriented activity.

00:46 → 00:49

That's why you need to build the modernization value upon

00:49 → 00:51

economic advantages.

00:51 → 00:54

Translate tech outcomes into biz profits.

00:54 → 00:57

You can do this by using the metrics and arguments that

00:57 → 01:02

speak to revenue, customer experience and market position.

01:02 → 01:05

The other challenge you may face is underestimating the

01:05 → 01:09

size of tech debt and its negative impact on the organization.

01:09 → 01:11

This translates into modernization outcomes being

01:11 → 01:13

seen as tentative and blurry.

01:13 → 01:15

If you want to deal with that,

01:15 → 01:19

start by comparing the cost of performing and postponing a

01:19 → 01:20

system upgrade.

01:20 → 01:22

Show the whole picture of the process,

01:22 → 01:26

the areas the legacy system touches and how modernization

01:26 → 01:28

will address these pain points.

01:28 → 01:31

Last but not least, the board might consider the

01:31 → 01:36

modernization process as more disturbing than using outdated systems.

01:36 → 01:39

Remember to propose solutions that won't interfere with

01:39 → 01:42

business performance but will accelerate growth like:

01:42 → 01:46

Solid strategy with a well thought roadmap Accurate

01:46 → 01:50

prioritization of goals and tasks Gradual transition to the

01:50 → 01:52

new technologies.

01:55 → 01:58

If people in general don't like changes,

01:58 → 02:00

digital users just hate them.

02:00 → 02:02

The modernization of the software means they will need

02:02 → 02:05

to relearn how to use it.

02:05 → 02:08

To avoid that, the users may downplay the burdens the

02:08 → 02:11

outdated app brings or even stick up for it.

02:11 → 02:16

However, behind the superficial sympathy stands a range of bots.

02:16 → 02:20

Your task is to uncover the hidden pains and show how the

02:20 → 02:22

upgraded system will relieve them.

02:22 → 02:24

Watch out for traps though.

02:24 → 02:27

Even if the gains are objectively valuable and

02:27 → 02:30

clearly defined, they might not provide users with enough

02:30 → 02:32

motivation to approve the change.

02:32 → 02:34

What's the reason behind this?

02:34 → 02:39

Users are afraid that using the new software will be difficult.

02:39 → 02:42

A flawed yet well known old system gave them a sense of

02:42 → 02:44

safety which they are losing.

02:44 → 02:47

These anxieties might be more intensive than a

02:47 → 02:49

rational definite profit.

02:49 → 02:53

So besides tangible advantages, I show an easy attractive

02:53 → 02:55

onboarding through the upgraded system.

02:55 → 02:59

Finally, gaining users' buy in is not only about

02:59 → 03:03

approval, but also about engaging them in the process.

03:03 → 03:07

That's crucial in the case of modernizing internal systems.

03:07 → 03:08

Unfortunately,

03:08 → 03:11

the users rarely notice how much influence on the work

03:11 → 03:15

these systems have and so they don't feel the need for active

03:15 → 03:18

involvement in modernization.

03:18 → 03:21

You need to secure the time for consultations and interviews as

03:21 → 03:25

well as the confidence that their voice will matter.

03:28 → 03:31

The internal IT team should be the most enthusiastic

03:31 → 03:34

about system modernization, shouldn't it?

03:34 → 03:36

Well, not necessarily.

03:36 → 03:39

Although everyday struggle with legacy code is usually a

03:39 → 03:43

nightmare, the fear of loss might gain the upper hand here.

03:43 → 03:45

What are developers afraid to lose?

03:45 → 03:49

Their jobs, of course, but also the authority and position.

03:49 → 03:52

They might not know the solutions that are going to be

03:52 → 03:57

implemented or have little experience doing tech transitions.

03:57 → 04:00

That's why you need to give the employee space for catching up

04:00 → 04:02

with new technologies.

04:02 → 04:05

On the other hand, mull over collaboration with a reliable

04:05 → 04:06

IT partner.

04:06 → 04:09

It will help you fill the talent gap quickly and adjust

04:09 → 04:12

team composition to the changing needs.

04:12 → 04:13

For the tech team,

04:13 → 04:16

outsourcing at least a part of the process can resolve the

04:16 → 04:18

problem of time shortage.

04:18 → 04:22

Thus, the other concern the IT employees usually

04:22 → 04:25

raise is maintaining, modernizing, and developing the

04:25 → 04:30

system at the same time requires additional resources.

04:30 → 04:33

And finally, the truth is modernizing the software is

04:33 → 04:36

neither the favorite nor the most attractive part of the

04:36 → 04:37

developer's job.

04:37 → 04:41

It's seen as tiring code fixing with distance effects,

04:41 → 04:44

many risks, and monotonous tasks.

04:44 → 04:47

The key to overcoming these motivational problems is

04:47 → 04:51

presenting a short term, yet detailed plan with quick wins

04:51 → 04:53

and small success of celebration.

04:53 → 04:58

Also, emphasize the know how your team will gain and the effects

04:58 → 05:00

it provides for the whole organization.

05:00 → 05:03

Of course, the list of stakeholders may be longer.

05:03 → 05:05

The rules remain the same though.

05:05 → 05:10

You need to uncover the needs and concerns to find a way to address them.

05:10 → 05:14

If you're looking for more insights about gaining ideas

05:14 → 05:17

for software modernization, read our white paper.

05:17 → 05:19

You'll also find their insightful knowledge about

05:19 → 05:23

roots of resistance to change together with tips and

05:23 → 05:25

methodologies to overcome it.