Tag Archive for: Advisory

The Hidden Cost of Leadership Indecision During Transformation

in , ,

Why execution readiness depends on how quickly leaders align, decide, and remove blockers

The issue: One of the most expensive risks in any transformation rarely shows clearly on a project plan. That is because transformation efforts do not usually lose momentum in one dramatic moment. More often, progress slows gradually as a decision waits for the next steering committee or a design question gets reopened after the team believed it was settled. Meanwhile, a cross-functional issue lingers because no one is entirely sure who owns the final call. From the outside, the project may still look healthy. Meetings continue, configuration progresses, and status reports show activity across every workstream. Underneath that activity, execution can already be slowing as unresolved decisions create ambiguity for the teams responsible for designing, building, testing, and communicating the future process.

The root cause: Leadership indecision does not always show up as a formal blocker or project risk. It often appears as delayed ownership, inconsistent direction, competing priorities, or a pattern of revisiting decisions. Most organizations understand that poor data, unclear processes, limited training, and low adoption can create implementation risk, but far fewer recognize that slow or inconsistent decision-making can create similar disruption.

In complex transformation programs, leadership alignment is operational. When leaders cannot make timely decisions, maintain direction, or reinforce ownership, project teams absorb the uncertainty. That uncertainty shows up elsewhere in timeline delays, rework, scope confusion, stakeholder frustration, testing issues, or weakened adoption.

There is another dynamic that makes this risk harder to address. In many organizations, teams recognize when decision-making is slowing progress but raising that concern directly can feel uncomfortable or precarious. Calling out leadership indecision is not always seen as constructive feedback. In some cultures, it can be interpreted as criticism, making teams more likely to work around the issue than escalating it.

As a result, the problem often remains implicit: teams adjust timelines, revisit assumptions, or absorb rework rather than explicitly stating that decisions are not being made quickly enough. By the time the impact becomes visible, it is usually framed as a delivery issue rather than a governance issue.

Technology rarely hides those issues; in many cases, it makes them easier to see.

Decisions Shape the Future Operating Model

Every transformation requires hundreds of decisions.

Some are strategic. Which outcomes matter most? What level of standardization is acceptable? Where should regional variation be allowed? Which processes need to be redesigned before they are automated?

Others are more operational. Who owns approval thresholds? What happens when an exception occurs? Which data fields are required? Who resolves conflicts between Procurement, Finance, IT, and the business?

Although these questions often surface during system design, they are not solely system decisions. They define how work will move, who will make decisions, what controls will apply, and how teams will operate once the new process is live.

Decision clarity matters because project teams can document options and explain tradeoffs, but they cannot create executive alignment. Leaders must decide what the future operating model requires and reinforce those decisions so teams can build, test, train, and communicate against a stable baseline.

The bottom line: When leadership decisions are not made or clearly communicated, implementation teams move forward using assumptions that have not been fully confirmed. Those assumptions may hold for a while, especially during design or configuration. Over time, however, they tend to surface as execution risk.

Confidence Breakdown: When Decisions Keep Getting Reopened

Most transformation teams have heard some version of the phrase, “Can we revisit that decision?”

Sometimes that is appropriate: new information emerges, a real risk is identified, or a requirement was misunderstood. Governance should allow teams to pause and adjust when the facts support it. The problem arises when decisions are reopened because alignment was never established in the first place. As a result, teams stop treating decisions as stable and stakeholders hesitate to commit because they expect decisions to change. The project carries multiple versions of the future state at the same time.

Leadership alignment ambiguity increases meeting volume, slows configuration, complicates testing, weakens training messages, and frustrates users who are trying to understand what is changing. By the time the issue becomes visible, it may be labeled as a requirements problem, a communication problem, or a system limitation. In many cases, the underlying issue is a lack of decision discipline.

This is how decision debt builds inside a transformation. Each unresolved or unstable decision moves forward with the project. The team may work around it temporarily, but the uncertainty remains. It becomes embedded in design assumptions, configuration choices, testing scenarios, training content, and stakeholder expectations.

When Decision Debt Gets Built into the Solution

Consider a Procure-to-Pay implementation where the team needs to configure approval routing for purchase requisitions. The project team asks leadership to confirm whether approval thresholds should be standardized across the enterprise or vary by region, business unit, or spend category.

At first, the decision may seem straightforward. Finance wants tighter control. Procurement wants a simpler approval path to improve cycle time. Regional leaders want flexibility to preserve existing practices. IT needs a decision so workflow configuration can continue.

As the discussion continues without resolution, the project team moves forward using the current threshold structure as a temporary baseline. It may not reflect the intended future state, but it allows configuration and testing preparation to continue.

Weeks later, during User Acceptance Testing, users begin raising questions. Some approval paths feel too complex. Some transactions route differently than expected. Certain regions question why their previous exceptions were not preserved. What appears during testing as a system issue is in fact an unresolved governance decision that was carried into the solution.

The system may be routing exactly as configured. The issue is that the organization never aligned on what the approval model should be.

At that stage, the cost of delayed decision-making is higher. What could have been clarified during design now has to be resolved under schedule pressure, with more stakeholders involved and less flexibility available.

Governance Must Do More Than Receive Status Updates

Many organizations establish steering committees for major initiatives, but their presence does not guarantee effective governance. Some steering committees primarily receive status updates. Effective governance forums make clear decisions and resolve issues.

Transformation programs need forums that confirm priorities, resolve escalations, clarify ownership, and limit unnecessary churn. A steering committee should not only hear that a milestone is at risk. It should help address the conditions behind that risk. When governance forums do not play that role, project teams manage decisions they do not have the authority to make. Leaders may see execution challenges while the team is waiting for direction.

Governance and organizational enablement influence execution readiness. Decision velocity, executive alignment, accountability clarity, escalation structure, and competing priorities all affect whether an organization can move from strategy to execution without losing momentum.

Mature Organizations Handle Decisions Differently

Mature organizations define which decisions require executive input, which can be handled within the project team, and where ownership sits when cross-functional issues arise. Escalation paths are established before major blockers emerge and decisions are documented and communicated so teams can move forward with confidence. When a settled decision needs to be revisited, there is a clear reason for doing so.

They also recognize that approval to begin a transformation is not the same as alignment on how it will be executed. A business case may confirm the investment, but leaders still need to align on how the organization will operate differently, which tradeoffs they are willing to make, and how they will support the teams responsible for execution. That alignment must be maintained throughout the project. Without it, teams may stay active but progress becomes harder to convert into results.

The Readiness Question Leaders Should Ask

Before launching a major transformation, leaders often ask whether the technology is the right fit, whether the timeline is realistic, and whether the implementation team has the right expertise.

Another question deserves equal attention:

Are we prepared to make and hold the decisions this transformation will require?

This question shifts the focus to execution conditions: clear decision rights, defined escalation paths, managed competing priorities, and executive sponsors who remain engaged beyond kickoff. It also broadens accountability: transformation success depends on project execution, technology, and implementation support. ISuccess also depends on the organization’s ability to govern the change it is introducing.

Closing Thoughts

Leadership indecision rarely disrupts a transformation all at once. It builds through delayed choices, reopened decisions, unclear ownership, and governance forums that do not resolve issues. By the time those problems appear in testing, training, or adoption, they are harder to address. Organizations that execute well do not avoid difficult decisions. They make decisions, communicate them clearly, and maintain alignment as the work progresses.

Execution readiness includes governance readiness. A successful transformation depends on more than a system that works. It depends on leaders who can align, decide, reinforce ownership, and guide the change through execution.

At Velocity Procurement, we work with organizations preparing for procurement and P2P transformations to assess readiness, identify risks, and strengthen the conditions needed for execution.

Embedded Procurement Teams – How managed services extend client capacity instantly

in , ,

Today, visibility is not a problem for most procurement teams. They already know where to focus and execute. The sourcing pipeline is defined, category opportunities are sitting in a backlog, supplier issues need attention, and stakeholders are asking for support. The real constraint is capacity. There are only so many projects an internal team can move forward at once, especially when it is also handling daily business needs.

That is why embedded procurement teams continue to matter.  They give clients a way to add experienced execution support quickly, without waiting through a long hiring cycle or pushing important work into the next quarter.  In practice, that can mean sourcing support, spend analysis, supplier management, savings tracking, stakeholder coordination, or a mix of all of it, depending on where the pressure is highest.

What makes the model effective is not simply that the resources are external.  It is that they are embedded.  They work inside the client’s priorities, operating rhythm, tools, and governance.  They join the meetings, support the live initiatives, and help move work through the same approval paths and stakeholder dynamics the internal team is already navigating.  That is very different from a traditional advisory model where recommendations are delivered from the outside and left for the client to implement later.

This matters even more right now, as AI and agentic AI become a bigger part of procurement operations.  Those tools will absolutely improve efficiency. They can help with data classification, opportunity identification, workflow management, document drafting, and reporting. Over time, they will make teams faster and more consistent. But they do not remove the need for people who can operate in a live business environment, manage stakeholders, work through resistance, and keep initiatives moving when priorities shift.

That is the key point. AI can make recommendations. It can surface patterns. It can help teams process more information with less manual effort. What it does not do on its own is step into a supplier conversation, manage a tense cross-functional decision, or push a sourcing wave forward when the business is short on time and attention. Embedded procurement teams still have a clear place because execution is still about relationships and relies on coordination, judgment, and follow through.

This model tends to be most useful when the internal team is stretched thin but leadership still expects results. That can happen during a transformation, after turnover, during a hiring freeze, or when a business is trying to accelerate savings or clean up a backlog of sourcing work. In those situations, the issue is often described as a prioritization challenge. In reality, it is a resourcing challenge. The organization may already know what it wants to do. It just does not have enough experienced hands to do it at the pace the business expects.

Embedded support works best when the model is set up clearly. Roles need to be defined. The client and the embedded team need shared priorities, access to the right data and stakeholders, and a simple governance rhythm to keep work aligned. Without that, added capacity can still get stuck. With it, the embedded team can start contributing in a meaningful way much faster than a newly hired internal resource who is still learning the business from scratch.

Embedded procurement teams are not a replacement for building a strong internal function. They are a practical way to extend that function when the workload is larger than the team can absorb on its own. They help clients keep momentum, tackle more of the roadmap, and avoid losing months while waiting for permanent hires. And even as AI becomes more capable, there will still be real value in experienced people who can plug into the work, navigate the business, and help turn plans into results.

Procurement Managed Services: Plug-and-play capacity without building in-house

in , , , ,

January is when procurement teams get a fresh list of priorities and, often, an unchanged or disadvantageous org chart. New savings targets. New stakeholder asks. More urgency. The same number of people (or fewer)

That is why procurement managed services keeps coming back. Certainly not because it is trendy, but because it deals with the part no one can talk their way around: throughput. How much work can your team actually push through the source-to-pay process without quality slipping or stakeholders losing patience?

Here is a realistic scenario. It is mid-February. A business unit flags a wave of contracts expiring in the next 90 days. At the same time, Finance asks procurement to “move faster” on a list of categories tied to the year’s savings goal. Then Legal changes language in a standard template, which means a bunch of agreements already in flight need a quick re-route. Nobody individually caused the pileup, but many organizations end up just like this due to incremental systemic shifts.

When markets are calm, teams sometimes patch the gap with late nights and a few favors. In a volatile year, that becomes the operating model. Stakeholders still buy. They just stop waiting.

Capacity becomes strategy when it is measured

A lot of procurement conversations start with headcount. Should we hire? Should we bring in contractors? Should we restructure?

Those can be valid moves, but outcomes are the better starting point. What needs to get done, how fast, and how consistently?

For the sake of illustration, here are a few metrics usually cut through the noise:

  • Cycle time from intake to award
  • Sourcing events completed per month
  • Contract turnaround time for common agreements
  • Compliance to preferred suppliers and buying channels

If those move, procurement becomes easier to work with, adoption improves, savings is less dependent on heroics, and supplier risk management gets more proactive.

Where managed services often fails is simple. The program tracks activity, not outcomes. You get lots of motion, and the business still complains that nothing is getting done.

What procurement managed services actually is

Procurement managed services is a standing delivery capability that runs inside your environment…with your P2P platform, your intake process, your approval paths, your policy, etc. It is designed to be “always on” rather than a one-time project.

It typically covers work that is steady, repeatable, and high enough volume that it creates real drag when the team is stretched. The scope depends on your operating model, but common areas include:

  • Intake and triage, including intake-to-procure workflows and stakeholder routing
  • Tactical buys
  • Strategic sourcing execution for defined categories and tail spend management
  • Supplier onboarding support and supplier management activities
  • Contract management support, including template coordination and routing

The scope of these activities needs to be clear. If the engagement is vague, it usually turns into staff augmentation under another name.

Where it tends to work best

Most organizations do not need managed services everywhere. They need it where the gap between demand and capacity is persistent, and where inconsistent execution is creating real business friction.

One common trigger is a backlog that never really goes away. Intake builds up, stakeholders get used to waiting, and “quick buys” creep back in. Tail spend grows. Then procurement gets blamed for low compliance, even though the root problem is that the system is too slow to use.

Another is when procurement has a strong savings pipeline but cannot execute fast enough to realize it. The plan assumes a certain number of sourcing events per month. The calendar and reality say otherwise. This is where outcome-led managed procurement services can be a force multiplier, because it converts plans into throughput.

There is also a benefit many underestimate: stakeholder experience. When internal customers do not know what to expect, they work around procurement. When there is a clear intake channel, predictable cycle times, and a team that responds quickly, behavior changes. This is how compliance improves without having to “police” people.

How to buy it without buying disappointment

If you are evaluating procurement managed services, start small and make it measurable. Pick a handful of outcomes that matter, define what “done” means, and build the model around those outputs.

A few decisions matter more than the rest:

  • Define service levels up front, including cycle time targets and volume assumptions
  • Make swim lanes explicit between internal procurement, Legal, Finance, and the managed team
  • Set a weekly prioritization cadence and a monthly value review cadence
  • Require documentation and playbooks as deliverables so process knowledge compounds over time

One small tangent that is worth calling out. Tools do not fix this on their own. A new intake workflow or a shiny source-to-pay upgrade can help, but only if someone runs the process with discipline. Many procurement teams already have solid procurement technology. What they lack is enough capacity to consistently operate it well.

If your 2026 plan assumes faster execution without adding headcount, managed procurement services is a lever worth taking seriously. Capacity becomes strategy when it is tied to outcomes you can measure, govern, and improve.

Tag Archive for: Advisory

Leveraging Sourcing with Organizational Growth

in

Comprehensive strategic sourcing program executed via managed services achieves long-term savings and organizational growth.Global organization that provides clinical services and medical devices for pharmaceutical and healthcare organizations.Elevate the maturity level of the procurement organization by developing bespoke, best-in-class, policies & processes, sourcing templates, and procurement/supplier scorecards. Analyze and categorize all spend. Strategically source all categories of spend to generate impactful savings, increase working capital and negotiate long term supplier agreements. Finally, document all projects for future reference.The organization had a minimal, de-centralized procurement organization, and its involvement was mostly tactical and administrative. Their spend was very fragmented with a high degree of rogue buying, which resulted in limited top-level understanding of what was purchased and why. Aside from ERP financial systems, there were no procurement tools in place, nor was the organization taking advantages of potential global synergies. The lack of a formal contract management tool led to many missed termination dates and automatic renewals with price escalations. Most agreements were on suppliers’ paper and internally the organization had no established levels of signing authority. The organization did not have a clear path forward to grow the procurement organization. They were not seen as a value-add department within the organization. They were seen as another administrative hurdle to place purchase orders and approve invoices for suppliers. This left the organization open to supply chain, financial and legal risks that negatively impacted its ability to be competitive.

Completed close to 80 sourcing projects, with nearly $50MM in total contract savings. On average, we achieved 25% savings across all spend categories. As a result of the strategic sourcing projects we executed, the client now has a better understanding of the requirements for these products and/or services leading to organizational growth.

By consolidating spend and establishing longer term agreements, risk was significantly reduced and the ability to control costs was greatly enhanced. 

Velocity enabled the client to fully understand their spend and helped expand the newly centralized procurement organization. In addition to the savings generated, we provided a 5-year roadmap, which included Source to Pay Technology, Organizational Design & Change Management, Policy and Process Redesign and a Procurement Toolbox for the client’s continued procurement transformation journey.

Velocity Procurement supported us for over 2 years and helped us take our procurement organization to the next level. They effectively acted as our extended procurement department generating an enormous amount of savings, which freed up a lot of capital for our organization to grow.

Procurement Organizational Uplift for Tech Solutions Provider

in

A procurement function uplift results in new supply management value and operational cost savings – just in time to meet the increased demand.Technology solution and services provider with over 100,000 users in their customer community,Due to recent rapid company acquisition growth the desire for a formalized procurement function. With the influx of new spend and new suppliers, a new procurement organization was to be formed that could effectively manage internal purchase requests, suppliers, and spend.Rapid growth naturally comes with some growing pains, the impact was evident in a multi-functional team who was now charged with a formal role in procurement. Though a dedicated staff, there were knowledge and experience gaps which needed addressed to meet the needs of increased demand. Lack of formal procurement policy and sourcing processes, combined with limited visibility into 3rd party spend, developed into an environment of supplier risk and lack of visibility to savings opportunities. In addition, despite change management efforts multiple business units were performing supplier contracting activities differently.

The new procurement structure, methodology and processes developed a strong foundation for the client team to build upon. This included leveraging a newly defined operating model, organizational chart and business-partner RACI model, allowing the team to better equipped to lead company-wide procurement.

Additionally, Velocity built the team a formal category management strategy and conducted multiple pilot sourcing projects over the course of several months. The exercises uplifted the procurement and sourcing skills of the existing team and of new procurement staff.

Within six months, Velocity accelerated the team to reach their savings target goal to reduce addressable spend by 15%, and the client achieved ROI of 17X.

Velocity helped us to build the foundational structure we needed to mature our procurement organization while in a state of hypergrowth.

Sourcing Achieves Savings for Environmental Services Provider

in

Delivering strategic sourcing savings with the adoption of a
new strategic sourcing model and best-practices training.Service Company present in more than 550 communities across North America, leveraging a complex relationship between water, waste and energy to solve environmental challenges and help customers reach their goalsThis project was to launch for ten months several strategic sourcing activities with a scope of roughly 15 Direct and Indirect industrial type categories. The expected deliverables were to deliver at minimum 10% savings, to develop the corresponding strategic sourcing position papers and to train the procurement team on strategic sourcing methodologies.The collection of spend data was especially difficult without any existing P2P tool or adapted processes in place. The fragmented supplier base made it hard to build an external and internal overview cross the different information systems. Last, the lack of strategic supplier or category papers obliged the team to start with basic data collection, aggregation of spend by main categories and suppliers to build step by step an executable action plan.

Our overall approach was to address the spend analysis, to define executable addressable sourcing waves, to deliver savings, and to train the team on strategic sourcing processes. Each of the work-streams were delivered using best practices in strategic sourcing, change management and training.

The various business users and key stakeholders were enthusiastic about the training programs and to learn more about best in class strategic sourcing practices. All of the addressed spend categories had a defined action plan with a new preferred supplier network and the financial results were above target with 16% savings across the addressable spend.

The project delivered a well-balanced approach to both adoption of process change and achievement of new cost savings.