Solution Architecture Practice

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

View project on GitHub

New Architect Onboarding

Welcome to the Solution Architecture Practice!

This 90-day onboarding plan will help you integrate into the team, learn our practices, and start contributing effectively as a solution architect.

Onboarding Overview

Your First 90 Days

  • Days 1-30: Foundation & Learning
  • Days 31-60: Practice & Contribution
  • Days 61-90: Integration & Leadership

Onboarding Buddy

You’ll be paired with an experienced architect who will:

  • Answer questions
  • Provide guidance
  • Review your work
  • Help you navigate the organization

Onboarding Checklist

Track your progress using the Onboarding Checklist.


Week 1: Getting Started

Day 1: Welcome & Setup

Morning:

  • ✅ Meet with Director of Solution Architecture
  • ✅ Meet your onboarding buddy
  • ✅ Review this onboarding plan
  • ✅ HR and administrative setup

Afternoon:

  • ✅ Set up development environment
  • ✅ Complete Tools & Access Setup
  • ✅ Join Slack channels: #architecture, #architecture-reviews, #architecture-patterns
  • ✅ Set up 1-on-1s with team members

Reading:

Day 2-3: Understanding the Practice

Activities:

  • ✅ Meet with each Principal Architect (1 hour each)
  • ✅ Attend daily architecture office hours (observer)
  • ✅ Review org chart and team structure

Reading:

Deliverable:

  • Write a summary of your understanding of the practice (1 page)

Day 4-5: Frameworks & Methodologies

Activities:

  • ✅ Complete C4 Model tutorial
  • ✅ Review existing architecture documentation
  • ✅ Practice creating simple C4 diagrams

Reading:

Deliverable:

  • Create C4 diagrams for a simple system (e.g., personal project)

Week 2: Deep Dive into Processes

Monday-Tuesday: Architecture Review Process

Activities:

  • ✅ Shadow an Architecture Review Board (ARB) meeting
  • ✅ Review recent ARB submissions and feedback
  • ✅ Understand quality gates and criteria

Reading:

Wednesday-Thursday: Decision Making

Activities:

  • ✅ Review 10 existing ADRs
  • ✅ Understand decision-making framework
  • ✅ Practice writing an ADR for a past decision

Reading:

Deliverable:

  • Write practice ADR using template

Friday: Governance & Standards

Activities:

  • ✅ Review architecture standards
  • ✅ Understand technology radar
  • ✅ Learn exception management process

Reading:


Week 3-4: Technical Deep Dive

Week 3: Architecture Patterns

Daily Activities:

  • ✅ Study one pattern category per day
  • ✅ Review reference architectures
  • ✅ Discuss patterns with your buddy
  • ✅ Attend Architecture Council meeting

Reading:

Deliverable:

  • Present one pattern to the team (15 min tech talk)

Week 4: Reference Architectures

Activities:

  • ✅ Study each reference architecture
  • ✅ Understand when to use each
  • ✅ Review real implementations
  • ✅ Shadow architecture consultation

Reading:

Deliverable:

  • Document learnings from shadowing (2 pages)

Days 31-45: First Real Engagement

Getting Your First Project

Week 5:

  • ✅ Assigned to first project (with buddy support)
  • ✅ Attend project kickoff
  • ✅ Understand business context and requirements
  • ✅ Meet with stakeholders

Activities:

  • Initial discovery and requirements gathering
  • Create system context diagram
  • Draft high-level architecture
  • Weekly check-ins with buddy

Week 6-7:

  • ✅ Develop detailed solution architecture
  • ✅ Create architecture documentation
  • ✅ Write ADRs for key decisions
  • ✅ Get peer review from buddy

Deliverables:

  • Solution architecture document
  • C4 diagrams (Context, Container, key Components)
  • 3-5 ADRs
  • Present to buddy for feedback

Days 46-60: Review & Presentation

Week 8: ARB Preparation

Activities:

  • ✅ Prepare ARB submission
  • ✅ Practice presentation with buddy
  • ✅ Address feedback and refine
  • ✅ Submit for ARB review

Support:

  • Buddy reviews submission
  • Dry run with friendly architect audience
  • Principal architect guidance

Week 9: ARB Presentation

Activities:

  • ✅ Present to Architecture Review Board
  • ✅ Respond to questions and feedback
  • ✅ Refine based on ARB feedback
  • ✅ Get approval

Reflection:

  • What went well?
  • What was challenging?
  • What did you learn?
  • What would you do differently?

Days 61-75: Expanding Contribution

Week 10-11: Broadening Exposure

Activities:

  • ✅ Participate in architecture office hours (as answerer)
  • ✅ Review another architect’s design
  • ✅ Contribute to pattern library
  • ✅ Join a working group or guild

Deliverables:

  • Provide peer review on 2 designs
  • Contribute 1 pattern or update to knowledge base
  • Support 3 office hours sessions

Knowledge Sharing

Activities:

  • ✅ Give a tech talk on a topic of expertise (30-45 min)
  • ✅ Write a blog post or article
  • ✅ Present at Architecture Council
  • ✅ Mentor an engineer on architecture

Topics (choose one):

  • Technology you’re expert in
  • Lesson learned from recent project
  • Deep dive on architecture pattern
  • Industry trend or emerging technology

Days 76-90: Integration & Independence

Week 12: Leading

Activities:

  • ✅ Lead an architecture review (with Principal oversight)
  • ✅ Take on second project independently
  • ✅ Mentor new team member or intern
  • ✅ Contribute to practice improvement initiative

Week 13: Reflection & Planning

Activities:

  • ✅ 90-day review with Director
  • ✅ Peer feedback session
  • ✅ Self-assessment against capability matrix
  • ✅ Create development plan for next 6 months

Reflection Questions:

  • How do you feel about your integration into the team?
  • What are your strengths as an architect?
  • Where do you want to grow?
  • What support do you need?

Deliverables:

  • Self-assessment document
  • 6-month development plan
  • Areas of expertise and interest

Onboarding Success Criteria

By the end of 90 days, you should be able to:

Technical Competence

  • ✅ Create comprehensive architecture documentation
  • ✅ Apply appropriate architecture patterns
  • ✅ Make and document architecture decisions
  • ✅ Present and defend architectural choices
  • ✅ Review others’ architectures constructively

Process Fluency

  • ✅ Navigate the engagement model
  • ✅ Prepare and present ARB submissions
  • ✅ Follow documentation standards
  • ✅ Use templates and tools effectively
  • ✅ Apply governance appropriately

Collaboration

  • ✅ Build relationships across teams
  • ✅ Communicate effectively with stakeholders
  • ✅ Work collaboratively with peer architects
  • ✅ Contribute to practice community
  • ✅ Support and mentor others

Practice Integration

  • ✅ Understand practice mission and values
  • ✅ Participate in practice activities
  • ✅ Contribute to knowledge sharing
  • ✅ Represent practice professionally
  • ✅ Demonstrate practice values

Resources for Onboarding

Documentation

  • All sections of this documentation site
  • Project templates and examples
  • Past ARB submissions
  • Architecture pattern library

People

  • Your onboarding buddy
  • Principal Architects
  • Director of Solution Architecture
  • Peer architects in your domain

Tools

  • Slack channels
  • Office hours
  • Architecture Council meetings
  • Study groups
  • Mentorship program

Training


Weekly Check-ins

With Your Buddy

Frequency: Weekly, 30 minutes
Topics:

  • Progress update
  • Questions and challenges
  • Review work products
  • Guidance on next steps

With Director

Week 1: Welcome and expectations
Week 4: Progress check-in
Week 8: Mid-point review
Week 13: 90-day review and goal setting

Self-Reflection

Weekly:

  • What did I learn this week?
  • What went well?
  • What was challenging?
  • What do I need help with?
  • What are my goals for next week?

Tips for Success

Do’s ✅

  • Ask Questions: No question is too basic
  • Be Curious: Dive deep into how things work
  • Seek Feedback: Regularly ask for feedback
  • Build Relationships: Get to know the team
  • Contribute Early: Share your perspective
  • Take Notes: Document your learnings
  • Be Patient: Learning takes time

Don’ts ❌

  • Don’t Suffer in Silence: Speak up if struggling
  • Don’t Skip Reading: Foundation is important
  • Don’t Go Alone: Leverage your buddy and team
  • Don’t Rush: Quality over speed
  • Don’t Be Afraid to Say “I Don’t Know”: It’s expected

After 90 Days

Ongoing Development

Career Growth

  • Regular 1-on-1s with manager
  • Quarterly goal setting
  • Annual performance reviews
  • Career development planning

Giving Back

  • Onboard future new hires
  • Contribute to practice improvement
  • Share knowledge through talks and writing
  • Mentor junior architects and engineers

Questions?

Your Onboarding Buddy: [Name]
Director of Solution Architecture: [Name]
Practice Email: solution-architecture@company.com
Slack: #architecture-onboarding

We’re excited to have you on the team!


Back to Training Home