Strict Standards: Non-static method PermissionsCache::exists() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 69
Strict Standards: Non-static method PermissionsCache::getIdentifier() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 15
Strict Standards: Non-static method PermissionsCache::getObject() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 70
Strict Standards: Non-static method PermissionsCache::getIdentifier() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 45
Strict Standards: Non-static method Area::getOrCreate() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/block.php on line 63
Strict Standards: Non-static method Area::get() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/area.php on line 153
Strict Standards: Non-static method Cache::get() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/area.php on line 121
Strict Standards: Non-static method Cache::key() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/libraries/cache.php on line 117
Strict Standards: Non-static method Cache::getLibrary() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/libraries/cache.php on line 121
Strict Standards: Non-static method Cache::key() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/libraries/cache.php on line 137
Strict Standards: Non-static method Cache::get() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/block.php on line 67
Strict Standards: Non-static method Cache::key() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/libraries/cache.php on line 117
Strict Standards: Non-static method Cache::getLibrary() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/libraries/cache.php on line 121
Strict Standards: Non-static method Cache::key() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/libraries/cache.php on line 137
Strict Standards: Non-static method PermissionsCache::exists() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 69
Strict Standards: Non-static method PermissionsCache::getIdentifier() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 15
Strict Standards: Non-static method PermissionsCache::getObject() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 70
Strict Standards: Non-static method PermissionsCache::getIdentifier() should not be called statically in /home/s552988/public_html/updates/concrete5.4.2.1/concrete/models/permissions.php on line 45
Team Alignment
Our Perspective
Helping a team to work together at high performance levels can be achieved in many ways. There are a lot of team building activities and excersises from puzzles to paint balling. The games are not our forte.
We believe
… that aligning a team is about creating a space and enviromnemt where the team can explore
1. Their common purpose (for the individual, the team and the organization.)
2. Their difference as individuals
3. a shared commitment.
4. Clarify roles and responsibilities
This exploration will lead to a deep understanding of why the team does what It does and also how it will do what needs to be done.
The alignment process promotes and supports:-
1. Awareness
2. Honesty
3. Trust
4. Personal and shared responsibility
Signs that a team is not aligned:
1. Lack of ownership and follow through
2. Pushed deadlines
3. “them” and “us” attitude
4. Gossip and back biting
5. Low morale
6. Passive compliance.
7. Polite conversation and nodding heads.
When is a good time to align a team?
1. When there is a new leader
2. New team members
3. There is a new direction, strategy or major project.
4. Performance of team is low.
5. Moral is low and / or conflict is high.
How is it done?
1. One to one discussion with Leader to clarify, vision, goals, current challenges and obstacles, current initiatives, and agree outcome of the alignment process.
2. Interview all team members.
3, Design alignment process based on the outcome of the above.
4. Facilitated workshop(s).
5. Wrap up report and meeting with Leader, and one to one coaching if required.
What does an aligned team look like?
1. Common purpose and a passion for that purpose
2. Shared values
3. Good relationships
4. Honest conversations
5. Clear roles and priorities.
6. Goals are achieved (bottom line)
7. Vocal about concerns and not afraid to challenge.
8. Differences are worked out.
9. Total commitment as an individual and as a team.