# What is Planguage?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Planguage, short for Planning Language, is Tom Gilb's language for writing plans in numbers: each Value with a "Scale", a "Meter" and "Levels".

## Deeper

Tom Gilb, who has worked in Norway since 1958, carried earlier ideas of measured improvement into software in the 1970s. He showed planners and engineers how to write down every critical factor, the soft qualities too, and called it Planguage. GilbVeda, the shared list of terms, calls it a language for writing requirements and designs, with methods for estimating how designs move the requirements, checking the quality of what is written, and running a project in evolutionary steps: change, feedback, learning, and change again. Its formal definition is in Tom Gilb's book Competitive Engineering \(2005\). [The answer on where the Kai-Zen method comes from](http://support.gilb.com/help/where-does-the-kai-zen-method-come-from) tells the rest of that history; Kai-Zen is the planning agent that plans in Planguage.

In Planguage a quality is not a word such as fast: it is a Value with numbers that you can check. A Value is a perceived benefit, measured as a number. The "Scale" is the ruler a Value is measured on, and the "Meter" says how someone reads the current level off the "Scale". The "Levels" are numbers on the "Scale": "Status" is where you are now, "Tolerable" is the survival limit \(worse than it, the whole project is expected to fail\), and "Goal" is the number you plan to reach. Example: for Quick sign-up, in minutes per sign-up, lower is better: "Status" 6, "Tolerable" 10, "Goal" 2.

A Planguage line names the level, then in square brackets when and where it holds, then the number, and after "&lt;-" who said it. GilbApp's paste box on a Value shows one: "Paste lines, e.g. Goal \[2027-06-30, Release 3.0\] 5 &lt;- Kai-Zen estimate", a "Goal" of 5 by 2027-06-30 for Release 3.0, estimated by Kai-Zen. A level holds only at its date and its condition.

When Kai-Zen writes a Value, it never uses the words non-functional, NFR or quality attribute: it calls such a quality a Value. In GilbVeda, a quality is how well a system works as a stakeholder \(a person, group or system that cares whether a Value goes up or down\) sees it, and every quality can be described as a number on a "Scale".

Kai-Zen works in Planguage: it chooses the way with Planguage, Value Decision Tables and Value Kick-out Tables, and with decisions on Values at several levels. A Value Decision Table \(VDT\) is a table that ranks options by how much they move the level's Values for their cost; a Value Kick-out Table \(VKT\) is a table that picks one of several options by how much Value each gives for its cost. When Kai-Zen writes a Value, it fills in the Planguage form its standards give for it, so each Value it writes has a "Scale", a "Meter" and "Levels"; it does the same for each step it plans to deliver.

In GilbApp, "Plan" \("Your Kai-Zen plan: Functions, Values, Development Resources and Solutions."\) keeps the plan as cards, and a Value's card has the lines "Scale", "Meter" and "Levels". [The answer on writing a Value in your plan](http://support.gilb.com/help/how-do-i-write-a-value-in-my-plan) shows how to fill them, and [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 the limits. [The answer on the levels of a plan](http://support.gilb.com/help/what-are-the-levels-of-a-plan) explains "Business", "Stakeholder" and "Product".

This answer is written for a computer screen.

Source: Public pages read 2026-11-10: https://myjackfruit.com/about/ \("1970s · Into software": "Tom Gilb, born in California in 1940 and working in Norway since 1958, carried these ideas into software. He showed planners and engineers how to articulate all critical factors, including 'soft' qualities, to better understand the complex systems, and called it Planguage, short for Planning Language."\); https://myjackfruit.com/ \(technical card: "Planguage \(Tom Gilb's language for quantified requirements\)"; "Each level states its values with numbers, so "fast" and "secure" mean something you can check."\); https://myjackfruit.com/news/kai-zen-and-its-23-agents/ \(2026-11-04, Kai Gilb: "The way of working underneath is Planguage, the specification language Tom Gilb has taught for decades. Every Value is written in numbers ..."\). GilbVeda public read https://veda.gilb.com/base/t/&lt;name\> and /base/terms?q= 2026-11-10 \(mint kit signed out\): t:Planguage \(\*030, Approved: "a specification language and a set of related methods for systems engineering. It specifically supports requirement specification, design specification, design impact analysis, specification quality control, and evolutionary project management."\), t:PlanguageConcept \("Planguage is defined formally in Gilb: \*Competitive Engineering\* \[2005, Elsevier\]"\), t:Quality \("a scalar attribute reflecting 'how well' a system functions as viewed by a defined Stakeholder ... All qualities can be described numerically using a defined Scale"\), t:Value, t:Qualifier \("Square brackets around the qualifier conditions are used to denote a qualifier"\), t:Scale, t:Meter, t:Status, t:Tolerable, t:Goal. Standards \(2026-11-10\): Kai-Zen \(step Kai-Zen.Path: "Choose the path with Planguage, VKT, VDT and multi-level value decisions."\), Kai-Zen.WriteValue.Planguage \("You are writing one Planguage Value. Fill Kai-Zen.ValueTemplate."\), Kai-Zen.WriteStep.Planguage \("You are writing one ValueDeliveryStep. Fill Kai-Zen.ValueDeliveryStepTemplate."\), Kai-Zen.ValueTemplate \(Scale, Meter, Status/Tolerable/Goal \[YYYY-MM-DD, condition\] &lt;number\> &lt;- &lt;Source\>\), Kai-Zen.ValueRules.Words \("Never write "non-functional", "NFR" or "quality attribute". Call it a Value."\), .SpaceTime. GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 \(https://gilb.com/app/version.json read 2026-11-10, buildTime 2026-11-09.522Z, dirty false\), read: PlanValueLines.tsx:2185 \(paste box placeholder "Paste lines, e.g. Goal \[2027-06-30, Release 3.0\] 5 &lt;- Kai-Zen estimate"\); shell/gilbAppMenuRows.ts:163 \("Your Kai-Zen plan: ..."\). Published wording reused word for word: Value gloss, "Scale" gloss, "Meter" gloss, Status/Tolerable/Goal glosses \("What are Levels?"\), Quick sign-up example \("What are Levels?"\), VDT and VKT glosses, "What is Kai-Zen?" \("the planning agent"\), "A level holds only at its date and its condition.", GilbVeda gloss.
