Process mapping consists of Apps, Types and Fields.
Apps area reflects your organization and work structure, removing any mismatch between the tool and your work model.
App usually represents some process. Like Product Development, Hiring, Vacation Tracking, etc.
Type represents specific information you want to capture inside an App. For example, in Hiring App you have Candidate Type. App consists of several Types.
Field is a smallest unit of information inside Type. For example, text field, email field, formula field, relation field.
Let’s start from an example of a moderate complexity:
We have several Apps here:
- Sales App with three Types: Customer → Purchase, Activity.
- Execution App with Product → Initiative → Task.
- Strategy App with Goal.
Note that Types are linked via Relations. For example, Initiative has a collection or Tasks and Initiative is linked to Product.
The best thing in Fibery is that you can create (grow) your own process by creating Apps and Types. Nothing is forced. In almost all other tools you have to adapt, you have to live with workarounds, unnatural relations, unfamiliar naming conventions and excessive functionality. In Fibery you have exactly what you need.
This flexibility comes with a cost. As a Fibery administrator you have to understand things in depth to be effective. This is not Trello. Fibery can be as simple as Trello, but this should be your deliberate choice.
How to build your own process? There are two options right now:
- Manually by Adding Apps and Types
- Install Apps