> On the technical and process side, we had a policy of things not existing (or not existing properly) unless they were in written form. This included decisions

> On the technical and process side, we had a policy of things not existing (or not existing properly) unless they were in written form. This included decisions, context, back-and-forth reasoning, announcements, etc. We used GitHub for non-code "tickets" this way, almost like an internal blog and topic-focused discussion forum. We are working on making this process more scalable at Aether’s Pro version, it is especially useful for remote companies as you mentioned. It helps that we are a remote company as well, eating your own dog food is the fastest way to improve. If you’d like to get on the pilot, hit me up and I’ll add you in.