fpf.tools
Jump to text
On this page
Copy and source
Original source · lines 39–76
Published source confirmed at last check

Source changed 2026-10-14 19:58:00 UTC · snapshot created 2026-10-14 19:58:38 UTC · last check 2026-10-15 00:05:10 UTC

Customization and Productization Management Principles Framework Readme

Practical entries

Bring the question you are actually trying to answer. These entries are selected examples, not a catalogue or a coverage boundary. If none fits, search the Table of Contents or enter a pattern directly. You can ask an assisting agent: “Explain this and give me your comments in ordinary language, without framework jargon.”

CUST-ENTRY-DELIVERY - Turn a successful delivery into an obtainable method

  • Situation: A service works when its author is present, but another prepared team cannot yet repeat it.
  • Question: Which work, preparation and help must become available for the next delivery?
  • First useful result or blocker: A constructed delivery method with an attainable receiving performance, or the exact missing capability, permission or support.
  • Start with: CUST.6.
  • Stop or return: Retain explicit assisted provision when it fits; return a false family assumption to CUST.3 rather than adding unexplained instructions.

CUST-ENTRY-CHANGE - Improve the common offering while current customers continue

  • Situation: A shared change affects installed configurations, accepted meanings or support promises.
  • Question: How can the affected customers obtain a valid continuation?
  • First useful result or blocker: A compatible extension, transition, coexistence or retained arrangement with its work and authority, or the unresolved receiving result.
  • Start with: CUST.8.
  • Stop or return: Do not widen the change beyond its supported conditions. Preserve unaffected service and obtain the missing contribution.

CUST-ENTRY-GROWTH - Grow without hiding repeated invention

  • Situation: Several customers want related adaptations, and common development appears attractive.
  • Question: What can we share, how will it be delivered and what burden follows?
  • First useful result or blocker: A supportable answer connecting what can be shared, an obtainable delivery method and the full resource comparison, or the condition preventing it. A successful local case can remain local.
  • Start with: CUST.1, connecting the family in CUST.3, delivery in CUST.6 and resource comparison in CUST.7.
  • Stop or return: Use an adequate existing configuration directly. Narrow or stop the affected promise when capability, permission, resources or current obligations defeat it.

Use the whole Method or a sufficient part

Start with the supported offering and the actual customer result. Recover their consequential differences, then construct a compatible local and shared continuation. Productization can produce a repeatable service or reusable contribution; it does not require every local adaptation to become a common product.

The intended reader manages a product, service, customer delivery, implementation practice or another undertaking with continuing customer commitments. Use the large CUST.1 Method when the customer case and future offering must be developed together. Use a smaller Method when the current problem is already bounded. A supported configuration needs no new productization programme.

Read the Architectural Reference for the field, connections and limits. Using FPF and its DPF Suites explains how to obtain supplying frameworks. Reading a Method supplies neither its required professional capabilities nor permission to perform restricted work.