IC2-2 Change Models

We talked about our different projects. Here are a couple of things that stuck with me:

  • Don’t make too much assumptions.
  • Is case-study the language the colleagues speak?
  • Use students to prove your point; let them preach what they need?
  • Peer review is vulnerable.
  • Make the project approachable.
  • Top down
  • Gather stories, anecdotes of the change.
  • Provide clear outcomes – look at what’s gone really well and use it to convince others, make them curious.
  • What do I need to be able to make the next step?

These sentences may not be all that clear if you don’t have the context of my project, but in itself they can be transferred to other project. Something I found out during these sessions is that change is very subjective matter. What works in one situation doesn’t necessary work in another. I get the feeling it’s about “feeling” what people in your environment want, where they are and where they could be. On the other hand, certain theories can be worked out to enable change smoothly and transfer to other situations. Frameworks for change can help, but you still need to work with the properties of your group.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s