Mnémosyne vs. Craft for Consultants: Two Different Approaches to Working on a Mac

At first glance, Mnémosyne and Craft may seem similar.

Both apps place a strong emphasis on the quality of the Mac experience. They allow you to save information, organize your work, and find what you've written.

The resemblance, however, ends rather quickly.

Craft is primarily built around the document. Mnémosyne is built around the folder and its memory.

This difference becomes significant when a consultant is no longer simply trying to locate a note or a document, but—several months later—is trying to understand what happened in a client file, what decisions were made, and why.

Craft first organizes documents

Craft lets you create documents, link them, organize them into folders and Collections, assign tasks to them, and work in shared spaces. It remains positioned as a relatively general-purpose document and work environment.

For a consultant, this can be a great way to organize by client.

For example:

Client A
→ Project 1
→ Meeting Notes
→ Minutes
→ Proposal
→ Reference Materials

You can take it a step further by using Collections, links between documents, or templates.

So the problem isn't that Craft is incapable of organizing a client file.

The problem arises when this organization is asked to store anything other than the content itself.

Mnémosyne starts from the client file

In *Mnémosyne*, the starting point is not a blank page.

The system already recognizes elements such as:

Client → File → Assignment → Documents → Notes → Decisions → Timeline

This structure changes the way we work.

A note isn't just a note filed away in a folder. It may be part of a specific assignment.

A decision may be linked to the problem that prompted it, the reasoning that preceded it, and the documents used as sources.

An event can occur within the timeline of the case.

The difference may seem small when the file has just been created.

It becomes much more noticeable six months later.

Finding a piece of information is not the same as understanding the context

Let's imagine a consultant who returns to an assignment after eight months.

He recalls that a solution had been considered and then rejected, but he doesn't remember exactly why.

In a document management system, he will generally begin by searching for the relevant items:

• meeting notes; ;
• comparative document; ;
• minutes; ;
• previous proposal; ;
• possibly a daily task or note.

The information is available.

But they still need to rebuild their relationship.

In Mnémosyne, the approach is different: important elements may already be stored in the file's memory.

The goal, therefore, is not simply to locate the document that contains the information.

It is to be able to find the context in which this information had become significant.

A decision isn't just a line in a memo

This is probably one of the most significant differences between the two approaches.

In Craft, you can record a decision in a document, create a dedicated template, or even build a Collection to track them.

That's a real possibility.

But the structure then depends on the organization created by the user.

In Mnemosyne, a decision is directly linked to the professional memory model.

It can preserve:

• the context; ;
• the problem to be solved; ;
• the options considered; ;
• the decision reached; ;
• the reasons for the choice; ;
• the options that were ruled out; ;
• risks; ;
• the consequences; ;
• related sources.

The goal is not to add more information.

The goal is to prevent a decision from becoming, a few months later, a statement whose reasoning no one really remembers.

This is also the reasoning outlined in our guide on [the history of decisions related to a client project].

Can we recreate this structure in Craft?

In part, yes.

And it would be disingenuous to claim otherwise.

Craft includes features such as Collections, related documents, folders, templates, and tasks. This makes it possible to build a relatively sophisticated organizational structure.

We could create:

• a Customer Collection; ;
• a Projects Collection; ;
• a decision-making model; ;
• meeting materials; ;
• the connections between the various elements; ;
• the same structure for each new folder.

But from that point on, part of the system relies on the user.

We must decide on the structure, replicate it, maintain it, and, above all, continue to use it consistently enough to ensure that it retains its value over time.

This is where Mnemosyne takes a different turn.

The memory structure is not a workspace that the user has to create. It is part of the product.

Comparison Based on an Actual Case

The table does not imply that any one tool is superior in every case.

They're simply starting from different problems.

Craft makes more sense when the document is centered

If your main need is to create polished documents, share them, collaborate with others, or have the same environment across multiple platforms, Craft is a better fit.

Craft offers shared spaces, co-publishing, and Collections, among other features, and operates on multiple platforms.

That is not the area in which Mnemosyne seeks to replace him.

Mnémosyne is not intended to be a general-purpose writing or collaboration tool.

His problem is more specific.

Mnémosyne becomes more relevant when the file needs to stand the test of time

A consultant rarely works on just one project.

Customers are piling up.

Some assignments last several months.

Others are returning after a long hiatus.

And part of the work involves gradually recalling things that seemed obvious at the time they happened.

Why was this option rejected?

Which document led to this decision?

What had the client agreed to?

What risk had been identified?

Where exactly were we before the mission was interrupted?

That is precisely the problem that Mnemosyne seeks to solve.

Not by asking the consultant to write more.

But by providing a lasting structure for the elements he chooses to keep.

AI is not the main difference

Craft also features an assistant that can help with tasks such as writing, organizing, or summarizing content.

It is therefore not relevant to present AI as the difference between the two products.

For Mnemosyne, the memory must remain usable even without Clara.

The case file, the decisions, the relationships, the sources, and the timeline form, first and foremost, a deterministic structure.

Clara can then help identify or understand certain elements.

Its purpose is not to retroactively construct a memory that would never have been preserved.

This distinction is essential.

Mnemosyne or Craft?

Ultimately, the choice depends on the problem you want to solve.

If your work revolves mainly around documents, writing, sharing, and collaboration, Craft is probably a better fit.

If you work on a Mac with multiple client folders and your main challenge arises when you have to revisit a project several weeks or months later, Mnémosyne addresses a different need.

The question, then, is no longer just:

Where did I put that information?

It becomes:

Why did we make that decision, and under what circumstances?

That's where professional memory begins.

Conclusion

Both Craft and Mnémosyne can store notes, documents, and information related to a project.

But they do not assign the same role to this information.

Craft organizes what you write.

Mnémosyne aims to preserve the information needed to understand your case as time goes by.

For a consultant who regularly has to revisit old cases, track down decisions, and understand their origins, this difference ultimately matters more than the number of available functions.