Building from Zero: Designing Workflows That Stakeholders Actually Adopt | Bhakti Save

Creative project manager Bhakti Save addresses a specific problem: how to build a process when nothing exists yet, no structure, no ownership, and no established way of working to follow. She lays out a repeatable four-step framework for designing a workflow from zero and getting people who do not report to you to actually use it.

Step 1: Find where the work is actually breaking

The starting point is diagnosis, not design. Before building anything, identify where ad-hoc work is actually breaking down: bottlenecks, missed handoffs, and stages with no clear owner. Save notes that both times she has done this, the starting point looked the same, work happening ad hoc with no structure and no clear ownership for any of it.

Step 2: Design the approval sequence

Once the break points are identified, the next step is designing the actual workflow: who approves what, in what order, and why. This is the part that turns a diagnosis into something people can actually follow, a defined sequence rather than an informal habit.

Step 3: Drive adoption

Save calls this the step most people underestimate. A process nobody follows is not a process. Anyone can follow an existing standard operating procedure, but building one that cross-functional stakeholders, people who do not report to you, will actually adopt is a different skill entirely. That distinction, she says, is the line between operations support, running a process that already exists, and operations design, building the process that did not exist before.

Step 4: Iterate on real usage

The framework does not end once the process ships. Real usage always exposes what the design missed, and the fix is to adjust based on that real usage rather than starting over from scratch. Save has done this build twice, in two different environments with two different sets of stakeholders, which is part of why she frames it as a repeatable skill rather than a one-off project.

The practical challenge

Save closes with a prompt aimed at applying the framework directly: look at a process in your own work that feels ad hoc or unowned, map where it is actually breaking, and sketch a four-step build, find the break, design the workflow, drive adoption, iterate. The suggestion is to run this on something in your own work that has never had real structure.

Key takeaways

• Building a process from zero starts with finding where ad-hoc work is actually breaking, not with designing a solution first.
• A workflow needs a clear approval sequence: who approves what, in what order, and why.
• Getting cross-functional stakeholders who do not report to you to adopt a process is a distinct skill from simply following an existing one.
• A process nobody follows does not count as a process, no matter how well designed it is on paper.
• Real usage will expose gaps in the design; iterate on those gaps instead of restarting the whole build.

Who this is for

This is for operations, project management, and creative production professionals who need to establish structure and ownership in a team or workflow where none currently exists.