Communication

We are a remote consulting company. Clear communication is not a soft skill. It is the skill. Without it, nothing else works.

Principles

The Standard

Every message, to a teammate or a client, should be:

Clear. Say what you mean. Not what sounds diplomatic. If something is broken, say it is broken.
Complete. Include enough context that the reader does not have to ask a follow-up question. If they do, your message was incomplete.
Timely. Share blockers, delays, and bad news early. Surprises erode trust faster than problems.
Professional. The same quality bar applies in Slack, email, GitHub, and client channels.

Writing

Write Like You Mean It

Much of our work happens in writing. Slack messages, PR descriptions, GitHub issues, emails to clients. The quality of your writing directly affects how well others can work with you.

Before hitting send, ask yourself:

Is this complete? Or will they need to ask "what do you mean?"
Is this clear? Or am I using vague language to avoid being specific?
Would I be comfortable with the CEO of our client reading this?

Simple English is good English. Complete sentences. Proper capitalization. No sloppy shorthand. Slack may feel casual, but habits carry. A person who writes carelessly in Slack writes carelessly in client emails.

Growth

Getting Better

Communication improves with practice and feedback. If you notice repeated issues in someone's writing, tell them. Respectfully, but tell them. And when someone gives you that feedback, take it seriously.

We are not just building software. We are building trust. Every message either adds to it or subtracts from it.