Every engagement is scoped, delivered, and reviewed by Amelia Caldwell alone, with no subcontractors and no templated slide decks.
MindVault Lab Flow started in the autumn of 2019, in a rented office on King Street West in Toronto, with a single client: a forty-person software firm whose leadership team had stopped agreeing on anything. Amelia Caldwell had just left a large strategy consultancy where she had spent four years producing reports that were thorough, well-formatted, and largely unread. The software firm did not need another report. They needed to slow down long enough to understand what they were actually arguing about. That first engagement ran six weeks and ended with a decision framework the team still uses. It was the clearest signal that the practice had found its shape.
The name came later. 'MindVault' was a term Amelia used in her notebooks for the space where a team's real assumptions live, the ones that drive decisions but rarely get written down. 'Lab Flow' was a nod to the kind of focused, low-interruption work she wanted the practice to model. By 2021, the practice had grown to a small roster of recurring clients across Ontario and Quebec, mostly founders of companies between twenty and two hundred people, all of them dealing with some version of the same problem: too much information, too little clarity, and decisions that kept getting deferred. Amelia kept the practice deliberately small, taking on no more than three active engagements at a time, because the quality of attention required does not scale the way a slide deck does.
The firms that struggled most were not short on data but on the capacity to think clearly.
— Takes on no more than three active engagements at a time
— All deliverables written in plain language, no jargon or proprietary acronyms
— In-person sessions available in Toronto, Montreal, and Ottawa
— Frameworks are sourced and named so clients can use them independently
— No templated slide decks; every document is written for the specific client
Four weeks, one high-stakes decision. We map the decision space, surface hidden assumptions, and produce a written decision map the team can use without a consultant in the room. Includes one two-hour working session and one debrief call.
Eight weeks, structured interviews with up to six team members, a review of existing processes, and a written diagnostic report with prioritized recommendations. Designed to be acted on independently after delivery.
A half-day working session each quarter, preceded by a written brief and followed by a one-page action summary. For teams that have a strategy and want to pressure-test it regularly with an external perspective.
Single-day or half-day sessions for values alignment, roadmap prioritization, or post-mortems. Session structure is designed in advance. Available in-person in Ontario and Quebec, or remotely across Canada.
The best first step is a thirty-minute introductory call. Use the form below or reach out directly. Amelia responds to all enquiries personally, usually within one business day.
+1 416-882-5043
Book a free callAmelia Caldwell handles every engagement personally. No handoffs to junior staff, no account managers in between. You work with the same person from the first call to the final debrief.
Every project has a defined scope and a fixed end date. Engagements run four to twelve weeks. If the problem needs longer, we talk about why before extending.
Outputs are plain-language documents: decision maps, prioritization frameworks, meeting protocols. Nothing that requires a consultant to interpret.
Every leadership team has at least one of these on record: a decision that was made, unmade, remade, and then quietly shelved until someone raised it again at the wrong moment in a quarterly review. The frustration is real, but the instinct to blame indecisiveness or weak facilitation usually misses the point. What keeps a decision cycling is almost never a lack of process — it is a disagreement that has not yet been named clearly enough to be resolved. This guide walks through how to structure a decision review session specifically for that situation: where the team has already reversed course at least once, where trust in the room may be strained, and where the goal is not another vote but a genuine close.
Read more →A few weeks ago I was fifteen minutes into what should have been a scoping call when I realized we were still untangling which version of the org chart was current. The client had sent six documents the night before, each one confidently titled "FINAL," and none of them agreeing on who owned the budget. We spent the first third of our hour on archaeology. That kind of call is recoverable — most first conversations are — but it sets a particular tone, and that tone tends to cost more than people expect, in time, in goodwill, and eventually in fees. What follows is a frank account of what actually helps before a first consulting engagement begins, drawn from years of those calls, the good ones and the ones that started in the weeds. The goal is not to hand you a checklist, but to give you a clear enough mental model that you can make good judgment calls on your own, whatever your situation looks like.
Read more →Most post-mortems begin the same way: someone books a meeting room for ninety minutes, pastes a shared document into a Slack channel, and everyone arrives with a privately rehearsed version of events that places them somewhere adjacent to blameless. By the end of the session, the document contains thirty bullet points, half of which say some variation of "improve communication," and three action items assigned to people who are already overloaded. Six weeks later, the document sits in a folder no one opens, and the team makes the same mistakes on the next project. This is not a failure of intention — everyone in that room genuinely wanted to do better. It is a failure of structure. A post-mortem is a precision instrument, and when you pick it up without knowing how it works, it tends to cut in the wrong direction. This guide is concerned with how to run one that produces findings your team will actually carry forward, written for the consultant or team lead who has sat through enough unproductive retrospectives to know that something needs to change.
Read more →Amelia Caldwell spent eleven years in organizational strategy before founding MindVault Lab Flow in 2019. She trained under a systems-thinking framework at the Rotman School of Management in Toronto, then spent four years advising mid-sized manufacturing firms on operational restructuring across Ontario and Quebec. A turning point came when she realized the firms that struggled most were not short on data but on the capacity to think clearly under pressure. She left consulting at a large firm to work directly with founders and leadership teams, one engagement at a time. Outside work, she keeps a handwritten journal of decision frameworks she finds genuinely useful, a habit she started in 2014 and has not broken since.
The clearest signal is that your team has the information it needs but keeps deferring the decision, or keeps making decisions that do not stick. If the problem is primarily technical, legal, or financial, this practice is probably not the right fit and Amelia will say so on the first call.
Yes, remotely. Most of the work happens asynchronously anyway. In-person sessions are available in Toronto, Montreal, and Ottawa without a travel surcharge. For other locations, travel costs are added to the scope at cost.
