Home / Client path
Details
How working together actually proceeds
This page describes the path a client walks with GALINA MANOLII. It is the operating design of the practice itself: what happens first, what is needed from you, how work is done, and how it is closed.
Initial contact
Write through the contact form or email info@digitalmadobs.my. A useful first message names the journey that hurts, the result it is supposed to produce, and whether the work is physical, document-based, or mixed. You do not need a brief already written in consulting language.
If the request is outside process redesign — for example, a request to build software, run payroll, or produce a certification file — that will be said plainly. There is no bait page that later becomes a different service.
Discovery conversation
A short conversation tests fit. Topics include the journey under pressure, who can convene the people who do the work, constraints that cannot move (legal, safety, contractual), and whether remote sessions will be enough.
Nothing in this conversation is a paid diagnosis. It exists so neither side spends a month discovering a mismatch. If there is a fit, a scoped proposal follows. Formats are listed on the offer page.
Preparation
Before mapping starts, both sides agree: the journey boundary, the roles to involve, the evidence to share, the working language, and the review dates. Access to live items matters more than a kickoff presentation.
You remain the owner of internal data. The practice works with what you choose to share and does not require unnecessary personal data. See the Privacy Policy.
Workflow
Work happens in concentrated sessions, not in a fog of status meetings. Diagnosis and redesign use the same spine: evidence, map, challenge, reconstruct, rehearse. You will see drafts while they are still ugly, because a pretty map that arrives too late is a different product.
Sessions are scheduled. Between them, the practice writes; the client gathers the next set of real cases. That split keeps the operating team from living in workshops.
Delivery
Delivery is a working pack, not a theatre of recommendations. Depending on the service, that pack includes maps, ownership tables, interface contracts, exception rules, and a rhythm card. A walkthrough is part of delivery so the pack can be used without the author in the room.
If implementation companion work is included, delivery continues through the first agreed review cycles, then closes with a note on what is stable and what still needs an owner inside the company.
Communication
There is one named counterpart on the client side and one on the practice side. Questions do not get lost across a large account team, because there is not one. Written notes follow working sessions. Urgent operational incidents remain yours to run; this is a redesign practice, not an outsourced operations desk.
Next steps
After close, the client owns the path. A later review can be booked if volume, regulation, or structure changes the journey again. There is no lock-in retainer unless you ask for a defined companion period in the offer.
Typical continuations: move from diagnosis into redesign; add handoff design where the new path still snags; or add implementation support for the first live cycles. Return to services.
