Day 297
Week 43 Day 3: Section 1: My Working Genius and My Working Frustrations
The first section of your Leadership Operating Manual tells your team where you are at your best and where you struggle. This is not weakness -- it is honesty, and honesty is the foundation of efficient collaboration.
Lesson Locked
You completed your Working Genius assessment in Week 2. You explored your gaps in Week 7. Now you write it down for your team. 'My genius is Wonder and Galvanizing. I am at my best when I am exploring possibilities and building momentum for the team. My frustration is Tenacity. I struggle with detailed follow-through and can lose track of commitments if they are not in a system. If you need me to track something, put it in our project tracker -- do not rely on my memory.'
Here is how to write Section 1 of your Leadership Operating Manual. The section has three parts. Part A -- My genius areas: describe the types of work where you are at your best. Be specific about what this looks like in practice. Not just 'Wonder' but 'I am at my best when I am exploring new approaches to problems, looking at our work from different angles, and asking questions that challenge assumptions. In brainstorming sessions, I will generate many ideas quickly -- some good, some terrible. I need the team to help me sort the good from the terrible because my Wonder does not naturally include evaluation.' Part B -- My frustration areas: describe the types of work that drain you and where you are most likely to make mistakes. Be honest. 'Tenacity is my frustration area. I tend to lose interest in projects once the exciting discovery and launch phase is over. I can miss details, forget follow-ups, and move on to the next interesting problem before the current one is fully resolved. This is not because I do not care about completion -- I care deeply. My brain is simply not wired to sustain attention on incremental execution. The team should not rely on me for detailed project tracking. I have built systems to compensate (our project tracker, our weekly status review, our Definition of Done), but those systems exist precisely because my natural tendency is to move on too soon.' Part C -- How the team can help: describe what the team can do to ensure your frustration areas do not create problems. 'If I have committed to something and seem to have lost track, remind me directly. I will never be offended by a reminder -- I will be grateful. If you see me starting to disengage from a project before it is complete, flag it: "Hey, I noticed you have not checked in on the migration project this week -- is it still on your radar?" That directness helps me enormously.' The key principle: vulnerability in this section is strength. The leader who writes 'I have no frustration areas' is either lying or lacking self-awareness. Either way, the team will not trust the manual.
Section 1 implements what Lencioni (2022) calls 'Working Genius transparency' -- the practice of making the team aware of each member's genius and frustration profiles to improve task allocation and reduce interpersonal friction. His organizational case studies demonstrate that teams where all members' profiles were visible and discussed showed 30% fewer miscommunication incidents and 20% faster project completion, because team members could anticipate each other's strengths and compensate for each other's frustration areas proactively rather than reactively. The vulnerability component is documented by Brown (2012) in 'Daring Greatly' as the 'vulnerability paradox' -- the finding that leaders who express vulnerability (admitting weaknesses, asking for help) are perceived as more trustworthy and more competent by their teams, not less. Her research found that vulnerability is perceived as courage in others and as weakness in oneself, which explains why leaders resist being vulnerable despite the benefits. Research by Owens and Hekman (2012) on 'expressed humility' in leadership found that leaders who openly acknowledged their limitations were rated 14% higher on overall leadership effectiveness by their teams compared to leaders who projected comprehensive competence, because the acknowledged limitations created opportunities for team members to contribute their complementary strengths, which increased both team performance and team member engagement.
Continue Reading
Subscribe to access the full lesson with expert analysis and actionable steps
Start Learning - $14.99/month View Full Syllabus