How we change what others think, feel, believe and do

| Menu | Quick | Books | Share | Search | Settings |



Disciplines > Change ManagementThe 4D Change Project Framework > Documents > Requirements

Description | Template | See also



The Requirements document in a change project indicates the need that must be addressed, the outcomes that should be achieved and some indication of what this looks like.

Requirements are a key output of the Discovery phase.

Change projects fail when people come out of the woodwork with requirements that have not been previously considered. This document should thus include interests of all stakeholders and should identify the outcomes even for people who are targets of change.

Positive, desired outcomes are often called 'benefits'. Negative outcomes that are not desired by the people affected are sometimes called 'disbenefits' and are typical sources of resistance to change. Outcomes that are neither desired nor not-desired are just outcomes.

Change project vary greatly in what they deliver, and particularly where the deliverable is specified by key stakeholders then this may be detailed here.

It is important here also to identify the boundaries of the project in the overall scoping. This, along with other information here, allows the project to be realistically planned. Getting the scope right can be tricky and will require careful questioning of stakeholders, who often have a vague need but find it difficult to put a boundary on this. This can lead to an 'I'll know it when I see it' attitude that is almost impossible to satisfy. Time up front to bound requirements thus is often very important.




The background sets the project in context, with brief detail of how the project came about.


This section describes customer and other interested parties and what they seek. This includes people who are targets of change and those who may be obliquely affected. From this initial analysis issues of resistance to change may be derived.


Stakeholder Interest Notes



Outcomes are what happens as a result of the project (do not confuse them with deliverables). Some outcomes are desired by the stakeholder (benefits) whilst others are not desired by them (but may well be desired by other stakeholders).


Stakeholder Outcome Notes



The requirement may also specify individual deliverables that are required, which may range from physical changes to education.

Deliverables achieve outcomes, and it may be useful to link these here.


Stakeholder Deliverable Notes



Specified deliverable are provided to key stakeholders. There may well be measures or other criteria which may be applied to determine whether these are acceptable.

Criteria may include such as timescales for delivery, physical quality measures and satisfaction ratings.


Deliverable Acceptance Criteria



The scope defines the boundary of project action and capture what key stakeholders want to be included and what they do not want to be included.


What's in What's out



This lists factors that limit what may be done in the Discovery phase, such as timescales, secrecy, standards and regulations that must be followed, etc.


Constraint Note



This section offer non-mandatory suggestions that will help the Discovery phase to be successful, for example notes around organizational politics.


Depending on the project, there may be limited or very significant detail available about what is required. As appropriate, requirements may broken down from the summary above into further detail.


See also


Site Menu

| Home | Top | Quick Links | Settings |

Main sections: | Disciplines | Techniques | Principles | Explanations | Theories |

Other sections: | Blog! | Quotes | Guest articles | Analysis | Books | Help |

More pages: | Contact | Caveat | About | Students | Webmasters | Awards | Guestbook | Feedback | Sitemap | Changes |

Settings: | Computer layout | Mobile layout | Small font | Medium font | Large font | Translate |



Please help and share:


Quick links


* Argument
* Brand management
* Change Management
* Coaching
* Communication
* Counseling
* Game Design
* Human Resources
* Job-finding
* Leadership
* Marketing
* Politics
* Propaganda
* Rhetoric
* Negotiation
* Psychoanalysis
* Sales
* Sociology
* Storytelling
* Teaching
* Warfare
* Workplace design


* Assertiveness
* Body language
* Change techniques
* Closing techniques
* Conversation
* Confidence tricks
* Conversion
* Creative techniques
* General techniques
* Happiness
* Hypnotism
* Interrogation
* Language
* Listening
* Negotiation tactics
* Objection handling
* Propaganda
* Problem-solving
* Public speaking
* Questioning
* Using repetition
* Resisting persuasion
* Self-development
* Sequential requests
* Storytelling
* Stress Management
* Tipping
* Using humor
* Willpower


+ Principles


* Behaviors
* Beliefs
* Brain stuff
* Conditioning
* Coping Mechanisms
* Critical Theory
* Culture
* Decisions
* Emotions
* Evolution
* Gender
* Games
* Groups
* Habit
* Identity
* Learning
* Meaning
* Memory
* Motivation
* Models
* Needs
* Personality
* Power
* Preferences
* Research
* Relationships
* SIFT Model
* Social Research
* Stress
* Trust
* Values


* Alphabetic list
* Theory types


Guest Articles


| Home | Top | Menu | Quick Links |

© Changing Works 2002-
Massive Content — Maximum Speed