Their own process · The requirements · Element
What it asks of you
The demand the requirement makes on the supplier — and where in your own business that demand has to be met.
The part
What it is
A requirement binds the customer, and in binding them it asks something of everyone who wants to serve them. A demand for a documentation format asks for documentation in that format, produced by someone, published somewhere, findable at the phase where it is needed. Recording only the obligation and not what it asks is why suppliers discover the demand at the point of losing to it.
The field that does the work is where the answer lives. A requirement is recorded here, in the Market Core, but what it asks of you almost never belongs here: the ability to produce it is a competence, the material itself is content, finding it is an experience question, and whether anyone uses it is a measurement. Pointing each demand at its own home is how a customer’s process becomes visible as pressure on your own business rather than as a note in a sales file.
The honest states are four: you have it, you partly have it, you do not, or nobody has checked. The fourth is the most common and the least often written down.
The smallest level
The attributes it carries
Each attribute is one of the framework’s shared types. What a date is, and how it is written, is defined once for the whole model — the note here says what it means in this particular place.
Answered at
Where in your own framework the demand has to be met — a competence, a piece of content, an experience, a measure.
Reference shared type
The other elements in the requirements
The obligation
What has to be satisfied, stated as the requirement states it.
LearnWho imposes it
Where the obligation comes from, which decides whether it can be argued with at all.
LearnWhen it is settled
The phase at which the requirement becomes fixed, after which arriving with an alternative is too late.
Learn