When taking down notes on a process (cataloging them, analyzing them, etc) you need some data about the process. Here's a set of data points used in practice to describe a process in the book:
---
- Name of process
- "Vision" - or *objective*
- Process owner
- Customer of process
- Expectation of customer - what is is the [[Business Value]], which is always customer-centric
- Outcome - which feels redundant given the *objective* from above
- **Trigger** - what *activates* the process
- First activity - the dot on [[UML]] [[Activity Diagrams]], essentially
- Last activity - the other dot
- Interfaces inbound - essentially what process(es) *precedes* this one
- Interfaces outbound - essentially what process(es) *succeed* this one
- Required resources - these are the [[IDEF0#Mechanisms]] basically, equipment, people, supporting templates, etc
- Process performance measures - [[Leading Measures]] and [[Lagging Measures]] to measure process health
---
This is just **one** set of data points. There's plenty of other ways you could collect and collate data. Other data points that come to mind:
- Automation level
- Expected frequency
- Expected duration
- Full [[Responsibility Assignment Matrix|RACI]]
- Alternatives
I think a minimum viable set I'd use in a **simple** process description dataset:
> [!tip] Simple Set
> - Name
> - Objective
> - Trigger
> - Owner
> - ...and as desired expand to
> - Customer
> - First activity
> - Last activity
> - Required resources
> - Performance measures
****
# More
## Source
- [[Fundamentals of Business Process Management]]