Workflow architecture

From a manual process to a working system.

I first map the flow of data, roles, and decisions. Then I connect the interface, logic, and documents into one controlled workflow.

Short demo

One process. Two states.

Switch modes to see the manual workflow first and the proposed automation next. Local browser rules produce the comparison.

01
InputReceive documents
Data is passed between roles manually and can be lost or become inconsistent.
Manager
02
WorkVerify data
The same data has to be entered at several stages.
Specialist
03
DocumentAssemble the set
The final document is assembled manually from several sources.
Specialist
04
ApprovalApprove
The process stops until the responsible person confirms the action manually.
Supervisor
05
RegistryUpdate the journal
The result is copied into a journal or registry again.
Manager

Product in operation

Testing laboratory automation

Requirements, UX/UI, architecture, frontend, backend, database, documents, testing, and launch — one completed cycle.

Experience and responsibility

I started in frontend development and moved into applied-system design and engineering leadership.

2021 — present

10 people in the department

Planning, work distribution, technical decisions, quality control, and responsibility for the team's result.

Engineering role

I connect process research, UX/UI, frontend, backend, data, documents, testing, and launch.

Approach

I map roles, exceptions, and data movement before choosing technology or visual design.

Small applied tools

Two compact solutions for processing files and producing verifiable results.

01XLSX → report

Processes an incoming XLSX, calculates working time and SLA, groups requests, and produces a report with four connected sheets.

02PDF → XLSX

Batch-processes PDFs, counts printable characters and author sheets, keeps history, and exports a verifiable table.

Contact

Tell me about the process, product, or role. I reply on Telegram and by email.