template

    Personal README

    Engineering-style user guide

    README.md format for documenting individual collaboration preferences

    Purpose

    Tech-friendly format for sharing work style and communication needs

    Training Enrichment

    Core Insight

    A Personal README is a powerful tool for setting clear expectations and fostering transparent communication in professional relationships.

    Real-World Challenge

    Imagine you're a new team leader at a tech company, joining an existing team during a high-stakes project. Tensions are high, deadlines are looming, and you notice a lack of communication and misunderstandings about roles and expectations. Without a clear way to express your work style and preferences, your team's inefficiencies and frustrations continue to grow.

    Actionable Guidance

    • 1Identify key elements of your work style and communication preferences, such as preferred communication channels, decision-making processes, and feedback reception.
    • 2Draft your Personal README, focusing on clarity and brevity. Use headers like 'How I Work', 'Communication Preferences', and 'What I Value' to organize your thoughts.
    • 3Share your Personal README with your team and encourage them to create their own. Use it as a starting point for open discussions about collaboration and expectations.
    • 4If you notice a communication breakdown, refer to your README to realign and address any discrepancies immediately.
    • 5Regularly update your README to reflect changes in your work style or priorities, especially after major projects or role changes.

    Coaching Prompts

    • ?What are the three most important aspects of your work style that others should know?
    • ?How could misunderstandings about your preferences impact your team's performance?
    • ?In what scenarios might you need to update or revisit your Personal README?

    Application Drill(5 minutes)

    Spend 5 minutes writing a paragraph on 'How I Prefer to Communicate' in your Personal README. Focus on specific channels, frequency, and tone.

    Success Criteria:

    • ✓Includes specific communication channels (e.g., email, Slack, video calls).
    • ✓Mentions frequency and tone preferences (e.g., daily updates, concise messages).

    Examples

    • •Engineering leader onboarding
    • •Product team building empathy
    • •Remote IC introducing self

    Exercises

    • 1Write Your README (60 min): Complete all sections-how you work, communicate, what you value, how to support you
    • 2Team Exchange: Share READMEs with new collaborators within first week of working together
    • 3Manager-Report Pairing: Have managers and direct reports exchange READMEs and discuss alignment/gaps
    • 4Onboarding Integration: Make README sharing a standard part of your onboarding process for all new relationships

    Tags

    template
    documentation
    engineering

    Related Artifacts

    Expected Outcomes

    • ✓Practical Readme for immediate implementation
    • ✓Consistent application of best practices
    • ✓A written structure to agree expectations
    • ✓Enhanced effectiveness through tested approach

    Authors

    Chad T. Dyar

    Target Audience

    coaches
    managers
    team-leaders

    Duration

    30-60 minutes

    Difficulty

    beginner

    Mark as Complete

    Ready to move forward? Mark this complete to track your progress.

    Was This Helpful?

    Your feedback helps us improve the Performance Lab experience for everyone.