wip

docs/administrative/nais-system/initiatives.md

@@ -12,7 +12,11 @@ These are the key components of an initiative:
 
 ### Essence
 
-It describes essence, i.e. what is the core idea and purpose of the initiative. 
+The essence should describe is the core idea and purpose of the initiative.
+
+This should be clear and concise. This ensures that you have solid understanding of the problem, and help the working group make scoping decisions along the way.
+
+
 
 - especially important if you're not part of the working group
 - makes it easier to make scoping descisions along the way
@@ -55,14 +59,9 @@ Having worked through this, we can also see if we are introducing or removing an
 
 Being able to understand the technical and/or human impact is crucial when evaluating the initiative.
 
-3. Skissere mulig løsning
-
-> Finne en grov, men gjennomtenkt, løsning på problemet innenfor rammene man definerte i forrige steg.
+Depending on how clear your understanding of the problem is, this can be a chaotic process where many ideas are thrown around and you find yourself exploring many alternative solutions, refining the essence, and the investment as you go along.
 
-Den virkelige jobben er å kartlegge ulike måter man kan løse problemet på.
-Hvilke systemer er involvert?
-Hvilke muligheter finnes for løsning?
-Hva bør man unngå å gjøre?
+To make sure you understand the different 
 
 Her kan det være lurt å involvere de som har kjennskap/eierskap fra før for å få med historikken og deres perspektiver.
 Man kan eventuelt bruke nais-tech, github issue eller noe liknende.