@darkdriving Hey Andrew, thanks so much for your patience. We really appreciate your excitement around what we're building and hope we can get you started soon!
Many of us had never met in person before our first @considerhq offsite. But after 2 hours of facilitated activities, we understood each other on a deeper level. I wrote about it, in hopes this helps other teams build foundations of trust and closeness. 🥰 https://t.co/uYusOMUgtH
At @considerhq, we wanted a strong stance on security and privacy from the outset.
@bobjlong has put together a great guide based on what we've learned:
https://t.co/Ydm38GjnjF
We hope this can help other early-stage teams!
Our team is split between two offices, three thousand miles apart.
@AllieHitchcock wrote about three ways we manage the distance.
https://t.co/AyOdidKmMl
Nice post by @AllieHitchcock on how we've been managing our SF–Boston office communication at @considerhq: https://t.co/fIq6AbV12Q
As teams, the small details in *how* we choose to use our tools can be so powerful.
🥳We just released reactions, comments, and more in @considerhq to help you have higher quality discussions, and set a friendlier tone for email. https://t.co/Ao9R0CNBzD
This is really interesting from @considerhq. Just last week, we sent an internal announcement through both email and slack -- the latter just folks could do non-intrusive reactions. Contextual comments also seem clearly useful.
https://t.co/XMM2ZIbdw8
Today we're giving conversations their biggest upgrade since email was first conceived nearly half a century ago.
Introducing reactions, comments, and presence for email. Available for all teams on Consider.
Check it out: https://t.co/Fk1MFkwICK
There's one classic mistake we've seen when prioritizing bugs.
If you're working on a product or product area that requires attention to detail, you should read this:
https://t.co/fNoYIk3kif