Diagrams and relationships
Make process steps, system components or an organisation’s structure visible. Distinguish a line’s appearance from its meaning in the work.
Explain a topic in its own terms using flows, organisation structures, classes, data tables and diagram shapes. Connect shapes, label lines and clarify boundaries with frames or containers.
A sequence of steps, a relationship between records and a dependency between tasks carry different meanings. Xohre’s approach is to make the type and basis of a relationship understandable rather than treat every connection as the same kind of arrow.
Fold subordinate detail in a dense diagram, focus on a chosen structure and move connected objects together. The relationship remains attached to the relevant objects as the visual layout changes.
An organisation chart distinguishes a position from the person occupying it. An open position does not require an invented employee; units and reporting relationships can be described in their own structure.
Drawing a transition does not execute it in a source system. A source operation requires its own consideration of the record, permissions, required information and result. This distinction keeps real data under control while a team designs a process.
EXAMPLE ACTIVITY
The team wants to explain where requests wait, who is responsible and under which conditions they can move forward.
Draw the steps from the arrival of a request through review and decision.
Consider work sequence, responsibility and related records according to their different meanings.
Use alternative branches to show where information is missing or corrections are needed.
Review the new flow as a design; handle any real source change through a separate operation.
A process model in which the team can discuss steps, responsibilities and exceptions.
WHAT REMAINS?
Labelled relationships with clear context
An editable visual process model
A clear boundary between design and source operations
YOUR QUESTIONS
No. An explanatory line, a local semantic relationship and a relationship confirmed by a source system are different things.
The current task view shows dependencies; automatic date shifting is not assumed. Advanced planning behaviour is considered separately.
Bring ideas, records and decisions into the same context.
