Difference between revisions of "Inter-Organizational Workflow"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
##Time management | |||
We can abstract and list the purpose for async and sync communication. For sync meeting, I found it efficient to demonstrate something which one already have, like a wiki function, technical issue. The listener can output all of their thoughts and start discussion base on the rich context<ref></ref> | We can abstract and list the purpose for async and sync communication. For sync meeting, I found it efficient to demonstrate something which one already have, like a wiki function, technical issue. The listener can output all of their thoughts and start discussion base on the rich context<ref></ref> | ||
Revision as of 11:13, 7 July 2021
We can plan the meta workflows here and the link to the sub workflows internally
- Time management
We can abstract and list the purpose for async and sync communication. For sync meeting, I found it efficient to demonstrate something which one already have, like a wiki function, technical issue. The listener can output all of their thoughts and start discussion base on the rich contextCite error: Invalid <ref> tag; refs with no name must have content