Wiki contents

Journals

2019 Learning journals
2018 Learning journals
2015 Learning journals
2014 Learning journals
2013 Learning journals

Smartsims Support Centre

Blog updates

Recently Updated

Recent updates

Recently Updated

All updates

Skip to end of metadata
Go to start of metadata

It is coming to the point of the semester where we only have a few rollovers left and sitting in 2nd on the global leaderboard for our course seems to be a pretty good position to be in at this point. However, since ‘hostiley’ taking over another company within the simulation, we seem to be in a position where we are not generating a profit, and the rollover this week was our chance to try and change that.

 

The problem that my team faced this week was opening the lines of communication to the other business, as they felt like we had undergone a hostile takeover and I am sure all they wanted to be able to do was try and figure out a way to get their company back and get the best possible result from the simulation that they can. Needing to communicate with the other team wasn’t the issue, it was the fact that our CEO was the man in charge for that sort of thing and he could not attend the lecture time due to personal reasons.

 

If we were to leave the issue for the next rollover in hopes that they would carry out decisions simply because we knew our CEO would be the ideal man for the conversation, then our company wouldn’t have generated such a good result from the rollover and we would not be the 2nd highest on the global leaderboard. That is the difference between single and double looped learning, as explained by Argyris. Because the rest of our team took the initiative and did not wait for the go ahead from our CEO or wait to see what he would say, our company saw substantial growth, as did the company which we took over.

 

After carrying out a conversation with the other team, both companies have come to a realization that we can now carry out decisions that will be in the best interest for both teams, working together in order to have more market share between us, thus leaving other companies with less.


Argyris, C. (1977) Double loop learning in organizations. Harvard Business Review, 55(5), 115–125

4 Comments

  1. Hey Eden, 


    It was nice to see someone coming on top of the simulation for once, and it's nice to see you come to the conclusion to work with the other team as a team and making them one to get the best reward and maximise profits or SHV. However it would be nice to elaborate how your teams wants to work better with the company you ought over and what kind of challenges you faced, apart from lack of communication that brought down your profits. Is there a specific strategy you want to implement with the amount of products you have now at your disposal. 


    Great read, keep up the good work!

  2. Hi Eden,

    Good to hear that your team and the company you took over has worked out well and that you have both increased your SHV!

    One thing I think you can work on for your learning journal is making sure you make it more personal. It's great to see that your team is doing well, but this journal should be about the team, it's about you!

    In future, make sure you cite your references.

    Hope you guys continue to do well!

  3. Hello,

    I enjoyed reading your learning journal. I liked that you incorporated the reading into your journal to help support your problem and why it was happening the way it was. One thing I thought you could do differently is talk about how the problem affected you and how you, personally, were going to act on in. Overall, great job and good luck with the future rollovers.

    Alea

  4. Hey Eden,

    i'm a little confused to why four people were given your journal to review, however i really enjoyed your journal this week, and its nice to see that other people in my team are on the same page. to improve upon this journal i would try making it more personal or at least adding more personal reflection to it. also Nicholas mentioned it that you should make sure to include an in site reference when referring to some resource material. 

    keep it up and see you next week.