MyJackfruit

Help
Browse topics · How good it must be (Values and goals)

How good it must be (Values and goals)

← Back to How does Kai-Zen keep the whole project's Values in view?

What are the levels of a plan (Business, Stakeholder, Product)?

Checked against GilbApp d529620.

Levels split a plan, top down: Business, what the owners gain; Stakeholder, what each stakeholder wants; Product, what the product does and how well.

Deeper

Also asked:

What do Business, Stakeholder and Product levels mean? Business holds what the owners gain, such as profit; Stakeholder, what each stakeholder wants, needs and cares about; Product, what the product does (its Functions) and how well (its Values).

A Level says which part of the plan a record belongs to. A Value is a perceived benefit, measured as a number. In the Kai-Zen method, each Product Value helps a Stakeholder Value, and each Stakeholder Value helps a Business Value.

Business is the top level. It holds the Values of the owners' highest purpose, and all of the project's Development Resources, the things the work uses up, such as money, time or people: at least the total budget and the running cost per month. It holds no Functions. The owners are the project, business or organisation owners. For a business, its Values measure what the owners gain, such as profit, earnings, stock price or the company's reputation; for a charity or public body that declares a mission, the outcomes of that mission, such as people served. Reach, such as users or sign-ups, belongs at Stakeholder, unless the Value turns it into money for the owners. A quality of the product is not a Business Value: the owners' outcome it drives is written instead.

Stakeholder holds only Values about the stakeholders: what each one wants, needs and cares about for themselves, their business or their ventures, such as money, efficiency, success at their goals, or fun. A stakeholder is a person, group or system that cares whether a Value goes up or down. The level holds no Functions, and the Development Resources stay at Business. The owners are stakeholders here too: what they value beyond their highest purpose, such as sign-ups, goes here. A Stakeholder Value does not describe the product and, if it can, does not name it. Kai-Zen writes the Values one stakeholder at a time. 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.

Product holds Functions and Values. A Function is what a system does, written as an action. A Product Value belongs to the product: it goes from the product to a stakeholder, or to another product or system. Example: how easy the app is for its user is a Product Value, not a Stakeholder Value. Kai-Zen splits each Stakeholder Value into one Product Value per way the product delivers it, such as coverage, speed, ease or safety: one Scale, the ruler a Value is measured on, measures one thing. The level is done when every Stakeholder Value has at least one Product Value that helps it. Kai-Zen writes a Function only when more than one Value needs it, or when you ask for one; usually the Value's Value of Function line is enough. On a Value at Product or below, Value of Function names the Function the Value measures; at Business and Stakeholder, that line stays empty.

Below Product, GilbApp also lists Solution, the level of the Solutions. A Solution is how a Function gets done.

Kai-Zen writes the levels in this order: Business, then Stakeholder, then Product. Within a level it writes the Functions first, then the Values, then the Development Resources, then any Solutions, in your order of priority if you gave one. Then a Value Decision Table (VDT), a table that ranks options by how much they move the level's Values for their cost, picks what the next level holds; the VDT at Product picks the Solutions. In GilbApp, a Value Decision Table is made for one pair of levels, chosen under LEVEL when you make it: Business: Business Values × Stakeholder Values, Stakeholder: Stakeholder Values × Product Values or Product: Product Values × Solutions, which it shows first.

When Kai-Zen writes your plan, each level is written by these rules. If you give Kai-Zen a Value that belongs at another level, it moves the Value there, keeps your words and numbers, and lists each move when it shows you the plan for approval. How to start is in the answer on starting work with Kai-Zen.

In GilbApp, every Value, Function, Solution and Development Resource card shows Level on the line under its header. Open the list next to it and choose the level; the answer on writing a Value in your plan shows how. The levels you can choose are the project's own, Business, Stakeholder, Product and Solution by default. Until you choose, a Value shows Product, a Solution Solution and a Development Resource Business; a Function shows none. GilbApp lets you put any card at any level; it does not check the rules above, which are the Kai-Zen method's.

+ Add level… at the end of the list adds a level of your own. Type its name in the box that shows Label. In the list under it, keep main level for a level of its own, or choose a level to put the new one under it. Then press Add level; Cancel adds nothing. With no name, the screen says A level needs a label. A level put under another shows beneath it in the list, set in. A card whose level is not one of the project's levels says not one of this project's levels under that line; choose another.

On the Plan screen, the row of levels above the list shows All, then one button per main level of the project. Press a level to show only its cards, press more than one to show the cards of each, and press All to show every card again. A card at a level you put under another counts under that main level. A Function with no level, and a VDT, VKT or VTT table (Value Decision, Kick-out and Tracking Tables) with no level, are left out while a level is pressed, and a line says how many and why. The row of kinds under it, from All and Value to VTT, narrows the list the same way.

A plan's levels are not the Levels on a Value's card: those are numbers on its Scale, such as Status, Tolerable and Goal. The answer on setting a Goal and a Tolerable level shows them.

This answer is written for a computer screen.

Source: GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 (https://gilb.com/app/version.json read 2026-11-09, buildTime 2026-11-09.522Z, dirty false); code read at af0f04ee (no checkout). Level list and line: PlanTypeLevelVersion.tsx:56-158 (Type:, Level:, Version:; select with + Add level… :145; button outside edit :147-157); planLevels.ts:33-43 (DEFAULT_LEVELS Business, Stakeholder, Product, Solution), :26 (not one of this project's levels), :211-213, :216-226 (sub-level set in by depth), :358-396, :426-456 (add level; A level needs a label. :434); planKinds.ts:202-213 (shown before stored: Solution and Solution Constraint Solution, Value Product, Resource Business, Function none); PlanFunctionForm.tsx:858-881 (choose and add level, no rule check; error to the notice), :974-982, :1737-1738, :1754-1785 (add-level form: Label, main level, Cancel, Add level), :1789-1828 (line on every plan card), :1823-1824 (warning). Filter rows: RecordGrid.tsx:1182-1209; PlanFilterRows.tsx:28-61 (All, one button per main level; kinds All, Value ... VTT), :65-91; planFilterRows.ts:19-29 (kinds), :66-91 (left-out sentences), :112-152 (OR within a row, AND between rows; Function with no level and tables left out); planLevelPair.ts:14-16, :39-66 (sub-level counts under its main level; type default when none stored). VDT level: recordTypes.ts:270-290 (TABLE_LEVEL_OPTIONS, TABLE_LEVEL_WORDS, required, default Product), :445-457; ConnectedCreateDialog.tsx:1530-1541 (required field beside the name), :2474-2478 (label drawn uppercase: LEVEL), :2492-2509 (option labels). Value card lines: planKinds.ts:101-112, :162-175 (Value of Function, Levels, Scale). Standards (2026-11-09): Kai-Zen.BusinessLevelRules (Contents, Purpose, Stakeholder, Values, Mission, NotReach, NotProduct, Resources; Endpoint and Currency not used), Kai-Zen.StakeholderLevelRules (Contents, AboutThem, Owners, NotProduct, ByStakeholder, Supports, CanMove), Kai-Zen.ProductLevelRules (Contents, Attached, Endpoint example, Supports, Functions, Split, Coverage), Kai-Zen.ValueRules.Function, .Wish, Kai-Zen.WriteLevel (Order, Functions, Write, Resources, Solutions, Next), Kai-Zen.New.Down, Agent.Outcome.Gate, Kai-Zen.ValueRules.HumanSet (the level still moves), Kai-Zen.SolutionRules.How. GilbVeda public read 2026-11-09: t:BusinessLevel, t:StakeholderLevel, t:ProductLevel, t:SolutionLevel, t:CauseEffectLevel, t:ValueDecisionTable (a:does read). Also: Kai-Zen.StakeholderLevelRules.CanMove, Kai-Zen.ValueRules.Wish, Kai-Zen.ValueRules.Estimate, Kai-Zen.StopRules.Conflict.