Target-state concept
A target-state concept describes the intended future process or system through tasks, rules and checkable expectations.
Describe the intended way of working
A target-state concept records how a defined area should work in the future. It includes tasks, responsibilities, data and rules, as well as expected outcomes. In a fictional example, each service request should belong to exactly one responsible team; unclear requests enter a defined clarification step.
The intended rule must remain understandable during cover arrangements and exceptions. Describe how compliance will be checked and which assumptions remain unresolved. A target-state concept is not finished code or evidence that the intended state has been achieved. It provides a shared basis for implementation and later checking.
Sources
Related terms
- Current-state analysisCurrent-state analysis examines how processes and systems actually work today, including exceptions and unresolved questions.
- Requirements catalogueA requirements catalogue organises requirements with identifiers and verifiable details. It helps track scope, unresolved questions and changes.
- Acceptance criteriaAcceptance criteria state verifiable outcomes used to assess whether a requirement meets its intended need.
- Exit strategyA prepared route to switch, take over or retire an IT service in an orderly way.
- Migration costsEffort and expenditure for the planned move of data or functions to another environment.
- Investment costsCosts of building a new or expanded IT capability, as considered in project planning.
Articles on this topic
IT Consulting & Strategy with ASES
Strategy, architecture and technology choice