Home Services

Services

Services that make the flow of work explicit

Andrian Pronin offers five business process strategy services. They can stand alone or follow one another. A diagnosis often comes before a redesign. Cadence often comes after. The commercial shapes of that work are on the offer page.

Plain terms

Who is offering this, and what it costs

The business

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 service

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 payment model

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.

What the form asks for

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.

Service 01

Operating model clarity

Purpose: give a growing organisation a shared picture of how functions divide work and where they depend on each other.

Description

Teams often inherit a structure that no longer matches the work. This service clarifies the operating model for a defined part of the business: the functions that matter, the interfaces between them, and the decisions each one is expected to make. It is not a reorganisation programme and it does not redraw every job.

Scope and process

  • Bound the part of the organisation in view, usually from commercial commitment through delivery.
  • Hold conversations with the leaders who share those interfaces.
  • Test the stated model against one or two real cases.
  • Draw the interface map and agree the open questions.

Deliverables and fit

  • Operating model note
  • Interface map
  • Decision inventory
  • Notes for the first 90 days of use

Fits leadership teams that have added people or functions and can feel coordination getting heavier.

Service 02

Process diagnosis

Purpose: see where one priority workflow actually stalls, repeats, or changes hands without a rule.

Description

Diagnosis looks at a single flow, such as client onboarding, order to delivery, internal requests, or complaint handling. The output is a current-state map and a ranked friction register. It explains the present line. It does not yet install a new one.

Scope and process

  • Select the workflow and the cases that will be walked.
  • Speak with people who do the work, not only the managers of the work.
  • Mark waits, rework, missing inputs, and informal fixes.
  • Rank issues by the effect on time, quality, or ownership.

Deliverables and fit

  • Current-state map
  • Friction register
  • A short priority note

Fits teams who feel busy but cannot point to where the time goes. It is also the first movement of a Diagnostic Brief.

Service 03

Workflow redesign

Purpose: design a future-state process that a team can pilot, including the paths that are not the happy path.

Description

Redesign turns a diagnosis, or a known failing flow, into a line people can run. It covers stages, roles, handoff rules, and exceptions. It is intentionally narrower than a company-wide transformation. If a system change is coming, the redesign gives that project a process to configure rather than a pile of wishes.

Scope and process

  • Agree design principles from the diagnosis.
  • Draft the future-state map with the people who will use it.
  • Write the exception routes and the pilot boundary.
  • Prepare a checklist for the first live cases.

Deliverables and fit

  • Future-state map
  • Role notes for the stages in scope
  • Handoff rules
  • Pilot checklist

Fits after a diagnosis, or when a known process must be rebuilt before a tool is changed. See how delivery works on the journey page.

Service 04

Decision and handoff design

Purpose: remove ambiguity about who decides and what must be true before work passes to the next role.

Description

Some processes are slow because the steps are known and the authority is not. This service lists the recurring decisions inside a flow, assigns decision rights, and writes the standard for a clean handoff. It is more precise than a general RACI pasted across a whole department.

Scope and process

  • List the decisions that repeatedly delay the chosen flow.
  • Name the decider, the contributors, and the inputs required.
  • Define escalation when an input is missing.
  • Write the handoff standard in the language the team already uses.

Deliverables and fit

  • Decision register
  • Ownership sheet for the roles in scope
  • Handoff standards

Fits organisations where work waits because approval, sign-off, or “who takes this next” is unclear.

Service 05

Operating cadence

Purpose: install a review rhythm so a redesigned process stays visible after the working sessions end.

Description

Cadence is the lightest of the five services and often the one that makes the others last. It chooses a few measures, a meeting or review that already has a chance of surviving, and an escalation path when the measure moves the wrong way. It does not create a new reporting bureaucracy.

Scope and process

  • Select measures the team can actually collect.
  • Define each measure in one paragraph: source, owner, and rhythm.
  • Design a short review agenda.
  • Trial the cadence and adjust anything that is theatre.

Deliverables and fit

  • Cadence calendar
  • Measure definitions
  • Review agenda
  • Escalation path

Fits teams that have already redesigned a flow and do not want it to fade. It is the core of Cadence Advisory.

Not sure which service fits?

Say what is slow, unclear, or repeatedly reworked. The first conversation is for scoping, not for selling every service at once.