Back in June 25, 2009, I blogged about a new collaborative teaching approach here.  At the time of that blog we were in the Measure phase of  project to take an interesting idea and create a new solution.  Well, we're at the tail end of that project (the Recognize phase) and the story is a very successful one.  The pilot launched with 3 sites and another 2 are coming on line.  The client is very happy and we're hoping to meet with the project team over the next couple of weeks to complete our close out review.

So what was the secret to our success?  In short, the client was clear on the 'what': They understood their process.  We do plan on a more detailed post implementation review to dissect the success in more detail but every ounce of my experience is convinced that the fundamental reason for the success of this project was that the client was very clear on what needed to be done but was challenged to build an on-line system to make it happen.  That's where Collaboration Consulting Inc. came in.

The nucleus of the solution is a configuration of SharePoint, and was based on our Process Portal approach.  The net result was a hybrid that brings some excellent teaching theory in to a practical collaboration application.  Physicians in Alberta going through residency, as well as their teachers (Preceptors and Advisors) now have a way to record observations about Residents. 

We'll be reviewing this solution more seriously as a case study at the SharePoint Summit 2010 if you're more curious.

The net effect - for the first time in medical education:

• Residents, Preceptors and Advisors can now have a collaborative dialogue about observations, learning and accomplishments (i.e. the tracking of competency development over time)
  • These observations (known as field notes) also have both sides of the conversation (student-teacher) tracked over time
  • Observations can be made on a mobile browser (through a blackberry, Pocket PC or iPhone with mobile IE or Safari)
  • Observations can be recorded in real time or later on at the choice of the user
  • When learners are geographically apart from teachers, both user groups can still review progress at any time, in real time
• Advisors now have a way to build a body of evidence to support the recommendation to licence a Resident as a doctor.  This is a world first in medical education and the University has already begun sharing this idea at conferences around the world.
  • Imagine the idea of a Doctor being certified based on the opinion of the teacher alone.  Would it not be a surer process if a body of evidence were based on actual field observations and mutually agreed accomplishments?

The learning for me?  This is more of an enforcement of something I already knew: The clearer the problem (and client) is on the the process-context surrounding the problem (i.e. what exactly do people do, and what information do they need to do it?) the more likely we are to succeed.  And if the client is not clear on the collaboration model (process and information) then push harder to get that clarified as a part of requirements definition.

Back in June 25, 2009, I blogged about a new collaborative teaching approach here.  At the time of that blog we were in the Measure phase of  project to take an interesting idea and create a new solution.  Well, we're at the tail end of that project (the Recognize phase) and the story is a very successful one.  The pilot launched with 3 sites and another 2 are coming on line.  The client is very happy and we're hoping to meet with the project team over the next couple of weeks to complete our close out review.

So what was the secret to our success?  In short, the client was clear on the 'what': They understood their process.  We do plan on a more detailed post implementation review to dissect the success in more detail but every ounce of my experience is convinced that the fundamental reason for the success of this project was that the client was very clear on what needed to be done but was challenged to build an on-line system to make it happen.  That's where Collaboration Consulting Inc. came in.

The nucleus of the solution is a configuration of SharePoint, and was based on our Process Portal approach.  The net result was a hybrid that brings some excellent teaching theory in to a practical collaboration application.  Physicians in Alberta going through residency, as well as their teachers (Preceptors and Advisors) now have a way to record observations about Residents. 

We'll be reviewing this solution more seriously as a case study at the SharePoint Summit 2010 if you're more curious.

The net effect - for the first time in medical education:

• Residents, Preceptors and Advisors can now have a collaborative dialogue about observations, learning and accomplishments (i.e. the tracking of competency development over time)
  • These observations (known as field notes) also have both sides of the conversation (student-teacher) tracked over time
  • Observations can be made on a mobile browser (through a blackberry, Pocket PC or iPhone with mobile IE or Safari)
  • Observations can be recorded in real time or later on at the choice of the user
  • When learners are geographically apart from teachers, both user groups can still review progress at any time, in real time
• Advisors now have a way to build a body of evidence to support the recommendation to licence a Resident as a doctor.  This is a world first in medical education and the University has already begun sharing this idea at conferences around the world.
  • Imagine the idea of a Doctor being certified based on the opinion of the teacher alone.  Would it not be a surer process if a body of evidence were based on actual field observations and mutually agreed accomplishments?

The learning for me?  This is more of an enforcement of something I already knew: The clearer the problem (and client) is on the the process-context surrounding the problem (i.e. what exactly do people do, and what information do they need to do it?) the more likely we are to succeed.  And if the client is not clear on the collaboration model (process and information) then push harder to get that clarified as a part of requirements definition.