Skip to content
Trevin Nimaladasa

Essays

Long-form arguments about decisions in systems programs. Each one makes a claim, names the decision it bears on, and shows what good looks like.

14 ESSAYS · BUSINESS ANALYSIS · RSS

  1. NO. 05 · · 4 MINWhat you resource is your strategyEvery 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.
  2. NO. 08 · · 1 MINPractice Archetypes — Why Quality Variance Isn't A People ProblemRequirements quality is a property of the practice's architecture, not of the people you hire into it.
  3. NO. 07 · · 1 MINDecision DebtEvery requirement that cannot be traced to the decision that authorised it is debt, and it always falls due at the worst moment.
  4. NO. 111 · · 9 MINMost Business Analysts write requirements. Senior BAs build the system that writes them.Senior business analysts design the system that produces good requirements, not just the requirements themselves.
  5. NO. 02 · · 4 MINMinimum Viable Business AnalysisMVBA 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.
  6. NO. 108 · · 15 MINFOBA 2025 Talk - Career Capital for BAs: How to Become So Good They Can't Ignore YouThe write-up of my FOBA 2025 talk on building career capital as a business analyst.
  7. NO. 59 · · 5 MINThe Great Escape: Breaking Free from the Whirlwind of Rework with a Strong Definition of Ready (DOR)A strict Definition of Ready, enforced as a gate before build, is the most effective way to cut rework, and developers should push back on any requirement that fails it.
  8. NO. 47 · · 5 MINBreaking Free: Latest Trends in Overcoming Requirements Challenges in Digital Transformation ProjectsNew requirements will surface at every stage no matter the method, so the answer is structured methodologies for implementation, Agile for continuous improvement, thorough business analysis and cautiously validated GenAI.
  9. NO. 54 · · 4 MINDX Lockdown: Why Digital Projects Get Stuck Behind BarsMisunderstood requirements damage an ERP project before, during and after delivery, and the cost shows up as scope creep, rework, poor adoption and lost trust.
  10. NO. 70 · · 7 MINNeeds AssessmentA fifteen-step needs assessment for ERP implementation that covers processes, resources, support, readiness and requirements, not just system features.
  11. NO. 83 · · 2 MINChange Readiness QuestionnaireCreating a comprehensive questionnaire is essential for navigating the complexities of ERP implementation and ensuring that your organization's unique needs are addressed.
  12. NO. 84 · · 3 MINChange Request TemplateThis template is designed to facilitate the structured submission, evaluation, and negotiation of change requests in ERP projects.
  13. NO. 99 · · 10 MINTest PlanningCreating a comprehensive test plan for ERP implementation involves meticulous planning across several testing stages, each with its unique focus and objectives.
  14. NO. 102 · · 8 MINVendor Evaluation Checklist and QuestionnaireSo, you're in the market for an ERP system—congratulations on taking a monumental step towards transforming your business operations!