Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My developer built something that is not what I asked for

Short answer

Most wrong-thing builds come from a brief that two people read differently. Spoken requests and short messages hide assumptions. Write the task as a user story with how it is checked, show working screens early, and review each small piece before the next starts, so a misunderstanding costs days and not months.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The result works, but it is not what I had in mind.
  • My developer says it is exactly what I asked, and I disagree.
  • I only saw the finished product at the end and then found the problems.
  • The idea was described in a call or voice note and nothing was written down.
  • Every correction turns into more work that I did not expect.

Why does this happen?

  1. The idea was in your head, not on paper

    You know your customers and your day. A developer does not. Words like simple, quick or like the other app mean different things to each person.

  2. Nobody described how it would be checked

    Without a sentence such as when a customer does this, they should see that, there is no shared test of whether the work is done.

  3. You saw it too late

    A first view after weeks of work means every misunderstanding has already been built into the product and costs more to undo.

  4. The developer filled gaps with guesses

    Unanswered questions do not stop the work. Developers make a reasonable choice and move on, and it may not be your choice.

  5. A wrong thing and a changed mind look the same

    Sometimes the build matches the brief and the brief was not what you really wanted. Both need a fix, but the next step differs.

What can I do about it today?

  1. Do not argue about blame yetFirst compare what was asked for against what was delivered, using any messages or notes you have. Blame helps nobody and the facts help everyone.
  2. List the differences one by oneWrite each gap as a pair: what I expected, what I see. Pictures or screen recordings help a lot.
  3. Mark which gaps matterTag each as must change, would like or can live with. Many wrong-thing projects turn out to be three important gaps and a lot of preferences.
  4. Ask the developer to repeat it backBefore any new work, ask them to explain in plain words what they will build and what the user will see. Fix the difference before they start.
  5. Ask for a view every few daysRequest a short demo or screenshots of working parts at regular points, not only at the end.

When should I bring someone in?

  • You and your developer disagree about what was agreed and you need a neutral reading.
  • The product is large and you cannot tell whether the wrong part is small or fundamental.
  • You are about to pay for a restart and want an independent view of what can be reused.

How do I handle it?

  1. Turn the wish into written storiesEach need is written as who does what and what they see, with a short way to check it.
  2. Ask the questions up frontGaps are raised as questions to you before the work, so they are not settled by guesswork.
  3. Show screens before buildingA rough sketch or clickable mock shows misunderstandings when they are still cheap.
  4. Review small piecesWork is delivered and reviewed in short steps so a wrong turn is caught early.
  5. Assess what can be keptIf something is already built wrongly, I read what exists and write down what can be reused and what must be redone.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How detailed does a brief have to be?

Detailed about what a user sees and does and how you will check it, but it does not need technical wording. Plain sentences and a few screenshots or sketches are enough.

Do I have to pay for the wrong version?

That depends on your agreement with the developer, and I cannot give legal advice. A written list of gaps against the original request is the best starting point for that conversation.

Can the wrong build be fixed or must it restart?

Often parts can be kept. It needs someone to read what was built and compare it with what is needed.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.