|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#6
|
||||
|
||||
|
Re: Team Continuity
Another tip is to just write things down. Just because one person has done a specific task for the past ten years doesn't mean they will be around to do it for another ten. If you write down lessons learned, processes, team goals, and future plans, it is much easier to pass on the knowledge if someone were to move on for whatever reason. Having written documentation also helps make sure that everyone is on the same page.
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| paper: Cyber Blue 234 Continuity Plan Presentation - CHP | Chris Fultz | Extra Discussion | 3 | 21-04-2009 22:48 |
| paper: Cyber Blue 234 Business Plan and Team Continuity Plan | Chris Fultz | Extra Discussion | 1 | 21-04-2009 09:17 |
| Team 234 - Belt / Chain Drive and Team Continuity Planning | Chris Fultz | Championship Event | 0 | 14-04-2009 08:03 |
| Bernoullis versus Continuity | Corey Balint | Math and Science | 13 | 15-09-2007 17:59 |
| Thank you Team 179, team 237, team 269, team 303, team 1065, and team 1251 | Arefin Bari | Thanks and/or Congrats | 13 | 16-03-2006 20:52 |