How outcomes and constraints realise a board-level goal The Goal realisation viewpoint refines one high-level goal into concrete sub-goals, then separates outcomes that realise a sub-goal by achieving it from the principle and requirement that only influence how it is pursued: conflating the two is the common motivation-layer error.
How outcomes and constraints realise a board-level goal
A top-down realisation tree for the ArchiMate Goal realisation viewpoint, from the ArchiMate 3.2 Specification by The Open Group. The goal Decarbonise the distribution network sits in an accent panel at the top of the tree. Two solid accent arrows labelled realises rise into it from the sub-goals Connect low carbon demand quickly and Cut network losses and emissions. Beneath, four motivation panels point up at the sub-goals: the outcomes 500 MW connected and Losses reduced use solid realises arrows, while the principle Flexibility first and the requirement Annual loss report use dashed influences arrows. A legend names the element tints and both relationships.
Decarbonise the distribution network Board-level statement of intent Connect low carbon demand quickly Heat pumps, EV charging, new homes Cut network losses and emissions Own estate and technical losses 500 MW connected New low carbon demand Outcome, measured Flexibility first Use flex before copper Principle, guiding Annual loss report Losses tracked Requirement, binding Losses reduced Down 10% by 2030 Outcome, measured realises
realises
influences
influences
realises Goal or sub-goal Outcome Principle or requirement realises influences Derived from the ArchiMate 3.2 Specification, The Open Group
