Remote Working Essentials

Whilst we’re all working remotely, as I’m sure most people are, we thought we’d share our tools of the trade for keeping business moving as usual, even though we’re not in the studio.

Project, Team & Time

Projects: Monday.com

Monday.com is a great project management tool for small businesses like ours. It’s basically spreadsheets on steroids. And we did manage our weekly schedules using Google Sheets before upgrading to proper project management software.

The main feature we use is our main weekly team tasks board, which documents job categories, statuses, who’s assigned to what, and the associated phase and ultimate deadlines. It also allows you to view activity logs for each ‘row’ of the boards, meaning everything is fully documented.

Projects: Google Calendars

Alongside our Monday.com task boards, we also maintain Google calendars for each team member, which acts as a default diary and maps out a longer term overview of our projects pipeline and priorities.

Time: Harvest

We use Harvest for time tracking, so we can monitor budgets and project scopes, and also analyse the areas where our time is being spent. We can use this data to see how we’re performing and where we’re at in relation to our total team capacity on a daily, weekly and monthly basis.

Team: Zoom

Of course, (I’m sure you’re probably sick of hearing the word, but) we use Zoom video conferencing throughout the day for both team and client meetings, daily 9am briefings and end-of-day debriefs.

The screensharing feature is also super easy to use and great for design review sessions, thrashing out concepts and ideas, presentations, and troubleshooting things like software issues.

Web Development

Source Version Control: Git & Github

With multiple developers working on any given web development project, it’s important to maintain source version control to ensure all changes are updated centrally, fully documented, backed up, and reversible.

Github is used as our master/origin, which is ‘checked out’ as a working copy onto the developers machine, changes are made, then these changes are ‘committed’ with a description of what’s being done, and then ‘pushed’ back to Github to update the master/origin version.

In addition to this, both the staging (private development/test version) and live sites are also managed and maintained as part of this same version control process.

We’re always looking for ways to improve our setup, so please get in touch if you have any ideas or tools we’re missing!

Jason Nye

Co-director