Monday, August 31, 2009

28 August

Team work - this is the most dynamic team I've ever seen, and other people comment on it too. Do we need to quantify what we've achieved - how do you show a return on investment? Obviously we will have an end product - the online induction Wiki, but we've also developed team skills, as well as team building skills and tools to use with our own teams; project management skills, with the team leaders powering with their ability to draw together information and to then share it with everybody else on the project, and to be able to use technology, which we've probably improved in by about 50%, especially SharePoint, which can be cumbersome.

On the 28th we revistied the TMS work preferences, discussing how we've been able to apply this in our workplaces, with different styles of communication, having your profile posted in your office, doing the abbreviated tool with your own team, and various other impacts that the knowledge we gained about ourselves has had.

We then worked out a rough time line for the induction online, with a Media wiki workshop on the 10th Septebmer to learn more about populating and modifying the resource, and also drew together the results of the research, content, and promotion work with the design. Another good meeting, and thanks to Sharyn for facilitating, but to all for your enthusiastic, positive and constructive input to this project.

Saturday, August 1, 2009

Where are we up to?

A great day on Thursday 30 July with the TMS analysis - what are our work preferences, and how do they fit with others on our project team. At the same time, our mid-term report is due, and the feedback reflects the calibre of this team - constructive, dynamic, flexible to say the least.

We decided that for the induction resource introduction we need to emphasise the need for:

Trust, mutual respect and helpfulness, working together and how this relates to Teaching and Learning

The TMS looks at nine key success factors which make teams high-performing.

This was about different characteristics of teams – the different type of tasks that need to be completed to ensure excellent performance.

We had some great “real life” examples of these roles from the tem team members attending.

Discussion re Floor Robe - sometimes the incidental learning is the most important :-) any suggestions on how to get teenagers to get rid of their Floor Robe will be gratefully received.

We decided to advertise jobs looking for people in the North-West sphere - Advising and Innovation - to expand our workforce capability. A prize is offered to the first person to fit this category. We had no people in the ‘green sector” which is not a problem for our project, but may be for the organisation.

Our project people find the profiles a bit spooky in terms of the accuracy of the profiles. We recognised that our preferred roles did not necessarily fit with our current roles.

One of the most helpful things from today was about how to work best with other work role preferences.

e.g. The Assessor – Developer is:

· Analytical and objective
· Developer of ideas
· Enjoys proto type or project work
· Experimenter

When working with, for example, the Concluder Production

· Be structured and practical
· Give notice of proposed changes
· Stick to your word
· Keep deadlines
· Stay focussed
· Don’t waffle
· Don’t change your mind too frequently

Some things to work on:

· 2 things I’d like you to know about me:
· 2 things you can do to best communicate with me
· 1 thing I’d like help with


· Develop a personal action plan
· What could you STOP, START and CONTINUE to be even more effective at work?
· Swap profiles with your Manager/Section team/ Colleague. Discuss how to best work with one another.
· Build on your individual strength but remember if preferences are overdone, the strength can turn into a weakness.