Super Mario Flowchart
Link: http://bit.ly/SuperMarioFlowchart

seen from Australia
seen from Netherlands

seen from United States

seen from Malaysia
seen from United States
seen from United States
seen from Taiwan
seen from China
seen from Canada

seen from United States
seen from United States
seen from Türkiye
seen from China

seen from China

seen from United States

seen from India

seen from Greece
seen from United States
seen from Russia
seen from Argentina
Super Mario Flowchart
Link: http://bit.ly/SuperMarioFlowchart
As many of you know I am on a Mobile-Only adventure. Yet, one of the biggest reasons I still have to access a PC via RDP is because I need to use Microsoft Visio. Well, that may be coming to an end. This past week I stumbled across DroidDia. DroidDia is a diagramming app for Android that allow users to create flowcharts, org charts, venn diagrams, network diagrams, etc – many of the same functions that are available in Microsoft Visio. This is fantastic news for mobile productivity.
Planning a Software Project, Part 4 - Flowcharting
Part 1, Part 2, Part 3
Now that you know the landscape of the clients technology, workflow processes, existing systems, vendors, and the desired state, it's time to flowchart.
At this point I usually try to enhance the user scenarios by mapping out the steps the user must undertake to interact with the system and acheive the desired effect. I've seen a million good examples of how to do this, so I'll not go in to too much detail, but if you want to see a local example, try MaRS.
Basically, in plain language describe the steps that users (both external and internal) of the system go through while using it. Map the flow. There's no need to get as formal as UML at this point.
You're simply trying to document the flow of users and data through the system. This includes integration points and any workflow/approvals.
An example of a process flowchart (I didn't say it had to be pretty!!).