Content

Note

This is a facilitated group discussion I ran for a local Technical Architect meetup. It was meant to get a conversation going about what it means to be an architect and provide an opportunity for those not in the role yet to converse with those already in a architecture role about what it takes to succeed.

So You Want to Be an Architect

So You Want to Be an Architect

Intention

  • Find out what does 'architect' mean to us

  • What does our current meetup group composition look like

  • Share in our experience to help guide aspiring attendees or connect on problems we're trying to solve currently

  • Raise your hand if:

    • Currently hold a title with the word 'architect' in it
    • You currently work as a person who is looked to for architectural guidance
    • You have taken on an architect role before (title not important)

We are going to do "Around the World"...

  • You will be assigned into small groups
    • You will get markers and sticky notes
    • You will be stationed at a question that the group will discuss for 3 minutes (I will track time and let you know)
    • Place a sticky note or 2 on the question that best represents highlights in your discussion
    • Move to the next question, repeat

You may not get to all the questions

  • I think an architect is...

  • I think an architect title means...

  • I think an architect makes a difference by....

  • I think the future of technical architecture will likely involve...

  • I think at their worst an architect is...

  • I think a challenge architects often face is...

  • My company's view of an architect is...

  • Advice I would give to an aspiring architect is...

  • One misconception about architects is...

  • A lesson I learned from a mistake in my architecture career was...

Conclusion

  • Move between each question, "What did we learn?"

References

  • 6:00 - 6:20 Socialize (20 minutes)

  • 6:20 - 6:25 Society’s intent and operation (5 minutes)

  • Increase adoption of good technical architecture

  • Connect experienced practitioners with each other

  • Connect experience practitioners with aspiring practitioners

  • 6:25 - 6:30 Adam Hill (architecture contest)

  • 6:30 - 6:40 Speaker (Ben): “So you Want to Be an Architect? (10 minutes)

  • 6:40 - 7:00 Breakout (20 minutes)

  • 7:00 - 7:15 Group Feedback (15 minutes)

  • Representatives from each group will share their collaborative solutions

  • 7:15 - 7:20 Closing (5 minutes)

  • Thank attendees

  • Next meeting

  • Invite to meet after (probably until at least 8)

  • After Closing: Hang out

References