SYSE.8:1 - Problem Frame

Many engineered results are usable only through an arrangement that continues beyond transfer of a product. For example, software needs operating infrastructure and change capability; a machine may need consumables, calibration, maintenance, logistics, data, trained operators, or financing; and a promised condition such as temperature, availability, or stock level needs Systems that can observe and restore it. Changing the commercial or access relation can also change the technical architecture and the allocation of risks—for example, variability, failure, asset, or update risk.

Product-only engineering leaves those changes to later improvisation. Service-first rhetoric creates the opposite failure: every object and Work occurrence is bundled under one broad word, and the project assumes that renaming the offer creates a desired effect—for example, demand, recurring revenue, sustainability, or provider capability.