Mem Tutorial and Case Study: How to Take Meeting Notes

Meeting notes don’t fail because someone can’t capture enough information—they fail because the system makes it hard to retrieve the right details later. In a hands-on Mem setup review, an IT consultant focused on NetSuite ERP implementations describes spending most of his day in “capture mode” during client meetings, then struggling to find what matters afterward and to turn quick notes into executed tasks.

The fix centers on reducing tag overload and using Mem’s structure to create a “central resource” per client. During meetings, he uses a meeting template, links his calendar to create Mem4 events, and tags notes for context like meeting type and client-related topics (e.g., NetSuite, CRM, ERP). But the workflow still creates friction: too many tags, too much topic-specific tagging, and not enough connective tissue between notes and action items. The consultant admits he often doesn’t know where to look when revisiting recurring work, and he spends more time capturing than executing.

The session reframes tagging as a limited, context-based tool rather than an all-purpose filing system. Instead of tagging by infinite topics (which quickly becomes unmanageable), he’s encouraged to keep tags general—around recurring contexts such as “onboarding meeting,” “client follow-up meeting,” “implementation timeline,” or “CRM requirements.” Links, meanwhile, are positioned for connecting ideas and relationships. That distinction becomes the core operational change: replace “data migration” as a standalone tag with a bi-directional link that ties the action item directly to the relevant meeting notes.

A key workflow upgrade is moving from scattered notes to client-centered hubs. For a fictitious client (“nsco”), the recommended structure starts with a central Mem page for everything related to that client, then links out to separate notes for timeline and scope of engagement. From there, additional Mems can represent repeatable phases—requirements gathering, ERP requirements, and CRM requirements—each created from templates so the process stays consistent while the content changes. This reduces context switching inside Mem and makes it easier to review all onboarding or requirements work across multiple clients.

Task management also gets attention, but less as a standalone system and more as a downstream benefit of better note structure. Mem’s tasks can be scheduled for specific times, moved to “upcoming,” and snoozed via reminders in the inbox, so action items don’t clutter today’s focus. The consultant also learns to use templates for recurring action items and responsibilities, so meeting capture automatically produces the right follow-ups.

Finally, the session broadens beyond client delivery: lessons learned, methodologies, personal “open loops,” and even video outlines for a YouTube channel are organized using the same principles—general context tags plus bi-directional links. The expected payoff is both time savings (days, not hours) and better insight: once notes and tasks are organized around repeatable contexts, patterns across clients—common requirements and recurring problems—become visible rather than buried. The consultant’s goal shifts from merely remembering to extracting reusable solutions for future NetSuite engagements.