Training Expedition

January 19, 2009

In 2008 we started Training Expeditions. They are 2 days in the year (in Apr/May and in Oct/Nov) when I try to create an interactive and fun way for the team to experience research and learn new skills. In November we had our second Training Expedition.

The planning started in September when I decided a good base theme would be: a treasure hunt. The treasure would be the new research skills or insights…

  • They would have to explore and uncover (key aspects to our mission)
  • They would be going on a range of expeditions
  • The stages required them to be observant, resourceful, and problem solving
  • Some elements required team work, some individual work
  • Timeliness as well as thoroughness is important

Next, I developed a list of things I noticed they needed to improve. Then put them together so it was a treasure hunt.

My followers on Twitter gave me the venue for the lunch session.

On the day, I reported the progress of the team on Twitter:

Tweet 1: is having our Training Expedition, a treasure hunt in Sydney, starting in 6 hours. Looking forward to see what the team uncovers!
Tweet 2: the team are off and running at a Speed Thinking Course run by Ken Hudson (They loved the introduction to Speed Thinking Course)
Tweet 3: Thinking that I made the Training Expedition too difficult. Team not started Stage 3 & so now they’re running an hour late. Doh! (Apparently they were busy networking with people they met at the course! Excellent for branding, not so good for being time efficient)
Tweet 4: Wooo hooo, someone just logged on for Stage 3. Hopefully my laptop battery will last until they get here for Stage 4 & 5. (They went to the Apple store and logged onto their webmail, as the information said the next clue would be emailed to them. They thought if it required them to know something from the walk to the office, which it did, they wouldn’t have to double back – impressive)
Tweet 5: 1 of 3 have finished Stage 3… but will they find me for Stage 4?
Tweet 6: I counted the banks on their Expedition wrong. Me=11. Team=14. The number was in a formula to get to me. Had to text the them the address.
Tweet 7: Stage 5: Wagamama lunch & feedback form review. 3 in Sydney CBD. Went to location they knew, not closest. Google could have saved 3/4hr! (They didn’t go to the wrong location, actually they texted a friend to find out the closest Wagamama, which was resourceful. They then spent 2 hours at lunch which we discussed at the de-brief)
Tweet 8: Team have recovered well and are now on their final stage. Sure to have interesting discussion at Sanctuary Hotel from 4pm.

At our team de-brief, I was interested to hear, not only the first statement, when I walked in ‘that is the best day we have ever had, I can’t believe we got paid for that‘. Throughout the day they worked as a team which was interesting as the incentives were individual based.

The team provided two testimonials for the day (they are not edited!):

“The training expedition at Tribe Research was definitely a unique way to get to know the rest of the team better. It was hands on training with a scavenger hunt using all the skills we put into action at work every day, thinking outside the box, understanding different people’s strengths and weaknesses in a team and effective planning. The great thing about the day was it was fun and different and engaged us instead of a dull lecture, and we found at the end of the day that all the skills we used that day translates to the work we do as well. I’ve found now that I can better appreciate the different dynamics of the team and see that problem solving can be done more than one way.”

“The activities organised for our Training Day were really different and exciting! We were on our ‘toes’ the entire day and still pumped come reviewing time at 4pm. It gave us the chance to really bond as a team and address issues within the organisation in a fun, creative manner. More organisations should try and make their Training Days as creative and as exciting as ours – the outcomes will speak for themselves. It was the best Training Day we have ever had!”

My thoughts after the day, and we have just had our Planning Expedition which discussed the Training Expedition further…

  1. I really enjoy organising them
  2. The team bonded
  3. The team have greater job satisfaction
  4. I learnt how the team thinks and works together
  5. The team learnt research approaches

At a time when staff retention is really important: it costs more than their annual income to replace; it is important that quality staff grow and stay with you. Developing your team, so they want to stay with you, and when they leave want to maintain a relationship with you, is even more important.

What are you doing to keep your tribe of staff with your business?

  • Share/Bookmark

We need a Mapper

January 17, 2009

In 2008 we started a new role at Tribe Research: Mapper.

I’m not a fan of conventional job titles as they have a tendency to put people in boxes which people then try to fit, rather than broad roles that people can use to grow the business with their ideas and individual skills.  You can read more about our roles on our team page.

Our first Mapper was fantastic. She has her own business, Bounce Walking Tours, and learnt so much at Tribe Research that her business has grown too much to stay with us in her Mapper role. So we are now looking for someone as fantastic to fill the hole she left.

Mappers put things onto a map and bring them to the public eye, make them known or prominent and arrange them in an understandable order. In this capacity a Mapper:

  • Finalises and distributes our newsletter Tribal Voice
  • Proof reads my articles ready for publication
  • Organises opportunity appointments and manages my diary
  • Organises our Advisory Board meetings
  • Organises our annual TRX event and distributes their newsletter [TRX is our previous staff club]
  • Keeps MYOB up to date
  • Keep the website up to date
  • Does random other administration and marketing roles.

Tribe Research is fairly technology focused. We have CRM, wiki, remote working, and Skype. Having a handle on basic HTML will be useful.

A Mapper is a casual role of 8-16 hours per week. Preferably done as a few hours each day over the week.

Work at home, have a monthly meeting with me, need to come to 2 Planning Expeditions each year.

You must have your own computer with good quality internet connection [not wireless]. You must be independent, resourceful, positive and detail minded.

Interested? Please use our contact form

  • Share/Bookmark