CASE 04 / PROCESS & SYSTEMS DESIGN — IFIN SISTEMI

A development process from nothing

Client
IFIN Sistemi
Year
2022
Role
Process & Systems Design
Scope
Operating system for how work moves
Outcome
Structured delivery · clear ownership

OP 10

Context

Not every design problem shows up on a screen. IFIN Sistemi had no structured project-development line. Departments communicated waterfall-style, the commercial team kicked off processes that never formally ended, and daily change requests produced no tangible deliverables.

The problem wasn’t on any screen — it was in how work moved between people. So that’s what I designed.

OP 20

Problem

When there’s no shared system, everyone invents their own. Handoffs get lost between departments, ownership is ambiguous, and “done” means something different to each team. The result is constant motion with little that ships.

OP 30

Process

I treated the organisation itself as the product. I mapped how work really flowed across the three departments, found where it stalled, and designed a development process with explicit stages, ownership, and deliverables — one people would actually follow, not an ideal chart nobody uses.

Development process flow across three department swimlanes — commercial, development, and QA and release — moving work left to right from request to release. DEPT 01 / COMMERCIAL DEPT 02 / DEVELOPMENT DEPT 03 / QA & RELEASE REQUEST SCOPE & ESTIMATE SPEC BUILD TEST & VERIFY RELEASE
FIG. 04 — A DEVELOPMENT PROCESS FROM NOTHING

OP 40

Outcome

Three departments and more than twenty people moved onto a shared, structured way of delivering. Clear stages, clear ownership, and change requests that resolve into real deliverables instead of noise.