Primary Role: Workflow Manager
Learning Focus: Learn → Apply
Where: Workflow Editor & Mobilize AI
Primary Role: Workflow Manager
Learning Focus: Learn → Apply
Where: Workflow Editor & Mobilize AI
🎯 Why This Matters
The data your workflow captures determines what you can report on, learn from, and act on. Too little data limits insight; too much data frustrates users and reduces quality.
📝 How to Think About Workflow Data
When designing a workflow, focus on purpose-driven data, not “just in case” questions.
Ask yourself:
What decision will this data support?
Who will review or act on this information?
Is this required for compliance, follow-up, or trend analysis?
If a question doesn’t support a clear outcome, it likely doesn’t belong.
🛠️ What to Include
Well-designed workflows typically capture data that:
Confirms what happened (observation, inspection result, event)
Identifies risk, hazards, or gaps
Triggers follow-up actions when needed
Supports consistent reporting across similar workflows
Favor:
Clear, specific questions
Consistent wording across workflows
Only required detail — not exhaustive detail
⚠️ What to Avoid
Avoid adding questions that:
Are “nice to have” but rarely used
Duplicate information captured elsewhere
Require long text when a simple choice will do
Add effort without improving decisions or outcomes
More questions ≠ better data.
✅ What Good Looks Like
A strong workflow:
Is easy for users to complete correctly
Produces data you actually review
Supports reports without manual cleanup
Balances insight with usability
👉 Quick Check Before Publishing
If you can’t explain why a question exists or how the data will be used, revisit or remove it.
🔑 Key Takeaways
Start with decisions and outcomes, not questions
Capture only data that supports action, reporting, or compliance
Simple, consistent questions produce better data
Job Role: Workflow Manager | Permission Level: Admin / ANVL Manager + TECH / ANVL Workflows | Special Rights: Workflow Management (Create)