A very interesting and active discussion has followed the initial comment to the post made by John Owens stating:
One of the major errors taken in business analysis and modeling is that of modeling the “As Is”, then the “To Be” and then trying to plot a trail from the one to the other. This approach is hugely wasteful of time, money and peoples’ goodwill. Most modeling projects run in this way take so long to deliver results that they fail.
My take? I commented that I think there can be value in comparing as-is and to-be models to highlight the benefits of the proposed changes. I also think that an as-is model provides a contextual baseline (gets you on the same page) when dealing with stakeholders across business silos. That said, I am an advocate of not doing work that no one will use and no one is waiting on to complete their work. So when that is the case, by all means, skip the as-is.
Since that initial interaction, Owens, Marchis and several others have weighed in with well-reasoned comments over the value – or lack thereof – of the “as-is”. Scott Sehlhorst (@sehlhorst) and David Wright (@dwwright99) have also provided their “two-cents” just to name a couple gentlemen readers of this blog will probably recognize.
What do you think about documenting the as-is process? Valuable, or waste of time?
Before weighing in, I’d encourage you to go read the comments on the original post.
While we’re on the topic, do check out John Owens’ site, where he has posted on the discussion as well. He has some very interesting insights and material available on business systems analysis and business and data modeling.
Being able to learn from great posts like Adrian’s, and interaction between folks like David, Scott, John and others who know what they’re doing and have been doing it for a long time is one of my favorite things about the BA blogosphere. Read up!