# Trevin Nimaladasa

> Field notes on decisions in large systems programs. Trevin Nimaladasa is a business analyst and transformation lead in Melbourne (CBAP). His argument: systems are rarely the problem; leadership decision-making is.

Each register entry makes one claim, names the decision it bears on, and says what to do about it. Every entry is also available as Markdown at its URL plus `.md`; all of them together are at /llms-full.txt.

## The register

- [No. 05 · What you resource is your strategy](https://trevin.co/writing/what-you-resource-is-your-strategy.md): Every organisation has two strategies: the one in the deck, and the one visible in where its scarcest people, calendar time and decision attention actually go. When they disagree, the second one wins.
- [No. 04 · Vendor selection is a strategy test](https://trevin.co/writing/vendor-selection-is-a-strategy-test.md): A weighted scoring matrix measures how well vendors answer your questions. It does not measure whether you knew what to ask — and selections fail on the second problem far more often than the first.
- [No. 03 · Why ERP programs fail in plain sight](https://trevin.co/writing/why-erp-programs-fail-in-plain-sight.md): ERP failures are rarely surprises. The signals are visible months before anyone uses the word, and almost all of them are organisational rather than technical.
- [No. 02 · Minimum Viable Business Analysis](https://trevin.co/writing/minimum-viable-business-analysis.md): MVBA is not less business analysis. It is business analysis aimed at the next decision that actually needs to be made — and a test for telling analysis apart from inventory.
- [No. 01 · Decision governance before delivery governance](https://trevin.co/writing/decision-governance-before-delivery-governance.md): Programs in trouble tend to add forums rather than decisions. The difference between tracking work and owning trade-offs, and how to tell which one your governance actually does.

## Guides

- [The MVBA Field Guide](https://trevbuilds.github.io): Minimum Viable Business Analysis: how to aim analysis at the next decision that needs making, and stop producing inventory.
- [EZRP: ERP, module by module](https://ezrp.io): Maps of the modules, the processes inside them and the workflow steps teams actually run. Written so a delivery lead can read one before the design workshop.
- [What You Resource Is Your Strategy](https://trevin.co/writing/what-you-resource-is-your-strategy): An organisation's strategy is already legible in its resourcing decisions, whether or not anyone wrote it down. The book-length version of entry 05. (in progress)

## Tools

- [Decision Clarity Score](https://trevin.co/tools/decision-clarity-score): How clearly your program knows who decides what — and where it doesn't. (in build, Clariti)
- [IT Optimisation Scorecard](https://dxadvisory.com/score): Where your technology spend is working for the operating model and where it's compensating for it. (live)
- [EZRP Navigator](https://ezrp.io): Click through ERP domains, value streams and the processes inside them. (live)
- [Vendor RFx Killer](https://trevin.co/tools?tool=vendor-rfx-killer): The four tests worth more than a weighted matrix, run as a structured exercise. (concept, Clariti)
- [Scalable Practice Score](https://trevin.co/tools?tool=scalable-practice-score): For practice leaders: how much of your delivery depends on people who can't be replaced. (concept, Clariti)
- [Chockers](https://chockers.ai): Answers calls, books jobs and chases quotes for Australian tradies. A different audience, same instinct. (live)

## Optional

- [About](https://trevin.co/about)
- [Talks](https://trevin.co/speaking)
- [RSS](https://trevin.co/rss.xml)
- [Advisory work: Clariti](https://clariti.global)