Not Working “Not working” is the most common technical error message in the world, yet it tells us absolutely nothing. When a user submits a support ticket, posts on a developer forum, or texts a coworker stating that something is “not working,” it instantly halts productivity. It forces the person on the receiving end to become a detective, guessing whether a system crashed, an interface froze, or a button simply failed to click.
To bridge this communication gap, we must transform the unhelpful phrase “not working” into an actionable roadmap that solves technical problems quickly. Why “Not Working” Fails Everyone
Saying something doesn’t work is an emotional reaction to frustration, not a technical description. It fails to resolve issues because it leaves out three critical pieces of data:
The Context: What specific action was being attempted right before the failure?
The Expectation: What did the user expect the software or device to do? The Reality: What did the system actually do instead?
Without these points, engineers, customer support reps, and IT professionals are left entirely in the dark. The Anatomy of a Perfect Bug Report
To fix a broken system, you must describe it precisely. Instead of writing “the app is not working,” use a structured four-step approach to get your problem resolved on the first try.
[Clear Summary Sentence] 1. Steps to Reproduce: (Click A -> Fill B -> Press C) 2. Expected Behavior: (What should happen) 3. Actual Behavior: (What actually happened, including error codes) 4. Environment Details: (Device, Browser, Operating System) 1. Trace the Steps
List the exact sequence of actions that led to the issue. Be specific about buttons clicked, fields filled, or commands run.
Bad: “I tried to upload my file and it’s not working.”
Good: “I logged into the dashboard, clicked ‘Upload PDF’, selected a 5MB file, and pressed ‘Submit’.” 2. Contrast Expectation vs. Reality
Clearly state what you expected to see versus what actually happened on your screen.
Expected: The file should upload and a green ‘Success’ banner should appear.
Actual: The screen turned completely white, and a spinning wheel appeared indefinitely. 3. Capture the Evidence
Never ignore the text on the screen. Take screenshots, record short video clips, or copy error logs verbatim. If a specific system error code appears (e.g., Error 404, NullPointerException, or Connection Timed Out), include it. These codes point developers directly to the broken line of code. 4. Define the Environment
Software behaves differently depending on where it runs. Always provide your hardware and software setup: Device: Mac, Windows PC, iPhone, Android Operating System: Windows 11, iOS 19, macOS 16 Application/Browser: Chrome v140, Safari, Shopify App The Power of Precise Communication
Shifting away from vague complaints like “not working” saves hours of back-and-forth messaging. It transforms an ambiguous tech failure into a straightforward engineering task, ensuring your tools get fixed faster and your frustration disappears sooner.
If you are dealing with a specific tech issue right now, let me know: What app, device, or code is misbehaving? What specific error message or behavior are you seeing? Saved time Comprehensive Inappropriate Not working
A copy of this chat, including the images and video, will be included with your feedback A copy of this chat will be included with your feedback
Your feedback will include a copy of this chat and the image from your search
Your feedback will include a copy of this chat, any links you shared, and the image from your search.
Thanks for letting us know
Google may use account and system data to understand your feedback and improve our services, subject to our Privacy Policy and Terms of Service. For legal issues, make a legal removal request.
Leave a Reply