The Architecture Clinic is designed to guide and accelerate your exposure to the practices of modern software design.
It is a 5 day highly interactive event where you will learn, improve, and exercise software architecture skills,
all based on the IDesign Method – a breakthrough, battle-proven approach to software architecture that has shown
up to 80% reduction in the effort and time required for architecting, designing, and implementing software solutions.
Through its application, it produces an easy-to-follow blueprint for the construction of a software system, while covering all the important aspects involved.
During the Clinic, you will architect several systems, most of them based on real-world problems brought in by the
Clinic’s participants (and you may offer a system for the teams to work on as well, which could be a nice side benefit).
Through guided practice, you will exercise the IDesign Method and become proficient at it - the Clinic will be run by an
IDesign Master Architect who will teach you the thought process and the rationale behind the design decisions. Along the
way we will walk you through the steps of the IDesign Method, share insight and best practices, and also help develop
the “soft skills” that are so important to success such as customer interview and design review presentation. In normal
day-to-day work, this type of knowledge and insight can take many years to attain. The Clinic will shorten your learning
curve through our years of deep industry experience, and provide a perfect forum for focused, high caliber discussions and mentorship.
The clinic starts with a thorough presentation of the IDesign Method, after which the first system is presented. The attendees
are divided into teams; each analyzes and architects the system. Then, the Master Architect will critic each team's
design as well as present the school's solution. For the subsequent systems design, all teams are reshuffled, so that no team
is ever the same. This helps train architects to focus and communicate, and work efficiently and effectively with other architects.
But the clinic is not just about architecture. A good design is only good if you were able to build it. The clinic bridges the
crucial gap between the design and the development process in the last day. You will see how to derive and design a project plan
out of your architecture, how to design against the critical path of integration, how to identify potential problem in the plan
that may necessitate changes to the design, and how to estimate the cost and schedule of constructing your architecture, to enable
educated decisions further on.
Clinic Alumni refer to it as a "career changing event" since "finally, the blinders are off", and they can confidently architect
correctly any system they encounter and execute that design.
A combination of presentation and a lot of hands-on practice.
Any architect, project lead or senior developer would benefit greatly from the clinic.
5 very intense days.
Available as an on-site training class and as a public training class.
There are a lot of great things to be said about the Architect's Master Class and the follow-up Architecture Clinic. The breadth and depth of information conveyed along with the flawless execution of the material, is something that must be experienced to be understood. If you don't leave the class without experiencing at least one epiphany I will be shocked. The information presented is fact-based, backed by years of practice and documentation and is presented with such focus and mastery that it should be worthy of an award. The IDesign architects are literally the masters of the art and science that is Software Engineering. If I had to sum up the entire experience in one sentence, it would be: This is the modern equivalent of an aspiring artist being taken under the wings of Da Vinci, Dali, or Monet.
Pour the IDesign Method out on the table, grab your hard hat, and get to work! That's the Architecture Clinic in a nutshell. Be warned, however: This awesome, multi-day, hands-on, team-oriented session is not for the faint of heart or brain. The stories you've heard are indeed true – grueling days and nights, intense design critiques, heated debates, walking on beds of hot coals, raised glasses. You'll come away thoroughly worked, molded, and evolved. You'll view distributed systems in a new light. You'll finally see how IDesign’s pragmatic approach and all of the great theory you've soaked up over the years fits together, how straightforward solving hard, complex problems can be, how it all makes sense. So what are you waiting for? You need this Architecture Clinic. Pull the ripcord. Sign up. Now.
Just got back from a grueling week at IDesign’s Architecture Clinic. Much like the Master Class, I feel this one propelled me ahead years (which explains why I’m so exhausted). I’ve struggled with what functional decomposition is, why it’s bad, and what’s the right way to decompose based on volatility. A couple days into the Clinic, I was still stuck and thinking that maybe my brain was just not wired right. However, after working with my team to decompose our third system, things finally clicked, lights flicked on, rubber met road, and I got it! I can just about guarantee if you’re struggling like I was, the Clinic is the solution to your problem. The two things the Clinic gave me that are tough to get in the real world were four opportunities to practice architecting a system – non-trivial, real systems BTW – and get my designs reviewed by master software architects. Those two things in conjunction made it worth every penny, and everything else – hearing eight other designs and reviews, the IDesign Method training, the process lecture, the bonus classes, lunches and dinners with the IDesign architects – made it that much better. To top it all, the Clinic was a great opportunity to meet 14 of the best leads/architects in the field, and work closely with the Masters from IDesign. Richard and Shy, you guys were awesome, and thanks for going above and beyond with the sessions. You have frighteningly relentless amounts of energy. I learned a ton.
Overall the clinic was awesome. I personally feel it provides more value for the $ than the AMC does (if you can imagine that is possible). Knowing there is a better way of architecting is great, which the AMC class helps bring to light - however I still found myself struggling with what it all meant prior to attending this clinic. The clinic is a special environment where like-minded peers can meet, work and learn together while surrounded with the attentive IDesign master architects. The result was a truly unique experience that has helped to elevate my skill set provided me with the tools and mindset to think outside the box.
The clinic comprised of much more than just training on the IDesign method and architecture techniques. It provided invaluable experience and feedback on critical thinking, conducting interviews with clients and presentation skills, all while encouraging you to ask questions you normally have no hope of answering and is tailored to assist with your specific projects which makes it priceless. I also appreciated IDesign's patience with all the additional questions that were thrown at them outside off-hours. That was extremely helpful to the attendees. In short, the clinic is a must-do for any established or up and coming architect.
Software Technology Analyst
Tyler Technologies, Inc.
Veterans of the IDesign already value the knowledge gained at an IDesign master class. I attempted to apply The Method after taking the WCF and Architect's master classes in 2009 and 2010, and thought I was doing fairly well. However, I still struggled with identifying the volatile areas in real-world business systems. After attending the Architecture Clinic I now feel that I have truly seen the light. The IDesign Master Architects took us under their collective wing, and we architected four different systems. We also reviewed and critiqued twelve other architectures of the same systems. This clinic is more of a brief apprenticeship than anything else. An apprenticeship with world-renowned masters focused on boosting your knowledge and understanding to a level that is unattainable anywhere else. After only four time-crunched applications of The IDesign Method, we all progressed significantly. I feel that I moved ahead five or more years. On a personal note, if you are serious as a software architect, I implore you to become the change we desperately need to see in software architecture! Take this clinic as the first step. Then take again... I'll see you there.
Independent software architect
I just wanted to let you know what a truly amazing week I had and how thankful I am to the IDesign team. From getting to meet my peers to designing real-world systems to your emphatic slaps of “FUNCTIONAL” and “APPROVED”, it was an experience I won’t be forgetting anytime soon! Having had a few days to step back, I think the biggest personal impact of the clinic was going beyond learning about the IDesign Method to learning how I could apply it and the realization that it is something I can actually do, and instruct others in executing. Of course, the flip-side of that is appreciating for the first time how much more there’s still to learn and practice. It was inspiring and real pleasure learning from IDesign, not just the design techniques but also the “softer” aspects of architecting a system such as customer interview and presenting a design for review. I can’t wait to see where IDesign takers the work of educating architects next.
Team Lead, Software Engineer/Architect
University of Oregon
The Architecture Clinic is an exceptionally well designed and organized week.
The level of knowledge and experience available for consumption in the clinic was astounding.
Each day from sun up, until well past sun down we worked through exercises and discussions on applying “The Method”.
This clinic is a battle, through the fields of volatility fighting the functional thought process.
You are not alone in this battle as you are led by world renowned Generals in the field of software architecture, and fight
along side others of varying yet valuable skill sets. The final victory is an “Approved” sign stamped on your architectural design.
There is nothing that can compare to the feeling of a panel of Industry leaders rewarding you for your work.
The amount of hard forged experience available by attending this course is immeasurable.
The IDesign Architecture clinic was a truly unique experience which allowed me to be immersed in both time tested and the latest architectural concepts and trends all under the mentorship of true masters of the art. It was a rare opportunity to work so closely and share knowledge with other individuals in this field on real world architectural problems and solutions. The week long class far exceeded my expectations and I recommend it to any serious Architect who is interested in taking their knowledge of systems architecture to a higher level.
The IDesign Architecture Clinic was hands down the best training I have
attended in my career. Juval's passion for architecture shines through
and I learnt a great deal. It was refreshing to be challenged to think,
rather than just being spoon fed course content. Running through the
IDesign Method for a few real life systems gave me a good understanding
of the thought processes behind the Method. The focus on decomposing a
system into change resilient components is invaluable. If you want a
thought provoking, challenging week of training, I highly recommend the
IDesign architecture clinic.
nib health funds limited
Four weeks after the Architecture Clinic we have completed the design for a substantial project based on the IDesign Method. My journey started after the Architect's Master Class last year. The architect’s role was so much broader than I imagined. Would I be able to do all these unfamiliar tasks that I still hadn’t quite got my head around? Was that really my responsibility? Would I even be allowed to try? I was battling to get my everyday tasks done as it was. But the new perspective came with an obligation, and I started looking at old problems in a new light and talking about some of the concepts (don’t base design on the requirements because they will change, encapsulate volatility, separating orchestration from execution, etc.). I was pleasantly surprised at how receptive people were to the concepts (especially business people). Those conversations were noticed and in November last year I was asked to take on the architecture of the new project. The biggest stumbling block for me at that time was getting the decomposition of the Managers and the Engines right – I knew what I was supposed to do in theory, but I kept running into problems (I felt I needed another layer of managers above the managers). Through the most amazing luck the Architecture Clinic came to Australia at just the right time and working through real life examples helped it all fall into place. It was also great to have a refresher of some of the Architect's Master Class material (I could much better understand the significance this time around). It was invaluable to bounce some of our specific problems off Juval. At the time I thought the emphasis on presentation skills was a bit off-topic but it was a tremendous help when I found myself standing in front of a crowded room presenting our design just a few weeks later. It really drove home what an important role confidence plays at all levels.
When I attended the Architect Master Class several years ago I was literally blown away by all of the content covered. It was easily the most thought provoking week of professional training I had ever experienced. It was also a bit overwhelming similar to when you first dump a 1000 piece jigsaw puzzle onto a table. The Architecture Clinic helps you to piece all of the theory learned in the Master class together by applying it to real live systems that the participants are working on, as nothing crystallizes theoretical concepts like the act of applying them to real-life scenarios. The ability to architect multiple systems side by side with your peers is invaluable—the level of expertise and knowledge contained in one room is profound.
That alone is worth the price of admission but there is so much more. You spend an entire week with the IDesign architects whose credentials speak for themselves—not only are they teaching software design, they are your mentors—the key to your success.
Success not only in architecting a software system using the proven methodology ("The IDesign Method") but success in selling your design to your boss and managing the project to its successful completion while both minimizing costs and risks.
The Architect Master Class combined with Architecture Clinic creates a lifetime worth of training that any aspiring architect should not hesitate to attend. It was the best training in my lifetime.
J. J. Koran
Information Technologies Manager
I have attended both the Architect's Master Class and the Architecture Clinic. This is by far the best educational self-investment I have made. The two complete each other.
The content presented in the Architect's Master Class is an eye opener, to a point where I could actually identify exactly what went wrong with past projects that have led them to overrun, and what can be done in the future to decrease the chance of it happening again. Understanding the core principles of The IDesign Method and the thinking that has led to this approach might not be enough to recognize how powerful it can become when applied to real live systems. This is where the Architecture Clinic comes in.
Group-architecting several systems, looking at each from several view points, is the experience I needed to feel confident that I actually understand how the IDesign Method works. It has been several months now since the Architecture Clinic. The more I practice “The Method”, even just by redesigning old projects, the more I realize how unbelievably powerful it is.
Thought I would drop a note regarding the Architecture Clinic which I attended last week in San Jose - it was FANTASTIC, and everything that I wanted to be. My only regret is that it was over too quickly, even though we worked most days from 8AM to 11PM. (No we were not in class after 7PM - and yes we DID work until 7PM - but after class we all stuck together and simply continued the discussion.)
That was the point of the clinic however, discussion. The exchange of ideas, and how to structure and convey those thoughts via diagrams at a high level. That made this clinic, in my opinion, priceless. How often do you (an aspiring architect) get to review 4 systems, in 4 days (+1 day for an intro), and define an architecture for them. This type of experience in the real world would take many years! There are very few architects working in large corporations that would see 4 systems per year, let alone have the freedom to architect those systems without any restrictions (politically, environmentally). On top of all that, there is a room of Architects exchanging ideas across these systems – the learning in this environment simply is exponential!
The Architecture Clinic was unquestionably the single best week of training I have attended and it was the perfect follow-up for the Architect's Master Class. I came into the week thinking that I understood the IDesign Method. While I was comfortable with the mechanical aspects of the IDesign Method, I still had a strong bias to decomposing systems in a functional manner. In the scope of one week, I had the opportunity to go through three cycles of architecting real world systems alongside my peers and with expert IDesign architects providing constant feedback. After the first system, it was clear to me that I did not yet understand the deeper concepts presented from the Architect's Master Class. Over the next two systems, I was able to get to a point at the end of the week where I feel much more comfortable with following a volatility-based approach to system architecture. Beyond just the technical aspects of architecture, the Architecture Clinic also provided an opportunity to practice the other skills the architect requires. I got very useful feedback on not just the quality of my design, but on how effective I was at selling the design in an architecture review. Also, we had an entire day to take one of our completed designs and walk through designing the project plan. The Architecture Clinic took knowledge that would have taken years to acquire and compressed the learning curve down into a matter of days. I would highly recommend any veterans of the Architect's Master Class to attend the clinic.
The IDesign Architecture Clinic is a thought provoking in-depth look on how to properly architect software systems. The Architecture Clinic picks up where the Architect's Master Class leaves off by allowing you to apply the IDesign Method to real software projects under the tutelage and mentoring of IDesign. This is the kind of real hands-on experience that you can’t get anywhere else.
If that was all there was it would be the best class I have ever taken, but it does not stop there. We practiced everything from the soft skills of communicating effectively to how to guide and execute the project to its conclusion.
We had bonus night training sessions and an entire day devoted to process. If you want to know how to better decompose a system based on volatility or how to provide real answers to questions like “how long will it take and how much will it cost?” than this is the class for you. No fluff, no nonsense real world training presented in language that is simple to understand but deep in meaning. The IDesign Architecture clinic is a must for any software architect who is looking take the next step in building great software.
I’ve been practicing the IDesign Method for a while now, and over the years my solutions keep getting better. They are consistent, they meet the requirements, they are extensible, easy to maintain, scalable, robust, secure, and delivered on time. I will admit I still make mistakes, both technical and soft-skills, and I wish I had a world-class architect looking over my shoulder telling me what I was doing wrong, how to recognize functional design, how to spot process mistakes and how to resolve the issues. That is what the Architecture Clinic addressed for me. A week of having IDesign architects guiding and teaching me what I needed to do, techniques for how to do it correctly, how to spot mistakes early on and fix them, and how to present my ideas with confidence. The speed at which everyone attending the clinic learnt was phenomenal. There were people that weren’t full time architects and had no industry knowledge, designing the architecture for financial trading software on day three of the clinic!! The solutions presented by the groups on day 4 were what I would expect a top software architect with years of training and experience to produce. The transformation from day 1 to day 4 was truly amazing.
In summary, I will never have to ask myself what I need to do again. I simply follow the mechanical process of the IDesign Method and apply the techniques of the Architecture Clinic, following its steps and at the end I will have captured the correct requirements, a beautiful architecture, an impressive presentation technique, and a software delivery process ready for success.
After a while back “in the trenches” I wanted to post about my experience with the Architecture Clinic and beyond. For the past 17 years, I’ve been rolling along with different techniques for breaking systems up into their various components, based on functionality that was either complex or likely to change. The systems I put together were modular yet did not handle changes in the business as well as I would have liked. The eye opener for me with the IDesign Method was the focus on the volatility in the business and then architecting the system based on those areas of volatility. For those that have attended the Architect's Master Class but haven’t had an opportunity to attend the Clinic, I cannot stress enough the value of the Clinic since it will have a profound impact on future architecture and design decisions that you make. After the Architect's Master Class, I understood the concepts with the IDesign Method, but once I got back and had a blank piece of paper staring back at me I was struggling. The week of the Clinic and the intense “hands on” exercises have solidified my understanding of the IDesign Method. Plus, techniques that helped navigate from the overall mission statement down to the areas of volatility has helped tremendously to stay focused on the areas of the system that are of importance. Acquiring a solid set of skills to get you from interviewing the customer to completing a system architecture (and all the steps in between) was priceless. Overall, I have to say this is by far the best investment I’ve made in terms of architecture training. I never would have thought that just a single week would have such an impact on my career, but I definitely will never look at architecting systems the same as I did prior to the Clinic. It was awesome to spend the week with so many sharp folks that are dedicated to good system design and a lot of fun to get to know everyone I had a chance to.
Fort Smith, AR
Thank you for the Architecture Clinic. The passion that Shy and Monty bring to the clinic is impressive. It is the best bang for the buck ever just on the face of it – 15 students, 2 instructors, and 14-hour days. But of course the real value is the opportunity to practice the IDesign method and to have our work critiqued by two veteran architects as well as our peers. The extra material about the Cloud was a cold shower – a wake-up call about the cloud – and yet inspiring about its possibilities. The Architect's Master Class a year ago helped me to improve my contributions to and to 3M Health Information Systems, and to gain the trust of many of my coworkers. I am confident that the clinic will accelerate that trend (I’m equally sure that continuous, patient evangelism will be needed).
IDesign’s commitment to mentoring is much needed, and of great value to the software community.
3M Health Information Systems
Having previously attended the Architect's Master Class, I simply didn't believe it was possible to attend another course that could expand my mind to the same degree with such clarity and sense. But an intense week in the Architecture Clinic put that illusion to rest: Shy Cohen's step-by-step elucidation of the IDesign Method is both masterful and engaging, and he conducts himself with seemingly endless enthusiasm and patience. In addition, his passion for teaching is self-evident, as is his willingness to help with any questions you may have. All the aspects of the Method are covered, and three increasingly challenging design workshops are punctuated with tips, advice and training on everything from non-functional decomposition to body language. For anyone who understands the theory of the Method, but still cannot seem to get it right in practice, then this is the course for you; by the end, you will find it hard to imagine designing software in any other way. Pound-for-pound, the Architecture Clinic is one of the best value training courses I have ever attended, as the good people at IDesign once again continue to provide a much-needed service that surpasses all expectations.
Dr Riccardo Bennett-Lovsey
Senior Programmer Analyst
The Clinic was a very valuable experience for me. It moved me from "kind-a" believing I could use The Method in real life, to actually having used it to produce several designs. Now I'm way more confident I can effectively use it in real life projects. For me, it was a required next step after the Architect's Master. Not only was Monty's experienced mentoring very valuable, but the questions, input and collaboration of all the students was really great. Plus, teaching the soft skills required for the client Interview and the design presentation was quite useful for me.
The combination of the Architect's Master Class with the Architects Clinic provides a great, well rounded approach for budding architects as well as seasoned professionals that want to get a handle on the task of design and implementation of service based architecture. I am glad I got a chance to attend both classes within a few months of each other. It’s not every day that you get to sit in a room with top of your peers and discuss designing systems on the fly, or presenting your designs to the group and having them critique your designs. In many teams there are few people to run ideas by, and having this forum was of immeasurable value to me. I’ve had similar comments from the other attendees from my company. In addition, it gave me a wealth of topics for research, as well as practical experience in all phases of creating architecture. From the interview, to the use case and areas of volatility identification, and on to the design diagrams and beyond, the clinic provides real world examples of the problems people are trying to solve daily, and a roadmap to accomplishing that in a standardized, rational way. I highly recommend these classes to any architect wanting to learn more about what today’s evolving technological landscape has in store for an architect, and how to meet those challenges head-on.
There are moments in life that stake claims to permanent spaces in our minds. Some are universally relatable; marriage, graduation, the birth of a child. Sometimes though these are uniquely personal, moments that can only be described as epiphanies. For me, a number of these moments were instigated by Juval’s no-nonsense, no excuses approach to Software Architecture. Awakenings like this don’t take place in some classroom, being led through scripted labs by a questionably-qualified instructor who fails to answer any question whose answer can’t be gleamed from the course materials or found by consulting Google. Your brain has to be stimulated and engaged enough to force this kind of introspection, and that’s what the Clinic delivers. I cannot begin to express how career-changing a course like this can be when it is led by a true master of the craft. The Clinic didn’t merely teach me new things, it taught me new ways to think about things I already knew and also to revisit things I thought I already knew. If you haven’t attended the Clinic, do it. If you’ve already attended the Clinic, send your team. You will produce software leaps and bounds ahead of your best prior to the Clinic.
Lead Software Engineer
The Architect's Master Class was invaluable (I cannot stress that enough). Leaving there left me with this tremendous energy to go and apply what I've learned, except for one thing: I really didn't know what I was doing. Or at least, I haven't had the opportunity to practice and refine The IDesign Method and be sure that what I'm doing was the right thing.
Next came the Architecture Clinic. I was fortunate to schedule both back to back, with only a month apart. Juval called the clinic “training wheels” for The Method. I would say the training wheels were only on for the first day. By the second day we were hard at work applying and learning from mistakes and misconceptions. Finding volatility was the more challenging aspect of the whole process. Monty really helped refine our way of thinking. Every evening we met up for a bonus session which was great as well. All of the guys in the class were great. We talked about our experience and bounced ideas off each other. These days were long: 9AM to 9PM. And the common comment I heard was, "I wish we could do this for a couple of more days.” That just goes to show you how valuable this experience was.
We spent the first two days applying The Method on server-oriented applications. I would say the presentation reviews and interview reviews helped greatly. Now, on the fourth day we designed a client-centric application. That threw us for a loop. Our minds were so focused on server-aide volatility that we really didn't see the client aspect coming. It was good to see both sides of the spectrum. In all, the clinic was great. The Architect's Master Class opened my eyes, but the Architecture Clinic gave me the confidence to put it in practice. If you are considering the clinic or are on the fence, rest assured, it was time well spent.
The clinic throws you into the deep-end of the pool. It is an intense, hands-on workshop. The core of the clinic are the 3 days in the middle – each of which is devoted to running a single system through the IDesign Method at an accelerated pace. The morning is spent in requirements gathering, the afternoon in design followed by each team presenting their solution to the group. At each step along the way there are critiques and discussions of what worked and what didn't work and how to handle any challenges that arose. The focus is primarily on the architectures but Monty also emphasizes presentation skills and how to communicate our ideas to non-technical collaborators including the folks who are writing the checks. At the end of the day, Monty leads a discussion of the strengths and short-comings of each of the proposed architectures and then he presents his “school” solution. The next day you get to do it all again. The direct participation and immersion into three complex systems accelerated my learning by putting flesh on the bones of volatility analysis, identifying and working the core use cases and mapping those to managers, engines and communication patterns, etc. Working the Method alongside a group of sharp, motivated technologists pushed me hard. On top of that, you have Monty in the room as a full participant providing guidance, perspective and insights. There are many opportunities to discuss, refine and reframe ideas and approaches as the week goes on and the complexities of the real-world systems under discussion push everyone to think on their feet. If you’re struggling to figure out how to apply the IDesign Method or simply looking for an opportunity to solidify the skills you've developed I would strongly recommend taking the clinic.
The clinic is in high demand, so getting a seat was very exciting for me. The clinic featured Michael 'Monty' Montgomery as the instructor. If you’ve ever attended any IDesign training, you know that it can be… overwhelming. At times, it felt like we were drinking through a fire hose, but Monty managed to cut through the complexity (real and imagined) of the systems we were working with while helping us refine our thoughts and hunches to create designs that, while not perfect, were completely viable in an afternoon. Let that sink in for a minute. If you’ve been around IDesign for a while, you’ll have heard the talk surrounding volatility and how to identify it. I felt like it might be impossible for a guy like me. Throughout the week, though, Monty did an amazing job of showing us how root out volatility through interviews with executives, business analysts, and developers while giving insightful advice about how to conduct yourself in that environment. In particular Monty demonstrated that volatility didn’t simply live in the business domain, but exists on multiple axes – some of it technical, some of it organizational, and some of it in the problem space of the application itself. On day 5 Monty invited Ally Pearl to give us a great presentation on effective leadership and then spent the rest of the day revealing his original tips and techniques for creating robust service oriented applications. Monty showed us how he handles the problem of junior and senior hand-offs, service naming conventions, and pure, practical sense on what it takes to develop systems that meets the customer’s needs. Suffice to say, Monty was an amazing instructor and presented the material with passion and skill. As a result of attending, I feel more confident in my abilities as an architect. Do yourself a favor and sign up immediately for the next clinic. It truly will be a career changing week and I don’t believe that anyone who is serious about architecture can afford to miss it.