The ROAMER Model organizes work into three stages—Before, During, and After. Each stage is designed not just to clarify processes, but to intentionally foster alignment, transparency, and shared understanding—especially in cross-functional and multi-stakeholder environments.
Overview of Stages
- Before: Lay the groundwork. Clarify why you’re doing the work, what success looks like, who benefits, and who should be engaged. Establish a common language and align all stakeholders on purpose and expectations from the start.
- During: Execute and iterate. Gather insights, include diverse perspectives, build collaboratively, test, and learn as you progress—ensuring transparency and active engagement throughout.
- After: Reflect, transition, and support. Review outcomes and processes as a group, capture lessons learned, and ensure a clean, well-documented delivery to the next owner or team for sustained alignment and success.
Quick Reference: Stages vs. Phases
| Stage | Phases |
|---|---|
| Before | Origin, Outcome, Persona |
| During | Retrieve, Observe, Analyze, Make, Evaluate |
| After | Review, Handoff |
Use this table to orient your team and choose the right level of depth and alignment for your work. Always favor phases that enable shared understanding and stakeholder engagement, even when streamlining.
When to Apply the ROAMER Model (Levels of Altitude)
The ROAMER Model is best used at the following levels of work (from broadest to most specific):
| Level | ROAMER Applicability | Altitude Example (Project Scale) |
|---|---|---|
| Vault | Rarely applicable | Entire business unit or context switch |
| Initiative | Useful | Multi-project strategy or large business goal |
| Project | Important | Time-bound body of work delivering key outcomes |
| Release | Critical | Versioned package or major delivery |
| Feature | Informative | Incremental value, usually for a defined persona |
| Component | Occasionally | Only relevant parts of ROAMER Model, if at all |
| Task | Rarely | Generally too granular for the full model |
- For a vault level, usually only applicable for new new businesses, major organizational transformation, or M&A activity, etc.
- For initiatives, projects, releases, and features, use the full ROAMER Model to maximize alignment and collaboration across teams.
- For tasks and components, use only what adds value—avoid unnecessary overhead.