MyJackfruit

Help
Browse topics · What it must do (Functions)

What it must do (Functions)

← What it must do (Functions)

Why does my plan need Functions, and how many?

Short answer

Functions are what your app must do, such as book a repair; they tell the builder what to build. Start with the main ones.

Deeper

Also asked:

How many Functions should my first version have? There is no set number. Kai-Zen writes the Functions for your whole idea, and your first version does not need them all: the app is delivered in steps, each as small as possible while it still brings something real.

What is the difference between a Function and a feature? A Function says only what your app does, such as book a repair time. A feature, such as a calendar where customers pick a time, can mix that with one way of doing it; in the plan, that way is a Solution.

What are Functions, Values, Development Resources and Solutions under Plan? They are the parts of your plan under Plan in Main menu: Functions, what your app must do; Values, how well it must do it; Development Resources, what building it costs: time, money, people; Solutions, the ways it is built.

What does Function mean in my plan? A Function is something your app must do, written as an action, such as book a repair time. It says what, not how well, which is a Value, and not how, which is a Solution.

What is the difference between a Function and a Value? A Function is what your app must do, such as book a repair time; a Value is a goal for how well it must do it, such as how quickly a customer can book.

A Function is what a system does, written as an action, such as book a repair time. It says what, not how well and not how: how well is a Value, a goal for how well your app must do something, and how is a Solution, a way of doing it. In GilbApp you meet them in Plan in Main menu, the button at the top left next to your profile picture that shows the name of the section you are in. Functions there reads What the system does: Functions and Function Constraints.

What they do for your app: they are the list of what gets built. Each one has the ways to build it linked to it, and the Values that say how well it must work. Each has a Status, one of Planned, Building, Developed, Production or Retired, so you can see what is built and what is still to come.

A made-up example, a booking app for a small bike-repair shop: book a repair time, change or cancel a booking, see the day's bookings, and remind a customer the day before. Book a repair time is a Function; how quickly a customer can book is a Value about it; an online calendar to pick a time in is one way, a Solution, to do it.

A Function and a feature: a feature, such as a calendar where customers pick a time, can mix what the app does with one way of doing it. The calendar holds the Function, book a repair time, and one way to do it, the calendar. The plan keeps them apart: a Function says only what the system does, and the way is a Solution.

How many? There is no set number. Say in your own words the main things a person does with the app. Kai-Zen, the planning agent, writes the Functions for your whole idea, each only once, and a big one can be split into parts. Your first version does not need them all: Kai-Zen delivers the app in steps, each as small as possible while it still brings something real. The answers How big should my first version be? and How do I write a Function in parts and link them? say more.

To write one yourself, see the answer How do I write a Function in my plan?

This answer is written for a computer screen.

Source: Kai-Zen standards: Kai-Zen.FunctionRules (What, Lookup, PartOf, Status, Values); Kai-Zen.ValueRules.Function; Kai-Zen.New.Down; Kai-Zen.ValueDeliveryStepRules.Small. GilbVeda t:Function. GilbApp 96968de7 (live build, 12 November 2026): src/shell/gilbAppMenuRows.ts:162-169 (Plan, Functions, What the system does: Functions and Function Constraints.). Live help pages, shared: What is a Function? (A Function is what a system does, written as an action.); What is a Value?; What is a Solution?; How do I write a Function in my plan? (the four Status words; linked Values and Solutions); How big should my first version be? (steps as small as possible while still bringing something real); How do I write a Function in parts and link them?. GilbApp 49467c2b (live build, 14 November 2026): src/shell/gilbAppMenuRows.ts:163-175 (Values, How well it does it.; Development Resources, What it costs: time, money, people.; Solutions, How it is done: Solutions and Solution Constraints.).

Checked against GilbApp d529620.