Solution Architecture Practice

Comprehensive guide to software architecture frameworks, patterns, and best practices

View project on GitHub

Architecture Review Board (ARB)

Overview

The Architecture Review Board (ARB) is the governance body responsible for reviewing and approving significant architecture decisions across the organization. This ensures architectural alignment, quality, and consistency.

Purpose

The ARB exists to:

  • Review and approve major architecture decisions
  • Ensure alignment with enterprise architecture principles
  • Maintain architectural integrity across systems
  • Share knowledge and best practices
  • Identify and mitigate architectural risks
  • Foster collaboration and consistency

When ARB Review is Required

Mandatory Review

ARB review is required for:

  • ✅ New product or platform development
  • ✅ New technology adoption
  • ✅ Major architecture changes to existing systems
  • ✅ Projects with budget > $500,000
  • ✅ Integration with external systems
  • ✅ Cloud migration initiatives
  • ✅ Security-critical systems
  • ✅ Systems handling PII or sensitive data
  • ✅ Data platform initiatives
  • ✅ API platform decisions
  • ✅ Infrastructure platform changes

Optional Review

ARB review is recommended for:

  • Significant refactoring initiatives
  • Performance optimization programs
  • New design patterns adoption
  • Vendor selection decisions
  • Architecture experiments/POCs

Exempt from Review

ARB review is not required for:

  • Minor feature additions
  • Bug fixes
  • Internal component changes
  • Prototype/exploratory work (pre-commitment)
  • Changes within approved architecture

Note: When in doubt, consult with a Principal Architect.

ARB Composition

Core Members

Chair: Director of Solution Architecture

  • Facilitates meetings
  • Ensures process adherence
  • Final decision authority

Voting Members:

  • Principal Architect - Application Architecture
  • Principal Architect - Data & Analytics
  • Principal Architect - Infrastructure & Cloud
  • Principal Architect - Integration
  • Chief Information Security Officer (or delegate)
  • VP Engineering (or delegate)

Extended Members (As Needed)

  • Domain experts for specific topics
  • Security architects for security-critical reviews
  • Data architects for data-intensive systems
  • Compliance representatives for regulated systems
  • Enterprise architects for enterprise-wide initiatives

Non-Voting Participants

  • Presenting architects
  • Project stakeholders
  • Subject matter experts

ARB Process

1. Pre-Submission

Before submitting:

  1. Complete solution architecture design
  2. Create architecture documentation
  3. Document key decisions in ADRs
  4. Get peer review from another architect
  5. Ensure all required artifacts are ready

Checklist:

  • Solution architecture document
  • C4 diagrams (Context, Container, key Components)
  • Architecture Decision Records (ADRs)
  • Non-functional requirements (NFRs)
  • Security and compliance considerations
  • Risk assessment
  • Cost estimates
  • Timeline and milestones

2. Submission

How to Submit:

  1. Complete ARB Submission Template
  2. Email to arb@company.com with subject: “ARB Review Request: [Project Name]”
  3. Include all required artifacts
  4. Specify any urgency or constraints

Submission Deadline:

  • Submit by Friday 5pm for review the following week
  • Urgent requests may be accommodated with advance notice

What Happens Next:

  • ARB coordinator acknowledges receipt within 1 business day
  • Initial review for completeness
  • Scheduled for upcoming ARB meeting
  • Pre-read materials sent to ARB members 3 days before meeting

3. Pre-Review

ARB Members:

  • Review submission materials (pre-read)
  • Prepare questions and feedback
  • Identify concerns or risks
  • Consult with specialists if needed

Submitting Architect:

  • Available for clarifying questions
  • Prepare presentation (15-20 minutes)
  • Anticipate questions and concerns
  • Have backup slides ready

4. ARB Meeting

Meeting Format:

  • Duration: 60 minutes per submission
  • Frequency: Weekly (Wednesdays 2-4pm)
  • Location: Conference room / Virtual

Agenda:

  1. Presentation (15-20 min)
    • Business context and objectives
    • High-level architecture overview
    • Key technology decisions
    • Security and compliance
    • Risks and mitigation
  2. Q&A and Discussion (25-30 min)
    • ARB members ask questions
    • Discuss concerns and alternatives
    • Explore trade-offs
    • Identify risks
  3. Decision (10-15 min)
    • ARB deliberates (presenters may be excused)
    • Votes on approval
    • Communicate decision and conditions

Possible Outcomes:

  • Approved: Architecture is approved as-is
  • Approved with Conditions: Approved with specific requirements to address
  • Approved with Recommendations: Approved, with non-blocking suggestions
  • Deferred: Needs more work, resubmit when ready
  • Rejected: Fundamental issues, significant rework needed

5. Post-Review

Within 2 business days:

  • ARB decision documented and sent to submitter
  • Feedback and action items documented
  • Conditions clearly specified (if any)
  • Follow-up scheduled if needed

Submitting Architect:

  • Address any conditions
  • Update architecture documentation
  • Communicate decision to stakeholders
  • Proceed with implementation (if approved)

For Conditional Approvals:

  • Address conditions
  • Provide evidence of completion
  • May require follow-up review or email confirmation

Review Criteria

Architecture Quality

Alignment:

  • Aligns with architecture principles
  • Consistent with enterprise architecture
  • Follows approved patterns and standards
  • Supports strategic objectives

Technical Excellence:

  • Sound technical design
  • Appropriate technology choices
  • Scalability and performance
  • Resilience and reliability
  • Maintainability

Security & Compliance:

  • Security by design
  • Appropriate security controls
  • Compliance requirements met
  • Data privacy considerations
  • Threat model documented

Integration:

  • Integration approach sound
  • API design appropriate
  • Data flows clear
  • Dependencies identified

Business Value

Alignment:

  • Supports business objectives
  • Clear value proposition
  • Appropriate for problem scope
  • ROI justified

Risk:

  • Risks identified and assessed
  • Mitigation strategies defined
  • Dependencies managed
  • Contingency plans

Feasibility:

  • Timeline realistic
  • Team has required skills
  • Resources available
  • Technology mature enough

ARB Best Practices

For Submitters

Do’s ✅:

  • Submit early if possible
  • Complete all required artifacts
  • Get peer review first
  • Be prepared for questions
  • Listen to feedback openly
  • Document decisions in ADRs
  • Focus on key decisions, not every detail

Don’ts ❌:

  • Don’t submit incomplete materials
  • Don’t be defensive about feedback
  • Don’t hide risks or challenges
  • Don’t over-present (stay within time)
  • Don’t assume approval
  • Don’t skip peer review

For ARB Members

Do’s ✅:

  • Review materials before meeting
  • Ask clarifying questions
  • Focus on architecture, not implementation details
  • Be constructive with feedback
  • Consider context and constraints
  • Share relevant experience
  • Vote based on criteria, not preference

Don’ts ❌:

  • Don’t nitpick minor details
  • Don’t push personal preferences
  • Don’t assume one-size-fits-all
  • Don’t forget business context
  • Don’t make it personal

Escalation

If you disagree with an ARB decision:

  1. Discuss with ARB Chair: Understand the reasoning
  2. Provide Additional Information: If new information changes the picture
  3. Appeal: Formal appeal to VP Engineering and CTO
  4. Exception Process: Request exception through Exception Management

ARB Metrics

We track ARB effectiveness:

  • Average cycle time (submission to decision)
  • Approval rate
  • Conditional approval rate
  • Resubmission rate
  • Stakeholder satisfaction
  • Project outcomes (post-implementation)

Targets:

  • Cycle time < 2 weeks
  • First-time approval rate > 60%
  • Satisfaction score > 4.0/5.0

ARB Schedule & Logistics

Regular Meetings:

  • When: Wednesdays, 2-4pm
  • Where: Executive Conference Room / Zoom
  • Capacity: 2 submissions per meeting

Holiday/Blackout Periods:

  • Check ARB calendar for exceptions
  • No meetings during major holidays
  • Summer and winter breaks may have reduced schedule

Emergency Reviews:

  • Can be scheduled outside regular cadence
  • Requires approval from ARB Chair
  • Must be truly urgent (production issue, regulatory deadline, etc.)

ARB Calendar

View the ARB Calendar for:

  • Upcoming meetings
  • Submission deadlines
  • Holiday blackouts
  • Available slots

Resources

Templates

Examples

Support

  • Email: arb@company.com
  • Slack: #architecture-arb
  • Office Hours: Daily architecture office hours
  • ARB Coordinator: [Name] - arb-coordinator@company.com

FAQs

Q: How long does the ARB process take?
A: Typically 1-2 weeks from submission to decision.

Q: Can I present remotely?
A: Yes, remote presentation is supported via Zoom.

Q: What if I can’t make the scheduled meeting?
A: Contact ARB coordinator to reschedule.

Q: Can I bring stakeholders to the ARB meeting?
A: Yes, but please notify ARB coordinator in advance.

Q: What if my architecture changes after approval?
A: Minor changes are ok. Significant changes require re-review.

Q: Do I need ARB approval for a POC?
A: Not for exploratory POCs. Yes if committing to the technology.

Q: Can I get early feedback before formal submission?
A: Yes! Bring to architecture office hours or request informal review.

Back to Processes Home