Skip to content

The Most Expensive Word in Software: Simple

A simple software request is the sentence that skips the state the change will touch. The screen looks small. The promise does not.

Founder Logs #39 · Part of Binary and Beyond. LinkedIn newsletter edition follows.

A simple software request is usually a kindness someone offers the room. One field. A badge. A color. I have watched both sides relax when the word lands, because a small surface feels like a small commitment. The screen will be small. The fact the screen is about to publish often is not.

The word is doing a specific job. It claims the change stays inside one boundary, and that every other system already agrees about the fact the change will show. When that claim is true, the work is small. When the claim is unearned, the badge ships on time and the argument about the fact starts the morning someone trusts it.

The badge that was called simple

This scene is a composite, not a client story. The shape is familiar.

A wholesale distributor wants the invoice list in the dealer portal to show whether an invoice is paid. A regional agency holds the relationship. The ask arrives as a sentence: a simple paid badge, finance already knows, no new integration, a few days. The list already exists. The column is empty. The component that would fill it is one the team has written before.

Under the column, three facts already live in the business, and they are not the same fact.

The ERP marks an invoice paid when cash has been applied to that invoice. The bank feed shows cash that landed and has not been applied yet. The portal, as of this morning, treats a remittance PDF uploaded by the dealer as enough to stop a salesperson from chasing.

A short-pay, where the dealer sends most of the balance and deducts a damage claim, is paid in the salesperson's mouth and open in finance. A credit note issued on Tuesday does not move a list that was cached for the morning call sheet.

The happy path is a green dot. The production path is which of those facts the dot is allowed to repeat, how old the fact may be, and who eats the conversation when two of them disagree (Enterprise Software Is Mostly Negotiation, Why Every Workflow Is Really a State Machine).

The diff prices the dot. The weekday morning prices the sentence a salesperson will say with the dot on the screen.

A few days is a duration for a component. The agency hears a favor. The distributor hears a list sales can trust before a call. The delivery team hears a field they have rendered before. When the word simple never records which of those hearings won, the first complaint decides it, and the complaint arrives as a bug.

Why the word feels like a favor

Calling a request simple is how a client avoids feeling expensive, and how a team avoids a meeting that might turn a favor into a scope conversation. Both motives are human. Neither of them checks whether the fact is shared.

Engineers use the word on themselves. "Should be simple" often means "I can see the file I would touch." Seeing the file is evidence about the surface. It says nothing about the definitions that will meet in that file. A person who has only looked at the component is telling the truth about the component. The room hears a truth about the work.

A slightly longer estimate does not repair that. Two days becomes four, and the adjective stays. The credit note still has no sentence. The cache still has no age. The extra days get spent on the component, which was never the part that was going to hurt.

"We will confirm the rule with finance in the build" meets the boundary without a decision. A confirmation that cannot change what the badge says, or stop the badge from shipping, is a meeting you can no longer use. The line that matters is which boundaries someone has already watched disagree, and which ones the word is being asked to cover by silence. A calmer adjective does not draw that line. A definition does.

When nobody in the room can say what the salesperson is allowed to tell a dealer who short-paid yesterday, the honest output is sometimes a narrower badge, or no badge, rather than a greener one (Why We Sometimes Say No to Projects).

Simple is a claim about boundaries

Before I trust the word, I separate two things that the sentence glues together.

The surface is the diff. A column, a component, a query, a color. Surfaces have a size, and that size is often honestly small.

The boundary set is every place two parties can disagree about the fact the surface will display, including disagreement across time. Cash applied versus cash landed. A remittance PDF versus a posted credit note. A list generated at six in the morning versus a payment at nine. A salesperson who will stop chasing versus a collections clerk who must not.

Simple asserts that the boundary set is empty, or already settled by a system the sentence names in passing. "Finance already knows" is that assertion. Finance knows one of the facts. The badge is about to teach a second audience a fact they will act on. Publishing a fact to someone who will repeat it is a boundary, even when the query is short.

You can earn the word. A badge that reads "remittance PDF received, not yet applied," drawn from a table this team owns, refreshed when the page loads, with no one instructed to treat it as paid, has an empty boundary set. The surface is small and the claim is true. That request is simple. It is also a different product from the one the sales meeting asked for.

The expensive case is the unearned word. The surface stays small, and the boundary set is borrowed from silence, because nobody has to lose an argument in the kickoff.

A duration can still be honest about the split. The estimate records the surface and refuses to swallow the boundary set (Every Software Estimate Is a Risk Estimate). The adjective works the other direction. It shrinks the conversation until the boundary set no longer fits in the room.

Where the word shows up

I keep meeting it in three rooms, and it does a different kind of damage in each.

In the brief, before anyone estimates. "A simple paid badge" teaches the room that the work is a column. The definitions never get a line item, so they never get a sponsor. Finance and sales can both say they were clear, about different facts, under one shared sentence.

In the change request, after the date is fixed. "Can we just also treat a bank payment as paid? Should be simple." The date makes the new boundary feel like a courtesy. A courtesy that changes what a salesperson is allowed to say is a product decision. The release plan has no row for it, so the row lands on a person.

In the incident, once the badge is live. "The badge is wrong" is filed against the component. The component matched the rule it was given. The rule was the unearned word. The proposed fix is often the same word again: just check one more system. Each new system is another definition, offered as a patch.

The request saysThe change crosses
A paid badgeWhich system's paid the badge is allowed to repeat
Finance already knowsCash applied, cash landed, and a remittance uploaded are three facts
One field on the listA morning cache a salesperson will quote on a call
No new integrationA definition you will now publish to people who act on it
Should be quickA short-pay, a credit note, and who may contradict the badge
Just a colorThe sentence someone will say because the color is green

The right-hand column is the change. When those cells are blank, the blank is an assignment. It lands on whoever answers the phone when the badge and the ledger diverge.

How an unearned simple arrives as a bug

The first week can look like the word was earned. The column renders. The query matches the sample file finance sent. Standup is short. The trouble stays quiet until a person acts on the color.

  • A salesperson sees Paid and tells the dealer to ignore the collections email. The dealer short-paid and deducted a damage claim. Finance still has the invoice open. Both employees followed the system in front of them. The two systems were never introduced.
  • A credit note posts on Tuesday afternoon. Wednesday's call list was built at dawn from a cache nobody named in the ticket. The dealer hears they are clear, and then hears from collections. The bug report says the color is wrong. The color is the age of a fact, wearing a component's name.
  • Someone adds the bank feed so the badge will look more real. Unapplied cash now paints the same green as cash applied to the invoice. The patch used the same adjective as the original request. The boundary set grew.
  • The release stays put. Short-pays and credit notes are called phase two. Phase two is the boundary set, renamed once it was no longer allowed to touch the badge. What ships is the surface. The promise the sales meeting heard loses its sponsor the week the column looks done.

A green dot for "remittance PDF received" can be the right first release, when every listener heard that sentence and nobody heard "the dealer is paid up." The harm begins when one adjective is allowed to stand for both. The meaning of paid, across a ledger, a bank line, a PDF, and a phone call, is the contract. A badge that does not name those meanings has the shape of a reassurance (Data Contracts Matter More Than APIs).

What should you ask before you accept a simple software request?

Ask these questions before the adjective is allowed to leave the room. They are a gate on the word simple. Clear answers mean the surface is small and the boundary set is either empty or written down. Fog means you have a component. Say component, and staff a component, until someone names the fact.

  1. What will a person repeat because this ships? Write the sentence in their words. "The dealer is paid up" is a different product from "a PDF arrived." If you cannot write the sentence, you do not know what you are publishing.
  2. Which systems already hold a version of that fact, and where did they disagree in the last month, not in a diagram? A disagreement you have not looked for is not evidence that the boundary is empty.
  3. When two versions disagree, which one is the badge allowed to show, and who may override it? A rule with no person beside it will be rewritten by the loudest ticket.
  4. How old may the fact be before someone acts on it? A cache, a nightly file, a list exported at dawn: each one is a boundary in time. Name the age on the same line as the color.
  5. Which event after the badge flips must move it: a credit note, a reversal, a short-pay, a deleted remittance? Who notices if it does not move, and on what morning?
  6. Who is on the phone when the badge and another system diverge? If that person was not in the room where the word was accepted, the room was missing the cost.
  7. What would you have to see before the word is earned? If the answer is a small diff, you have priced the surface and left the boundary set for later. Later is the moment the dealer is already on the call.

When the lines that name the fact, the age, and the person have to be invented, the adjective is an invention too. A friendly ask should not be the author of what sales is allowed to promise. A badge that says "remittance received, as of this page load," with short-pays left off the green state, is a request a collections lead can argue with. A simple paid badge is a slogan with a component. The two phone calls are where that component loses.

Implications for how you hear the word

Replace the adjective with the boundary list. The sentence you want in the ticket is the fact, the source, the age, and the person who may contradict it. A column can still be small after that sentence exists. The sentence is what makes the smallness true.

Let a small diff testify only about the surface. File count, component count, and "we have built a badge before" are real facts about the diff. They do not answer whether two departments share a meaning.

Treat the word in a change request as a new claim. A fixed date does not empty a boundary. "While you are in there" is how a second definition inherits the first definition's lack of a sponsor. If the new fact changes what someone will say on a call, it gets its own line, including the option to leave it out of this release.

Ship the narrower fact on purpose. "Remittance received" is allowed to be the whole release. A smaller promise is a finished product when the larger one has no owner. Calling the cut phase two, and leaving the color to say Paid, keeps the larger promise alive with nobody sponsoring it.

Put the person who will be contradicted in the room where the word is accepted. The collections clerk who works short-pays. The salesperson who will stop chasing. The finance lead who knows which cash is applied and which cash has only landed. Care is a named fact with a person beside it. A green dot with no sentence, priced as a favor, sits inside a release the relationship has made immovable. Name the fact, or keep the color off the list.

The fingerprint

Simple is not a size.

It is a claim that the change never has to say whose fact it is repeating, or how old that fact may be before someone acts on it.

If you cannot name the fact, and who is allowed to contradict it, the word has already spent the money. The invoice arrives as two phone calls, both quoting your badge, telling the same dealer opposite things.

Related reading

Founder Logs #39 · Part of Binary and Beyond. LinkedIn newsletter edition follows.

Agency partner

Need delivery stability without adding headcount?

Quick Brown Fox helps agencies ship complex web platforms, tighten QA, and scale engineering capacity—without becoming a liability to your client relationships.