Enterprise workflow exploration
Enterprise Deliverable Automation: Scaling report production

Monthly and quarterly tracker deliverables involved substantial repetitive work for project teams and designers. They updated data, rebuilt charts, corrected layouts, and reviewed output, mainly in Microsoft PowerPoint and Google Slides. Separately, I used Figma to test whether a structured design system could provide the components, naming, and metadata an automation workflow would need.
Over three weeks, I extended that investigation across all three ecosystems and built working prototypes. I used them to test whether automation could reduce production work while keeping deliverables editable and easy to review. The prototypes showed how much the automation approach depended on structured templates, metadata, and data readiness.
- Role
- Sole Product Designer & Prototype Builder
- Product
- Enterprise reporting workflows
- Scope
- Workflow strategy, system design, and technical prototyping
- Timeline
- Three weeks






Where It Landed
The three prototypes showed that each ecosystem could generate an editable first draft. They also made the dependencies clear: structured templates, reliable content mapping, production-ready data, and human review. This remained an exploratory feasibility study and did not move into production.