Have you ever wished your work partner came with an instruction manual?

You know, a simple guide to decode their quirks, know when they’re at their best, dos and don'ts? Think of it as the README file for a human being.

So, during the "All ways UP!" sprint planning I asked it to my Sircle members: prepare a personal user manual for each of us. Nothing heavy or corporate, just a candid snapshot of our strengths, weaknesses, work habits, and how we like to connect. The reactions ranged from intrigued nods to outright chuckles, but I’m convinced this could be a quiet revolution for any team that wants to thrive and improve its collaboration (one of the Sprint Values!).

We spend hours with our teammates, tackling projects, debugging code, or brainstorming the next big feature. Yet we don’t know whether someone’s a morning rockstar or a late-night coding ninja. Or if they prefer a quick ping on chat versus a formal email.

My manual, for instance, would say I’m sharpest before noon, love diving deep into problem-solving (sometimes too deep), and thrive on clear, written communication. Don't interrupt my flow state with a call, or I might need a beat to catch up - not because I’m disengaged, but because I need a moment to switch.

The beauty of this exercise isn’t just in sharing your strengths, like how you can develop under pressure or spot a UI flaw from a mile away. It’s also about owning your vulnerabilities. Maybe you’re a wizard at development but need extra time to prep for presentations because public speaking makes you sweat. Or perhaps you’re the team’s go-to for creative brainstorming but prefer clear deadlines to avoid getting lost in a sea of ideas. By putting these things on the table, you’re not just helping others understand you: you’re building a foundation of trust and clarity.

When you know your teammate needs a heads-up before a big brainstorm or prefers async updates, you’re not just working better: you’re respecting who they are.

My Sircle and I already started drafting our own manuals, each in its own way and if you are curious: here you can find my onw manual, while here is Filippo's!

And if you want some literature and more examples, they are here!

So, here’s my call to action: grab a coffee, jot down your own user manual, and share it with your team. Keep it real, keep it light, and watch how it transforms the way you work together. A little clarity about each other might just be the starting point to build something great.