Inter-Organizational Workflow

We can plan the meta workflows here and the link to the sub workflows internally

Project Management

Useful project management namespaces.

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

Communication Management

From Synchronous to Asynchronous Communication

By specifying different communication scenarios, collaborators can have better expectation of one another's reply time.

• Face-to-face meeting: participants communicate in realtime by either audio or video.
• 1st level: participants are focusing on the message; the turn taking period is 5 to 60 seconds.
• 2nd level: participants work on other things and talk at the same time; the turn taking period is 1-10 minutes.
• 3rd level: the turn taking period is 10mins to 1hr
• 4th level: the turn taking period is several hours to days.

Structuring Talks

To best utilize communication, each piece of information could be further transformed into content, actions, or any types of data and managed in PKC. This process could be iteratively improved by some rules of a team. The core of the rules is the abstraction of data. For each piece of information, if its type is well-defined, users can categorize it and trigger following actions [either manually or automatically/place at the back]. If the type isn't defined or only weakly defined, users can choose w to define its type or optimize them. (Universal data abstraction, evolving abstraction).

For example:

• For an undefined pattern, define a new page.
• For a set of messages, create a summary and locate in Channel namespace.
• For some actions, create an action item and locate in Project namespace.

Improvement

Design space

• tools expressible
  • in the space

not expressible should have annotation