# How do I plan a Value the project cannot move?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Press "Main menu", choose "Plan", search and select the Value, press "Edit", press "Wish", not "Goal" or "Tolerable", under "Levels", type the number.

## Before you start

You need to be [signed in to GilbApp](http://support.gilb.com/help/how-do-i-sign-in-to-gilbapp) on a computer, with a vault you can write to, such as [your own vault](http://support.gilb.com/help/how-do-i-create-my-first-vault). The [Value must already exist](http://support.gilb.com/help/how-do-i-write-a-value-in-my-plan) at the level "Stakeholder", with a "Scale" and a "Status" number, and the vault needs [a stakeholder](http://support.gilb.com/help/how-do-i-add-a-person-as-a-stakeholder) for step 7. The pictures show a made-up person on a test site; your screen shows your own name and address.

## Steps

1. Press "Main menu" at the top left and choose "Plan".

   Press "Main menu", next to your profile picture at the top left, and under "YOUR SECTIONS" choose "Plan". The button shows the name of the section you are in, such as "Vaults".

   A panel headed "GO TO" opens; "Plan" reads "Your Kai-Zen plan: Functions, Values, Development Resources and Solutions." You can also press the "Plan" button on the card of a vault \(the place where a person or a group keeps their records\) in "Vaults". The "Plan" screen lists your plan records and has the views "Grid", "Graph", "Both" and "Card".

   ![GilbApp with the "GO TO" panel open, and "Plan" under "YOUR SECTIONS" outlined in orange.](http://support.gilb.com/help/media/a82ee78879a56e7f.png)
   What you see: The "GO TO" panel is open over the screen. Look in the left column under "YOUR SECTIONS": the outlined row is "Plan", with the line "Your Kai-Zen plan: Functions, Values, Development Resources and Solutions." Press it to open the Plan screen.
2. Search and select the Value in the list.

   Type part of the Value's tag \(its short name\) in the search box and select the Value in the list. A Value is a perceived benefit, measured as a number.

   The search box shows "Search in current filters…" while a filter is on, and "Search your vault…" otherwise. The button "Value" in the row of kinds shows only Values.

   ![The "Plan" screen with a Value's tag typed in the search box above the list and the Value found; the search box is outlined in orange.](http://support.gilb.com/help/media/6fb7ad4dd2dc1600.png)
   What you see: You are on the "Plan" screen in "Grid" view. The outlined search box holds the first word of the Value's tag, and the list below shows the Value Landowner.RiverRent. Press its row to select it.
3. Press "Edit".

   At the top right of the Value's card, press "Edit". The button then reads "Done".

   The card says "Editing. Changes save as you leave a field." There is no Save button. Beside "Done", a "+" does what "+ Add Information" at the foot of the card does; you do not need it. The card shows "Edit" only to a person who may write in its vault. "+ Level" also works without "Edit": it opens a panel with the same kinds as buttons, and the new row shows "Add value", which you press to type the number. "Edit" is clearer, because the number box is then ready at once.

   ![The Value's card with its "Edit" button at the top right outlined in orange.](http://support.gilb.com/help/media/4345fa75a8b2f8ac.png)
   What you see: The Value is selected in the list and its card shows in the right pane: "Level: Stakeholder", and under "Illustration" one point, the "Status" 4000 on the arrow, in EUR. Press the outlined "Edit" at the top right of the card.
4. Under "Levels", press "Wish" beside "+ Level".

   Under "Levels", press the button "Wish" beside "+ Level". A new "Wish" row appears, with its number box ready to type in.

   A "Wish" is a number someone says they would like on a "Scale". The buttons are "Past", "Status", "Tolerable", "Goal" and "Wish", then "Other word…". "+ Level" opens a menu of the same kinds, but in GilbApp today choosing from it can end edit mode, so press the button. The new row has no date yet. It copies the qualifier choices and conditions of the latest level. Press neither "Goal" nor "Tolerable": the rule for the level "Stakeholder" uses neither for a Value the project cannot move \(Deeper, below the steps\). If the Value already has a "Goal" or "Tolerable" row, "×" at the end of that row removes it.

   ![The Value's card in edit mode, with the "Wish" button beside "+ Level" under "Levels" outlined in orange.](http://support.gilb.com/help/media/6a750ba9fc705e67.png)
   What you see: The card is in edit mode \(the pane is widened here\). Under "Levels" is the Status row 4000, and below it "+ Level" with the buttons "Past", "Status", "Tolerable", "Goal", "Wish" and "Other word…". Press the outlined "Wish".
5. Type the "Wish" number in the new row and press Enter.

   Type the number someone says they would like in the new "Wish" row and press Enter. Count it in the unit of the "Scale", the ruler the Value is measured on.

   The first box of the row holds its word, "Wish". Clicking away saves it too; there is no Save button. Kai-Zen writes a "Wish" only when you or the source state the number; it does not estimate one. The box that shows "Note, e.g. estimate" takes a short note; it is optional. "⧉" copies the row's qualifiers to a new level and "×" removes the row; you need neither.

   ![The Value's card with a new "Wish" row under "Levels", with its number box holding 5000 outlined in orange.](http://support.gilb.com/help/media/b738a204d9785add.png)
   What you see: A new row whose first box reads "Wish" is under the Status row. The outlined number box of the Wish row holds 5000, typed and saved with Enter.
6. Type the date in the "Wish" row's date box.

   In the date box of the "Wish" row, type the date by which the number would be reached. A level holds only at its date and its condition.

   If the number holds only in one case, type it in the box that shows "Condition, Enter" and press Enter; "×" beside a condition removes it. For a "Scale" with qualifiers, the row also shows a box for each, to say which case the number is for. The date is not needed to save.

   ![The Value's card with the date box of the "Wish" row, holding 31/12/2027, outlined in orange.](http://support.gilb.com/help/media/2e92ec6be62b4fc1.png)
   What you see: The "Wish" row holds 5000. The outlined date box of the Wish row holds the date 31/12/2027. Type the date the Wish was said for.
7. Search and select who said it in the "Wish" row's "Source" box.

   In the "Wish" row's "Source" box, type part of the name of the person who stated the number and select them. It records who said it.

   The box finds the stakeholders and documents in the vault; a stakeholder is a person, group or system that cares whether a Value goes up or down. If none matches, it says "No stakeholder or document matches." and offers a button that keeps the words you typed as text instead. A red round \(−\) in front of a chosen source removes it. The source is not needed to save; in the Kai-Zen form for a Value, a "Wish" has a person as its source.

   ![The Value's card with a name typed in the "Source" box of the "Wish" row and one stakeholder found, with the "Source" box outlined in orange.](http://support.gilb.com/help/media/fe48f453a95229d7.png)
   What you see: In the "Wish" row, the outlined "Source" box at the right holds the first letters of a name, and one stakeholder is found under it, marked "Person". Choose that person.
8. Press "Done" when you have finished.

   Press "Done" at the top right of the card. What you typed is already saved.

   The Value now has a "Status" and a "Wish", and no "Goal" or "Tolerable". GilbApp works out a % only from one "Status", one "Tolerable" and one "Goal", so under "Impacts", the effects Solutions are expected to have on it, and in a Value Decision Table, a table that ranks options by how much they move the level's Values for their cost, this Value's cells say "No % yet": no option gets a % for it.

   ![The Value's card with a "Status" and a "Wish" under "Levels", with the "Done" button at the top right outlined in orange.](http://support.gilb.com/help/media/6518ba07a7e24ae9.png)
   What you see: Under "Levels" the card shows the Status row and the Wish row with 5000, its date and its source. Press the outlined "Done" at the top right of the card when you have finished.

## Deeper

Also asked:

What if the project cannot change something? Plan it as a Value with a "Wish", a number someone says they would like, instead of a "Goal" and a "Tolerable": nothing the project builds can change it, so the project promises no number for it.

What does "Wish" mean? A "Wish" is a number someone says they would like for a Value, which the project does not promise to reach. Kai-Zen writes one only when you or a source state the number.

What is the difference between "Goal", "Tolerable" and "Wish"? "Goal" is the number you plan to reach. "Tolerable" is the survival limit: worse than it, the project is expected to fail. A "Wish" is a number someone would like that the project does not promise, for a Value it cannot move.

A Value the project cannot move is one whose number nothing the project builds or does can change. Example: for a club that builds an app for its members' catch log, the rent the landowner gets for the club's stretch of river. Kai-Zen's rule for such a Value is one of its rules for the level "Stakeholder", where each Value is about the stakeholder: what they want, need and care about. For a Value the project cannot move, the rule for the level "Stakeholder" is to use no "Goal" \(the number you plan to reach\) and no "Tolerable" \(the survival limit\) but a "Wish" \(a number someone says they would like\), which Kai-Zen writes only when you or the source state the number. Another Kai-Zen rule, to set "Tolerable" and "Goal" itself for every Value, says otherwise; where two rules disagree, Kai-Zen chooses the reading that best serves the Values.

GilbVeda, the shared list of terms, calls a Wish a target level that a stakeholder values and that is not committed: not a number the project promises to reach.

For a Value the project can move, [the answer on setting a Goal and a Tolerable level](http://support.gilb.com/help/how-do-i-set-a-goal-and-a-tolerable-level) shows how to set them. [The answer on the levels of a plan](http://support.gilb.com/help/what-are-the-levels-of-a-plan) explains "Stakeholder", and [the answer on writing a Value in your plan](http://support.gilb.com/help/how-do-i-write-a-value-in-my-plan) shows the rest of the card.

This answer is written for a computer screen.

Source: GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 \(https://gilb.com/app/version.json read 2026-11-10, buildTime 2026-11-09.522Z, dirty false\), read \(no checkout, no copy\). Levels buttons: PlanValueLines.tsx:2138-2151 \(one button per offered kind, "Add &lt;kind\> level"\), :2152-2160 \("Other word…"\); planValue.ts:1655 \(OFFERED\_LEVEL\_KINDS Past, Status, Tolerable, Goal, Wish\), :1668-1680 \(newLevelFromClick: only Status dated today; qualifier choices, conditions and side copied from the most recent level\). Level row: PlanValueLines.tsx:2491-2501 \(kind box\), :2504-2510 \(date box, type date\), :2533-2545 \("One side" only for target\), :2546-2550 \(conditions\), :2551 \(number box, autofocus on the new row\), :2552-2560 \(Source\), :2561-2567 \("Note, e.g. estimate"\), :2568-2585 \("⧉" "Copy qualifier to a new level"\), :2586-2593 \("×" "Remove level"\). Source box: PlanSource.tsx:37 \(placeholder "Source"\), :204-231 \(finds stakeholders and documents; "No stakeholder or document matches."; \`Use "&lt;typed\>" as text\`\), :198-202 \(RemoveControl "Remove source" before a chosen one\); RemoveControl.tsx:1-20 \(red round \(−\) at the left\). No %: valueLimits.ts:90-93 \("No % yet: &lt;tag\> needs one Status, one Tolerable and one Goal."\), :111-116 \(no Tolerable or no Goal = no %\); planTable.ts:315-330 \(cells say "No % yet"\). Standards \(2026-11-10\): Kai-Zen.StakeholderLevelRules.CanMove \("Values the project can not move; don't use Goal or Tolerable; use Wish"\), .AboutThem, .Contents; Kai-Zen.ValueRules.Wish \("Write a Wish only if the requester or the source states it."\), .Estimate, .SpaceTime; Kai-Zen.ValueTemplate \("Wish \[YYYY-MM-DD, condition\] &lt;number\> &lt;- HumanAgent"\). GilbVeda public read 2026-11-10: t:Wish \(\*244, Approved: "a stakeholder-valued, not-committed target level for a scalar attribute"\), t:PlanguageWishLevelWhen \("the deadline or window by which the accompanying Wish level would be reached"\). Example from https://myjackfruit.com/news/kai-zen-and-its-23-agents/ \(the made-up fly-fishing club; "the landowner who rents the club its stretch of river"\). Published wording reused: "What is a Wish?" short answer; Step 4 names the Stakeholder-level rule. "Before you start" names the stakeholder step 7 and its picture need \(the "Source" box finds the vault's stakeholders and documents, else "No stakeholder or document matches.", PlanSource.tsx:204-231; shots.json fixture c\). Also: Kai-Zen.ValueRules.Estimate, Kai-Zen.StopRules.Conflict. Live answer: How do I set a Goal and a Tolerable level?
