1. Roll Call (by timezone - East to West)

  2. Scribe Shout-out

  3. Announcements

  4. Business Architecture and the Process of Change
    Piet Niederhausen and Jenni Laughlin, University of Washington

Roll Call


  1. Itana events
    1. Itana Fall FTF at Educause-24 Registered
    2. Itana one hour session
    3. MESA Presentation
  2. API Working Group
    1. 2nd Thursday API call. October 13th is next call. Round table of what is going on at each campus.
    2. Three people leading including Ashish
  3. Link shared for Itana wiki
  4. Steering group candidates
    1. 8 candidates so far
    2. Will discuss and decide in the next two weeks
    3. Need case studies for people coming to the Face-To-Face
  5. Check wiki or email to determine if next meeting is a go because it is just before the Educause Itana Face-to-Face

Business Architecture and Process Change

  1. By Piet Niederhausen and Jenni Laughlin, University of Washington
    1. New capability for them - 1-2 years in the making
    2. See slides
    3. UW - Large public school with 16 colleges and schools and a Med Center
    4. Enterprise Architecture in central IT but Jenni is a federated partner to EA
    5. “The ultimate goal is to actively manage change rather than letting change manage the University."
    6. Business Architecture: Facilitating change through common language and alignment
    7. Industry piece on describing the Business Architecture (technology agnostic)
    8. It is about pulling together a shared understanding of the spaces we work in
    9. Private sector looks different in decision-making and complexity
    10. Figuring out how to think about change in our organizations
    11. Business architecture needs a federated model and needs to pull in those who are practicing across the institution whether they call it that or not.
    12. EA practice supports this in different ways. Proposing a model on the slide.
    13. EA promotes the practice of Business Architecture.
    14. Challenge: the institution works in different ways across different areas
    15. Good change process relies on mature organizations
    16. Much of the work over the last years is cross-functional
      1. Finding shared goals
      2. Sustaining them over time
      3. Is neutrality an important component - yes but there is also benefit to have a technical perspective.
      4. There is somewhat of a barrier initiating these conversations from the IT Organization but that can be overcome with good, well conceived participation and building trust
    17. This moves the IT organization towards a campus partner
    18. A four boxer demonstrating IT’s response across two axises - Change Complexity (high to low) x Customer Readiness (high to low)
    19. Reflection on similarity to Cyefin Framework
    20. More and more we are facing change in high complexity low readiness situations
    21. Part of the work is getting the tools in place to build a shared language and tools to have literacy and strong foundations to work together
    22. List of gaps that Business Architects fill
    23. Case Studies
      1. Space information about facilities
      2. Build a shared sense of purpose
      3. Show the decencies on each others information
      4. Collect all the related efforts under way to maintain current state
      5. Vin Diagram on the village problem - people, process, technology
      6. Pivot on evolving a village
      7. Make it real by building a future state
      8. Future state vision depicts a lot of work over a lot of time
      9. Recommendation high-level motivating view
  2. Questions-How do you approach working with the different teams and getting them to work in a federated model?
    1. One coffee at a time
    2. Putting together senior sponsor and stakeholder groups
  3. How did you get inserted into the opportunity to work with stakeholders?
    1. Worked on various test-balloons on different initiatives, bring those to her senior leaders, then move out, one stepping-stone at a time
    2. Leverage existing relationships and keep building your network

  • No labels