The Indicee Blog

Business Intelligence class needs a makeover

by Geoff Devereux on May 25th, 2010

The title of this post is an homage to Dan Meyer, a high school math teacher and TED speaker.  He argues that the traditional methodology for teaching math is fundamentally flawed.

“I sell a product to a market that doesn’t want it, but is forced by law to buy it.” – Dan Meyer

Watching his talk, I couldn’t help but draw a parallel to the way the Business Intelligence concepts and methodologies have traditionally been presented to non-techies.  Is it just a matter of complex tools?  Or is it deeper?

“The formulation of a problem is often more essential than its solution, which may be merely a matter of mathematical or experimental skill”  – Albert Einstein

Meyer references this quote by “the man”, Albert Einstein.  Can you think of how B.I. manages the formulation of data schemas, hierarchical data models, nesting, etc?  Bust open a textbook or Wikipedia, read it, then ask yourself, how engaging would this content be to someone who:

1. Lacks initiative

2. Lack perserverance

3. Lacks retention

4. Has an aversion to word data problems

5. Eagerness for formula reporting output

Meyer highlights these factors as being emblematic of his captive audience in the classroom.  I’ve made a couple of adjustments to tweak the context to that of B.I.  If you don’t agree that these factors apply equally to the vast majority of business users of B.I., please speak up.

Advances in technology are creating the ability to put the tools into the hands of the end user.  Our technology is proof of that; however, we still have some serious work to do on the owner’s manual.

For example, How would you deconstruct the process of building a data hierarchy to facilitate creation of a Data Mart?

I’ve recently started volunteering with Junior Achievement teaching business concepts to 5th graders.  You can see the attention of my little budding capitalists wax and wane throughout the session.  They haven’t yet learned to hide their expressions so when they “check out” it’s pretty obvious. But I’m glad for it.  I know exactly when I need to inject some PT Barnum into the act.

Let’s do the same for Business Intelligence.

Here’s Dan Meyer’s suggestions for fixing math education delivery.  Let’s do the same and give Business Intelligence class a makeover.

The Fix

1. Use multimedia

2. Encourage students business users intuition

3. Ask the shortest question you can

4. Let students business users build the problem

5. Be less helpful

I encourage you to watch the whole talk (below):

Enjoy!

  • Share/Bookmark

Business Intelligence Adds a Dimension to Your Strategy

by Geoff Devereux on May 10th, 2010

Everyone wants meaningful Business Intelligence (B.I.).  At least, everyone who hopes to do well in business endeavours to do so intelligently.  Everyone I know anyways.

Recently, someone kindly pointed out that B.I. is actually DETERMINISTIC as opposed to intelligent by its very nature…. being just a construct of rules and structure within an IT system.

This comment was brought about through a discussion around creating B.I. solutions, what is a good approach.

The talk actually ended sounding more like a Philosophy class than an IT group.  Inductive and deductive reasoning.  Asking questions.  Treating matters objectively.

Stuff about helping management understand their own strategy by questioning manifest business processes.  In order to arrive at answers to seemingly imponderable business questions.  Things like, “What are your business goals?”

Some Focus Points

- Let outcomes guide decisions

- Let goals guide focus

- Let value guide priority

* NORTH STAR Business Intelligence

The above-mentioned firm put on a talk through TDWI (The Data Warehousing Institute) in Vancouver last Friday and I was fortunate enough to attend.  For anyone local who is looking to better understand the B.I. space, these monthly meetings are a good start.  The local chapter is fairly “young”, but it’s been growing and I’ve got to say, the meeting was quite interesting.

Some other points that jumped out were:

- B.I. is a technical issue, but success is a human issue

- Always keep the broader vision in mind

- Understand that business processes, definitions, and meanings change over time

- Greenfield B.I. projects have an advantage [over existing systems (i.e. no baggage)]

- Think big picture, work the details

and – Choose for impact!


It appears the growing consensus in this group is that the technical barriers aren’t what is standing in the way of getting good B.I. spread all throughout the organization.  But it’s organizational psychology that sometimes stinks.

There’s a delicate balance that has to be struck.  Top management don’t want to feel like they are being lectured, or questioned.  But it’s education and Socratic inquiry that are required if the end B.I. solution is going to work.

In my view, part of the difficulty is that management doesn’t necessarily have their strategy worked out to the level of detail really required to get a “perfect” solution.  There’s a lot of moving parts regardless of business size.  But don’t look at me I’m just a software vendor.

Do you think I could be counted on to whip business strategy into shape?

Anyway you slice it, I think B.I. and strategy will always be inextricably linked.  As mentioned in the talk, these are tied into part of a feedback loop.

Helpful to remember this stuff.

Enjoy!

  • Share/Bookmark

Legacy IT Systems – Understand Your History

by Geoff Devereux on January 6th, 2010

1 hockey canada logoDuring the normal course of life, being part of a “legacy” is generally considered a good thing.  I am writing this on the eve of the IIHF World Junior Hockey Championship so legacy is weighing heavy on the mind.  The tournament includes the top ten national teams (players under 20yrs old) from around the world (Top Division only please).  As you might expect, Canada is a stalwart of the tourney and tonight will be battling the USA for its 6th straight gold medal.  Legacy – case in point.  Legacy is powerful, there’s a historical element and there’s an emotional one too.  Show me a Canuck who doesn’t get misty with talk of our game and I’ll show you a hoser-without-a-country.

Think about what you might consider a legacy.  Lots of Americans will likely read this, so let’s use something more Americana.  The Ohio State football program maybe? -> BTW, they need to optimize their website, it’s coming up 3rd when I google “OSU”.  We’re on the west coast, so how about USC?  Or how about this; the BCS Championship game is being played on Thursday – Texas Longhorns against Alabama Crimson Tide.  How does the legacy of these football programs affect all the students (past and present) from all of these schools?  Just to give you an idea, for the uninitiated, any college team worth a legacy gets roughly 100,000 fans in attendance PER GAME.

I think all of us look for these kinds of connections.  Of course, Benedict Anderson (International Studies prof at Cornell) would argue these are just Imagined Communities; but those arguments notwithstanding, the point is that normally legacy is a good thing.

Yet, in the realm of Information Technology, legacy takes on an entirely different complexion.  Legacy IT Systems are routinely the whipping boy of the modern organization.  If your system was built prior to last week, the inclination is to believe (fervently) that something better MUST exist and that this dog you’re currently computing on needs to be taken out back the woodshed.old_yeller

There seems to be very little respect and appreciation for the history of organizations that is captured by these Legacy IT Systems.  I think, anymore, we all just see the problems, work-arounds, and supplement that with a healthy dose of “the grass is always greener”.  I think that if you track down your IT guy and start asking some questions, you’ll be amazed at the history behind your systems.  Were there purchased over a number of years?  Has your organization grown by acquisition? What’s the oldest piece of hardware in the backroom?

We’re interested to hear what your organization is running on.  Share your story in the comments.  Maybe it’s time to cast the legacy of your IT system in a more positive light.  After all, no team has a perfect record.  It’s as much about the losses as it is about the wins.

Go Canada!

  • Share/Bookmark

Defining Business Intelligence

by Geoff Devereux on December 16th, 2009

The Historical View circa 1958

The notion of intelligence is…  “the ability to apprehend the interrelationships of presented facts in such a way as to guide action towards a desired goal.”

- Hans Peter Luhn, IBM Journal, October 1958

The above quote is generally credited with coining the term Business Intelligence (B.I.).  Luhn’s vision was ambitious for his time and it’s still ambitious today.  How much of the following article do you find relevant right NOW with respect to your business reporting challenges?

The following are direct quotes from the IBM Journal Article, “A Business Intelligence System” published 1958 with my commentary added:

Information is now being generated and utilized at an ever-increasing rate because of the accelerated pace and scope of human activities and the steady rise in the average level of education. At the same time the growth of organizations and increased specialization and divisionalization have created new barriers to the flow of information. There is also a growing need for more prompt decisions at levels of responsibility far below those customary in the past. Undoubtedly the most formidable communications problem is the sheer bulk of information that has to be dealt with. In view of the present growth trends, automation appears to offer the most efficient methods for retrieval and dissemination of this information.

With respect to the volumes of data being created in 1958, I think we can safely say, you ain’t seen nothing yet.  Keep in mind that 1958 was really the primordial soup of computing and information management.  At that time, the Integrated Circuit had just been developed which would pave the way for development of computing as we know it today.  Looking back on IT in 1958, I’m thinking it consisted of a “series of tubes”.

Luhn continues:

Ideally, an automatic system is needed which can accept information in its original form, disseminate the data promptly to the proper places and furnish information on demand.

So, in 1958, the concept of “on-demand” is also christened.  A blog I follow called, Only Dead Fish, by Neil Perkins references the Greek term, Kairos, recently when discussing the importance of context.  Kairos refers to, “the right or opportune moment” or “the supreme moment”.  I think this is the best way to think about the basic need/want underpinning the concept of on-demand.  I think this is how Luhn was thinking about it too:

One of the most crucial problems in communication is that of channeling a given item of information to those who need to know it. Present methods of accomplishing this are inadequate and the general practice is to disseminate information rather broadly to be on the safe side. Since this method tends to swamp the recipients with paper, the probability of not communicating at all becomes great.

  • Share/Bookmark

Accounting for Interdepartmental Language Barriers – Accounting and IT Part 2

by Geoff Devereux on October 27th, 2009

Last week we were talking about the language barrier between Accounting and IT.  I managed to maneuver the conversation to the more specific area of IT known as Business Intelligence (B.I.) in a laughably transparent attempt to further my own agenda.

Providing some standard B.I. terms without definitions, I was looking to gauge your understanding of typical B.I.-speak through a quick game of word association.  There were no responses.  I figure I’ll probably need to establish myself more before I can expect comments.  I’m also going to assume there is a vague understanding of these terms.  Taking a line from The Simpsons when Bart’s teacher asks him if he knows Long Division, Bart replies, “I know of it”.  I would argue these are the “I know of it” terms of B.I. for an average accountant.

  • Share/Bookmark
Older Posts »
RSS Twitter