The Small Change That Was Not Small
Alex runs a small product company. On a Tuesday morning a customer asks for one more field on the invoice screen. Alex messages the engineer: how long?
"It's just a small change. About an hour."
Three weeks later the field is still not live, and nobody has done anything wrong.
What the engineer meant
The engineer was telling the truth about the part they could see. Adding a field to one screen really is about an hour. What they had not yet looked at was everything the field would touch.

Software is a tower of small decisions made at different times by different people. Pull out one block and you find out which others were resting on it. In Alex's case the new field also appeared in the exported PDF, the spreadsheet download, the mobile app, the tax rounding rules and the translations. Each of those had its own tests, and two of them had none.
Engineer-to-English
We keep a running list of phrases that sound like promises but are really first guesses. Here are four of them.
- "It's just a small change." What it means: I have not looked at what else it touches.
- "That should take an hour." What it means: I have not thought about testing yet.
- "It works on my machine." What it means: I have not met your machine yet.
- "We'll clean that up later." What it means: that is now part of the design.
None of these are lies. They are honest first guesses, said out loud, and then repeated by everyone else as a commitment. The damage comes from the repetition, not the guess.
Why it keeps happening

Nobody builds a bridge from a first guess. Construction has a stage where someone walks the site and reads the drawings before a number is given. Software teams skip that step because it feels too slow for something small, and because the person asking is waiting.
The pressure is real. A manager who hears "I need a day to look" often hears "I do not want to do it." That is the first thing to fix. A day of looking is the cheapest part of the whole job.
Three questions that make a small change honestly small
You do not need to read code to ask these. Ask them before you agree to a date.
- What else does this touch? Ask the engineer to list the screens, reports, integrations and files that mention the thing being changed. If the list is short and they can name each item, the change really is small.
- How will we know it works? A change without a test is a change you will find out about from a customer. Ask what will be checked, by whom, and whether that check already exists.
- Where does it run? Development, a test copy, the live system and every customer's phone are different places. Ask which ones this change reaches and who moves it from one to the next.

The sentence to try instead
Replace "it's just a small change" with "I think it is small, and I will confirm by tomorrow." It costs one day, it turns a guess into a finding, and it gives the person asking something they can plan around.
If the answer comes back as "yes, it really is an hour," you have lost nothing. If it comes back as three weeks, you have saved the other two and a half.
What we do at Adyakshar Labs
We build custom software, embedded systems and cloud platforms for clients, and we write estimates only after the looking is done. When a request arrives that sounds small, the first thing we send back is the list of what it touches. It makes the conversation shorter, not longer.
If you have a project where the small changes are getting expensive, we are happy to talk it through. You can reach us through https://adyaksharlabs.com.

