Kendo HQ

Appearance

Developer PM Sentiment 2025-2026: What Developers Actually Say About Their Project Management Tools ​

Thesis ​

Kendo's positioning rests on four core assumptions: (1) developers are frustrated with Jira's complexity, (2) context switching between tools is a top productivity killer, (3) time tracking as an add-on is a pain point, and (4) developers want PM tools that meet them where they already work (the terminal/IDE). This investigation tests those assumptions against real developer sentiment data from surveys, community discussions, and market research across 2025-2026.

Verdict: All four assumptions are validated by data. But the research also surfaces pain points Kendo's messaging underweights, and one assumption that is weaker than expected.

1. Is "Jira Fatigue" Real and Quantifiable? ​

Answer: Yes. It's real, widespread, and measurable — but Jira remains dominant.

The numbers ​

  • Jira holds 89.45% market share in bug-and-issue-tracking (6sense, 2026). Over 116,800 companies use it. It is not going anywhere.
  • But desire is shifting. The 2025 Stack Overflow Developer Survey (49,000+ respondents, 177 countries) shows Jira stepped down as the most desired collaboration/documentation tool. GitHub is now the top desired tool for code documentation and collaboration.
  • 46% of developers report using Jira (Stack Overflow 2025), but usage does not mean satisfaction. The "Jira alternative" keyword cluster is one of the most competitive in the PM tool SEO space, with at least 15 "best Jira alternatives" articles published in 2025-2026 alone — an indicator of search demand driven by dissatisfaction.
  • A dedicated anti-Jira community exists. The site ifuckinghatejira.com catalogs developer grievances. HN threads like "I fucking hate Jira" (2022, hundreds of comments), "Why Jira Sucks" (2021), "JIRA is an antipattern" (2018), and "The Slow, Painful Death of Agile and Jira" (2024) consistently surface with high engagement. This is not a passing fad — it's a decade-long pattern.

What developers specifically say ​

The complaints cluster into five categories:

1. Performance and slowness.

"Every transition takes 3-5 seconds, and those transitions happen dozens of times per day."

Jira's Java-based architecture is noticeably slower than modern tools like Linear. When a developer updates a task dozens of times daily, cumulative latency destroys flow state.

2. Configuration bloat.

"You need to fill out 87 fields just to report a simple bug."

Over time, Jira instances accumulate hundreds of inactive projects, thousands of unused custom fields, orphaned workflows, stale dashboards, and automation rules nobody remembers creating. Atlassian's own community documentation addresses "Why Your Jira is Slow" with advice on cleaning up configuration bloat.

3. Process overhead.

"You spend more time updating tickets than writing code."

Developers consistently report that Jira becomes a tool for management surveillance rather than developer productivity. Over-engineered workflows — mandatory fields, approval chains, status transitions with required comments — slow teams down before development work even starts.

4. UI complexity.

"The Jira interface is overwhelmingly cluttered."

Atlassian's 2025 UI overhaul drew mixed reactions. While 97% of early access testers opted to stay with the new navigation, broader community feedback on Atlassian Community forums reflects frustration with constant UI changes ("change fatigue") and remaining complexity.

5. Pricing structure.

"Pricing quickly becomes unsustainable as teams grow."

Key features are locked behind Premium ($14.54/user/month) or Enterprise tiers. AI features (Rovo) require Premium. Audit logging requires Premium. This creates a perception that Jira nickels-and-dimes teams.

The nuance ​

Not everyone agrees. Some HN commenters argue the anti-Jira sentiment is an "echo chamber about perceived project management overhead by individual contributors rather than issues with the product itself." The tool works well for large enterprises with dedicated Jira admins. The fatigue is concentrated among:

  • Small-to-mid teams without Jira admin resources
  • Individual contributors who see the tool as management overhead
  • Developers who compare Jira's speed to modern alternatives like Linear

Kendo relevance: Jira fatigue is real and validated. But Kendo should be careful not to position purely as "anti-Jira" — the market is saturated with that message. The more compelling angle is what Kendo adds (terminal-native, time tracking included, EU-hosted) rather than what Jira lacks.

2. Context Switching: The Biggest Productivity Tax ​

Answer: This is the #1 developer pain point by multiple measures.

The numbers ​

  • 12-15 major context switches per day for the average developer (industry data, 2025-2026).
  • 23 minutes recovery time per switch. That's 4.5+ hours of lost deep focus daily.
  • $78,000/year per developer in estimated lost productivity from context switching (industry analysis, 2026).
  • 1,200 app toggles per day for the average digital worker — roughly one every 24 seconds during an 8-hour workday (Speakwise, 2026).
  • 50% of developers lose 10+ hours per week to non-coding tasks; 90% lose 6+ hours (Atlassian State of Developer Experience 2025, n=3,500).

The paradox Atlassian found ​

Atlassian's own 2025 DevEx report uncovered an irony: developers save ~10 hours/week using AI tools, but lose ~10 hours/week to organizational inefficiencies. The productivity gains from AI are being canceled out by tool friction, context switching, and information-finding overhead. The top time-wasters cited: finding information (services, docs, APIs), adapting new technology, and switching context between tools.

What developers want ​

JetBrains publicly stated in March 2026 that the solution is to "fix context switching at the IDE access layer" — bringing external tools into the IDE rather than forcing developers out of it. This aligns directly with the MCP approach: instead of opening a browser to update a Jira ticket, the developer manages issues from their terminal.

The MCP ecosystem validates this demand. By early 2026, at least 10 major PM tools have official MCP servers. Over 1,000 MCP servers exist across services. MCP was donated to the Linux Foundation in December 2025. The market consensus is clear: developers want their tools to come to them, not the other way around.

Kendo relevance: This is Kendo's strongest validated pain point. The terminal-first positioning is not a nice-to-have — it addresses the single biggest productivity complaint developers have. The messaging should lead with the productivity math: "12 context switches/day x 23 min recovery = 4.5 hours lost. What if your board lived in your terminal?"

3. Time Tracking: The Quiet Frustration ​

Answer: Validated, but it's a mid-tier pain point — not the top one.

The landscape ​

Time tracking is surprisingly absent from the most popular developer PM tools:

  • Linear: No native time tracking. Requires Toggl, Harvest, or similar.
  • Asana: No native time tracking. Requires integrations.
  • GitHub Projects: No time tracking at all.
  • Shortcut: No native time tracking.
  • Plane: Time tracking on Pro+ ($6/user/month) only.
  • ClickUp: Time tracking on Unlimited+ ($7/user/month) only.
  • Jira: Via add-ons only (Tempo, etc.).

Developer sentiment ​

The frustration surfaces most clearly among:

  • Freelancers and agencies who need time tracking for client billing. Using Jira + Toggl means two subscriptions and manual sync between systems.
  • Small teams where the tech lead needs time data for sprint retrospectives and capacity planning but doesn't want to manage a separate tool.
  • Toggl users who report frustrations with cross-tool sync, manual tag/description copying, disconnects between machines, and the cognitive overhead of remembering to start/stop timers.

Linear's response is telling: when asked about time tracking, Linear's team has consistently declined to add it, instead pivoting toward AI-driven automation ("Issue Tracking is Dead," March 2026). This creates a persistent gap that competitors can exploit.

The nuance ​

Time tracking is not universally desired by all developers. Many actively resist it — they see it as management surveillance. The demand comes from specific personas:

  • Freelancers/contractors who bill by the hour
  • Team leads who need capacity data
  • CTOs who need time data for client reporting

Kendo relevance: "Time tracking included" is validated as a real differentiator, especially for the Floris (freelancer) and Tessa (tech lead) personas. But it's not the lead pain point for most developers — context switching and tool complexity rank higher. Position time tracking as a "no extra subscription" bonus, not the primary pitch.

4. What Developers Praise: Lessons from Linear and Plane ​

Understanding what developers love is as important as what they hate.

What makes Linear beloved ​

Linear consistently receives the highest developer praise among PM tools. The reasons are instructive:

  • Speed. "The absence of loading states, combined with keyboard navigation that flows naturally between actions, creates something that project management software almost never achieves: a flow state." Developers compare it to an IDE, not a web app.
  • Keyboard-driven workflow. S for status, A for assign, P for priority, L for label, Cmd+K for command palette. Every action is reachable without a mouse.
  • Opinionated simplicity. Linear limits status types to six. You can't create 47 custom statuses. This is both its greatest strength (reduces cognitive load) and its limitation (teams with unique processes feel constrained).
  • Design quality. The UI is described as "closer to an IDE than a spreadsheet." Developer aesthetics matter — ugly tools get resented.

What makes Plane attractive ​

Plane (46,500+ GitHub stars) appeals to a different developer archetype:

  • Open source and self-hostable. For data-sovereignty-conscious teams, being able to inspect and host the code is non-negotiable.
  • Zero cost for basic use. Internal sprint planning, bug tracking, and roadmap management at zero cost (apart from hosting).
  • Clean design. Keyboard shortcuts, inbox triage, rich issue detail pages.
  • Limitations acknowledged. Advanced reporting, resource management, and portfolio views are less developed than commercial tools. Time tracking is only on Pro+.

The pattern ​

Developers consistently praise PM tools that exhibit:

  1. Speed — sub-second response times on every interaction
  2. Keyboard-first navigation — command palettes, single-key shortcuts
  3. Opinionated defaults — fewer choices, better out-of-box experience
  4. Developer aesthetics — dark themes, monospace fonts, dense information display
  5. Minimal ceremony — create an issue in seconds, not minutes

Kendo relevance: Kendo's dark-themed, dense UI with JetBrains Mono and keyboard shortcuts aligns well with what developers praise. The MCP integration takes this further by eliminating the browser entirely. But speed is non-negotiable — if Kendo is not sub-second on every interaction, none of the other advantages matter.

5. The Small Team Problem ​

Answer: Small teams are underserved and actively frustrated.

The core finding ​

Most PM tools were built for enterprises and then offer stripped-down free tiers for small teams. The result:

"Many teams have signed up for tools, gotten overwhelmed, and quietly gone back to spreadsheets or group chats."

The 2025-2026 data shows that small teams (1-15 developers) face specific frustrations:

  • Feature overwhelm. They use only 20% of the tool's features but pay for 100%.
  • Setup overhead. Tools require extensive onboarding before producing value. Jira reportedly takes 2-3 weeks to master.
  • Price-to-value mismatch. Paying for Jira + Toggl + Slack integrations is overkill for a 3-person team.
  • Missing middle ground. GitHub Issues is too basic (no proper board, no time tracking, no sprint planning at scale). Jira is too complex. The tools in between (Linear, Shortcut) are good but lack time tracking or EU hosting.

What small teams actually want ​

Based on community discussions and market research:

  1. A board and a backlog that work out of the box — no setup wizard
  2. Quick issue creation without mandatory fields
  3. Time tracking if they bill clients — built in, not bolted on
  4. GitHub integration that syncs automatically
  5. A price that doesn't scale to Jira-level before they've hired their tenth developer

Kendo relevance: This directly validates the Floris persona. The positioning of "When GitHub Issues isn't enough, but Jira is too much" resonates with documented small-team frustration. The "all-in-one without bloat" angle is strong here.

6. AI as a Purchase Driver — But Trust Is Low ​

The numbers ​

  • 55% of PM software buyers say AI functionality is their primary motivator for purchasing new software (Capterra 2025, n=2,545 project management professionals globally).
  • 84% of developers use AI tools in some form (Stack Overflow 2025).
  • But 46% report distrust in AI outputs (Stack Overflow 2025).
  • 41% of organizations say AI adoption is their top software challenge (Capterra 2025).
  • 39% report a lack of AI skills on staff.

The paradox ​

AI is simultaneously the #1 purchase trigger and the #1 adoption challenge. Developers want AI features but don't trust them yet. The winning position is not "we have AI" (everyone does) but "our AI is transparent and trustworthy":

  • Audit trails for AI actions (what did the AI do, when, and why)
  • Human-in-the-loop workflows (AI drafts, human approves)
  • AI that reduces work rather than creating new work to manage

MCP as the practical AI interface ​

The terminal/MCP approach to AI in PM tools is interesting because it puts the developer in control. The AI assistant reads issues and updates boards via MCP, but the developer types the command. This is a more trusted interaction model than "AI agent autonomously triages your backlog."

Kendo relevance: Kendo's hash-chained audit logging for AI actions is a genuine differentiator in this trust gap. The positioning should emphasize AI transparency: "AI manages your board — and every action is audited." The MCP approach (developer-initiated AI actions) maps to higher trust than autonomous AI agents.

7. EU Data Sovereignty: A Growing Wedge ​

The numbers ​

  • GDPR fines totaled €5.65 billion since 2018, with 2025 alone accounting for €2.3 billion — a 38% year-over-year increase.
  • The EU Data Act (effective September 2025) extends sovereignty to non-personal and industrial data.
  • The US CLOUD Act allows US authorities to demand data from US-based providers regardless of where data is stored — directly conflicting with GDPR.
  • 71% of PM software buyers rank security as their #1 selection factor — above price, usability, and features (Capterra 2025).

Developer sentiment ​

The question is no longer just "Where is my data stored?" but "Who owns the platform, and which courts can issue binding orders to it?" For EU teams evaluating PM tools, this creates a real decision factor:

  • Jira, Linear, Asana, GitHub, ClickUp, Monday.com — all US-owned, US-headquartered
  • Plane — US-based but self-hostable (sovereignty via infrastructure control)
  • Kendo — Amsterdam-hosted, Dutch-owned, database-per-tenant

The dedicated site jira-alternatives.org specifically lists "Top 8 European Jira Alternatives" — indicating that EU origin/hosting is becoming a distinct market segment.

Kendo relevance: The Christiaan (CTO) persona is validated. EU data sovereignty is a growing purchase factor, especially with 2025's enforcement escalation. "Amsterdam-hosted, Dutch-owned, database-per-tenant" is a message that sells itself to this segment without needing to be the primary pitch.

8. What the Market Wants in 2026-2027 ​

The APMIC 2026-27 report on agile PM tool effectiveness and other market analyses converge on what the market is moving toward:

  1. Operational impact over feature count. "The real question is whether a tool improves delivery quality under pressure — can it reduce decision lag, expose blocked work early, and give leaders visibility without burying teams in reporting overhead?"
  2. Financial features rising. Budget tracking, variance analysis, and forecast dashboards inside the PM tool rather than in separate finance systems.
  3. Integration depth over breadth. Teams prefer deeper integration with fewer tools over shallow connections to everything.
  4. Adoption over power. "No matter how powerful a PM tool is, if dev teams find it annoying, they won't use it — adoption matters more than features."
  5. AI that improves judgment. Not AI that creates noise, but AI that helps prioritize, triage, and surface what matters.

Findings Summary: Kendo's Assumptions vs. Reality ​

Kendo AssumptionValidated?StrengthNotes
Developers are frustrated with Jira complexityYesStrongDecade-long pattern, quantifiable in surveys, search demand, community discussion
Context switching is a top pain pointYesVery strong#1 productivity killer by multiple measures; $78K/year estimated cost
Time tracking as add-on is a pain pointYesModerateReal for freelancers/agencies/team leads; not universal across all developer types
Developers want terminal-native PMYesStrongJetBrains, MCP ecosystem, and 10+ PM tools adding MCP servers validate the direction
EU hosting mattersYesGrowing€2.3B in GDPR fines in 2025 alone; dedicated "European alternatives" market segment exists
AI is a differentiatorPartiallyErodingAI is now table stakes (55% purchase trigger), but audit trails and trust gap create differentiation opportunity

Surprises and gaps ​

  1. Speed is non-negotiable and underweighted in Kendo's messaging. Linear's praise centers on sub-second performance. Every "why developers love X" discussion starts with speed. Kendo's marketing doesn't lead with speed — it should at least address it.

  2. "Opinionated simplicity" is what developers actually want more than feature richness. The Kendo pitch of "everything included" could backfire if it reads as "another ClickUp." The framing should be "everything you need, nothing you don't" rather than "everything included."

  3. The small-team segment is more frustrated than expected. These teams don't just want a cheaper Jira — they want a fundamentally simpler tool. Many have tried Linear, Shortcut, and GitHub Projects and found each lacking in different ways. This is Kendo's sweet spot.

  4. Developer aesthetics matter more than expected. Dark themes, monospace fonts, dense layouts, keyboard shortcuts — these are not cosmetic preferences but signals that a tool "gets" developers. Kendo's design language (JetBrains Mono, kendo-red, dark theme) aligns well.

  5. The audit trail gap in MCP automation is a real finding. MCP adoption is booming, but no one is solving audit trails for what AI agents do via MCP. Kendo's hash-chained audit logging positions it uniquely here.

Recommendations for Kendo ​

Messaging adjustments ​

  1. Lead with context switching, not Jira fatigue. Everyone says "Jira alternative." Few say "your board lives in your terminal — zero context switches." The data shows context switching is the bigger pain point; use it.

  2. Add speed to the pitch. Even a brief mention — "sub-second everything" — signals developer seriousness. Linear's reputation was built on speed before features.

  3. Reframe "everything included" as "nothing extra." Instead of: "Board + sprints + time tracking + GitHub + AI." Try: "No Toggl subscription. No Tempo add-on. No enterprise tier for audit logs. Just one tool, one price."

  4. Amplify the MCP audit trail angle. "MCP automation is booming. Audit trails are missing." This is a market gap Kendo uniquely fills. It resonates with both the CTO persona (compliance) and the broader AI trust gap (46% developer distrust).

Persona validation ​

  • Floris (Freelance Dev): Strongly validated. The "paying for Jira + Toggl is overkill" pain point appears repeatedly in community discussions.
  • Tessa (Tech Lead): Strongly validated. Context switching, team visibility, and "we use 10% of Jira" are well-documented frustrations.
  • Christiaan (CTO): Validated with growing strength. EU data sovereignty is an increasingly distinct market segment with dedicated comparison sites.

Content opportunities ​

The planned blog post "Jira fatigue: what developers actually want" (listed in marketing-strategy.md) should be written using this research data. It can cite the Stack Overflow shift, the Atlassian DevEx paradox (save 10 hours with AI, lose 10 hours to friction), and the $78K/year context-switching cost.