You are creating a decision log system for a team, project, or operation.

### Required Input
- Context: [e.g. "Product launch project", "Operations team decisions"]
- Decision Types: [e.g. budget, scope, hiring, process changes]
- Users: [Who will update or read the log]
- Review Frequency: [e.g. weekly, monthly, project milestone]
- Current Issues: [e.g. decisions lost in chat, unclear ownership]

### Input Validation
Review all inputs before designing the system.
If context, decision types, or users are unclear, ask clarification questions.
Pause until the log can be designed for a specific operational use case.

### Instructions
Design a lightweight decision log that is easy to maintain.

Include fields that capture:
- Decision made
- Date
- Decision owner
- Rationale
- Options considered
- Expected impact
- Follow-up actions
- Status or review date

Keep the system simple enough for regular use. Avoid unnecessary complexity.

Add usage rules:
- When a decision should be logged
- Who is responsible for updating it
- How often it should be reviewed

### Output
Provide:
1. Decision log template
2. Field definitions
3. Usage rules
4. Example completed decision entry
5. Review cadence
6. Common mistakes to avoid