Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  Documenting Improvements and impediments during as-is mapping
Previous Previous
 
Next Next
New Post 6/21/2017 7:19 AM
User is offline Slojo
1 posts
No Ranking


Documenting Improvements and impediments during as-is mapping 

I have been working on producing As-Is business process documentation and have gathered some valuable insights along the way while discovering the ways that users interact with the system.  These will be valuable inputs to the To-Be process, however  that will be treated as a separate phase of the project, initiated at a later date.

My question is, how do we collect and document the inhibitors and process improvement suggestions during the As-Is phase?  The Business Process document does not feel like the right place, would you manage these as change requests, another document, or a section within the As-Is document?

Any suggestions or ideas would be much appreciated.

Slojo

 
New Post 7/9/2017 10:09 AM
User is offline Adrian M.
764 posts
3rd Level Poster




Hi SRe: Documenting Improvements and impediments during as-is mapping 

Hi Slojo,

They should definitely be separate from the as-is business process documentation.  It sounds like you are in need of a backlog of potential improvements/changes/requests.  Think of a it as a wish list.

My suggestion is that these should be tracked in a list format so that your list can be sorted, prioritized, searched.

Think about some of the metadata (aka columns) you might want to track for each item in the wish list such as:

* Title

* Summary/Description

* Rationale (what problem you are solving or what opportunity you are addressing)

* Source/Sponsor (the name of the one who requested/discovered it)

* Reference to existing process (here you can link/reference to the as-is process you are documenting and which relates to the line item in context)

* Priority

* Relative Complexity

* Disposition/Status

* etc.

Let us know what you end up using and how it worked for you.

Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 7/14/2017 3:40 AM
User is offline Kimbo
454 posts
5th Level Poster


Re: Documenting Improvements and impediments during as-is mapping 

Hi Slojo

 

I've just finished doing exactly that in my current contract. 

 

Just have an appendix in your AsIs document. Put it all in there. I capture most of that stuff under 'pain points'. Feeds into the ToBe nicely. You can get fancy as Adrian suggests if you like but I personally think that's overkill.

 

 

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  Documenting Improvements and impediments during as-is mapping

Community Blog - Latest Posts

Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...
I recently had the pleasure of chatting with Wolfgang Goebl, a visionary in the field of business architecture and enterprise design. His unique approach, which he refers to as "architectural thinking," and his work with the EDGY framework, offer valuable insights into the future of organizational structure and design. This tool covers th...
Our next speaker in our Blueprints for Success series is none other than Roger Burlton, a prominent leader in business architecture. As founder of Process Renewal Group, Roger has spent over three decades helping businesses worldwide translate strategy into execution. “Intention is everything.” – Roger Burlton Known for his ...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC