Process analysis
Find the failure point
Map handoffs, decision rules, exceptions, and ownership so a team can see where work stalls or breaks down.
Business operations and systems analysis
Make the work easier to see, control, and improve.
Jacob Herrmann analyzes complex HR operations, translates friction and failure patterns into practical workflows, and builds reporting that supports decisions instead of merely documenting the mess afterward.
What the work centers on
Operations, not theater.
The point is a defensible operating result: clearer decisions, less rework, stronger records, and tools people can actually use.
Reporting and controls
Turn activity into evidence
Build validated intake, reliable master data, and reporting that makes operational status and follow-up visible.
Practical improvement
Design for the people doing it
Translate a process into usable templates, automation, documentation, and training without pretending the real world is frictionless.
Operating model
The projects share a diagnostic spine.
Different situations, one task: identify the failure point, design a practical intervention, then surface what has to stay true for it to keep working.
Hover a ribbon or stage to trace its path through the operating model.
Ribbon width = reliability conditions, not volume
Trace a path to see the practical dependency behind it.
Selected case studies
Proof of work.
Intake and decision support
Transfer Preference System
Structured a high-volume preference process around self-service intake, automated notifications, eligibility review, latest-submission logic, and a retrievable audit trail.
Microsoft Forms · Power Automate · Excel · SharePoint
Reporting and process improvement
Training Attendance Architecture
Rebuilt manual attendance tracking into a validated Excel/VBA intake, a Power Query master log, and reporting designed for operational use.
Excel · VBA · Power Query · Dashboard Design
Workflow design pattern
HR Intake and Routing Pattern
An anonymized systems pattern for routing requests, approvals, handoffs, notifications, and audit-ready records across operational teams.
Microsoft 365 · Teams · SharePoint · Process Mapping
Working approach
From operating question to usable answer.
01
Investigate
Clarify the process, people, systems, exception paths, and the decision that actually needs support.
02
Design
Build the smallest durable workflow, reporting layer, or control that resolves the operational problem.
03
Enable
Document it, make it legible to stakeholders, and leave a trail someone else can maintain and audit.
Portfolio note
Real operating patterns, responsibly presented.
Public case studies use anonymized or synthetic data where appropriate. Claims are limited to documented workflows, practical systems patterns, and demonstrable project materials.
Review the case studies