Once I have a few process workflows completed and the members of my team are happy, the next step is to show them to others.
I don’t need all of them. I just want to show a few examples of the “least challenging” and get a better feel for how much these stakeholders want to participate. And I want to do this really quickly so I get input before I get too far in the process.
The workflows are meant to be conversation-starter.
For the process itself – “This is what we are
doing? What’s your process? What’s working? What’s not? What would you
like to be able to do?”
For architecture in general – “Is this something you would like to participate in? Is there something you would love to see coming out of this effort? Does this flowchart format make sense to you without me explaining it? Are you interested in seeing some of the other work we are doing to make sense of our environment?”
If all goes well, these little bits of outreach and relationship-building is the start of a beautiful relationship.
When having discussions with the
other trainers, I have to be really careful about couching this as just
our process. I don’t expect them to adopt it or want to use it or even
that it will work for them. Just a conversation.
This is where coming from the IT department, honestly, makes this conversation a bit more hazardous.
The last thing I want is to have the other training teams feel like they
are being forced to do something because “that’s the way IT does it.” That never goes well.