8 Signs It’s Time to Rethink Your Management Strategy

Your business goals may have changed since you approved this year’s projects. Customer demand may be growing in a new market, support teams may be stretched, or a competitor may be winning deals you used to close. If your teams are still working from the same list of priorities, it’s time to ask whether your management strategy reflects what the business needs now.

Start with the signals you already have. Are you attracting and retaining the people you need? Where are sales slowing down? Are customers buying again, getting the support they need, or leaving? Are teams bringing forward ideas and raising problems early? If sales are growing while your active customer base is shrinking, look at retention alongside new sales to understand what’s changing.

Strategic Portfolio Management helps you turn those signals into decisions about which projects to fund, where to assign people, and what to pause. Here are eight signs it’s time to revisit those decisions.

1. Your company’s goals have changed

You may have started by building a presence in your local market. If demand now supports national expansion, you’ll need to think through what that means for staffing, sales, delivery, and customer support.

Review your active projects against the new goal. Which ones directly support it? Which still serve an important purpose? Which could wait so teams have room for expansion work? Use a consistent project intake process to capture new proposals and compare them against the work you’ve already committed to.

2. Team performance has started to slip

When a team that usually delivers reliably starts missing commitments, find out what changed. In one-on-ones, ask where work gets stuck, which priorities compete, and what people are waiting on. Compare what you hear with planned effort, actual hours, and missed milestones.

If two projects are waiting for the same reviewer, the fix may be to change the order of the work or assign another reviewer. Give the team a chance to explain where the plan breaks down before deciding what to change.

3. Demand is growing faster than your current way of working can handle

Rapid growth can expose decisions and handoffs that used to work because everyone knew who to ask. Approvals slow down, teams interpret priorities differently, and practices that shaped the company’s culture may be hard for new employees to pick up.

Make those practices explicit. Clarify who can approve new work, how teams escalate a conflict, and which customer commitments take precedence. Then review how much growth work you can fund and deliver while maintaining the service your existing customers count on.

4. Employees are disengaging or bringing forward fewer ideas

If people have stopped suggesting improvements or raising risks, ask what changed. They may be dealing with shifting priorities, unclear expectations, limited opportunities to grow, or a workload that leaves little time to improve how they work.

Ask people what they want to develop and what gets in their way. Then act on what you hear. That might mean giving someone ownership of a meaningful initiative, protecting time to test an idea, recognizing a contribution, or addressing compensation when it’s part of the issue.

5. The market or technology has changed

Customer expectations, regulations, and new tools can change the value of work you approved months ago. Revisit the assumptions behind those projects. Does the customer still need the same outcome? Has a new requirement changed the scope? Could automation remove a manual step?

If you’re considering AI, start with a specific workflow, such as preparing a weekly project status report. Check whether the source data is current and consistent, decide who will review the output, and measure whether the pilot saves time. The Project Data Backbone guide series explains what to connect before you rely on that data for reporting, forecasting, or AI analysis.

6. Competitors are pulling ahead

Look at why customers choose a competitor. Sales conversations, lost-deal notes, customer feedback, and competitor research can help you see whether the gap is price, ease of implementation, product capabilities, or service.

Use that evidence to decide what deserves investment. If customers keep citing a long onboarding cycle, compare projects that could shorten it. Consider the expected improvement, cost, time to deliver, and effect on other commitments before choosing which one to fund.

7. Your team is growing and work is getting harder to coordinate

As headcount grows, more teams need to coordinate across sales, operations, delivery, and support. One department can add capacity while another still has to approve every order or handle every implementation.

Use cross-project resource and capacity planning to see where assignments overlap and which roles are short on time. Compare options such as reassigning work, moving a start date, hiring, or bringing in a contractor. Then use project budgeting and cost forecasting to see what each option would cost.

8. You haven’t reviewed your strategy in a while

Set a regular portfolio review and bring the information you need to decide what to continue, change, pause, or stop. Look at progress toward business goals, expected benefits, staffing, forecast costs, and dependencies. Record what you decided and why so teams can adjust their plans.

Even when the strategy still holds, the review can reveal a project whose original assumptions no longer apply or a team that has taken on more work than it can deliver.

Turn a strategy change into a plan your teams can deliver

Start with one business goal that has changed. List the projects that support it, check what teams are already committed to, and decide what needs to move. Give each decision an owner and a date to review the outcome.

Project Insight connects strategic goals, project requests, schedules, budgets, and team capacity. See what your organization has committed to, compare the trade-offs, and decide which work to take on next.

Explore Strategic Portfolio Management


Adapted from the original article by Scott Matthews.