Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Every demo is slides and promises, and I never see working software

Short answer

A demo should show real software doing one real task on a real device, not slides or screenshots. If every demo ends with 'it is almost ready', progress is being measured in activity, not in finished work. Ask for a small piece that works from start to finish, shown on your own phone or computer.

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

Does this sound like your situation?

  • Demos are screenshots, mock-ups or a developer's screen with a script.
  • I am told a feature is done, but I cannot try it myself.
  • The same feature appears in several demos and is never finished.
  • Demos only work on the developer's computer.
  • At the end I still do not know what I can ship.

Why does this happen?

  1. Work is split by layer, not by outcome

    If one person builds the screens and another the back end and they join at the end, nothing works until everything is done. A demo of half the layers can only be pictures.

  2. Nothing is released to a test environment

    A demo from a real test version, which you can open yourself, forces the pieces to connect each week. When there is none, problems pile up unseen.

  3. 'Done' has no definition

    If done means 'coded' and not 'works, is tested and you can use it', then every feature is almost done for weeks.

  4. The tasks are too large to show

    Large tasks sit at 'nearly done' for weeks. Small pieces that fit into a week show real progress or real trouble early.

What can I do about it today?

  1. Ask to use it yourselfRequest a test version you can open on your own phone or computer, with a login, before the next demo. Seeing it work for yourself is the strongest check.
  2. Agree what done meansWrite one sentence: a feature is done when it works end to end, has been tested and you can use it. Share it with the developer.
  3. Ask for one small, finished sliceInstead of a bigger list, agree on one small task that must work completely at the next demo, for example a customer signing up and seeing their first screen.
  4. Keep a short written listAsk for a list with three columns: works, in progress, not started. It should be updated after each demo.
  5. Confirm you own the accountsCheck that the code repository and the hosting accounts belong to your company, so you can always see the real state of things.

When should I bring someone in?

  • Two or three demos in a row show no working feature.
  • The developer cannot or will not give you a test version.
  • You suspect the real state is much worse than the demos suggest.

How do I handle it?

  1. Set up a test version you can openA test environment is made, updated with each change, and you receive a link and a login.
  2. Define done togetherI write a short definition of done with you and apply it to every item on the list.
  3. Cut the work into small slicesEach slice goes from screen to database to a working result, so every week something runs end to end.
  4. Run the demo on real useEach demo is you or your staff doing a real task, with me watching rather than driving.

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 normal for early demos to be rough?

Yes, rough is fine. A demo that shows a rough but real task working is useful. A demo that shows only pictures is not.

What if the developer says the work cannot be shown yet?

Part of the work, such as setup, may really not be visible. Even then, ask what can be shown by the next demo and why not sooner.

How often should a demo happen?

A common rhythm is every one or two weeks, with the same simple format each time. What matters is that something real is shown.

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.