What do you do on the team?
Choose the closest role. Open only the guidance you need.
EngineerKeep the definition connected
A simple daily routine
- Read your assigned requirements and recent changes.
- Check source, acceptance criteria and assumptions.
- Update design allocations and interface descriptions.
- Link affected verification cases and discuss gaps.
- Leave a clear next action for the receiving owner.
Before you hand work over
- Current requirement and design revisions
- Source and rationale for important choices
- Interface fields, units and timing
- Open questions and named owners
Two useful things to know
- A requirement describes required behavior; a function describes what the system does.
- An interface needs agreed interpretation at both ends.
Explain TRAIN-REQ-001 to a teammate without using its quality score as a substitute for the statement.
Helpful lessons
Assurance and verificationMake conclusions inspectable
A simple daily routine
- Review changed requirements and affected checks.
- Confirm measurable criteria and test conditions.
- Plan the method, procedure and evidence capture.
- Record observations before choosing an outcome.
- Review missing evidence and communicate the disposition.
Before you hand work over
- Requirement revision and case ID
- Procedure and test conditions
- Measured values with units
- Accessible evidence and unresolved findings
Two useful things to know
- A planned case, recorded result and supporting evidence are different records.
- A result must be assessed against the criterion and revision actually tested.
Explain why 3.2 seconds meets the original five-second criterion but fails the revised two-second criterion.
Helpful lessons
Project or discipline leadMake decisions and ownership clear
A simple daily routine
- Review actions and unresolved decisions.
- Ask for the source behind important summaries.
- Compare alternatives and affected work.
- Record a reasoned disposition with owners.
- Check that agreed follow-up work has happened.
Before you hand work over
- Decision and change dispositions
- Affected records and delivery dependencies
- Actual artifacts ready for the recipient
- Open actions with owners and review dates
Two useful things to know
- A recommendation proposes action; a decision records its disposition and rationale.
- A change can affect cost, schedule, design and verification together.
Review TRAIN-CR-001 and request the evidence needed before committing to its shorter update target.
Helpful lessons
Operations and receiving teamConnect observations to project knowledge
A simple daily routine
- Check the state and provenance of incoming information.
- Compare observations with agreed operating expectations.
- Record unexpected behavior as a linked issue.
- Discuss affected risks, assumptions and decisions.
- Capture a lesson with the conditions that made it useful.
Before you hand work over
- Intended behavior and known limitations
- Current interface and freshness rules
- Evidence and open operating questions
- Named route for raising issues or changes
Two useful things to know
- A sensor definition is not a live reading.
- A usable observation needs source, time, units, quality and context.
Decide whether an SOC value is current using its source timestamp, not merely the time it appeared on screen.
Helpful lessons
Roles suggest a starting point. You can use any lesson or search for the task you need.