Skip to content

At Hype­r­i­on, our hon­est answer to that ques­tion is often a hard pill to swal­low for the client. Because if we’re com­plete­ly hon­est: if you still have to ask your­self at this point how you’re going to get trac­tion, it’s actu­al­ly already too late. Why a suc­cess­ful dig­i­tal prod­uct should­n’t be ​‘pushed’ but ​‘pulled’, and why the trash can is some­times the right next step, read on for our analysis.

The myth of the ​‘push’

Many orga­ni­za­tions still approach inno­va­tion as a lin­ear process: Idea → Build → Roll-out (Push). They invest heav­i­ly in change man­age­ment and inter­nal com­mu­ni­ca­tion cam­paigns to con­vince employ­ees to use the new tool.

But in real­i­ty, dig­i­tal adop­tion works dif­fer­ent­ly. A tru­ly suc­cess­ful pilot project bare­ly needs that ​“push.” A pilot project should scale itself through pure val­ue cre­ation.

The sig­nal you should be wait­ing for as a Busi­ness Direc­tor or IT Man­ag­er isn’t an approv­ing nod from the steer­ing com­mit­tee, it’s the impa­tience of the user.

The ​‘pull’: the sound of success

What does a suc­cess­ful pilot sound like? It sounds like users tug­ging at your sleeve. In our pod­cast, we recent­ly described it like this:

“Wow, it’s so great that this works now! But could­n’t this also fit into that oth­er flow? Because that would real­ly save me time. And could­n’t the invoic­es roll out auto­mat­i­cal­ly from there too?”

This is the gold­en moment. Users aren’t just ask­ing for the tool, they’re ask­ing for more.

  • They see the value.
  • They want it to inte­grate into their dai­ly reality.
  • They become ambas­sadors to their colleagues.

If that ​“pull” is miss­ing, if you hear silence after the test phase, or worse, if you have to force peo­ple to log in, then you don’t have a scal­a­bil­i­ty prob­lem. You have a val­ue problem.

The ​‘sunk cost’ trap: daring to throw it away

Say you’ve built a tech­ni­cal­ly per­fect prod­uct, but that ​‘pull’ nev­er comes. What do you do then?

The human (and busi­ness) reflex is: fix it. We’ve already spent so much bud­get and hours, we can’t go back. We invest a bit more in train­ing, tweak the inter­face a lit­tle, force adop­tion through policy.

At Hype­r­i­on, we advo­cate for a more painful but health­i­er approach: dare to look at the trash can. Some­times you have to be will­ing to say: ​“This isn’t work­ing. Get rid of it.”

That sounds like destroy­ing cap­i­tal, but it isn’t.

  1. The lessons are the val­ue: you’ve learned what does­n’t work. That knowl­edge is cru­cial for the next attempt.
  2. Stop the bleed­ing: keep­ing a sys­tem alive that no one has embraced, and forc­ing it to scale, costs far more in main­te­nance, licens­es, and frus­tra­tion down the line than pulling the plug now.

Start over. Build some­thing new. Use the lessons, not the code.

The lifeline: business accountability

Is it always the fault of the prod­uct or the soft­ware? Cer­tain­ly not.

Some­times we see clients where the solu­tion gen­uine­ly holds up, but the orga­ni­za­tion freezes up. There’s fear of change, or pri­or­i­ties are unclear. At that point, our role shifts from ​“IT part­ner” to ​“strate­gic advisor.”

That’s when it’s time to, fig­u­ra­tive­ly, knock on the Busi­ness Direc­tor’s table. The dis­cus­sion should­n’t be about fea­tures or bugs any­more, but about account­abil­i­ty.

“Look, we built this togeth­er because we thought it was a good idea. Do we move for­ward or not? If we want to make this suc­cess­ful, it’s no longer an IT project, it’s a busi­ness respon­si­bil­i­ty. You need to show own­er­ship now.”

With­out that ​“Busi­ness Spon­sor” who sticks their neck out and says ​“From now on, this is how we work, and here’s why,” even the best soft­ware will die a qui­et death.

Seek out the resistance

Inno­va­tion isn’t a straight line. It’s a process of dis­cov­er­ing, fail­ing, and dar­ing to confront.

Work­ing on a pilot project and unsure about the next step? The lit­mus test is sim­ple: lis­ten to your users. Do you hear enthu­si­asm and demand­ing new ques­tions? Then it’s time to scale. Do you hear silence? Then be pre­pared to face the con­fronta­tion, whether with your prod­uct or with your management.

At Hype­r­i­on, we don’t just build tomor­row’s dig­i­tal solu­tions, we also dare to ask today’s dif­fi­cult ques­tions. That’s how we build your dig­i­tal future.

Listen to the full discussion

Want to hear Koen Ever­aert, Daan De Cat, and Tjel Breeur dig deep­er into the dynam­ic between busi­ness and IT? In this pod­cast episode, they dis­cuss unfil­tered why some projects fail and how an orga­ni­za­tion takes ownership.

Want to take the step together?

Reach out to us, and let’s explore how we can build future-proof solu­tions togeth­er. We’re just a mes­sage away!

Book a meeting!

Send us a message