Great questions on metrics and analysis approach. Let me address both comprehensively.
Cycle Time Metrics Implementation:
We track three levels of metrics using Mendix’s process analytics capabilities. First, stage-level duration - time spent in each approval tier (paralegal review, counsel approval, director sign-off). Second, end-to-end cycle time from contract submission to final approval. Third, wait time versus active time, which reveals where contracts sit idle versus being actively reviewed.
The workflow module automatically captures timestamps at each stage transition, and we built custom reports in Mendix that aggregate these into meaningful dashboards. Legal leadership reviews weekly metrics showing average cycle time by contract type, approval stage bottlenecks, and SLA compliance rates. We set SLA thresholds based on contract urgency - standard contracts have 3-day SLAs, urgent ones get 1-day targets.
Bottleneck Analysis:
We absolutely did upfront analysis before building. Spent two months manually tracking 150+ contracts through their approval journey, logging timestamps and handoff points in spreadsheets. This revealed that 40% of delays occurred during the initial routing phase - contracts sat in a shared inbox while someone figured out who should review them. Another 35% of delays happened when approvers were on vacation or traveling with no clear backup process.
These findings directly shaped our automated routing solution and the escalation logic. The data made the ROI case crystal clear - even a basic automation would eliminate those routing delays entirely. We presented findings to stakeholders showing that manual routing consumed 8 hours per week of paralegal time that could be redirected to substantive legal work.
Microflow-Based Notifications - Technical Details:
Our notification microflows follow a template pattern. Each approval stage has a corresponding notification microflow that pulls contract attributes, approval history, and urgency flags. The microflow builds a notification object with personalized content - including contract title, value, requesting party, and why this specific approver was selected. We use Mendix’s email template module to format professional notifications with embedded action buttons.
For in-app notifications, we leverage the Mendix notification widget connected to a custom Notification entity. The microflow creates notification records that appear in users’ dashboards with filtering by priority and age. Users can mark notifications as read or snooze them, and the system tracks interaction patterns to optimize notification timing.
Key Implementation Lessons:
Start with automated contract routing first - it delivers immediate value and builds user confidence. Add microflow-based notifications second, focusing on clarity and actionability over frequency. Implement cycle time metrics last once you have clean workflow data flowing. We rolled out in phases over 6 weeks, gathering user feedback at each stage and adjusting before moving forward. The phased approach prevented overwhelming users and let us refine the routing rules based on real usage patterns.
The 60% cycle time reduction came primarily from eliminating routing delays and providing visibility that kept approvals moving. Users now see exactly where each contract sits and who’s responsible, which creates natural accountability. Management loves the metrics dashboard that shows team performance and helps with resource planning during busy periods.