Gap analysis
Data management can be a bit daunting sometimes (there is so much to do, so little time, and nobody really supports it). So using an architectural approach can be counter productive (too many issues, too many fluffy slides) and turn people off in their drive for improvement.In this case it can be more useful to have an approach that has the focus on addressing the major gaps and clear deliverables. This approach can make use of the architecture patterns, which I posted earlier. The patterns can identify very quickly components that are missing. Say you have a transaction environment and no business intelligence solution - than this is quite likely a gap (etc), so something that may be a pain point that needs addressing.
If this is still too complex (the patterns can be complex to understand, because people mix up physical data stores with 'roles'), then the last resort is to use a simple set of interviews to create a heat map of where people experience pain with their IT systems. This pain is usually caused by the usual data management problems (no ownership, no clear rules & enforcement for quality, spaghetti integration, no standards, etc.). So the trick is to link the pain from the interviews to some root causes and then create a simple staircase diagram addressing the key gaps in a logical sequence. If you cannot define these clear deliverables that link to existing projects or programs, then it is very likely you will fail with any architectural attempt.
Labels: architecture
posted by Evert Ruijs @ 12:43 PM
0 Comments:
Post a Comment
<< Home