Most operational problems are invisible - not because the work is complex, but because no one has written down how it actually moves. We document current-state operations, surface where they break, and design leaner workflows before any technology decision is made.
Every organization has a gap between the process on paper and the process in practice. Work routes around outdated rules. Decisions get made in hallways. Exceptions become the norm. Staff carry institutional knowledge that exists nowhere in writing. When that person leaves, the process goes with them.
We close that gap - by observing, interviewing, and documenting what is actually happening before recommending what should happen instead. The result is a verified picture of current-state operations: decision logic, routing rules, exception paths, bottlenecks, and the informal workarounds that signal where the formal process has already failed.
That documented current state is the prerequisite for everything else - workflow redesign, system configuration, automation, technology selection, or organizational change. Without it, any intervention is guesswork.
Observe, interview, and map how work actually moves - not how the org chart says it should. Every handoff, every workaround, every undocumented decision captured in writing.
Turn the documented current state into a diagnostic - where volume concentrates, where decisions stall, where exceptions outnumber the rule. Patterns that are invisible in the day-to-day become legible on paper.
Elicit, structure, and validate what the redesigned system must do. User stories, acceptance criteria, business rules - grounded in what the current state revealed, not what stakeholders assumed.
Every state, every transition, every exception path - formally named and validated before any tool is configured or any org change is implemented.
Configure case management and workflow platforms against formal specifications - data models, rules engine, security, dashboards, and analytics. Standards-governed practice built on the 100+ federal deployments our principal supported.
Define the measures, dimensions, and data sets that will make the redesigned operation visible. No dashboards built on ambiguous data. No metrics without a definition agreed on in advance.
136 documented work products. 100+ distinct deployment environments. 9 federal agency client programs. Our principal's delivery record with MicroPact/Tyler Technologies teams: current-state documentation, workflow redesign, system configuration, and operational analytics - continuous delivery 2013-Present.
Federal client base: DHS / ICE · DOD · IRS · CFPB · SEC / OIG · DOL · Air Force
Delivered by Chromial's principal via MicroPact/Tyler Technologies delivery teams (2013-2023) - independent contract performance, not CHROMIAL LLC prime or subcontract awards.
Service Line 01 · The starting point for every engagement
Before any process is redesigned, any tool is selected, or any automation is scoped, we document how work actually moves today. That means going past the org chart and the policy manual - into the work itself. Who touches it, what they decide, what they do when the rule doesn't apply, and what they've never been asked to write down.
Observation-based documentation of how work moves through an operation - every handoff, queue, approval, and routing decision captured in a format that can be validated, challenged, and redesigned.
The informal rules that govern real decisions - who approves what, under what conditions, and what triggers an exception - extracted from institutional knowledge and put on paper before they disappear.
Every informal workaround is a signal that the formal process has already failed somewhere. We document them systematically - as evidence of where redesign is needed, not as violations to be corrected.
Structured elicitation sessions that surface what people know but have never been asked to articulate - the business rules, exception logic, and tribal knowledge that live in individual heads and nowhere else.
The process that actually runs alongside the official one - the spreadsheet that replaced the form, the email thread that substitutes for the system, the manual step that automation skipped over. All of it documented.
A consolidated, verified picture of operations as they stand - the reference document against which all redesign, requirements, and technology decisions are measured.
Service Line 02 · From documentation to diagnosis
Documentation reveals structure. Analysis reveals dysfunction. Once the current state is on paper, patterns emerge that were invisible day-to-day - where volume concentrates, where decisions stall, where exception rates signal a broken rule, and where process complexity is hiding a simple underlying operation.
Identify where work accumulates, where handoffs break down, and where throughput is limited by a single decision point, approval chain, or resource constraint. Named, located, and quantified.
High exception rates are a symptom of a rule that doesn't fit the actual work. We track exception patterns across a process, identify the recurring cases driving them, and distinguish broken rules from genuinely complex edge cases.
Some parts of an operation carry far more decision weight than their footprint suggests. We map where judgment concentrates, where it can be delegated, and where explicit criteria can replace implicit discretion.
A structured measure of how many states, transitions, and decision branches a workflow contains - used to identify operations that are more complex than the underlying work requires.
Before any dashboard is built, the measures are defined: what counts, what doesn't, how terms are operationalized, and what the number is actually supposed to tell a manager. No metric without a definition agreed on in writing.
A consolidated diagnostic - the specific locations in the operation where redesign will produce the highest return. Ranked by impact, not by ease. The direct input to workflow redesign.
Service Line 03 · 18 documented work products
We translate operational intent into structured, testable requirements that a system - human or automated - can be built against. Elicitation is grounded in what the current-state documentation revealed, not in what stakeholders assume is happening.
18-module working session methodology for defining measures, dimensions, and reporting requirements before any configuration begins. Deployed across 12+ federal agencies.
Complete methodology: user story standards (INVEST model), epic management, backlog refinement, acceptance criteria, and sprint integration. Documented across 9 work products.
Joint Application Design working sessions that surface implicit business rules and decision logic before they become design errors. Structured elicitation that turns tribal knowledge into written requirements.
Structured approach from business objectives down to operational specifications. Requirements standards and quality criteria that keep scope controlled across multi-phase engagements.
Field-level requirements captured from working sessions into formal data element specifications - the direct input to data model design.
Internal and client-facing standards for clear, testable, implementable requirements. Applied as a consulting discipline across all engagement types.
Service Line 04 · 9 documented work products
Once the current state is documented and the inefficiencies are named, we design the replacement - a complete formal specification of how work should move. Every state named, every transition documented, every exception path explicit. The deliverable that stands alone regardless of what technology, if any, follows.
Comprehensive workflow specification methodology: States, Statuses, Event Categories, Events with Actions and Conditions - the full decision grammar of an operation, written down before anything is built.
A lean redesign of the current state - removing steps that exist only because the previous step was broken, collapsing redundant approvals, and routing exceptions to the point where they actually arise.
Visual process diagrams designed to be validated by business owners. Not documentation of what was built - documentation of what should be built, ready for challenge before commitment.
Every decision rule governing the workflow - explicit conditions, thresholds, authorities, and exceptions - captured in a single reference document. The authoritative record of how the operation makes decisions.
Processing time calculation, deadline tracking, and active-day logic. The governance layer that makes work visible, accountable, and measurable - defined before implementation.
Where workflow redesign has staffing or structural implications - role changes, consolidated functions, eliminated handoffs - we document the organizational change alongside the process change.
Service Line 05 · 29 documented work products · largest service line
We configure case management and workflow platforms against formal specifications - data models, forms, dashboards, search, rules engine, security, and reporting. Standards-governed practice built on the 100+ federal deployments our principal supported on Entellitrak® delivery teams (MicroPact / Tyler Technologies). Vendor-trained at MicroPact's Herndon headquarters, our principal has worked in the platform for more than a decade and still supports legacy etk systems.
AE Guidelines & Standards (v1.0-v2.0) governing all implementation work: naming conventions, code libraries, SQL standards, security requirements, and package structure. Applied across every client deployment.
Tracked Data Objects (TDOs), Reference Data Objects (RDOs), Business Tracked Objects (BTOs) - structured data model configuration with documented lookup standards, null checks, and ordering rules.
Rules Engine for business rules, Condition Scripts for workflow event conditions, Action Scripts for automated triggers. Decision logic implemented from business rules documentation - not invented during configuration.
Federal-grade security: role-based access (Administrator, Manager, Analyst, Read-only), CAC/PIV integration, SAML2/Shibboleth SSO, XSS prevention, SQL injection protection, and 508 compliance.
Measures, dimensions, data sets, reports, and dashboard collections configured against client-validated requirements. Reporting pipelines from Jaspersoft Studio to scheduled delivery.
Advanced searches, display mappings, data forms, view pages, and application launcher - all configured to agency-specific requirements. JavaScript and CSS standards enforced across implementations.
Service Line 06 · Multi-agency · 18-module methodology
We define the data layer before building it. Measures, dimensions, data sets, reports - specified in working sessions with client stakeholders, then configured against those definitions. No dashboard is built before the underlying question is written down.
As process-mining and workflow platforms move event and case data directly into enterprise analytics tools, the two disciplines converge: the operational data model that connects how work happens to what the business measures is the deliverable - not a process map on one side and a dashboard on the other.
Structured methodology for defining what the data must answer before any report is built. Client formulates business questions; consultant maps to measures and dimensions. Deployed across DHS, DOD, IRS, CFPB, DOL, SEC, and Air Force.
Quantifiable data elements (count, sum, min, max, mean) paired with categorical dimensions (status, type, role, time). No metric left undefined. No report built on terms that mean different things to different teams.
Reports structured to surface operational patterns - not just activity counts. Trend analysis, exception tracking, SLA compliance, and throughput visibility - specified before any tool is selected.
Three supporting service lines with substantial documented delivery records - surrounding and enabling the six core practices.
Agile delivery management across complex, multi-stakeholder engagements. Sprint ceremonies, backlog refinement, demo scripts, retrospectives, and project initiation - standardized across client engagements.
13 documented work products · active 2023 sprint artifacts
Production deployment planning, upgrade impact analysis, infrastructure migration, and rollback procedures. Version-by-version upgrade impact assessments for client agencies across a decade of platform releases.
21 documented work products · largest supporting line
Structured training curriculum and delivery: named course sequences, full participant guides across platform versions, and distributed training sites for client capability development.
18 documented work products · multi-version curriculum
Structured entry points from rapid diagnostic to full operational architecture. Each tier produces work that stands alone and prepares the ground for the next.
A rapid audit of one operational surface - inbox, funding pipeline, content workflow, or support queue. Documents the decisions being made repeatedly, maps who is making them, and classifies each for delegation or escalation.
Current-state documentation and lean redesign of a specific workflow. We map what is actually happening, identify where and why it breaks, and deliver a formal specification of what should replace it.
Full current-state documentation, operational intelligence analysis, workflow redesign, requirements elicitation, and business rules documentation. The complete consulting layer before any technology decision is made.
"We don't redesign operations from a blank page. We document what is actually happening - then design what should replace it."
NAICS 541611 - Administrative & General Management Consulting
Every engagement begins with a clear picture of where your operations are and what the next layer needs to look like.