• Friday 3rd February 2023
  • Presenters / Facilitators
    • Jim Phelps, University of Washington
    • Louis King, Yale
    • jeff kennedy - University of Auckland
    • Dana Miller, University of Texas at Arlington
    • Daniel Poole - Newcastle University
    • Rupert Berk - University of Washington
    • Henry Pruitt/Marc Ulan - NYU
  • Poll / Survey
  • Slides
    • Google Slides presentation includes detailed information about responses to the poll noted above.

Jim - More than half of EA teams consisted of 1 person, yet they had a campus-wide scope 

How did you get started?

  • Went to university to become a polymer chemist and ended up doing experimental psychology and an MSc in psychoacoustics and the experimental analysis of behavior and half a PhD
  • Quit studying, and took an administrative job with a Student information system
  • That initial job led to me progressing into other things, including roles as Systems Analyst, Information Specialist, Integration Architect, and Enterprise Architect
  • Took 5 years break to start my own practice

What was most challenging?

  • People - most challenging part
  • A toxic work culture where people wanted to be right but not focus on good of the community (almost 20 years back)

What did you find most helpful?

  • Community!  CAUDIT and Itana and other peer and community groups are the most valuable
  • Curiosity

There are additional slides in the deck that are not posted here and self explanatory.


When you became an architect, how do you deal with the slow pace of change in universitiy environment?

  • Louis
    • Came from the central IT 
    • When moved from strategy, what I thought can be accomplished in 3 years, took 10 years
    • Reset the expectation as it almost takes 3 times more effort to build consensus in the university environment
    • Work across different teams, building 

How do you navigate the modality from doing everything by yourself to working with people?

  • Rupert - Reset the measure of impact. It may not be a clear concrete thing. Have to be patient. 
  • Dana - It is nice to see Artifacts that I developed being used by others 

Use project-based language

  • Jeff - Architects could be more What stakeholders are looking for
    • Give the name of the project - resources, and roles
    • Deliver as part of the project and it gives a lot
  • Henry - The project drives the need for change. Especially integration-related change. You can point people, and how the ripple effect can drive the change
  • Jim - the project can drive the change
    • Current state/ future state/ fit gap analysis/ capability change.
    • The project language can drive more acceptance. Using the project to start the practice.
    • Louis - the campus is based on cost - The new projects will move to further the cause. 
  • Louis 
    • Break down architecture in phases and spread it over-funded projects
    • That seems more concrete and deliverable

CIO buy-in 

    • It doesn't have to be CIO buy-in. 
    • Look for an anchor in any leaders.
    • A senior business leader may have more leverage than an IT leader

What to do so that the changes you are making are sticky

    • Henry - If you can create an artifact that is widely used will make a difference
    • Jeff - The consistency of the use of the capability model
    • Daniel -  
    • Louis -
      • Embedded architects in projects to make lasting change
      • Planning capability across the service team. A lot of rewards. Planning and continued collaboration are part of the culture
      • Embed improvements in the project/ processes of the large implementation.
  • How do you get people to understand the value of EA practice
    • Number of artifacts being used
    • Henry -
      • Making things easier to do provides value.
      • For that, you may have to leave IT roam and go to business roam
      • Architecture thinking making connections amongst it strategy, drivers, and business process makes the point
      • Getting more business buy-in and less friction
    • Jeff
      • Be a good storyteller,
      • People needing EAs in the room show the value
    • Daniel
      • Number of different projects where EAs are involved 
    • Dana
      • A list of common problems can be solved by EA.
    • Rupert 
      • Creating the model in a future state
      • Creating a picture/view that people show it around on the campus has a lot of value 


Sorry, didn't take a screenshot of the attendees

  • No labels