Interviews, artefact review, and a small number of live walk-throughs. The output is a current-state narrative and a first map.
About the practice
A business management practice based in Chișinău.
Svetlana Şevtova provides business management services: helping an operating company see how work actually moves, decide how it should move, and settle that decision into a weekly rhythm.
What the practice is for
Companies come here when the informal way of working that built the business is starting to cost time, quality, or management attention. The symptom is rarely “we need a process diagram.” It is a queue that nobody owns, a customer promise that depends on a single person, or a leadership meeting that re-decides the same exception every week.
The practice stays small on purpose. Svetlana Şevtova leads the work directly. There is no separate sales team and no bench of junior analysts presented as the delivery team. If a specialist is needed for a narrow interview, that is agreed in the written offer before the work starts.
Clients are typically founders, operating directors, and functional leads in growing companies. Engagements are in English. Sessions can be held at Strada Petru Rareș 77, Chișinău, at the client’s location when the scope says so, or remotely.
The Operating Sequence
Methodology is a sequence, not a brand of workshop. Each movement has an output. We do not start the next movement until the previous output is accepted by the people who will use it.
A short list of the decisions, queues, and handoffs that create the friction. Everything else is context, not the project.
The future flow, the forum that manages it, role boundaries, and the exception rule. Reviewed in a working session, then revised once.
The cadence is placed in the real calendar. Early cycles are observed so the design is corrected against practice, not against opinion.
Principles
- One operating question per engagement. A project that tries to redraw the whole company produces a poster. We agree the boundary in writing.
- Managers stay in the work. Management design fails when it is delegated entirely to a project group. The people who run the week attend the design sessions.
- No invented certainty. We will not forecast a percentage improvement. We will tell you what will be clearer, who will decide, and what still depends on your team.
- Tools follow the flow. Software requirements are written only after the flow and the decisions are stable enough to brief a vendor.
- Confidential by default. Client material is used to do the engagement. It is not reused as a public case study unless you ask for that in writing.
Review the services · See how an engagement runs · Write to the practice