Archive for April, 2015|Monthly archive page

Overcoming the pain of Technical Debt

Many businesses are hamstrung by expensive and inflexible information technology. To wit: The average firm’s spend on IT has swelled to the equivalent of between 4 percent and 6 percent of revenue, thanks in part to neglect, poorly executed integrations and the breakneck speed of technological change.

While the exact toll of lost productivity and hampered innovation for any given firm is difficult to quantify, it’s safe to say that the true cost IT is greater than what appears on a company’s ledger. Research firm Gartner estimates the total cost of poor systems architecture, design and development will reach US$1 trillion in 2015. Put another way, that’s an average of US$1 million per organization, according to analytics firm Cast Software, and US$3.61 per line of code.

This hidden expense is referred to as “technical debt.” Reining in technical debt is an ongoing challenge for IT leaders because the cost of lost opportunities is tricky to peg while the cost of modernizing legacy systems is immediately tangible and often significant. But understanding technical debt is vital for organizations angling to improve performance through new technologies, improved agility and tighter cost controls.

I first encountered the dangers of technical debt when I did consultant work for a medium-sized manufacturer. In our search for savings, we found that maintaining one legacy system was consuming nearly 85 percent of the firm’s IT maintenance budget while rendering the integration of new applications difficult and risky. Worse, support activities were diverting scarce resources away from growth-enabling automation initiatives.

In that instance the firm was able to successfully phase out the old system while phasing in a new, more effective and cost-efficient replacement. But the question remains: Why did the firm’s IT leaders run up so much technical debt in the first place?

“The challenge is twofold,” explains Mike Grossman, founder IDI Systems, an automation development firm that regularly confronts technical debt in the course of infrastructure projects. “First, how can you economically and practically support current processes and business capabilities with existing — and potentially deteriorating — code, tools and processes? And second, how and when are you going to transition these old systems to support your new business objectives?”

Think of a legacy IT system as an old clunker. The driver understands that buying a new car is cheaper and easier in the long run, but either doesn’t have the down payment on hand or can’t spare a day without wheels. So instead of efficiently getting where they need to go, they’re stuck trying to keep an old car running by repairing old parts and adding new ones.

Where the metaphor falls flat, however, is in underscoring the value proposition of abandoning the old. The difference between a messy legacy IT system and a modern, fully integrated and efficient one is greater than the difference between an old car and a new one. While either vehicle will get you where you want to go, a world-class IT system can take your firm places that your current infrastructure would never allow. This is due to the opportunities for innovation that arise from a top-notch system.

That’s not to say that eliminating technical debt is as simple as hiring a team of developers to rebuild your infrastructure from the ground up. Before any such decision is made, consider the following steps:

  • Calculate your existing technical debt. To do this, compare the capabilities of your current software and hardware to industry-leading versions.
  • Determine your firm’s goals. Consider both the extent to which your current activities depend on your legacy system and what new functionality you will require for future, growth-generating activities.
  • Identify and align around the priority areas for remediation.
  • Find and deploy talent to replace or redesign legacy systems.
  • Measure and track progress at a senior level along the way.

And remember: Even after you’ve successfully upgraded your IT systems, the threat of running up technical debt remains. This is due both to the changing nature of technology and of business. While senior leaders ought not to obsess over technical debt, keeping a vigilant eye on the efficiency and capabilities of IT operations can be the difference between running in place and forging forward.

For more information on our work and service, please visit the Quanta Consulting Inc. web site.

Advertisements

Gamification boosts customer engagement at Insurance firm

What is more boring, but useful, than learning about your workplace RRSP plan? What is more fun, but useless, than playing games at work?

“We regularly look outside our industry for innovative ways to help our customers learn more about retirement savings,” says Nadia Darwish, vice president, Market Development at Sun Life Financial. “Gamification was a natural fit.”

Gamification is less convoluted than the word implies. Essentially, the idea is to combine the basic appeal of video games — purpose, competition and the desire for mastery — with behavioral psychology to increase revenue. This could mean improving productivity, enhancing engagement or increasing sales.

Ms. Darwish and her team released an online game called Money Up in late 2014. Money Up features “missions” exploring the basics of retirement planning, investment asset allocation and different financial products. Players are quizzed about what they’ve learned before they can proceed to the next level and, like a classic arcade game, there is a leaderboard so employees know how they stack up against their colleagues.

The business results exceeded management’s expectations, Ms. Darwish says, generating significant improvements in participation, contributions and product penetration. She attributes success to the game’s seamless integration with Sun Life’s broader “financial literacy” program and is particularly happy that Money Up reached “the unique Generation Y audience in a way that resonates with them.”

Making simple, functional games is easier today than ever before. With a modest investment, a behaviour-changing game can be designed, tested and released within six months. Here are five tips for developing a gamification strategy based on the experience of Ms. Darwish and her team:

Don’t treat gamification like a side project. Gamification must be considered a strategic initiative and should incorporate input from senior leaders.

  • Don’t gamify in a silo. Adopt a collaborative approach by soliciting feedback from both internal and external stakeholders at every stage of development.
  • Don’t lose sight of your goal. Work backwards from your desired result (e.g. educate customers) to ensure that your game is more than just fun.
  • Don’t lose sight of your audience. Put the needs of your potential players ahead of your messaging by developing a product for them, not you.
  • Don’t set it and forget it. Monitor performance and solicit customer feedback after launch in order to develop fixes and improvements on the fly.

When a gamification strategy fails, it’s rarely for lack of enthusiasm. Here are three common pitfalls:

  1. Uncertain ownership. It can be difficult to determine who should ‘own’ a project that necessarily spans multiple departments within an organization.
  2. Narrow thinking. It can be difficult to articulate a compelling business case for something with which an organization has no prior exposure.
  3. Lack of knowhow. It can be difficult to develop a successful gamification strategy without experience in game design and behavioural psychology.

But the potential benefits of gamification are too significant to throw the baby out with the bathwater. The trick is tempering ambitious vision with lean resource allocation and a willingness to pivot along the way to mitigate risk and keep the project within its intended scope.

For more information on our services and work, please visit the Quanta Consulting Inc. web site