Intentional - Strategy
Learn more about Well-Architected Easy → Intentional → Strategy → Governance
| Where to look? Product Area | Location | What does good look like? Pattern |
|---|---|
| Platform | Business | ✅ Team members know who's responsible for what throughout app lifecycle |
| Platform | Business | ✅ Teams and projects only use AI models approved for business uses |
| Platform | Business | ✅ Hot-fixes have a clear path to production |
| Platform | Business | ✅ Users can easily report bugs and request features |
| Platform | Business | ✅ The prioritization process for work items is documented and transparent to all stakeholders |
| Platform | Business | ✅ Environment strategy is clearly documented and development environments match the documentation |
| Platform | Business | ✅ Production support processes are clear |
| Platform | Business | ✅ Release planning is predictable and transparent to all delivery team members |
| Platform | Business | ✅ Releases are clear to users and delivery/maintenance teams |
Learn more about Well-Architected Easy → Intentional → Strategy → Prioritization
| Where to look? Product Area | Location | What does good look like? Pattern |
|---|---|
| Platform | Company | ✅ Implementation and maintenance costs have been identified for all KPIs |
| Platform | Company | ✅ Requests for features are prioritized based on business impact, amount of new work required to deliver, and amount of work required to maintain |
| Platform | Documentation | ✅ Roadmaps show that automations are prioritized based on business value |
| Platform | Documentation | ✅ All new work items have clear business value metrics (for example, revenue increases, cost savings from process optimizations, and so on) |
Learn more about Well-Architected Easy → Intentional → Strategy → Roadmapping
| Where to look? Product Area | Location | What does good look like? Pattern |
|---|---|
| Platform | Business | ✅ Delivery teams know how to evaluate backlog items against longer term priorities |
| Platform | Business | ✅ Teams know who's doing what and how to manage dependencies |
| Platform | Business | ✅ Stakeholders understand the "why" of work items |
| Platform | Business | ✅ Work is intentional, even when priorities have to change quickly |
| Platform | Roadmap | ✅ Show prerequisites and dependencies |
| Platform | Roadmap | ✅ Communicate information that's tailored to your audience (business or technical) |
| Platform | Roadmap | ✅ Communicate information at the correct level of detail |
| Platform | Roadmap | ✅ Show start and end dates |
Learn more about Well-Architected Easy → Intentional → Strategy → Governance
| Where to look? Product Area | Location | What to avoid? Anti-Pattern |
|---|---|
| Platform | Business | ⚠️ Teams do not know who is responsible for what |
| Platform | Business | ⚠️ Teams select AI models ad hoc |
| Platform | Business | ⚠️ Work items have no clear prioritization |
| Platform | Business | ⚠️ Environments are provisioned ad hoc and may not be refreshed predictably; developers often do not have the environments and access they need |
| Platform | Business | ⚠️ Documentation is not easily accessible |
| Platform | Business | ⚠️ Your backlog has become an "idea bank" that is stale and stagnant |
| Platform | Business | ⚠️ Releases are unpredictable for delivery teams and users |
| Platform | Business | ⚠️ Governance bodies act as a help desk that troubleshoots support requests |
| Platform | Business | ⚠️ Hot-fixes are addressed ad hoc |
| Platform | Business | ⚠️ Bug reports and feature requests are ad hoc |
Learn more about Well-Architected Easy → Intentional → Strategy → Prioritization
| Where to look? Product Area | Location | What to avoid? Anti-Pattern |
|---|---|
| Platform | Company | ⚠️ Costs associated with implementing and maintaining automations are unclear |
| Platform | Company | ⚠️ Requests are delivered on an ad hoc or first-in/first-out basis |
| Platform | Documentation | ⚠️ Roadmaps don't exist |
| Platform | Documentation | ⚠️ Business value associated with work is unclear or nonexistent |
Learn more about Well-Architected Easy → Intentional → Strategy → Roadmapping
| Where to look? Product Area | Location | What to avoid? Anti-Pattern |
|---|---|
| Platform | Business | ⚠️ Stakeholders often feel frustrated and confused about what's being done and are usure when new capabilities will be delivered |
| Platform | Business | ⚠️ Work is pulled from whatever is in the backlog and there is no clear "why" |
| Platform | Business | ⚠️ Teams have trouble coordinating interdependent work and often replicate work without realizing it |
| Platform | Business | ⚠️ Work is often reactive |
| Platform | Roadmap | ⚠️ Are used as project kickoff materials and not artifacts for delivery |
| Platform | Roadmap | ⚠️ Do not help align stakeholders and delivery teams |
| Platform | Roadmap | ⚠️ Contain information that isn't tailored to their audience (for example, business capabilities and systems within the same roadmap) |
| Platform | Roadmap | ⚠️ Mix levels of detail (for example, by including systems and components within the same roadmap) |