Understand
Map the case lifecycle, the responsibilities at each stage, and the information needed for follow-up.
Case study · ARIA
From scattered case tracking to a shared workflow.
A small operational team needed a clearer way to manage cases, deadlines, and reporting. ARIA brought that work together using Google Sheets, Apps Script, and the tools the team already had.
ARIA was designed and implemented by DEVOGEL founder Daniel Rodríguez as an internal operational improvement project.
Explore process improvement consulting →01
The operational problem
Case tracking depended on individual memory, messages, and spreadsheets that were not standardized. Each case passed through several stages, with different owners, dates, and follow-up needs. Without a unified view, understanding what needed attention required manual coordination.
The constraint
There was no dedicated development team or IT budget for the project. The solution needed to work within the existing Google Workspace environment and fit the team’s daily work.
02 · THINK → DESIGN → BUILD → IMPROVE
How the work was redesigned
Design
Create a common case record, consistent statuses, deadline indicators, and views tailored to each role.
Build
Connect the shared record to automated reminders, management reports, and dashboards using the existing tools.
Improve
Refine the system through successive versions informed by day-to-day use.
03
What ARIA brought together
Shared case register
Active and closed cases in a common record covering the case lifecycle.
Role-specific views
Different working views for team members, coordination, and management.
Deadline follow-up
Business-day calculations, visual status indicators, and automated email reminders.
Reporting and data quality
PDF management reports, Looker Studio dashboards, duplicate checks, and bulk status updates.
The documented change
ARIA replaced dispersed tracking with a central case register and made case status and workload visible through shared views. Management reporting moved from manual preparation to an automated generation flow. Reminders and alerts became part of the workflow rather than relying solely on individual follow-up.
These are documented functional changes. No independently measured percentage reduction in time, cost, or errors is claimed.
What this shows about the approach
Improvement did not begin by selecting a new platform. It began with the work: its stages, responsibilities, information, and constraints. The resulting system used existing tools to support a more consistent way of working.
The organization and identifying operational details are omitted. This account describes the project’s documented implementation, not an audit of its current performance.
Where does your work get stuck?
Start with a process your team knows well. We can explore what needs to change and which tools can support it.