Not allowed to use cloud services at work

A strict “no cloud services” rule at work forced a freelancer to rebuild a productivity system from scratch—without Notion, to-do apps, or Google Calendar—while still handling the realities of office life: scheduling, task tracking, and capturing information. The core takeaway is that productivity doesn’t need a single perfect platform; it needs a reliable “holy trinity” of appointments (calendar), tasks (to-dos), and notes (a personal knowledge base), each adapted to what a company allows.

For appointments, the solution is straightforward: use the company’s centralized calendar (often Microsoft Outlook in large organizations). The real advantage isn’t personal preference—it’s visibility and coordination. A shared calendar makes it easier to see when other people are booked, which meeting rooms are free, and how to align on timing, location, and agenda. That centralized view outweighs any productivity gains from using a different calendar tool.

Tasks are handled next, with a key distinction: many teams already have kanban/scrum boards for larger work items, but smaller “in-between” tasks still slip through—like preparing for a peer code review or handling quick items that arrive before they fit a board. The workaround starts immediately with something always available (a basic notepad or equivalent) to capture tasks the moment they appear. Then the system evolves into a more permanent tool, and in this case Microsoft Tasks becomes the default.

Microsoft Tasks doesn’t match Todoist’s label/filter power, but it offers a different mental model: a “today” view that starts empty and pushes planning into the day itself. Instead of cleaning up an already-loaded list, the workflow flips into a more positive rhythm—selecting what to do from other lists and letting completed items visibly disappear with checkmarks and strike-through. Over time, the creator also changes Todoist behavior by moving tasks to “no date” and choosing them based on the current project (work, home, or YouTube), discovering that many tasks don’t truly require due dates.

Notes become the hardest constraint. New companies scatter information across coworkers’ heads, wikis, SharePoint sites, emails, and slide decks, and the usual approach—building a collaborative database in Notion—breaks under the cloud ban. OneNote is tried first but feels too freeform, causing lost structure and constant rearranging. The secure alternative is Obsidian, installed locally so notes remain on the laptop as local encrypted markdown files rather than syncing to the cloud. Obsidian’s strength is linking and building a personal “mental head” of knowledge, plus plugins for journaling and capturing meeting details. The main limitation is collaboration: Obsidian can’t easily support real-time commenting and feedback like Notion, so shared outputs are handled by copying into emails or publishing to a wiki once the content is ready.

After months of running Obsidian successfully, the workflow later shifts to Logseq, which becomes a better fit—though the details are left for another time.