Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I change what is urgent every week and my developers are losing patience

Short answer

Developers lose patience when work is dropped half-finished, because each switch costs them time to stop, restart and rebuild context. The fix is a single ranked list that one person owns, a short fixed planning rhythm, and a rule that urgent changes replace something on the list instead of being added on top.

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

Does this sound like your situation?

  • Every week I ask for something new and the last thing is still not finished.
  • My developers say they keep starting things and never completing them.
  • Features are half-built in the code but not usable by anyone.
  • I cannot tell what the team is working on right now, and neither can they.
  • Good developers have started to sound tired or have left.

Why does this happen?

  1. Every request arrives as urgent

    When customers, staff and the owner all ask directly, whatever was asked last feels most important. Without one ranked list, the loudest request wins, not the most valuable one.

  2. Switching has a hidden cost

    Stopping a task midway means leaving code in a state nobody can ship, then coming back later and re-reading it. The developer is busy the whole time, but less gets finished.

  3. Work is never small enough to finish

    Large tasks stay open for weeks, so any new priority lands while they are still open. Smaller pieces that can be completed and released in a few days make a change of direction cheap.

  4. Nobody can say what a change costs

    If a new request is accepted without hearing what it pushes back, it feels free. The team then absorbs the cost silently, and it shows up as late or half-finished work.

What can I do about it today?

  1. Write one list in orderPut everything you want built on a single page, ranked one to ten. Ties are not allowed; if two things are equal, pick one.
  2. Ask the team what is half-doneAsk for a plain list of work that has been started but not released. Finishing those usually brings more value than starting anything new.
  3. Send requests to one personDecide who collects requests from staff and customers, and ask everyone else to send them there. Developers should hear about changes from one voice.
  4. Fix the day you re-planPick a fixed slot, for example every second week, when the order may change. Outside that slot, only a real emergency interrupts the team.
  5. Swap, do not stackWhen something new is urgent, ask the team what comes off the list to make room. Say the answer out loud so the cost is visible.

When should I bring someone in?

  • Your developers or agency keep missing dates and you cannot tell if the cause is the work or the changes.
  • A key developer has resigned or hinted they will.
  • You have no one on your side who can judge technical effort when they say a task takes long.

How do I handle it?

  1. List what is openI start by writing down every started and unfinished item, who is holding it and what is blocking it.
  2. Cut work into releasable piecesLarge requests are split so each part can be shipped and used on its own, which makes later changes of direction cheaper.
  3. Agree a simple planning rhythmOne ranked list, one owner on your side and a short regular check-in. Changes are recorded with what they displace.
  4. Write down the cost of changesWhen a new request arrives I say in plain words what it delays, so the decision is yours and informed.

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?

Is it wrong to change priorities?

No. Real businesses change direction. The problem is changing without choosing what gets dropped, and changing so often that nothing reaches users.

How do I know if the delay is my changes or my developers?

Ask for a list of what was started, what was released and what was changed in between. If many items were started and few released, changes are a likely cause. If little was started, the problem lies elsewhere.

What counts as a real emergency?

Something that stops customers paying, loses data or exposes private information. A strong opinion or a competitor's feature is usually something for the ranked list.

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.