Explore Problems

Monday.com's mobile app suffers from extreme lag and instability on both iOS and Android, making daily work dread-inducing for users. Each update introduces new problems rather than fixing existing ones, and the app is described as unusable for regular work.

AT&T provided written confirmation of a $815.76 billing adjustment but applied only $96, then cited a retroactive policy time limit to refuse completing the remainder — despite the delay being AT&T's own. Customers who relied on AT&T's written commitments and chose not to escalate are penalized by the carrier's internal processing failures. This pattern of using policy constraints to abandon acknowledged billing obligations is a structural carrier accountability problem.

Bank of America's automated system provides no path to a human representative, and account notification emails obscure account number digits, preventing login. The two failures create a compound lockout scenario customers cannot resolve independently.

Southern California Edison is perceived as an unaccountable monopoly that controls its regulator, makes electricity bills impossible to understand, and actively frustrates solar panel users. Consumers and businesses have no recourse against rate increases or service failures.

New users of ClickUp-style tools face a busy interface and many customization options that take time to learn. Larger workspaces make the clutter worse, and default layouts do little to guide setup.

Gusto pay schedule cutoff times are unclear, making it hard to know when pay periods begin and end.

Google Drive mobile users experience chronically slow uploads and downloads, with stalling progress bars even on new high-end devices

ISP billing systems send payment-due alerts to accounts that are fully current, indicating a state synchronization failure between billing and notification systems. These false alerts erode trust and generate unnecessary customer service contacts. Customers have no self-service way to verify their billing state or suppress erroneous notifications.

As AI coding agents generate increasing amounts of code, teams lack a systematic way to verify behavioral correctness and safety constraints, such as credential leaks, permission violations, or duplicate side effects from retries, beyond static code review and conventional test suites. Unit, integration, and E2E tests leave a gap in behavior-only issues that remain untested.

Boards that start clean drift out of alignment with reality as priorities shift, tasks split, and work is postponed, until the tool no longer reflects what the team is actually doing. Restoring trust in the view requires ongoing manual cleanup, which becomes its own overhead. The tool adopted to simplify coordination ends up generating maintenance work of its own.

Current AI assistants hit hard capability boundaries and refuse tasks slightly outside their predefined scope. Users want AI that can perform computer actions, adapt to novel requests, and extend capabilities based on user needs. The fixed-scope architecture limits AI assistants to known task categories rather than general problem-solving.

AI autocomplete exists in code editors but nowhere else on the desktop. Knowledge workers typing in Slack, email, Jira, and other apps lack a system-wide AI that learns their writing patterns and completes thoughts with a single keystroke.

AI chat conversations generate valuable ideas and thinking, but these insights are scattered across hundreds of chat sessions with no way to connect, organize, or build on them over time. Users keep restarting the same thought processes because previous conversations are effectively lost.

A developer describes management mandating a 2x AI-driven productivity target, which pushed the team toward spec-driven development producing large specs, plans, and merge requests (thousands of lines) that teammates refuse to review as "too much," even though activity logs show they never actually opened the documents. Both a full-detail version and a heavily distilled version of the same work were rejected, revealing a structural mismatch between how much AI-assisted developers can now produce and how much a team can realistically review and absorb.

Mortgage servicers aggressively market VA IRRRL refinances to veterans that violate the 36-month recoupment requirement under federal law, with break-even periods exceeding 80 months. Veterans with no financial expertise cannot easily calculate whether a refinance offer meets federal guidelines. The predatory churning strips home equity while providing no financial benefit to the veteran homeowner.

Immigrants pursuing the EB-1A extraordinary ability visa self-petition route have no reliable way to evaluate whether their evidence profile meets the USCIS officer criteria before filing. Generic eligibility calculators do only binary yes/no screening, missing the nuanced evidence mapping and narrative gap analysis that distinguishes strong from weak petitions. The attorney cost creates a structural barrier that disproportionately affects highly skilled immigrants who are price-sensitive.

Reviewers compare Jira unfavorably with Notion, calling out a rigid, ticket-centric structure that does not flex for product discovery, strategy, or cross-functional collaboration. Critical features sit behind premium plans.

Teams and individuals lose valuable context and insights as tasks move through project management tools like Notion, Linear, and ClickUp. Task-level notes rarely make it into wikis, and buried details become impossible to retrieve months later. Existing tools create silos between task execution and knowledge capture.

Engineering teams lose critical decision-making context over time — rationale buried in Slack threads, stale PR descriptions, or the memory of departed team members. As agentic coding tools accelerate code production, this context decay problem compounds: knowledge is generated faster than it can be captured or surfaced. The result is that AI coding sessions lack institutional memory, causing repeated mistakes, redundant discussions, and degraded code quality over time.

Support teams find a major helpdesk platform overly complex, with SLAs not applying to all tickets regardless of channel and setup needing vendor support. Small configuration changes can break the whole chain and force rework.