Business Solution Offerings 

MIKE2.0 Business Solutions provide recommendations for solving a number of business problems for which information management is critical to success. 

Initial MIKE2.0 Business Solutions include:

• Agile Business Transformation
• E-Discovery
• An Information Development Approach to MiFID
• Being a Leader in Consumer Lending
• An Integrated Approach to Meeting Regulatory Requirements
• Global Identity Management
• Improving Customer Profitability
• Billing Systems Consolidation
• Supply Chain Management
• Building the Customer-Centric Systems Architecture 

Feel free to check them out when you have a moment- we’re always open to suggestions.  

Sincerely,

MIKE2.0 Community  

1. Understand that collaboration is a process, and a subset of broader executive set business outcomes.

2. Control of  information is necessary to mitigate risk.

3. The importance of Records management.

 4. Understand your content sources and types to be able to track and analyze them.

5. Use a solid collaboration platform (the author in this post recommends Microsoft SharePoint) to work from.

6. Educate management and employees on the goals and benefits of collaboration for positive participation.

7. Consider the knowledge worker and do not overload him or her. 

8. Utilize Records management for back end and administrative tasks.

Do you agree or disagree?  Based on your experience, can you recommend any others to add?

Dan Power

Dan is President of Hub Solution Designs, Inc., a consulting firm specializing in Master Data Management and Data Governance.

Prior to founding Hub Solution Designs, he was the general manager for Dun & Bradstreet’s strategic alliance with Oracle Corporation.

Mr. Power has twenty years of experience in management consulting, enterprise applications, strategic alliances, marketing, corporate strategy, project management and entrepreneurship at companies like Deloitte & Touche, Computer Sciences Corporation, eCredit and Parson Consulting.

He has worked with Oracle’s MDM, ERP and CRM platforms for more than twelve years. He is frequently an invited speaker at technology conferences and has written several articles for publications such as DM Review. He regularly advises clients on developing & implementing high impact MDM strategies.

He studied Computer Science at Princeton University, and earned a Bachelor of Science in Entrepreneurial Studies from Babson College in Wellesley, MA.

Connect with Dan.

Get Featured in our Member Profile Listings!

Every week, MIKE2.0 features a new community member, their experience and recent contributions in the IM space.  If you’re interested in joining our other members in the spotlight, feel free to drop us a line.

Sincerely,

MIKE2.0 Community  

Nitin Joshi, senior business analyst at Wipro Technologies, suggests that Net present value is one of the better methods to quantify the benefits of master data management, and that it may also justify the choice of a project in the capital budgeting process. 

In your experience, is it possible to quantify the business value of MDM, and if so, how would you recommend IM professionals to approach this task?

Pieter Stroop

Pieter Stroop is a member of the management team of Experian Nederland and responsible for Experian’s data quality solutions in the Netherlands.

He is also chairman of the data quality commission of the DDMA (Dutch Dialogue for Marketing Association), co-organizer of the DDMA Data Quality Day and one of the first supporters of the DDMA Data Quality Award.

At Experian, Stroop founded the data quality department, which did not exist in the Netherlands until 2003.

Pieter Stroop speaks regularly about data quality subjects at events like the Masterclass Data Quality Management at the Nyenrode Business Universiteit and is a regular host and speaker at data quality events.

Connect with Pieter.

This is big step forward for MIKE2.0. I’m increasingly seeing clients moving forward with initiatives that leverage a semantic approach. Whereas I used to see it primarily with government clients I am now seeing financial services organizations going forward as well.

Tips for Contributing to MIKE2.0

If you are contemplating adding a new Solutions Offering to MIKE2.0, here are some guidelines and tips.

Get Familiar with Existing Content

Become familiar with the existing MIKE2.0 articles. Peruse the 731 articles already on the site.  The easiest way to do so is to go to the Special pages link (found in the upper right box under the Wiki tab), then the All pages link under List of pages. From that page, you will then be able to see a full listing by clicking on the various links at the bottom (e.g., links at bottom). As you peruse these articles:

• Read pages of interest, note possible ones that you may want to refer to or link to as you develop your Offering write-up
• Make special note of which pages you may need to return to in the future with updates or modifications once you begin adding content about your new Offering
• Note gaps in the key concepts necessary to explain your Offering
• Make sure that you will be drafting an Offering in its proper group. (new Core or Foundational Solutions should be rare; Composite Solutions as well; if you want to create one of those, make sure to get in touch with one of the members of the MIKE2:Leadership Team) Then, begin to map out what content needs to be written.
• Also make sure to familiarise yourself with the MIKE2.0 category structure. Again, go to the Special pages link, then the Categories link under List of pages. You will see major clusters of content and patterns in the category names themselves. The number of members for each category is a count of sub-categories (if any) and articles. And you can assign your solution offering pages to these categories to link them with other content on the site.

Begin Preparing Your Content

• Depending on which group of Solution Offering at hand, there is a starting Creation Guide. These are, in essence, structured and organized document templates for what content should be in your Offering. Please first refer to the appropriate guide in order to prepare the keystone document for your Offering. Look carefully at other Solution Offerings in your chosen group to see how they have been written and constructed. Once done, prepare your Offering overview
• You may also need to prepare various images for your Offering. Depending, that might include architectural diagrams, flowcharts, schematics, or the like. You will see the appropriate kinds of figures based on your review of similar Solution Offerings. You may also want to check out the What is MIKE2.0 page, which contains many of the high-level MIKE2.0 diagrams. Another common figure is the Mike2 Solution Groups, which has many variants in that it uses red highlighting to place Solution Offerings in context
• You will likely identify other patterned content from your initial MIKE2.0 review that should be prepared. Examples include articles related to particular steps within The 5 Phases of MIKE2, current or future states of implementation, guiding principles, etc. Also likely is that you will discover missing content specific to your Offering that provides important background or explanatory material. This content, too, should be prepared
• Also, as suggested during the review step, you will likely find that certain terminology or concepts is missing within the current MIKE2.0 content to adequately explain your offering. The convention is to title each of these as “New Concept”, write it with a short explanation and a link to its corresponding Wikipedia article, and then to place it into the Concept Article category
• In all cases, try to be attentive to assign your various articles into the proper MIKE2.0 categories. This helps keep the site organized and more easily navigated.

Monitor, Update and Expand

• Remember, MIKE2.0 is an active collaboration framework. Expect that others will modify and enhance what you have initially written. Make sure to visit your content on a periodic basis
• Updates are also important. As you learn more in your own local practices, bring those lessens back to your MIKE2.0 Offerings to keep them fresh and current. This might mean updating or changing some of your existing contributions, or adding new articles that deepen the material in the chosen area
• Lastly, continually look for making linkages and connections across the entire suite of MIKE2.0 content. Try to refer to other articles and increase the number of appropriate links across articles. It is in this manner that the whole structure and usefulness of MIKE2.0 is increased for all.

Sincerely,

MIKE2.0 Community  

Matthias Leybold

Matthias Leybold has over 8 years experience in the field of information management, primarily dealing with unstructured content.  He is currently a Senior Manager at Deloitte in Switzerland.

His areas of key interest and expertise include enterprise search and the analysis of natural language as well as enterprise communications which deals with the whole value chain from template management for document driven processes, document creation at runtime and, finally, multi-channel publishing of these documents. In addition to leading the Swiss ECM practice at Deloitte Consulting, he most often acts as engagement manager or subject matter expert.

Connect with Matthias.

MIKE2.0 Supporting Assets

MIKE2.0 Supporting Assets are reusable building blocks that provide detail to compliment the overall methodology. Many of the activities within the MIKE2.0 Methodology have sample assets that can be referred to during the implementation process. There are a number of different types of Supporting Assets:

• Tools and Technique Papers are methods that can be used to speed up the implementation process and includes tools such as Information Maturity QuickScan. These assets focus on a specific business or technical problem and are oftentimes incorporated into Solution Offerings.

• Deliverable Templates are framework documents that can be used on any project implementation. Unlike Tools and Technique Papers which are focused on process, Deliverable Templates provide a document structure that defines the output of an activity and its tasks.

• Capability Statements are overview presentations, selling messages, client cases studies and vendor case studies related to the MIKE2.0 Methodology. They encourage users to take a MIKE2.0 approach.

• Software Assets on the open MIKE2.0 site are open-source software artifacts that can be used as part of the overall methodology. Users of the MIKE2.0 Methodology may also wish to house private software assets mapped into the overall organising framework provided by MIKE2.0. Vendors can also map in their product sets into MIKE2.0 through MIKE2.0 Vendor Solutions.

• Engagement Management Assets provide recommended team structures, estimating models and starter project plans for conducting Information Development projects. Engagement Management Assets are often MIKE2.0 Private Supporting Assets but some of these assets are available on the open methodology site.

• Project Examples are example deliverables (both document and software-based) that have been used in Information Development implementations and can help provide guidance for project implementations.

Feel free to check them out when you have a moment- your contributions are much appreciated! 

MIKE2.0 Community