If you’ve worked in software, you’ve likely run across a README file. README files are an easy-to-read document that typically serve as the first point of reference for anyone interacting with a project, software, or dataset. Their main purpose is to explain what the project is, how it works, and how to use it. Turns out, it’s not just software that benefits from publishing README files; humans benefit from offering each other a human README file, too!
When I first ran across this kind of concept, it was introduced by Charlie Rowat as a Ways of Working Canvas. Charlie’s goal was to fast‑track cohesion in small, high‑pace project teams, especially when members don’t know each other well. He believed this canvas could enable teams to quickly become “well‑oiled machines” capable of working together intuitively. When I used the Ways of Working Canvas, I found it produced effects not dissimilar from norming with your product team, but the personal detail it provided allowed us find meaningful ways to better support each other.
Here’s how we use READMEs at Atomic Object.
When I joined Atomic Object, I was excited to find that the Ann Arbor office uses README docs for its team. Here, the README files serve double duty. They support new project teams getting to know each other and also better matching in our Career Development Manager (CDM) program. The concept was introduced here by Monica Worline from the University of Michigan’s Center for Positive Organizations, inspired by a chapter in Rich Smalling’s book, Practically Positive.
One of a new employee’s onboarding tasks in the first 30 days is to draft their version of a README and share it with their teammates. New employees also review the README docs of the Ann Arbor CDM team to identify which individuals would be their best match for a coach and mentor for their first year.
Our READMEs generally cover a few main topic areas:
- Strengths and communication preferences
- Highlights of what helps them excel on a team
- Callouts of what can prevent them from contributing effectively on a team
- Areas of improvement they’re currently targeting
- Random fun facts to add a bit of whimsy!
Talking about topics like strengths, communication preferences, work patterns, and growth areas with team members creates a foundation of trust, empathy, and efficiency. When teammates understand what conditions help each person excel, how they prefer to receive feedback, and which situations might make it harder for them to contribute, they can work together to create an environment where everyone thrives.
Sharing collaboration styles, values, and boundaries also reduces misunderstandings and helps align expectations from the start. Even lighthearted elements, like fun facts, add a human touch that fosters stronger connections and makes it easier to build rapport. Altogether, these conversations give teams a shared language for supporting each other’s success while deepening relationships beyond the work at hand.
Try it yourself.
Looking for an example? Here’s my own most recent README doc!
Want a template? Download a starting point
Before tackling filling out your README, reflect on the following questions. Once you’ve answered these questions, synthesize them into the headings contained in the README doc. If there are other headings you’d like to see, create them! Feel free to reference past evaluations (DiSC, StrengthsFinder, VIA Strengths) and self-development work for this exercise.
- Strengths & Communication – What are your top personal or professional strengths, and how do you prefer to communicate with others (e.g., in-person, digital, async)?
- At My Best – In what kinds of situations, environments, or tasks do you feel you’re able to contribute at your highest level?
- Feedback Style – How do you prefer to receive feedback, and what helps you apply it most effectively?
- Work Patterns – What conditions (time, space, structure) help you stay focused and productive?
- Triggers & Challenges – What situations, behaviors, or dynamics make it harder for you to do your best work?
- Growth Areas – What skills, habits, or mindsets are you currently working on developing or improving?
- Collaboration Preferences – How do you like to engage with colleagues during work—constant interaction, periodic check-ins, or independent focus with occasional collaboration?
- Values in Action – Which values guide how you work with others, and how do you show them in your day-to-day interactions?
- Boundaries & Needs – What boundaries help you sustain your energy and maintain positive relationships at work?
- Fun Facts – What are some personal tidbits or achievements that might help others connect with you as a person?
Now share it with others!
Once you’ve drafted your README, the next step is to put it to work! Share it with your team, your manager and anyone you collaborate with regularly. Invite others to read it and ask questions, or even better, encourage them to share their own so you can exchange and compare. Revisit it every few months or after major shifts in your role, team, or personal growth, and update it to reflect your current strengths, needs, and working style.
You can also use it as a reference point in one-on-ones, project kickoffs, or feedback sessions to keep communication clear and expectations aligned. The more openly and actively you use your README, the more it becomes a tool for building mutual understanding, strengthening relationships, and making your team’s collaboration smoother and more rewarding.