What I like

  • Good presentation and slides
  • Well selected set of techniques
  • Practical and usable
  • Will be useful as soon as Monday
  • Good link with fellow Agile practitioners at my table
  • Good flow, good balance between "theory" and interaction
  • Nice tools
  • "SImple", compact
  • Good expertise of the the presenters
  • Humor!
  • Hands on
  • Sensible and simple
  • The four methods to think about your problem
  • Switching between workshop and presentation
  • Presenting skills
  • More broadly applicable than just for architecture
  • Great practices
  • The exercises
  • The interactivity
  • Some new tools to think about using to communicate with stakeholders
  • Great presentation skills
  • Good link rules/exercises
  • Focus on communication
  • Focus on communication tools
  • Practicing
  • Interesting
  • Techniques can be used right away
  • Some good techniques
  • Good idea to apply communication & problem solving tools to architecture fights
  • Not technical
  • Exercises
  • Good slides
  • Good content
  • Very practical, interactive
  • Good techniques
  • Learned to use drawings, sketches and stories to detach from a context to start thinking from a different angle
  • Communication tools to get the bigger picture common goals, to think creatively => what does success look like? It was very powerful
  • Focus on communication & value for architects
  • Interactive part
  • Ways to talk about your situations and tools to realise your solution
  • Fun, interactive collaboration
  • Lots of effective and short exercises keep the session lively
  • Interesting methods clearly explained!

To improve

  • 7 minutes instead of 5
  • A bit more time
  • More references to  books about the content
  • Maybe too much content for the available time? Too much content for participants to assimilate?
  • A round of beer at the end :-)
  • Give some use case cases and discuss them in a bigger group
  • Apply real architecture examples
  • Correct synopsis and title
  • Make it relate more the job of an architect or make it broader and relate it to other roles as well
  • Storytelling in 5 minutes is very short to get across the power of this method
  • I did not expect this content: "softer" than expected
  • Slides could be more readable
  • Longer?
  • More techniques, less workshop
  • Abstract didn't match the content well
  • The schedule
  • More examples from the real world (e.g. real story instead of imaginary stories)
  • Based on the abstract I was expecting something else. I expected tools or ideas fro improving architecture, not communications stuff.
  • Stay on schedule!!
  • I would like to have heard Sander more, it was clear that Gerard was the "manager" :-)
  • Has not a lot to do with "architecture" (and even less with "enterprise architecture"), is broader than architecture
  • 10 principles -> 4 techniques !
  • Overlap of Solutions-Based Thinking with session by Pierluigi
  • Timing
  • It's not really specific for architecture. It can be used in any role, so the title could be better.
  • Extra link to architecture
  • A lot of material for one hour