The same failure, in places that had nothing else in common.
Avanza Methods helps organizations build the systems that make knowledge trustworthy, execution reliable, and AI actually useful, then hand the system to their team.
The Pattern
IT. Policy implementation. Finance. A public agency with approximately 14,000 employees. Different environments, different mandates, different pressures.
The same root problem kept appearing.
Knowledge nobody owned, scattered across systems nobody trusted. Teams making consequential decisions from duplicated spreadsheets, stale files, and data with no clear owner. What held the operation together was tribal knowledge, which is another way of saying it held together until the right person left.
After watching that repeat, and hearing the same frustration from leaders across sectors, I stopped treating it as an industry problem.
Every organization needs clear, authoritative sources of truth for the work that matters. I have spent years building exactly that.
What I Refuse to Sell
The standard move is to sell technology as a fix for operational chaos. The current version of that move is to point AI at a broken knowledge base and call it a strategy.
AI is a catalyst. It accelerates whatever it touches, including everything wrong underneath it.
Selling software before the knowledge and delivery systems are sound is not a shortcut. It is a more efficient way to fail.
The Name Is the Argument
Avanza is Spanish for advance. Not a single transformation, but progress, improvement, and elevation over time. Organizations do not arrive at good operations. They get better at them.
Methods is the action layer. A method is a specific, procedural way of doing something: how people perform work, make decisions, communicate, maintain information, and carry responsibility. Strategy alone produces nothing. Someone has to act, and there has to be a reliable way to act.
Systems is the environment those methods run inside. People, processes, knowledge, data, technology, governance, decision rights, feedback loops, and tools working together to produce an outcome.
The distinction is simple. Methods describe how action happens. Systems make that action repeatable. A system without practical methods stays abstract. A method without a supporting system works once and then fails to scale.
Organizations need both. That is the whole name.
The Mark
Two peaks and an upward line moving left to right.
The first peak forms the A. The two peaks together form the M. The sweeping line creates a subtle S, and its lower portion doubles as the crossbar of the A.
The line continues past the second peak and keeps rising, because two peaks mean continued ascent rather than a single destination.
The Sequence
-
Knowledge is the foundation.
An organization needs knowledge that is trustworthy, current, and findable, including the institutional knowledge that lives in people rather than files.
-
Execution is the engine.
Project management discipline turns knowledge into action through ownership, process, handoffs, decision rights, risk management, and feedback that carries forward.
-
AI is the catalyst.
Once the foundation holds and execution is reliable, AI amplifies what already works.
The order is not a preference. It is the argument.
Background
Approximately 15 years across IT, public policy, finance, process improvement, and organizational governance.
Established and launched a centralized Project Management Office supporting approximately 14,000 employees, including operational protocols and an enterprise steering committee for project approval, risk evaluation, and portfolio oversight.
Led cross-functional improvement initiatives that produced tens of millions of dollars in documented cost savings.
Served as Regional Project Manager on a $2.1 billion statewide IT program.
Different environments, different constraints. The range is the point.
A problem that appears in a policy implementation workflow and again in a statewide IT program is not confined to one sector. The setting changes. The need for reliable knowledge, clear ownership, and disciplined execution does not.
Credentials
- Project Management Professional (PMP)®
- PMI Agile Certified Practitioner (PMI-ACP)®
- PMI Project Management Office Certified Professional (PMI-PMOCP)™
- Lean Six Sigma Black Belt
- Professional Scrum Master I (PSM I)
- Google AI Analytics Professional Certification
- IBM AI Developer
Credentials tell you how I was trained. How I work matters more.
Two Lines I Will Not Cross
-
I will not tell you your situation is better than it is.
The Organizational Knowledge Assessment exists to give you an accurate picture, including the parts that are uncomfortable to read. A diagnosis you enjoy hearing and cannot act on is worth nothing.
-
I will not build a system that depends on me.
I do not design engagements around continued dependency. I design the architecture, guide your team through building it, and leave the capability with your people.
Nobody should be held hostage to a vendor, including me.
Avanza means advance. Methods create action. Systems make it repeatable.
Clarity is what scales.