We are a remote-first company. This is how we make sure our team can effectively work together to create the last marketing and analytics tool you will ever need!
8. 1. Slack over email always
a. I check my emails a couple of times a day
b. I always keep an eye on Slack
2. Use one-on-one chat for your one-on-one discussions,
use #general for team wide discussions/questions
9. 1. We span multiple time zones so folks might get your
message late in the night or too early in the morning
a. Don’t mention (@) someone unless you want them to know
that they need to act ASAP
b. Use common sense to decide what needs to be handled
ASAP
c. If EVERYTHING is urgent, then nothing is urgent
Example of urgent cases: Customer satisfaction issues/bugs, the
apocalypse (although arguably communicating that is useless)
10. #Alerts: Errors/Exceptions from production
environment go here
#Circleci: Build events are reported here as part of
our gitOps
#Code: Code commits made by everyone are
reported here
#Registration-alerts: Notifies us about actions
customers take on the website: e.g Register, Enable
App, Initialize Checkout, and subscriptions
#Customers_lounge: We give access to some
customers to our Slack workspace. Those are usually
active customers and they are very vocal about what
works (or doesn’t)
11. Use Zoom for one-on-one and ad-hoc calls
● You can start a Zoom call right from Slack by writing /zoom
Use Google Hangout for 2+ participants
If a call can save discussion time then, by all means, jump on a
call. For the other 90% of the cases, chat fits better
Always document the call conclusions
12. Use Notion to document everything, solutions, hacks, etc.
This should be the first place to search for information and
documents on Funnelll
If it is not on Notion, add it
13. We prefer to use WebStorm as our IDE
By having everyone using the same IDE, we keep the same
indentations and code format across development
environments
By hay, who are we to tell a developer which IDE to use?!
14. Use Asana to manage our requirements and backlogs
Marketing Backlog,
Experiment backlog,
Feature backlog, etc.
20. ● Daily Scrum (15 mins)
○ Daily (duh!)
● All team meeting (45 mins)
○ Bi-weekly
● One on One with Sherif (30 - 45 mins)
○ Monthly
○ Whenever you feel like it