Morning,
Significant progress on our round, more soon.
This also happened:
- We spent a bunch of time onboarding new users and also doing the rounds with the current users to collect feedback. Primarily with our goal of shaping/filtering our roadmap for improvements around our core focustime-saving features.
- After finding a time, or when moving an internal event around, we visually show who is not available. We made a change to make a visual distinction between time that's marked as focus time and time that's blocked with meetings. We obviously don't want to promote focus time to book meetings in, but we also don't want there to be no time to meet ever. Now we're clearly giving the user the data so they can make their own trade off.
- On top of that find a time upgrade, one of the things our users and we ourselves also feel is that sometimes you want to more clearly understand why our Find a time picked what it picked. So we have been working on a toggle that switches between the clean available/not-available/focus time view and showing all events + focus time for each attendee. Close to shipping that.
- We also added analytics so we're able to measure how many times our users create events vs use find a time.
- We added alerts to warn us when our API endpoints are becoming slow, so we'll catch regressions early and can roll out changes fast and confidently
- We shipped a feature that allows to quickly toggle an additional timezone
- We prepared our first two jobopenings. Our strategy is to attract top tier talent, which will require top tier pay. We heard the different perspectives and we feel this is our best chance of building a world class team. We've also based our salary range on this fantastic post by Gergely Orosz, by the way. And for full perspective: we want to keep the team as small as possible, especially before we got traction on the product.
What's next:
- We'll be shipping more improvements to the find a time flow
- Key people in teams are users that schedule a lot of internal events. As this is super useful information to have when we're onboarding / expanding teams, we'll adjust our report to surface this info for us
- We want to pro-actively start calculating event scores for our users, so we can highlight events that are particularly problematic and offer suggestions before highlighting events
How can you help?