Archive for the ‘IMF Updates’ category

Flexibility Key During Project Implementation

January 26th, 2012

Organizations are constantly in the midst of implementing or rolling out huge projects that impact the business, users, and customers. This process is rarely easy when you have deal with unexpected challenges, whether it is technology related, a scheduling conflict, or whatever. That is why it is critical for the success of the project that you and your team remain flexible throughout the implementation. Rob Murphy, a Program Manager for the U.S. House of Representatives, recently led one of our Web Forums and he discussed the idea of project flexibility. The House is in the process of implementing a Financials ERP so Rob spoke about some of the challenges they have encountered and how being flexible has enable them to be successful thus far. You can read the full IMF Report on Rob’s presentation here.

Below is a snippet from the report where Rob talks about the advantages of limiting project customizations…

When it comes to large technology projects, many organizations tend to stay pretty close to vanilla in terms of their approach. Certain companies may flat out say “no we are not going to have any,” “you can have one or two different levels” or “if you have some they have to be this type of characterization.” They can have only so much effort and impact, which is excellent. You definitely want to limit it because these are very complex applications, even without customizations. They still roll out patches and fixes regularly whether it is desktop computers and very simple software or more complex. There will always be patching and fixing taking place. Vendors and IT organizations know that so any time you can limit the complexity on your end it is an advantage.

You will reach a certain point on most projects where customizing becomes a necessity, whether it means minimally invasive tasks like designing your own reports or possibly more invasive items. The project team at the House started out with the idea that they were going to stay vanilla and only do a couple of items, some of which were required. They may have been for reporting or regulatory needs but there were certain items they had to produce. The software package that was selected may not have all of the features, fields, and data that are needed. Consequently those fields and reports will need to be created…

Performance Management Reporting

November 4th, 2011

We recently held an IMF Connect with several member companies based on “Performance Management Reporting.” You can download the full IMF Report on our website in the Published Reports section. This was a great discussion focusing on some very pertinent issues including:

-          A balanced scorecard approach

-          Consolidating your metrics and KPIs to a select few

-          Dashboard organization and drill-down capabilities

-          Erasing silos around the business and technology

-          Establishing common metrics for different organizations tasked with different objectives

-          Customer survey response rates and asking “the right question”

Here is a brief excerpt where one member company talks about what they see in the consumer banking industry in terms of dealing with large metric indexes:

We haven’t had a lot of luck with that but I’d love to hear other opinions on this. Rolling things up into this big index turns out to be useless because no one can understand it. I followed index 97.43 and our goal is to get down to 97.22, that sort of thing. Instead you could say we want to have an organizational goal that 95% of our things happen on time. So everybody has their own individual SLA’s but you better make 95% within your SLA or within that scorecard as you break it down. You could also say something like you must attain a customer rating of XYZ and find that common metric. At the end of the day, if you’re looking at what the customer wants, they only care about when we’re late or we make a mistake. To that point you want to find how many errors we make, how many times we’re late. You generally look at it that way and then you roll it down by individual. Now that is the customer satisfaction side and you can do the same thing for sales. However, since a lot of people share IT or operations on the productivity side, you can say we want to have a certain cost per customer or account and find something to normalize it across that. Of course this is all much harder than it sounds but finding that common metric is always hard.

What we are experiencing right now in the consumer bank is that having people get rid of their individualities is very difficult. For instance, trying to compare ATMs next to mortgage next to a branch is not easy. On the other hand, if you can have people agree on those key customer metrics, like how many times are we late, make mistakes, or do something that costs us money, then you can track those things. Just in our mortgage business alone there are five sub-lines of business and a few thousand people. That’s not just across the business, that’s in one LOB. It is tough getting people to sign onto these four particular things that we need to run our business. However, unless you do that, you’re going to end up building it from the bottom-up and having a million metrics that don’t roll up anything. So you end up with two things. You either end up with an index that means nothing or you end up with a 100 page report because all you are doing is up pages and then shoving that up to senior management. The balanced scorecard fails if you do any one of those thing…”

Benchmarks for StaaS

October 7th, 2011

A consistent focus area for IMF benchmarking clients over the past year or so has been more robust implementations of utility models for storage. We’ve all seen the charts in meetings showing exponential growth of storage footprints year over year, and seen storage become a bigger and bigger piece of the IT cost pie. Caleb Masland, who heads The IMF’s benchmarking practice, recently gave a presentation to members on benchmarks for storage as a service (StaaS). Below is a snippet from that report involving some observations on storage technologies:

Backup infrastructure is being virtualized quickly. This is the space where you can reach a lot of “low hanging fruit” because the environment tends to have a lower transaction volume. Therefore, you have some ability to take dedicated backup islands and consolidate them. Most physical and off-site media is disappearing. Physical tape in general is decreasing drastically and really only used for compliance purposes. There are more specific backup management policies that are being developed. Note that companies are not backing up everything because that is the easiest policy to make. They realize now there needs to be a correlation between data availability for business reasons and for compliance reasons. Somewhere in the middle is the right balance to strike as it relates to your data backup policies.

Storage resource management and storage footprint reporting are becoming critical skillsets. A lot of organizations have historically had a problem with footprint reporting in terms of storage installed on the floor that is allocated to business units, applications, or being utilized. As you move toward a StaaS model, companies need to take a step back and make improvements in their capacity management and planning. One trend The IMF sees is companies having more mature and robust capacity planning organizations and teams that are being centralized. More importantly, those groups are earning a seat at the table for major decisions about infrastructure upgrades and even project portfolio management…”

IMF members can download the full report here.