Project development workflow
From intended use to comparison samples and project records
A sourcing team can begin with a shared description instead of inferring capability from a label or an image.
Which intended-use details belong in the first development discussion?
Record the use setting, reference sample, package direction and conditions that need observation in the first discussion.
- Use objective
- Reference sample
- Observable conditions
How can every sample comparison stay on the same basis?
Identify each sample with its configuration and observation criteria so differences can be discussed against the same baseline.
- Sample identity
- Configuration
- Comparison notes
Which documentation needs should be recorded with the project?
Questions about packaging, the dispensing system and verification needs belong in the project record so later reviews share the same context.
- System choices
- Verification needs
- Project record