Flow is context. Flow is relationships. Flow is knowledge.
Howz that again?
Context (Oxford American Dictionary):
"The circumstances that form the setting for en event, statement or idea and in terms in which it can be fully understood and addressed."
"The way in which two or more concepts, objects or ideas are connected, or the state of being connected."
Knowledge (freely gleaned and distilled from Plato):
"How objects or subjects relate to other objects or subjects."
Ad hoc events and you're completely dependent on search and ad hoc communication: "What's meant by this?", "Is this expense relevant?" or "Who could take this ball and run with it?"
Searching the web, contacting the people responsible for the trip or searching the firm's employee roster or supplier list.
That's how things are done today. Thus focus is on bettering the crutches that support the less-than-perfect ways: Office applications, communication tools, search engines...
Now, how about fixing the root, not pruning the leaves?
An event in a flow: You know why it's there, you know what has happened so far, you know where it's going, you would get all pertinent information (if not you'll have that fixed for next round!).
You'll have the context, the relationships and the knowledge inherently delivered with the event. But only if it's a part of a flow.
So, use the flow and make a quantum leap :)