How to move from spreadsheets to a database
The signs a spreadsheet has outgrown itself, and how to move without losing the flexibility that made it work.
Separate calendars per purpose, the right level of visibility, and how to keep it readable as the team grows.
The reliable way to share team schedules is to create a separate calendar for the shared thing — holidays, releases, on-call, client meetings — and give the team access to that calendar, rather than sharing personal calendars with each other. Personal calendars stay personal; the shared one carries what the team needs to see.
This also solves the visibility problem: colleagues can see that you are busy without seeing what you are doing, which is what most people want from a work calendar.
Do not put confidential information in event titles on a shared calendar. Titles are the part everyone sees, including people who were added later and forgotten about.
Ettex Calendar gives you month, week, day and list views, coloured calendars and reminders, with events sitting next to the documents and boards they relate to — so a release event can link to the checklist instead of describing it.
Share availability, not detail. Free/busy tells colleagues when you can meet without exposing what you are doing.
As many as there are distinct purposes, usually two to four. More than that and people stop turning them on.
The person responsible for that calendar plus a backup. Everyone else views.
Always create events with an explicit time zone and let each person’s calendar do the conversion — never write “3pm your time” in the title.
The signs a spreadsheet has outgrown itself, and how to move without losing the flexibility that made it work.
The five sections that matter, in the order visitors read them — and what to do before you pick a template.
Decisions, owners and dates — a structure that takes five minutes and survives the week.