# Nano Banana: a prompt for a four-step process diagram

Give Nano Banana a clear sequence, arrows and exact labels for a process diagram, then check its exception branch and correct a single block.

Canonical URL: https://boswidget.ru/en/nano-banana-a-prompt-for-a-four-step-process-diagram/

![A fabric diagram on a terracotta background: four blue nodes with light-coloured arrows and an ochre branch leading to a help icon.](https://boswidget.ru/assets/images/articles/nano-banana-process-diagram-1200.cf773ed90ed8.webp)

The main route and the exception branch need distinct directions and positions, not just different colours.

A collection counter needs a short guide: show your code, check the order, confirm receipt and collect the parcel. The sequence sounds clear enough. In an image, an arrow might skip the check, or “Confirm receipt” might become something to do too early. Work out the logic on paper before asking Nano Banana to give it a visual form.

We will use a guide that visitors read while standing at the counter. It has one main route and one exception: the code cannot be found. This is a practice scenario; for your own collection point, use approved procedures and replace the labels. The model should not decide when staff may hand over an order or what counts as sufficient confirmation.

## First, fix the sequence that must not change

Write each step as a short phrase describing one action. If a line needs three verbs, the diagram probably needs another block. Identify the start, the end and the point where the normal route breaks off. Arrows carry meaning; they are not decoration between cards.

```
Source scenario for the practice guide:
1. Show your code.
2. Check the order with a member of staff.
3. Confirm receipt.
4. Collect your parcel.

Main route: 1 → 2 → 3 → 4.
Exception: after step 1, code not found → “Ask a member of staff”.
There is no arrow from the exception branch to steps 3 and 4. This guide does not describe what happens next.
The arrow from the first step to the second is labelled “Code found”. The “Ask a member of staff” block is an endpoint: it has no outgoing arrows.
```

The draft deliberately includes no waiting times, document requirements or promise of automatic collection. If you need those conditions, add them to the source scenario before generating the image. Do not leave gaps for the model to fill with invented rules.

## Use the prompt to separate content from presentation

Google’s image-generation documentation recommends describing the scene in detail and refining the result through follow-up edits. For a diagram, separate the required text from its visual treatment. List the labels and connections first, then specify size, colour and visual density. A list of attractive styles will not make up for a missing connection.

```
Create a flat process-diagram guide for a visitor at a collection counter. Use a vertical composition, a light background, large dark text and simple icons. This is an instruction sheet, so the design must not compete with the order of actions.

Four main blocks, from top to bottom. Reproduce these labels exactly, without abbreviations or added words:
1 — “Show your code”.
2 — “Check the order with a member of staff”.
3 — “Confirm receipt”.
4 — “Collect your parcel”.

Connect the main blocks with directional arrows only in the order 1 → 2 → 3 → 4. From block 1, draw a separate side branch labelled “Code not found” leading to a block labelled “Ask a member of staff”. Give the side branch a different colour. Do not connect it to blocks 3 and 4, and do not add arrows pointing backwards.

Give each block one short label. Leave clear margins. No logo, decorative wording, additional steps or small explanatory text.
Label the connection from the first main block to the second “Code found”. Make the “Ask a member of staff” block an endpoint, with no outgoing arrows.
```

This request defines a composition, but does not guarantee that every letter or connection will be correct. If a phrase will not fit, shorten it yourself first and update the source list. Otherwise, the image becomes a place where the instructions change unnoticed. For a guide in another language, prepare a separate, agreed set of labels.

## Check the diagram in two passes

In the first pass, follow the route. Set appearance aside and trace every arrow from start to finish. Then follow the exception separately. In the second pass, check the wording: compare the labels with the source list, including word endings, negatives and word order. A readable phrase can still be the wrong phrase.

- There are exactly four main blocks, with none repeated or missing.
- The next action is clear at each main step; arrowheads are visible and do not accidentally point into a neighbouring block.
- The “Code not found” branch starts at the first step and ends with asking a member of staff, with no connection to collection. The help block is an endpoint with no outgoing arrows; the normal connection to checking the order is labelled “Code found”.
- The labels match the draft. No new conditions, deadlines, promises or actions have appeared.
- At the intended viewing size, the text, numbers and arrow directions remain distinguishable; the meaning does not depend on colour alone.

Show the diagram to someone who was not involved in preparing it and ask what they would do if their code could not be found. If they go to the final block, fix the route or the branch placement, even if every label is spelled correctly.

## One edit, one visible problem

If the available mode supports editing an existing image, supply it along with a specific correction. Do not ask to “make it look better”, change the font and fix an arrow all at once: afterwards, it is hard to tell what else has changed. Keep the previous file for comparison.

```
Correct only the exception branch. It currently appears to connect to block 4. Remove that connection. The “Code not found” branch must run from block 1 only to the “Ask a member of staff” block. Preserve the other blocks’ labels, sequence and positions, and the main route 1 → 2 → 3 → 4. Do not add any new elements.
The “Ask a member of staff” block must remain an endpoint, with no outgoing arrows of any kind. Preserve the “Code found” label on the connection from the first main block to the second.
```

The rest of the image can change even when you ask to preserve it. After an edit, repeat both checks. If editing is unavailable in your chosen interface, add the clarification to the full original prompt and generate a new diagram; do not assume the service remembers the previous image.

## When to put text on a separate layer

Long labels, small mandatory text and frequently changing conditions are easier to maintain in an editor. You can ask Nano Banana to prepare the layout and icons with blank spaces, then add the approved wording and arrows manually on top. Changing one word will no longer require generating the entire image again.

Before printing, choose the guide’s physical size and check a proof from the distance at which people will read it. For an on-screen version, view it in a normal-sized window. An attractive large image does not mean that a negative word in a label or a thin side arrow will be visible at the counter.

- [Create a diagram with Nano Banana on YesAI](https://yesai.su/en/nanobanana)

Keep the final image, the approved step list and the prompt together. When the process changes, update the list before the design. That leaves a clear record of where each label came from and why an arrow leads to that particular block.

[Prompts for Nano Banana](https://boswidget.ru/en/prompts-for-nano-banana/)

- [Google: Gemini image generation and editing](https://ai.google.dev/gemini-api/docs/image-generation)