Turned On, Tuned Out: The PM Features Teams Stop Using
Time Tracking: Many teams abandon time tracking features due to poor alignment with actual project progress needs.
Custom Columns: Excessive custom columns can complicate workflows and reduce overall team efficiency and clarity.
Task Dependencies: Task dependencies often fail in practice due to maintenance challenges and real-world disruptions.
Over-Automation: Complex automation can confuse teams, leading to mistrust and straying from intended workflows.
Simplicity Wins: Returning to simple, effective methods often leads to better project management outcomes than complex features.
Project management tools are packed with features designed to bring order to complex work. But more features don't always mean better outcomes. Across teams of all sizes, the pattern repeats itself: a promising feature gets switched on, runs for a few weeks, and quietly dies. What's left is a system that's harder to use than before and a team that's found its own workarounds.
We asked several practitioners what features they came across in the field that looked useful in setup but failed in practice. Here’s the good, the bad and the ugly.
The Promise of Time Tracking (And Why It Collapsed)
Native time tracking is one of the most commonly enabled — and abandoned — features in tools like Jira. Aaron Whittaker, VP of Demand Generation at Thrive Agency, turned on Jira's built-in worklog for exactly the reasons most teams do. "We turned it on because it looked like a practical way to understand how effort was being distributed across paid media, SEO and content work," he says. "The goal was clearer reporting and better planning for campaign timelines."
Unlock for Free
Create a free account to finish this piece and join a community of forward-thinking leaders unlocking tools, playbooks, and insights for thriving in the age of AI.
Have an account? Log In
It never took hold. Whittaker points to a fundamental mismatch between what the feature measures and what teams actually need to know. "The feature tracks hours not progress," he explains. "Logging five or six hours on ad optimization or landing page updates doesn't tell you if performance improved or if the work is close to completion."
The manual input requirement made things worse. After running the feature for about a month across more than 170 work items, only about 55 had usable entries — and those lacked consistency. "Logging time meant jumping into multiple tasks throughout the day which kept breaking focus," Whittaker says. "After a while it just felt like something you had to do, not something that actually helped."
Logging time meant jumping into multiple tasks throughout the day which kept breaking focus. After a while it just felt like something you had to do, not something that actually helped.
His team dropped it and returned to a simple board-based workflow. "Time tracking looked useful during setup but in real workflows, it duplicated visibility we already had and added friction without improving delivery."
Custom Workflow Columns: When Flexibility Becomes a Liability
Custom columns feel like a natural extension of good process thinking. Scott Davis, Founder & CEO of Outreach.io, learned the hard way that the feature can quickly spiral out of control. "We enabled 'add custom columns' in Jira scrum boards a few years ago for transparency in our workflow," he says. "We turned the feature on in under a minute. We spent weeks turning it into a hidden overhead."
We turned the feature on in under a minute. We spent weeks turning it into a hidden overhead
What started as one "To Verify" column between In Progress and Done multiplied fast. "Before we knew it, there was a column for review for each team," Davis says, with Product adding a column for stakeholder approval and QA adding another for additional checking. "Each scrum board looked different from one another and was not easy to navigate around. People have to check the board configurations just to know how to move that ticket."
The cost showed up in the data. "Our team's cycle time during our high volume sprints kept increasing from 8 days to 10.75 days on average and it was mostly because it was unclear what's the meaning of each extra custom status field," Davis explains. "Our retrospective feedback metrics were full of 'wasted time debating status names.'"
His advice for any team considering column customization: "Treat every added column as technical debt. Without good role discipline and a good reason to deviate from the defaults, it's more difficult to scale work than modifying the default workflow. Most teams will silently decline those extra columns after a few sprints."
Task Dependencies: Clean in Theory, Broken in Practice
Task dependencies are one of the most appealing features in any project management tool. The logic is sound: link tasks together so that delays automatically surface and trigger the right responses. In practice, the feature tends to collapse under the weight of real-world variability.
Dmitrii Malashkin, Founder & CEO at Born to Move, implemented dependencies and advanced task completion automations in Asana — and later in monday.com — to keep project timelines updated and controlled. "The reality, though, was that our team members never really used them beyond the first week after the implementation," he says. The reason was straightforward: "Maintaining your dependencies and automations is a whole job on its own that nobody's supposed to do or actually wants to do, especially once it's not enforced."
Maintaining your dependencies and automations is a whole job on its own that nobody’s supposed to do or actually wants to do, especially once it’s not enforced.
When real-world disruptions hit — a missing permit, a last-minute schedule change, a client availability conflict — the chain broke. "That causes a single point of failure to break the whole dependencies chain," Malashkin explains. "The workflow ends up sending people a flood of generic status update requests, which then leads to everyone muting those." The result was notification fatigue across the board.
His team ultimately abandoned the feature entirely. "Our project managers and crew leads ended up reverting to flat, non-hierarchical task lists plus group chats as their primary modus operandi to coordinate efforts and get more work done."
Eric Turney, President at The Monterey Company, saw the same pattern. "The feature I have seen die on contact with real workflows is task dependencies in a project management tool," he says. "It never stuck since priorities changed too often, the upkeep was annoying, and the system got out of date faster than anyone wanted to maintain it." His team fell back to simpler ownership, clear due dates, and direct communication. "The feature looked smart in the setup phase, but in real life it added admin without giving us enough control back to justify it."
It [task dependencies] never stuck since priorities changed too often, the upkeep was annoying, and the system got out of date faster than anyone wanted to maintain it.
Over-Automation: When the System Works Against the Team
Automation is one of the biggest selling points of modern project management platforms — and one of the easiest things to overdo. Tom Jauncey, Managing Director at Global Sound Group, describes a familiar trap: "One thing that looks good on paper but does not really work out is when we make things too automatic in tools like monday.com. It can get too complicated for the team to follow."
One thing that looks good on paper but does not really work out is when we make things too automatic in tools like monday.com. It can get too complicated for the team to follow.
When automation becomes too layered, teams stop trusting it. "What happens is that people start to ignore the system or do things their way because it seems too hard to understand or it feels like it is holding them back," Jauncey says. The planned workflow and the actual workflow diverge. "The way we plan out the work looks great when we are planning it. It does not really match how the team works from day to day."
The lesson his team landed on was simple: "The best way to do things is the way that people actually use, not the way that has the features."
Percentage Completion Fields and the Illusion of Progress
Some features don't fail because they're too complex — they fail because they're too reductive. Nikita Patil Brennan, Senior Project Manager, flags percentage completion fields as a prime example. "One project management feature that appears on MS Project/Asana is % completion on tasks," she says. "It doesn't tell the whole story — 71% could reflect tasks mostly completed, tasks at risk, tasks blocked etc." A single number flattens context that teams need to act on. Progress isn't the same as health, and a metric that can't distinguish between the two isn't giving anyone useful information.
It [% completion on tasks] doesn’t tell the whole story — 71% could reflect tasks mostly completed, tasks at risk, tasks blocked etc.
AI Features That Overpromised and Underdelivered
As AI features have rolled out across project management platforms, the gap between demo performance and real-world usefulness has been a recurring frustration. Megan Cotterman, Fractional Project Manager and Operations Consultant, encountered this firsthand. "I did have that experience when Asana first rolled out its AI function," she says. "I would ask questions about certain projects in certain contexts and I would have a really hard time finding what I was asking for."
I would ask questions [to Asana AI] about certain projects in certain contexts and I would have a really hard time finding what I was asking for.
The problem isn't unique to Asana — it reflects a broader challenge with AI features that are built for general use cases but haven't yet been trained on the specificity and nuance of how real project data is structured and searched.
Going Back to Basics — The Case for Simplicity
Across every feature category, the teams that found their footing again did so by simplifying. James Dyble, captures the sentiment that many practitioners eventually arrive at. "I used to swear by digital task managers, convinced that everything should live in an app," he says. "Then I caught myself reaching for pen and paper again and again."
I used to swear by digital task managers, convinced that everything should live in an app. Then I caught myself reaching for pen and paper again and again.
His solution wasn't to abandon digital tools entirely but to be more intentional about what they're used for. "Now I've settled on a hybrid approach: I keep my major projects and lists in a digital tool, but I manage my daily priorities on a simple sticky note. There's something satisfying about the physical act of checking things off as I go."
The most effective project management system isn't the one with the most features turned on. It's the one that the team will actually use.
Want more insights like these? Sign up for a free DPM account to hear from more experts like these.
