• Home
• About
• Contact LÛCRUM
• Polls
• Archives
• BI EVENT Sept 1, 2010

• Business & Leadership
• Business Intelligence
• Featured
• Jobs
• LUCRUM News
• Podcast
• Technology

Subscribe

On Not Reinventing the Wheel, Part 1: Take Your SharePoint Data With You

At some point in every project, I’m usually confronted with the question – should we build or should we buy?  The pendulum of thought on this topic swings back and forth.  As a consultant that regularly advises clients on these kinds of questions, my current read is that the mindset has moved toward the “buy” side on some key fronts.  The trends underlying this, and their impact on both business and technology, are complex and evolving.

Another way to frame the discussion is, “Has someone already solved that problem?”  When the answer is yes, the existing solutions deserve a good look.  In my experience, a combination of both buy and build often turns out to be the right answer.

Let’s take the issue of getting more out of all that data that has been loaded into your company’s Microsoft SharePoint-based collaboration site.  Someone (probably many someones) has spent lots of time getting thousands of documents, contact lists, project plans, and other kinds of essential data into this amazingly versatile tool.  And if your portal has been well-designed, you probably find it an invaluable resource while you’re using your laptop or desktop at the office.

As soon as you try to get this information out using your mobile device, let’s say using your iPhone, it becomes a different story.  Even if you manage to navigate to the right place, the functional richness of the interface is not ideal when you move into the realm of finger touches and gestures .

So what to do?  Build a new, mobile version of your SharePoint site (probably a tough sell given the current economy)?  Or has someone already solved this problem?

As it turns out, the creators of SharePoint provided a shortcut to get to stored data directly.  This method uses web services – in human terms we might call it the “just give me the data, please ” service – to make the data available without the need to navigate through a web page.  It’s up to the application you’re using to determine how the data should look and be presented.

But until recently, not many people had solved the other part of the problem – taking the SharePoint web services and building an iPhone app to make it useable on a mobile device.

When he put two technologies together (buy + build), it increased the value of the data we already had, by making it more portable and our staff more productive.  Kudos to him for seeing the opportunity and going for it!

A growing number of developers have followed this lead to build iPhone apps that put all of your SharePoint data at your fingertips.  There are several choices now available in the Apple App Store, including (in alphabetical order):

• Attache: SharePoint Client (LUCRUM)
• iShare (Spyk Software)
• iSharePhone (Webstate)
• iSP-Browser (iSP Apps)
• Moshare (Moprise)
• SharePlus Office Mobile Client (SouthLabs)
• Sharetica (Celltica)

I’ll expand further on some of the topics touched on here in later posts, including more thoughts on the “build vs. buy” decision, the changing dynamics in data visualization, and how business intelligence solutions on mobile devices are impacting the way we work.

-Eric

Using Business Intelligence to Drive your own Recovery.

eWeek published a video describing the value of using Business Intelligence to find and exploit market and revenue opportunities.  Great point, and very well worth the 6:49 it takes to view it.  Many organizations are using BI to understand some of the basic historical results of their business.  It’s the next level of organization who begins to answer questions like the below using their BI toolset:

• What are my customer’s buying is a basic question, but moreover, what products do they buy together?
• Which products do they buy when times are tough?
• What did they buy during the last recovery?
• What aren’t they buying, and what should I recommend they buy?

All great questions, and clearly a value add of a strong BI platform.

eWeek – Using-Business-Intelligence-to-Find-Your-Economic-Recovery

BI and Software-As-A-Service (BI SaaS)

Who moved my cheese…again???

Economy challenges always seem to prompt new business models and productivity increases.  Remember 10 years ago and the dot.com bomb??  Prior to 1999, websites were being developed in great numbers but there was no revenue model to support it.  Those companies failed…others, that found a way to take a seemingly free service and get paid for it thrived.  Additionally, with the fall off in the economy, people had to find a way to deliver the same services their customers were used to but do it for less.  Voila!  Off-shore resources!!

In the last several years though, even off-shore resources are expensive.  Seasoned IT professionals (baby boomers) are retiring and taking valuable company info along with them.  Profit margins for most companies continue to erode as spending has slowed.  DASD has gotten significantly less expensive and bandwidth has quadrupled (or more?)!  Those “free” websites now charge fees, but they aren’t outrageous.  Given these changes, it makes sense that more and more applications are moving into the Cloud.

As you know, here at LUCRUM, “we do BI”.  Respoinding to our customers, we implemented Agile BI concepts long before it was fashionable.  We are able to get BI projects up and running in significantly less time than our “big 6″ competitors (and do it for less!).  As we continue to investigate ways to get data to our customers faster, we have become fascinated with the Cloud.  Certainly there has to be a way to take all of these company assets, secure them in the Cloud and give users better/faster access to their data.

We’ve investigated a few companies that are doing this today:  Good Data, OCO, BIRST, and PivotLink.  What’s interesting about each of these companies is that they’ve taken the common business problems –   Sales and Finance – and created models to support them.  I was fortunate to participate in a meeting with Good Data last week.  I’m excited to learn more about each of these companies and even more excited to see how LUCRUM can support BI in the Cloud!

Stay tuned!

 - Jodie

Trusting Your Gut

In a recent McKinsey Article, “Strategic decisions: When can you trust your gut?”, Nobel laureate Daniel Kahneman and psychologist Gary Klein debate the power and perils of intuition for senior executives.  Being in the business of business intelligence, I was at first shocked at the premise that there would be a time to trust your gut.  After all, I’ve been telling execs for years that data, not intuition, should be the premise for making key business decisions.  *Breathe* They agree.  

What I found most interesting was that while they gave credibility to the strength of one’s intuition, they cautioned not to be seduced by overconfidence.  They noted that most executives are promoted because of the confidence that they project which makes them more likely to be leaders in the first place.  This confidence can cause others to trust the intuition of an exec because the exec believes they they themself are right.  Hmmm…interesting point.

I think in my next BI engagement I’ll be adding a new dimension to the cube:  Exec Intuition.  We can plot that as a 1 (yes) or a 2 (no) and then analyze how often their intution is correct. 

 – Jodie

Alignment, Iteration and Business Intelligence

For most of the last two decades, LÛCRUM has participated in creating over 100 solutions for some of the most prominent organizations in business and education.  In 1998, LÛCRUM published its first full Business Intelligence Methodology, iStream.   The word “stream” was used to symbolize the continuous aspect of the software development lifecycle versus traditional “waterfall” SDLC’s.  This post is intended to conceptually explain how LÛCRUM’s iStream is a differentiated and unique approach to the development of successful Enterprise Business Intelligence Solutions. After years of focus on the delivery of Data oriented projects, LÛCRUM has continued to refine its methodology, leveraging the continuous learning from each new engagement to benefit the next, and to enrich the iStream process itself.

The first and probably most important non-technical differentiated aspect of iStream is the concept of Alignment.  Many consulting organizations and internal IT organizations have some type of design or planning step often called “Envisioning” as an initial step in their development process.  This is for good reason:  understanding the customer’s end goal or picture of success is critical to the success of the project.  At the same time, this does not procedurally support the fact that many individuals are involved in determining the success of a project, and further, in most cases these individuals are not in detailed agreement in regards to what that success looks like, or how it is defined.  Alignment takes this into account, and is a prescribed process to ensure a common understanding of the success criteria by the key stakeholders involved in any enterprise project, including department heads and/or the Information Technology department.  This includes a focus on ensuring that a miscommunication cannot occur where language is not specific enough, for example in clarifying the accepted definition of the term “Sales” in a company.  To explore this a bit, is “Sales” the number of transactions? The dollar volume closed?  Over what timeframe? By what channel? (sales people, resellers, distributors, telesales, etc.) As simple as this concept may sound – misunderstandings or assumptions in areas as simple as this are generally a key reason for project failure.  In this area, LÛCRUM is unique and differentiated in its development approach.

Another key differentiation of LÛCRUM’s approach, particularly as it relates to Business Intelligence, is in the concept of the iteration of a project.  The iStream methodology allows for iteration in the development of the end result, particularly through the recognition that many pieces may make up the whole.  For example, related to Business Intelligence; we may begin by working with an individual decision maker, say the VP of Marketing.  In working with this person we may offer to them the YourView Instant Analytics solution, allowing them to rapidly see their information in a new way through the combination of several different reports or sources into a single view.  Per the YourView solution, this can take place in a matter of days; however by definition it follows the iStream process – however abbreviated – as it is focused on only a single user.  When that VP is prepared to create a complete solution for the Marketing department, the initial work now functions as a pilot/proof of concept rolling into the Alignment, Discover and Architect components of iStream for the larger YourView 360 (Data Mart) project.  In this fashion, we are “iterating” our development of the data mart through one or more “Instant Analytics” projects.  Both projects follow iStream; however the smaller engagements feed into the larger.  When that organization is prepared to roll out an Enterprise Data Warehouse – the same holds true, the work that had been completed at the Data Mart level for the Marketing department will now be employed in the Alignment, Discover and Architect phases of the Enterprise Data Warehouse project.  In this fashion the work that we accomplish at any level of the Business Intelligence Solution chain is applicable for the next, and all would be accomplished using iStream.

While the items above are not descriptive of the entirety of iStream, nor of the entire list of benefits of the LÛCRUM approach, they are absolutely two of the components of iStream which differentiate it from the plethora of SDLC approaches available in the market, and another aspect of what makes LÛCRUM a unique Business Intelligence Consultancy.

Using OLAP to Improve Organizational Effectiveness – Part 3

This is the third and final post in my series on using OLAP tools to improve the effectiveness of organizations.  In Part 1 I discussed some background concepts and terminology.  In Part 2, I talked about some specific examples of how OLAP can have an impact in this area.  In this post, I’ll talk about a specific application: utilizing OLAP software to provide improved performance feedback to employees.

OLAP and Performance Feedback

Improvements to organizational effectiveness can also be realized by utilizing OLAP tools to provide performance feedback to individual employees.  Improved performance feedback will help employees achieve group and individual performance objectives.  Increased attainment of these individual and group performance objectives will, with proper alignment of these objectives and organizational objectives, improve organizational effectiveness.

There are several advantages to providing performance feedback with an OLAP tool.  If the situation is right, feedback can be provided:

• At an individual level
• On a larger sample of employee activity
• Quickly
• In a meaningful manner.

Common Problems with Performance Feedback

Organizations often make attempts to improve the provision of feedback to employees.  Newsletters with departmental performance numbers, posters in gathering places displaying performance charts, and managerial reports with quantitative measures of performance are all attempts to improve the distribution of feedback to employees throughout the organization.  One problem with such efforts is that they are usually not provided at an individual level.  Feedback on departmental, team, or group performance is certainly helpful but depending on the size of the group, its effect will be limited.  Individual performance feedback has its own problem in that it is often time prohibitive to provide extensive individual performance feedback.  The result is often weekly or monthly group performance feedback with individual feedback coming only during annual or quarterly reviews.

Individual performance reviews often suffer from another problem: small sample sizes for review.  If an insurance company is reviewing the performance of claims adjusters using manually prepared data, it may be impossible to review more than a small sample of the adjuster’s work over what is typically a long review period.  Small samples may, of course, result in a flawed appraisal of an employee’s overall performance.

The elapsed time between events reviewed and performance appraisals is also a problem with traditional feedback provision.  Consider the timing of typical reviews: an employee makes a mistake in handling a situation in January, the incident turns up in a sample taken in May, and a review is finally conducted in June.  If a review had been conducted immediately following the incident, the chance of the employee repeating the mistake will obviously be lower.

Traditional feedback provision often suffers from poor presentation of the message.  An interview conducted by a busy manager attempting to perform a number of appraisals in addition to other work may not be optimally effective.

Performance Feedback Improvements with OLAP

Utilizing an OLAP tool may remedy some of the traditional problems with employee feedback.  Imagine again the situation of an insurance company reviewing the performance of claims adjusters.  As a solution to the problems listed above, an OLAP cube could be developed and made available to adjusters on a daily basis.  Adjusters could be presented with individual performance feedback delivered via the web.  They could see at a glance how their activity the previous day compared to group averages and organizational objectives.  Exceptions could be noted immediately by the individual employee, rather than organizational objectives.  Exceptions could be noted immediately by the individual employee, rather than a manager, and quickly corrected.  Feedback could be provided on all activity from the previous day or week rather than on a small, dated sample.  Finally, feedback could be presented in easy to understand charts which, in addition, roll-up to display departmental and organizational performance as well.

Improved performance feedback gives employees the ability to monitor their own performance and to take corrective action quickly.  By improving the ability of individual employees to meet their performance objectives, the ability of the organization to meet its objectives and fulfill its mission is improved as well.

Conclusion

OLAP technology can improve organizational effectiveness by:

• Improving management’s knowledge of progress on objectives
• Improving employee coordination on efforts to achieve these objectives
• Communicating the link between employee effort and performance
• Communicating the link between employee performance and reward
• Improving employee performance feedback.

Although OLAP tools can provide assistance in these areas, their impact is obviously limited by factors specific to each organization.  An OLAP tool cannot compensate for poor development of objectives, poor performance reward systems, or any of the other organizational factors discussed.  Utilizing an OLAP tool as I’ve described in this series with no attention given to the underlying systems it is trying to address will, at best, have no effect.

In an organization that has clearly defined its objectives and has implemented well-designed reward systems, utilizing an OLAP tool as we’ve discussed can offer a tremendous payoff.  The ability to provide employees with improved performance feedback and to demonstrate the link between individual performance and organizational performance is extremely valuable.  By helping an organization align individual goals with corporate goals, an OLAP tool can help an organization become more effective.

Good enough?

When is good enough, well,  good enough?  I suppose that depends, one old argument says that close only works in horseshoes and hand grenades.  Can it work with decision making?  How about decision support systems?  Is good enough the manually created spreadsheets that over 90% of organizations use for decision support?  I would argue that while it’s not good enough, most business decision makers work that way. 

To get at the data that most executives feel they need to make accurate decisions, many turn to the manual modification of existing reports, or the creation of their own “Pet” spreadsheet they use almost daily, or certainly many times a week. 

 In an update to a report cited last spring on this site, a September, 2009 Dartmouth University study suggests that the error rates in formulas on spreadsheets in their study were only .087% of all formulas they audited.  HOWEVER, these were in cases where the formula produced the WRONG RESULT, and actually resulted in 87% OF THE SPREADSHEETS REVIEWED having errors in which the spreadsheet then produced the wrong result. 

How good is good enough?  What if you could reproduce the “Pet” spreadsheet in a true Business Intelligence solution which would ensure that the data and results in the sheet were as solid as the data in your transactional systems in the first place?  How much does the wrong data or the wrong decision cost you, or your company?  I would argue that “good enough” might just be good enough, if you could ensure that the data was accurate, and mitigated the possibility of error, while increasing the timeliness of the information to the decision maker.  We have deployed such systems in a couple weeks’ time leveraging tools like SharePoint, Excel, and other software products that our customers already owned, and quickly delivered a system to our customer where we dramatically increased the accuracy of their information.  These solutions form the basis of our iterative approach to Business Intelligence.

The Title is Information Officer … Chief Information Officer

Love that title!  Ha ha ha!  What a great way to end John Bostick week here at thefuturevalueofbusiness.com.  I hope you’ve enjoyed the look back.  This last post comes to us from InfoManagement 09.2007.  Enjoy!

********************

Say the name Sean Connery, and virtually everyone who enjoys movies will think of his most famous line: “The name is Bond, James Bond.” Ian Fleming’s spy novels made the Bond character popular before Connery first played him onscreen in 1962. And five other actors have played Bond during the last 45 years. But it is Connery most of us see in our heads when we hear the famous musical riff from every film’s opening sequence. And Connery is the standard against which all other would-be Bonds – perhaps even all other secret-agent characters – are measured. Does the name George Lazenby mean anything to you?

Yet, of the 28 nominations and 12 awards recognizing his acting prowess, none were for his role as James Bond. Not only has he starred in dozens of films other than Bond flicks, he defied the bane of the acting world – typecasting. In fact, he won an Oscar not for playing a super-spy, but for his turn as Jim Malone, the aging, street-weary Irish cop in The Untouchables.

Connery’s secret? Transformation. He captured our collective imagination as the dashing British Bond, but he realized the role was ultimate a dead end. He made the tough decision to abandon the old role in his comfort zone at the height of its popularity in order to improve his long-term career prospects. He then used his box office appeal as leverage with the studios to give him the broader roles he knew were critical to his professional survival.

Today’s senior IT execs, and those who aspire to move up the ladder, can take a few pointers from Connery.

During the late ’90s, IT executives were the stars of many businesses, capturing the imagination of their companies and customers by leading them in new directions for information technology. E-commerce. Web services. Name a tech trend; the CIO and his/her senior staff were in the lead. But as the world moved from seeing technology on its own as a strategic advantage, and began making technology decisions based on the business value they were supposed to bring instead, the CIO and senior IT execs went from stars to bit players in their organizations. They were typecast as the tech geeks with no business sense.

New priorities have replaced the corporate IT “space race” of the last century in the minds of C-level executives: compliance, mergers and acquisitions, corporate governance and outsourcing. No longer impressed with IT’s nuts and bolts, CEOs, CFOs and COOs are more concerned with IT’s cost and its contribution to generating value. With little more to offer than gripes about interoperability and the shortage of IT workers, many CIOs risk losing their seats at the executive table.

Like Connery using Bond as leverage, today’s CIOs and other senior IT executives need to branch out from their traditional roles in order to become true information officers – the type who understand how technology applies to the financial, operational and competitive sides of the enterprise. Based on my experience of talking to CIO’s, IT executives and aspiring IT executives everyday, here are a few suggestions on how to fight the technology typecast.

Business First

Actors call this “sharpening their craft.” Business pundits call it “business/IT alignment.” What it means is understand the basics of your industry and your organization first. Know your company’s customers, suppliers, and competitors. Read broadly and deeply about business, to be perceptive about management, markets, global culture and accelerating change that technology is in large part driving. Know before your executive peers can blink that – the world is flat – the tail is long – the ocean is blue – and – the implications that the truth can be terribly inconvenient. Insert perceptive IT questions into your company’s customer satisfaction surveys and champion the insights. Try to get a seat at Board meetings as a participant, advisor, observer or guest. Develop IT buy-in with your executive peers make sure you have a clear IT governance strategy that the CFO and/or general counsel helped develop. This is the first step toward an IT vision that ties into business objectives, strategies and measurements.

Refocus Your IT Organization Away from Commodity Activities and Toward Business Value

If you want to increase your standing in the enterprise, you have to show more than mere competence at what’s expected. Here’s an example. Ben Stiller gets a lot of work in Hollywood. But he doesn’t command Connery money. That’s because he’s essentially playing one of the three Ben Stiller types in every movie.

CIOs and their organizations should emulate Connery’s ability to evolve with the times and changing needs of the “audience.” Departmental time management is an excellent example of adapting to dynamic conditions. Time and resources will always be finite. What will change is how those hours and resources are deployed. Identify IT activities that have been commoditized. Some may be critical and require world-class performance. But, they will still be commodities that offer no differentiating value to your company. Treat them as such. Outsource those activities to specialized providers, and then stack internal time and resources against objectives dictated by business strategy.

Remember that the definition of an IT commodity will change over time and in response to market conditions. So, stay agile and flexible with staff and budget deployment. But also stay focused on the brainwork instead of the mechanical work, and you will provide greater value.

Want to know what practices work best? Keep in touch with your peers – their careers and their organizations. Outsiders have no political stake in the game and can provide insight and honest feedback.

Measure Results

Much like distribution doesn’t measure a film’s success – the box-office take does -activity in IT doesn’t equal results. Your staff may be busy doing something. But that something may not be moving the business forward.

IT managers focus on activities. CIOs and senior IT executives must focus on leadership, goals and results. Tie your department’s results to business objectives anchored by the business’ front-line results. For example, if the business missed its numbers for the quarter, you should consider IT’s role in that deficit and how IT can help put revenue back on track. Keep measurements simple and keep them aligned with executive priorities and operational plans. Measure IT in a business context rather than an IT-focused one and you will increase your prestige with other executives.

Nurture and Grow Business and IT Strategy Together

Some of the actors who followed Connery followed his successful strategy and parlayed a stint as 007 into more lucrative work. Some did not. You should expect the same experience with your IT staff. As you transform your role in the business, it’s important that your people follow that path as well. Encourage them to pursue the same kind of new education and awareness you are. Do what you can to provide growth opportunities for them. After all, you are a team, and you will only go as far as the team can take you.

For example, you can provide your team members with an “MBA career roadmap” instead of an IT-centric employee development plan. Get their buy-in that their careers have to be aligned with the business and not just tethered to IT. The more they understand how business works, the better prepared they’ll be to make valuable contributions to the organization.

Accept that not all of the team will follow this path. Some will – and should – remain focused on the nuts and bolts of IT. In fact, it’s your job as a leader to help individuals discover when this role fits and what value it delivers.

The rapid pace of change in technology and the dynamic nature of global business put CIOs and senior IT execs of all kinds, from midsized company to major corporation at risk of being typecast as a one-role actor. If you aspire to the executive suite, you need to ask yourself: Am I Connery? Or am I Lazenby?

Bond fans know what I mean.

– JB

Give Yourself Some Wiggle Room to Drive Innovation and Change

Originally shared in InfoManagement Direct on 12.21.2007, John share’s his thoughts on how Managed Services can drive innovation.

********************

Recently I came across a quote by the legendary Chicago Sun-Times journalist Sydney Harris who observed, “Our dilemma is that we hate change and love it at the same time; what we really want is for things to remain the same, but get better.” Nothing like a little paradox to reboot the brain and inspire a new look at the same landscape.

We want things to stay the same – only get better. Ain’t that the truth? There’s a lot of comfort in things remaining the same. We know what to expect, we can predict our reactions, nothing is going to catch us off guard and cause us pain or make us look bad.

We gain a sense of security in things remaining the same, especially over a long period of time. It’s like a baseball hitter who spends hours hitting off a pitching machine. The speed and location of the ball are predictable, so eventually, no matter how fast the pitch comes in, the hitter can whack it. He starts feeling good about himself. Then he gets into a game where the pitcher is changing speeds and location, and suddenly those hard line drives turn into soft pop-ups and groundouts. Without the predictability of the machine, hitting becomes a much tougher job.

Change by definition upsets the status quo. Sometimes that’s good. Sometimes it’s not. If it makes things better, then we love it. But because we only know the outcome after the change occurs, we hate the prospect of it, mostly because we’re afraid of losing what we already have. That’s human nature.

While I was in the process of wrapping my brain around this concept I was given a copy of a recent article by Geoffrey Moore from the Harvard Business Review.¹ The article has proved very helpful in understanding the power of this paradox – stay the same only better.

The always-insightful Moore pointed out that there are three terms or time horizons we work in. Normally we deal in the short-term horizon and the long-term horizon. But according to Moore, there is also the overlooked, often borrowed from and always-misunderstood middle-term horizon, which ironically is the only place where innovative ideas can gain traction.

Eureka! Paradox solved – or at least given clarity.

We are very comfortable in the short term, getting instant gratification for our immediate needs – be it food (hence the proliferation of quick-service restaurants), receiving a thumbs-up for doing a good job, making a quick sale, or achieving our quarterly quota, etc. Hitting a short-term objective is satisfying, although getting there can be difficult. Still, the shorter the term we’re dealing with, the fewer chances there are for the rules, the environment or the assumptions we’re working under to change. As Harris points out, we would prefer it if it were a bit easier.

We are comfortable in long-term thinking about the future, designing new products and services, opening new geographic markets and starting new businesses because we apparently enjoy a degree of accountability that is, shall we say, more fluid at the edges. The future is ripe with possibility, riches and romance; or as they say in baseball – all teams look good in spring training.

The other comfort with the long term is that if changes do sneak up on us, we will have time to react to them. Changes that face a long-term outcome aren’t nearly as traumatic, giving us the opportunity to try different things, regain our equilibrium and return to a state of nonchange before we reach the day of reckoning. Things may have changed in truth, but they don’t feel like they did as much because we have time to assimilate the changes.

“Our dilemma is that we hate change and love it at the same time; what we really want is for things to remain the same, but get better.”

What Moore gets right in his essay and that the Harris quote misses is that innovation is not actually a dilemma. A dilemma is a choice between two painful alternatives. Moore demonstrates that there is a third alternative, a middle horizon or a middle term, that incorporates the best of the other two. He says that in order to implement change, we need to create a space in this middle horizon that is free from the pain and rewards of the short-term horizon and also free from the open-ended “explore all options” thinking of the long-term horizon.
 
What’s needed, then, in order to implement innovation and alignment in the middle horizon, is a little wiggle room. I realize the term “wiggle room” isn’t listed in the glossary of the latest MBA textbooks – but it works for me. Wiggle room means there is flexibility in the business expectations of ROI and market share for new product and service innovations, making the prospect of change a less fearsome one; but it also means there are needed restraints that sharpen the focus. There is less of a tendency to push off concerns about the consequences of your actions on “future you” when the future is not as far off. Flexibility with restraint is the ideal environment to nurture innovation.

One of the ways to create an innovative middle horizon is to build both flexibility and structure into an IT organization through the use of managed services. On the flexibility front, managed services give companies two critical advantages – flexibility of capital resources and flexibility of human resources.

Innovation by its nature requires a large investment in human resources in particular. In most cases, it helps to have many minds brainstorming a variety of concepts from different points of view to nurture innovation. It also takes a fair amount of freedom from the restraints of day-to-day work in order to envision what does not already exist or is not already a part of the corporate culture. Yet it is difficult to achieve that free-thinking mindset when your best resources are bogged down in the day-to-day tasks involved in keeping the current business operating. Offloading the mundane tasks onto a managed services provider frees your experts to think in an innovative way. Reducing current cost and avoiding future costs also enables new products and services to attain more realistic maturity cycles.

Managed services address the structure part of the equation by making the costs of ideas real. In a typical organization, the cost of the day-to-day running of IT tends to be loosely defined, coming out of a central budget that can be applied conveniently. When working with a managed services provider costs are much more tightly controlled, with greater accountability across the board. Knowing this level of detail helps place a practical focus onto innovation, assuring that it is being driven by the needs of the business, not just innovation for its own sake.
In the end, business survival is about bringing innovation to market. Managed services are an often-overlooked yet critical tool in a CIOs portfolio for creating that little bit of wiggle room in the mid-term horizon for new products and services to find their potential. They can help take some of the fear and pain out of change by redefining roles in order to encourage it. While the individuals may not learn to love change unequivocally, they may at least learn to embrace it as a necessary step on the road to success. And that’s definitely movement in the right direction.

Reference:

1. Geoffrey Moore. “To Succeed in the Long Term, Focus on the Middle Term.” Harvard Business Review. July/August 2007.

– JB

The Reality We Can All Agree On

This post was originally shared on InfoManagementon 4.11.08.  Although JB focused on Wiki’s at the time (Twitter wasn’t much of a tool 2 years ago), his wisdom is spot on!

– Jodie

*******************

For centuries, the encyclopedia was viewed as the single most reliable reference source for just about everything. Encyclopedia articles were written, edited, vetted and edited some more, until finally an article appeared that was as close to absolute truth as humans could make it. 

Then came the Internet, and shortly thereafter sites such as Wikipedia. Now, instead of content on a given topic being determined by the elite few, anyone can contribute their thoughts, ideas and points of view. How egalitarian. The other side to it is all of this collaboration has created what comedian Stephen Colbert refers to as “the reality we can all agree on.”

That may be bad for pure academic research. Not to mention students trying to write their term papers with as little effort as possible. But it could be the way of the world for IT executives in the future. Forty-four percent of those surveyed by CIO Insight in November 2007 agreed that technologies that “gather and present the wisdom of crowds” will be among the most important technological developments in 2012 to 2017.¹ So perhaps the “wiki way” will not be so bad for the business world.

For years, when organizations would outsource applications or services, they pretty much had to take whatever the supplier offered. And just as with the politics Colbert skewers on a regular basis, sometimes the choice wasn’t that you wanted option A so much as you really didn’t like option B, and wouldn’t use it/vote for it in a million years.

The wiki mentality has the chance to change that. Rather than settling for a hard set of capabilities based on the knowledge and abilities of the supplier’s internal development team, taking a wiki-like approach means using a much larger set of brains to create an application or service that is more flexible than in the past. This flexibility gives it the ability to satisfy a much larger set of demands, and to do it without waiting for the next major revision.

Take infrastructure management services, for example. A decade ago outsourcing the management of the data infrastructure at all was considered heretical. It was an organization’s strategic advantage, and thus not to be trusted to outsiders. Today, we’ve come to realize that the data (and our ability to analyze it) is the strategic advantage. The infrastructure is merely the vessel that holds it. It’s just like the difference between gold bars and a vault. One has intrinsic value, and the other is merely there to contain and protect that value.

Because of that, organizations are finding less and less reason to keep (and manage) the infrastructure inside their own walls. Perhaps the one thing holding them back is finding an infrastructure management partner that will do things the way they want them done.

With a wiki-style approach, that will change. The suppliers will become used to taking and incorporating customer input not only to satisfy the needs of a particular customer, but also to benefit their entire customer base. In other words, the ideas/improvements that Company A wants to implement are seen by other customers, and together the customer base helps drive the way the infrastructure is managed. The business model then becomes the reality the customers can all agree on.

This wiki mentality is also being used in areas such as product development. Open source software is doubtless the best-known example. Open source applications are constantly being improved upon by the people who use them; more importantly, as users develop improvements they are morally and contractually obligated to share their innovations with all other users. It doesn’t take long before one person’s great idea becomes the reality all users can agree on.

This idea is now being expanded into other product areas. Communities are springing up to help organizations tap into a much wider range of brain power than they’ve had access to in the past. Here’s how they work:

Suppose Company A has an idea for a product or service, but isn’t quite sure how to make it work. They can go to a community site and look for individuals or other organizations that may have the expertise they need, or they can post a notice of their needs on the community site. Company A and interested members of the community can then brainstorm the concept, divide up the work and ultimately share in the rewards.

One of the advantages of this community-based approach is that it removes many of the old limitations of business, such as geography and budget. Organizations are free to seek out talent wherever it happens to live and can review solutions from several providers – while only paying for the one they ultimately accept. The end result is the sum of the knowledge of all who contribute to it, which is certain to be greater than the knowledge of any single individual or organization.

Therein lays the opportunity. Rather than relying solely on our own knowledge and experience the way the old encyclopedia-makers did, the wiki approach allows organizations to leverage a much broader range of knowledge and experiences than they could ever afford to develop internally. Sure, some of that “knowledge” might elicit a smirk from Stephen Colbert. But it won’t take long before the cream rises to the top, as it always does. And at that point, the business reality truly will be one we can all agree on.

Reference:

1. CIO Insight. “The Technologies of Tomorrow.” CIOInsight.com, December 12, 2007.

-  JB

Next Page »

Polls

Which of the following BI SaaS Vendors have you heard of?

• www.gooddata.com
• www.birst.com
• www.1010data.com
• www.oco.com
• www.pivotlink.com
• Other
• I've not heard of any of these.

View Results

 Loading ...

Recent Comments

• Steven McWhorter on The VLOOKUP Hookup
• eicg on Data Mining – We want it Now!
• LUCRUM Incorporated on Better BI on Bigger Data
• LUCRUM Incorporated on Data Mining – We want it Now!
• LUCRUM Incorporated on The Science of Visual Analytics

Tags

andy erickson BI Blog blogging Business Business Intelligence Collaboration Communication Consulting Culture Customer Service Dashboard Data database Data Management Data Mart Data Warehouse Data Warehousing David Bowman David Cordas Dayton development Enterprise 2.0 Information Technology IT Jodie Heflin Jody Detzel John Bostick Leadership marketing Microsoft networking Ohio Podcast Project Management Raveen Rajavarma Sales Scott Felten Service SharePoint Social Media Strategy Technology Twitter Web 2.0

What we're talking about...

• RT @marksmithvr Blog: Kalido Does Data Governance Right http://bit.ly/b2mQmR #DataGovernance #Kalido #CIO #MDM #Data #DataQuality 2010-06-22
• Figured out folders. Love that! #iPhone OS4 2010-06-22
• Upgraded to iPhone OS 4. When will I see multitasking? 2010-06-22
• Shocking?!? RT @OneMicrosoftWay Microsoft puts Messenger on the iPhone's App Store - http://arst.ch/lcy 2010-06-22
• Been off of Twitter lately due to lack of access at new client. Boy have I missed a lot! 2010-06-22
• More updates...

Copyright © 2010 LUCRUM, Inc. 7755 Montgomery Rd, Suite 160, Cincinnati, Ohio 45236 TheFutureValueofBusiness.com