Our Founding Principles

Some people learn
systems. Others
think in them.

The methodology is formal. The credentials are real. But the ability to walk into a broken operation and see it clearly in twenty minutes, before anyone has explained anything, that part was never taught in a course.

Myths is deliberately small. That is not a stage. It is the model. A limited client roster means every engagement gets full attention. Ask about availability.

The methodology names what you can see. The instinct finds what you cannot. Myths was built at the intersection of both.
Myths · Toronto, ON
i.The long view

Before there was a name for it,
there was the work.

Decades before Myths existed, the pattern was already there. Walk into a system. See what everyone else has normalized. Name the thing nobody has said out loud. Fix it and move on.

It happened in warehouses. In clinics. In back offices running on software held together with workarounds and institutional memory. In conference rooms where the meeting was about the wrong problem. The industries changed. The pattern did not.

What took time was not developing the instinct. That arrived early and never left. What took time was understanding that the instinct had a structure behind it, and that the structure had a name, several of them, and that those names were worth learning formally so the work could be explained to people who needed a framework before they could trust a diagnosis.

The frameworks were never the point. They were the vocabulary that made the instinct legible to the people who needed to hear it.

LEAN. Kaizen. Just-in-Time. Agile. Waterfall. PMP. Each one is a lens. Each one illuminates something the others miss. The skill is not knowing which framework to apply. The skill is knowing which lens fits this room, this problem, this team, this moment, and then putting it down when it stops being useful.

Most consultants pick a methodology and stay inside it. The work that actually gets done lives between them.

ii.The methodologies

Formal training in systems thinking across the full spectrum of operational methodology. Each framework is a tool. None of them is a religion.

Manufacturing origin
LEAN
Eliminate waste. Every activity either adds value for the person at the end of the process or it does not. If it does not, it is a candidate for elimination. The discipline to see waste clearly in your own operation is rarer than it sounds.
Continuous improvement
Kaizen
Change for the better, incrementally and relentlessly. Not a single overhaul but a culture of small corrections that compound over time. The organizations that do this well stop needing expensive rescues. The ones that do not accumulate myths instead.
Flow and pull
Just-in-Time
Produce exactly what is needed, when it is needed, where it is needed. The opposite of buffer-and-batch thinking. When applied to information flows and handoffs, not just inventory, it exposes the bottlenecks that are invisible in traditional operations.
Iterative delivery
Agile
Deliver value in working increments. Adapt to what you learn. Do not build twelve months of requirements before testing a single assumption. Applied correctly outside software, Agile is a powerful diagnostic tool for organizations that have been planning instead of doing.
Sequential structure
Waterfall
Define the full scope before the first resource is committed. When the problem is well-understood and the requirements are stable, structured sequential delivery prevents the scope drift that kills otherwise good projects. The skill is knowing when this applies and when it does not.
Project governance
PMP Certified
Project Management Professional certification. The formal language of scope, schedule, cost, risk, and stakeholder management. The credential that proves the instinct for systems has been tested against a rigorous international standard, not just accumulated through experience.

The credential list is not the point. The point is that every framework on it was learned not to add letters after a name but because it genuinely changed how a broken system could be seen and fixed. The methodology earns its place or it gets set aside.

iii.The way of working

What a Myths engagement
actually looks like.

What we bring in
Day 1
No assumptions. The brief gets read but not believed until the room confirms it. The real problem is almost always one conversation away from the stated problem.
Day 2
The map. Every input, every handoff, every system, every human dependency drawn out until the whole thing is visible in one place. This is usually when the client sees their operation clearly for the first time.
Day 3
The diagnosis. Not a list of problems. A structured finding with root causes, cost-of-inaction estimates, and a prioritized path forward. Written, specific, and actionable without us in the room.
After
The fix. Either a scoped project, an ongoing retainer, or a complete handoff spec. The engagement ends when the problem is gone, not when the contract runs out.
What makes it different
Both sides at once. The technical system and the human system are diagnosed simultaneously. A perfect process with the wrong person in a key role fails. A great team running a broken process fails differently. You have to see both.
No investment in the current state. We did not build what exists. We have no reason to protect it. That absence of loyalty to the way things are is what makes the diagnosis honest.
The right framework for this problem. LEAN for waste elimination. Kaizen for compounding improvement. Agile for iterative delivery. Waterfall when scope is fixed. The framework serves the problem. Never the other way around.
Small and intentional. Myths will never be a large firm. Large firms have incentives to extend engagements. We have an incentive to fix things quickly and cleanly so the referral that follows is worth more than the retainer. A small roster means every client gets the same person, the same attention, and the same instinct that found the problem in the first place.
iv.Credentials and training

Formal certification across the full operational methodology spectrum, applied across healthcare, manufacturing, logistics, professional services, and technology sectors in Ontario and beyond.

PMP Certified
LEAN Practitioner
Kaizen Methodology
Just-in-Time Systems
Agile
Waterfall / SDLC
Database Architecture
Systems Analysis
Process Mapping
Organizational Design
AI Integration
Toronto, Ontario

The credential list is long because the problems are varied. A manufacturing efficiency engagement requires a different lens than a healthcare data migration or a professional services workflow rebuild. The methodology follows the problem. The instinct finds the problem first.

The right engagement
starts with the right conversation.

Not a pitch. Not a proposal. A straight conversation about what is broken, whether it is fixable, and what it would take. Fifteen minutes. Free. That is where every Myths engagement begins.

Book a free clarity call Take the assessment
Myths Advisory Corporation