FOUNDER | CLARITI
Trevin Nimaladasa
Trevin is a business analyst, requirements engineer, and author focused on bridging the gap between business intent and system delivery. He has designed requirements architectures for enterprise transformation programmes, and published the Requirements Engineering field guide (trevbuilds.github.io/guides/businessanalysis/Requirements), which catalogs a hierarchy system and 12 reusable work-type templates covering discovery through delivery. His work centers on moving the BA role from execution (transcription) to architecture (system design), and building institutional knowledge systems that let SMEs author requirements without BA bottlenecks. He previously spoke at FOBA 2025 on Career Capital for Business Analysts.
Presentation: Career Capital 2.0: From Documentation Clerk to Requirements Architect
The BA role is at an inflection point. As AI handles transcription, the “clerk” model—where BAs listen to SMEs and write requirements—is becoming commoditised.
Career Capital 2.0 is the evolution to architect thinking: designing systems where others write good requirements without BA mediation.
The clerk model breaks at scale: change requests with invisible sources, orphan stories with untestable criteria, permanent SME dependency, no institutional memory, and transcription is automatable.
The architect model inverts this. Stop writing requirements. Design the environment where they get written well.
The five structural choices (proven in practice) include:
-
Hierarchy: Six levels (Intent → Capability → Journey → Process → Requirement → Test) decomposing business intent into verifiable behavior
-
Work Types & Templates: Pre-built scaffolds for Epic, Journey, Process, Requirement, Story, Task, Decision, Constraint
-
Naming Convention: TYPE | Domain | Behavior (makes traceability visible in the title)
-
Traceability Rules: Link types that matter; nothing invisible (Implements vs. Relates-to distinction)
-
Quality Gates: Definition of Ready/Done at each transition stage Authority shifts from execution (writing requirements) to architecture (designing the system). When SMEs author within a well-designed environment, they produce consistent, traceable, testable requirements—without BA bottlenecks. Career Capital 2.0 is built on four capitals: Domain (hierarchy mastery), Delivery (scalable systems design), Influence (architecture authority), and IP (documented patterns that persist beyond you). This shift protects BA authority in the AI era.