I’ve been on both sides of the consulting relationship—implementing consultant recommendations as an employee and giving advice as a consultant. This dual perspective has taught me that a lot of consultant advice isn’t worth following.

Good consultants provide genuine insight based on expertise and outside perspective. But the consulting industry also generates a steady stream of generic, CYA, or outright counterproductive recommendations. Learning to distinguish between the two protects your organization from wasting resources on implementation theater.

”Implement an Agile Transformation”

Agile done well can improve software delivery. Agile done badly creates ceremony without substance. When consultants propose organization-wide agile transformations with certified scrum masters, standup meetings, and sprint planning for every team, be very skeptical.

The teams who would benefit from agile practices can adopt them incrementally. The teams who won’t benefit shouldn’t be forced into agile processes because consultants sold a transformation program.

Real advice: Let teams experiment with agile practices that make sense for their work. Don’t mandate methodology across the organization based on what worked at a different company with different challenges.

”Reorganize Around Customer Journey Stages”

This one appears in every third consulting deck. The proposal is to restructure teams around awareness, consideration, purchase, and retention stages rather than functional expertise or product lines.

In theory, this aligns everyone to customer needs. In practice, it creates coordination chaos. The same people end up working across multiple stages anyway because skills and responsibilities don’t map cleanly to journey stages.

The customer doesn’t experience your organization chart. Whether you’re organized by function, product, or journey stage matters less than whether teams can actually collaborate when needed.

Real advice: Fix collaboration and communication problems directly rather than assuming reorganization will solve them.

”Conduct a Full Process Audit”

Process audit recommendations appear when consultants need to justify their fees but haven’t identified specific problems. The deliverable is a 200-page document mapping every workflow with recommendations to optimize each one.

Most of those recommendations are obvious to the people doing the work. “Reduce approval steps” and “automate manual data entry” aren’t insights worth paying consultants to discover.

Comprehensive process audits generate documentation that sits on a shelf. The effort required to implement hundreds of small improvements across dozens of processes exceeds available organizational energy.

Real advice: Identify the 2-3 processes causing the most pain or consuming the most resources. Fix those. Ignore the rest until they become problems worth solving.

”Create a Digital Innovation Lab”

This recommendation peaked around 2018 but still appears. The pitch is to create a separate team insulated from normal business operations to experiment with emerging technology and develop innovative products.

The reality is usually a handful of people building demos and prototypes that never integrate with actual business operations. Innovation labs become sandboxes where interesting work happens without accountability for business results.

The lab either gets shut down when executives realize it’s not generating ROI, or it becomes a permanent overhead cost justified by vague claims about “culture change” and “learning.”

Real advice: Innovation happens when people solving real business problems have permission and resources to try new approaches. You don’t need a separate lab for that.

”Implement OKRs to Improve Alignment”

Objectives and Key Results can work, but only when there’s genuine strategic clarity about what the organization is trying to achieve. Consultants sell OKRs as a solution to alignment problems, but OKRs don’t create alignment—they require it.

If leadership isn’t aligned on strategy, implementing OKRs just makes that misalignment explicit and measurable. You’ll get incompatible objectives across teams and key results that conflict with each other.

The OKR implementation becomes a massive coordination effort—workshops, training, quarterly planning sessions—that consumes time without improving strategy.

Real advice: Get strategic clarity first. Then decide if OKRs or some other goal-setting framework makes sense to operationalize that strategy.

”Develop a Comprehensive Change Management Plan”

When consultants identify problems that require changing how people work, they often recommend elaborate change management programs with stakeholder mapping, communication plans, resistance assessment, and training schedules.

The underlying changes might be simple—use a new tool, follow a slightly different process. The change management overhead makes simple changes feel enormous.

Most people can handle change if you explain why it’s happening, what’s different, and what support is available. You don’t need consultants orchestrating a 12-month change management program for every process update.

Real advice: Communicate clearly, provide support, and make changes incrementally when possible. Save comprehensive change management for genuinely transformative changes.

”Benchmark Against Industry Best Practices”

Consultants love best practices because they’re reusable across clients. The recommendation is usually to adopt processes or organizational structures that worked at other companies.

But best practices are often context-dependent. What works at a 10,000-person enterprise doesn’t work at a 100-person startup. What works in fintech doesn’t work in manufacturing.

Blindly implementing best practices without understanding whether the underlying context matches your situation leads to processes that don’t fit your actual needs.

Real advice: Learn from what others have done, but adapt solutions to your specific context rather than copying best practices wholesale.

”Invest in a Data Lake”

This one appears when consultants identify data silos and integration challenges. The proposed solution is building a centralized data lake where all data lives in one place for easy analysis.

Data lakes are good for some organizations. But for many companies, the problem isn’t where data lives—it’s that nobody knows what data exists, what it means, or how to use it effectively.

Building a data lake without solving those fundamental problems just creates a centralized repository of confusing, poorly documented data instead of distributed repositories of confusing, poorly documented data.

Real advice: Start with data governance and documentation. Make existing data usable before consolidating it.

When to Actually Listen

Not all consultant advice is bad. The recommendations worth implementing usually share certain characteristics:

They’re specific to your organization’s context rather than generic best practices. The consultant has invested time understanding your situation rather than applying a template.

They identify root causes rather than symptoms. Good consultants explain why problems exist and address underlying issues, not just visible symptoms.

They come with realistic implementation plans that account for organizational capacity. Bad consultant recommendations assume unlimited time and resources for implementation.

They acknowledge tradeoffs rather than presenting solutions as pure upside. Every decision involves tradeoffs, and consultants who pretend otherwise aren’t being honest.

The Real Value of Consultants

The best consultants bring one of three things: specialized expertise you don’t have in-house, outside perspective that challenges assumptions, or additional capacity during constrained periods.

When you hire consultants for those reasons and judge their recommendations accordingly, you’ll get value. When you hire consultants to tell you what to do because leadership can’t make decisions internally, you’ll get expensive advice that probably shouldn’t be followed.

Trust your own judgment about what makes sense for your organization. Consultants don’t live with the consequences of their recommendations—you do. If consultant advice doesn’t make sense in your specific context, it’s probably safe to ignore regardless of how confidently it’s presented.