Business process strategy · Chișinău
Andrian Pronin advises leadership teams on how work is owned, handed across functions, and reviewed. The practice is for organisations whose coordination used to be informal and now needs a clearer operating line.
Plain terms
ANDRIAN PRONIN provides business process strategy at Mihai Eminescu Street 74
MD-2012, Chișinău
Republic of Moldova. Email [email protected]. The practice is independent. It is not a Google partner, not a government office, and not a software vendor.
The work is advice on how a workflow is owned, handed on, decided, and reviewed. The services are operating model clarity, process diagnosis, workflow redesign, decision and handoff design, and operating cadence. Formats are a Diagnostic Brief, a Redesign Program, and Cadence Advisory. Nothing on this site is a promise of a savings figure or a headcount change.
The enquiry form is free. This website does not take payment, start a subscription, or add a call-out charge. A fee appears only in a written proposal after a scoping conversation. That proposal states the amount, what is included, and what is not. You pay only if you accept it in writing. Declining it costs nothing.
Your name, email, organisation, and a short note about the workflow, so a reply can be specific. The form does not ask for a password or a payment card number. How that information is used is in the Privacy Policy.
Where the thread breaks
The practice starts from the places leadership teams already recognise, then turns them into a bounded piece of process work.
Everyone is helpful until a delay appears. Then it is unclear who was meant to carry the work.
The next step depends on who is in the room, which inbox is watched, or which version of the file is current.
Approval stalls because the input, the authority, or the exception path was never named.
A workshop produces a new map. A month later the old habit is back, because nothing reviews the line.
What the practice does
Each service has a boundary. The point is a finished piece of operating clarity, not a permanent presence in the business. Full scope, process, and deliverables are on the services page.
A shared picture of how functions divide work and where they depend on each other.
For teams that have outgrown informal coordination.
A current-state reading of one priority workflow: where it waits, repeats, or changes hands without a rule.
One flow, walked with the people who run it.
A future-state line the team can pilot, including the exception paths that usually get left off the map.
Follows a diagnosis, or precedes a system change.
Named decision rights and a standard for what “ready to pass on” actually means.
Useful when work waits on approval or ownership.
A small set of measures and a review rhythm so the new line does not depend on memory.
The follow-through after a redesign.
Approach
Start from a real case, not a template. A recent job, order, client, or internal request shows the process more honestly than a blank workshop board.
Name the owner before changing the tool. Software can record a process. It cannot decide who is accountable for the next step.
Leave a line the team can run. The engagement ends with maps, rules, and a review rhythm the organisation can use without the advisor in the room. Read the practice principles or the client journey.
Choose the flow and the edges of the work.
Follow a real case with the people who touch it.
Record the breaks in ownership, handoff, and decision.
Draw the future line, including exceptions.
Set how the line will be reviewed.
Before you write
With a short conversation about one workflow that is causing delay, rework, or unclear ownership. If the fit is right, a written proposal follows. The full path is on the journey page.
No. Andrian Pronin does not sell or implement a BPM suite. The work is the design of ownership, handoffs, decisions, and review. A later system project can use that design.
Founders, operations leads, and function heads in growing organisations. The usual moment is when coordination that used to happen in conversation now needs an explicit line. More questions are in the FAQ.
In a written proposal after scoping. The proposal names the workflow, the people involved, the timeline, and what is outside the work. Formats are described on the offer page. There is no published rate card, because scope changes the effort.
Correspondence
A useful first note names the workflow, who feels the friction, and whether you need a diagnosis, a redesign, or help deciding.
Mihai Eminescu Street 74Enquiries are read by the practice. A reply is usually sent within two business days. That timing is a working courtesy, not a contractual promise.