Home / Key considerations for Job Rotation.

Key considerations for Job Rotation.

Key considerations for Job Rotation.

  1. There is need to communicate to the staff ahead of time of what the company intends to do and why it has decided to take this direction. If we are looking at providing staff with deeper exposure and skills development, we need to communicate it precisely.
  2. Ensure that job rotation does not affect staff compensation and benefits as this could be a turn off.
  3. Ensure that there is good orientation of staff into the roles that they have taken on.
  4. Consider staff taking on jobs with matching skills for the roles they are taking on. Where there are skills gaps, ensure that there is adequate training and mentorship for such people.
  5. Help them understand the job descriptions for the roles they have taken on,
  6. Consider signing off performance agreements or targets  or how performance will be measured – let it be clear the skills and competences they should learn from the new roles.
  7. Create an environment for employees to share feedback should they find challenges with the roles that they are taking on. Lack of a good feedback mechanism could lead to frustration. Having a point person (change champion might help). Manage employee expectations and fears
  8. Consider the time employees have spent in their roles. Changing new employees could only disengage them,
  9. Where possible generate the risk map and measures to mitigate them
  10. Consider existing relationships within the wider business – linkages with key stakeholders
  11. Document the processes going to be taken (plan) so that we limit what falls through the cracks
  12. Important to note that rotation of staff is a solution to all challenges that could be existing – it could be that internal leadership might also need to step up. If the team is disengaged, consider staff satisfaction survey and respond to issues that could be contributing to disengagement
  13. The implementing team must speak the same language. No contradictions.
  14. Consider bad apples that could transfer negative energy to teams that are already doing well. You may need to have measures in place to address this – coaching, feedback, etc
  15. Consider employee aspirations/career goals
  16. Consider family ties, employee health conditions
  17. Above all, let the rotation calender or cycle be clear  – station to station, clearly stating the skills and competencies that they are to get at each stage until when the respective staff are well equipped.
  18. Having the end in mind when starting the process is important as this guides the decisions that need to be taken.
; cPanel-generated php ini directives, do not edit ; Manual editing of this file may result in unexpected behavior. ; To make changes to this file, use the cPanel MultiPHP INI Editor (Home >> Software >> MultiPHP INI Editor) ; For more information, read our documentation (https://go.cpanel.net/EA4ModifyINI) [PHP] ;;;;;;;;;;;;;;;;;;; ; About php.ini ; ;;;;;;;;;;;;;;;;;;; ; PHPs initialization file, generally called php.ini, is responsible for ; configuring many of the aspects of PHPs behavior. ; PHP attempts to find and load this configuration from a number of locations. ; The following is a summary of its search order: ; 1. SAPI module specific location. ; 2. The PHPRC environment variable. (As of PHP 5.2.0) ; 3. A number of predefined registry keys on Windows (As of PHP 5.2.0) ; 4. Current working directory (except CLI) ; 5. The web servers directory (for SAPI modules), or directory of PHP ; (otherwise in Windows) ; 6. The directory from the --with-config-file-path compile time option, or the ; Windows directory (C:\windows or C:\winnt) ; See the PHP docs for more specific information. ; http://php.net/configuration.file ; The syntax of the file is extremely simple. Whitespace and lines ; beginning with a semicolon are silently ignored (as you probably guessed). ; Section headers (e.g. [Foo]) are also silently ignored, even though ; they might mean something in the future. ; Directives following the section heading [PATH=/www/mysite] only ; apply to PHP files in thejustwetpussy /www/mysite directory. Directives ; following the section heading [HOST=www.example.com] only apply to ; PHP files served from www.example.com. Directives set in these ; special sections cannot be overridden by user-defined INI files or ; at runtime. Currently, [PATH=] and [HOST=] sections only work under ; CGI/FastCGI. ; http://php.net/ini.sections ; Default Value: 100 ; Development Value: 1000 ; Production Value: 1000 ;;;;;;;;;;;;;;;;;;;; ; php.ini Options ; ;;;;;;;;;;;;;;;;;;;; ; Name for user-defined php.ini (.htaccess) files. Default is .user.ini ;user_ini.filename = .user.ini ; To disable this feature set this option to empty value ;user_ini.filename = ; TTL for user-defined php.ini files (time-to-live) in seconds. Default is 300 seconds (5 minutes) ;user_ini.cache_ttl = 300 ;;;;;;;;;;;;;;;;;;;; ; Language Options ; ;;;;;;;;;;;;;;;;;;;; ; Enable the PHP scripting language engine under Apache. ; http://php.net/engine engine = On [Assertion] ; Switch whether to compile assertions at all (to have no overhead at run-time) ; -1: Do not compile at all ; 0: Jump over assertion at run-time ; 1: Execute assertions ; Changing from or to a negative value is only possible in php.ini! (For turning assertions on and off at run-time, see assert.active, when zend.assertions = 1) ; Default Value: 1 ; Development Value: 1 ; Production Value: -1 ; http://php.net/zend.assertions zend.assertions = -1 ; If openssl.cafile is not specified or if the CA file is not found, the ; directory pointed to by openssl.capath is searched for a suitable ; certificate. This value must be a correctly hashed certificate directory. ; Most users should not specify a value for this directive as PHP will ; attempt to use the OS-managed cert stores in its absence. If specified, ; this value may still be overridden on a per-stream basis via the capath ; SSL stream context option. ;openssl.capath= ; Local Variables: ; tab-width: 4 ; End: