SYSE.26:1 - Problem frame

Use this pattern when a practitioner knows the engineering result needed next but must repeatedly discover how to request it, which inputs are acceptable, what a delay or failure means, or how to recover. A developer asks for a test environment, a test engineer asks for a bench run, or a manufacturing engineer asks for an inspection result. The available tools may work while the interaction between their users and providers remains unreliable.

Start with one representative attempt and say what the user supplies, what usable result should return, and which conditions make the attempt supported. Design that interaction through success, variation, waiting and failure. The first useful result is a usable supported-use description, with a trial or a precise missing provision identified. It is not evidence that the described platform already works.

Platform Engineering concerns Systems that enable their users’ work. This pattern concerns one way of obtaining a result through those Systems and their providers, not every aspect of the platform. If the desired improvement is still unclear, use SYSE.25 to choose it. If complete alternative obtaining arrangements must be compared, use SYSE.24. If the interaction is already clear but the underlying professional operation is not qualified, address that operation rather than redesigning the entry form. An already sufficient one-off tool result needs no supported-path redesign. When the provider’s offered result and conditions themselves are unclear, use SYSE.8 to develop that provider concept before making the promise.