Traces on Architects and Architecture
My architecture journal notes are called traces, underscoring the informal format. A sampling follows.
LinkedIn: Ruth Malan
Email: Ruth Malan at bredemeyer.com
I am a senior consultant with Bredemeyer Consulting. I work primarily with architects (from enterprise architects and chief architects, to system and product architects and tech leads) and with teams, on system and software architecture and design. This work depends on the point in the system lifecycle -- ranging from strategy and design incubator work in early stages, to architecture assessment and renewal for legacy systems.
Architecture encompasses strategically and structurally significant system design decisions -- decisions that impact agility, system integrity and sustainability (in technical, economic, organizational, and environmental terms). System design addresses key challenges and tradeoffs, to create systems with the desired capabilities and properties taking into account customers and users as well as operations and development teams. Moreover, these systems are co-evolving within broader socio-technical systems. It is demanding work with a lot riding on guiding and informing decisions that impact the system as it evolves. While experience is a critical base on which to build, training can be useful, drawing out what's been learned as it applies to systems design, and adding concepts, techniques and heuristics to that base. Our workshops focus on system design, and the role of architects (whatever their title, for developers and tech leads may be doing system design).
Our (enterprise, system and software, respectively) architecture workshops have an emphasis on situated learning, where small teams work on creating a draft architecture, drawing on the models and guidance in visual architecting. We work iteratively, and weave concepts and architecting techniques into lectures/discussion that bookend work sessions. Hence, the order of lecture topics is driven by the concerns that are being addressed at that stage of the architecting process. This makes it a "non-traditional" format, but it is one that works well as it allows us to work end-to-end through the creation of a draft architecture.
We primarily run in-house workshops, with a couple of open enrollment workshops each year. The next Software Architecture Workshop is scheduled in:
Design Leadership and Other Skills Workshops
When we talk about design leadership, we mean it in both senses — design leadership in the market, and design leadership in the organization. In this workshop, we explore what that means and how we develop design excellence and leadership in ourselves, and nurture it in our teams. Our workshops combine a base in theory with practice elements, working in small teams. We cover essential topics in system design; strategic context understanding and shaping; organizational skills including communication and influence; and how to be a more effective technical leader. The next open enrollment Design Leadership and Other Skills is scheduled in:
Posts on LinkedIn:
Slidesets from Conference talks:
Cutter Consortium Enterprise Architecture Executive Reports:
"Highly recommend taking one of @ruthmalan’s workshops" -- Phillip Johnston
"I took this course 10+ years ago. Still use what I learned on a daily basis." -- Eelco Rommes
"I use what I learned from y'all every day" -- Eric S.
"I’d strongly recommend this course to both aspiring and practicing architects [..]. I consider the Bredemeyer course to be one of the best professional investments I have ever made and I absolutely intend to make more." -- Mark Mullin
"I took @ruthmalan's software architecture workshop in the fall. We collaborated in teams to solve a business problem then compared our approaches and outcomes. So much learning." -- Susan Almon