A Day in the Life of Setaris
One of the funny things about working for Setaris is that we all have quirky things hiding in our backgrounds. Sure, most of Setaris has a background of some sort in tech, whether it’s in coding or UX. I, however, have probably the least technical knowledge of anyone on the team (although I still manage well enough). And while Josh has degrees in Electrical Engineering, he spends more time on the management and vision of Setaris these days than he does on crazy coding projects.
I bring this post up because it’s operationally relevant, and it details a practice I think anyone can find useful. Take, for example, some of Setaris’s internal projects, like Operations or Marketing. While we don’t necessarily follow this process to a T, we still use a framework somewhat similar to what Josh describes to help run these projects. We try to schedule things in a minimum of half-hour blocks, for example, so that even if planning meetings or certain tasks take less than that, the rest of that half hour can still be dedicated to productivity. And of course, we utilize metrics (even if they’re as simple as “Done” or “Not Done”, meaning a feature is bug-free and in production) as much as we possibly can.
These sorts of operational ideas turn out to work very well for us, and so I think they’re definitely worth sharing. Without some of these practices, for instance, Setaris meetings might turn into hour-long discussions that run off on tangents like minute features that would be beneficial to work on, and that inevitably boil down to “I hate our project tracking system”, or “Oh, Skype, why are you so terrible to us”, or only result in a little bit of headway on that thing that we were supposed to be planning or working on in the first place. So instead, we try to keep these practices in mind, especially the last one. Because, at Setaris, we definitely love to have fun!