AMIGO Wiki
AI Managed Implementation Governance Office - Documentation
Introduction
Key Relationship
Important Field Dependencies
Object | Usage Notes | Visibility | Filter & Search Criteria -- | -- | -- | -- Hyperlink to Portfolio | Parent | | Hyperlink to Project | Child | | | | |Key Decision Dashboard
Open By Organization
Open By Portfolio
Open By Program
Open By Project
Open By Object
Open By Responsible
💼 Business Usage
PMO Application
Key Decisions provide a formal audit trail of critical choices made during program execution. This ensures accountability, enables retrospective analysis, and supports governance compliance by documenting who made decisions, when, and the rationale behind them.
Common Use Cases
| Use Case | Description |
|---|---|
| Architecture Decisions | Document technology stack choices and design patterns |
| Vendor Selection | Record evaluation criteria and selection rationale |
| Scope Changes | Document decisions to add/remove features |
| Resource Allocation | Track staffing and budget allocation decisions |
| Go/No-Go Decisions | Document gate review outcomes |
| Risk Responses | Record chosen mitigation strategies |
Decision Categories
- Strategic: Long-term direction impacting multiple workstreams
- Tactical: Short-term choices within a single project
- Technical: Architecture, tools, and technology decisions
- Operational: Process and workflow decisions
📚 References
- Governance - Governance overview
- Operational Readiness - Cutover decisions
- Meeting Minutes - Decision capture in meetings
- Change Request Log - Formal change decisions