Building Cross-Functional Alignment During Transformation

Transformation projects rarely struggle because one department got its requirements wrong. More often, every department got its own requirements right, and nobody checked how those requirements fit together.

The problem usually surfaces late. Sales configures flexible order promising that the warehouse can’t fulfill. Procurement designs an approval workflow that delays the receipts finance needs to close the month. Each team signed off on its piece of the design in good faith, and each sign-off was accurate within that team’s walls. The gaps sit in the handoffs between departments, and handoffs are the one place siloed discovery never looks.

Cross-functional alignment isn’t a kickoff-meeting slogan or a soft skill you hope the team picks up along the way. It comes from a few deliberate structural choices: what the organization agrees success looks like, who owns that success, and how design work actually gets done.

Start With Success Criteria Everyone Signs

Most projects have success criteria of some kind. The trouble is that they’re often written as system milestones (“go live by Q3,” “deploy the sales and inventory modules”) or as a collection of departmental wish lists. Neither one creates alignment. A milestone tells you when the project ends, not whether it worked, and a wish list just formalizes the silos you already have.

Strong success criteria describe business outcomes you can measure:

• Reduce order-to-cash cycle time from 45 days to 30.
• Close the books in five business days instead of ten.
• Reach 98% inventory accuracy across all warehouse locations.

What makes criteria like these useful is that no single department can hit them alone. Order-to-cash runs through sales, customer service, fulfillment, billing, and collections. When the goal belongs to the whole process, each department has a reason to care about what happens upstream and downstream of its own work.

Cross-functional criteria also force trade-offs into the open while they’re still cheap to resolve. Sales may want unlimited flexibility to change orders, while the warehouse wants picks locked once they’re released. If that conflict comes up while you’re defining success, it’s a conversation. If it comes up during user acceptance testing, it’s a crisis. Agreed criteria give the team a tiebreaker: whichever option better serves the outcome everyone signed wins.

And “signed” should be literal. Formal sign-off from executive sponsors and business process owners, before discovery begins, turns the criteria from a slide in the kickoff deck into a commitment people can be held to.

Make Business Process Owners Accountable for the Criteria

Success criteria without owners tend to become everyone’s priority and no one’s responsibility. That’s where business process owners (BPOs) come in.

A BPO is the person accountable for a specific business process from end to end, not just for their own department’s share of it. The order-to-cash owner cares about the whole flow from quote to cash receipt, including the parts that run through teams they don’t manage. That end-to-end view is what makes the role different from a department head, and it’s why BPOs are the natural owners of cross-functional criteria. (For a deeper look at the role itself, see our article on the pivotal role of a business process owner in ERP implementation.)

To make the role work in practice:

• Tie each success criterion to a named BPO. Every measurable outcome should have one accountable person, even when several departments contribute to it.
• Define decision rights. BPOs should have the authority to make design decisions within their process, including which requirements are essential and which are preferences.
• Align BPOs with each other, not just with the project team. Processes intersect. Procure-to-pay and record-to-report meet at accounts payable and accruals, and those owners need a regular forum to settle overlaps. When they can’t agree, the conflict should go to the steering committee with a clear recommendation attached, not as an open-ended debate.

One caution: a BPO title without authority or time is worse than no title at all. If the person named can’t make decisions stick, or is expected to do the job on top of a full day job with no backfill, the role will quietly collapse, and the design decisions will default back to the loudest department.

Run Discovery and Design Together, Not in Silos

Many projects run discovery and design one department at a time. It feels efficient, since each session stays focused and the calendar is easier to manage. The hidden cost is that nobody in the room can see the handoffs.

In siloed sessions, the consultant becomes the integrator by default, carrying assumptions from one room to the next and hoping nothing gets lost along the way. Conflicting requirements go unnoticed until build or testing. And each department tends to defend its current process, because nobody downstream is in the room to explain what that process costs them.

A better approach is to organize sessions around end-to-end processes instead of org charts. An order-to-cash session might include sales operations, customer service, warehouse leads, billing, and accounts receivable, walking through the process together and mapping every point where data or responsibility changes hands. Joint sessions also build something that’s hard to get any other way: understanding. When a sales rep hears firsthand that a late order change costs the warehouse two hours of rework, the requirement conversation changes.

Transformation is not easy, but it doesn’t have to be impossible. Take control of your project’s success today and schedule a free 30-minute consultation to find out how Victoria Fide can equip you for transformational success.

Not Everyone Needs to Be in Every Room

Joint sessions don’t mean everyone attends everything, and over-inclusion carries real costs of its own. Sessions with too many people struggle to reach decisions. Subject matter experts get pulled away from day jobs that still need doing. Attendees who sit through an hour of discussion that doesn’t touch their work will disengage, and they’ll be less likely to show up when it does.

The goal is shared understanding of the handoffs, not shared attendance at every meeting. A useful rule of thumb is to bring people in when the conversation affects their inputs, outputs, or decisions:

• Go joint for handoffs, shared data, shared metrics, and any design decision that changes another team’s work.
• Stay focused for detail that lives inside one department, such as general ledger account structure, warehouse bin configuration, or pricing rule setup. Run these as smaller working sessions with the right experts, then play back any decisions that affect other teams to the wider group.

Tiered participation helps keep the balance. A core group of BPOs and key subject matter experts attends the process sessions. Others are consulted for specific topics and join only for those agenda items. Everyone else stays informed through design summaries and playback sessions. Publishing detailed agendas ahead of time lets people see where they’re needed and plan their time around it.

Keep Alignment From Drifting

Alignment built in the first month of a project will erode if nothing holds it in place. Timelines slip, people change roles, and small decisions pile up until the design no longer resembles what everyone agreed to.

A few habits keep it steady:

• Maintain a decision log. Record what was decided, who decided it, why, and which success criterion it supports. When someone asks six months later why the approval workflow works a certain way, the answer shouldn’t depend on who remembers the meeting.
• Review designs against the criteria at each gate. Before sign-off, ask whether the design as documented still delivers the outcomes the BPOs committed to.
• Evaluate change requests against the criteria. “Which success criterion does this move?” is a far better filter than “which department wants it most?”
• Revisit the criteria formally when the business changes. Criteria can and should evolve, but through a deliberate decision, not by being quietly ignored.

Alignment Across Prepare, Execute, and Sustain

Cross-functional alignment isn’t a single activity. It shows up in every phase of Victoria Fide’s Process for Transformational Change™.

Prepare. Define measurable, cross-functional success criteria and get them signed. Appoint BPOs with real authority and protected time. Plan your discovery and design structure around end-to-end processes, with tiered participation decided before the first session is scheduled.

Execute. Run joint process sessions for handoffs and shared decisions, and focused working sessions for department-specific detail. Keep the decision log current, review designs against the criteria at each gate, and route change requests through the same lens.

Sustain. Monitor adoption at the handoffs, where problems tend to appear first. Measure results against the same success criteria signed during Prepare, so the definition of success doesn’t shift after go-live. Maintain alignment by keeping BPOs accountable for their processes long after the project team moves on.

Cross-Functional Alignment Checklist

Success criteria are written as measurable business outcomes, not system milestones

 At least some criteria require more than one department to achieve

 Known trade-offs between departments have been discussed and resolved against the criteria

 Executive sponsors and BPOs have formally signed off on the criteria

 BPOs have defined decision rights and time allocated for the role

 An escalation path to the steering committee exists for cross-process conflicts

 Discovery and design sessions are organized around end-to-end processes

 Department-specific decisions are played back to affected teams

 Design gates and change requests are evaluated against the agreed criteria

Build the Structure Before You Need It

Getting departments aligned takes governance as much as goodwill. Clear criteria, accountable owners, and a thoughtful session structure give your teams a shared definition of success and a practical way to reach it together. If you want help putting that structure in place, explore Victoria Fide’s ERP Project Management & Governance services to see how we help organizations keep complex transformations aligned from kickoff through go-live and beyond.