Why you should write a “how to work with me” user manual

Marko Saric
Oct 17, 2018 · 5 min read

Confusion, miscommunication and disappointment

Picture this common situation:

What’s the intention with the guide?

Claire joined in 2014 when the company had 165 employees and helped Stripe grow to over 1,000 as of now. Previously she worked at Google.

  • When do I want to hear from you?
  • What are my preferred communication modes?
  • What makes me impatient?
  • Don’t surprise me with X

What does Claire’s guide look like?

Claire’s guide starts with the “operating approach” where she explains the way she likes to deal with one on one chats, team meetings and other planning sessions.

I don’t like chasing deadlines but I do notice when things slip

Next up, she shares details on her management style. On topics such as action items and deadlines:

FYI = no response required

There’s also a section on emails:

What would the guide to working with you be like?

This type of doc seems like a very useful way to get to know someone quicker, minimize misunderstandings and miscommunication. And it could help you run a better team and a better organization.


This story is published in The Startup, Medium’s largest entrepreneurship publication followed by + 379,306 people.

Subscribe to receive our top stories here.

The Startup

Medium's largest active publication, followed by +469K people. Follow to join our community.

Marko Saric

Written by

I’m a blogger and content marketer focused on creating win-win situations. https://howtomakemyblog.com/

The Startup

Medium's largest active publication, followed by +469K people. Follow to join our community.