Commit to Greatness
Team members that are present and engaged operate at a higher performance level. If you are distracted or not fully present, you can pull others off track. When you are in the team space, be “in”. Remember that when you Check In you are agreeing to the Core Commitments.
Use the Check Out protocol if you aren’t “in”, or if you can’t uphold the commitments.
Check In Protocol
Use Check In to begin meetings or anytime an individual or group Check In would add more value to the current team interactions.
Steps
- Speaker says “I feel [one or more of MAD, SAD, GLAD, AFRAID].” Speaker may provide a brief explanation. Or if others have already checked in, the speaker may say “I pass.” (See the Pass protocol.)
- Speaker says “I’m in.” This signifies that Speaker intends to behave according to the Core Commitments.
- Listeners respond, “Welcome.”
Commitments
- State feelings without qualification.
- State feelings only as they pertain to yourself.
- Be silent during another’s Check In.
- Do not refer to another’s Check In disclosures without explicitly granted permission from him or her.
Notes
- In the context of the Core Protocols, all emotions are expressed through combinations of MAD, SAD, GLAD, or AFRAID. For example, “excited” may be a combination of GLAD and AFRAID.
- Check In as deeply as possible. Checking in with two or more emotions is the norm. The depth of a group’s Check In translates directly to the quality of the group’s results.
- Do not do anything to diminish your emotional state. Do not describe yourself as a “little” mad, sad, glad, or afraid or say “I’m mad, but I’m still glad.”
- Except in large groups, if more than one person checks in, it is recommended that all do so.
- HAPPY may be substituted for GLAD, and SCARED may be substituted for AFRAID.
The Core Commitments and The Core Protocols are part of The Core developed by Jim and Michele McCarthy.
The Core is distributed under the terms of the GNU-PL. For exact terms see http://www.gnu.org/licenses/gpl.txt. The Core is considered as source code under that agreement. You are free to use and distribute this work or any derivations you care to make, provided you also distribute this source document in its entirety, including this paragraph.