I'm trying to find some saged advice on creating swim lanes to document where processes cross functional boundaries. How much detail is enough? ...... I am looking to provide enough detail to show the interaction/interrelated processes, but not map the whole world.
How much detail is enough? That's THE big question, to which there just isn't a simple answer. It depends on many things, particularly:
- purpose (what's it to be used for?)
- audience (who'll use it? eg, how much do they know, how much can be assumed, how much can be left out, etc)
I can suggest that:
- try to fit it on 1 page, or at most 2 (few people can concentrate on something that goes longer than that)
- try reviewing drafts with various people to get their feedback
- if there are bits where there's a LOT of detail, perhaps break those down into sub-processes.
How will you know when it's 'enough'? When it's generally acknowledged to be useful for its purpose and most common audience. This should generally be more than just you and an auditor!!
But I'd encourage the approach. I used it recently & successfully with a large organisation where things were consistently 'falling between the cracks' when they crossed functional boundaries. Each of the units involved had their own view of how things were/should be. But putting things together in a swimlane chart helped a lot of discussion and realisations about the end to end process. These included a realisation of the parts that other teams played, and the time required to pass things back and forth (complex process).
PS - sorry, but there isn't any freebie program I know of. I use Visio. I'd hate to try drawing something like this up in any program that wasn't designed for such uses.