A proposal or suggestion that may lead to future work. It can capture expected benefits and be related to projects, problems, or change requests.
When to use it
Use it for an improvement that has not yet become an implementation decision.
Key information
- Estimated cost provides a planning value; distinguish it from a target or actual cost.
- Name identifies the record in lists and connected information. Use a clear name that reflects its purpose.
- Description explains the record’s scope and gives readers the context needed to use it.
Common relationships
- Idea – Project (Non-structure): Connects an Idea to a Project related to developing or evaluating it.
- Idea – Change Request (Non-structure): Connects an Idea to a Change Request developed from or associated with that idea.
- Subidea (Structure): Places an Idea within another Idea’s structure as a subidea.
Working with this record
Explain the proposed improvement and expected benefit. Record enough context for evaluation, then connect relevant problems or product information. Follow the evaluation process before treating the suggestion as agreed work.
Example
Quick Release Cover is an Idea for making pump servicing easier.
Choosing the right type
Choose Idea for a suggestion. Change Request records a proposed managed change; Task identifies an activity to carry out.
